How You Upload Attachments of Work Definitions and Work Definition Operations Using a SOAP Service
This topic provides specifics for uptaking the ERP Object Attachment SOAP service for maintenance work definitions and maintenance work definition operations.
attachmentRows Attributes for Work Definition Header
Here's a table with attachmentRows Attributes for Work Definition Header information.
|
Attribute Name |
Type |
Description |
|---|---|---|
|
UserKeyA |
String |
Work Method Code. |
|
UserKeyB |
String |
Organization Code. |
|
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). |
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>MAINTENANCE</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>MNTALM</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>ReplaceSwitch</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>?</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>?</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>Att01</erp:Title>
<!--Optional:-->
<erp:Content>Hello MNT Folks, Howdy?</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>attachmentRows Attributes for Work Definition Operation
Here's a table with attachmentRows Attributes for Work Definition Operation information.
|
Attribute Name |
Type |
Description |
|---|---|---|
|
UserKeyA |
String |
Work Method Code. |
|
UserKeyB |
String |
Organization Code. |
|
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 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>MAINTENANCE</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>MNTALM</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>ReplaceSwitch</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>Hello World</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>