Container element not created in the WI description

[Matthan Logronio]

Hi Sue,
Thanks for the inputs.
I dont have a corresponding SAPGUI transaction since this leave transaction
of ours is purely java webdynpro customized.  I only update a customized
table to store the transaction.  I also looked into that timing of database
update.  I have several steps before going to the task and everything is
updated.  (The BOR date attributes have the corresponding values).

Thanks.
matt

On Sat, Jun 5, 2010 at 3:37 AM, Keohan, Susan - 1140 - MITLL <
keohan at ll.mit.edu> wrote:

>  Hi Matthan,
>
> Have you tried triggering the WF by using the native SAPGUI transactions?
> This will give you a more accurate picture than using SWUE or SWUS, since
> the timing of database updates cannot be the issue using these transactions
> (you’ve already created the Leave data, right?)
>
>
>
> A long time ago, FIPP workflows used to bomb out because the workflow would
> be triggered and begin processing before the FIPP document had been
> committed to the database.  This issue with dates sounds similar to me.
> Although, playing with dates in HR data is a trick unto itself.
>
>
>
> I would try to generate the leave request via SAPGUI and see what happens.
> If you still get the issue – then I would start my debugging engine J.
>
>
>
> Cheers,
>
> Sue
>
> ----
>
> Susan R. Keohan
>
> SAP Workflow Specialist
>
> Enterprise Applications
>
> Information Services Department
>
> MIT Lincoln Laboratory
>
> 244 Wood Street, LI-200
>
> Lexington, MA. 02420
>
> 781-981-3561
>
> keohan at LL.MIT.EDU
>
>
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Matthan Logronio
> *Sent:* Friday, June 04, 2010 1:25 AM
>
> *To:* sap-wug at mit.edu
> *Subject:* Container element not created in the WI description
>
>
>
>
>
> Hi All,
>
> Hope anyone had already encountered this problem of mine regarding the
> generation of container element in the WI description in the task.  This
> quite a simple problem but i cannot find the solution to the problem.
>
> Im using a date attributes in the WI description for leave request approval
> task :
>
>  e.g. Leave request for Approval &emp.name& &emp.date_from& -
> &emp.date_to&
>
>
>
> The workflow is started thru a start event triggered by a RFC call from the
> SAP portal.
>
> Somehow, when the WI is generated in the task, a syntax error occurs in the
> error log and the date attributes are not generated successfully:
>
> e.g sample WI description result : Leave request for Approval Employee Name
> -
>
> (the emp.date_from and to are not displayed).
>
>
>
> To make it more complicated, when it i started the workflow in SWUE or
> SWUS, all the attributes are generated successfully, no syntax errors in the
> logs.
>
> e.g sample WI description result : Leave request for Approval Employee name
> 06/01/2010 - 06/02/2010
>
>
>
> All bindings are correct from Workflow to task.  I cannot find a problem in
> the RFC call that triggers the event since the workflow is started
> successfully (previous tasks prior to the task with erroneous description,
> like background task are completed).  When i looked at the BOR container in
> the task, the from and to dates attributes have values.
>
>
>
> Appreciate any help on this.  BTW, we are on 4.7 r/3.
>
>
>
> Thanks in advance.
>
> matt
>
> _______________________________________________
> 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/20100605/cc0d8e8e/attachment.htm