<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Hi all,<BR>
<BR>
This problem get a little bit deeper. I'm pretty sure that SAP has missed a trick with the 'new' 'Structure Persistence' code designed to cope with the 'old' BOR Object Container table SWW_CONTOB.<BR><BR>I've been looking at the new ECC 6.0 code and made a bit of a discovery. Basically, the ABAP Classes do not understand what a Logical System is. They do not possess any attribute to store it, nor do they have any means to pass it through to functionality that will eventually invoke database updates. Simply put: they always assume you are dealing with local instances.<BR>
<BR>
Now I have absolutely no idea if this affects any of you who are using the 'new' OO container but it certainly affects us who want to stick with the 'old' BOR Container because a Logical System can be 'local' or 'remote', i.e. it could point to the same client/system combination you are working on, or it could point to a completely different client/system altogether.<BR>
<BR>
Take ABAP Class Method [CL_SWF_CNT_PX_CONTAINER->_container_write_values] as a point in case. This method is supposed to replace the old code that eventually calls Function Modules SWW_WI_CONTAINER_INSERT and SWW_WI_CONTAINER_MODIFY.<BR>
<BR>
It manages to work at the moment because it invokes FM SWO_CREATE which has a nifty subroutine in it (logical_system_handling) that copes with a blank value for LOGSYS being passed in. So the instantiation of an instance will only fail if the key is invalid for the <STRONG>local</STRONG> client. But since this FM does not pass out the LOGSYS value it determines at runtime the calling Method has no way of catching this.<BR>
<BR>
Worse still, when Method [CL_SWF_CNT_PX_CONTAINER->_container_write_values] finally gets around to carrying out the database updates (which it does directly I might add, bad SAP!) it has no way of ever passing through a decent value in LOGSYS. <BR>
<BR>
Hence we have blanks. And hence, I think, SAP has forgotten something.<BR>
<BR>
At least, that's my take on things anyway. Perhaps people here have some thoughts?<BR>
<BR>
Regards,<BR>
<BR>
Mike GT<BR>
<BLOCKQUOTE>
<HR>
From: madgambler@hotmail.com<BR>To: sap-wug@mit.edu<BR>Subject: RE: ECC 6.0 SWW_CONTOB Logical System name not being updated properly<BR>Date: Thu, 20 Mar 2008 17:11:38 +0000<BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
Official response from SAP on this one seems to be:<BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"><EM>Yes, there may well be a problem updating this field, but frankly we don't care because you shouldn't be looking in that table anyway, and you are very naughty for not using our WAPIs!</EM><BR></BLOCKQUOTE>Nice one SAP. Okay, so I made that last part up, but OSS Message 1153860 reads a bit like that :)<BR> <BR>I have no idea if this is going to cause any of you any grief, but those of you intending to continue using the 'old' container tables might want to keep an eye out for general instantiation problems with Business Objects that can't seem to be explained.<BR><BR>Regards,<BR> <BR>Mike GT<BR>
<BLOCKQUOTE>
<HR>
From: madgambler@hotmail.com<BR>To: sap-wug@mit.edu<BR>Subject: RE: ECC 6.0 SWW_CONTOB Logical System name not being updated properly<BR>Date: Tue, 11 Mar 2008 14:08:33 +0000<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass EC_body.hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
We too are on patch level 13.<BR> <BR>Our development system clearly shows LOGSYS values appearing regular as clockwork before the upgrade and now only occasionally after the upgrade, which is most odd.<BR><BR>It kind of implies a deep-down MOVE statement or something not working properly to my mind. <BR> <BR>Probably a unicode bug or something...will see what SAP have to say.<BR> <BR>MGT<BR>
<BLOCKQUOTE>
<HR>
From: araskin@3i-consulting.com<BR>To: sap-wug@mit.edu<BR>Date: Tue, 11 Mar 2008 07:49:19 -0400<BR>Subject: RE: ECC 6.0 SWW_CONTOB Logical System name not being updated properly<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding-right:0px;padding-left:0px;padding-bottom:0px;padding-top:0px;}
.ExternalClass EC_BODY.hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
<STYLE title=owaParaStyle>
.ExternalClass P
{margin-bottom:0px;}
</STYLE>
<DIV dir=ltr><FONT face=Tahoma color=#000000 size=2>Hi Mikey,</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma></FONT> </DIV>
<DIV dir=ltr><FONT face=tahoma>I just took a look at our sandbox and I see a logical system in most of our entries. We are on ECC 6.0 patch level 13.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma></FONT> </DIV>
<DIV dir=ltr><FONT face=tahoma>Out of approximately 200K entries in this table, I did find approximately 9K entries without LogSys including _WORKITEM entries. </FONT></DIV>
<DIV dir=ltr><FONT face=tahoma>I am honestly not sure why some do and some don't. Maybe others have an idea?</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma></FONT> </DIV>
<DIV dir=ltr><FONT face=tahoma>Oh and you are so old school for using that table (though I do understand why) :-)</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma></FONT> </DIV>
<DIV dir=ltr><FONT face=tahoma><FONT face=tahoma><FONT face=tahoma><FONT face=tahoma><FONT face=tahoma><FONT face=tahoma><FONT face=tahoma><FONT face=tahoma>Alon</FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></DIV>
<DIV>
<DIV><FONT face=Tahoma size=2>
<P class=EC_EC_EC_MsoNormal><FONT face=Calibri color=navy size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy; FONT-FAMILY: Calibri"></SPAN></FONT><STRONG> </STRONG></P>
<P class=EC_EC_EC_MsoNormal><FONT face=Calibri color=navy size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy; FONT-FAMILY: Calibri"><STRONG></STRONG></SPAN></FONT> </P></FONT></DIV></DIV>
<DIV id=EC_EC_EC_divRpF545651 style="DIRECTION: ltr">
<HR>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] On Behalf Of Mike Gambier [madgambler@hotmail.com]<BR><B>Sent:</B> Tuesday, March 11, 2008 6:30 AM<BR><B>To:</B> SAP Workflow Users' Group<BR><B>Subject:</B> ECC 6.0 SWW_CONTOB Logical System name not being updated properly<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi,<BR> <BR>Has anyone else noticed or seen evidence of the 'old' Workflow Container table (SWW_CONTOB) not being updated properly where the Logical System name field (LOGSYS) is concerned? I'm a little bit worried that this field is only sometimes being updated when entries are being added.<BR> <BR>Our 'new' Workflow instances do not appear to be updating this field when creating new entries, although any triggering event container instances do have their proper logical system name values.<BR>So, for example, '_WORKITEM' entries are being created with a blank value for LOGSYS (which just isn't right) whereas any importing container elements definitely do have a kosher value.<BR> <BR>This is causing us some grief with FMs like CHECK_OBJECT_IN_WF because the standard SAP code is looking for a like-for-like match with whatever value you pass through in OBJECT-LOGSYS.<BR> <BR>I'm going to trawl through OSS but I thought I'd ask around to see if this is a 'known' feature.<BR> <BR>I'd like to ask anybody else who is currently working on an upgrade project to check out their SWW_CONTOB entries too (that is if they still intend to use the old tables) and let me know if they have this problem at all, or whether it's just our system misbehaving :)<BR> <BR>Regards,<BR> <BR>Mike GT<BR><BR>
<HR>
Think you know your TV, music and film? <A href="https://www.searchcharades.com/" target=_blank>Try Search Charades!</A> </DIV></BLOCKQUOTE><BR>
<HR>
She said what? About who? <A href="http://www.msnsearchstar.com/" target=_blank>Shameful celebrity quotes on Search Star!</A> </BLOCKQUOTE><BR>
<HR>
She said what? About who? <A href="http://www.msnsearchstar.com/" target=_blank>Shameful celebrity quotes on Search Star!</A> </BLOCKQUOTE><br /><hr />A prize an hour, 24 hours a day. <a href='http://www.bigsnapsearch.com
' target='_new'>Try Big Snap now!</a></body>
</html>