MXL - SD - WF Approval Specifications

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 10

Functional Requirement

SAP S/4HANA - 21-12-2022

Workflow Approval Process – Sales Documents

Table of Contents

1 Master Data, Organizational Data, and Other Data

2 Business Case

3 Functional Requirements with Specifications


1 Master Data, Organizational Data, and Other Data

The organizational structure and master data of your company has been created in your system during activation. The organizational structure reflects the structure of your company. The master data
represents materials, customers, and vendors, for example, depending on the operational focus of your company.

Data Sample Details Comments


Value
Customer 17100003

Material FG29

Company Code 1710

Sales organization 1710

Distribution channel 10

Division 00

Quotation Document Type ZQT

FIORI APP 1 F1852 STAND- Manage Sales Quotation


ARD

FIORI APP 2 ZF2097 CUSTOM My Inbox for Approval

Refr.- IBO_WDA_INBOX (EHPRC_INBOX) for


Reference
F0862 – My Inbox (TCODE – SBWP)

Procedure

Test Step Test Step Instruction Expected Result Pass / Fail / Comment
# Name
1 Log On Log on to the SAP S4 GUI On Premise ver- The SAP S4 Logistics screen is dis-
sion played

2 FIORI APP 1 F1852 STANDARD Manage Sales Quotation

3 FIORI APP 2 ZF2097 CUSTOM My Inbox for Approval


Test Step Test Step Instruction Expected Result Pass / Fail / Comment
# Name
4

8
2 Business Case

This section describes the business case for creating a sales quotation by sales representative and submitting for price approvals after doing the price estimation. Once the decision is taken by respec-
tive stake holders, based on that, sales rep. will either convert this quotation into sales order or keep as rejected and inform to the customer.
3 Functional Requirements with Specifications

Approval table for decision making by Business Stakeholders.

General Logic :
 Sales Person will submit the Quotation with Mandatory comment ‘ WF Approval Comments’.
 Approval to start always from level 1 , IF approved then pass to next level of approver withstatus update at Quotation as ‘APV’ if exists in decision table.
 IF Approvers not maintained for any level, check for next level and pass the Work Item for decision making./ Table level validations required for unfilled/partial filled field level values.

 Logic to be implemented on Net Value validation for decision making.


 IF more that Approver 1 limit, then workitem should not be created and the status to be set as ‘APV’ for AUTO Approval.
 Except status 'INI / APV' system should not allow to do any changes in sales document, need to put the enhancement for Quotation document.
 Interval cases – if there is a gap between the Net Value of Two approvers, for above example, Appover 1 – 1000 and Approver 2 – 900, quotation value = 950, it must be auto approved af-
ter previous level approval.
 if only 1 / partial approvers exists--- only those many work items to be created for validations.
 if table entries are not there with any approver(s)—send for direct AUTO Approval and set the Quotation status as ‘APV’.
 Text Object for Comments to be filled up/ updated under Quotation Text Object - ZWF1 – WF Approval Comments. It also should print the approver name and time stamp.
e-Mail Logic :
 Once work items are submitted, e-mail should go to the sales rep and the approver based on the mail id mentioned under user profile (T.CODE-SU01).
 if approver accepts/rejects, mail to be sent to sales rep and approver
 for Acceptance, move WF to next level
 for Rejections - pull the list of rejection codes and show to select by approver, no comments are required to be entered by approver but we can enter ‘Reject’ under Quotation text obj
ZWF1.
 Once Rejected, Sales Rep to negotiate and if customer agrees with new terms then set the status as ‘INI’ and do changes, then re-submit for approval with status ‘SUB’ to trigger the new
work item.
e-Mail Contents :
 HI, Please find the quotation details for your approval,
 QTN # - print dynamically.
 CUST # print dynamically.
 CUST NAME - print dynamically
 QTN VALUE - print dynamically
 Comments for decision - print dynamically, show previous comments of approvers if exists.
Approver Screen Contents :
 HI, Please find the quotation details for your approval,
 QTN # - show dynamically with Link (VA22/23).
 CUST # show dynamically
 CUST NAME - show dynamically
 QTN VALUE - show dynamically
 Attachments – show attached quotation documents with link.
 Comments for decision - print dynamically, show previous comments of approvers if exists.
Technical Details :
Tables VBAK - OBJNR
Pass OBJNR - JEST
TJ30 – Status Profile
TCODES
SWO1 - Business Object -BUS2031
TEXT Object - ZWF1
Test Data – Quotation – 20001943 (VA22/23)

Sample Design Templete :


My Work Overview App ID - IBO_WDA_INBOX (EHPRC_INBOX) for Reference
App ID- F0862 – My Inbox (TCODE – SBWP)
Overview Screen
 All the existing available functionalities to be available with improvements wherever required.
 All work items as per person's authorization to be listed for decision making
 Upon selection of items, system should show the high level Overview Information

DETAIL

 Detailed screen will open up once user double click on the work item/click on 'Detail Button' option.
Customer No with link and Name
Quotation NO with Display Link
Quotation Value
C.Code/Sales Area
Sales Rep's / Approver's Comment with Time Stamp
Right side show the link for any attached documents

All decision Buttons must be available as per standard FIORI offerings.


APPROVE Button - Mandatory Text box to be provided for approver if 'Approve' Button is Clicked.

Approver Comment.... approved as per the attached


supporting documents.

REJECT Button – Comments are not required but the two digit rejection codes to be provided as selection option.

You might also like