You will get this error when creating a new partner in the transaction we20 if you

have not maintained the partner as a Logical System in bd54 (sale).

iDoc configuration error “Maintain a Valid Partner Number”

Check the prerequisite #2 of the guide. The logical system should be maintained in
bd54 before it can be used as an EDI partner in we20.
E0266 – Could not find code page for receiving system

This is an iDoc error that could occur when passing the iDoc to Receiver Port. If
the Program ID of the RFC destination is not registered correctly, this issue can
occur.

The outbound iDoc will terminate with the error in status 02 (Error passing data to
port). You can request your BASIS team to troubleshoot this error.
How to Debug Outbound iDocs

We can debug the iDoc generation Process Code of an Outbound iDoc configured via
Output Control in four easy steps:

Set the Output Type Dispatch Time to Option 1 (Send with a periodically
scheduled job)
Set a break-point in iDoc processing FM (process code)
Issue the output from SAP application document
Execute program RSNAST00

Step 1 – Change the Dispatch Time of the Output Type to Option 1

It is important to understand we cannot easily debug the iDoc generation FM

(process code) using Dispatch Time option 4 (Send Immediately when saving the
application).

Go to transaction NACE > Application Area > Output Type and change the Dispatch
time to “Send with Periodic Batch Job”.
Change the dispatch time of the output to "Send with Periodically Scheduled Job"Set
the Dispatch Time of the output to “Send with Schedule Job”

Click “Save”.
Step 2 – Assign a Break-point in iDoc Processing FM (Process Code)

First, find the Process Code under Message Control of Partner Profile.
Identify the Process Code of the Outbound iDoc via partner profile configuration in
transaction we20Identify the Process Code of the Outbound iDoc

Then, go to transaction we57 and find the iDoc processing FM. Or you can directly
go to transaction se16n or se11 to find the FM using table EDIFCT.
identify the FM that generates output docs via transaction we42. FM is assigned to
a iDoc Message Type and Basic type
Identify the iDoc processing FM of the Process Code
Alternative method to find the iDoc processing FM - Table EDIFCT via transaction
se16n
Alternative method to find the iDoc processing FM – Table EDIFCT

Finally, go to transaction se37 and set a break-point in iDoc creation Function

Module “IDOC_OUPUT_ORDRSP”.
ABAP source code of the iDoc processing FM.ABAP Source Code of iDoc Processing FM.
– IDOC_OUPUT_ORDRSP
Step 3 – Create a New Output in Sales Order Document

Either create a new sales order document or a new output from an existing sales
order. The output should be in yellow status (ready to be dispatched).
issue a new output from sales order header manually. output is yellow (ready to be
processed) statusIssue a new output from sales order header

When you save the sales order, output entry should be stored in NAST table. The
output will be in a status 01 (Not yet processed).
Output stored in NAST table as entry. Processing status is 0 (ready to be
processed)Output entry created in NAST table
Step 4 – Execute Program RSNAST00

Execute the program RSNAST00 that issues outputs. The breakpoint in iDoc creation
FM will be triggered.
debug mode of the ABAP FM that creates output iDocs
iDoc generation FM in Debug Mode

Now you can debug the FM that generates the iDoc from application data.

To summarize, you can use Output Determination to generate Outbound iDocs in SAP.
Outbound iDocs generated by the output go through a processing pipeline that has
multiple milestones (statuses). iDoc processing can be set up for “immediate
processing” or “background processing”. This is controlled in the partner profile.

You can debug iDoc processing ABAP source code by setting a break-point in iDoc
processing FM. Moreover, you can troubleshoot iDoc processing errors using iDoc
status messages.

If you have any questions, leave a comment below!

This entry was posted in ALE/iDoc and tagged Access Sequence, ALE, bd54, Condition
Records, Debug, EDI, FSHORD03, iDoc, iDoc Port, iDoc Status, Logical System, NACE,
ORDRSP, Outbound iDoc Configuration, Output Determination, Output Determination
Configuration, Output Procedure, Output Type, Partner Profile, RFC Destination,
sale, Sales Order Output, sm59, we20, we30, we31, we57, we80, we81.
Isuru Fernando

Hi, I am Isuru Fernando, Senior SAP Integration Consultant with 10 years of SAP
full-cycle implementation and support project experience. From the early days, I
had a passion for coding, software development, and everything tech-related. I
started my carrier as an ABAP developer and soon found my love for system
integration when I learned SAP XI 3.0 in 2008. Playing a variety of roles from an
offshore technical consultant (ABAP, PI/PO, BW, BOBJ) at the beginning of my career
to a technical lead managing a team of consultants in different countries, I have
gained immense experience in SAP project implementation life cycle. Having the
opportunity to work on SAP implementation projects in USA, EU, and Asia, I learned
valuable ins and outs of global business processors in Sales and Distribution (SD),
Material Management, Retail, Customer Relationship Management (CRM), and Finance
and Controlling (FICO). Through this blog, I want to share my expertise in SAP
technical areas such as SAP ABAP, PI/PO, AIF, and Basis. I also want to provide a
platform for others with similar ambitions who would like to share their SAP
technical expertise with the world!
Change Pointer Tables in SAP (ALE) and BDCP2
Microsoft Power Apps Integration with SAP S4 HANA

