Migrate Oracle

B2B Trading
Partner Setup
to Collaboration
Messaging
Framework
WHITE PAPER / JULY 10, 2019
PURPOSE STATEMENT
The purpose of this document is to provide you with detailed information on how you can migrate
your Oracle B2B trading partner setup to Oracle Fusion Collaboration Messaging Framework.

DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is the
exclusive property of Oracle. Your access to and use of this confidential material is subject to the
terms and conditions of your Oracle software license and service agreement, which has been
executed and with which you agree to comply. This document and information contained herein may
not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written
consent of Oracle. This document is not part of your license agreement nor can it be incorporated
into any contractual agreement with Oracle or its subsidiaries or affiliates.

This document is for informational purposes only and is intended solely to assist you in planning for
the implementation and upgrade of the product features described. It is not a commitment to deliver
any material, code, or functionality, and should not be relied upon in making purchasing decisions.
The development, release, and timing of any features or functionality described in this document
remains at the sole discretion of Oracle.

Due to the nature of the product architecture, it may not be possible to safely include all features
described in this document without risking significant destabilization of the code.

2 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
TABLE OF CONTENTS

Purpose Statement ...................................................................................... 2

Scenarios in Which You Can Import Oracle B2B Setup Data ...................... 4

Points to Consider ....................................................................................... 5

POINTS TO CONSIDER BEFORE MIGRATING ORACLE SUPPLIER NETWORK SETUP

DATA ........................................................................................................................................... 5

POINTS TO CONSIDER AFTER MIGRATING ORACLE SUPPLIER NETWORK SETUP DATA5

POINTS TO CONSIDER BEFORE MIGRATING NON-ORACLE SUPPLIER NETWORK SETUP

DATA (SCENARIO: ONE B2B SUPPLIER SITE CODE PER TRADING PARTNER) ................. 5

POINTS TO CONSIDER AFTER MIGRATING NON-ORACLE SUPPLIER NETWORK SETUP

DATA (SCENARIO: ONE B2B SUPPLIER SITE CODE PER TRADING PARTNER) ................. 6

POINTS TO CONSIDER BEFORE MIGRATING NON-ORACLE SUPPLIER NETWORK SETUP

DATA (SCENARIO: MANY B2B SUPPLIER SITE CODES PER TRADING PARTNER) ............ 6

POINTS TO CONSIDER AFTER MIGRATING NON-ORACLE SUPPLIER NETWORK SETUP

DATA (SCENARIO: MANY B2B SUPPLIER SITE CODES PER TRADING PARTNER) ............ 6

B2B Setup Data Migration Process Flow ..................................................... 7

B2B Setup Data Migration Steps ................................................................. 7

Create a Collaboration Messaging Setup Data File ..................................................................... 8

Import Collaboration Messaging Setup Data ..............................................................................14

Artifacts Created by the Import Process .....................................................................................14

Manage Collaboration Messaging Setup Data Import ................................................................15

3 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
SCENARIOS IN W HICH YOU CAN IMPORT ORACLE B2B SETUP DATA
There are three scenarios for migrating pre-Collaboration Messaging Framework B2B configurations
from Service-Oriented Architecture (SOA) B2B:

• Migration of Oracle Supplier Network trading partners

• Migration of non-Oracle Supplier Network trading partners (a single trading partner, setup with
many B2B supplier site codes)
• Migration of non-Oracle Supplier Network trading partners (many trading partners , each with
a single B2B supplier site code)

In the case of Oracle Supplier Network, both inbound and outbound message setups are imported. After
the migration process is completed, and after the delivery method updates are done (see Points to
Consider for details), B2B is longer be used for Oracle supplier Network messaging; all messaging
interactions use a web service interface.

In the case of non-Oracle Supplier Network setups, after the migration is completed, B2B is still involved
in the partner interaction, and all B2B artifacts continue to be used exactly as before. In this case, the
migration is only switching the internal routing of the XML message between B2B and the application —
before the migration, the message flow is between B2B and specific application components, whereas
after the migration, Collaboration Messaging Framework acts as an intermediary between the
application and B2B.

