- SAP Community
- Groups
- Interest Groups
- Application Development
- Discussions
- Trouble shooting an Idoc
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Trouble shooting an Idoc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2006 10:57 PM
Hi All,
Can anybody explain me how do we trouble shoot an error Idoc both on inbound and outbound side. Normally do we do that using any tcodes or is there any specific procedure to be followed ? Please tell me where the resources are available or if you have any documents please forward them to vijaynagendrak@yahoo.com.
Experts please help me.
Regards,
Vijay
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2006 11:36 PM
Hi Vijay,
on the inbound side you can use transaction WE19. Enter the IDoc number that is in error and start the IDoc using the button <i>Inbound function module</i>. Here you have the option to start in debugger.
You need to enter the function module that should be processed. If you don't know the name of it, click on <i>Standard inbound</i> first. It gives you the name of the function module.
Regards,
Claus
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2006 11:36 PM
Hi Vijay,
on the inbound side you can use transaction WE19. Enter the IDoc number that is in error and start the IDoc using the button <i>Inbound function module</i>. Here you have the option to start in debugger.
You need to enter the function module that should be processed. If you don't know the name of it, click on <i>Standard inbound</i> first. It gives you the name of the function module.
Regards,
Claus
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2006 11:42 PM
Hi Claus,
This is a way to debug single Idoc. Is there any means to debug all Idocs which have similar error at a time othere than bd87.
Regards,
Vijay.
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2006 3:19 AM
Vijay,
If you are able to debug one IDOC and fix that issue, guess the error with other IDOCS also will get fixed, as you are saying its the same error.
Regards,
Ravi
- SAP Managed Tags:
- ABAP Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2006 4:30 AM
Hi Vijay,
Based on my experiences, I always go to WE02 (IDoc List) to analyze the error message. Sometimes, the error message is very straight forward and explainable by looking at status records. For example, 'Missing Partner Profile'. But sometimes the error is very challeging and is hard to understand.
For this case, I usually go to WE19 (Testing Tool) in QUA system to simulate the error message and also try to debug step by step the inbound/outbound processes.
As a results of the above activities, I usually able to figure out the issue. The more you practise, the better result you will get.
The most common issue are related to incorrect input data and incorrect data mapping (mandatory field vs optional field). Sometimes, it could conflict with process configuration for particular application area (you may need functional folk to help) or incorrect ALE and IDoc configuration.
After finding and able to solve the issue in QUA system then you can try to reprocess the production error IDoc via BD87.
Hope this information will help you.
Please let me know if you need further assistant.
Regards,
Ferry Lianto
- SAP Managed Tags:
- ABAP Development
