Import Your Adjustment Data

How You Map Your Source Data to Target Object Attributes

To import your Adjustment 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 setups are done, if applicable.
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.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new Adjustments or are updating Adjustments that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Adjustment 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. This table lists the required attributes for importing new Adjustment records, required attributes for updating Adjustment records, required attributes for deleting Adjustment records, prerequisite setup tasks for the attributes, and specific validations, if any, for Adjustment import:

Attributes	Description	Prerequisite Setup Task/Import Validation	Creating a Adjustment record	Updating a Adjustment record	Deleting a Adjustment record
AdjustmentTypeCode	The code of the adjustment type.	A valid code from ORA_QP_LINE_ADJ_TYPES lookup.	Required	Not Required	Not Supported
AdjustmentAmount	The amount which need to be adjusted.	N/A	Required	Not Required	Not Supported
CoverageHeaderPuid	The Alternate key for the standard coverage header record.	The standard coverage header should exist.	Required	Not Required	Not Supported
CoverageDiscountPuid	The Alternate key for the standard coverage charge discount record.	Need to be unique.	Not Required. If provided , the record will be created with the given value else it will be stamped with the value generated by the system	Required	Not Supported
ServiceActivityName	The type of service activity associated with the change discount.	A valid value which is configured using the Manage Service Activities and active.	Required	Not Required	Not Supported
BillingTypeCode	The code of the billing type associated with the Service Activity.	A valid value which is configured using the Manage Service Activities for the service activity.	Required	Not Required	Not Supported
PricingBasisName	It tells what amount the % adjustment is based on such as list price/net amount basis.	This need to be an existing pricing setup.	Condionally Required. This is needed only when the Adjustment Type is a precentage type.	Not Required	Not Supported
ServiceItemNumber	The identifier of Service Item.	This need to be a valid item mapped to the BillingTypeCode.	Condionally Required. This is needed only when the Adjustment Type is a amount type.	Not Required	Not Supported
PriceUOMCode	The price unit of measure associated with the service item selected for the coverage adjustment.	A valid price unit of measure.	Condionally Required. This is needed only when the Adjustment Type is a amount type.	Not Required	Not Supported
CurrencyCode	The currency code of the coverage adjustment.	A valid fnd currency code.	Condionally Required. This is needed only when the Adjustment Type is a amount type.	Not Required	Not Supported
ChargeDefinitionCode	The onetime type pricing charge definition code.	This must be a valid onetime type pricing charge definition code.	Condionally Required. This is needed only when the Adjustment Type is a amount type.	Not Required	Not Supported

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the Adjustment object. The page also lists attribute information like type, length, description, and so on.

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:

Go to Navigator > Tools > Import Management > Import Objects.
Select the Adjustment 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

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

Go to Navigator > Tools > Import Management > Import Queue.
Click Create Import Activity in the Manage Imports page.
In the Enter Import Options page, provide a name for the import activity, and select Adjustment from the Object drop-down list.
Select the CSV file in the File Name field, and click Next.
You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.
Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.
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:

Go to Navigator > Tools > Import Management > Import Queue.
Click All Imports and search for the import activity that you created earlier.
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.