SAP SD For Dummies

Mickael QUESNOT © https://s4hclub.
com/
http://www.youtube.com/user/MrSharesap
SAP SD For Dummies

Flexible Sales Workflow in SAP S/4 HANA
Flexible Workflow is a powerful feature in SAP S/4 HANA that allows you to streamline and customize
your sales processes. Here's a breakdown of its key aspects:
**What it is:**
* Introduced in SAP S/4HANA 1809, it simplifies workflow creation for various sales documents like
quotations, credit memo requests, and (since 1909) sales orders.
* It's part of the broader SAP Business Workflow functionality used across departments in S/4HANA.
**Benefits:**
* **Flexibility and Agility:** You can design workflows that precisely match your specific sales
approval processes.
* **Simplified Setup:** Compared to traditional workflow tools, it offers a user-friendly interface for
creating and managing workflows without extensive coding.
* **Improved Efficiency:** Automates tasks and approvals, reducing manual work and speeding up
sales cycles.
* **Enhanced Collaboration:** Ensures clear handoffs between sales reps, approvers, and other
stakeholders.
**How it Works:**
* You define scenarios based on conditions, such as order value or customer type.
* When a sales document triggers a scenario, the system automatically routes it to designated
approvers based on pre-defined rules.
* Approvers receive notifications and can take actions (approve, reject, etc.) within the workflow.
Here's a step-by-step guide to creating a Flexible Sales Workflow in SAP S/4 HANA:
**Prerequisites:**
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
1
Mickael QUESNOT © https://s4hclub.com/
* You'll need the necessary permissions, typically assigned through roles like SAP_BR_BPC_EXPERT.
* Teams and approvers should be defined in the "Manage Teams and Responsibilities" app.
**Steps:**
1. **Define Relevancy for Approval (BAdI Implementation):**
- Go to SPRO > Settings for Business Workflow > Business Workflow Definition > Basic Settings >
Enhancement Implementations.
- Search for the Business Add-In (BAdI) named "WF_ sordoc_req_reason" (for Sales Orders). There
might be similar BAdIs for other sales documents.
- Click "Create" and provide an implementation ID and description.
- Within the implementation, define logic to determine the "Reason for Approval" based on your
criteria (e.g., sales order value, customer type). This reason will trigger the workflow.
2. **Define Teams and Responsibilities:**
- Launch the "Manage Teams and Responsibilities" app.

- Choose "Category: Sales" and create a new team with a name and description.
- Assign relevant team members as approvers, specifying their function (e.g., first-level, second-
level).
3. **Set Up Flexible Workflow for Sales:**
- Go to the "Manage Sales Document Workflow" app.

- Select the appropriate document type (e.g., Workflow for Sales Order).
- Click "Create" to create a new workflow.
- Enter a workflow name, description, and validity period.
4. **Define Conditions:**
2
- In the "Start Conditions" tab, define the criteria for triggering the workflow.
- Use the "Reason for Approval" determined in step 1 or other conditions like sales order value or
customer attributes.
5. **Add Recipients (Approvers):**
- In the "Step Sequence" tab, define workflow steps.

- For each step, choose "Release of Document" and then select the team (or specific users) from
step 2 as recipients who will approve/reject the document.
6. **Define Rework Cases (Optional):**
- Specify actions users can take if a document is rejected (e.g., revise and resubmit).
7. **Save and Activate the Workflow:**
- Once you've configured all steps, save and activate the workflow.
Remember, this is a simplified overview, and the specific configuration might vary depending on your
S/4 HANA version and desired workflow complexity.
1.1.1 Define Reasons for Approval Requests

Short text
Define reasons that are displayed in sales documents or preliminary billing documents to let the
business user know why these documents need to be approved.
Note that to be able to make use of preliminary billing documents, a configuration expert must have
activated the business function Functionality for Preliminary Billing
Documents (SD_BIL_PRELIMBILLINGDOC) in Customizing activity Activate Business Functions.
Use
You must define at least one reason for approval requests to set up the approval workflow for sales
documents or preliminary billing documents.
3
For sales documents, the following applies:
• If a sales document meets the conditions that are defined in the BAdI Set Approval Request
Reasons for Sales Documents and in the approval workflow, the relevant reason is displayed
in the sales document.
• In case you want to use the approval workflow of an external system, you can indicate this for
one or more approval request reasons. The BAdI determines in which cases a reason is valid.
• In case you do not want the system to automatically create a purchase requisition as long as
the sales document is in approval, you can indicate this for one or more approval request
reasons. Once the sales document is approved, the purchase requisition is created.
• Afterwards, assign your reasons to sales document categories in the Assign Reasons for
Approval Requests Customizing activity.
For preliminary billing documents, the following applies:
• If a preliminary billing document meets the conditions that are defined in the BAdI Set
Approval Request Reasons for Preliminary Billing Documents and in the approval workflow,
the relevant reason is displayed in the preliminary billing document.
• For preliminary billing documents, you cannot use the approval workflow of an external
system.
• Afterwards, assign your reasons to the preliminary billing document (PBD) category in
the Assign Reasons for Approval Requests Customizing activity.
Example
You define the reason Customer 1 always needs to be approved. In the BAdI and the workflow, you set
up the corresponding conditions. Once a business user creates a sales document for customer 1, the
system automatically displays this reason in the sales document and triggers the approval workflow.
4
5
6
1.1.2 Assign Reasons for Approval Requests

