Skip to Content

Introduction:

This blog will emphasize on “Troubleshooting of ALE Process. It covers following matrixes:

         

  1. How to determine what code the IDoc is executing       
                

    1. Outbound
    2.           

    3. Inbound
    4.      

         

  2.      

  3. High Level Error Resolution for Outbound/Inbound Idocs       
                

    1. Not sure if IDoc was created or received
    2.           

    3. IDoc not created/received, which should have been.
    4.           

    5. IDoc created, but not received by receiving application
    6.           

    7. How to resend an IDoc.
    8.           

    9. IDoc received, but not posted (inbound side).
    10.           

    11. IDoc Batch Job:
    12.      

         

Lets look at each in detail.

         

  1. How to determine what code the IDoc is executing:
         In some cases, you may need to debug through the IDoc code to see where data is being pulled from and/or where the IDoc is failing. The following will provide this information for Outbound and Inbound ALE IDocs.       
                

    1. Outbound –IDoc can be created in 3 ways.            
                       

      1. Message Control
      2.                

      3. Direct Path
      4.                

      5. Change Pointers
      6.           

                

    2.      

         

Message Control:

         

  1. Execute Transaction Code – WE20
  2.      
                 

  3. Select the logical system and double click the message type under Outbound Parameter.
  4.      
                 

  5. Select the Message Control Tab
  6.      
          
         
         Note: This tab will be displayed if “Message Control” is used. In this case, message control is being used and Idocs will get created for every New and/or Change of delivery notes. If you don’t see message control set up, go to Direct Path and changes pointers.
         
         

  7. Double click on process code to see what code it’s triggering.
  8.       
         
         

  9. You can double click on the inbound function module name to view code and set breakpoints.
  10.      
          
         

  11. DO NOT DO IN PRODUCTION: Process an Idoc via BD87 and you should stop at the breakpoint.

Direct Path:

         

  1. DO NOT DO IN PRODUCTION: Debug program RSEOUT00 for direct path       
                

    1. You can also look at transactions WE64, but not all process codes will be listed there.
    2.      

         

Change Pointers:

         

  1. DO NOT DO IN PRODUCTION: Debug program RBDMIDOC for direct path       
                

    1. You can also look at transactions WE64, but not all process codes will be listed in there.
    2.      

         

So far we covered the Outbound process. Let’s look at the Inbound Processes.

b. Inbound:

         

  1. Execute Transaction Code – WE20
  2.      
         
         
         

  3. Select the logical system and double click the message type you are looking for on the right hand side under “Inbound Parameter”.
  4.      
         
         
         

  5. Double click on the process Code
  6.      
         
         Note: The function module name is in the “Identification” Field. This is what gets executed when the IDocs is inbound. The processing does many data validation checks and then updates the database tables.       

  7. You can double click on the inbound function module name to view code and set breakpoints.
  8.      
         
         
         

  9. DO NOT DO IN PRODUCTION: Process IDoc via BD87 and you should stop at the breakpoint.

So far we’ve seen what code an IDoc is triggering. Now lets see how to troubleshoot the Problems.

         

  1. High Level Error Resolution for Outbound/Inbound Idocs       
                

    1. Not sure if IDoc was created or received
    2.           

    3. IDoc not created/received, which should have been.
    4.           

    5. IDoc created, but not received by receiving application
    6.           

    7. How to resend an IDoc.
    8.           

    9. IDoc received, but not posted (inbound side).
    10.      

         

Case 1: Not sure if IDoc was created or received.

         

  1. Execute Transaction WE05; enter correct date/time frame and logical message type. (You can also search by a specific IDoc, see section Searching for a specific IDoc)
  2.      

  3. Double click on your valid Message type line to get a list of IDocs.
  4.      
         
         
         

  5. See IDoc Statuses section to determine if IDoc(s) was successful or not. Note: there maybe several different statuses for a Message type so you may need to repeat steps 1-2 for the different status until you find your IDoc(s). If IDoc not found, go to IDoc batch job section and Case 2 section.
  6.      

  7. If IDoc is found in a successful status, go to case 3. If IDoc found in failed status, open status records folder and double click on the failed status records to get error message as why IDoc failed.

Case 2: IDoc not created/received, which should have been.

         

  1. Use steps in Case 1 to verify if the IDoc was created or not and successful or not.
  2.      

  3. If IDoc is not found, validate job is running. See section IDoc Batch Job.

Case 3: IDoc created, but not received by receiving application.

         

  1. Use steps in Case 1 and 2 to verify if the IDoc was created or not and if IDoc is in a successful status or not.
  2.      

  3. If the IDoc is in Yellow status (Status-30), you can push through Transaction code – BD87.
  4.      

  5. If the IDoc is located and status is successful but receiver has not received the IDoc, Execute transaction SM58 to determine if IDoc is stuck in the ALE/RFC layer. Enter in ‘*’ in all fields except leave Display period field with default values.
  6.      
         
         
         

  7. Hit execute.
  8.      
         
         
         

  9. If entries exist in SM58, look for Message Type. If message type exist and Run the Program “RSARFCEX”
  10.      

  11. If after the RSARFCEX program has ran and IDocs are not in SM58, issue should be solved. Validate in receiving system via WE05 that the IDoc was received. If IDoc is still stuck in SM58, check RFC connection. Go to SE37, enter function module RFC_PING.
         Note: In most of the case we’ll not have access to SM59 to test the RFC Connection.
  12.      

  13. Hit test button, Enter RFC destination (the interface system of the IDoc). NOTE: when entering RFC destination, keep in mind the field is case sensitive.
  14.      

  15. Hit execute button
  16.      

  17. If function module fails, there is an RFC issue. Contact team, which creates the RFC Destination.

