<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16788" name=GENERATOR></HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space">
<DIV dir=ltr align=left><SPAN class=770495121-12022009><FONT face=Arial
color=#0000ff size=2>Hi Carolyn, I think you should raise a SAP message about it
now... but re changing the business object container operations - all
workflow bindings are exactly the same regardless of the table or XML container
approach. In your reports you can use the XML confainer and just use the WAPIs
to derive the appropriate data e.g. SAP_WAPI_READ_CONTAINER and similar.
Standard reports these days are delivered via BI content which does a more
thorough extract. But I always try to avoid using outmoded
approaches as problems invariably kick in over time. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=770495121-12022009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=770495121-12022009><FONT face=Arial
color=#0000ff size=2>Good luck. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=770495121-12022009><FONT face=Arial
color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=770495121-12022009><FONT face=Arial
color=#0000ff size=2>Jocelyn </FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@MIT.EDU
[mailto:sap-wug-bounces@MIT.EDU] <B>On Behalf Of </B>Carolyn
Fuller<BR><B>Sent:</B> Friday, 13 February 2009 3:40 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> [LIKELY JUNK]Re: Binding issues after
transport to production<BR></FONT><BR></DIV>
<DIV></DIV>Jocelyn,
<DIV><BR></DIV>
<DIV>When we upgraded to ECC 6.0 a little over a year ago, I did not
convert our existing workflow templates to use XML persistence. Therefore their
profiles are all set as "<SPAN class=Apple-style-span
style="FONT-SIZE: 10px; FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre"><FONT
class=Apple-style-span face=Helvetica size=3><SPAN class=Apple-style-span
style="FONT-SIZE: 12px; WHITE-SPACE: normal">Compatibility." I compared our
container handling between development and production via
transaction </SPAN></FONT><SPAN class=Apple-style-span
style="FONT-SIZE: 12px; FONT-FAMILY: Helvetica; WHITE-SPACE: normal">SWU_CONT_PERSISTENCE.
But this seems to be used to maintain the outdated "Structure" mode
configuration. The table is empty in both environments. Is there another
transaction I should run to check container handling?</SPAN></SPAN></DIV>
<DIV><BR></DIV>
<DIV><SPAN class=Apple-style-span
style="FONT-SIZE: 10px; FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre"><SPAN
class=Apple-style-span
style="FONT-SIZE: 12px; FONT-FAMILY: Helvetica; WHITE-SPACE: normal">We have
reports that read workflow containers which is one of the reasons I chose
not to convert. It is my understanding that converting to XML persistence means
I would need to change these reports. Since we weren't experiencing performance
or storage concerns I didn't have the incentive to convert. Also, wouldn't I
need to change all the business object container operations if we
converted?</SPAN></SPAN></DIV>
<DIV><BR></DIV>
<DIV>A lot of these old custom workflow templates created by the non-workflow
developer caused us heartaches during our upgrade to ECC 6.0, which is how I
discovered some of his unorthodox practices, but they are all working smoothly
now.</DIV>
<DIV><BR></DIV>
<DIV>Carolyn</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>
<DIV>
<DIV>On Feb 11, 2009, at 7:28 PM, Dart, Jocelyn wrote:</DIV><BR
class=Apple-interchange-newline>
<BLOCKQUOTE type="cite">
<DIV>Carolyn - just a thought - check in your workflow admin settings
that<BR>both systems are set up with the same container handling (XML)
and<BR>persistency rules. Also if you aren't already doing this...
make sure<BR>your test scripts for QA always include a test on workflow
instances<BR>that was created and running before your changes were applied.
It can<BR>be worthwhile deliberately creating workflow instances for
this purpose<BR>before importing your changes into QA. <BR>Regards,<BR>Jocelyn
<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@MIT.EDU [<A
href="mailto:sap-wug-bounces@MIT.EDU">mailto:sap-wug-bounces@MIT.EDU</A>] On
Behalf<BR>Of Carolyn Fuller<BR>Sent: Thursday, 12 February 2009 11:05
AM<BR>To: SAP Workflow Users' Group<BR>Subject: Re: Binding issues after
transport to production<BR><BR>Alon,<BR><BR>Yes. We modified the workflow
binding in production in order to fix <BR>the problems that appeared in
production but did not appear in either <BR>QA or
development.<BR><BR>Carolyn<BR>On Feb 11, 2009, at 4:16 PM, Alon Raskin
wrote:<BR><BR>
<BLOCKQUOTE type="cite">Just to clarify, you are modifying the workflows
directly in the<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">production system?<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Alon Raskin<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">e: <A
href="mailto:araskin@3i-consulting.com">araskin@3i-consulting.com</A><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">-----Original Message-----<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">From: sap-wug-bounces@mit.edu [<A
href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</A>] On
<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Behalf<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Of Carolyn Fuller<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Sent: Wednesday, February 11, 2009 2:17
PM<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">To: SAP Workflow Users' Group<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Subject: Binding issues after transport to
production<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Hi all,<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">On a couple of occasions I've moved modified
workflows from our<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">development environment to our QA environment with
no problems only to<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">encounter binding issues in production. On these
occasions, deleting<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">the bindings in production and re-creating them in
production has<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">solved the problem.<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Are these issues due to the fact that I didn't run
SWU_OBUF after the<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">transports went in? Should SWU_OBUF be on our action
log when modified<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">workflows go into production?<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">---<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Carolyn Fuller<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Massachusetts Institute of Technology<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Information Services and Technology<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Administrative Computing<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Senior Analyst/ Programmer<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">(617) 253-6213<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><A
href="http://fuller.mit.edu/">http://fuller.mit.edu/</A><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE
type="cite">_______________________________________________<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">SAP-WUG mailing list<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><A
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE
type="cite">_______________________________________________<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">SAP-WUG mailing list<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><A
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></BLOCKQUOTE><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></DIV></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>