Short text
7
Assign the approval request reasons that you have defined to document categories.
Use
Once you have defined approval request reasons, you specify which documents these reasons are
valid for by assigning them to one or more document categories.
• If a sales document meets the conditions that are defined in the BAdI Set Approval Request
Reasons for Sales Documents, the relevant reason is displayed in the sales document.
In case you want to use the approval workflow of an external system, you can indicate this for
one or more combinations of sales document categories and approval request reasons.
• If a preliminary billing document (PBD) meets the conditions that are defined in the BAdI Set
Approval Request Reasons for Preliminary Billing Documents, the relevant reason is displayed
in the preliminary billing document. Note that to be able to make use of preliminary billing
documents, a configuration expert must have activated the business function Functionality
for Preliminary Billing Documents (SD_BIL_PRELIMBILLINGDOC) in Customizing
activity Activate Business Functions.
Requirements
You have defined approval request reasons in the Define Reasons for Approval Requests Customizing
activity.
Example
You have defined the reason Customer 1 always needs to be approved. However, you don't want to
apply this rule to all sales documents, so you only assign this reason to document category K (credit
memo request). In the BAdI and the workflow, you set up the corresponding conditions. Once a
business user creates a credit memo request for customer 1, the system automatically displays this
reason in the sales document and triggers the approval workflow. For any other sales document that
a business user creates for customer 1, the workflow isn't triggered.
8
9
10
11
12
13
14
*Workflow retours articles

IF salesdocument-sddocumentcategory = 'H' AND
salesdocument-salesdocumenttype = 'ZH02' AND
salesdocument-salesorganization = '1032'.
salesdocapprovalreason = 'ZH02'.
RETURN.
ENDIF.
*Workflow matériel de prêt

IF salesdocument-sddocumentcategory = 'C' AND
salesdocument-salesdocumenttype = 'ZC04' AND
salesdocument-salesorganization = '1032'.
salesdocapprovalreason = 'ZC04'.
RETURN.
ENDIF.
**Workflow de validation pour l’annulation d’une commande

**All sales orders with a reason for rejection shall trigger a workflow by setting approval request
reason ZC02.
LOOP AT salesdocumentitem INTO DATA(ls_salesdocumentitem)

WHERE salesdocumentrjcnreason <> ' '.
ENDLOOP.
IF salesdocument-sddocumentcategory = 'C' AND

salesdocument-salesorganization = '1032' AND
salesdocument-salesdocumenttype = 'ZC02' AND
ls_salesdocumentitem-salesdocumentrjcnreason <> ' '.
salesdocapprovalreason = 'ZC02'.
RETURN.
ENDIF.
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
REsult
40
41
42
43
44
45
46
47
48
49
50
51

SAP SD For Dummies

Uploaded by

Copyright:

Available Formats

You might also like

SAP SD For Dummies

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP SD For Dummies

Uploaded by

Copyright:

Available Formats

Mickael QUESNOT © https://s4hclub.

SAP SD For Dummies

1. **Define Relevancy for Approval (BAdI Implementation):**

2. **Define Teams and Responsibilities:**

- Launch the "Manage Teams and Responsibilities" app.

3. **Set Up Flexible Workflow for Sales:**

- Go to the "Manage Sales Document Workflow" app.

Mickaël QUESNOT © - Copyright

5. **Add Recipients (Approvers):**

- In the "Step Sequence" tab, define workflow steps.

6. **Define Rework Cases (Optional):**

7. **Save and Activate the Workflow:**

1.1.1 Define Reasons for Approval Requests

For sales documents, the following applies:

For preliminary billing documents, the following applies:

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

1.1.2 Assign Reasons for Approval Requests

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

*Workflow retours articles

*Workflow matériel de prêt

**Workflow de validation pour l’annulation d’une commande

LOOP AT salesdocumentitem INTO DATA(ls_salesdocumentitem)

IF salesdocument-sddocumentcategory = 'C' AND

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

1. Define Relevancy for Approval (BAdI Implementation):

2. Define Teams and Responsibilities:

3. Set Up Flexible Workflow for Sales:

5. Add Recipients (Approvers):

6. Define Rework Cases (Optional):

7. Save and Activate the Workflow: