Troubleshooting of ALE Process - SAP Blogs PDF

11/29/2017 Troubleshooting of ALE Process | SAP Blogs
Products
Products Industries
Industries Support
Support Training
Training Community
Community Developer
Developer Partner
Partner
About
About
 
Home / Community / Blogs + Actions
Troubleshooting of ALE Process
July 19, 2007 | 478 Views |
Raja Thangamani
more by this author
SAP Cloud Platform Integration for process services
Integration and Certification Center | idoc | idoc processing | SAP Integration And Certification Center | troubleshooting of ale
process
share
0 share
0 tweet share
0

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

https://blogs.sap.com/2007/07/19/troubleshootingofaleprocess/ 1/20
1. How to determine what code the IDoc is executing

1. Outbound

2. Inbound

2. High Level Error Resolution for Outbound/Inbound Idocs

1. Not sure if IDoc was created or received

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

3. IDoc created, but not received by receiving application

4. How to resend an IDoc.

5. IDoc received, but not posted (inbound side).

6. IDoc Batch Job:

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. Direct Path

3. Change Pointers

Message Control:

1. Execute Transaction Code – WE20

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


3. Select the Message Control Tab

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.

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

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

6. 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.

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.

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

1. Execute Transaction Code – WE20

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


3. Double click on the process Code

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.
4. You can double click on the inbound function module name to view
code and set breakpoints.


5. 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. IDoc not created/received, which should have been.

3. IDoc created, but not received by receiving application

4. How to resend an IDoc.

5. IDoc received, but not posted (inbound side).

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. Double click on your valid Message type line to get a list of IDocs.

3. 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 12 for the different status
until you find your IDoc(s). If IDoc not found, go to IDoc batch job
section and Case 2 section.

4. 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. 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. If the IDoc is in Yellow status (Status30), you can push through
Transaction code – BD87.

3. 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.

4. Hit execute.

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

6. 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.

7. 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.

8. Hit execute button

9. 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. 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. To push Customer Master – use Tcode BD12

3. To push Vendor Master – use Tcode BD14

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

1. Execute transaction WE19.

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

3. Select Execute

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


5. Select Continue.

6. 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. Execute transaction BD87

3. 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.

4. Hit execute

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

6. 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.

7. Click “Process” button.

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

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. RBDMANIN (posts status 51 IDocs)

3. RBDMIDOC (Change Pointers, can check via BD50)

2. 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. RSEOUT00 (sends IDocs – we14)

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

4. RBDMOIND (changes IDoc from status 03 to 12)

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
Alert Moderator
15 Comments
You must be Logged on to comment or reply to a post.
Harrison Holland
December 12, 2006 at 3:42 am
This is a good blog, and will serve as a nice checklist for someone running into issues.
Jay Kavala
December 12, 2006 at 6:10 am
A well organized presentation
seshu madhava
February 6, 2007 at 4:23 am
very useful for reprocessing the idocs and correcting out the errors in idocs.
very good
Raja Thangamani Post author
March 2, 2007 at 9:29 am
Thanks a lot for your comments..
Raja T
Jayanthi Jayaraman
March 7, 2007 at 7:28 pm
It’s very useful.
March 8, 2007 at 2:51 pm
Thanks for your comments…
Raja T
Sharan Sreenath
May 2, 2007 at 9:12 am
Hello Raja,
We are getting code 56 when trying to process a inbound
IDOC. Can u pls help me.
Thank You,
Sharan Alemane
Sharan Sreenath
May 2, 2007 at 9:15 am
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
May 3, 2007 at 6:31 am
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
May 4, 2007 at 7:37 am
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
John Hansen
July 12, 2007 at 12:52 pm
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.
wenyao ma
March 30, 2010 at 6:45 am
Thank you,Raja.
The artical is helpful for me.
Tejaswini Chintawar
April 15, 2010 at 3:05 am
Thanks for posting such a nice article.
It is really a helpful one.
GURU AILSINGHANI
June 22, 2010 at 2:39 am
Thanks Raja
Ning Li
January 12, 2013 at 12:18 pm
Thanks, very helpful
Share & Follow
Privacy Terms of Use Legal Disclosure Copyright Trademark Sitemap Newsletter

Troubleshooting of ALE Process - SAP Blogs PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Troubleshooting of ALE Process - SAP Blogs PDF

Uploaded by

Copyright:

Available Formats

11/29/2017 Troubleshooting of ALE Process | SAP Blogs

You might also like