Skip to Content
author's profile photo
Former Member

Activation of workflow for Non PO invoices in FI

Hi Everone there

Please advise on the customizing settings to activate workflow for Non PO invoices with example in FI

Thanks and I will not forget to reward.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Posted on Sep 13, 2007 at 01:30 PM


    follow the below steps:

    1. OBWA - create workflow variant. Make sure you have activated prelminiary posting (= parking) and/or payment release. Subworkflow WS10000051 is delivered for releasing parked documents, I would recommend to use that for the start.

    2. OBWJ Assign your workflow variant from step 1 to your company code(s).

    3. SM30, V_VBWF08 Release groups - feel free to adjust, standard entries are OK for first tests, no need to change. Do not forget to maintain the vendor master on company code level - you have to enter an approval group (field LFB1-FRGRP, if this is not visible in FK02, check your field status control for the vendor master).

    4. SM30, V_VBWF03, Approval paths, again, no need to change the standard entries for the first tests. You can maintain later if you like.

    5. SM30, V_VBWF05 Assign approval paths. This is important, assign approval paths to workflow variant (step 1) and document types.

    6. OBWE - Subworkflow allocation. This is also essential. Specify release levels (0 to 3) and subworkflow (use F1 help to see a list of standard workflows by release level, use those) by workflow variant, approval path and amount/currency. To make it easy, start with a 1-level approval first. Otherwise, the higher the amount the more release levels makes sense.

    7. OBWF Assign users. Here you cna specify who should release the parked documents. Enter workflow variant, Approval path, release level and amount (limit) first. Then select the entry and click Details (org object). Here you can assign organizational objects (not users directly). Also you can create organizational objects from here.

    But it is better to use transactions PPOCE (create) and PPOME (change) to maintain organizational units. You can create an organizational unit Zxxx first then create some new Positions and assign the positions to the org,unit. You can then assign users to the positions. Finally, you can go back to OBWF and assign the positions there.

    After all of those steps, when you have parked a document and marked it as complete, a new workitem will come up in the business workplace of the assigned users. They have to execute the workitem, which ends up in a similar screen like FBV0, but they got there 2 buttons (Release / Reject) which they can use. In case of an approval, document can be posted. In case of a rejection, the creator of the document will receive a workitem (pls. change doc xxxxxx) and it starts then from the beginning.

    Some additional info: after you have parked a document, check the following fields in the document header:

    Release necessary: it has to be ON, meaning document is relevant for releasing.

    Doc. complete: obvious, ON is saved as complete

    Approval path / Release levels: as customized, should not be initial in order to get the workflow running.

    Released: obvious, after release, it becomes active.

    Hope that helps, points welcome 😊


    Add comment
    10|10000 characters needed characters exceeded

    • 😊))

      approval path and release levels are fields in the parked document header. If those are initial, your workflow won't work. Check the assignments again (doc type, etc.)

      Released is another checkbox in the doc.header. At first, it is initial, after the approval, not very surprisingly, it will become active (X, checked).

      Hope that helps, points welcome 😊