Import Your Subscription Product Price Escalation Data
You can use Import Management to create update or delete Subscription Product Price Escalation records.
To import Subscription Product Price Escalation records, perform the following tasks:
- Map your source data to Oracle Applications Cloud object attributes.
- Create source Comma Separated Values (CSV) file for import.
- Create the import activity.
- Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Subscription Product Price Escalation 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 cases or are updating cases that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Subscription Product Price Escalation 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 Subscription Product Price Escalation records, required attributes for updating or deleting Subscription Product Price Escalation records, prerequisite setup tasks for the attributes, and specific validations, if any, for Subscription Product Price Escalation import:
| Attribute | Description | Prerequisite Setup Task/Import Validation | Creating a Subscription Product Price Escalation record | Updating a Subscription Product Price Escalation record | Deleting a Subscription Product Price Escalation record |
|---|---|---|---|---|---|
| EscalationPuid |
The unique identifier for escalations associated with product price. |
Should be unique value. Will be auto generated if not provided. |
Optional | Required | Required |
|
EscalationName |
The name of the escalation associated with product price. |
NA | Required | Optional | Not Required |
|
SubscriptionProductPuid |
The unique identifier for the subscription product associated with product price escalations. |
EnablePriceEscalationsFlag should be Y on this subscription product . |
Required | Optional | Not Required |
|
SequenceNumber |
The sequence number of the product price escalation. |
NA | Required | Optional | Not Required |
|
EscalationType |
The type of product price escalation. |
Accepts only 2 values. ORA_FIXED or ORA_MP_EXP. |
Required | Optional | Not Required |
|
EscalationValue |
The value of the product price escalation. |
NA |
Required if Escalation type is ORA_FIXED. |
Optional | Not Required |
|
EscalationValueExpression |
The value expression associated with product price escalation. |
Should be a valid SQL expression. The variable number should be enclosed in curly braces. Example1: {CPI_101} + {CPI_102} Example2: CASE WHEN {CPI_101} > 5 THEN {CPI_101} - 0.5 ELSE {CPI_101} END |
Required if Escalation type is ORA_MP_EXP |
Optional | Not Required |
|
EscalationStartDate |
The start date of the product price escalation. |
Will be calculated using the Start Offset |
Optional | Optional | Not Required |
|
EscalationStartOffsetDuration |
The offset duration for the escalation's start associated with product price. |
NA | Optional | Optional | Not Required |
|
EscalationStartOffsetPeriod |
The offset period for the escalation's start associated with product price. |
NA | Optional | Optional | Not Required |
|
EscalationEndDate |
The end date of the product price escalation. |
Will be calculated using the End Offset |
Optional | Optional | Not Required |
|
EscalationEndOffsetDuration |
The offset duration for the escalation end associated with product price. |
NA | Optional | Optional | Not Required |
|
EscalationEndOffsetPeriod |
The offset period for the escalation end associated with product price. |
NA | Optional | Optional | Not Required |
|
PricingTermEndDate |
The end date of the pricing term. |
NA | Optional | Optional | Not Required |
|
PricingTermEndOffsetDuration |
The offset duration for the pricing term's end date. |
NA | Optional | Optional | Not Required |
|
PricingTermEndOffsetPeriod |
The offset period for the pricing term's end date. |
NA | Optional | Optional | Not Required |
|
PricingTermDuration |
The duration of the pricing term. |
NA | Optional | Optional | Not Required |
|
PricingTermPeriod |
The period of the pricing term. |
NA | Optional | Optional | Not Required |
|
ChargeDefinition |
The charge definition code associated with product price escalations. |
NA | Optional | Optional | Not Required |
|
NextEvaluationDate |
The next evaluation date for a product price escalation. |
Not Updatable | Not Required | Not Required | Not Required |
| NextPricingTermStartDate |
The start date of the next pricing term associated to a product price escalation. |
Not Updatable | Not Required | Not Required | Not Required |
You can view the Subscription Product Price Escalation object 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 CSV templates available in the Import Objects UI page to create the source CSV file. To download a CSV template:
-
Go to .
-
Select the Subscription Product Price Escalation object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 .
-
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Subscription Product Price Escalation from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
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 .
-
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.