$uuid

Hi Jason
That’s all bout UUID? :-)

Tips for use, or how we did it

We also generate an ID from the UUID, but then remove all the "-" characters. (We don't need the internal structure with network card IDs and the like.)
Then I do the following:
v_SYS_ID = $concat(<the_tbl_name>,"_",<shortend_uuid>)
This SYS_ID is then written to the SYS_ID column in the various tables.

Advantage:
When working with different applications and needing to exchange IDs, you always know which table a "message" belongs to. Or, better yet, I send data—including the SYS_ID—to the other system. That system stores the ID as an EXT_ID in its database. When the other application sends us a request, it also sends the EXT_ID, which is actually our SYS_ID.
I take the SYS_ID, remove the first part, and already know which table is being referenced. I can then use the SYS_ID to find the correct record in the table.
So, for example, if a command like "Read a record" or "Delete a record" comes in via a SOAP interface, everything is already handled by the SYS_ID; I don't need separate SOAP messages for every possible table.
Of course, for an update, the content has to be sent along with the SYS_ID, but that's no big deal.

It also works great if you have a workflow set up in the UnifAce application; it references the relevant records using the SYS_ID :-)

Regards
Ingo

Hi Ingo,

Thanks for sharing additional things people could consider.

Regards,

Jason.

CU in A’dam 😀