In either case, Collaboration Messaging Framework enables customization of the messages, alternate
delivery methods, centralized logging and error handling, ability to reprocess messages and other
features that were not possible earlier.

Note:

The migration assumes a very specific approach for modeling trading partners in B2B, and can only
extract and import Collaboration Messaging Framework setup data if trading partners have been set up
accordingly. Based on your migration scenario, review the expected B2B setup before proceeding with
the import.

Ideally, Collaboration Messaging Framework setup data should not exist in the environment where the
import is being done. If there is any existing Collaboration Messaging Framework setup data, then the
import process may result in additional setup records getting created that are not desired.

Supported use cases

1. Oracle B2B setup with one trading partner per supplier-site — Oracle Supplier Network
service provider
2. Oracle B2B setup with a single trading partner setup for multiple supplier-sites — Non-Oracle
Supplier Network service provider*
3. Oracle B2B setup with one trading partner / B2B Supplier Site Code per supplier-site — Direct
trading partner or Non-Oracle Supplier Network service provider

In the Collaboration Messaging Framework Oracle Supplier Network model for service providers, a
service provider is setup in B2B as a single trading partner. For outbound messages from B2B to the
service provider, the actual trading partner information is provided in the B2B message header OR can
be retrieved from within the payload.

*Inbound messages to B2B may require additional configuration.

4 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
POINTS TO CONSIDER

POINTS TO CONSIDER BEFORE MIGRATING ORACLE SUPPLIER NETWORK SETUP DATA

• In the B2B setup, Oracle Supplier Network trading partners are assumed to be modeled as
many trading partners, each with a unique B2B site code. Any trading partner that does not
have B2BSiteCode as an identifier will not be imported.
• Every trading partner must have an HTTP channel with a RECEIVER_ID and a
RECEIVER_ID_TYPE tag (the values in these tags are used to create the trading partner in
Collaboration Messaging Framework) and the channel URL pointing either to Oracle Supplier
Network Test or Oracle Supplier Network Production. Any trading partners that do not have
these values will not be imported.
• Each trading partner must have at least one or more outbound trading partner agreements that
use one of the pre-defined V1 OAGIS 7.2.1 document definitions, and the trading partner must
reference an Oracle Supplier Network channel. Any trading partner that does not have at least
one trading partner agreement that meets this condition will not be imported.
• The global Enable Procure to Pay Messaging flag in Collaboration Messaging Framework
must be enabled (it is enabled by default). Otherwise, both outbound and inbound messages
will not be processed.

POINTS TO CONSIDER AFTER MIGRATING ORACLE SUPPLIER NETWORK SETUP DATA

• Inbound messaging from Oracle Supplier Network will continue via the B2B setup until Oracle
Supplier Network switches the buyer account’s delivery method to Web Service instead of
HTTP Post. You can do this manually after completing the migration steps. Oracle Supplier
Network Administration automatically does it within a few weeks of enabling outbound
messaging via Collaboration Messaging Framework (for which Oracle Supplier Network must
be able to derive the web service endpoint URL from the B2B HTTP receiver URL). Until then,
B2B setup is used for inbound messaging and you should not update the B2B setup.
• After inbound messaging from Oracle Supplier Network is enabled via web services, you can
deactivate the B2B trading partner agreements that were in place earlier and delete any Oracle
Supplier Network related B2B trading partners and trading partner agreements. Oracle
Supplier Network will no longer use these trading partners or agreements for messaging.
• The global Enable Procure to Pay Messaging flag in Collaboration Messaging Framework
must be enabled (it is enabled by default). Otherwise, both outbound and inbound messages
will fail processing after the migration.

POINTS TO CONSIDER BEFORE MIGRATING NON-ORACLE SUPPLIER NETWORK SETUP DATA

