Workflow WS75700040 steps - step number 3 - Revision - usage

[Former Member]

Hello,

In the workflow WS75700040 which is delivered by SAP, there are the following 3 workflow steps defined by default:

1. Processing (Step 1)
2. Final Check (Step 2)
3. Revision (Step 3)

(Path: MDGIMG - Master Data Governance - General Settings - Process Modeling - Workflow - Other MDG Workflows - Define Workflow Step Numbers)

Then in "Assign Processer to Workflow Step Number (Simple Workflow)" it is possible to assign Agents to Change Requests for each Step of a used Workflow.

I'm experiencing the following problem:

When I create a change request through NWBC which uses this Workflow, where all 3 steps have different agents assigned - I'm not able to get into a step in the Workflow, where the list of allowed multiple Current Processors would contain the user/position defined for "Step 3 - Revision".

I don't understand where exactly and how to define, that for example this "Step 3 - Revision" defined in "Define Workflow Step Numbers" is which step/tesk in the actual Workflow WS75700040 (in transaction SWDD). Maybe some screenshots would help me to see, what is connected with what.

When I open the Workflow WS75700040 through SWDD, I see the following 3 Step Names with Agent Assignment (swdd - left: Navigation area):

• Execution of Changes (Task Name: Process Change Request; Workflow step type: Process - initial value: 3)
• Final Check (Task Name: Approve Change Request; Workflow step type: Approve - initial value: 2)
• Revision After Rejection (Task Name: Revise Change Request; Workflow step type: Revise - initial value: 4)

What exactly does this initial value mean? And shouldn't all the 3 Step numbers from "Define Workflow Step Numbers": 1,2,3 be somewhere defined in the actual workflow? If yes, then where?

Thank you!

Regards,

David

[bpawanchand]

HI,

I'm not able to get into a step in the Workflow, where the list of allowed multiple Current Processors would contain the user/position defined for "Step 3 - Revision".

You mean to say that you are not able to see the work item in the NWBC work list. The process would be some thing like below:

1. When Initiator submits the change request the reviewer can either finalize processing or send it for revision, when reviewer clicks on send for revision then in that case it should again go back to the initiator of the change request. So make sure in the Assign processor to workflow you give the initiator as agent.

2. You do not have to do any changes in the workflow template. every thing purely depends on the configuration and (BADi implementations if required).

3. Once the reviewer finalizes the process then it would go the final check where approver can either approve or reject. ..

Let me know if you require any other information.

Regards

Pavan

[Former Member]

Hi Pavan,

Thanks for your answer.

I'm able to see the work item/change request in my NWBC work list in all steps of the workflow - also in the steps where only the initiator can see it, because I'm the initiator.

I don't understand, don't see when the agents I assigned to the Step "3 - Revision" will see the work item in their NWBC work list.

For me it looks like, that only the agents I assigned for Steps 1 and 2 are assigned during the workflow process of the work item, but never the agents defined in Step 3.

Example:

Step 1 - I assigned the USER_A

Step 2 - I assigned the USER_B

Step 3 - I assigned the USER_C

I went through all the possible workflow steps and statuses of this workflow, but the user USER_C was never part of the assigned processors list - so I don't understand the meaning of this 3rd step if it is never used in the workflow. Is this step 3 - Revision really necessary?

Thank you.

Regards,

David

[Former Member]

Hi David

these 1,2,3 is nothing but condition alias, i think either you haven't assigned agent for step 3, or might be providing wrong user id. one more thing did u defined this step as assigned agent or general task  in your worflow?? please check

and i think this step 3 is not necessary.

Regards

Nitish Sharma

[Former Member]

Hi Nitish,

these 1,2,3 is nothing but condition alias

condition alias - aliases for conditions? where are these conditions defined for which they serve as aliases only?

did u defined this step as assigned agent or general task  in your worflow?

Where can I do this? What's the difference if I define it as assigned agent or general task in respect to whether an agent defined in "Assign Processer to Workflow Step Number (Simple Workflow)" for Step 3, will have the change request in his work list or not? (maybe screenshot would help a lot about how the correct configuration should look like)

