How to Trigger an IDoc When a Purchase Order Is Created in SAP

Introduction

In the world of SAP, IDocs (Intermediate Documents) play a crucial role in integrating different systems and facilitating data exchange between business partners. Automating IDoc generation when a Purchase Order (PO) is created not only streamlines operations but also minimizes manual intervention and errors. This guide walks you through the step-by-step process to trigger an IDoc every time a PO is created in SAP.

Understanding the Core Components

A Purchase Order (PO) in SAP represents a formal request to a vendor to supply goods or services under specified conditions. IDocs are structured data containers used to exchange information between SAP systems or with external systems via ALE (Application Link Enabling). In this context, we leverage SAP's message control and output determination mechanism to automate the creation and dispatch of IDocs when a PO is created.

Preparatory Steps Before Configuration

Start by accessing the transaction NACE. NACE is the transaction used to configure output types for various applications. For POs, select the application "EF" (which stands for Purchase Order).

Determine the Active Message Schema

To find out which message schema is active, go to transaction SPRO. Navigate through:
Materials Management -> Purchasing -> Messages -> Output Control -> Message Determination Schemas -> Define Message Schema for Purchase Order
Click on "Assign Schema to Purchase Order." You’ll typically find that the procedure "RMBEF1" is active for application EF.

Exploring the Output Type NEU

Now return to NACE, select EF, and click on "Output Types." For this demonstration, we’ll use the standard output type "NEU". Double-click on NEU to configure it.
Make sure the checkboxes for "Access to conditions" and "Multiple issuing" are checked. These settings allow the system to determine the output type based on condition records and permit multiple outputs for the same document.

Setting Up Output Medium for IDoc

On the left-hand side, click on "Processing Routines." Ensure there is an entry for medium "A" which stands for Distribution via ALE. This setting is vital for triggering IDocs.

Creating Condition Records

From the main screen of NACE, select EF and click on "Condition Records." Then select NEU and click on "Condition Records." In the pop-up, choose the radio button for "Purchase Organization."
Add a new record with medium "A" (ALE) and date/time set to "4" (Send Immediately). This ensures that as soon as a PO is created, the IDoc is triggered and sent without delay.

Date and Time Configuration

The date/time field in the condition record should be set to "4" which means the output will be triggered immediately upon document creation. This setting is crucial for real-time processing.

Ensuring ALE Configuration

Make sure that the basic ALE configuration is already done. This includes setting up logical systems, partner profiles, and port definitions.
In the partner profile, use the message type "ORDERS" and the IDoc type "ORDERS05." These are standard types for Purchase Orders in SAP.

Partner Profile Essentials

Navigate to transaction WE20 to access or create partner profiles. Under the appropriate partner (e.g., the receiving system), ensure the following settings in the "Message Control" tab:
  • Message Type: ORDERS
  • Output Type: NEU
  • Process Code: ME10 (for PO Create) and ME11 (for PO Change)
Ensure the partner profile is configured to process inbound and outbound parameters as needed.

Assigning Process Codes

Process codes are linked to function modules that interpret the IDoc data. ME10 is used for PO Creation and ME11 for PO Changes. These should be assigned correctly in the partner profile to enable smooth processing.

Testing the Setup

Create a new Purchase Order using transaction ME21N. Once saved, check transaction WE02 to view the generated IDoc. Verify the IDoc status to ensure it was successfully created and sent.

Troubleshooting Common Issues

If no IDoc is generated, revisit the condition records to ensure the correct medium and timing are set. Also, double-check the partner profile, output type settings, and process code assignments. Ensure the IDoc status is not in error; if it is, analyze the error message for guidance.

Advanced Tips for Production Use

Consider using custom output types instead of NEU to avoid conflicts with other configurations. Additionally, implement change pointers if you need IDocs to be generated only on changes to specific fields. Always test thoroughly in a QA environment before moving configurations to production.

Conclusion

Setting up SAP to trigger an IDoc automatically upon the creation of a Purchase Order can significantly streamline business processes. By configuring output types, condition records, partner profiles, and ALE settings correctly, you can achieve seamless data integration across systems.

Bonus Tips and FAQs

Can I use this method for other document types?
Yes, similar configurations can be used for Sales Orders, Delivery Notes, and Invoices.

What’s the difference between ORDERS and ORDERS05?
ORDERS is the message type, while ORDERS05 is the version of the IDoc structure used to represent the data.

How do I set this up in a multi-client system?
You need to ensure that partner profiles, ports, and logical systems are set up for each client separately.

Is it safe to use this in production without testing?
No. Always test in a quality system first and validate end-to-end scenarios.

What are best practices for message control in SAP?
Use custom output types, avoid hardcoding, document all configurations, and maintain change logs for audit purposes.

Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP MM Books
SAP Material Management Certification, Interview and Configuration Reference Books

SAP Material Management Tips
SAP MM Configuration Tips and Materials Management Discussion Forum

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.