How to work around with the retraction of data into R/3 from SEM

How to work around with the retraction of data into R/3 from SEM

How do I do a work around with the retraction of data into R/3 from SEM?

    Requires Free Membership to View

    Login

    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.

SEM BPS provides standard retraction functionality for certain functional areas, like cost center planning. If you want to retract data for these functional areas, you can use standard functions delivered by SAP. If you want to retract data for functional areas that do not have standard retraction functionality, you have to develop your own ABAP program. You can review the standard BAPIs in SAP R/3, and use them if they fulfill you requirement. If there is no suitable BAPI for your requirement, you can develop custom RFC function to retract data. You can integrate your custom retractor into your planning folders to send data into R/3 after the user completes his/her tasks in BPS. Or you can use your function as a standalone ABAP program to read data from the transactions cube (which your plan data is stored) and post the data into the relevant R/ 3 component.

This was first published in December 2004