Assume that I have everything correctly configured in MDG (which I probably don't have at the moment):

Which status needs the change request have in order for it to show up in the work list for the user assigned for Step 3 - Revision?

Regards

David

[Former Member]

Hi david

I worked on slightly different scenario , i assigned agent in brf+ (not under other mdg workflow->assign processor), you will find these aliases under brf+ , if these values 1,2,3 are the condition aliases i am thinking you are using.

regards

Nitish

[Former Member]

Hi Nitish,

ah, ok, in BRF+ I know what condition aliases are .

As you wrote, my scenario is different from yours - the workflow I'm using is not rule-based -> I'm not using BRF+ to assign agents/processors to workflow steps.

I don't see the meaning of step name 3 - Revision in the workflow WS75700040 and how it can be used in a real-life example.

Regards

David

[bpawanchand]

Hi,

The real use you can see only if reviwer sends it back by clicking on the button send for revision .

Very simple

1. Initiator submitted the change request.

2. Reviewer can either click on finalize processing or send for revision. IF you click on send for revision button then the workitem will be sent to the processor which you have configured USER_C.

Regards

Pavan

[Former Member]

go for this link......you will find real life example.....

http://help.sap.com/erp2005_ehp_05/helpdata/EN/84/d454d14dbf4a8bb5fce8e696accade/content.htm

Regards

Nitish Sharma

[Former Member]

Hi Pavan,

In my case, this doesn't work and this is my problem, which I'm trying to figure out.

After creating a change request, I as the reviewer click on "Send for Revision". When I check the Workflow Log for this change request, only the initiator is assigned as the current processor of the change request.

According to this configuration:

both the assigned Position and the User should be assigned to the change request in this step, but they aren't, instead only the initiator is assigned:

So, what I still don't know, how does MDG know, that the step Revision (step number 3) in the workflow WS75700040, is the step that follows after a reviewer clicks on "Send for Revision" in the change request.

Is there any other configuration, where the step numbers are defined in the workflow? Because the only one I know about is this one:

But, how does the workflow know, that the Step 3 is the step after somebody clicks on "Send for Revision"?

Is there a way what I can check to figure out some more info, why the agents I assigned to this step 3, aren't displayed as the current processors in the workflow log?

Thank you!

Regards,

David

[Former Member]

Hi David

Did you get some idea by this real time example, or any further information needed??

[Former Member]

Hi Nitish,

My latest answer from today (Apr 23, 2012 10:00 AM) is here: http://scn.sap.com/message/13196866#13202432

I replied a little bit further up, so you might have missed it.

Thanks!

Regards,

David

[Former Member]

Hi David

Below is the screenshot of scenario i did.....every step triggers new workflow for supplier, may your revision step triggers new workflow which you haven't assigned yet,....

under   

• General Settings->Process Modeling->Create Change Request Type

after assigning workflow, manualy you have to assign agents or role.

Tell me if you got any idea.

Regards

Nitish Sharma

[Former Member]

Hi David

Added to above screenshots...please went through following link.....

http://help.sap.com/saphelp_aii710/helpdata/en/89/4879b23c71449e8b4af0d403d39513/content.htm

[Former Member]

Hi Nitish,

Thanks for your help so far.

1. This is how my concrete change request type looks like:

I think the workflow I'm using doesn't trigger any other (sub)workflows. This is a default pre-delivered change request type with default configuration, I didn't customize it.

What would make sense is (if you have the time and possibility), if you for example would try to reproduce this behavior with the exactly same scenario as my scenario: MDG-F, 0G_W005 as the change request type, WS75700040 as the workflow.

2. Regarding the link: in the configuration they are using this workflow WS75700040, but unfortunately in "step 5. Assign Processors" they are only using the first 2 steps. They don't mention why they don't use step 3 Revision. Also they are not discussing anything about troubleshooting like how to find out if a step is configured correctly or how to proceed if the agent is not assigned to the change request as it happen should per configuration.

Thanks again for all your help.

Regards,

David

[Former Member]

I just noticed the following important Note in the link you sent:

Note

You do not assign a processor to step number 3 (Revision), since the workflow template automatically determines the processor.

I took a look at the Workflow through Workflow Builder (SWDD) and now I understand it a lot more:

In the default configuration for this workflow, the processor assignment for Step 3 Revision is ignored, because directly in the workflow, the change request initiator is always assigned as the current processor for this workflow step.

Regards,

David

[bpawanchand]

Hi David,

Your R & D is 100% correct. In our case we designed a custom workflow and we mapped to our crequest. so that was the reason it was considering the  entries from the table....

SO may be you can try to take a copy of this template and modify the agent determination as it is done for the approval step in the workflow 75700040.

Regards

Pavan

[Former Member]

Now whats your requirement??  

do you want to assign this revision step to some particular agent??

[Former Member]

Hello,

Currently I don't have any specific requirement, no open questions. The problem has been answered.

The problem/requirement was, that the agents assigned to Step 3 Revision were never assigned to the change request. And I didn't know how to find out why they aren't assigned. I wanted them to be assigned. Also I didn't know what to do, to make the agent assignment for Step 3 Revision work the same way as steps 1 and 2 work (in "Assign Processer to Workflow Step Number (Simple Workflow)").

Now I know for sure which step is the step / what needs to be clicked in NWBC in the change request to get to the "Step 3 - Revision".

Now I know, that in case I want to assign some users to the "Step 3 Revise", I need to adjust the used workflow through Workflow Builder where currently the initiator of the workflow is set as the processor.

Also what I wasn't sure about was the question whether there is some kind of connection/relationships between the entries that are/can be defined in "Define Workflow Step Numbers" and the actual workflow which can be modified through Workflow Builder. - YES, they are related, go hand in hand. So it doesn't make sense to only define new steps in the "Define Workflow Step Numbers" configuration screen, if it hasn't been correctly configured also in the actual workflow.

David

[rlm1]

hi David,

am facing the similar issue.i took std material template. initially in the workflow  the workflow log"No processor" i have chaned in the swdd control tab background processing to agent assign ment.

now am getting the current processor as "agent name"

shall i assign for all the steps? while changing am getting binder error...