Troubleshooting File-to-IDOC Scenario in XI.

SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials

I was just going through the SDN XI Forums and found many questions on troubleshooting of File-To-IDOC scenario in XI. I felt I can share some of my experiences in this regard. Hope this blog helps.

(1) Error scenario – File is not getting picked up from the source

(i) Check if the given source file location path and source file name is same as what is specified in sender communication channel. Then check if the Adapter status is Active in the sender file communication channel.

Using the below URL we can monitor the sender file communication channel status (File Adapter) in Adapter Monitoring.

:/mdt/amtServlet”>http://<hostname>:<J2EE Stack Portnumber>/mdt/amtServlet

If the sender communication channel shows processed successfully in adapter monitoring, then check point 4 below.

(ii) Error scenario – File is picked successfully from the given source path but is not getting converted to xml format, The adapter monitoring shows success but no messages in SXMB_MONI.. (This occurs when the file is a fixed length or comma delimited or tab delimited).

The problem could be that file structure lengths and datatype structure lengths in IR are not same. If both structures are same and still if the file is not getting converted into xml format then the problem could be in File Content Conversion (FCC). FCC parameters might not be configured correctly in sender file communication channel.

(2) Error Scenario – Cache is not getting refreshed

Cache needs to be refreshed. To refresh the cache, Tcode SXI_CACHE, XI Runtime Cache -> Start Complete cache refresh.

Check the Cache Notification in IR and ID. Status of the objects should be “Success”.

To achieve this,

Go to IR, Environment -> Cache Notification

Status of the objects should be “Success” .

Go to ID, Environment -> Cache Notification

Status of the objects should be “Success” .


IR – Integration Repository

ID – Integration Directory

(3) Error Scenario – Message is not appearing in Tcode SXMB_MONI

If there is no message in SXMB_MONI, do the below setting at Tcode SXMB_ADM.

Execute the Integration Engine Configuration

Check if role of business system has been configured to ‘Integration Server’ or not. If it is not ,then configure it to ‘Integration Server’.

(4) If message appeared in Tcode SXMB_MONI, check the XI Pipeline steps.

By default Pipeline steps do not appear in the Tcode SXMB_MONI. To get the Pipeline steps in SXMB_MONI we need to do following external setting in Tcode SXMB_ADM (Usually this setting will be done by an XI technology consultant, but its always better to know the steps)

Category: RUNTIME, Parameter: LOGGING, Current Value: 1

After entering the values, save the settings and test the scenario. Now we can view the pipeline steps in SXMB_MONI for an XML Message.

Using the XI pipeline steps we can find out the source payload and the payload after the mapping conversion. It also explains as to what happens in each pipeline step during runtime.

(5) Error Scenario – ATTRIBUTE_INV_SND_SERV or unable to convert sender service to an ALE logical system name.

The problem occurs when sender and receiver business system or business service does not have a logical system name.

ID – Integration Directory

Posting the IDOC’S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system. Please see below screen shot.

If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.


If business system type = Third-Party, then add the logical system in business system level and Save.

If the business service does not have the logical system name in ID, it needs to be configured as follows.

Check the below screen shot which shows how to add the logical system for business service.

Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.


Apply and activate.

SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials


The problem is in Technical routing.

Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.

Also check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.


Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.

Following is further info on those two mandatory parameters.

(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.

(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.

(8) Error Scenario – IDOC not yet created in target SAP R/3 system.

Go to R/3 system and check at Tcode WE05 if the IDOC has been created successfully. If error is ‘”Partner profile not configured” check point 9.

Suppose IDOC did not get created at R/3 end and all the pipeline steps were successful in SXMB_MONI, then go to Tcode : IDX5 in XI and click on Transaction ID field and check the status description which explains the problem.

(9) Error Scenario – Partner profile not configured.

Go to Tcode WE20 in R/3 system and check if the partner profile has been configured correctly and is filled with the inbound parameters.


SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
   Send article as PDF   
This entry was posted in SAP PI Troubleshooting. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *