Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Workflow Variants

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 3

There may be times when you want to release a payment that has been blocked, once released you

can then pay for that line item. You will need to configure the workflow variant with the document types for payment release, the level at which the release happens and who can release the payment and up to what amount. we will use transaction OBWA,

workflow var - this is a identifier currency - self explaining wf var.name - self explaining posting release - select this if you want a mandatory posting release before a posting a document release from - this indicates the amount beyond which you want the release activated subworkflow - we selected the SAP supplied WS10000055 release pmnts - this is used to impose a payment release before a payment can be made creator permitted - don't select this if you want to prevent the documents creator from releasing the payment this way you can impose dual control payt release - enter the amount beyond which you will require a payment release pmnt rel.ver - select the appropriate line item variant, in this case DD - posting key, account, business area, name, tax, etc

Now we can assign the above variant/s to the company codes using transaction OBWJ,

Next we will define release approval groups for release of payment, we need to create approval group first using transaction code OBWB,

Since the system determines the subflow based on the release approval path and the amount we now need to define the release approval path, using transaction code OBWC,

Next we tie everything together, the approval groups, release approval paths, workflow variant, document type using transaction code OBWD,

We now need to to assign the above procedures (for amount and payment release) for each combination of workflow variant, release approval path, currency and amount, we will use transaction code OBWE,

wrkf - the workflow payment release apth - the release approval path

amount to - the amount on which the specific release approval procedure will be triggered crcy - this is default by the system, which is the currency of the workflow variant rel levels - the system determines the number of release levels and saves them in the parked document swf amnt rel - the amount release for parked/posted documents is executed via a sub-workflow template, select a workflow template that has already been predefined for this purpose for parked documents: WS10000052 (for single level release), WS10000053 (for two level release) or WS10000054 (three level release), if not amount release is required you may enter a blank workflow template (WS2000006) you can use similar sub-workflow templates for posted documents (WS00400011, WS00400021 or WS00400022) swf pmnt rel - this is the same as above but for payment release

You can also define relevant document types for release of payment using transaction code OBWQ, I will leave you to invest this option. The authorization is in the form of an organizational object (business unit a user is attached to or the position of an individual in the organization) that will then be assigned to the release approval step. We will use transaction OBWP, the currency will be completed by the system. If you highlight an entry and then select goto -> details (org object) you can then add the organizational group or type of role as you can see in the right hand screenshot

You might also like