Overwriting old reports in the SAP QA system

Overwriting old reports in the SAP QA system

When I transport customized programs from the DEV system to the QA system, everything works fine. But, when the ABAPers check their work in the QA system, they find their latest reports don't overwrite the older reports and the 'last changed' date of the reports remains the old date.

What do you think the problem is, and how can I fix it?

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Have a look at the log file generated by TP. In transaction STMS, choose your transport request and select the 'view log file' button. If TP did not import the reports, it should report why.

One reason might be that the reports were changed in the target system. If so, import the request using the 'overwrite originals option', which can be selected when you start the import.

This was first published in December 2006

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.