IDOC Configuration Manual (SAP side)

1. Inbound IDOC1.1 Define logical system

T-CODE: BD54In this step we define logical system and it will be partner profile name in the next step. Logical system is one of the partner type in SAP. Press button to enter logical system code and name.

1.2 Define Inbound Function module

T-CODE: SE37In this step we define inbound function module to process the inbound idoc data.Detailed information for function module, please see the following function module documentation.

1.3 Assign Function Module to Message and IDOC typeT-CODE: WE57In this step we assign the inbound function module to the message type and idoc type. Relationship between idoc and function module is 1:N, it means inbound idoc can has different function modules for further processing.

Press button and enter below information.

1.4 Define the Characteristics of the inbound function moduleT-CODE: BD51In this step we define the input type of the inbound function module, press button to create new characteristics of the inbound function module

Input type 0 means mass processing, 1 means individual input, 2 means individual input with Idoc lock in CALL transaction. ‘Dialog allowed’ means IDoc can be processed in dialog mode, it is for frontend debugging purpose.

1.5 Define Inbound process codeT-CODE: WE42In this step we define the process code for the function module, process code will be used in the partner profile to specify the inbound function module for standard inbound process. Technically SAP allows create several process codes for one function module, but typically it has 1:1 relationship.Press button and enter the following information

1.6 Define Partner Profile for inbound IDOC

T-CODE: WE20In this step we define the partner profile for inbound idoc

Press button and Enter the following information

Agent is the one who creates/responsible for any errors/idoc failures. Common practice is create a specific SAP user ID for IDOC use.

Press button at the bottom of the inbound parameters.

Set the partner profile status as ‘Active’.

2. Outbound IDOC2.1 Define IDOC segment

T-CODE: WE31In this step we define IDOC segment for outbound data transfer, we defined 4 segments in this step. Data elements start with ‘A’ to ’X’ are reserved for SAP standard use and only ‘Z’ and ‘Y’ is reserved for customer use.

ZINFTY

ZPERNR

ZRETURN

ZDOCNUM

2.2 Define IDOC typeT-CODE: WE30In this step we define the IDOC type using IDOC segment which is defined in previous step.

Enter IDOC name and then press button to create new idoc type

Set the cursor on the IDOC type and then press button to create new segments

2.3 Define IDOC message typeT-CODE: WE81In this step we define the IDOC message type Press button to create new message type

2.4 Bind IDOC message type and basic type

Message type is the message which is transferred between the business partners. Basic type is the container of the actual message information. One message type may contain several different basic types T-CODE: WE82In this step we assign IDOC basic type to the message type Press button to create new combination

2.5 Define RFC destination T-CODE: SM59In this step we need to define the RFC connection with the SAP adapter in BPM side. This is only need for outbound idoc processing.

Press button to create new RFC destination

Enter the following information

PS: SAP gateway information can be displayed with t-code ‘SMGW’ and it is defined by the basis team at the point of the system setup

2.6 Define Port

T-CODE: WE21In this step we can define port which used for outbound idoc partner profile.

Set cursor on the transactional RFC and then press button

Enter the following information

2.7 Define logical system for outbound idocT-CODE: BD54In this step we define logical system for outbound idoc Press button to create new logical system

2.8 Define partner profile for Outbound IDOC

T-CODE:WE20In this step we define the partner profile for outbound

Press button and Enter the following information

Partner profile can be both of sender and receiver, if we maintain the outbound parameters then it will be outbound partner profile, if we maintain the inbound parameters then it will be inbound partner profile, but one logical system can not be a sender and receiver in one idoc at the sametime

Press button under the outbound parameter and then input the following information

‘Transfer IDoc immed.’ means it will send the IDoc as soon as it is created in the SAP system, ‘Collect IDocs’ means it will keep IDOC with ‘transaction recorded’ status and not send out automatically. Schedular setup is needed for the ‘Collect IDOCS’ option.

3. Test With WE19 Type ‘WE19’ in the command field Select Basic type radio button Enter HRSM_A03 and then press button

Set cursor on the EDIDC and then press to expand all sub tree

Click right side of the EDIDC and enter the following control record information

Click right side of the E1P0000 and enter the infotype 0000 information Click right side of the E1P0001 and enter the infotype 0001 information Click right side of the E1P0002 and enter the infotype 0002 information Click right side of the E1P0006 and enter the infotype 0006 information Click right side of the E1P0008 and enter the infotype 0008 information

After input all of the required information, click the button** Please see the RFC definition v1.4 for mandatory field information.

Press button Write down the IDOC number information

Type ‘WE05’ in the command field and then press Enter Press button Find the inbound idoc with the idoc number. Status 56 means there are some

error in the idoc data

Double click the idoc number Expand Status records sub tree to see the error message

After find out the reason, we can go back to the we19 and fix data and try again. If the light is green, it means that the inbound idoc is successfully added to SAP

system

After the inbound idoc we can also see the outbound reply idoc send out correctly.

PS: Outbound test is basically same with the inbound test, the only difference is control record and we need to click button instead of button

Control record for outbound test4. Trouble shooting

4.1 There are too many ‘transaction recorded’ status for outbound idoc in SM58 GO to T-CODE ‘SMQS’

Press Goto->QRFC Resources on the top menu

If the resources status is NOT OK, it means there are not enough dialog progresses for TRFC/QRFC, we need to increase the dialog process numberSolution:

Go to T-CODE RZ10 Select the instance profile and latest version Select ‘Basic maintenance’ radio button and then press Change button

Increase the dialog no of work processes (At least 6~7)

After modification, need to restart SAP server

For more information about the resource not ok, please refer to the SAP NOTES 527481:https://websmp130.sap-ag.de/sap(bD1rbyZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=0000527481&nlang=1