Entry in SWW_CONTOB table

[akshay.bhagwat@wipro.com]

Thanks for the inputs Jaro and Florin...
 
Regards,
Akshay

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Strba, Jaroslav
Sent: Monday, December 08, 2008 1:20 PM
To: SAP Workflow Users' Group
Subject: RE: Entry in SWW_CONTOB table


Hello Akshay,
 
when there is XML persistence set for workflow, the container data are
not in tables SWW_CONT and SWW_CONTOB, but there are in table SWWCNTP0
and saved in XML format. 
 
Regards,
 
Jaro
 

________________________________

From: sap-wug-bounces at mit.edu on behalf of akshay.bhagwat at wipro.com
Sent: po 8. 12. 2008 05:22
To: sap-wug at mit.edu
Subject: Entry in SWW_CONTOB table


Hi All,
 
We are on version ECC6.0
There is custom application developed to capture the status of custom
workflow developed for PCR.
This exisiting JSP application is using this table view SWIVOBJECT (
which uses tables SWW_CONTOB and SWWWIHEAD) to retrieve work item
status.
 
For all other existing workflows, parent work item id i.e. flowitem id
is getting updated in this table SWW_CONTOB , however in case of newly
developed workflow,  parent work item id is not present in SWW_CONTOB
table.  Due to this, in application, workflow status is not getting
reflected correctly. (Whereas this work item ID is present in SWWWIHEAD
table.)
 
I can see that work item id is found in SWWWIHEAD for every workflow
scenario that is tested, but the same is not present in SWW_CONTOB
table.Anybody have an idea , when is the work item ID is stored in this
table SWW_CONTOB? 
 
Any inputs are appreciated.
 
Thanks and Regards,
Akshay

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email. 

www.wipro.com 


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20081208/9452c1dd/attachment.htm