Professional Documents
Culture Documents
Manage WFL Guide
Manage WFL Guide
1. Workflow .........................................................................................................................................4
4. Pre-Requisite.................................................................................................................................. 7
5. Limitation ....................................................................................................................................... 7
Start conditions - The workflow will start only when the start condition specified in it is
met.
Agent determination rules – These rules are used to identify an approver for a workflow.
Activities - Activities are tasks that are used to perform functions such as approve or
reject.
2. Overall Release
You can configure document type, net amount, creation indicator, and company code as a start
condition for the overall release of a purchase requisition. For example, a workflow will start only
if the net amount of a purchase requisition (PR) is greater than a certain value.
Note
If a company code is used as a start condition, then the company code assigned to a user via
Default settings for user app is considered rather than the one assigned to the purchase
requisition items. In case, no default company code is assigned to the user, the company code of
the first item in the purchase requisition is considered.
For Manage Purchase Requisitions – Professional app, only Badi Agent Determination rule is
supported.
Overall release of a purchase requisition will create a work item for an agent depending on the
agent rule that is specified in the Manage Workflow for Purchase Requisitions app.
The agent can either approve or reject this work item or forward it to other agents.
Automatic release of PR will approve the PR in the background and release it.
Note
If none of the start conditions specified in the active workflows are met, then the PR will be
automatically approved in the background.
You can configure plant, purchasing group, material group, accounting type, creation indicator,
and catalog ID as a start condition for the item level release. For example, a workflow will start
only if a plant specified in the start conditions is used in a purchase requisition.
Note
Start condition ‘accounting type of purchase requisition item is equal to’ is supported only for the
following accounting types:
If a user chooses this start condition, then either of these four accounting object types should be
maintained. In SAP S/4HANA 1705 release, only these four categories are supported.
Note
1. For Manage Purchase Requisitions- Professional app, only accounting object responsible and
BADI agent determination rules are supported. In case of the accounting object responsible
agent rule, one of the start conditions should be ‘accounting type of purchase requisition item
is equal to’.
2. Accounting object responsible agent rule is based on the account assignment category used
in a purchase requisition. For example, if the account assignment category used in a purchase
requisition is ‘K’ then the person responsible for the cost center mentioned in the PR is
assigned as an approver. For the other account assignment categories, manager of workflow
initiator is assigned as an approver.
3. BADI Agent determination is based on the implementation of the BADI
MMPUR_WORKFLOW_AGENTS. Default implementation CL_EXMPL_WORKFLOW_AGENTS
implementation is available.
To use the accounting object responsible agent rule, follow the steps below:
1. Create a cost center and assign ‘User Responsible’ for the cost center. If you are using an
existing cost center, then ensure that the cost center has user responsible assigned to it.
2. The user responsible for the cost center should have SAP_BR_MANAGER’ and
‘SAP_BR_EMPLOYEE_PROCUREMENT’ roles.
3. A workflow with recipient as ‘Accounting Object Responsible’ should be active.
If a PR uses the cost center created or modified in step 1, then it will go for approval to the cost center
responsible.
Release requisition item will create a work item for an agent depending on the agent rule that is
specified in the Manage Workflow for Purchase Requisitions app.
Automatic release for PR Item will approve PR in the background and release it.
Note
If none of the pre-conditions specified in active workflows are met, then the PR will be
automatically approved in background.
4. Pre-Requisite
1. The approval or rejection of a purchase requisition is done via My Inbox app.
2. The approver needs to have sap_br_manager role to approve or reject purchase requisitions.
3. Flexible workflow will be triggered only if the flag ‘scenario based workflow’ is selected under
the customizing Materials Management -> Purchasing -> Purchase Requisition > Define
Document Types. Overall release of a purchase requisition should be selected to execute
header level Approval.
4. Manage workflows for purchase requisition app can be accessed by users with the roles
‘sap_br_bpc_expert’ or role ‘sap_br_administrator’.
5. Limitation
The restart of the workflow is not supported for SAP S/4HANA 1705 release. Any changes done to
the PR after approval will not result in restart of the workflow.
For more information on Manage Workflow for Purchase Requisitions app, please refer to following
documentation:
http://help.sap.com/saphelp_nw751abap/helpdata/en/de/3df3c499124cea9e3078cc9317b47c/content.htm?f
rameset=/en/b3/69e10d33664f0a9896e8d119620f64/frameset.htm¤t_toc=/en/b3/69e10d33664f0a9
896e8d119620f64/plain.htm&node_id=43