(SCENARIO: ONE B2B SUPPLIER SITE CODE PER TRADING PARTNER)
• If the existing B2B setup involves inbound messaging, then there is a manual update required
in the B2B setup in addition to the steps documented for migration. The document definitions
referenced for inbound messages are not the same as the document definitions referenced by
Collaboration Messaging Framework. You need to update the B2B setup to reference the
Collaboration Messaging Framework document definitions. You have to redeploy all trading
partner agreements after the update.
• In this scenario, many trading partners could have the same HTTP Post URL, or each trading
partner could have a different URL. Both scenarios are treated the same way. That is, the
Create Collaboration Messaging Setup Data File scheduled process represents them in the
generated CSV files as trading partners with service provider as None, with trading partner
name the same as the B2B trading partner name, trading partner ID the same as B2B trading
partner name, ID Type as Name, and a set of outbound and inbound documents based on the
trading partner agreements that exist for the trading partner. Note that, in this scenario, you
should not update the service provider name in the CSV file. Otherwise, outbound message

5 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
 recipients may see additional HTTP header fields in the message they receive. Inbound
messages will continue to be successfully received by the B2B, but will fail validation in
Collaboration Messaging Framework because an additional SENDER_HUB_ID HTTP header
field is required in the HTTP header to process the message.

POINTS TO CONSIDER AFTER MIGRATING NON-ORACLE SUPPLIER NETWORK SETUP DATA

(SCENARIO: ONE B2B SUPPLIER SITE CODE PER TRADING PARTNER)
• The B2B setup will continue to exchange messages with partners.

POINTS TO CONSIDER BEFORE MIGRATING NON-ORACLE SUPPLIER NETWORK SETUP DATA

(SCENARIO: MANY B2B SUPPLIER SITE CODES PER TRADING PARTNER)
• If the existing B2B setup involves inbound messaging, then there is a manual update required
in the B2B setup in addition to the steps documented for migration. The document definitions
referenced for inbound messages are not the same as the document definitions referenced by
Collaboration Messaging Framework. You need to update the B2B setup to reference the
Collaboration Messaging Framework document definitions. You have to redeploy all trading
partner agreements after the update.
• In this scenario, the Create Collaboration Messaging Setup Data File represents the trading
partner as a Collaboration Messaging Framework Service provider in the generated CSV file,
with the service Provider Name the same as B2B trading partner Name, Service Provider ID
the same as B2B trading partner Name, ID Type the same as Name, and all the trading
partners identified with trading partner ID as the B2BSiteCode value, ID Type as B2BSiteCode
and a set of outbound documents based on the trading partner agreements that exist for the
trading partner. The scheduled processes, Import Collaboration Messaging Setup Data, then
creates equivalent collaboration messaging setup records, including a service provider with the
delivery method for the service provider specified as B2B Adapter.

POINTS TO CONSIDER AFTER MIGRATING NON-ORACLE SUPPLIER NETWORK SETUP DATA

(SCENARIO: MANY B2B SUPPLIER SITE CODES PER TRADING PARTNER)
• The B2B setup will continue to exchange messages with partners.

6 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
B2B SETUP DATA MIGRATION PROCESS FLOW

Figure 1. Process for migrating supplier network trading partner B2B setup data to Oracle Fusion
Collaboration Messaging Framework.

B2B SETUP DATA MIGRATION STEPS

Most B2B setups include partners and agreements that have been created but are not being used. Also,
within trading partners, there may be channels or other configuration parameters that are created but
not used. The B2B export does not indicate the state of a trading partner agreement (deployed or not).
As a result, the import process may not always be able to correctly create a final desired CSV
representation of the Oracle Supplier Network trading partners. For example, without knowing if a
trading partner agreement is deployed, it is not possible to determine if the status of outbound
messaging should be enabled for a document.

7 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
To address this, the import allows for two stages of data verification — one after creating the CSV
import file, before importing into Fusion, and the other after importing the CSV and using the Import
Type as Validate Only to see if there is any conflict if the setup records are imported into the application.

To import the B2B setup data, here’s what you have to do:

