Avoid Overlapping of Internal Ids in Oracle Cloud Objects (in J2C Project)
Our project is a journey to cloud project, where existing system EBS is going to get migrated in Cloud.
Considering that, internal Ids that are referred for any object (for e.g., supplier, Item, invoice , receipts, ledger etc.) are going to get changed while migrating to Oracle Cloud.
We have few external systems that use these IDs for some logics.
It could be a high risk of overlapping, because we cannot manipulate new IDs generated by Oracle Cloud (and not even new IDs generated during migration).
Which is the best practices suggested by Oracle in such cases?
Could be an option to alter sequences in order to define a specific ID from which it should start before migration?