How You Upload Work Definition and Work Definition Operation Attachments Using a SOAP Service
This topic provides specifics for uptaking the ERP Object Attachment SOAP service for the manufacturing business entities work definition and work definition operation.
You can use the ERP Object Attachment SOAP service to perform an automatic, mass upload of attachments for discrete and process manufacturing work definitions. You specify the input parameters for the payload of this service to upload attachments to existing work definitions at the header or operation levels.
Request Payload
Here's a table with request payload information.
|
Element Name |
Type |
Description |
|---|---|---|
|
entityName |
String |
Valid business entity names are: WORK_DEFINITION, WORK_DEFINITON_OPERATION |
|
categoryName |
String |
Document Category Name associated with the business entity. |
|
allowDuplicate |
String |
Whether duplicate is allowed. Valid values are: Yes, No. |
|
attachmentRows |
List of elements, each containing the details of the attachment to upload. The details include the user keys, attachment type, and title. |
attachmentRows Attributes for Work Definition Header
Here's a table with attachmentRows Attributes for Work Definition Header information.
|
Attribute Name |
Type |
Description |
|---|---|---|
|
UserKeyA |
String |
Organization Code. |
|
UserKeyB |
String |
Item Number. |
|
UserKeyC |
String |
Work Definition Internal Name. |
|
UserKeyD |
String |
Keep this key with value #NULL. |
|
UserKeyE |
String |
Keep this key with value #NULL. |
|
AttachmentType |
String |
Valid values are: FILE, TEXT, URL. |
|
Title |
String |
The title of the attachment. |
|
Content |
String |
The following is an example. Your content may be different. URL: https://www.google.com Text: Use Lathe L123. File: Encode the source data to a Base64 string (Base64 encoding). |
attachmentRows Attributes for Work Definition Operation
Here's a table with attachmentRows Attributes for Work Definition Operation information.
|
Attribute Name |
Type |
Description |
|---|---|---|
|
UserKeyA |
String |
Organization Code. |
|
UserKeyB |
String |
Item Number. |
|
UserKeyC |
String |
Work Definition Internal Name. |
|
UserKeyD |
String |
Version Number. |
|
UserKeyE |
String |
Operation Sequence Number. |
|
AttachmentType |
String |
Valid values are: FILE, TEXT, URL. |
|
Title |
String |
The title of the attachment. |
|
Content |
String |
The following is an example. Your content may be different. URL: https://www.google.com Text: Use Lathe L123. File: Encode the source data to a Base64 string (Base64 encoding). |
Sample Payload for Work Definition Header
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/"
xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
<soapenv:Header/>
<soapenv:Body>
<typ:uploadAttachment>
<typ:entityName>WORK_DEFINITION</typ:entityName>
<typ:categoryName>MISC</typ:categoryName>
<typ:allowDuplicate>Yes</typ:allowDuplicate>
<!--Zero or more repetitions:-->
<typ:attachmentRows>
<!--Optional:-->
<erp:UserKeyA>M1</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>AS54888</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>ORA_MAIN</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>?</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>?</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>File1</erp:Title>
<!--Optional:-->
<erp:Content>Use Lathe L123.</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>Sample Payload for Work Definition Operation
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/"
xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
<soapenv:Header/>
<soapenv:Body>
<typ:uploadAttachment>
<typ:entityName>WORK_DEFINITION_OPERATION</typ:entityName>
<typ:categoryName>MISC</typ:categoryName>
<typ:allowDuplicate>Yes</typ:allowDuplicate>
<!--Zero or more repetitions:-->
<typ:attachmentRows>
<!--Optional:-->
<erp:UserKeyA>M1</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>AS54888</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>ORA_MAIN</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>1</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>10</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>Att001</erp:Title>
<!--Optional:-->
<erp:Content>Use Lathe L123.</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>Sample Payload for Work Definition Operation