-
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
- Discussions
- Re: Issue when specific code is processed during a...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Issue when specific code is processed during a standard inbound Idoc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2015 Feb 12 3:28 PM
- SAP Managed Tags
- ABAP Development
Hi Gurus,
I've a problem to submit to you : I've modified the standard FM IDOC_INPUT_ORDERS in order to insert two specific functions during input of the standard IDoc.
One function which aims at sending a mail including data of the input Idoc (using standard classes and methods),
another which aims at modifying the status of the created purchase order (using standard FM STATUS_UPDATE).
The fact is that this two specific codes run properly when I process an inbound IDoc through the transaction WE19. (all work perfectly : a mail is sent, and the statuses are moved as I want).
My problem is that, when this inbound IDoc is processed in an automatic mode, thanks to background processes, none of the two specifics are executed : no mail is sent, no status is updated...
I tried to add "COMMIT WORK..." or "WAIT UP TO...", expecting that this problem was created by a problem of buffer... But no effects...
Has somebody an idea to understand what happens, or, more, to correct this issue ?
Thanks in advance,
Pascal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2015 Feb 27 9:25 AM
- SAP Managed Tags
- ABAP Development
Back of the damned abaper !
Sorry for the delay (I was in holidays).
The source of this dysfunction is very tricky : somewhere in the specific code, the table which contains the IDOC_CONTROL records is read in order to test the result of the process of the IDoc.
The fact is that the final IDoc status is not the same when you use "Standard Inbound" or "Inbound function module". In one case, the status is 53, in the other 64... So beware of the value you test !
Have a nice day !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2015 Feb 12 5:00 PM
- SAP Managed Tags
- ABAP Development
Hi.
If Mail is first process to be executed, probably it goes in error. What's the function used for mail sending?
I would call this function in a separate task.
Did you check out st22 for dumps?
Hope to help
Bye
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2015 Feb 13 7:48 AM
- SAP Managed Tags
- ABAP Development
Hello Roberto,
The fact is that the IDoc is processed : we can see it through WE02 as a green process. No dump...
I continue to check, and will come beck if i find others elements,
Pascal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2015 Feb 27 9:25 AM
- SAP Managed Tags
- ABAP Development
Back of the damned abaper !
Sorry for the delay (I was in holidays).
The source of this dysfunction is very tricky : somewhere in the specific code, the table which contains the IDOC_CONTROL records is read in order to test the result of the process of the IDoc.
The fact is that the final IDoc status is not the same when you use "Standard Inbound" or "Inbound function module". In one case, the status is 53, in the other 64... So beware of the value you test !
Have a nice day !
Bluesky