chaging description by the approver causes worng behaviour of workflow

[Former Member]

Hello,

When approver makes changes to the SC "descritption" of SC and approves the SC is routed back to requistioner for accept/reject changes as well as appear in inbox the first approver for his approval.

Error reporoduction

Create a SC, single item, non-catalog,via “Describe requirement” functionality.

The SC is sent to the first approver determined, for approval.

The approver makes changes to ‘Description’ of SC and saves the changes(i.e. saving is equivalent to approve here)

The SC is routed back to requisitioner as well as seen in the first approver inbox for approval agian.

As per the normal flow if the item are rejected the workflow goes to requistioner for approve/reject changes only(as the value of the SC changes), but here changing the desc causes the undesired bahaviour.

I am using WS14000133 workflow(n step dynamic workflow).

please advice

regards

Sachin

[Former Member · Accepted solution]

Hello,

I don't understand what has security level of the workflow got to do with the issue?

But still can you please let me know as how to set the security level of the workflow?

The approver when rejects one of the line items straight away, without making any changes, the workflow routes back to the requisitioner for accept changes or withdraw the SC. In this case the workflow works fine.

But when the same approver goes and changes the line item say desc or the

G/L account the workflow routes to the requaisitoner for approval fo the cahnegs as well as appear in the inbox of the first approver

In both the cases the approver is the same , hence the security level could not be the reason.

Do you think that the changes to the worflow items ( as in desc. changes or G/l chages) needs to be handled by the BADI ? Directly appoval or rejection of the line items are handled by the standard SAP code, hance no issues occur here.

The Workflow is WS14000133.

Regards

SAchin

[khan_voyalpadusman · Accepted solution]

Hi,

There is still difference between the two cases , one case you are not making change and in the second case you are making the change.

Only difference i can see between the two cases is the restart of the workflow. ANd restart only depends on the security level of the user.

when the approver changes the shopping cart , the restart of the workflow happens .

when the approver makes no changes , the restart does not happen.

Please let me know of what you see in the workflow log for the two cases of shopping carts?

1. start SWI6

2. Enter the shopping cart in object id , object type BUS2121.

3. Enter all for the remaining options , and press F8

How many entries do you see in the result?

And security level of the user can be found in transaction 'SU01' , personalization tab .

[Former Member · Accepted solution]

Hello,

Here are the observatiosn regarding the workflows, for 2 Shopping carts.

1. SC Approval N-step sarted : In Process

2. subworkflow for n-level sshopping cart : In process

3. Determine next approver : Completed

4. Approve SC : Ready state(Work item)

In ready state the worktitem is with the approver

I did like to share other inforamtion that as the contents of the SC have changed the technial logs show as the worklfow as being started by the approver as opposed to the requistioner. This are just additional details. I think it shouldnot be be a problem

N.B Both the SC , had thier values changed

Regards

Sachin

[Former Member · Accepted solution]

Hello

Sorry for the ealier post.

I will send you the observations regarding 2 case

1. When the SC is changed by approver

2. When the SC is rejected

Regards

Sachin

[Former Member · Accepted solution]

Hello

Here are the observations

case 1 SC is changed

1. SC Approval N-step sarted : In Process

2. subworkflow for n-level sshopping cart : In process

3. Determine next approver : Completed

4. Approve SC : Ready state(Work item)

The worktiem is in pending with the approver(not requistioner)

Case 2 SC is rejected

1. SC Approval N-step sarted : In Process

2. subworkflow for n-level sshopping cart : completed

3. Determine next approver : Completed

4. Approve SC : completed by the approver

5. Determine next approver : Completed

6 Update SC after approval : In process

7 Subworkflow to send email : completed

8 read language dependent texts : completed

9 SC has been rejeceted, please edit it : Ready state( Work item ) with requisitoner

Please let me know in case of other inputs

Regards

Sachin

[Former Member · Accepted solution]

SRM 4.0

setting the personalization object key : BBP_WFL_SECURITY(in personalization tab) in the SU01 data determines the restart of the WFL

i.e making the changes to SC by approver will restart the WFL by him or not.

The standard functionality approve and reject , works the same.

[Former Member]

HI Sachin,

Please maintain the security level for the workflow. Any changed to workflow may cause a restart if the security level is set to low..as

Regards

Rakesh

[khan_voyalpadusman]

Hi,

Can you please check in the workflow log , how many workflows are available dor the shopping cart.

1.you can find the workflow log using transaction SWi6.

2 looks like the workflow restart happens in your case , please check the security level of the approver who changes the shopping cart.