The following (standard) workflows support EBP basic processes:
Workflow for:
Shopping cart (SC)
WS10000060 – Without approval,
WS10000129 – One-step approval,
WS10000031 – Two-step approval
Confirmation (CF)
WS10400010 – Without approval,
WS10400002 – One-step approval,
WS10400009 – Two-step approval,
WS10400020 – Administrator approval
Invoice (IV)
WS10400016 – Without approval,
WS10400017 – One-step approval,
WS10400018 – Two-step approval,
WS10400021 – Administrator approval
Purchase order (PO)
WS14000075 – Without approval,
WS14000089 – One-step approval
WS14000145 – n-step approval
Contract (CTR)
WS14000086 – Without approval,
WS14000088 – One-step approval
Bid
WS79000010 – Without approval,
WS79000002 – One-step approval
New user
WS10000192
New password
WS10000223
New bidder/vendor
WS10000209
Transfer of SC to PM system
WS10000202
Scenario
Approval workflows for shopping carts
The relevant approval workflow is started,
depending on the total value of the shopping
cart and the role of the requester.
Approval workflows for confirmations
The relevant approval workflow is started,
depending on completion status, creator role,
and total value of the confirmation.
Approval workflows for invoices
The relevant approval workflow is started,
depending on completion status, invoice
category (credit memo or invoice), creator role,
and total value of the invoice.
Approval workflows for purchase orders
and change versions of purchase orders
The relevant approval workflow is started,
depending on various attributes of the object
type Purchase Order EC (BUS2201), for
example change of account assignment data,
and total amount difference.
Approval workflows for contracts and
change versions of contracts
The relevant approval workflow is started,
depending on various attributes of the object
type Purchase Contract (BUS2000113), for
example change of conditions.
Approval workflows for bids
The relevant approval workflow is started,
depending on whether a manager or an
employee of the purchasing group accepts a
bid for a bid invitation.
In this workflow, the manager of the new user
created has to approve the new user.
This workflow starts after an EBP user requests
a new password.
This workflow starts when a bidder or vendor
requests a new user for the EBP system.
This workflow causes a SC to be transported
as requirement coverage request to the PM
backend.
(Only for classic scenario!)
HCL Internal
These workflows support further EBP processes or are provided as an alternative to standard
workflows:

Workflow for: Scenario

Spending limit for SC (one-step) One-step approval workflow for shopping
WS10000276 cart (alternative to SC workflows)
The system uses spending and approval limits
to first determine whether approval is
necessary, and then to determine the approver.
Spending limit for SC (n-step, dynamic) Multi-step approval workflow for shopping
WS14000109 cart (alternative to one-step spending limit
WFL)
Step by step approval of SC depending on
spending and approval limit.
Spending limit for SC with BAdI N-step approval workflow for shopping cart
(n-step, dynamic) (alternative to all SC workflows)
WS14000133 Determination of approver occurs dynamically
via a BAdI.
Complete SC Completion of shopping cart by purchaser
WS14000044 Incomplete shopping cart completed by
purchaser before approval.
Purchasing-Budget Workflow (SC) Approval of the SC is not dependent on its
(Workflow scenario) value, but rather on the employee’s
purchasing budget
Vendors from OPI Approval of vendors
WS14000043 – Without approval Relevant approval workflow is started,
WS14000030 – One-step approval depending on processor authorization.

Procurement card Approval of card charges

WS10000093 – First approval
WS10000100 – Second approval
Stochastic Document Check (IV and CF)
The cardholder is responsible for approval
unless the settlement value exceeds the
spending limit set in Customizing. If this is the
case, the manager is responsible for approval.
(For more information, see the IMG: SRM
Server Procurement Card  Process
Procurement Card)
Flexible use of approval workflows for
stochastic document check of invoices and
confirmations

Depending on the document type, its

subtype, and the document value, you can
create your own rules for using certain
specific workflows for random checks of
IV and CF.
For more information, see:
Release Note Changes in SAP Business
Workflow (Enterprise Buyer 4.0), Section

HCL Internal
 Workflow Settings for Stochastic Document
Check

HCL Internal