Sending IDocs Using One Connect for SAP

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 message types to transmit business documents to your target platform via the One Connect Smart Gateway.

This guide covers the three configuration phases required to send IDocs through One Connect, using a Sales Order (ORDERS) scenario as an example. The same pattern applies to any IDoc-enabled business process.

 

Phase

Description

SAP Transactions

1

Output Message Configuration

NACE

2

EDI/ALE Environment Setup

SALE, WE21, WE20

3

ALE Distribution Model

BD64

Prerequisites

Before you begin, ensure the following are in place:

•       One Connect for SAP is installed and configured in your SAP system

•       The One Connect Smart Gateway is deployed and accessible

•       An RFC destination for the Smart Gateway has been created and tested in transaction SM59

•       You have authorization to configure output types, EDI ports, partner profiles, and distribution models

•       You know the IDoc Message Type and Basic Type for your business scenario (e.g., ORDERS / ORDERS05 for Sales Orders)

 

Phase 1: Output Message Configuration

Define how the system triggers an IDoc output message for specific business documents (Transaction: NACE)

1.1 Create a New Output Type

Access transaction NACE, select Application V1 (Sales), and click Output Types. Create a new entry for the IDoc output.

Configure the output type with the following general data:

 

Field

Value

Output Type

ZONS

Description

Oneconnect Sales ord

Access sequence

0002 (Order Type)

Access to conditions

Checked

Multiple issuing

Checked

 

Figure 1: Output Type ZONS configuration in NACE — General data tab with Access sequence and options.

Figure 2: The new Output Type ZONS entry in the Output Types list view.

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 output message.

Figure 3: Partner Functions assigned to Output Type ZONS.

1.3 Maintain Processing Routines

Navigate to Processing routines in the dialog structure. Configure the transmission medium and processing program:

 

Field

Value

Transmission Medium

A — Distribution (ALE)

Program

RSNASTED

Form Routine

ALE_PROCESSING

 

Figure 4: Processing Routines for Output Type ZONS with program RSNASTED and Form Routine ALE_PROCESSING.

1.4 Assign Output Type to Procedure

Add the newly created Output Type to the relevant Determination Procedure (e.g., V10000). This links the output type to the sales document processing flow.

Figure 5: Output Type ZONS added to Determination Procedure V10000.

Figure 6: Detailed view of the procedure assignment showing the output type entry.

1.5 Create Condition Records

Maintain Condition Records to automate output generation based on criteria such as Document Type. This ensures the system automatically proposes the IDoc output message whenever a sales order is created or modified.

Figure 7: Condition Records configuration for automatic output proposal.

Figure 8: Condition Record entries showing the triggering criteria.

 

Note

After completing Phase 1, the system will automatically propose the ZONS output message on sales orders that match the condition criteria. The output will not be transmitted until the EDI/ALE environment is configured in Phase 2.

 


 

Phase 2: EDI/ALE Environment Setup

Configure the communication layer between SAP and the One Connect platform

 

2.1 Define Logical System (Transaction: SALE)

Access transaction SALE and navigate to Define Logical System. Create a new Logical System (LS) that represents the One Connect destination platform.

 

Info

The Logical System name should clearly identify the One Connect endpoint (e.g., USCU_S01). This name will be referenced in the Partner Profile and Distribution Model.

 

Figure 9: Transaction SALE — navigating to Define Logical System.

Figure 10: New Logical System entry created for the One Connect destination.

2.2 Configure EDI Port (Transaction: WE21)

In transaction WE21, create a new port under XML HTTP. Associate it with the RFC destination configured in SM59 for the One Connect Smart Gateway.

Configure the port with the following settings:

 

Field

Value

Port

ONECONNECT

Description

ONIBEX ONECONNECT

RFC destination

ONIBEX_NEW

Content Type

application/x-sap.idoc

HTTP Version

Version 1.0

 

Figure 11: XML HTTP port ONECONNECT in WE21 linked to RFC destination ONIBEX_NEW.

2.3 Maintain Partner Profiles (Transaction: WE20)

In transaction WE20, create a Partner Profile of type LS (Logical System) for the Logical System defined in Step 2.1.

Figure 12: Partner Profile created for the One Connect Logical System in WE20.

