Workitem to contain values of attributes entered in Adobe form

[prasath natesan]

Thanks a ton...This would definitely suit my requirement. Will get back to
you in case of issues :-)

Thanks & Regards,
Prasath N


On 8/23/06, Munday,Sherie J. <MUNDAYSJ at airproducts.com> wrote:
>
>  Prasath,
> 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.
> Best Wishes,
> Sherie
>
> Sherie Munday
> Workflow Developer/Analyst
> Air Products & Chemicals, Inc.
>
> FUNCTION isr_special_data_get.
>
> *"----------------------------------------------------------------------
>
> *"*"Lokale Schnittstelle:
>
> *" IMPORTING
>
> *" VALUE(NOTIFICATION_NO) TYPE QMNUM
>
> *" EXPORTING
>
> *" REFERENCE(SCENARIO) TYPE QSCENARIO
>
> *" REFERENCE(SPECIAL_DATA) TYPE QISRTSPECIAL_PARAM
>
> *" EXCEPTIONS
>
> *" NO_INTERNAL_SERVICE_REQUEST
>
> *" INVALID_NOTIF_NUMBER
>
> *" INT_SERVICE_REQUEST_NOT_FOUND
>
> *"----------------------------------------------------------------------
>
> * local data
>
> DATA: lt_dummy TYPE qisrsgeneral_param.
>
> DATA: lr_isr_document TYPE REF TO cl_isr_xml_document.
>
> DATA: ls_notif TYPE qmel.
>
> * MAIN
>
> * try buffer first
>
> CALL FUNCTION 'ISR_SPECIAL_DATA_BUFFER_GET'
>
> IMPORTING
>
> ET_SPECIAL_DATA = special_data
>
> ED_SCENARIO = scenario
>
> EXCEPTIONS
>
> BUFFER_EMPTY = 1.
>
> IF sy-subrc eq 0.
>
> EXIT.
>
> ENDIF.
>
> * check notification number
>
> SELECT SINGLE * FROM qmel INTO ls_notif
>
> WHERE qmnum = notification_no.
>
> IF sy-subrc NE 0.
>
> RAISE invalid_notif_number.
>
> ELSEIF ls_notif-auswirk IS INITIAL.
>
> RAISE no_internal_service_request.
>
> ENDIF.
>
> * set scenario
>
> scenario = ls_notif-auswirk.
>
> * read ISR XML document
>
> CALL METHOD cl_isr_xml_document=>read_for_display
>
> EXPORTING id_notif_no = notification_no
>
> IMPORTING er_isr_xml_document = lr_isr_document
>
> EXCEPTIONS bds_error = 1.
>
> IF sy-subrc NE 0.
>
> RAISE int_service_request_not_found.
>
> ENDIF.
>
> * read data from XML document
>
> CALL METHOD lr_isr_document->get_data_from_xml
>
> IMPORTING general_data = lt_dummy
>
> special_data = special_data.
>
> * TODO: check general_data against ls_notif data
>
> ENDFUNCTION.
>
>  ------------------------------
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *prasath natesan
> *Sent:* Wednesday, August 23, 2006 9:23 AM
> *To:* SAP Workflow Users' Group
> *Subject:* Workitem to contain values of attributes entered in Adobe form
>
>
>  Hi All,
>
> 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?
>
> We are using ECC5.0 and EP6.0.
>
> Thanks,
> Prasath N
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060823/ac71f01f/attachment.htm