-
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
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Blog Posts
- Debug outbound IDoc triggered by one output type
Application Development and Automation Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forÂ
We have launched new Developer forums/groups in the SAP Community. If you are here to publish developer- or SAP-technology related blog posts, please check out our new groups instead. You can find more information about the developer forums in this What's New post.
Jigang_Zhang
Active Contributor
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
‎2021 Jan 28
2:55 AM
36,385
- SAP Managed Tags
- ABAP Development
It's a cliche about how to debug outbound Idoc triggered by one output type. There're dozens of good articles that already talked about this, Including:
Just recap this, have a try the efficiency approach first before going through all various approaches.
1.Get the process code from WE20 by message Type;
2.Get the Function module by Process code;
3.Set the breakpoint at FM get from the above step and run the program RSNAST0D.
- WE19;
- Change the timing setting for output type to '1' along with the program RSNAST00;
- Active update debugging;
- Maybe the most direct way is using the program RSNAST0D(Generic output issue).
Just recap this, have a try the efficiency approach first before going through all various approaches.
1.Get the process code from WE20 by message Type;
2.Get the Function module by Process code;
3.Set the breakpoint at FM get from the above step and run the program RSNAST0D.
Bluesky