How do I import subscription product bill line data?

You can use import management to create or update Subscription Product Bill records.

To import Subscription Product Bill 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 Bill 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

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 for uniquely identifying 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 Subscription Product Bill object, the attributes are CoveredLevelPuid, PrePaymentNumber and SequenceNumber.

Required Attributes and Validations for Subscription Product Bill 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 Bill records, required attributes for updating Subscription Product Bill records, prerequisite setup tasks for the attributes, and specific validations, if any, for Subscription Product Bill import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Subscription Product Bill Record	Updating an Existing Subscription Product Bill Record
DateBilledTo	The date up to which the subscription product is billed	This must be a valid date.	Required	Not required
RecurringFlag	Option indicating whether this line is recurring. Note: Pass recurring flag as 'Y' if you need to create Credit Memo.	Y or N	Required	Not required
BillingPeriod	The billing period	This must be a positive number and unique for the product.	Required	Not required
DateToInterface	The date to interface	This must be a valid date.	Not Required	Not required
DateBilledFrom	The date from which the subscription product is billed	This must be a valid date.	Required	Not required
BillLineId	The bill line ID	Do not pass any value.	Not Required	Not required
InterfacedFlag	Option indicating whether the bill line is interfaced	Y or N	Required	Not required
SubscriptionProductPuid	The subscription product PUID	This must be a valid subscription product PUID.	Required	Not required
SubscriptionId	The subscription ID.	Do not pass any value.	Not Required	Not required
SubscriptionProductId	The subscription product ID.	Do not pass any value.	Not required	Not required
BillLinePuid	The bill line PUID.	This must be a unique bill line PUID.	Required	Required
Amount	The amount	This must be a positive number.	Required	Not required
UsageFlag	Option indicating whether the line is a usage line.	Y or N	Required	Not required
UsageAcquiredFlag	Option indicating whether the usage has been acquired.	Y or N	Not required	Not required
UsagePricedFlag	Option indicating whether usage line has been priced.	Y or N	Not required	Not required
TransactionClass	The transaction class.	This must be INV for invoice and CM for credit memo.	Required	Not required
TransactionTax	The transaction tax.	This must be a positive number.	Not required	Not required
TransactionAmount	The transaction amount.	This must be a positive number.	Not required	Not required
InvoiceBillLineId	The invoice bill line ID.	Do not pass any value.	Not required	Not required
UsageCaptureDate	The usage capture date.	This must be a valid date.	Not required	Not required
UsageQuantity	The usage quantity.	This must be a positive number.	Not required	Not required
ChargePeriod	The charge period.	This must be a valid charge period.	Not required	Not required
PricingError	The pricing error.	Do not pass any value.	Not required	Not required
ListPrice	The list price.	This must be a positive number when TransactionClass is INV and a number when it's CM.	Required	Not required
RevenueLineId	The revenue line ID.	Do not pass any value.	Not required	Not required
TransactionClassMeaning	The meaning of transaction class lookup.	Invoice or Credit Memo	Not required	Not required
InvoiceDate	The invoice date.	This must be a valid date.	Not required	Not required
NewCreditMemoPUID	The credit memo PUID.	Do not pass any value.	Not required	Not required
CreditMemoAmount	The credit memo amount.	Do not pass any value.	Not required	Not required
CreditMemoFlag	The credit memo option.	Do not pass any value.	Not required	Not required
CreditMemoReason	The credit memo reason.	Do not pass any value.	Not required	Not required
CustomerTrxTypeSequenceId	The customer transaction type sequence ID.	This must be a number.	Not required	Not required
CoveredLevelId	The covered level ID.	Do not pass any value.	Not required	Not required
ChargeId	The charge ID.	This must be a valid charge ID.	Required	Not required

You can view the Subscription Product Bill 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.

Note: Total cost value (TCV) isn't automatically calculated while importing bill lines. You need to manually calculate it and add it to header and product level. You can automatically calculate the TCV and generate bill line by setting Generate Billing to Y in header.

Note: To import Subscription Bill Line Credit memo, you must include BillLinePuid, CreditMemoAmount, CreditMemoFlag, and CreditMemoReason attributes in the CSV file. The BillLinePuid should be the PUID of the existing Invoice Bill Line for which a Credit memo needs to be added.

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 Subscription Product Bill 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 Subscription Product Bill 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.