To define a source system:When importing data from a source other than Oracle Product Information Management Data Hub (PIMDH), you must create a source system within Import Workbench.
To define a source system:Navigate to the Import Workbench and select the Source System Setup tab.
Click Define Source System to create a new source system.
Alternatively, you can search for and view any existing source system item that is enabled only for customer items. Enable it for items.
On the Define Source System page, enter the following for the source system:
a unique name
a unique code
Note: The code can be alphanumeric, but must not contain any spaces. Ensure that the code matches the System Code defined on the System Setup page within the corresponding Oracle Application Integration Architecture (AIA).
Select the Enable For Items check box if you plan to use this source system for item-related data.
Additional Information: Oracle Product Hub uses the same architecture as Oracle Customer Data Hub. The Enable For Items check box communicates that you plan to enter item-related data. You can always uncheck this box at a later time.
Select the Enable for Data Pool check box if the source system is a GDSN data pool. The system can perform certain tasks for GDSN batches, such as:
using a group ID to process an entire item hierarchy
automatically sending a message to the data pool once data is imported
enabling you to send messages to the data pool as needed
Additional Information: You can specify a GDSN-enabled source system for both GDSN and non-GDSN batches. However, you cannot specify a non-GDSN source system for a GDSN batch.
On the Define Source System page, Click the Data Load Options sub-tab.
Select Yes by Automatically Match on Data Load if you want to run match rules.
Suggestion: If you want to load data from a source system and manually inspect it before running match rules, then select No.
If you are using match rules, then select a Default Item Catalog Match Rule from the list.
Determine whether to check or uncheck Apply Default Match Rule To All Records.
Uncheck - The system applies the default item catalog category-level match rule to unconfirmed items with an assigned item catalog category. The system assigns the item catalog level match rule for items with no item catalog category.
Check - The system applies the default item catalog-level match rule to all unconfirmed items.
Select Yes if you want to Automatically Confirm Single Matches that you find when running match rules for the entire batch. If you select No, then the system tries to match all unconfirmed records using the default match rule.
Select Yes if you want to Automatically Confirm New Item on No Match. When you run match rules for the entire batch, this option enables you to automatically confirm an item with no matches as a new item. If you select No, then you must manually move any unmatched items from the Unconfirmed tab to the Confirmed tab, where they are marked with the match status of New.
Note: If the Item Number and Description are not provided, the Source System Item Reference and Description will be used as the Item Number and Description by default.
Select the appropriate Import option:
Immediately on data load - automatically updates the Oracle Item Master table with matched data.
Schedule Data and Time - select the date and time to import the confirmed items or structures in the batch.
None - leaves the data in the Import Workbench. You can manually import the data at a later time.
Select the appropriate Default Revision Import Policy:
Create New - creates a new version of the item.
Update Latest - updates the latest item revision upon import.
Click the Import Options sub-tab.
Define default import options here. You can change the import options for a particular batch later, if necessary.
Select one of the following Change Order options:
Add To Existing - associates the imported data with an existing change order.
Create New - creates a new change order for the imported data.
Additional Information: When creating a new change order, you have the opportunity to enter or select the following:
Change Order Category
Change Order Type
Change Order Name
Change Order Description
Once you select the change order type, depending on the setup, the Change Order Number field is automated or you must manually enter a change order number.
None - imports the data into PIMDH without going through a change approval process.
Select one of the following New Item Request options:
None - you cannot create any new item requests from this source system. Instead, the system creates draft items. Later, you can navigate to the Item Workbench, further define the draft items, and add it to a new item request. See:
One per Item Catalog Category - create one new item request per item catalog category within an imported batch. This new item request can contain multiple line items.
One per Item - create one new item request per item.
For more information about new item requests, see: Creating New Item Requests.
If you are importing structures, select the following default options:
Structure Type
Caution: Oracle Product Hub recommends avoiding the use of the Root structure type. User-defined attributes and import formats are not supported for the Root structure type.
Structure Name
Effectivity Control Type - choose Date or Model/Unit Number
Structure Contains - choose All Components or Changed Components Only
Select one of the following Data Import options:
Import All Data
Create Cross References Only - Select this option if you want to create cross-references only. It will not import the data.
Click the Mapping sub-tab. Select one of the following Mapping Process options:
Define in PIMDH - Enables you to define the mapping of attributes between an external source system and PIM Data Hub within PIM Data Hub.
External - Enables you to upload an XSLT file containing mapping information between an external source system and PIM Data Hub.
None - No mapping occurs.
