Import Your Attachment Data

You can use Import Management to create, update, or delete Attachment records.

You can import attachment records using these steps:

Map your source attachment data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
Create the source CSV file with the attachment data you want to import.
Kick off an import activity.
Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

You import attachment data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

Before you create the source data file, you should:

Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the attachment import object.
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
Know how you can uniquely identify the records.
Check the target object attributes 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 attachment object, the attribute is PartyNumber and shows up in the UI as Party Number. 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 attachments or are updating attachments that have source system reference data, then provide the source system and source system reference values. For attachment object, these are SourceSystem and SourceSystemReferenceValue and show up as Party Source System and Party Source System Reference Value in the UI.

Required Attributes and Validations for Attachment 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 attachment records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating an Attachment record	Updating an Existing Attachment record
PK!Value	This is the primary key of the record to which the attachment is being associated.	When creating or updating attachments, the parent record to which the attachment is associated must exist in the database.	Either Pk1Value or PUID is mandatory.	Either Pk1Value or PUID is mandatory.
ObjectPUID	This is the public unique identifier of the record to which the attachment is being associated.	When creating or updating attachments, the parent record to which the attachment is associated must exist in the database.	Either Pk1Value or PUID is mandatory.	Either Pk1Value or PUID is mandatory.
Category	Category to which the attachment belongs. If you don't specify a value, the default is considered. For example, the default attachment category for lead is MKL_LEAD_CATEGORY.A source system reference that's the unique ID of the Attachment in your legacy or external system.	If passing the category, it should be a valid category for that object.	Not required If you don't provide a value, the default is used.	Not required If you don't provide a value, the default is used.
Description	A brief description of the attachment.	This can be any string of specified length.	Not Required	Not required
FileName	Name of the attachment file in which the attachment is stored.	This can be any string of specified length.	Either the File name or the URL is mandatory.	Either the File name or the URL is mandatory.
PK2 Value	This is the primary key of the record to which the attachment is being associated.	This is useful when the object has a composite primary key.	This is useful when the object has a composite primary key.	This is useful when the object has a composite primary key.
PK3 Value	This is the primary key of the record to which the attachment is being associated.	This is useful when the object has a composite primary key.	This is useful when the object has a composite primary key.	This is useful when the object has a composite primary key.
PK4 Value	This is the primary key of the record to which the attachment is being associated.	This is useful when the object has a composite primary key.	This is useful when the object has a composite primary key.	This is useful when the object has a composite primary key.
PK5 Value	This is the primary key of the record to which the attachment is being associated.	This is useful when the object has a composite primary key.	This is useful when the object has a composite primary key.	This is useful when the object has a composite primary key.
URL	If the attachment type is url, this specifies the url.	The URL format is validated.	Either the file name or the URL is mandatory.	Either the file name or the URL is mandatory.

For more information on importing an attachment, see the topic Import Attachments in the related links section.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the attachment object. The page also lists attribute information like type, length, description, and so on.

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 Attachment 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 attachment 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 Attachment 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.