1. Export your B2B configuration data using the B2B export feature.
This creates a compressed file that contains all the B2B set up data.
2. Upload the file into the scm$/B2BConfigurationImport$/import$ account.
3. Create a collaboration messaging setup data import file.
This creates Collaboration Messaging Framework setup data records. If no Oracle Supplier
Network trading partners are found during the export, then the scheduled process status is set
to Error, with the details mentioning that no Oracle Supplier Network trading partners were
found. If at least one trading partner is found, then the process status is set to Success.
4. Review the CSV files that are created and update as required (verify trading partners and
documents, remove unwanted records, update status for documents to Enabled or Disabled).
5. Import the collaboration messaging setup data.
6. Review the imported data.
If needed, delete the import batch, make updates to the data as required, and import the data
again.

Create a Collaboration Messaging Setup Data File

After you export your B2B set up data and upload it to the scm$/B2BConfigurationImport$/import$
account, run the Create Collaboration Messaging Setup Data File process.

1. Go to Tools > Scheduled Processes.

2. Click Actions > Schedule New Process.
3. Search for Create Collaboration Messaging Setup Data File and click OK.
4. Specify the following parameters:
o B2B Configuration ZIP file: The file that you uploaded to the
scm$/B2BConfigurationImport$/import$ account
o Import Type: Oracle Supplier Network B2B Setup or Other B2B Setup

Table 1: Import Types for Creating Setup Data File

IMPORT TYPE IMPORT DATA EXTRACTED

Oracle Supplier Network • Trading partners that have the Oracle Supplier Network Test or Production
B2B Setup URL set up with an HTTP Delivery Channel.
• Trading partners with a single ID, with ID Type of B2B Supplier Site Code.
• Trading Partner Agreements for trading partners that use one of the pre-
seeded (V1 implementation) OAG 7.2.1 document definitions.

Other B2B Setup • Trading partners that have an HTTP Delivery Channel with a non-Oracle
Supplier Network Test or Production URL.
• Trading partner with a single ID or multiple IDs with ID Type of B2B Supplier
Site Code.
• Trading Partner Agreements for trading partners that use one of the pre-
seeded (V1 implementation) OAG 7.2.1 document definitions.

8 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
 5. Click Submit.

The scheduled process extracts the setup data and creates two CSV files into the
scm$/B2BConfigurationImport$/import$ account (which is the same account to which you uploaded
the B2B export file). The CmkConfigImportPartners.csv file contains all the trading partner
information that is extracted from the B2B export file and the CmkConfigImportDocs.csv file
contains all the documents that are set up for that trading partner.

CmkConfigImportPartners.csv Generation rules

• Setting the Service Provider in the CmkConfigImportPartners.csv

o If the delivery channel is an Oracle Supplier Network channel, then the service
provider name is set in the output as Oracle Supplier Network or Oracle Supplier
Network Test, depending on the channel URL.
o If the delivery channel is a non-Oracle Supplier Network channel, and the trading
partner has multiple B2B Supplier Site Codes, than the service provider name is set
as the trading partner name.
o If the delivery channel is a non-Oracle Supplier Network channel, and the trading
partner has a single B2B Supplier Site Codes, then the service provider name is set
to None.
• Setting Trading Partner details in the CmkConfigImportPartners.csv
o If the import is of type Oracle Supplier Network B2B Setup, then the fields
OSNPartnerId and OSNPartnerIDType are populated from the RECEIVER_ID and
RECEIVER_ID_TYPE HTTP header fields on the channel. If there is a value here,
then the import setup data task uses it for creating the Collaboration Messaging
Framework trading partner IDs and ID Type (this overrides the values in the PartnerId
and IdType fields)
o Otherwise, if the import is of type Other B2B Setup, then these fields will be empty,
and the PartnerId and IdType fields use this for creating the Collaboration Messaging
Framework trading partner IDs and ID Type.
o The B2B Trading Partner Name is written to the PartnerId field and the scheduled
process sets the IdType to be Name.
• Setting PartnerKeyType and PartnerKey1 in the CmkConfigImportPartners.csv
o The scheduled process sets the PartnerKeyType as B2BSupplierSiteCode and the
value of PartnerKey1 is set as the value of the B2B Supplier Site Code ID from the
trading partner.

CmkConfigImportDocs.csv generation rules

• Setting the Document Name and Direction