2.4 Configure Outbound IDoc Parameters

In the Partner Profile, add an Outbound Parameters entry. Specify the Message Type and Basic Type for the IDoc to be transmitted:

 

Field

Value

Message Type

ORDERS

Basic Type

ORDERS05

Receiver Port

ONECONNECT

 

Figure 13: Outbound Parameters configuration with Message Type ORDERS and Basic Type ORDERS05.

Figure 14: Detailed Outbound Parameters view showing the receiver port assignment.

 

Note

The Logical System is now fully configured to process and transmit IDocs. Any IDoc generated for this Message Type will be routed through the ONECONNECT port to the Smart Gateway.

 

Figure 15: Complete Partner Profile showing the configured Outbound Parameters.

 


 

Phase 3: ALE Distribution Model

Create the final link between the message type, the sender system, and the receiver system (Transaction: BD64)

 

3.1 Create ALE Distribution Model

In transaction BD64, switch to Change mode and click Create model view. Define a new model view with a descriptive technical name.

Figure 16: Creating a new Distribution Model view in BD64.

Figure 17: The new Distribution Model view with its technical name.

3.2 Add Message Type to Model

Select the newly created model and click Add Message Type. Configure the sender and receiver systems:

 

Field

Value

Sender

Internal Logical System (your SAP system)

Receiver

One Connect Logical System (defined in Step 2.1)

Message Type

ORDERS

 

Figure 18: Adding the ORDERS Message Type with Sender and Receiver systems.

Figure 19: Completed Distribution Model showing the message flow from Sender to Receiver.

3.3 Verification

Once all three phases are complete, the IDoc output will be generated and transmitted automatically when a matching sales order is saved. You can verify the output in the sales order output screen:

Figure 20: Sales Order output screen showing the ZONS output type with Distribution (ALE) medium — status indicates successful processing.

 

Tip

Use transaction WE02 or WE05 to monitor IDoc status. Verify that the transmitted IDocs arrive successfully in your target platform (e.g., Confluent, Databricks, or Snowflake) by checking the relevant topic or table.

 

Troubleshooting

 

Symptom

Possible Cause

Resolution

Output message not proposed on sales order

Condition records missing or Determination Procedure not assigned

Review Steps 1.4 and 1.5; verify the output type is in the correct procedure

IDoc status 30 (ready to be dispatched)

Outbound processing not triggered

Run transaction WE14 to reprocess, or check the output timing settings

IDoc status 02 or 04 (error)

EDI port, Partner Profile, or RFC destination misconfigured

Check WE21, WE20, and SM59 settings; verify the Smart Gateway is reachable

IDoc status 03 (sent) but data not in target

Latency or topic/table mismatch in target platform

Allow time for processing; verify the correct topic or table name in your platform

Distribution Model not distributing

Model not activated or wrong sender/receiver

In BD64, select the model and click Distribute; verify Logical System names match

 



    • Related Articles

    • SAP Data Modeler - Set Up High Availability for One Connect for SAP

      How to Set Up High Availability for One Connect for SAP Overview One Connect's Data Modeler transmits data and metadata to the Smart Gateway via an HTTP endpoint configured in SAP transaction SM59 as an RFC destination (Connection Type G). To ensure ...

    • 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 ...

    • RFC Data Sending Guide – ZONCL_FETCH_DATA_V2

      RFC Data Sending Guide – ZONCL_FETCH_DATA_V2 This guide describes how to send data from a custom Z table in SAP to a remote system using the class ZONCL_FETCH_DATA_V2. The process supports optional filters and allows update/delete operations on the ...

    • Onibex SAP Data Modeler - Functionalities

      Introduction The following table outlines key functionalities offered by the SAP Data Modeler, highlighting features designed to enhance data extraction, customization, and integration within SAP environments. No Function Description 1 Direct Data ...

    • Sending Z Tables via SAP Data Modeler and Custom Z Program - For ABAP RAP

      Manual: Sending Z Tables via SAP Data Modeler and Custom Z Program In the SAP Data Modeler, create an “ANY” Entity including the desired Z tables. Ensure the Domain is set to ANY. Inside the entity, select the desired columns to send in the Column ...