Introduction:
blogs.sap.com
In continuation to the earlier blog now the second part is to design workflow for the Business object BUS2081 POSTED Event.
Goto transaction SWDD and follow below steps to design a workflow:
2. Create a step to check the posted document is blocked for payment or not.
3. if invoice is booked with a payment block then set the approval hierarchy level using container operation and fetch for workflow approvers:
4. Create a sequential approval block so that each approver in the list approves the invoice.
Create an activity to display invoice and a decision box to approve or reject invoice.
Create another decision step after exiting block for final approval authority to approve the invoice.
if a user approves the decision then he has to remove the Payment block from Transaction MRBR and the workflow step will end after removing the payment block.
Conclusion:
Whole workflow is now set to trigger once an invoice is posted in system with a payment block flag and after all approvals the invoice will be ready to be cleared from f-53 transaction.
Okumaya devam et...
Building a Payment Block Workflow process for vendor payments | SAP Blogs
Introduction: often there is a requirement from clients to check the outgoing payments to vendor and then proceed with clearing the open invoices. Here is a solution to clients requirement which includes
blogs.sap.com
In continuation to the earlier blog now the second part is to design workflow for the Business object BUS2081 POSTED Event.
Goto transaction SWDD and follow below steps to design a workflow:
- Create a New workflow and set Posted event of BUS2081 as starting event of workflow
2. Create a step to check the posted document is blocked for payment or not.
3. if invoice is booked with a payment block then set the approval hierarchy level using container operation and fetch for workflow approvers:
4. Create a sequential approval block so that each approver in the list approves the invoice.
Create an activity to display invoice and a decision box to approve or reject invoice.
Create another decision step after exiting block for final approval authority to approve the invoice.
if a user approves the decision then he has to remove the Payment block from Transaction MRBR and the workflow step will end after removing the payment block.
Conclusion:
Whole workflow is now set to trigger once an invoice is posted in system with a payment block flag and after all approvals the invoice will be ready to be cleared from f-53 transaction.
Okumaya devam et...