Import Your Bill Plan and Revenue Plan Data

How You Map Your Source Data to Object Attributes

To import your bill plan and revenue plan data into Oracle Applications Cloud, you must 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:

Complete all the prerequisites for importing each attribute in your source data.
Have all parent records in place before importing child records.

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 option to uniquely identify an object record is through the public unique identifier. 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 bill plan and revenue plan object, the attribute is ContractPuid.

Required Attributes and Validations for the Bill Plan and Revenue Plan 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 bill plan and revenue plan records, prerequisite setup tasks for the attributes, and specific validations, if any, for bill plan and revenue plan import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Bill Plan and Revenue Plan Record	Updating an Existing Bill Plan and Revenue Plan Record
ContractPuid	The PUID of the contract for which the bill plan or revenue plan is being created or updated.	This must be a valid contract PUID.	Required	Not required
ExtSource	The external source of the bill or revenue plan.	This must be a valid combination of external source and key.	Required	Required
ExtKey	The external key of the bill or revenue plan.	This must be a unique combination of external source and key.	Required	Required
BillPlanName	The bill plan or revenue plan name.	N/A	Required	Not required
BillMethodId	The bill or revenue method ID.	This must be a valid bill method ID.	Required if bill method name isn't passed.	Not required
BillMethodName	The bill or revenue method name.	This must be a valid bill method name.	Required if bill method ID isn't passed.	Not required
BillToCustAcctId	The bill-to customer account ID of the bill plan.	This must be a valid customer account ID.	Required if customer account name isn't passed.	Not required
BillToCustAcctNumber	The bill-to customer account number of the bill plan.	This must be a valid customer account number.	Required if customer account ID isn't passed.	Not required
BillToContactId	The bill-to contact ID of the bill plan.	This must be a valid contact ID.	Required if contact name isn't passed.	Not required
BillToContactName	The bill-to contact name of the bill plan.	This must be a valid contact name.	Required if contact ID isn't passed.	Not required
BillToSiteUseId	The bill-to site use ID of the bill plan	This must be a valid party site use ID.	Required if party site use location isn't passed.	Not required
BillToSiteUseLocation	The bill-to site use location of the bill plan.	This must be a valid party site use location.	Required if party site use ID isn't passed.	Not required
InvoiceCurrencyOptCode	The billing currency type code of the bill plan.	This must be a valid currency type code.	Required if the currency type name isn't passed.	Not required
InvCurrOptMeaning	The billing currency type name of the bill plan.	This must be a valid currency type name.	Required if the currency type code isn't passed.	Not required
BillingCycleId	The billing cycle ID of the bill plan.	This must be a valid billing cycle ID.	Required if the billing cycle name isn't passed.	Not required
BillingCycleName	The billing cycle name of the bill plan.	This must be a valid billing cycle name.	Required if the billing cycle ID isn't passed.	Not required
PaymentTermId	The payment terms ID.	This must be a valid payment terms ID.	Required if the payment terms name isn't passed.	Not required
PaymentTermName	The payment terms name.	This must be a valid payment terms name.	Required if the payment terms ID isn't passed.	Not required
BillSetNum	The bill set of the bill plan.	N/A	Required	Not required
LaborInvoiceFormatId	The labor format ID of the bill plan.	This must be a valid labor format ID.	Required if the labor format name isn't passed.	Not required
LaborInvoiceFormatName	The labor format name of the bill plan.	This must be a valid labor format name.	Required if the labor format ID isn't passed.	Not required
NlInvoiceFormatId	The nonlabor format ID of the bill plan.	This must be a valid nonlabor format ID.	Required if the nonlabor format name isn't passed.	Not required
NlInvoiceFormatName	The nonlabor format name of the bill plan.	This must be a valid nonlabor format name.	Required if the nonlabor format ID isn't passed.	Not required
EventsInvoiceFormatId	The event format ID of the bill plan.	This must be a valid event format ID.	Required if the event format name isn't passed.	Not required
EventsInvoiceFormatName	The event format name of the bill plan.	This must be a valid event format name.	Required if the event format ID isn't passed.	Not required

You can view the bill plan and revenue plan 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 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 Bill Plan and Revenue Plan 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 Bill Plan and Revenue Plan 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 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.