Encode Message Payload to Base64 on CPI!

How to use Base64 message encoder in SAP Integration Suite.

Subscribe for more
My First Interface on CPI!

Learn how to develop your first iFlow on SAP Integration Suite within 7 minutes!
Subscribe for more

SIGN UP TODAY!
Sign up to receive our monthly newsletter and special deals!

I accept Newsletters & Blog updates.

32 thoughts on “Outbound IDoc Configuration with Output Determination in SAP –

Techno-functional Guide”

Gaurav Agrawal says:

Excellent stuff Isuru! Hats off to your work…keep going..Cheers!!!

October 31, 2019 at 9:13 pm
Reply
Isuru Fernando says:

Thank you, Gaurav!

November 2, 2019 at 5:39 pm
Reply
Chandra says:

Very Detailed..Great work!!..I configured similarly Output type determination

for PO..But Idocs are failing with ME 760 Error Code on PO change with respect to a
custom field scenario.We are triggering Idocs to two different systems parallely.
For the first time, Idoc is failing to a system and then after next change to PO it
is working fine.

Please share your valuable comments on the same.

November 18, 2019 at 2:12 pm
Reply
Isuru Fernando says:

Hi Chandra, Is the iDoc failing after getting created or output does not
get triggered when you change the custom field?
November 22, 2019 at 12:51 pm
Reply
Peter Danilovic says:

Thank you, well done!

November 25, 2019 at 9:53 am
Reply
Isuru Fernando says:

Thank you Peter!

November 27, 2019 at 1:40 pm
Reply
Rais Ahmed says:

Hi Isuru Fernando,
Firstly thank you for the detailed explanation. I am working in IS-Retail
environment, could you please help me understand what is the difference between
Partner Type KU and Partner Type LS.
December 23, 2019 at 1:33 pm
Reply
Isuru Fernando says:

Hi Rais,
 Partner type KU is for customers and partner type LS represents logical
systems. You can trigger outputs also to partner type KU, the prerequisite is the
customer should be available as a master record in SAP.

Cheers!
Isuru
December 23, 2019 at 5:03 pm
Reply
mahabooba shaik says:

Hi Isuru,

Great, Thanks much for sharing more valuable. keep sharing. Thanks! Mahabooba
February 26, 2020 at 11:03 am
Reply
Isuru Fernando says:

Thank you, Mahabooba!

February 26, 2020 at 12:10 pm
Reply
Jayasri says:

HI Isuru,
Thank you so much for sharing this, I have configured Invoice outbound Idoc ,
IDoc has been triggered without any issue, however missing few fields In Segment
E1EDP01 like PEINH, LGORT, MATNR.
Kindly help.
Thank you,
Jayasri
June 9, 2020 at 10:44 am
Reply
Sirisha Reddy says:

Hi Isru, Excellent explanation. Thanks.

November 24, 2020 at 9:46 pm
Reply
Isuru Fernando says:

Thank you very much, Sirisha!

November 25, 2020 at 8:34 am
Reply
Ramamurthy says:

Hi ISURU FERNANDO, this is an excellent explanation, While I am doing the same

thing with a Purchase order (BASIC TYPE: ORDERS04, Message type: ORDERS), the
output is triggering at Purchase order but in we20 Status is 02. How to solve it,
please explain to me.
Mail id: [email protected]
April 20, 2021 at 4:53 am
Reply
Nila says:

Hai. Such a nice work. Great explanation. Can u please help me with asn
outbound idoc process
July 6, 2021 at 7:19 pm
Reply
vana says:

thank you very much , very clear explanation, and very informative.
August 27, 2021 at 4:08 pm
Reply
Iliyas says:

Great Work Isuru! Clear and detailed explanation. Thank you very much!!
December 2, 2021 at 2:34 pm
Reply
Isuru Fernando says:

Appreciate the support! Thank you 🙂

February 10, 2022 at 8:05 am
Reply
Fernando says:

Thanks a lot, very helpful.

December 7, 2021 at 6:23 pm
Reply
Isuru Fernando says:

Thank you, Fernando!

February 10, 2022 at 8:04 am
Reply
Sridhar says:

Excellent
December 12, 2021 at 10:00 pm
Reply
Isuru Fernando says:

Thank you, Sridar!

February 10, 2022 at 8:04 am
Reply
Jay says: