<div>Thanks a ton...This would definitely suit my requirement. Will get back to you in case of issues :-)</div>
<div> </div>
<div>Thanks & Regards,</div>
<div>Prasath N<br><br> </div>
<div><span class="gmail_quote">On 8/23/06, <b class="gmail_sendername">Munday,Sherie J.</b> <<a href="mailto:MUNDAYSJ@airproducts.com">MUNDAYSJ@airproducts.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Prasath,</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">We have customized all of our pcr workflows and have brought in the data by extending the bus7051 and adding the data as a virtual attribute using the function module ISR_SPECIAL_DATA_GET (which was given to us by a consultant = Vinod Singh). code below. We then use a simple parsing to separate the fields.
</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Best Wishes,</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Sherie</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Sherie Munday</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Workflow Developer/Analyst</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Air Products & Chemicals, Inc.</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2"><font size="1">
<p>FUNCTION isr_special_data_get.</p></font><font color="#0000ff" size="1">
<p>*"----------------------------------------------------------------------</p>
<p>*"*"Lokale Schnittstelle:</p>
<p>*" IMPORTING</p>
<p>*" VALUE(NOTIFICATION_NO) TYPE QMNUM</p>
<p>*" EXPORTING</p>
<p>*" REFERENCE(SCENARIO) TYPE QSCENARIO</p>
<p>*" REFERENCE(SPECIAL_DATA) TYPE QISRTSPECIAL_PARAM</p>
<p>*" EXCEPTIONS</p>
<p>*" NO_INTERNAL_SERVICE_REQUEST</p>
<p>*" INVALID_NOTIF_NUMBER</p>
<p>*" INT_SERVICE_REQUEST_NOT_FOUND</p>
<p>*"----------------------------------------------------------------------</p></font><font size="1"></font><font color="#0000ff" size="1">
<p>* local data</p></font><font size="1">
<p>DATA: lt_dummy TYPE qisrsgeneral_param.</p>
<p>DATA: lr_isr_document TYPE REF TO cl_isr_xml_document.</p>
<p>DATA: ls_notif TYPE qmel.</p></font><font color="#0000ff" size="1">
<p>* MAIN</p>
<p>* try buffer first</p></font><font size="1">
<p>CALL FUNCTION 'ISR_SPECIAL_DATA_BUFFER_GET'</p>
<p>IMPORTING</p>
<p>ET_SPECIAL_DATA = special_data</p>
<p>ED_SCENARIO = scenario</p>
<p>EXCEPTIONS</p>
<p>BUFFER_EMPTY = 1.</p>
<p>IF sy-subrc eq 0.</p>
<p>EXIT.</p>
<p>ENDIF.</p>
<p>* check notification number</p>
<p>SELECT SINGLE * FROM qmel INTO ls_notif</p>
<p>WHERE qmnum = notification_no.</p>
<p>IF sy-subrc NE 0.</p>
<p>RAISE invalid_notif_number.</p>
<p>ELSEIF ls_notif-auswirk IS INITIAL.</p>
<p>RAISE no_internal_service_request.</p>
<p>ENDIF.</p></font><font color="#0000ff" size="1">
<p>* set scenario</p></font><font size="1">
<p>scenario = ls_notif-auswirk.</p></font><font color="#0000ff" size="1">
<p>* read ISR XML document</p></font><font size="1">
<p>CALL METHOD cl_isr_xml_document=>read_for_display</p>
<p>EXPORTING id_notif_no = notification_no</p>
<p>IMPORTING er_isr_xml_document = lr_isr_document</p>
<p>EXCEPTIONS bds_error = 1.</p>
<p>IF sy-subrc NE 0.</p>
<p>RAISE int_service_request_not_found.</p>
<p>ENDIF.</p></font><font color="#0000ff" size="1">
<p>* read data from XML document</p></font><font size="1">
<p>CALL METHOD lr_isr_document->get_data_from_xml</p>
<p>IMPORTING general_data = lt_dummy</p>
<p>special_data = special_data.</p></font><font color="#0000ff" size="1">
<p>* TODO: check general_data against ls_notif data</p></font><font size="1">
<p>ENDFUNCTION.</p></font></font></span></div><br>
<div lang="en-us" dir="ltr" align="left">
<hr>
<font face="Tahoma" size="2"><b>From:</b> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a> [mailto:<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">
sap-wug-bounces@mit.edu</a>] <b>On Behalf Of </b>prasath natesan<br><b>Sent:</b> Wednesday, August 23, 2006 9:23 AM<br><b>To:</b> SAP Workflow Users' Group<br><b>Subject:</b> Workitem to contain values of attributes entered in Adobe form
<br></font><br> </div></div>
<div><span class="e" id="q_10d3b65870bae03c_1">
<div></div>
<div>Hi All,</div>
<div> </div>
<div>We are creating a PCR based adobe form for the scenario "Seperation of an Employee". We have linked the form to a workflow which is triggered by the BUS7051-Created event and the workitem appears in the UWL of the approver. I want the workitem text to contain attributes that is entered in the adobe form(say employee number). The current binding between the trigerring event and workflow gives me only the notification details but i want the data entered in the adobe form by the initiator to appear in the workitem text. Can anyone help me how to acheive this?
</div>
<div> </div>
<div>We are using ECC5.0 and EP6.0.</div>
<div> </div>
<div>Thanks,</div>
<div>Prasath N </div></span></div>
<div></div></div><br>_______________________________________________<br>SAP-WUG mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br><br></blockquote></div><br>