STEP 1 : Use transaction SM59 on the Integration Server to establish communication with the SAP backend system.
1. Using transaction SM59, create an RFC destination of connection type 3.2.
Enter the logon information:The logon language must be the same as the language of the payload content, for example, for Japanese payload the language must be JA. Otherwise, the content will be corrupted in the target system.
3. Test the connection by choosing Test connection and Remote logon. Both tests must be successful.
If the user in the target system is a background user or does not have sufficient authorization no logon screen will be displayed.
STEP 2 : On the Integration Server, configure the port for IDoc communication.
Call transaction IDX1 to create a port.
The Port name must have the format SAPxxx, where xxx is the system ID of the SAP backend system.The
Client must be the client number of the SAP backend system. Select the RFC Destination that was created in the previous step.IDoc metadata is client-independent. Therefore, only the smallest client is used.
The fields
Partner No. and Partn. Type are not used; leave them empty.
STEP 3 : Create or verify the logical system name on the SAP backend system.
1. Either call transaction SALE on the SAP backend system and choose Define Logical System or call transaction BD54 directly without going through the Implementation Guide (IMG).
2. Create or verify the logical system name.
STEP 4 : Create or verify the business system in the SLD.
The business system name for the SAP backend system must contain a valid
Logical System Name. This Logical System Name is the one that was verified or created in the previous step.In the SLD, select the SAP backend business system, or create one if none exist. Verify the
Logical System Name.1. In the Integration Directory, choose the business system
In the menu, choose Service • Adapter-Specific Identifiers.
If the information is empty or incorrect,you have to synchronize it with the content of the SLD. Follow the steps
below for synchronization.
2. (Optional): Synchronization of the business system in the Integration Directory with the business system in the SLD.
Choose the business system in the Integration Directory. Switch to Edit mode.
In the menu, choose Service • Adapter-Specific Identifiers.
3. (Optional): In the dialog box, choose Compare with System Landscape Directory to re-synchronize.
4. (Optional): If the data expected from the SLD is not updated, the SLD cache may need to be cleared first.
STEP 5 : Verify or add the logical system name for the sender business system.
If the sender system is a third-party business system, repeat above 2 steps.
for the sender system. The sender business system must have a logical system name. Otherwise, the IDoc cannot be delivered.
If the sender business system already exists, but does not have a logical system name, the name can be added using the SLD.
1.
In the SLD, navigate to the business system and choose Change.2.
Enter the Logical System Name and choose Save.3. Re-synchronize the Integration Directory by following the synchronization instructions in above section .
STEP 6 : Create/configure the communication channel for the receiver IDoc adapter.
In the Integration Directory, create an IDoc receiver communication channel.
The
RFC Destination is the one from Step 1.The
Port is the one from section Step 2.The
Segment Version is either empty or smaller than the SAP Release.If you want to use IDoc parties as senders or receivers with a party type other than LS, select the check box
Apply Control Record Values from Payload.
NOTE:
There is no need to create a communication channel for the IDoc sender. Instead, the SAP backend system must be configured to send the IDoc to the Integration Server.
Configuration Management 
Infrastructure Management 
