PR release workflow triggers twice

[former_member196651]

Hello Friends,

I had created a custom workflow for the item wise release of Purchase Requisition(PR). 2 levels of release are needed for all items whose value is above a particular amount.

My problem is that, for all items in PR which requires 2 levels of release will generate 2 similar work items in agent's inbox. Even if we complete a work item execution, the other will remain in the inbox as not started.

I had used SWE2 to find anything is wrong with the event linkages. There it shows a linkage to the event 'RELEASESTEPCREATED' of BUS2009 to my custom workflow only. Similerly I used SWEC to find any linkages there. There also I can't find anything wrong.

Then I had used SWEL. I got the following result for a PR that contains only one item which requires 2 levels of release:

BUS2009 RELEASESTEPCREATED 04.11.2011 16:34:07 WS90000044

BUS2009 RELEASESTEPCREATED 04.11.2011 16:34:08 WS90000044

Is there anything else that I had to do? Can someone tell me what I had to do to correct this issue?

Please help me to solve this problem as soon as possible.

Regards,

Abijth

[bpawanchand]

Hi,

BUS2009 RELEASESTEPCREATED 04.11.2011 16:34:07 WS90000044
BUS2009 RELEASESTEPCREATED 04.11.2011 16:34:08 WS90000044

Can you please let me know that are you trying to rasie event from any custom code. If you are rasing the event through custom code then try to deactive the peice of code. I feel like the standard applicaiton or transaction must be rasing the event.

Regards

Pavan

[former_member185167]

Hello,

Checking in SWEL was a good idea. Two events are being created. Could you confirm in the workflow log that two different releasecode values are being passed to the workflows?

Not sure how to fix this, it's not really a workflow problem, more a configuration problem.

You may want to look in some of the other forums.

regards

Rick Bakker

hanabi technology

[former_member196651]

Hello Rick,

Sorry for being late in reply. We were having holidays on Sat & Sun.

I had checked the workflow log of the workitems that is appearing in the agent's inbox. The release codes are different for the workitems. Means, if the release codes are 02 & 03, then for example, the agent for release code 02 will receive 2 work items where the release codes will be 02 & 03.

Thanks & Regards,

Abijith

[RicardoRomero_1]

Hi,

I don't know if I understood well the problem, but if you want to not launch the workflow twice, you can use a "Check Function Module" within event linkages and if the workflow exits stop the second event...

Regards,

[suresh_subramanian2]

Hello !

Please check in SWEC transaction, whether any change document is configured.If so, delete it and check.

Also, check any user-exit or BAdI have been implemented for the same

Regards,

S.Suresh

[former_member196651]

Hello Ricardo,

My problem is that, workitems generates for all the release codes for each of the agents responsible for releasing the PR. That is, if an item of the PR requires 2 levels of release (say release code 03 for low level release where agent will be A and release code 02 for high level release where agent will be B ), then after the creation of the PR each of these agents A & B will receive 2 workitems in their inbox and in each of these workitems the ReleaseCode which is an import parameter of the event 'RELEASESTEPCREATED' will be 02 & 03 respectively.

I had also seen from some forum threads about the usage of Check Function Modules. Is it applicable here? If you think so, then how it can be used. Whether I had to use any standard FMs or I have to create one? Can you help me out with a sample code?

Hello Suresh,

I had used SWEC as I mentioned in my first post. There everything appears to be well.

Thanks & Regards,

Abijith

[suresh_subramanian2]

Hello Abijith !

Do you mean to state that once purchase requisition document is created, agent A receive two work items and after it is processed by agent A, agent B receives two work items ?

Have you deleted the configuration made in SWEC and checked again ? Have you verified no BAdI

or user-exit is triggering the workflow ?

Regards,

S.Suresh.

[former_member196651]

Hello Suresh,

At the time when a PR is created, both agents A & B will receive 2 woritems each in their inboxes and not as B receives 2 workitems after executing the workitems by agent A. In our scenario I had done this using a fork. The differences that I identify are, these workitems have different workitem IDs and their release codes will be that for agent A & B.

I forgot to mention one thing. I had also executed the standard workflow WF_REQ_REL for itemwise release of PR. Here also I am getting the same result.

I had used the transaction SWEC. There I can't find any form of linkages to the business object BUS2009. Similerly no workflow is triggered from a BAdI or an Exit.

Regards,

Abijith

[suresh_subramanian2]

Hello Abijith !

Once purchase requisition document is created, bot the agents get work item at a time with two different work item ids.Am I right ?

Please check in SPRO transaction, whether more than one release group is configured.

Hope none of the radio buttons are chosen for bus2009-releasestepcreated in SWEC.

Regards,

S.Suresh.

[former_member185167]

I still think it's a configuration problem. Concentrate on getting those events with different release codes NOT being created at the same time. Nothing to do with workflows or check functions.

[Former Member]

