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.
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.
XI System
Creating RFC Destination
1.RFC destination to the source system has to be created through the SM59 transaction.
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.
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.
Adapter Configurations
1.RFC destination and port information created above should be configured in the idoc receiver communication 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).
2.Inbound idoc should be specified for the created partner profile.
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.
9 Comments
