1. Implementing Order Management
  2. Update Extensible Flexfields During Fulfillment

Update Extensible Flexfields During Fulfillment

Call the FulfillmentResponse web service to update an extensible flexfield on a sales order after your user already submitted the sales order to fulfillment.

Make the call only when the orchestration process is on a wait step.

Here's an example payload.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Body>
         <ns1:FulfillmentRequest
xmlns:ns1="http://xmlns.oracle.com/apps/scm/doo/taskLayer/fulfillOrder/DooTaskFulfillOrderResponseInterfaceComposite">
             <ns1:FLine
xmlns:ns2="http://xmlns.oracle.com/apps/scm/doo/common/process/model/">
                 <!-- Mandatory attributes 3 below, make sure you provide the correct value--> <ns2:FulfillLineId>300100095720462</ns2:FulfillLineId>
<ns2:SourceOrderSystem>LEG</ns2:SourceOrderSystem>
<ns2:TaskType>FulfillOrder</ns2:TaskType>
                 <!-- Optional attributes -->
                 <ns2:OrderedQuantity unitCode="">11</ns2:OrderedQuantity>
                 <ns2:RecordNumber>1</ns2:RecordNumber>
                 <!-- Mandatory attributes assuming you want to update EFFs -->
                 <ns2:AdditionalFulfillLineInformationCategories
xsi:type="ns12:j_FulfillLineEffDooFulfillLinesAddInfoprivate" 
xmlns:ns12="http://xmlns.oracle.com/apps/scm/doo/processOrder/flex/fulfillLineCategories/" 
xmlns:ns22="http://xmlns.oracle.com/apps/scm/doo/processOrder/flex/fulfillLineContextsB/" 
xmlns:ns8="http://xmlns.oracle.com/apps/scm/doo/processOrder/model/" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ns8:Category>DOO_FULFILL_LINES_ADD_INFO</ns8:Category>
                     <!-- Nodes below repeats for each of the context that you want to update -->
                     <!-- The node itself contains the name of the virtual object for the context-->
                     <!-- To get these details, run the Publish Extensible Flexfields scheduled process-->
                     <!-- This example assumes  you are updating two contexts --> <ns12:FulfillLineEffBPackShipInstructionprivateVO>
<ns8:ContextCode>PackShipInstruction</ns8:ContextCode>
<ns22:_PackingInstruction>NKResponsePack</ns22:_PackingInstruction>
<ns22:_ShippingInstruction>NKResponseShip</ns22:_ShippingInstruction>
<ns22:_ShippingCost>31</ns22:_ShippingCost>
<ns22:_NeedbyDate>2016-04-21</ns22:_NeedbyDate>
<ns22:_PickDate>2016-04-21T12:12:12</ns22:_PickDate>
</ns12:FulfillLineEffBPackShipInstructionprivateVO>
<ns12:FulfillLineEffBFulfillLineContext1privateVO>
<ns8:ContextCode>FulfillLineContext1</ns8:ContextCode>
<ns22:_FL1AttributeChar1>FLC1-Resp</ns22:_FL1AttributeChar1>
<ns22:_FL1AttributeChar2>FLC2-Resp</ns22:_FL1AttributeChar2>
<ns22:_FL1AttributeNum1>620</ns22:_FL1AttributeNum1>
<ns22:_FL1AttributeDate1>2016-03-13</ns22:_FL1AttributeDate1>
<ns22:_FL1AttributeDateTime1>2016-03-13T12:12:12</ns22:_FL1AttributeDateTime1>
</ns12:FulfillLineEffBFulfillLineContext1privateVO>
</ns2:AdditionalFulfillLineInformationCategories>
             </ns1:FLine>
         </ns1:FulfillmentRequest>
     </soap:Body>
</soap:Envelope>

where

  • FulfillLineId identifies your fulfillment line, such as 300100095720462.

  • SourceOrderSystem identifies your source system, such as LEG.

  • Replace values for other attributes, as necessary, such as PackingInstruction, dates, times, and so on.

Related Topics