Object with over 70 chars key

[Shai Eyal]

Hi Mike,

Thanks for sharing the knowledge, unfortunately lately it is not obvious among senior colleagues.
Since STXH is standard table, I don't think of changing it.
I will have a look at persistent classes - it sound suitable.

Thanks again.
 
Regards,
Shai Eyal
SAP Logistics senior consultant
SAP Workflow & BPM specialist
http://www.linkedin.com/in/shaieyal
Mobile: 972-52-5816633



------------------------------

Message: 2
Date: Thu, 25 Mar 2010 15:03:53 -0000 (GMT)
From: "Mike Pokraka" <wug at workflowconnections.com>
Subject: Re: Object with over 70 chars key
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
    <0d176bf362e00902212859d4158d912a.squirrel at g.mail.aaisp.net.uk>
Content-Type: text/plain;charset=iso-8859-1

Yes you will either need a Z-table to map the GUID to your key, or else
you can extend/enhance your table to add a field for your GUID.
Use class CL_GUID_SERVICES to generate them.

If you have time for a bit of a learning curve, you can also look at
persistent classes (my preferred approach in most cases). You never need
to touch GUIDs, the persistent class provides a DB abstraction layer that
handles all DB interaction & GUID generation etc. Integrating them into a
WF class is also very simple and brings a few other benefits too.

Cheers,
Mike


      Get your preferred Email name!
Now you can @ymail.com and @rocketmail.com. 
http://mail.promotions.yahoo.com/newdomains/aa/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100325/a2d8ef93/attachment.htm