o The document name is extracted from any trading partner agreement that is setup for
the trading partner, if it is one of the pre-defined list of document definitions that was
part of the pre-Collaboration Messaging Framework B2B implementation. These are
PROCESS_PO_007/ PROCESS_PO_007, CHANGE_PO_007/ CHANGE_PO_007,
PROCESS_INVOICE_002/OAG_DEF, SHOW_SHIPMENT_005/OAG_DEF
respectively (B2B Document Type/ Document Definition). Direction is set to Outbound
for PO, and Inbound for Invoice and Shipment.
• Setting the Channel Endpoint
o This value is copied from the delivery channel of the outbound trading partner
agreements and is informational only.
• Setting the Status
o This value is set to Enabled by the scheduled process.

9 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
 The records of the CmkConfigImportPartners.csv file are described in the following table.

Table 2: Records of the CmkConfigImportPartners.csv file

COLUMN TITLE DESCRIPTION REQUIRED DURING IMPORT

ImportPartnerId Not used during import. No

ImportBatchId A unique batch ID. Yes

ImportPartnerLineNum A unique line number. Yes

ImportType Not used during import. No

PartnerId Trading Partner ID. For B2B export, Yes

this is the trading partner name set up
in B2B.

IdType ID Type. For B2B export, the ID Type Yes

is Name.

OsnPartnerId This is the RECEIVER_ID set up in Optional

the HTTP channel for Oracle Supplier
Network trading partners. If a value is
found, it is used as the Trading
Partner ID (this value overrides the
Trading Partner ID value). Required
only for Oracle Supplier Network
migration, that is, if partnerkeytype is
B2B Supplier Site Code.

OsnPartnerIdType This is the RECEIVER_ID_TYPE set Optional

up in the HTTP channel for Oracle
Supplier Network trading partners. If a
value is found, it is used as the
Trading Partner ID Type (this value
overrides the Trading Partner ID Type
value).

ServiceProviderName The service provider name to be Yes

associated with the trading partner.
This service provider must exist in
Collaboration Messaging Framework.

processedStatus Not used during import. No

ExtPartnerStatus Not used during import. No

ExtPartnerFailReason Not used during import. No

PartnerKeyType For importing trading partners to be Yes

associated to supplier sites, and for
the B2B Migration import, this is to be
set as B2B Supplier Site Code.

For manual import, this may be set to

Supplier Site and, in that case,
PartnerKey1, PartnerKey2, and

10 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
 PartnerKey3 are all required and need
to be populated as outlined.

PartnerKey1 For importing trading partners to be Yes

associated to supplier sites, and for
the B2B migration import, this is to be
set as the value of the B2B Supplier
Site Code as specified in the B2B
trading partner setup and the Oracle
Fusion supplier site record.

For manual import if the

PartnerKeyType is set to Supplier
Site, this is required and will be set to
Supplier Name.

PartnerKey2 For manual import if the Optional

PartnerKeyType is set to Supplier
Site, this is required and will be set to
Supplier Site Name.

PartnerKey3 For manual import if the Optional

PartnerKeyType is set to Supplier
Site, this is required and will be set to
Procurement Business Unit Name.

partnerKey4 Not used during import. No

PartnerKey5 Not used during import. No

PartnerKey6 Not used during import. No

AppPartnerStatus Not used during import. No

AppPartnerFailReason Not used during import. No

ApplPartnerId Not used during import. No

ExternalPartnerId Not used during import. No

importDateTime Not used during import. No

CreatedBy Not used during import. No

CreationDate Not used during import. No

LastUpdatedBy Not used during import. No

LastUpdateDate Not used during import. No

LastUpdateLogin Not used during import. No

ObjectVersionNumber Not used during import. No

11 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
The records of the CmkConfigImportDocs.csv file are described in the following table.

Table 3: Records of the CmkConfigImportDocs.csv file

COLUMN TITLE DESCRIPTION REQUIRED DURING IMPORT

ImportDocId Not used during import. No

ImportPartnerId Not used during import. No

ImportBatchId Key reference to an import batch. Yes

ImportPartnerLineNum Key reference to a trading partner. Yes

PartnerId Partner ID. Yes

