-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- SAP Business Suite
- Artificial Intelligence
- Business applications
- Data and analytics
- Technology Platform
- Financial Management
- Spend Management
- Supply Chain Management
- Human Capital Management
- Customer Experience
- SAP Business Network
- View products A-Z
- View industries
- Try SAP
- Partners
- Services
- Learning and Support
- About
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
WRONG IDOC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2022 May 13 7:51 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2022 May 13 8:01 AM
- SAP Managed Tags
- ABAP Development
Can you please give us some more details? Which message type process are you using?
For each message type/basic type there is am inbound function module behind which can be debugged, also using WE19.
Kind regards
Jens
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2022 May 13 8:18 AM
- SAP Managed Tags
- ABAP Development
jzaehringer not sure with the message type but details given were only it is an inbound document.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2022 May 13 8:58 AM
- SAP Managed Tags
- ABAP Development
walkerist but how do you test this scenario in this case? Using WE19 it would be easy to copy an existing IDoc (or to fill one from scratch) and then you are able to debug it.
But how should we help w/o having the main relevant information?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2022 May 13 9:41 AM
- SAP Managed Tags
- ABAP Development
jzaehringer iDOC document number is also given. I need to know where's the source field of material.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2022 May 13 9:47 AM
- SAP Managed Tags
- ABAP Development
walkerist But if you have the IDoc number for testing, then you could also tell us the message type?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2022 May 13 10:13 AM
- SAP Managed Tags
- ABAP Development
jzaehringer Status is 53, Message Type is ORDERS. Partner type is KU.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2022 May 14 6:22 PM
- SAP Managed Tags
- ABAP Development
Starting the debugger is easy, but finding the reason why a given logic is applied is much more difficult.
I think only people with a lot of experience in debug can do this, but only if they connect to your system. They could advise if you give more information.
Otherwise, use an ABAP trace (SAT) with all the details (without "aggregation") and try to locate the block of subroutines or methods whose names indicate they are about fetching the materials...
Bluesky