Hi
Sorry for the long text but I want to explain in detail.
I was asked to make changes to a heavily customized version of the standard SAP FIPP BOR workflow.
Background on current workflow
We initiate/trigger workflow for parked documents using the FIPP.CREATED event and in workflow we manage the monitoring of changes in loops looking for Change events and with a BTE 2214. In the BTE 2214 Z version if a document change is made and the document is saved as Complete (XPRFG = 'X') we fire another FIPP.CHANGE Event to force WF to restart from beginning.
Before I explain the issue I have to point out that all of this (before the latest set of changes in development) is working 100% in production.
Also, work lists are created in UWL and users respond from UWL.
We have 8 approver levels for a parked/completed document. Each level has 2 sub workflows. One for Approval and one for Change/Rejects.
In the Approval subWF the FIPP.RELEASE activity is called with an Approve and Reject outcome.
On a Release/Approve outcome WF is forwarded to the next approval group with it's own sub workflow doing the basically the same thing.
On a Reject outcome WF is forwarded to another sub workflow for this group with a User Decision (TS00008267) and with Change/Reject outcomes.
1. If user selects Reject:
An activity is called using same agent from above FIPP.RELEASE Reject. This activity calls a non background Z Class method which prompts user to enter reason for rejection.
After that it sends WF initiator an email and it sets a flag to restart the workflow process for this parked document from the beginning - first group.
2. If user selects Change:
On user decision WF goes in a Loop Until with a non background activity to FIPP.CHANGE method using same agent.
The loop continues until the FIPP.FLAGCOMPLETED value is set to 'X'.
If everything works the way it should it brings up the document in portal and user can make changes and park document again.
Workflow then continues to next set of approvers.
All of this works in production and worked in development until recent changes.
Problem I need to fix.
What was requested is to update a Z table after or before certain user actions - yes, like a tracker. Standard SAP workflow reports are not user friendly and will not help the intended audience.
To handle the new requirement I wrote a new method in the existing class we use for all other calls in this workflow which is using all the standard workflow interfaces to update the Z table with values passed from workflow. The call works and the table gets updated but what happens now is this:
1. On a Change Decision:
User gets prompted with portal User Decision page to Change or Reject. If user selects Change the document comes up in a page but when the user makes a change to the document and selects Park Document the FIPP.FLAGCOMPLETED value gets reset and the WF stays in the loop and a new 'Change Document' entry is created in the user's worklist.
The only way to get out of this loop is now for user to go to SAPGUI and use FBV2 and make a change. They have to Park and Complete it there before WF can go on and even then it does not always work. Because of BTE change this fire a CHANGED event and WF restarts from the beginning instead of being forwarded to next approver group.
2. On a Reject Decision: User does not see the popup screen anymore to enter the reason but instead a new worklist entry is created. If user clicks on that it creates another worklist entry and removes this one. If user clicks on that then only do you see the popup screen to enter the reason. If user saves then WF restarts the way it should. I must add that if all the approvers in the group only perform a FIPP.RELEASE with no rejects or changes then everything works.
The problem is only with Rejects and changes. Thinking that my recent changes are causing the problems I removed all my tasks/activities that I inserted to update the Z table but I still have this issue.
I have used SWU_OBUF after each change to refresh. Basis has also refreshed UWL cache many times.
Any suggestions will be appreciated.
Naas