How data comes from SAP to the IDoc

How data comes from SAP to the IDoc

How does the data actually come from SAP to the IDoc?

    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.

You need a function module or another self-written program that creates the data to send.

If the triggering transaction supports customizable NAST messaging, then you can create a NAST message that supports ALE or IDoc. The link between the message and IDoc is defined via the process code in the partner profile WE20. Whenever the NAST message is processed it will make a call to ALE_PROCESSING in program RSNASTED or EDI_PROCESSING in program RSNASTED, which does the job for you and eventually will call the function module that fills the data hive.

If a program does not support messaging via NAST then you need to create the IDocs with your own routine and then call MASTER_IDOC_DISTRIBUTE. You can find more in-depth developer know-how in SAP R/3 Guide to EDI and Interfaces.

This was first published in October 2004

Back to top