Example of Importing Recurring Revenue Data

You can use import management to create, update, and delete recurring revenue data. Recurring schedules in opportunities enables you to enter and track opportunity products or product groups that are part of a subscription business model.

For more information see Overview of Recurring Opportunity Products in the Related Topics section.

How You Map Your Source Data to Target Object Attributes

To import your recurring revenue 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 must 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.

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 opportunity revenues or are updating opportunity revenues that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Importing Recurring Revenue Data

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 recurring revenue data records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Tasks or Import Validations	Creating a Recurring Revenue Record	Updating a Recurring Revenue Record	Deleting a Recurring Revenue Record
RevnId	The unique identifier of the summary revenue for this Opportunity.	Not applicable	Conditionally Required Either RevnNumber or RevnId must be passed for identifying a record of Opportunity revenue. If both are passed then only the RevnId field is checked. Not passing either of these results in error.	Conditionally Required Either RevnNumber or RevnId must be passed for identifying a record of Opportunity revenue. If both are passed then only the RevnId field is checked. Not passing either of these results in error.	Conditionally Required Either RevnNumber or RevnId must be passed for identifying a record of Opportunity revenue. If both are passed then only the RevnId field is checked. Not passing either of these results in error.
OptyId	The unique identifier for the existing opportunity record in the destination table.	You can obtain the OptyId for an existing opportunity by exporting the Opportunity object by navigating to the following in the Setup and Maintenance work area: Offering: Sales Functional Area: Data Import and Export Task: Schedule Export Processes	Conditionally Required Either OptyId or OptyNumber is required.	Not Required	Not Required
OptyNumber	The public unique identifier of the opportunity.	Not applicable.	Conditionally Required Either OptyId or OptyNumber is required.	Not Required	Not Required
RevnNumber	The alternate unique identifier of the revenue.	Identify the Revenue Number for an existing opportunity revenue using the Revenue Management work area and by exporting the Revenue object by navigating to the following in the Setup and Maintenance work area: Offering: Sales Functional Area: Data Import and Export Task: Schedule Export Processes	Conditionally Required Either RevnNumber or RevnId must be passed for identifying a record of Opportunity revenue. If both are passed then only the RevnId field is checked. Not passing either of these results in error.	Conditionally Required Either RevnNumber or RevnId must be passed for identifying a record of Opportunity revenue. If both are passed then only the RevnId field is checked. Not passing either of these results in error.	Conditionally Required Either RevnNumber or RevnId must be passed for identifying a record of Opportunity revenue. If both are passed then only the RevnId field is checked. Not passing either of these results in error.
RecurFrequencyCode	The code that indicates the frequency of recurrence for the child revenue.	A list of valid values is defined in the lookup MOO_RECURRING_FREQUENCY.	Required	Not Required	Not Required
RecurNumberPeriods	The number of times the child revenue should recur.	None	Conditionally Required Either RecurNumberPeriods or RecurEndDate is required	Not Required	Not Required
RecurEndDate	The date when the child revenue recurrence ends.	None	Conditionally Required Either RecurNumberPeriods or RecurEndDate is required	Not Required	Not Required
RecurStartDate	The date when the recurrence starts.	None	Conditionally Required Either RecurStartDate or EffectiveDate is required	Not Required	Not Required
EffectiveDate	The date when the child revenue closes.	None	Conditionally Required Either RecurStartDate or EffectiveDate is required	Not Required	Not Required
ScheduleAction	The transient attribute. Need to pass a value to indicate the action to be taken on recurring schedule such as ADD and DELETE.	None	Required	Not Required	Required

Sample Input CSV File

You include the data that you want to import into Sales and Fusion Service in a source CSV file. Here is a sample .csv file to import recurring revenue data:

OptyNumber	RevnId	RecurFrequencyCode	RecurNumberPeriods	EffectiveDate	ScheduleAction
CDRM_123532	300100546223965	MONTHLY	3	12/25/2021	ADD

Create the Import Activity

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

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 Opportunity Revenue 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.