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 V1 Sales.

Once you select the application, go ahead and click on Output Types.

STEP 4

Click “Edit” and select “New Entries”

STEP 5

In the Output Type section, enter the following information:

Transactional Data
Process	Output type	Access Sequence	IDOC TYPE
Transport (V7)	ZTEC	001	SHPADV
Deliveries (V2)	ZDEC	001	DESADV
Invoices (V3)	ZFEC	001	INVOIC
Sales Order (V1)	ZPEC	002	ORDRSP
Purchase Order (EF)	ZOEC	001	ORDERS

 

 

 

 

Output type: Select the appropriate output type based on the process you are setting up.

Description box: Orders Onibex (Or add your own description) 

Access Sequence: Select the appropriate access sequence according to the process.

Select: Access to condition and Multiple Issuing

Once you have completed the information, choose "Default Values."

STEP 6

In the Default values section, enter the following information:

1. Dispatch time: 4 Send Immediately (When saving the application)
   

1. Transmission Medium: A Distribution (ALE) 
   

1. Partner Function: SP 
   

After this, Select Partner Functions 

STEP 7

Select New Entries

Medium: A Distribution (ALE) 

Function: SP

STEP 8

Select Processing routines

STEP 9

Select New Entries. 

Utilize the following data for the configuration of all required IDOC:

1. Transm. Medium : A Distribution (ALE) 
   

1. Program: RSNASTED
   

1. Form Routine: ALE_PROCESSING
   

2. IDOC Set up procedures.

STEP 1

Go to the Transaction field and enter “NACE” in the input box. Press Enter or click the checkmark.

STEP 2

Select the application that you want to configure. For this manual, we will choose V1 Sales.

Once you select the application, go ahead and click on Procedures

STEP 3

Select Order Output

Click in Control in the Dialog structure panel.

STEP 4

Select “New Entries”

STEP 5

Insert the following data

1. Step: Use the next available number.
   

1. Count: 0
   

1. Connection : ZPEC

Click Save

3. IDOC Set up Condition Records

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 V1 Sales.

Once you select the application, go ahead and click on Condition Records 

STEP 4

Scroll down and select the Output type to set up. 

STEP 5

Select Output Condition and click in Create.

STEP 6

Specify which document types will be created automatically with this output.

Click Save 

4. Configure Logical system  

STEP 1

Go to the Transaction field and enter “SALE” in the input box. Press Enter or click the checkmark.

STEP 2

Select Define Logical System 

STEP 3

Click in New Entries

STEP 4

Type Name  : Select the name of the Log System. We will use Onibex.

Name of Logical System : Select the name of the name of logical system.  We will use Onibex.

Click save

5.  Port Configuration Connection.

STEP 1

Go to the Transaction field and enter “WE21” in the input box.

Press Enter or click the checkmark.

STEP 2

Select create 

STEP 3

Please provide the information that needs completion, as shown below: 

1. Port: ONIBEX_ID
   

1. Description: Onibex IDOC
   

1. RFC destination : Select your pre-configured RFC Destination
   

Make sure to select in content type application / x - sap.idoc

Save

6. Logical system configuration IDOC 

STEP 1

Go to the Transaction field and enter “BD64” in the input box. Press Enter or click the checkmark.

STEP 2

Click in Edit 

STEP 3

Click in “Create model view”

Short text: ONIBEX

Technical name: ONIBEX

Click save 

STEP 4

Select Project and click More “Add Message Type”

STEP 5

Add the following data: 

1. Model View: Onibex
   

1. Sender: Default server system 
   

1. Receiver: Onibex
   

1. Message Type:  Select the output type accordingly to the IDOC TYPE that you are setting up. 
   

Transactional Data
Process	Output type	Access Sequence	IDOC TYPE
Transport (V7)	ZTEC	001	SHPADV
Deliveries (V2)	ZDEC	001	DESADV
Invoices (V3)	ZFEC	001	INVOIC
Sales Order (V1)	ZPEC	002	ORDRSP
Purchase Order (EF)	ZOEC	001	ORDERS

 

 

 

 

 

 

7. DOC Configuration

STEP 1

