Skip to Content
author's profile photo Former Member
Former Member

PARKED DOCUMENT

I tried to reject a parked document in FBV6. When I click on the green check I find myself in FV53 with a message "Document not relevant for release". That screen has a reject box and when I click on that box I go back to FBV6. What am I missing. WHy am I not able to reject teh parked doc. It was parked via t. code FV50.

Please help

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Nov 29, 2007 at 10:24 PM

    Dear Lakshmi,

    The release and refuse functions are used as additional Workflow

    functions. Someone creates a parked document and a person who is

    authorized for that receives a mail in his inbox and can decide

    whether the document is released (posted) or refused (not posted).

    If you already posted your parked document an option might be a reversal

    Please be noted that FBV6 is used to reject documents previously

    approved.

    If you didn't activate the workflow function and just want

    to refuse documents that haven't been approved,please go to transaction

    FBV0 and select menu path 'Document' ->'Delete'

    Also, please, verify the instructions of the SAP Note 323907.

    Regards

    Paulo EVaristo

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Lakshmi,

      Regarding the workflow, please, look the transactions below:

      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.

      For more information, please check the documentation from SAP help online in the link:

      http://www.saptechnical.com/Tutorials/Workflow/Workflow.htm

      Regards

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.