Change of Object key length

[Florin Wach]

Hi Wayne,

yes, instance 00001 <> 000000001 as there's a character-by-character comparison and the instances are left-justified, counting zeroes.

To get your old instances closed correctly (regarding the event couplings), you'll need to create a workaround for a while with an additional event coupling  ZBUS_OBJ.<for-each-event> and a check function module for STRLEN( objkey ) = 10 and a receiver function module that resends the event for objkey+5(5). You can write generic function modules and link them in each event you'd need.

After a while when all previous instances are completed, you should deactivate these event linkages again.

Best wishes,
   Florin


-------- Original-Nachricht --------
> Datum: Mon, 2 Feb 2009 17:25:16 +1100
> Von: "Hanrahan, Wayne" <WHanrahan at powercor.com.au>
> An: sap-wug at mit.edu
> Betreff: Change of Object key length

> Hello workflowers,
>  I have a custom Business object workflow etc. The length of the domain
> of the object has been expanded (from 5 to 10 numeric).
>  Changing the workflow containers using the FM's SAP_WAPI_READ_CONTAINER
> and SAP_WAPI_WRITE_CONTAINER seem to do the job fine.
>  However, for open instances of the object(workflows half way through),
> when an event is raised with the newly expanded object key the workflow
> does not move on.
>  Is it the case that if the workflow started out (created event) with a
> key 5 long, all subsequent events for the life of that workflow must be
> raised with a key 5 long?
>  BTW, all newly created workflows work just fine. This happens only for
> the ones 'in process' when the key is expanded.
>  Anyone been down this road before?
>  Many thanks,
>  Wayne Hanrahan.
> **********************************************************************
> CitiPower Pty and Powercor Australia Ltd. This email and any file
> attachments are confidential and intended solely for the use of the
> individual or entity to whom they are addressed. If you have received
> this email in error please tell us immediately by return email and
> delete the document.
> **********************************************************************