Migrate Public Unique ID Data

You can migrate PUIDs from a test to production instance, or the other way around.

The migration is essentially exporting the data in one instance using the ready-to-use bulk export process in the sales application and then importing the data into another instance using the import process.

Select a Migration Approach

Consider the following points before selecting a migration approach:

• If your organization frequently uses the bulk data load (migration) functionality, then use the document sequence approach. For more information, see the related topics.

• If your organization doesn't use the bulk data load frequently, then use Oracle's standard import process to import the data from one instance to another. When PUIDs are rejected in the process, manually define new PUIDs for the rejected PUID values and repeat the import process until all the data is imported. For more information on how to import, see the Implementing Sales guide.

Note: You can't migrate transactional data.

Manually Override PUID Values

You can manually override the PUID value during the import process. After a PUID is rejected in the import process, a new PUID value should be defined. For example, let's say SMTTXT-002 is rejected because the record already exists in the test instance. So, a new PUID value of SMTTXT-003 is defined and used in the import process.

Set Up Document Sequencing

Every object team defines a document sequence number for objects as part of PUID implementation. When a new PUID is created in the database, the PUID functionality uptakes the value from the document sequence process. For example, if the document sequence initial value is 0, when a PUID is created in the production instance, then the sequence generation creates the PUID starting from 0. If the document sequence has a different initial value between the test and production instances, then the possibility of PUID clashes between the test and production instance is removed completely.

Organizations know how many objects are typically created in a test instance versus a production instance. Therefore, defining an appropriate initial value for document sequence in the test and production instances should resolve the PUID clashes. For more information about setting up document sequences, see Set Up Document Sequences in the Oracle Fusion Applications Developer's guide.

Maintain Different Prefixes

You define the prefix information for specific objects in the Manage Public Unique Identifier Sequence Generation task in Setup and Maintenance. You can enter a uniquely identifiable prefix in the test instance to signify that the PUID values belong to the test instance. Similarly, while the same objects are defined in the same task flow in the production instance, enter a prefix to signify the PUID values belong to a production instance. Therefore, the PUID value as a whole never clashes when the migration occurs from the test to production instance or the other way around.