JVs Completed and Released but not Posted
(see Stuck JVs)

Step TS00008142 (Post parked document FIPP method POST) does not successfully post the document. Most common reason is that the posting period is not open:

not posted container

Our current workflow does not catch this error and ends successfully leaving the document completed and released but not posted. We have a report, transaction ZJVSTAT, that reports on these problem JVs but this still means the JV has to be deleted and new one created.

Proposed solution:

Part 1 - Change Workflow (see implementation documentation)

  1. Change workflow to detect the fact that the POST was not successful
  2. Reset the MIT custom fields - the approval workstation indicators on VBKPF:
    VBKPF approval workstation indicators
  3. Reset the workflow release indicator:
    release indicator from header
  4. Notify the creator, CAO and the workflow administrators that the document was not posted:
    proposed email
  5. Either cancel the workflow or throw an exception

This will allow someone to go into the document, correct the problem, contact the workflow administrators and have them restart the workflow, causing the document to re-enter workflow and ultimately post.

Part 2 - Change the Approval Step

Change the Approval Step (TS91000006 TS90500043) method JV_Approval_Step) such that a document with a posting period that is closed (the most common posting problem) can not be released

Old document in workflow inbox:

old document in inbox

Execute the workflow step:

old jv - before attempt to release

Attempt to "Complete and Release" it and you are thrown back into the inbox with the error message:

error message about closed period