Create a Collaboration Messaging Setup Data File
After you export your B2B set up data from B2B and upload it to the scm$/B2BConfiguration$/import$ account, run the Create Collaboration Messaging Setup Data File process.
-
Go to Tools > Scheduled Processes.
-
Click Actions > Schedule New Process.
-
Search for Create Collaboration Messaging Setup Data File and click OK.
-
Specify these parameters:
-
B2B Configuration ZIP file: The file that you uploaded to the
scm$/B2BConfiguration$/import$
account -
Import Type: Oracle Supplier Network B2B Setup or Other B2B Setup
Import Type
Import Data Extracted
Oracle Supplier Network B2B Setup
-
Trading partners that have the Oracle Supplier Network Test or Production 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 predefined (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 predefined (V1 implementation) OAG 7.2.1 document definitions.
-
-
Click Submit.
The scheduled process extracts the setup data and creates two the CSV files into the
scm$/B2BConfiguration$/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's extracted from the B2B export file and the
CmkConfigImportDocs.csv file contains all the documents that are set up for that trading
partner. The output is a ZIP file that contains these two CSV files.
The records of the CmkConfigImportPartners.csv file are described in this table:
Column Title |
Description |
Required During Import |
---|---|---|
|
Not used during import. |
N |
|
A unique batch ID. |
Y |
|
A unique line number. |
Y |
|
Not used during import. |
N |
|
Trading Partner ID. For B2B export, this is the trading partner name set up in B2B. |
Y |
|
ID Type. For B2B export, the ID Type is Name. |
Y |
|
This is the RECEIVER_ID set up in the HTTP channel
for Oracle Supplier Network trading partners. If a value is found,
it's used as the Trading Partner ID (this value overrides the Trading
Partner ID value). Required only for Oracle Supplier Network migration
if |
Optional |
|
This is the RECEIVER_ID_TYPE set up in the HTTP channel for Oracle Supplier Network trading partners. If a value is found, it's used as the Trading Partner ID Type (this value overrides the Trading Partner ID Type value). |
Optional |
|
The service provider name to be associated with the trading partner. This service provider must exist in Collaboration Messaging Framework. |
Y |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
For importing trading partners to be 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 SupplierSite
and, in that case, |
Y |
|
For importing trading partners to be 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 |
Y |
|
For manual import if the |
N |
|
For manual import if the |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
This value determines whether the service provider is user defined or not. The valid values are Y or N. |
Y |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import |
N |
The records of the CmkConfigImportDocs.csv file are described in this table:
Column Title |
Description |
Required During Import |
---|---|---|
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Key reference to an import batch. |
Y |
|
Key reference to a trading partner. |
Y |
|
Partner ID. |
Y |
|
Partner ID Type |
Y |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
A collaboration document name. There must be a message definition set up for the service provider for this collaboration document. The possible list of values depend on what's set up for the service provider. |
Y |
|
Direction of the message (In/Out). |
Y |
|
This isn't used by the import. It is populated by the Create Collaboration Messaging Setup Data scheduled process if there's 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. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Possible values are Enabled, Disabled, Hold. This is used to set the status of the application partner document to indicate whether the B2B document for the supplier site is enabled for processing after import. If no value is specified, or the value isn't one of the listed values, it's set to Enabled. |
Optional |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |
|
Not used during import. |
N |