Import Your MDF Claim Data

How You Map Your Source Data to Target Object Attributes

To import your MDF Claim 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 options to uniquely identify an object record are as follows

Internal ID: If you're identifying a record that already exists in Oracle Applications Cloud, then you can use the internal ID of the record, a system-generated unique identifier Attributes with "id" in the attribute name are typically internal IDs. Use this option only if you're updating MDF Claims. You can determine the internal ID of a record by exporting Oracle Applications Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the MDF Claim object, the attributes are Claim ID, Fund Request ID, and Owner ID.
Public unique identifiers: 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 MDF Claim object, the attribute is Owner Party Number.

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

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a MDF Claim Record	Updating an Existing MDF Claim Record
Claim ID	This is a system generated unique identifier to identify the MDF Claim.	This is automatically derived from the import process when you import a new MDF claim.	Not required	A value is required if you're not providing an identifier for the MDF claim.
Fund Request Code	Unique fund request identifier	If provided, the Status Code of the FundRequestCode must be either Approved or Terminated.	A value is required when importing a new MDF claim and you're not providing the unique identifier of the request.	Not required
Owner Party Number	A unique public identifier for the owner number	None	Conditionally required For a new MDF claim with any StatusCode, provide either the Owner ID or the, Owner Party Number.	Conditionally required When updating the owner of an MDF claim, provide either the Owner ID or the Owner Party Number.
Budget	Identifies the MDF budget associated with the claim	None	Not required	Not required
Fund Request ID	Identifies the fund request to which the MDF claim is associated	If provided, the Status Code of the fund request ID must be Approved or Terminated.	A value is required when importing a new MDF claim with any Status Code.	Not required
Name	Identifies the name of the MDF claim.	None	Required	Not required
Currency	The code that represents the currency for the MDF claim	None	Not required	Not required
Requested Amount	Specifies the amount for the MDF claim	None	Required	A value is required when updating the requested amount of an MDF claim with Status Code Draft or Returned.
MDF Request	Specifies the name for the fund request	None	A value is required when importing a new MDF claim.	Not required
Owner ID	Identifies the owner for the MDF claim	None	Conditionally required For a new MDF claim with any StatusCode, provide either the Owner ID or the Owner Party Number.	Conditionally required When updating the owner of an MDF claim, provide either the Owner ID or the Owner Party Number.
Owner	Identifies the owner of the MDF claim	None	Required	Not required
Status	Identifies the current status of the MDF claim such as Draft, Submitted, Pending Approval, Approved, or Rejected	This defaults to Draft when creating a new MDF claim.	Required	Not required
Conversion Rate to Budget	Specifies the conversion exchange rate. Stores the currency exchange rate used for converting the user entered currency on the MDF claim to the CRM corporate currency	None	Not required	Not required
Code	Unique MDF claim identifier.	None	Not required	A value is required if updating an existing MDF claim and you're not providing any other identifier for the MDF claim.

You can view the MDF Claim 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: When you create a record in the "Draft" status, it can't be moved directly to a terminal status such as "Approved", "Rejected", "Terminated", "Withdrawn" or "Returned". It should be converted from the "Draft" status to the OOTB defined status "Pending Approval" before it can be moved to a terminal status. You can create a record in any status except "Pending Approval".

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 MDF Claim 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 MDF Claim 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.