Go to the Transaction field and enter “WE20” in the input box. Press Enter or click the checkmark.

STEP 2

Select Partner Type LS

Select Create

STEP 3

Please fill the information as shown below: 

1. Partner No: Onibex 
   

1. Partner type : LS
   

1. TY: US
   

1. Agent: Username
   

1. Lang: Select the language that you want to set up.

Create new Outbound

Scroll down and select the “ Plus ” icon as shown below:

STEP 4

Please fill the information as shown below: 

Partner No: Onibex 

Partn.Type: LS

Message Type:  Select the Message type according to the process that you are setting up.

IDOC TYPE

Basic type: Select the Base type according to the process that you are setting up.

Once you complete the data, select : “Message Control”

 Use the table as reference.

IDOC Type	Base Type	Application	Output Type	Process Type
ORDRSP	ORDERS05	V1	ZPEC	SD10
DESADV	DELVRY07	V2	ZDEC	DELV
INVOIC	INVOIC02	V3	ZFEC	SD09
SHPADV	SHPMNT05	V7	ZTEC	SHPM

STEP 5

Create new Message Control 

Complete the data as shown below: 

Application: V1 

Message type: Select the Message type according to the process that you are setting up.

Process Code: Select the Process type according to the process that you are setting up.

Save 

Use the table as reference.

IDOC Type	Base Type	Application	Output Type	Process Type
ORDRSP	ORDERS05	V1	ZPEC	SD10
DESADV	DELVRY07	V2	ZDEC	DELV
INVOIC	INVOIC02	V3	ZFEC	SD09
SHPADV	SHPMNT05	V7	ZTEC	SHPM

NOTE: For transactional processes, configuration is required in both the outbound option tab and the message control tab. Materials and clients only need configuration in the outbound tab.

8. IDOC Reference Tables Summary.

 1. Master Data Outbound Idocs

Master Data
Process	IDOC TYPE
Clients	DEBMAS
	ADRMAS
	ADR3MAS
Materials	MATMAS
Purchase Order	ORDERS
Inventory	ZON_INV

 

 

 

 

 

 

 

2. Transactional Outbound Idocs

Transactional
Process	Output type	Access Sequence	IDOC TYPE
Transport (V7)	ZTEC	001	SHPADV
Deliveries (V2)	ZDEC	001	DESADV
Invoices (V3)	ZFEC	001	INVOIC
Sales Order (V1)	ZPEC	002	ORDRSP
Purchase Order (EF)	ZOEC	001	ORDERS

 

 

 

 

 

 

 

3. Outbound Idocs reference table.

IDOC Type	Base Type	Application	Output Type	Process Type
ORDRSP	ORDERS05	V1	ZPEC	SD10
DESADV	DELVRY07	V2	ZDEC	DELV
INVOIC	INVOIC02	V3	ZFEC	SD09
SHPADV	SHPMNT05	V7	ZTEC	SHPM
ADRMAS	ADRMAS03	-	-	-
ADR3MAS	ADR3MAS03	-	-	-
DEBMAS	DEBMAS05	-	-	-
MATMAS	MATMAS05	-	-	-

• Related Articles

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

• 04 - OneConnect Deployment and Configuration

  Deployment Deployment Access to Workloads Enter the main portal of the Kubernetes cluster and go to the Workloads section. In the Workloads section, click the Create button and select the Apply YAML option. Application of YAML On the empty YAML ...

• 02 - YAML configurations

  YAML Configuration Manual Requirements Unzip the fileoneconnect-kibernetes.identified at the bottom of this documentation. When you extract the file, two folders will be displayed:"Kubernetes"and"Kubernetes configuration Open the directory where the ...

• 1. One Connect - Installation

  Step by Step SAP Integration Manual. The following information provide a condensed overview of the comprehensive SAP Integration Manual. In this manual, you'll find detailed step-by-step instructions for seamless SAP integration. Here's a glimpse of ...

• 03 - Deployment of One Connect Platform

  Prerequisite Note Before you start deploying the One Connect platform, make sure you meet the following requirements: Compatible Operating Systems: Kubernetes cluster nodes must use Linux operating systems. Affinity for Other Operating Systems: If ...