Submitted by : Rajesh

     

This article details how logical system names of business system/service will be used for an IDoc scenario. It can be either an inbound or outbound.
Prerequisite for this tutorial is a brief knowledge on PI. This article is not going to detail the entire steps of a scenario.

While handling IDoc scenarios it is important that a care has to be taken while defining business system/service a proper logical system is being associated to that. We will see how to define these below.
If you are going to use a business system for your scenario then in the SLD we need to define the logical system during the creation of a business system itself.
Here I have defined the Business system BS_FS_G4 in SLD (where the technical system is File Sender).

During the creation of Business system itself I have associated the logical system name.

If you are going to use Business service then we know that the by using ID we can create the same, during the creation of business system we need to associate the logical system for the same by selecting the Adapter Specific identifiers of Business service.

Now we will see how these parameters are used by the integration engine during runtime.

In case of Inbound (that is IDoc send by R/3 system to PI).
After reaching IDoc to PI system (I assume that all the configurations required for sending the IDoc to PI are in place). As we know that for handling the IDoc we don’t need an IDoc sender adapter and sender agreement, so in this case for determining the receive business system ,Integration engine searches for the logical system of the business system whose IDoc control record (RCVPRN+SYSNAME+CLIENT) matches with these parameters (LogicalSystemName+R/3 SystemID+Client) in ID or for the business system having R/3SystemID+Client.
If Integration engine is not able to determine the Business system/service then it throws an error at sender system. We can see this error message in SM58 Tcode of sender R/3.

No service defined for system SAPSYS and Client in ID.

In case of outbound (that is IDoc sent by PI system).
In order to get process the IDoc in the target system it is important that the control record has proper /valid parameters, so it is important that the IDoc control record gets formed correctly during the generation of IDoc itself.
Integration engine forms the control record by taking the sender systems logical name and receiver systems logical name.

If these parameters not defined for one of business system/services we will end up with an error.
Unable to convert the sender/receiver system to ALE logical system.

Once IDoc gets generated and sent to R/3 system in order to get processed there we need to define the inbound params with the msgtype of IDoc and process code for the SNDPRN partner.

If partner profile does not exists or does not get match with the IDoc control record parameters we will get an error

StatusCode 56 : EDI Partner profile not found

I hope this tutorial give some insight for handling IDoc scenarios.

Cool !!!View other tutorials!________________________Submit a tutorial