Approval requesters can monitor the approval process for prices in the Manage Prices – Sales app.
After you submit a price for approval, you can view its approval details in the corresponding condition record. You can track real-time progress and see assigned approvers and their comments in each approval step. You also have the option to see how the approval workflow is defined, ensuring clarity and transparency throughout the process.
This component enhances the functionality of the Object Page by embedding a workflow instance viewer, enabling users to seamlessly interact with workflow-related data directly within the application.
Users are able to check detail information of the workflow process:
Before we start using enhanced workflow functionalities in Manage Prices - Sales app, we have to know how to do the pre-configurations: Configuration for workflow in Prices, the contents in this blog will only show you the configured results and how the UI displays the workflow instance data.
The workflow section is dynamic visibility, only visible when below specific conditions are fulfilled:
Scenario1:
Created a workflow process for only one of the approvers shall do action on the approval request, start condition is condition type is ZPR1
Other configuration parameters:
Create a new condition record for ZPR1 and submit for approval. E.g. it is 0000092575
Any user could go to the object page of this data (0000092575), and since it has workflow process now, we could see a new section names "Approval Workflow". Display column there means:
Click the item will go to its object page to see the detail information for this workflow process.
User can click "Show Definition Data" to see the brief definition for this workflow. The detail information will be expanded directly in the same page.
Once approver log on the Fiori Launch Pad, will see the price approve request in to-dos cards, or can open APP "My-Inbox" to see all approve request.
If approver clicks "Reject", a dialog for decision note (reject reason) will pop up, input decision note there and click "Submit".
Since ZPR1 is in workflow for 1 recipient, the process will be finished. If we back to the data object page, it shows status as "Rejected (with note)".
Click the item to enter the step detail page of this workflow process, we could see the "reject reason" in the column "Note".
Scenario2:
Created a workflow process for all users shall do action on the approval request, start condition is condition type is ZNEO, other configured parameters:
Create a new condition record for ZNEO and submit for approval. E.g. it is 0000092578
Any user could go to the object page of this data (0000092578), and since it has workflow process now, we could see a new section names "Approval Workflow". Display columns there have the same meaning which be explained in above contents.
Once approver log on the Fiori Launch Pad, will see the price approve request in to-dos cards, or can open APP "My-Inbox" to see all approve request.
If approver clicks "Approve", a dialog for decision note (approve reason) will pop up, input decision note there and click "Submit".
Since ZNEO is in workflow for all recipients, the process will not be finished unless below condition be fulfilled:
If we back to the data object page, it shows status with a process bar (e.g. 50% there with note).
Click the item there will go to its workflow step detail page and see the detail reason/time regarding user approved/rejected the workflow request there.
Unless all recipients approve the workflow request, the status will change to 100% and all approve reasons will be shown in the object page of the workflow step item of this data.
In addition, let's see a scenario for "completion by all recipients" but one of the processors rejects the workflow request. Same at the beginning, let's create a condition record:
If we go to its object page, we will see the status is 0%.
Status of all processors are "Ready".
Let's use processor "Daisuke" to reject the workflow with specified reason.
Back to the object page of this condition record, even only one user rejected the workflow, the whole workflow finished, and status changes to "Rejected" (with note).
We could check the reject reason there and also the status of other process(s) changed to "Cancelled".
Scenario3:
Similar to Scenario1, difference is to use role as approver instead of user.
Scenario4:
Similar to Scenario2, difference is to use role as approver instead of user.
Workflow in “Manage Prices – Sales” APP - SAP Community
Workflow Configuration for SAP S/4HANA Sales Price - SAP Community
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
5 | |
4 | |
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
2 |