Changing a wait event's key

[Michael Pokraka]

Ah, alas I have little faith in that, I suspect the whole thing is a lecacy
leftover which has just stuck around for far too long to ever be changed,
and that's why the object can be instantiatied using either or both keys.
This is with Projects, and WBS elements and Networks.

(FYI Kjetil, I've argued with WBS elements and their internal/external
numbers in 4.0b so don't feel too left behind in the technological
backwaters :-)

Also, we've - ahem - already 'fixed' the code by redefining the
existencecheck method to work around this problem originally. Now we have a
new requirement for raising the event from a CRM box, where half the key
isn't available. It's a bit of chicken and egg... I might go with Phil's
very unofficial idea, preferrable to having multiple RFC's and stuff.

Thanks Kjetil, Jocelyn and Phil for your input. To be honest, I actually
don't care right now as I'm off on holiday but will tackle this anew next
year,

Happy Christmas and a Merry New Year to all,
Cheers
Mike


Dart, Jocelyn wrote:
> Report to OSS - developer really should fix the event raising code.
> Regards,
> Jocelyn
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Soady, Phil
> Sent: Monday,20 December 2004 3:07 PM
> To: SAP Workflow Users' Group
> Subject: RE: Changing a wait event's key
>
> Hi Mike,
>
> Hacks allowed ?
> Direct update via custom code to SWFDVEVINS
>
> Not an "official" solution ;-/
>
>
> Phil Soady
> Senior Consultant
> Business Technologies
> SAP Australia
> M  +61 (0) 412 213 079
> E  phil.soady at sap.com
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Michael Pokraka
> Sent: Friday,17 December 2004 12:42 AM
> To: sap-wug at mit.edu
> Subject: Changing a wait event's key
>
> Hi all,
> Is it possible to change the object key of a wait for event step?
> 4.7/620
> system, the container element I'm using for the wait step has the
> correct
> key in the workflow, but the terminating event that gets triggered has a
> different key.
>
> Hmmm, more detail required I guess: It concerns those nasty little
> things
> called WBS elements which can have either an internal or the external
> number
> or both as the object key - all referring to the same object.
>
> Now, the flow is triggered using both keys, but the terminating event
> only
> has the external number (comes from outside the system).
>
> So we have BUS2054 with key INT1234EXT1234 and I want to wait for event
> BUS2054.BLAH with a key of INT1234 in the instance linkage.
> I've a few ugly workarounds, thinking pseudo-events which get the full
> key
> and fire off a second evt, or a custom object with half the key in the
> container and the likes, an second RFC call to get the full key
> beforehand.
> But that's all too much sledgehammer-walnut-ish and I can't help
> wondering
> if there's something simpler.
>
> Any ideas welcome,
> Cheers
> Mike
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>