IdType Partner ID Type. Yes

MessagingStandard Not used during import. No

Version Not used during import. No

MessageType Not used during import. No

MessageSubtype Not used during import. No

A collaboration document name. Yes

There must be a message definition
set up for the service provider for this
DocumentName
collaboration document. The possible
list of values depends on what is set
up for the service provider.

Direction Direction of the message (In/Out). Yes

ChannelEndpoint This is not used by the import. It is No

populated by the Create Collaboration
Messaging Setup Data scheduled
process if there is an HTTP channel
associated with the trading partner
agreement. This is informational only,
intended for the user to verify if the
documents and trading partners
extracted by the scheduled process
from the B2B ZIP file are accurate and
valid for import.

BusinessProcess Not used during import. No

ImportDelMethodId Not used during import. No

DeliveryMethodName Not used during import. No

ExtPartnerDocStatus Not used during import. No

12 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
 ExtPtnrDocFailReason Not used during import. No

AppPartnerDocStatus Possible values are Enabled, Yes

Disabled, and Hold. This is used to
set the status of the application
partner document, that is, whether the
B2B document for the supplier site is
enabled for processing after import. If
no value is specified, or the value is
not one of the listed values, it is set to
Enabled.

AppPtnrDocFailReason Not used during import. No

ApplPartnerDocId Not used during import. No

ExternalPtnrDocId Not used during import. No

PartnerMessageId Not used during import. No

CreatedBy Not used during import. No

CreationDate Not used during import. No

LastUpdatedBy Not used during import. No

LastUpdateDate Not used during import. No

LastUpdateLogin Not used during import. No

ObjectVersionNumber Not used during import. No

Collaboration Messaging Setup Data CSV File Review Actions

Once the CSV ZIP is generated, you can download the file from scm$/B2BConfigurationImport$/import$
(the same account as the B2B ZIP file) and review it.

It is critical that the CSV files that are generated be reviewed before proceeding with the second step of
the import. TheB2B export contains the entire B2B setup. Unless the B2B setup is precise and contains
exactly the artifacts required for the trading partners and trading partner agreements in use, there is no
guarantee that it will not contain trading partners, trading partner agreements, or other configuration
data that is not in use.

In general, assuming that the B2B setup does not contain any redundant data or deactivated trading
partner agreements, there should not be any need for any CSV updates. However, it is better to review
the generated CSV, to handle possible issues such as the ones listed below:

• In the CmkConfigImportPartners.csv file, remove any unwanted trading partners, and remove
their document references from the CmkConfigImportDocs.csv file.
• In the CmkConfigImportDocs.csv file, remove any document rows that are not needed. For
example, this could happen if the upgraded environment has redundant trading partner
agreements that are not deployed.
• In the CmkConfigImportDocs.csv file, update the desired status for all the records created by
the import. For example, the B2B export does not indicate if a trading partner agreement is
deployed. The export sets the status of all documents as Enabled by default, which you can
change.

13 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
 • Verify that all documents setup for the trading partner are present in the CSV, remove or
