Scribd
Upload
144 views

Approval Workflows For Documents and Objects

Shopping carts can be set up to require either single-level or multi-level approval workflows depending on their value. Confirmations, invoices, and spending limits typically only require single-level approval. Purchase orders and contracts can be approved upon creation or when change versions are saved, using either no-step or one-step approval workflows depending on the document type.

Uploaded by

raju221756_843567682
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
144 views

Approval Workflows For Documents and Objects

Shopping carts can be set up to require either single-level or multi-level approval workflows depending on their value. Confirmations, invoices, and spending limits typically only require single-level approval. Purchase orders and contracts can be approved upon creation or when change versions are saved, using either no-step or one-step approval workflows depending on the document type.

Uploaded by

raju221756_843567682
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Approval Workflows for Documents and Objects 

 
Shopping Carts With or Without Approval
You can use application-controlled workflows to define whether shopping carts are subject to an
approval procedure in the SAP Supplier Relationship Management (SAP SRM) system, and also
specify the criteria deciding which shopping carts are approved.
 Shopping carts without approval
You can use a workflow that directly assigns shopping carts the status Released in the
following cases:
 The shopping cart contains procurements of low value and is not subject to an
approval procedure.
 The shopping cart is created by a manager.
 Shopping carts with single or multilevel approval
You can specify a single-level approval procedure for shopping carts with low procurement
values, that is, only one superior needs to approve them, and multilevel approval procedures for
procurement transactions with higher procurement values. You use the Customizing settings to
determine who needs to give approval and in what order.
Confirmations and Invoices
The approval process for the confirmation of goods and services and for invoicing is a single-level
process. The workflows can however be modified in such a way to make a multilevel approval
possible.
Spending Limit Approval
This is a single-level workflow.
Approving Purchase Orders and Contracts or Their Change Versions
This approval workflow is used when purchase orders (PO) and contracts (CTR) are created or
changed. So, the workflow deals with the approval of change versions of these two document types.
For more information about change versions, see Processing of Change Versions.
If a PO or a CTR is created or saved, the 'Create' workflow provides the relevant approval procedure.
The result of the (positive) approval is the ordered PO or released CTR. If the change version of a PO
or a CTR is saved, the 'Change' workflow provides the respective approval procedure. The (positive)
result of this is the release of the change version and the transfer of the changed data to the active
document. 'Create' and 'Change' workflows use identical workflow templates:

Document Type Workflow Template

Purchase orders No-step approval WS14000075


One-step approval WS14000089

Contract No-step approval WS14000086


One-step approval WS14000088

Differences do exist, however, in the start conditions. The 'Create' workflow reacts to the BOR
event Saved and the 'Change' workflow reacts to the event ChangeVersionSaved. (The BOR objects
for PO and CTR contain attributes that are only really worth evaluating in the change case, for
example TotalValueIncreased and TechnicalListOfChanges.)
Differences also exist when you branch from the Universal Worklist (UWL): In the 'Create' case, the
approver sees and checks the original document (in the 'Change' case, the change version).

You might also like