on 03-19-2012 8:46 AM
Hi Guys,
I have changed an FIPP based workflow to suit my needs. In the subworkflow, there is a step which gets rejection text from the function module CATSXT_SIMPLE_TEXT_EDITOR. I am putting this text in a container RejectText. I export this from this step 'ZRELEASE' to the subworkflow. In the main workflow, I bind this container to the main workflow container in the subworkflow step. When I trouble shoot, I the container is filled only in the ZRELEASE step, but it is not filled in the subworkflow and in the main workflow.
I also have tried saving the text in a Z-table in the ZRELEASE step so that I can extract it in a step in the main workflow, but it doesn't work as well. But I have noticed that it works when I put debug point in the method of the main workflow step which gets the rejection text. The container is filled in correctly . This is weird to me because if it works in debug mode, then it should work in the normal process. Any ideas what is going on?
Regards,
Darlington
Hello,
I am working on the same requirement & facing same issue but I think I am one step ahead of you.
Please see the thread-
http://scn.sap.com/thread/3164287
I have the rejection reason value (got from the FM-CATSXT_SIMPLE_TEXT_EDITOR) in the main workflow(WS10000051) container element Rej_Reason.To achieve this, after getting the rej reason, I used FM- SAP_WAPI_GET_WORKITEM_DETAIL(passed MainworkItem Instance number) & SAP_WAPI_WRITE_CONTAINER to write to the main workflow.
I have value of rejection reason value in main workflow but I am unable to use it in the step 000132 Correct where the work item is sent back to the initiator to correct errors(takes user to FB02) after rejection. I am stuck here in this last step of the requirement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Don't use a ZTable. Can you see the values in the container in the workflow log? Does each side of the binding have the same type?
regards
Rick Bakker / hanabi technology
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anjan and Rick,
Thank you both for your prompt replies.
Anjan, I have refreshed the buffer several times, with no luck.
Rick, I am no longer using the Z-table, but still the contents are not being exported from the subworkflow to the main workflow. The data type is the same both sides. The values are not appearing in the workflow log. They only appear for the step ZRELEASE only. It seems they are not being passed to the subworkflow from this step. Could it be that I set up Dynamic Parallel processing?
Regards,
Darlington
Hi Darlington
Can you please check whether the comments are being binded back to sub workflow. Check in your business object method coding where you are setting back the container value. Try to run the comment method independenlty and check whether it returns the comments.Otherwise sometimerecreting the task also make things work.
Nabheet
Thanks Nabheet and Vidal for your input. I have tried both your suggestions but it still doesn't work. I even recreated the task and the bindings.
Since this is a rejection, when the rejection is selected, the other branches of the parallel branches and the subworkflow go into CANCELLED status. Could this contribute to this issue?But the 'experiment' I did with the Z-table also doesn't work as well, even though I'm sure the bindings are correct. Any ideas?
The method by itself returns values, Nabheet.
Regards,
Darlington
I have attached some screenshots to give you an idea of what is happening. The main workflow is WS9000003 and it calls subworkflow WS90000005 as many times as an internal table entries implemeted for Dynamic Parallel Processing. The attached picture is a result of 3 parallel branches from 3 table entries. When you execute one branch to its end (i.e. you release or reject) the other branches are sent into status CANCELLED. The Get Rejection Text is the step in which I extract the rejection text from a Z-table which has been inserted in the ZRELEASE step. RejectText is the multiline container for the rejection text and RejectAgent is the container for the person who rejected the document.
Hi Anjan,
Thanks for your reply. The other import parameters are not of concern at the moment. RejectText and RejectAgent are the ones I am concerned with at the moment. Does it have any effect on RejectText and RejectAgent if the others are not imported? Because they are not really needed anyway.
Regards
Hello ,
Enable event log(SWELS) and check SWEL if any event if triggered during FIPP Rejection. I do not have system access now, but I think there should be an event triggered.
Since this would logically delete your existing WF, you create another Workflow and bind it to the Rejection event and get your work done.
Also, this might help:
Hi
In your main workflow we can see in Fork you have sub workflow call as wel as wait for reject event. What is the condition for fork to get complete..? I think as soon you reject an event for reject is triggered and it set call to your subworkflow branch obsolete. Please check in log if this is the case then you need to play with reject event.
Please confirm if this is the case
Thanks
Nabheet
Hi Guys,
There is no End Condition in the fork.
I have now put the get rejection text step in the rejection branch of the fork, after the wait for rejection step. But this branch does not complete, there are errors that say:
Error handling for work item 000000012651
Error during result processing of work item 000000012654
Error when starting a CASE branch
Error when defining successor for node 0000000213
Error when starting a CASE branch
Work item 000000012651: Object FLOWITEM method EXECUTE cannot be executed
What could be the issue now? Please see attached screenshots.
Regards,
Darlington
Hi,
Try to refresh the buffer SWU_OBUF
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.