Import Your Deal Product Data

You can use Import Management to create, update, or delete your deal product data.

To import Deal Product records, perform the following tasks:

1. Map your source data to Oracle Applications Cloud object attributes.

2. Create source Comma Separated Values (.csv) file for import.

3. Create the import activity.

4. Review the import results.

How You Map Your Source Data to Target Object Attributes

To import your Deal Product data into Oracle Applications Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the .CSV file for data import:

• Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

• Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

• Understand your options for uniquely identifying the records.

• Ensure parent records exist before importing child records.

• Identify the target object attributes that are required in the .CSV file for a successful import.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

• You have completed all the prerequisites for importing each attribute in your source data.

• You have all parent records in place before importing child records. For example, when importing the address of an account, ensure the account exists.

Select a Unique Identifier for Your Records

To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Applications Cloud.

The preferred options to uniquely identify an object record are as follows:

• Internal ID: If you're identifying a record that already exists in Oracle Applications Cloud, then you can use the internal ID of the record, a system-generated unique identifier Attributes with "id" in the attribute name are typically internal IDs. You can determine the internal ID of a record by exporting Oracle Applications Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Deal Product object, this attribute is DealProdId.

• Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Deal Product object, the attribute is DealProdNumber.

Review Required Attributes and Validations for Deal Product Object

To import data successfully into Oracle Applications Cloud, your .CSV file must include the required attributes. Ensure that you provide valid values for the attributes.

The following table lists the required attributes for importing new Deal Product records, required attributes for updating Deal Product records, prerequisite setup tasks for the attributes, and specific validations, if any, for Deal Product import:

Attribute	Description	Data Type	Data Length	Prerequisite Setup Task/ Import Validations	Creating a Deal Product record	Updating an Existing Deal Product record
DealNumber	The public unique identifier value for the deal.	Text	30	You can obtain the Deal Number for an existing deal registration from the Deal Registration work area.	Conditionally required Provide either the DealId or the DealNumber to identify the deal.	Conditionally required Provide either the DealId or the DealNumber to identify the deal.
DealId	The unique ID for the existing deal record in the destination table..	Number	18	The deal must exist.	Conditionally required Provide either the DealId or the DealNumber to identify the deal.	Conditionally required Provide either the DealId or the DealNumber to identify the deal.
DealProdNumber	The relationship between the deal registration and the deal product.	Text	30	You can obtain the DealProductNumber for an existing deal registration product from the Deal Registration work area.	Required	Conditionally required Provide either the DealId or the DealNumber to identify the deal.
ProductGroupNumber	The public unique identifier value for the deal registration product group.			You can obtain the ItemNumber for an existing deal registration product from the Deal Registration work area.	Conditionally required When you import a new deal registration product item (as opposed to a product group), then you must provide either the ProductGroupNumber or the ProductGroupId.	Conditionally required When you import a new deal registration product item (as opposed to a product group), then you must provide either ProductGroupNumber or ProductGroupId
DealProdId	The unique ID for the existing deal product record in the destination table.	Number	18	The deal product must exist.	Not required	Conditionally required You must provide either the DealProductId or the DealProductNumber to identify the product.
ItemNumber	The public unique identifier value for the deal registration product item.	Text	30	You can obtain the ItemNumber for an existing deal registration product from the Deal Registration work area.	Conditionally required When you import a new deal registration product item (as opposed to a product group), then you must provide either the ItemNumber or the InventoryItemId.	Conditionally required When you update deal registration product item (as opposed to a product group), then you must provide either ItemNumber or InventoryItemId.
InventoryItemId	The unique ID for the existing sales catalog product (item) record in the destination table.	Number	18	You can determine the InventoryItemId by exporting the Product Group Products object. Navigate to the following in the Setup and Maintenance work area: Offering: Sales Functional Area: Data Import and Export Task: Schedule Export Processes	Conditionally required When you import a new deal registration product item (as opposed to a product group), then you must provide either the ItemNumber or the InventoryItemId.	Conditionally required When you update deal registration product item (as opposed to a product group), then you must provide either ItemNumber or InventoryItemId.
ProductGroupId	Unique Product Group ID defined in sales product catalog.	Number	18	You can determine the ProdGroupId by exporting the Product Group Products object. Navigate to the following in the Setup and Maintenance work area: Offering: Sales Functional Area: Data Import and Export Task: Schedule Export Processes	Conditionally required When you import a new deal registration product item (as opposed to a product group), then you must provide either the ItemNumber or the InventoryItemId.	Conditionally required When you update deal registration product item (as opposed to a product group), then you must provide either ItemNumber or InventoryItemId.
UomCode	Specifies the Unit of measure	Number	None	You can determine the units of measure. Navigate to the following in the Setup and Maintenance work area: Offering: Financials Functional Area: Items Task: Manage Units of Measure Profiles	Conditionally required A value is required when you import a new deal registration that's associated with product (Items).	Not required
RegisteredPrice	The value for the price of the product item associated to the deal registration.	Number	None	You can obtain the RegisteredPrice for an existing deal registration using the Deal Registration work area.	Not required	Not required
InvOrgId	The unique ID for the existing product item organization's record in the destination table.	Number	18	You can determine the InvOrgId by exporting the Product Group Products object. Navigate to the following in the Setup and Maintenance work area: Offering: Sales Functional Area: Data Import and Export Task: Schedule Export Processes	Conditionally required A value is required when you import a new deal registration that's associated with product (Items).	Conditionally required A value is required when you update an existing deal registration that's associated with product (Items), and you don't provide the product's ID (InventoryItemId).

You can view the Deal Product object along with all its child objects and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.

Create the Source CSV File

You include the data that you want to import into Sales and Fusion Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

1. Go to Navigator > Tools > Import Management > Import Objects.

2. Select the Deal Product object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

To import data into Oracle Applications Cloud, you need to create an import activity and provide the CSV file as an input to the activity.

To create an import activity, do the following:

1. Go to Navigator > Tools > Import Management > Import Queue.

2. Click Create Import Activity in the Manage Imports page.

3. In the Enter Import Options page, provide a name for the import activity, and select Deal Product from the Object drop-down list.

4. Select the CSV file in the File Name field, and click Next.

5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

1. Go to Navigator > Tools > Import Management > Import Queue.

2. Click All Imports and search for the import activity that you created earlier.

3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.