Technical Guide: IDoc Outbound Configuration via ONECONNECT

1. Output Message Configuration (Transaction: NACE)

The following steps define how to configure the system to trigger an output message for specific business documents (e.g., Sales Orders).

1.1 Create a New Output Type

• Access transaction NACE.
• Select Application V1 (Sales) and click on Output Types.
• Create a new entry for the IDoc output.
• Reference:

 

 

1.2 Define Partner Functions

• Assign the default partner functions to the new output type. This ensures the system identifies the correct partner role (e.g., SP - Sold-to Party) to receive the message.
• Reference:
  

 

1.3 Maintain Processing Routines

• Assign the transmission medium (typically 6 - EDI) and the required processing program.
• Reference:
  

1.4 Assign Output Type to Procedures

• Add the newly created Output Type to the relevant Determination Procedure (e.g., V10000).
• Reference:
  

 

1.5 Create Condition Records

• Maintain condition records to automate output generation based on criteria such as Document Type .
• Note:
  After completing these steps, the system will automatically propose the new output message whenever a sales order is created or modified.
• Reference:
  

 

 

---

2. EDI-ALE Environment Setup

Technical configuration of the communication layer between SAP and the ONECONNECT platform.

2.1 Define Logical System (Transaction: SALE)

• Access transaction SALE and define the new Logical System (LS) that represents the destination platform.
• Reference:
  

 

2.2 Configure EDI Port (Transaction: WE21)

• Create a new Transactional RFC Port and associate it with the corresponding RFC destination (SM59). It must be a specific port to receive the IDoc.

 

• Reference:
  

 

2.3 Maintain Partner Profiles (Transaction: WE20)

• Create a Partner Profile for the Logical System (LS) defined in step 2.1.
• Reference
  

 

2.4 Configure Outbound Idoc

• Add the specific Message Type (e.g., ORDERS) and Basic Type (e.g., ORDERS05) to the partner profile.
• Reference:
  

 

• Note:
  The Logical System is now fully configured to process and transmit IDocs.

 

---

3. Distribution Model (Transaction: BD64)

Final link between the message type, the sender system, and the receiver system.

3.1 Create ALE Distribution Model

• Define a new model view and provide a technical name.
• Reference:
  

3.2 Add Message Type to Model

• Select the newly created model and click Add Message Type. Specify the Sender (Internal LS) and the Receiver (OneConnect LS).
• Reference:
  

3.3 Confirmation and Execution

• Once these steps are finalized, the IDoc for the Sales Order confirmation will be generated and executed automatically upon saving the document.
• Reference:

 

• Related Articles

• IDOC Configuration Manual

  1. Output Message Creation for IDOCS STEP 1 Access SAP STEP 2 Go to the Transaction field and enter “NACE” in the input box. Press Enter or click the checkmark. STEP 3 Select the application that you want to configure. For this manual, we will choose ...

• OneConnect V2 SAP Manual

  OneConnect V2 SAP Integration The following manual configuration considers the fact that you have installed the version 2 of OneConnect in SAP, please make sure that you are using this version Install the Transport Install the transport request sent ...

• Sending IDocs Using One Connect for SAP

  Sending IDocs Using One Connect for SAP Output Message, EDI/ALE, and Distribution Model Configuration Overview One Connect for SAP supports data extraction through SAP IDocs (Intermediate Documents), allowing you to leverage standard and custom IDoc ...

• Sending Data via BW Extractors

  Sending Data via BW Extractors Using One Connect for SAP Overview One Connect for SAP supports data extraction through SAP BW (Business Warehouse) Extractors, allowing you to leverage existing BW DataSources to extract and transmit data to your ...

• SAP Data Modeler - Identifying CDS Views Compatible with OneConnect Modeler

  The purpose of this manual is to provide a simple and practical guide to identifying CDS views within SAP that are compatible with the OneConnect Data Modeler. It outlines the necessary steps in a clear and concise manner, allowing users to quickly ...