Hi Abijith,

Go to your SWEC and delete the event linkage. Now if the workflow itself dosent trigger then it is config issue but if u get only one workitem then it is check function module issue.Also check in SPRO how the item level strategy is defined.

Regards,

Dheepak

[former_member185167]

How are you going to get a workitem without an event linkage?

[former_member196651]

Hello Suresh, Rick & Deepak,

Thanks for your prompt replies.

Suresh, you were right. The workitems in one agents inbox is having different workitem IDs and the Release code, which is an import parameter of the event 'RELEASESTEPCREATED' is also different. I checked SPRO. There exists only one release group for PR which is 01. The other release group is for PO, which is 02. SWEC does not contain an event linkage for BUS2009.

Deepak, SWEC does not contain an event linkage for BUS2009. In our scenario the release strategy is setup as follows:

01 01 ZMAR value < 50,000

01 02 ZMAR value > 49,999

01 03 ZCAP value < 50,000

01 04 ZCAP value > 49,999

01 05 ZOTH value > 9,999

Rick, can you please help me to identify what is the config. issue, so that I can workout that with our functional guys.

Thanks & Regards,

Abijith

[suresh_subramanian2]

Hello Abijith !

I don't see any problem with the illustrated release procedure configuration as seen above.

Whether those two work item ids belong to same workflow or different ? If it is different, deactivate the event linkage of the workflow which is not required.

If both the work item ids belong to same workflow, then , whether release group is same ?

If release group is different, either delete the unwanted release groups from release procedures or incorporate start condition in workflow for the required release group only.Doing so, the workflow would trigger only if purchase requisition document is created with the required release group only.

Regards,

S.Suresh.

[former_member196651]

Hello Suresh,

I had checked both the workitems. Both of them belongs to the same workflow. Moreover the release group in both these workitems are same( here in my scenario it is 01 ). Then also I had added a start condition in start events so that it triggers only for release group 01.

After all this, I am having the same problem. Thanks for all your expert advice. Any other option to correct this.

Thanks & Regards,

Abijith

[suresh_subramanian2]

Hello Abijith !

Please check whether the event triggers from customizing table.

Also check in SWUD transaction -> Test environment -> Simulate event.

Regards,

S.Suresh

[former_member196651]

Hello Suresh,

How can I check whether the event is triggering from customizing table? As you said I had used SWUD. There in simulate event, event triggering against the workflow is shown as green. Now what should I do?

Thanks & Regards,

Abijith

[former_member185167]

It's configuration. I try to leave it to the functional guys. Demonstrate that two events are being created where there should be one and tell them to fix it

[suresh_subramanian2]

Hello Abijith !

In SWUD, hope only this workflow id is shown under "successfully started".

To know whether this workflow is getting triggered from customized table, check is there any custom table does have

BANFN field.If so, go to that table and Utilities -> Table maintenance generator.You will get new screen where Environment -> Modifications -> Events.

If any events are configured, delete them.

Regards,

S.Suresh.

[former_member196651]

Hello Suresh,

In SWUD only my custom workflow is shown under 'Successfully Started'. Can you simply give an example for a custom table containing BANFN field. Because when I listed using where used list from SE11, I got several tables, but can't identify which is a normal table and which is a custom table.

We will be having off on Sat & Sun. So may be I will be replying on Mon only. Thanks for all the help that you are providing.

Thanks & Regards,

Abijith

[Former Member]

Hi Abijith

I guess your issue is, two workflows are triggered for 2 different release codes at the same time and those are not completed even if work item is executed.

Do you want the workflow to be triggered for Release code 02 first and for 03 after Purchase requisition is released for release strategy '02'?

If above is the case, Release strategy configuration to be setup in such a way that 03 is set as a pre-requisite for 02. (You can check this with Functional)

The existing workflow for release code 02 can be completed if you add 'Released' as terminating event to this task. This task gets completed when corresponding release is executed and at the same time subsequent release step is created and new workflow gets triggered for release code '03'

Regards

Vaishali

[suresh_subramanian2]

Hello Abijith !

In SAP, all custom table name begins with Y or Z.

For example, EBAN is standard table and not custom table.

Regards,

S.Suresh.

[former_member196651]

Hello Suresh,

I was thinking of customizing tables(where customisations are stored) in SAP, not the Z or Y ones. OK. I fonud only one table and that don't have any event associated with it. Now I am trying for a workaround for this problem.

Thanks & Regards,

Abijith

[former_member196651]

Hello,

This problem arises because I am using 'RELEASESTEPCREATED' event of BUS2009. So I am going to try a different approch. I am going to trigger my custom workflow for the event 'CREATED' of the business object BU2105. Then I extended the business object and added a method which will return the items of the PR as objects in a table. By looping through this table I am going to get the release strategy & release group of the items and based on that my workflow will work. I am hoping that this will work properly.

Thanks & regards,

Abijith