on ‎2013 Jan 23 10:55 PM
Dear Team,
I have the following requirement on Purchase requisition(PR) item release rejection workflow(WS65400027).
Whenever an item release is rejected, the approver documents the reason for rejection in one of the PR item level text -Item note, mentioned below.
Text ID B02 Item note
Text Object EBAN Purchase requisition texts
Once the rejection notification goes to requestor of PR item release, the PR item text - Item note should get displayed in the task(TS65400032) description.
Below is the way I tried.
below is the code written in task description command editor. I tried with different ways to show up the dynamic text - Item note but none of them working.
Is it something like that dynamci texts using INCLUDE command won't work, and only the standard texts with INCLUDE command will work in task description.
Kindly let me know if you need any further information from my side.
Thanks for your help in advance.
Prathap
Request clarification before answering.
Hi,
(1) Write some code to fetch the rejection comments, given a PO item
(2) Add these rejection comments to (Z)BUS2009 as a virtual (multiline) attribute RejComments
(3) It's then easy to display the RejComments attribute in your workitem
cheers
Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Paul,
Thank you for your answer. I thought of doing it in the same way.
But I am trying uisng INCLUDE statement, just to check whether it is possible, it it works it reduces lot of effort for solution proposed by you.
By the way, is there any reason that INCLUDE command desn't work for dynamic texts like purchase requisition item texts?
Thanks
Prathap
Hi Prathap, We usually only use the INCLUDE command in work item texts for common static texts, e.g. created using Standard Texts.
The sequence in which the text is built and variables replaced is somewhat different to a normal SAPSCRIPT text, as the usual intention is to use the workflow container as the source for any dynamic information.
So basically - it's workflow, it's specific to workflow - use the workflow container as Paul suggests and you should be fine.
Rgds,
Jocelyn
P.S. In any case in my experience if you change editors in the text area, it's likely to wipe out a lot of that coding or modify it.
| User | Count |
|---|---|
| 9 | |
| 7 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.