Overview of Importing Collaboration Messaging Setup Data

You can import Oracle Fusion Collaboration Messaging Framework setup data or you can migrate your Oracle B2B setup data into Collaboration Messaging Framework for trading partners that use a service provider.

The service provider, with delivery method, and inbound and outbound collaboration messages, must already be set up in the environment into which you import the data. If you want to import your Collaboration Messaging Framework setup data, you need to create a ZIP file that contains two CSV files with these names:

• CmkConfigImportPartners.csv: This file contains information about trading partners.

• CmkConfigImportDocs.csv: This file contains the documents that are set up for the trading partner.

You need to upload both the files to the scm$/B2BConfiguration$/import$ account and then follow the procedure in the Import Collaboration Messaging Setup Data section.

You can migrate your Oracle B2B setup data and update Oracle Fusion application setup in these scenarios:

• Data of Oracle Supplier Network Trading Partners

• Data of non-Oracle Supplier Network Trading Partners (a single trading partner, set up with many B2B Supplier site codes)

• Data of non-Oracle Supplier Network Trading Partners (many trading partners, each with a single B2B Supplier site code)

To migrate the data you have to first export your B2B configuration data using the B2B export feature, which creates a compressed file that contains all the B2B set up data, and upload the file into the scm$/B2BConfiguration$/import$ account.

Then you need to use two scheduled processes to create a collaboration messaging setup data import file and then import the collaboration messaging setup data. And then you need to review the imported data using the Manage Collaboration Messaging Setup Data Import task.