Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Workflow Commit Work

nishantbansal91
Active Contributor

‎2015 Apr 14 11:53 AM

0 Likes
1,798

Dear Team,

I have seen a lot of transaction where we need to call the WF after creating the Document number. For WF we have function module SWE_CREATE event. How i can specify the Commit work in the standard transaction while calling the WF.

Because SAP never recommended to use Commit work in sap Transaction.

Hi Nishant,

Could you provide me the standard transaction & when you want to trigger the WF?

Regards,

Swaroop.

Reply
3 REPLIES 3
Read only

former_member191253
Explorer

‎2015 Apr 14 12:27 PM

0 Likes
1,052

Hi Nishant,

Could you provide me the standard transaction & when you want to trigger the WF?

Regards,

Swaroop.

Read only

nishantbansal91
Active Contributor
In response to former_member191253

‎2015 Apr 14 12:36 PM

0 Likes
1,052

Hi Swaroop,

It was just an thought, actually i want to clear my concept is there any other way to call the WF in new LUW that will not impact the current LUW.

Thanks and Regards,

Nishant Bansal

Read only

Former Member

‎2015 Apr 14 1:58 PM

0 Likes
1,052

Hey Nishant ,

We can always call out Event creation in update task. Even if you go with Oops , there is a method with a parameter "Update task" so that whenever the database commit is happening , event creation will be done after the document number is generated. This way , you are binding the database commit together in one database LUW with event creation. You never need a new LUW for WF event.

Hope that makes sense.

Thanks

Rakesh