IDocs with Message Control Provide Oversight of Goods Movements

  • by Michal Krawczyk, SAP Integration Consultant, BCC, Poland
  • March 25, 2009
Learn how to create a new Intermediate Document (IDoc)output for sending goods movements when you use transaction MIGO so that you can retain all the benefits of output message control.
Key Concept

An Intermediate Document (IDoc) is a standard SAP document used for message exchange between SAP application systems (such as SAP R/3, SAP ERP, SAP SCM, or SAP Customer Relationship Management [SAP CRM]). Material documents created from goods movements sometimes need to be delivered to different external systems. IDocs are the most standard way of interfacing SAP application systems with third-party systems.

Imagine you need to send goods movement data to external third-party systems. SAP doesn’t deliver any standard Intermediate Document (IDoc) output for this, and suggests use of a standard user exit to send the data. However, I prefer to use message control. Note that both options require development.

Most transactional interfaces (such as sending purchase orders, sales order confirmations, or deliveries) use a message control mechanism to send IDocs. If you use user exits instead, you lose a few important features:

  • You cannot use an access sequence to specify which movements (from which plants, storage locations) need to be delivered to the external warehouse management system. You would need to hardcode it in the user exit.

  • You cannot repeat the output (if this is necessary) from a material document transaction. In addition, you cannot check if the output was successful in any other way except by checking transaction WE02 (IDoc monitoring).

When you send material documents created by good movements as an IDoc using standard message control, you gain the ability to monitor your IDocs from a material document. You can also easily check for errors and resend the IDoc directly from the material document overview.

To use standard message control to send IDocs from material movements created using transaction MIGO, you need to follow the steps in the next section to implement the functionality. The steps are required because no predefined output type exists for an Electronic Data Interchange (EDI) Application Link Enabling (ALE) scenario for transaction MIGO.

Michal Krawczyk

Michal Krawczyk is an SAP consultant for BCC Poland. He works with SAP XI/PI, ALE/EDI, CRM middleware, and other SAP interface-related technologies. He was presented the Top Contributor award in the XI/PI area on SDN in 2005, 2006, and 2007, and the SAP Mentor award in 2007. He has published more than 60 articles about SAP XI and MDM on SDN and has written a book about PI published by SAP PRESS. He is also an SAP Professional Journal author.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.