Import Your Contract Billing Milestone Data

You can use Import Management to create update, or delete Project Contract Billing Milestone records.

To import Milestone 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 Project Contract Billing Milestone 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 Project Contract Billing Milestone 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 Project Contract Billing Milestone records, required attributes for updating or deleting Milestone records, prerequisite setup tasks for the attributes, and specific validations, if any, for Milestone import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Project Contract Billing Milestone Record	Updating an Existing Project Contract Billing Milestone Record	Deleting an Existing Project Contract Billing Milestone Record
LinePuid	The unique PUID that identifies the contract line.	This must be a valid PUID.	Required	Not Required	Not Required
ExternalSourceKey	The external source of the milestone information.	The external source and key combination must be unique.	Required A combination of external source and external key is required.	Required	Required
ExternalReferenceKey	The external key of the milestone information.	The external source and key combination must be unique.	Required A combination of external source and external key is required.	Required	Required
MilestoneName	The name of the milestone.	No validation	A value is required if you're creating a new milestone on a contract line, as opposed to adding an existing project plan milestone to the contract line.	Not Required	Not Required
ProjectId	The unique identifier of the project that owns the milestone.	The project must have an active association to the contract line.	Required if ProjectNumber isn't entered.	Not Required	Not Required
ProjectNumber	The number of the project that owns the milestone.	The project must have an active association to the contract line.	Required if ProjectId isn't entered.	Not Required	Not Required
ParentTaskId	The unique identifier of the project plan parent task under which the milestone is created.	The parent task of a milestone must be on or below the level at which the project is associated with the contract line. Don't populate this attribute if you want to create a milestone with the project as the parent.	Either ParentTaskId or ParentTaskNumber is required if the project is associated to the contract line at a task level.	Not Required	Not Required
ParentTaskNumber	The unique number of the project plan parent task under which the milestone is created.	The parent task of a milestone must be on or below the level at which the project is associated with the contract line. Don't populate this attribute if you want to create a milestone with the project as the parent.	Either ParentTaskId or ParentTaskNumber is required if the project is associated to the contract line at a task level.	Not Required	Not Required
PlannedFinishDate	The expected finish date of the milestone.	The planned finish date must be within the effective dates of the milestone's parent in the project plan if the Automatically Roll Up Task Planned Dates setting is not enabled. The planned finish date must also be within the effectivity dates of the contract line. If the milestone is for an Award, then the planned finish date must be on or after the earlier of the preaward date or the contract line start date and on or before the later of the close date or contract line end date.	A value is required if you're creating a new milestone on a contract line, as opposed to adding an existing project plan milestone to the contract line.	Not Required	Not Required
MilestoneAmount	The bill transaction amount for the milestone.	No validation	Required	Not Required	Not Required
TransactionCurrency	The currency code of the bill transaction amount for the milestone.	The bill transaction currency must be the same as the contract currency for milestones.	Required	Not required	Not Required
EventTypeId	The unique identifier of the event type of the billing event created for the milestone.	The event type must be active as of the current date. Event types with the Allow Item option enabled can't be used for milestones.	Required if EventTypeName isn't entered.	Not Required	Not Required
EventTypeName	The name of the event type of the billing event created for the milestone.	The event type must be active as of the current date. Event types with the Allow Item option enabled can't be used for milestones.	Required if EventTypeId isn't entered.	Not Required	Not Required
ProjectPlanMilestoneId	The unique identifier of the milestone in the project plan.	The project plan milestone must be billable, lowest-level in the project plan, have no duration, isn't in a Complete status, and isn't already associated to a contract line.	To add an existing project plan milestone to a contract line, either ProjectPlanMilestoneId or ProjectPlanMilestoneNumber is required.	Not Required	Not Required
ProjectPlanMilestoneNumber	The unique number of the milestone in the project plan.	The project plan milestone must be billable, lowest-level in the project plan, have no duration, isn't in a Complete status, and isn't already associated to a contract line.	To add an existing project plan milestone to a contract line, either ProjectPlanMilestoneId or ProjectPlanMilestoneNumber is required.	Not required	Not Required

You can view the Project Contract Billing Milestone 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 Project Contract Billing Milestone 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 Project Contract Billing Milestone 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.