How You Upload Attachments of Work Orders, Work Order Operations, Work Order Operation Materials, and Work Order Operation Resources Using a SOAP Service
This topic provides specifics for uptaking the ERP Object Attachment SOAP service for maintenance work orders, maintenance work order operations, maintenance work order operation materials, maintenance work order operation resources.
attachmentRows Attributes for Work Order Header
Here's a table with attachmentRows Attributes for Work Order Header information.
|
Attribute Name |
Type |
Description |
|---|---|---|
|
UserKeyA |
String |
Organization Code. |
|
UserKeyB |
String |
Work Order Number. |
|
UserKeyC |
String |
Keep this key with value #NULL. |
|
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 Order 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_ORDER</typ:entityName>
<typ:categoryName>MISC</typ:categoryName>
<typ:allowDuplicate>Yes</typ:allowDuplicate>
<!--Zero or more repetitions:-->
<typ:attachmentRows>
<!--Optional:-->
<erp:UserKeyA>MNTALM</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>MNTALM1167</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>?</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>?</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>?</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>BVM_Attachment</erp:Title>
<!--Optional:-->
<erp:Content>Hello World</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>attachmentRows Attributes for Work Order Operation
Here's a table with attachmentRows Attributes for Work Order Operation information.
|
Attribute Name |
Type |
Description |
|---|---|---|
|
UserKeyA |
String |
Organization Code. |
|
UserKeyB |
String |
Work Order Number. |
|
UserKeyC |
String |
Operation Sequence Number. |
|
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 Order 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_ORDER_OPERATION</typ:entityName>
<typ:categoryName>MISC</typ:categoryName>
<typ:allowDuplicate>Yes</typ:allowDuplicate>
<!--Zero or more repetitions:-->
<typ:attachmentRows>
<!--Optional:-->
<erp:UserKeyA>MNTALM</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>MNTALM1167</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>10</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>?</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>?</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>BVM_Attachment</erp:Title>
<!--Optional:-->
<erp:Content>Hello World</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>attachmentRows Attributes for Work Order Operation Material
Here's a table with attachmentRows Attributes for Work Order Operation Material information.
|
Attribute Name |
Type |
Description |
|---|---|---|
|
UserKeyA |
String |
Organization Code. |
|
UserKeyB |
String |
Work Order Number. |
|
UserKeyC |
String |
Operation Sequence Number. |
|
UserKeyD |
String |
Material Sequence Number. |
|
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 Order Operation Material
<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_ORDER_OPERATION_MATERIAL</typ:entityName>
<typ:categoryName>MISC</typ:categoryName>
<typ:allowDuplicate>Yes</typ:allowDuplicate>
<!--Zero or more repetitions:-->
<typ:attachmentRows>
<!--Optional:-->
<erp:UserKeyA>MNTALM</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>MNTALM1167</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>10</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>10</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>?</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>BVM_Attachment</erp:Title>
<!--Optional:-->
<erp:Content>Hello World</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>attachmentRows Attributes for Work Order Operation Resource
Here's a table with attachmentRows Attributes for Work Order Operation Resource information.
|
Attribute Name |
Type |
Description |
|---|---|---|
|
UserKeyA |
String |
Organization Code. |
|
UserKeyB |
String |
Work Order Number. |
|
UserKeyC |
String |
Operation Sequence Number. |
|
UserKeyD |
String |
Material Sequence Number. |
|
UserKeyE |
String |
Resource 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 Order Operation Resource
<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_ORDER_OPERATION_RESOURCE</typ:entityName>
<typ:categoryName>MISC</typ:categoryName>
<typ:allowDuplicate>Yes</typ:allowDuplicate>
<!--Zero or more repetitions:-->
<typ:attachmentRows>
<!--Optional:-->
<erp:UserKeyA>MNTALM</erp:UserKeyA>
<!--Optional:-->
<erp:UserKeyB>MNTALM1167</erp:UserKeyB>
<!--Optional:-->
<erp:UserKeyC>10</erp:UserKeyC>
<!--Optional:-->
<erp:UserKeyD>10</erp:UserKeyD>
<!--Optional:-->
<erp:UserKeyE>?</erp:UserKeyE>
<!--Optional:-->
<erp:AttachmentType>TEXT</erp:AttachmentType>
<!--Optional:-->
<erp:Title>BVM_Attachment</erp:Title>
<!--Optional:-->
<erp:Content>Hello World</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>