Import Your MDF Request Data

How You Map Your Source Data to Target Object Attributes

To import your MDF Request 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 Requests. 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 Request object, the attributes are Fund Request ID, Partner 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 Request object, the attributes are Owner Party Number and Partner Company Number.

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

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a MDF Request Record	Updating an Existing MDF Request Record
Fund Request ID	System generated unique fund request identifier	This is automatically derived from the import process when importing a new MDF request.	Not required	Required
Owner Party Number	A unique public identifier for the owner party number	None	A value is required for a new MDF request with any Status Code.	Required
Partner Company Number	A unique public identifier for the partner company number	None	A value is required for a new MDF request with any Status Code.	A value is required, when updating the partner of an MDF request in the Draft Status Code.
Name	Specifies the name of the fund request	None	A value is required when importing a new MDF request.	Not required
Currency	Specifies the transaction currency for MDF request amounts	If providing a value, the value must exist in the CURRENCY_CODE column of the FND_CURRENCIES_VL table. You can view valid currency codes. Navigate to the following in the Setup and Maintenance work area: Offering: Sales Functional Area: Data Import and Export Task: Manage Currencies	A value is required when importing a new request with any Status Code.	A value is required when updating a request with Status Code Draft or Returned.
Requested Amount	Specifies the amount requested by the MDF request	None	Required	A value is required when updating the requested amount of a request with Status Code Draft or Returned.
Partner	Identifies the partner associated with the MDF request	None	Not required	Not required
Partner ID	Identifies the partner for the MDF request	None	A value is required for a new MDF request with any Status Code.	A value is required when you're updating the partner of an MDF request in the Draft Status Code.
Owner ID	Identifies the owner for the MDF request	None	A value is required for a new MDF request with any Status Code.	Required
Owner	Identifies the owner of the MDF request	None	Not required	Not required
Code	Unique MDF fund request identifier	None	Conditionally required if you're providing a request name for a new MDF budget.	A value is required if you're updating an existing MDF request and you're not providing the unique MDF request ID.

You can view the MDF Request 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 Request 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 Request 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.