disable any documents as needed
• Do not update any service provider name in the CSV file. The name is used to correlate with
B2B (in the case of non-Oracle Supplier Network messaging use cases, and is used by
Collaboration Messaging Framework to perform updates (in the case of Oracle Supplier
Network use cases).
• Note that the URL information in the CSV file is for review only, and is not used for import
processing.

Import Collaboration Messaging Setup Data

After you create the import file, you need to import it using the Import Collaboration Messaging Setup
Data scheduled process. Note that you must have a service provider in Collaboration Messaging
Framework before you import the setup data. If a service provider doesn’t exist, you must create one.
The import process does not create a service provider.

1. Go to Tools > Scheduled Processes.

2. Click Actions > Schedule New Process.
3. Search for Import Collaboration Messaging Setup Data and click OK.
4. Select Import Type as Import to CMK.

Table 4: Import Types for Importing Setup Data

IMPORT TYPE ACTION

Uploads the setup data to the staging table, validates the import, and creates
Import to CMK
the valid records in Collaboration Messaging Framework setup tables.

Uploads the setup data to the staging table and validates the import. No
Validate Only
further processing is done.

5. Select the CSV Configuration ZIP File that you created using the Create Collaboration
Messaging Setup Data File scheduled process.
6. For Oracle Supplier Network data import, enter User Name and Password for the Oracle
Supplier Network buyer account.
7. Click Submit.
The records created by the process have a Batch ID stamped on them. These enable you to
delete the records, if needed.

Artifacts Created by the Import Process

The import process creates the following artifacts:

• Delivery Method: For Oracle Supplier Network or Oracle Supplier Network Test service
providers only. The migration updates the delivery method with the user name and password
of the buyer account (provided as part of the Scheduled Processes input).
• Trading Partners: These are created with or without a service provider reference, depending
on the data in the import spreadsheet. If a record exists, it is not updated, and this is not
treated as an error.
• The values from the Trading Partner ID and ID Type fields are used to create trading partners.
These are populated by the first scheduled process as either the B2B Site Code or the
RECEIVER_ID/RECEIVER_ID_TYPE (non-Oracle Supplier Network and Oracle Supplier
Network respectively).

14 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
 • Trading Partner Messages/Documents: These are created based on the data in the import
spreadsheet. If a record exists, it is not updated, and this not treated as an error. For trading
partner messages, the status is always set to Active by the import.
• Application Partners (association of the trading partner to supplier sites): The import
process tries to find a supplier site based on the B2BSiteCode in the CSV file. If multiple
supplier sites are found with the same B2bSiteCode in the supplier setup, they are all
associated to the corresponding trading partner. If an association already exists, then it is
skipped and not treated as an error. The B2BSiteCode value is copied to the Domain Value
Group in the application partner, for domain value map (DVM) lookups.
• Application Partner Documents: For each application partner created, the set of documents
that are in the CmkConfigImportDocs CSV file are set up. If a record already exists for the
document, it is skipped. The status of each document that is created is based on the status
provided in the spreadsheet.

Note: It is possible that an application partner gets created even if it was already an existing application
partner for the B2BSiteCode (there could be multiple supplier sites with the same B2BSiteCode, so
there could be multiple application partner records getting created for a single trading partner —
B2BSiteCode). You should review the outcome of the import to verify that all such scenarios are as
expected, and not due to set up errors (for example, due to incorrect B2BSiteCode values).

The records created by the process have a Batch ID stamped on them. These enable you to delete the
records, if needed.

Manage Collaboration Messaging Setup Data Import

After you import your collaboration messaging setup data, you can review the imported data.

1. Go to the Collaboration Messaging Framework work area and click Manage Collaboration
Messaging Setup Data Import from the Tasks pane.
2. Search for the imported data. You can:
• Select a row in the Trading Partners section and click Actions > Export to Excel.
• Select a row in the Documents section and click View > About This Record.
The search results include the following:
o Reasons for any import failure
o Status of the import of trading partners: Success, Invalid, or Skipped
o Reason for any failure of associating the supplier ID with the trading partner
o Status of association of the supplier with the trading partner: Success, Error,
or Invalid
3. Click Done.

UNDO IMPORT

After reviewing the data, you might sometimes need to undo the import of the setup data that you
created using the Create Collaboration Messaging Setup Data scheduled process, for example, if
duplicate application partner records are created, you can delete them. Here's what you can do:

1. In the Collaboration Messaging Framework work area, click Manage Collaboration

Messaging Setup Data Import in the Tasks panel.
2. In the Trading Partners section, click Actions > Undo Import.
3. Select the Batch ID and click OK.

If multiple batches are imported, you can delete the setup data created by each batch. Delete the latest
batch that was imported, followed by the previous one, and so on.

15 W HITE PAPER / Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework
ORACLE CORPORATION

Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA

Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com

CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.

blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed
orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0719
White Paper Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging FrameworkImport Oracle Fusion Collaboration Messaging
Setup DataImport Collaboration Messaging Setup DataImport Collaboration Messaging Setup Data
July 2019July 2019
Author: [OPTIONAL]
Contributing Authors: [OPTIONAL]