Shopping cart completation

[Former Member]

Hi experts

In SRM 7.0, I have a requirement that is, when a shopping cart is created it must to go to purchaser that will see the requirement and can send shopping cart back to the creator for completation or send it to other user of the organizational plan too, and the shopping cart can go and back several times and when no doubts remain, go to SOCO.

IIs it possible with process controlled workflow?

Some help will be welcome.

Thanks

Nilson

[Former Member · Accepted solution]

http://help.sap.com/saphelp_srm701/helpdata/en/5c/b5a6783fc34466834fbc48def23d2d/frameset.htm

Approval with Completion

The approval process design takes into account that documents are often incomplete and require completion u2013 or at least a document check u2013 by a specialist. This is especially true for shopping carts. In such cases, the process schema provides process levels of the type approval with completion, subsequently called completion levels. If the process schema contains a completion level, it always precedes the approval levels.

For completion levels, the SAP Business Workflow starts template WS40000017 (Completion Subworkflow).

Process

The completion level is triggered if one of the start conditions defined in Customizing applies, for example:

Free text items exist

Items without supplier exist

Items without price exist

Requester of the shopping cart is not a purchaser

The system determines the alternative responsible agents for the document and generates work items that the agents can access in the Universal Worklist (UWL).

Typically, the responsible agent is a purchaser from a specific purchasing department or a category manager responsible for a specific product category.

During the completion level, only decision types 1 and 2 are possible, that is, the document cannot be split into several decision sets. For more information, see Decision Types.

One of the responsible agents accesses and processes the work item, which is then locked for the other users.

During the completion level, the agent can change the document.

If the agent changes the shopping cart, a work item is sent back to the requester. However, to accelerate the process, the agent can also release the document immediately without involving the requester again.

The following table shows the typical actions taken in a completion level and their consequences for the process flow:

Agent

Work Item Type

Action

Consequence

Approver

Decide

Rejects shopping cart

If configured, work item of type adjust sent to requester for acceptance

Rejects at least one but not all shopping cart items

Work item of type adjust sent to requester

Completes and approves shopping cart

Approval process not complete: next process level determined

Approval process complete: if configured, work item of type adjust sent to requester

Changes shopping cart and sends back to requester (Inquire function)

Work item of type adjust sent to requester

Requester

Adjust

Accepts rejection

Shopping cart not released

Accepts partial rejection

Rejected items deleted; next process level determined

Accepts changes

Next process level determined

Makes further changes

Process level restart

Not applicable

Edits shopping cart using POWL

Open work items called back; work item of type revise created for requester

Revise

Changes shopping cart

Complete restart

Note

In general, changes to a document can only be made if the agent has a work item for this document in his or her UWL. Therefore, if a requester wants to make changes to a shopping cart, the system calls back all generated work items and creates a new work item for the requester.

End of the note.

More Information

[Former Member]

http://help.sap.com/saphelp_srm701/helpdata/en/5c/b5a6783fc34466834fbc48def23d2d/frameset.htm

Approval with Completion

The approval process design takes into account that documents are often incomplete and require completion u2013 or at least a document check u2013 by a specialist. This is especially true for shopping carts. In such cases, the process schema provides process levels of the type approval with completion, subsequently called completion levels. If the process schema contains a completion level, it always precedes the approval levels.

For completion levels, the SAP Business Workflow starts template WS40000017 (Completion Subworkflow).

Process

The completion level is triggered if one of the start conditions defined in Customizing applies, for example:

Free text items exist

Items without supplier exist

Items without price exist

Requester of the shopping cart is not a purchaser

The system determines the alternative responsible agents for the document and generates work items that the agents can access in the Universal Worklist (UWL).

Typically, the responsible agent is a purchaser from a specific purchasing department or a category manager responsible for a specific product category.

During the completion level, only decision types 1 and 2 are possible, that is, the document cannot be split into several decision sets. For more information, see Decision Types.

One of the responsible agents accesses and processes the work item, which is then locked for the other users.

During the completion level, the agent can change the document.

If the agent changes the shopping cart, a work item is sent back to the requester. However, to accelerate the process, the agent can also release the document immediately without involving the requester again.

The following table shows the typical actions taken in a completion level and their consequences for the process flow:

Agent

Work Item Type

Action

Consequence

Approver

Decide

Rejects shopping cart

If configured, work item of type adjust sent to requester for acceptance

Rejects at least one but not all shopping cart items

Work item of type adjust sent to requester

Completes and approves shopping cart

Approval process not complete: next process level determined

Approval process complete: if configured, work item of type adjust sent to requester

Changes shopping cart and sends back to requester (Inquire function)

Work item of type adjust sent to requester

Requester

Adjust

Accepts rejection

Shopping cart not released

Accepts partial rejection

Rejected items deleted; next process level determined

Accepts changes

Next process level determined

Makes further changes

Process level restart

Not applicable

Edits shopping cart using POWL

Open work items called back; work item of type revise created for requester

Revise

Changes shopping cart

Complete restart

Note

In general, changes to a document can only be made if the agent has a work item for this document in his or her UWL. Therefore, if a requester wants to make changes to a shopping cart, the system calls back all generated work items and creates a new work item for the requester.

End of the note.

More Information

[former_member697956]

Actually, I have issue - when the user rejected 1 line and approves 2 lines. its going back to the creator. Once the creator accepted - rejected line has been removed and approved line re-routing to the approvers again. It should be auto approve right?

[Former Member]

you can control via any work flow

Requester creates a cart

Buyer can approve the cart

now the BUYER can source the cart in the cockpit.

rule is that shopping cart will be available to cockpit only after approval process only.

Buyer can do only three things

1. buyer create a follow on documents like PO, BI ,contract etc.

2. Buyer can complete the shopping cart item so it can not be procured any more. request become dead

3.Buyer can transfer the shopping cart to another Buyer via redistribution of workload.

[Former Member]

Hi Muthu

A requestor creates a shopping cart and it goes to purchaser completation, purchaser can send back to requestor , after requestor inserts more information the cart goes to purchaser agaim, that can aprove the cart, right?

My doubt is purchaser can start an ad hoc completation workflow to other user?

Thanks

Nilson

[Former Member]

Hello Nilson

SAP rule :- SC created - approval by Business team (manager / purchaser) - then cart goes to cockpit or create a follow on document.

now there are some function called inquire with this facility requester again edit the cart and it goes to approval.

i will study and come back to you on INQUIRE functionality ..

Requester can add adhoc approval if he wants or Approver (Buyer) can forward to his/her boss for approval.

[masa_139]

Please check this.