Strange Behavior of Decision Work Item

[Sue Doughty]

We have solved the issue with the Decision Work Item:

ENVIRONMENT:
We have a Z* business object that calls a screen in a large Z* function pool.  The object method used CALL FUNCTION to enter the pool and inside that function the CALL SCREEN arises.  This approach was erratic.  The method was changed to do a SUBMIT AND RETURN, which appears to be stable.  This required writing a very simple REPORT that accepted parameters and passed them to the same Z* function module.  By SUBMITting a new REPORT it appeared to clear the ghosting in HTML differently than the CALL FUNCTION into a FUNCTION-POOL did.

ADDITIONAL TESTING NOTES:
Changing the system parameters [the system GUI buffer sizes?] had no impact on the behavior.

Having the method call directly into a FORM of the function pool (e.g. PERFORM Entry_Point(SAPLZxxx) USING ... where Zxxx is the function group) also had the erratic behavior.

Having the method call directly [i.e. the PERFORM into another program] into a REPORT that calls dynpros with CALL SCREEN had some success and some failures.  In the failure case, the SWO1 business object dumped with DYNPRO_NOT_FOUND because it looked for it in the calling program [business object,] not the called one!  However, a later test did appear to transfer control to a different called program correctly.

It appears that something happens with the SUBMIT that really passes control (perhaps the active call stack) to the called REPORT and clears the HTML ghosts in the layer, whereas program-to-program calls and CALL FUNCTION into a FUNCTION-POOL do not always appear to register that control has passed.  This may be a bug in the SAP business object, as the developer has never encountered similar erratic behavior elsewhere in ABAP.  Or perhaps the HTML gets off track in its version of the stack.

The Developer suspects that the erratic behavior is more likely to arise with large function pools (many screens, large GUI STATUS to buffer, lots of F1 help on the fields) and is likely avoided in normal-sized applications.  If this is the case, another approach would be to make smaller function pools for these entry points and their screens.


Regards,
Sue Doughty
SAP Workflow Specialist
Old Dominion Freight Line, Inc.
Thomasville, NC 27265

________________________________
From: Sue Doughty
Sent: Monday, October 03, 2011 7:46 AM
To: 'SAP Workflow Users' Group'
Subject: Strange Behavior of Decision Work Item

We are in ECC 6.0, EHP4.  Any help would be greatly appreciated.

I have a very simple custom workflow.  It loops until the user clicks the Complete Workflow button.
[cid:image001.jpg at 01CC8978.8E3CC590]

The first button takes the user into change mode of the custom transaction.
[cid:image002.jpg at 01CC8978.8E3CC590]

When clicking the Green Arrow back in QAS or PRD, it returns to a blank screen.  In DEV, it takes the user back to the first screenshot above, which is what should happen.  Then the user can Complete the Workflow or go back into the transaction.
[cid:image003.jpg at 01CC8978.8E3CC590]

Like I said, in DEV, the workflow works perfectly, but in QAS and PRD, the blank screen appears.  The user then has to go out of the workflow in-box and back in before executing it again to get the decision steps again.

Sometimes there is a pop-up window that appears when exiting the transaction saying that the data has changed and asking if the user wants to save the changes.  The pop-up will display in DEV, but not in QAS or PRD.  In QAS and PRD, it goes to the blank Decision screen.
[cid:image004.jpg at 01CC8978.8E3CC590]

We have created a test user in DEV that has the user's security that is in QAS.  So, the security is the same in all three systems.

I feel like it must have something to do with the pop-up screen, but don't know why that would display in DEV, but not QAS or PRD.


Regards,
Sue Doughty
SAP Workflow Specialist

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20111013/f7bffa94/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 28001 bytes
Desc: image001.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20111013/f7bffa94/attachment.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 59080 bytes
Desc: image002.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20111013/f7bffa94/attachment-0001.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 19579 bytes
Desc: image003.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20111013/f7bffa94/attachment-0002.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 9695 bytes
Desc: image004.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20111013/f7bffa94/attachment-0003.jpg