Case 4: How to resend the IDocs.

We can segregate into 2 parts here:

         

  1. How to resend Master IDocs
  2.      

  3. How to resend an Existing Idoc

Lets see the option 4a: How to resend Master Idoc

Here i gave couple of Transaction to push the Master data.

         

  1. To push Material Master – use Tcode BD10
  2.      

  3. To push Customer Master – use Tcode BD12
  4.      

  5. To push Vendor Master – use Tcode BD14
  6.      

  7. …..

Lets look at the option 4b: How to resend an Existing Idoc

         

  1. Execute transaction WE19.
  2.      

  3. Enter the Idoc # you would like to resend in the Existing Idoc field.
  4.      

  5. Select Execute
  6.      

  7. Click on “Standard Outprocessing”. Be very careful not to change the Idoc information. This gets save to the Database if changed
  8.      
         
         

  9. Select Continue.
  10.      

  11. Idoc has been resent. Notice the message IDoc no. ### saved in database. A new IDoc number has been resent but sent with same information.

Case 5: How to process an IDoc.

         

  1. After an issue has been resolved and/or you need to process an IDoc, besides processing IDocs via programs, you can also process IDocs via Transaction BD87
  2.      

  3. Execute transaction BD87
  4.      
         image
         

  5. If you know the Idoc number, enter the Idoc number in the Idoc number field. If you need to process many Idoc numbers, you can also just hit execute.
  6.      

  7. Hit execute
  8.      
         
         

  9. Expand the Idoc(s) you would like to process.
  10.      

  11. Select the Message Type you would like to process. Note: If you did not enter a specific Idoc number, when you select the Message Type, ALL of those Idocs for that message type will be processed.
  12.      

  13. Click “Process” button.
  14.      

  15. You results will be displayed (if Idoc processed successfully)
  16.      
          

IDoc Batch Job.

If IDocs are processed in SAP batch, validate the job is running via SM37.

         

  1. Typical Inbound jobs run programs:       
                

    1. RBDAPP01 (posts IDocs)
    2.           

    3. RBDMANIN (posts status 51 IDocs)
    4.           

    5. RBDMIDOC (Change Pointers, can check via BD50)
    6.      

         

  2.      

  3. Typical Outbound jobs run programs       
                

    1. RSNAST00 – WE15 (if using message control, can check via partner profile WE20). Also validate message control is set up properly via NACE. (Creates IDocs)
    2.           

    3. RSEOUT00 (sends IDocs – we14)
    4.           

    5. RSARFCEX (clears IDocs out of ALE/RFC layer)
    6.           

    7. RBDMOIND (changes IDoc from status 03 to 12)
    8.      

         

 

IDoc Statuses:

 

See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes

Successful Transmission:

         

  • 03 – Successful outbound transmission
  •      

  • 12 – Dispatch OK

IDoc being processed:

         

  • 01 – IDoc created
  •      

  • 30 – IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)

ALE Error Messages:

         

  • 02 – Error passing data to port
  •      

  • 04 – Error within control information on EDI subsystem
  •      

  • 05 – Error during translation
  •      

  • 25 – Processing despite syntax errors (outbound)
  •      

  • 29 – Error in ALE service
  •      

  • 32 – Resubmit edited intermediate document (DO NOT USE)

Syntax Error Messages:

         

  • 26 – Error during syntax check of IDoc (outbound)
  • Inbound ALE Status Codes

IDoc Processed Successfully:

         

  • 50 – IDoc added
  •      

  • 53 – Successful posting

IDoc ready for processing:

         

  • 64 – IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.

Errors in IDoc Processing:

         

  • 51 – Error – application document not posted
  •      

  • 56 – IDoc with errors added (You should never see this error code)
  •      

  • 60 – Error during syntax check of IDoc (inbound)
  •      

  • 61 – Processing despite syntax error (inbound)
  •      

  • 63 – Error passing IDoc to application
  •      

  • 65 – Error in ALE service – indicates partner profiles are incorrect
  •      

  • 69 – IDoc was edited
To report this post you need to login first.

15 Comments

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

  1. Sharan Sreenath
    Hello Raja,

    We are getting code 56 when trying to process the inbound IDOCS, can you pls help.

    System : 4.6c
    Inbound : From biztalk to 4.6c

    Thank You,
    Sharan Alemane

    (0) 
    1. Raja Thangamani Post author
      Error code- 56; stands for “IDoc with errors added”.

      Just try to debug the while posting the IDoc to know what/why/when you are getting the error. The above blog will help you how to debug it.

      Raja T

      (0) 
  2. Dear Raja,

    please, could you give advice on IDOC status 54 (Error during formal application check)?…

    Has this status any specific meaning and usage?

    In which cases it is recommended by SAP to set it?

    Should it be always followed by a record with status 51?

    Thanks and best regards,
    Vlad

    (0) 
  3. John Hansen
    Where did you get this information?  Since the user ids are people that I work with and you do not work form my company, I was curious how you came by this information.
    (0) 

Leave a Reply