Scribd
Upload
24 views1 page

1) Vendor Block

1) This document describes two workflows. The first blocks a vendor whenever their master data is changed and requires approval to unblock the vendor or send for data correction. The second triggers when an invoice is parked, sends it to three approvers simultaneously, posts the invoice if two approve, and uses deadline monitoring to remind approvers until the invoice is posted or deleted. 2) Both workflows involve master data changes that require approval. The vendor workflow blocks the vendor during approval and terminates when unblocked. The invoice workflow sends to three approvers simultaneously, posts if two approve, and terminates when the invoice is posted or deleted. 3) The workflows automate approval processes for vendor master data changes and parked invoices

Uploaded by

karthikeyan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
24 views1 page

1) Vendor Block

1) This document describes two workflows. The first blocks a vendor whenever their master data is changed and requires approval to unblock the vendor or send for data correction. The second triggers when an invoice is parked, sends it to three approvers simultaneously, posts the invoice if two approve, and uses deadline monitoring to remind approvers until the invoice is posted or deleted. 2) Both workflows involve master data changes that require approval. The vendor workflow blocks the vendor during approval and terminates when unblocked. The invoice workflow sends to three approvers simultaneously, posts if two approve, and terminates when the invoice is posted or deleted. 3) The workflows automate approval processes for vendor master data changes and parked invoices

Uploaded by

karthikeyan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

1) VENDOR BLOCK

Whenever a vendor master changed, the vendor should be blocked and it should be notified to
the persons in the purchase organizations dealing with the vendor.
To block the Vendor we make use of the transaction (XK05) and to unblock the document we
use the same transaction (XK05).
For the above scenario, we need to build a workflow that will block the corresponding vendor
whenever there is a change in Vendor master.
The Approver can approve the change or send for data correction again.
1) Approve to UNBLOCK the Vendor
2) Reject the Vendor Change and send for data correction
Terminate workflow when the block gets released.

2) PARK DOCUMENT RELEASE


Whenever an invoice (MIRO) is parked, the workflow should be triggered.
Send the document for 3 approvers same time.
If any two approvers approved then post the parked document and inform the approvers.
Use deadline monitoring to send reminder mails to approvers.
The Workflow should terminate until the parked document is posted or deleted.

You might also like