Attachment Information

Provide the elements details like Entity Name, Category Name and User Keys for unique identification of business object to which the Attachment need to be uploaded. In addition the element also contains the attachment(s) details like Attachment Content, Attachment Type and Attachment Title.

QName: {http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/}AttachmentDetails

Relationships

The following table describes how this service data object is related to other service data objects or business object services.

Relationship Type	Object or Service
Handled by	ERP Object Attachment Service

Attributes

The following table describes attributes in the service data object.

Name	Type	Description
AttachmentType	string	Indicates the specific type of attachment to be uploaded. The supported attachment types are FILE, TEXT, or URL. Primary Key
Content	string	The attachment content. Text or URL can be mentioned for attachment. Provide base64 encoded string for file attachments.
Title	string	Indicates the title of the attachment that imply Attachments of any type such as FILE, TEXT or URL must have a title.
UserKeyA	string	Indicates one of up to five values corresponding to the business entity attribute through which an attachment(s) can be uploaded by uniquely identifying the business object. The values of the user keys are dependent on the seeded data provided by distinct product application areas of specific business entities. For example, in order to upload attachments to the header level of a supplier invoice, it may be necessary to provide the business unit as one of the user key in order to uniquely identifying the header row and upload an attachment to the header level.
UserKeyB	string	Indicates one of up to five values corresponding to the business entity attribute through which an attachment(s) can be uploaded by uniquely identifying the business object. The values of the user keys are dependent on the seeded data provided by distinct product application areas of specific business entities. For example, in order to upload attachments to the header level of a supplier invoice, it may be necessary to provide the business unit as one of the user key in order to uniquely identifying the header row and upload an attachment to the header level.
UserKeyC	string	Indicates one of up to five values corresponding to the business entity attribute through which an attachment(s) can be uploaded by uniquely identifying the business object. The values of the user keys are dependent on the seeded data provided by distinct product application areas of specific business entities. For example, in order to upload attachments to the header level of a supplier invoice, it may be necessary to provide the business unit as one of the user key in order to uniquely identifying the header row and upload an attachment to the header level.
UserKeyD	string	Indicates one of up to five values corresponding to the business entity attribute through which an attachment(s) can be uploaded by uniquely identifying the business object. The values of the user keys are dependent on the seeded data provided by distinct product application areas of specific business entities. For example, in order to upload attachments to the header level of a supplier invoice, it may be necessary to provide the business unit as one of the user key in order to uniquely identifying the header row and upload an attachment to the header level.
UserKeyE	string	Indicates one of up to five values corresponding to the business entity attribute through which an attachment(s) can be uploaded by uniquely identifying the business object. The values of the user keys are dependent on the seeded data provided by distinct product application areas of specific business entities. For example, in order to upload attachments to the header level of a supplier invoice, it may be necessary to provide the business unit as one of the user key in order to uniquely identifying the header row and upload an attachment to the header level.