Skip to Content

Configuration steps required for posting idoc’s(XI)

During the course of our XI training, we had done handful exercises for posting Idoc’s. But when I started working on that exercises I faced problems due to the configuration that needs to be done in the sender, receiver and XI system. This blog lists the configuration steps required in the sender, receiver and XI system for posting Idoc’s from the third party system to SAP Systems.

Sender System

Logical System Name

1.If the sender system is maintained in the SLD as a business system then we need to enter the proper logical system name while creating the business system.

Logical System Name

2.If the sender system is maintained as the business service then we have to edit adapter specific identifiers and give the appropriate logical system name in the integration directory.

Logical System Name

Logical System Name

XI System

Creating RFC Destination

1.RFC destination to the source system has to be created through the SM59 transaction.

Create RFC Destination

2.The appropriate logon and application system details has to be provided depending on the receiving SAP system.

Creating a Port

1. Port has to be created through idx1 transaction for the RFC destination created above.

Create Port

2.The port has to be displayed in the idx2 transaction and we should be able to view the idoc’s which we imported through integration repository otherwise we have to manually import the idoc’s from idx2 using the port created above.

View Idoc MetaData

Adapter Configurations

1.RFC destination and port information created above should be configured in the idoc receiver communication channel.

Receiver Idoc Channel

Receiving System

1.Partner profile has to be created in the receiving system of type LS with the same name specified in the sender business system through WE20 transaction(I used the logical system HTTPSO which i mantained as a business service in the integration directory).

Create Partner Profile

2.Inbound idoc should be specified for the created partner profile.

Inbound Idoc

With this the configuration is complete and we can start developing interfaces. I hope this blog might be useful for kick starting to post Idoc’s. I googled for this kind of information but could not get all the information at a single shot, therefore the blog here.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    I have been scouting the XI forum for some time and could see ppl struggling to get a chklist for the config steps to be done for posting IDOCs. This blog will really help us
  2. This is a good and concise sequence of steps that has been compiled you. Really helpful to anyone and everyone dealing with IDOC’s and XI
  3. Former Member
    Is idx2 a mandatory step ? i beleive that the metadata for IDOC will be made available to XI when the first IDOC is posted, even thoe i dont manually import into XI using IDX2 !!


    1. Former Member Post author
      idx2 is not a mandatory step but some times metadata will not be imported due to some problems.idx2 will be useful when we need to trouble shoot problems.
  4. Hi Ravi !

    How do you manage the transport of the modified business service across different environments? we completed the Logical System of our business service and when we tranported it to QA system, we noticed that the business service kept the logical system entered in DEV system. The same when transporting from QA to PROD system, which is worse because we have a lot of IDOCs with the ALE error. Should be edit manually the logical system, every time we transport the business service? and if many developments groups made concurrent transports of the same business service ? how do you manage that? is using business system instead of service the answer? thanks !


Leave a Reply