on 01-13-2015 10:11 PM
Hi Folks,
I am working on a business functionality. The requirement is to create work items at header level and trigger workflow when the task is released (TSRL). Further, the workflow should not be triggered at the task level when the task in release(TSRL).
Since the "Correction Tasks" in the ITEMS header and TASKS header screen share a same screen, the workflow logic is getting triggered when the Task is Released(TSRL) at header level in TASKS header screen.
Both screen fields data are getting saved in table "QMSM".
Can anyone help me how to restrict the workflow functionality at Items level when the task is released.
Thanks
Hi Sandeep,
The main difference between the tasks available at header -level and Item - level is decided by Item record number (QMFE-FENUM).
Based on this value if you sort the Task table (QMSM-FENUM) then you can see the tasks which are at ""Item Level". So the understanding is if QMSM-FENUM is blank and tasks are available, they are all header tasks.
Please consider these inputs while you design your workflow with ABAP team.
Thanks,
Arijit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Arijit,
That is really helpful, you are right all the tasks with QMSM-FENUM field available are Item level tasks and all the tasks with QMSM-FENUM field blank are header level.
I discussed it with my ABAP team and now they said they are not able to find a field at workflow level to restrict it, is there any workaround for this.
Thanks
Sandeep
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.