What Is the NEU Output Type and Why It Matters
Let’s start with the basics. In SAP, the NEU output type is the standard way to generate and send a purchase order (PO) document. It's used in the message control process to trigger outputs such as print, email, or — in our case — an EDI IDoc. When properly configured, NEU ensures that every time a PO is created or changed, an IDoc (specifically, ORDERS) gets generated and transmitted to your vendor or third-party system. Sounds simple, right? But that simplicity depends entirely on the setup being airtight.How the NEU Output Works with IDoc and EDI
Here’s the thing: The NEU output type relies on SAP's message control framework. This framework checks whether an output condition is met (like a specific vendor or document type), then triggers a predefined output method, such as sending an EDI document. The entire process hinges on a complex but elegant dance between output types, partner profiles, access sequences, and more. Once set up, every PO can trigger an IDoc of type ORDERS05 (or a custom version like /NFM/ORDERS05), which travels through your ALE system or middleware to reach the vendor’s system.Step 1: Create a Port in WE21 (Transactional Port)
First up, head to transaction WE21. You’ll want to create a Transactional RFC Port — this is the communication pathway that SAP uses to transmit the IDoc. - Choose "Transactional RFC" from the left panel.- Create a new entry, give it a logical name.
- Assign the RFC destination (which should point to your EDI subsystem or middleware like PI, PO, Seeburger, etc.).
- Save and exit.
Step 2: Maintain the Partner Profile in WE20
Next, navigate to transaction WE20 and set up the vendor as an EDI partner: - Choose "Partner Type: LI" (for vendors).- Create a new partner number (same as vendor number).
- Under Outbound Parameters, add:
- Message Type: ORDERS
- Basic Type: /NFM/ORDERS05 (or ORDERS05 for standard)
- Process Code: ORDE
- Port: The one you created in WE21
- Set the Output Mode, Change Message Indicator, and IDoc type settings. Also, go to the Message Control tab:
- Application: EF (Purchasing)
- Message Type: NEU
- Process Code: ORDE Save everything.
Step 3: Create Condition Record for NEU in NACE
Head over to transaction NACE and select the "EF" application for purchasing documents. - Choose Output Types and select NEU.- Double-click Processing Routines and ensure:
- Program: SAPFM06P
- Form Routine: ENTRY_NEU
- Smartform/Script: MEDRUCK or a custom form.
- Medium: 6 (for EDI)
- Date/Time: 3 (Send with application own transaction)
- Partner Function: VN
- Partner: Vendor number
Now, go to Condition Records and create a new record:
Step 4: Validate in MN06
Now test the setup by going to MN06. This shows existing output records for a given PO.- If the NEU record is present and set to medium 6, you’re good.
- If it’s missing, either the condition record isn’t properly created, or the PO doesn't meet the condition (wrong vendor, PO type, etc.). Use MN05 to display conditions and MN04 to create new ones.
Step 5: Define Condition Table via SPRO
To create or review condition tables:- Navigate to SPRO → MM → Purchasing → Output Control → Condition Tables
- Use existing ones like 14 (Doc type, Purch Org, Vendor) or create a new one.
- Be sure it includes all the fields you need for PO message determination. Think of condition tables as the “IF” clause of your output logic.
Step 6: Configure Access Sequences
Now set up access sequences:- SPRO → MM → Purchasing → Output Control → Access Sequences
- Define or reuse one (e.g., 0001)
- Assign your condition tables in sequence (like 14, 18, etc.)
- Think of this as SAP’s checklist: it’ll try each table until it finds a match.
Step 7: Define Message Type NEU
Still in SPRO, go to: - Output Types → Define Message Type- Choose NEU (or create a ZNEU for custom needs)
- Link the access sequence
- Assign the processing routines (same as NACE setup: SAPFM06P, ENTRY_NEU)
Step 8: Maintain Message Schema
Back in SPRO:- Go to Message Schema → Define Message Schema for PO
- Include NEU in the schema
- Assign schema to PO types in "Assign Schema to Purchasing Document"
Step 9: Define Partner Roles per Message Type
- Go to Partner Roles per Message Type in SPRO
- Ensure the Partner Function "VN" (Vendor) is defined for NEU
- This ties the output to the right role in the document
Step 10: Create Condition Record in MN04
For each vendor or vendor group: - Go to MN04- Create a record with medium 6, date/time 3
- Fill in key fields like doc type, vendor, org, etc.
This is a critical step many forget. No condition = no output.
Step 11: Create and Release a PO (ME21N)
Now put it to the test:- Create a PO using ME21N
- Use the vendor and PO type from your condition record
- Save and release it (if approval is required)
Also use WE02 to check if IDoc was created.
Step 12: Review Output Program and Form
In NACE:- Ensure correct linkage to SAPFM06P, FORM: ENTRY_NEU, and SMARTFORM: MEDRUCK or a custom form.
- If you’re sending PDF via EDI, you might need a different smartform setup.
Step 13: Define Communication Strategy
Navigate to:- SPRO → SAP Web Application Server → Basic Services → Message Control → Define Communication Strategy Ensure it supports medium 6 and links properly to the vendor’s communication method (e.g., EDI).
Troubleshooting Tips
- NEU doesn’t appear? Check message schema assignment and condition records.
- IDoc not created? Check partner profile, port config, and output medium.
- Status 02 in IDoc? Could be RFC failure or missing port.
- Message red light in PO? Probably due to missing output determination logic.
Advanced Tips & Best Practices
- Always test with multiple vendors.
- Use custom message types (ZNEU) if you want separate logic.
- For mass updates, use LSMW or MASS transactions.
- Enable change pointers for PO if you're sending changes (BD50/BD60).
Conclusion
Getting NEU output type configured for IDOC generation might seem like a lot, but once you understand how all the parts fit — partner profiles, ports, message control, conditions, and communication strategies — it becomes quite logical. With this guide, you now have a roadmap that goes beyond theory, into practical, tested steps that work in real SAP environments. Happy configuring!FAQs
Q1: How do I resend a failed PO IDoc?Use transaction ME9F or ME22N → Messages tab to reissue the output manually.
Q2: Can I use both print and EDI for the same PO?
Yes, by assigning multiple output records with different
mediums (e.g., 1 for print, 6 for EDI).
Q3: What's the difference between NEU and ZNEU?
NEU is standard. ZNEU is a custom message type, useful
if you want separate logic or forms.
Q4: Can condition records be automated?
Yes, via LSMW, BDC, or mass maintenance tools like MASS
transaction.
Q5: Which SAP roles should be authorized for this config?
Usually, MM Functional Consultants and EDI/IDoc Technical
teams with access to SPRO, WE20, WE21, and NACE.
