ECC 6 - New SWWWIDH fields including 'Status'

Mike Gambier madgambler at hotmail.com
Thu Oct 23 12:39:26 EDT 2008


Hi,
 
With regards to the Workflow Technical Log and the Chronological View, I have received, implemented and tested a brand new OSS Note 1264958 (thanks Peter if you're reading this) that switches the code to use the old 'Get Dependent WIs' approach when displaying a pre-ECC 6 Workflow Log (i.e. where SWWWIHEAD-TOP_WI_ID is empty).
 
This seemed to do the trick for old logs :)
 
Just a word of warning though, during the upgrade when the new index (SWWWIHEAD~D) was created for this new field our back-end database had nothing to go on when preparing table stats because this field was brand spanking new and not retrospectively populated. 
 
Consequently, even with the OSS Note fix, the SQL still hung occasionally but this time only when trying to look at new Workflow logs! We traced this and found the SQL was executing a full table scan instead of using the index, presumably because the parser assumed the index was worthless.
 
Once we regenerated the stats and tried again, everything was fine and both old and new Workflow logs could displayed in this view. So we have added this extra step to our uprade plan to be carried out an hour or two after switching on Workflow post-upgrade and would recommend other people do the same.
 
I'm still waiting on the SWWWIDH update...
 
Regards,
 
Mike GT



From: madgambler at hotmail.comTo: sap-wug at mit.eduSubject: RE: ECC 6 - New SWWWIDH fields including 'Status'Date: Tue, 21 Oct 2008 13:03:10 +0000


Hi all, The official word from SAP on these new SWWWIDH fields will be published as an OSS Note in a few weeks time, so I'm told. As soon as I find anything out I'll pass on the details. I'm still curious as to whether anyone else can find SWWWIDH-STATUS values of '2' in their systems yet? On a slightly different note I've spotted a slight issue with the new Technical Log, specifically the 'Chronological' view, which is trying to select from SWWWIHEAD using a new field called TOP_NODE_ID via a new index SWWWIHEAD~D. In our 4.6c=>ECC 6 test environments the view will just hang (presumably ending in a timeout) because all our 'old' Workflows have a blank value in this field since it was added by the upgrade and not updated during migration or the upgrade process. Interestingly the 'Tree' view works just fine. The code at fault appears to be this Class Method:CL_SWL_PROCESS_LOG->SELECT_CHRONOLOGIC...* new codingIF me->read_from_buffer( ) = ga_true.  ...ELSE.  IF pa_old_logic = ga_true.    ...   ELSE.      SELECT * INTO TABLE at_swwwihead      <======     FROM swwwihead                                 <======     WHERE top_wi_id = pa_swwwihead-wi_id. <======    ...  ENDIF.ENDIF.* end of note 1049570On the plus side the new TOP_NODE_ID field is a nice top-down link from Parent entries to Children that should do away with a lot of that recursive searching using the 'old' WI_CHKWI field :) Regards, Mike GT



From: madgambler at hotmail.comTo: sap-wug at mit.eduSubject: ECC 6 - New SWWWIDH fields including 'Status'Date: Tue, 14 Oct 2008 14:17:30 +0000

Hello fellow WUGgers, As part of our upgrade testing we've spotted a few new fields on the Workflow Deadlines table SWWWIDH that have crept in without any explanation or warning: 
WI_TIMESTAMP      SWW_TSTAMP  DEC   21    7     Workflow: UTC Time Stamp
TIMESTAMP         TIMESTAMPL  DEC   21    7     UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)
RETRY_CNT         SWW_RETCNT  NUMC  2     0     Retries for Work Items with Temporary Errors
ALERT_SEND        SWW_ALTSND  CHAR  1     0     Workflow: Alert Sent
RNDNUMBER         SWF_RNDNUM  NUMC  2     0     Workflow: Random Number
STATUS            SWW_DEASTA  NUMC  2     0     Workflow: Status of SWWWIDH Entry The one that caught my eye was the new 'Status' field, which currently has two possible values 1 (Active) and 2 (Error). During some of our test we've noticed the odd '2' value creeping in which seems to mark the deadline for death so that it is completely ignored by the SWWDHEX job. Has anyone got any info on what these new fields are used for? The 'Random Number' field is also a bit curious. I haven't trawled through SAP's ABAP Classes yet to find out what it's for but it strikes me as some kind of load-balancing or performance tweak, possibly for parallel streaming. If anyone knows otherwise can they share their knowledge please? :) Regards, Mike GT

Win £3000 to spend on whatever you want at Uni! Click here to WIN! 

For the best free wallpapers from MSN Click here! 
_________________________________________________________________
Discover Bird's Eye View now with Multimap from Live Search
http://clk.atdmt.com/UKM/go/111354026/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20081023/ad07f3a1/attachment.htm


More information about the SAP-WUG mailing list