Oracle Fusion Logistics: Web Services For Integration With Execution Systems

Oracle Fusion Logistics
Web Services
for
Integration with Execution Systems
Applications Release: 11.1.11.0.0
1. Introduction ..........................................................................................................................................4
1.1 List of relevant External Services in Fusion Logistics ..............................................................4
2. Send Receipt Advice ............................................................................................................................5
2.1 Overview ....................................................................................................................................5
2.2 Service Operations .....................................................................................................................6

2.2.1 getReceiptAdviceDetails .......................................................................................................................... 6
2.3 Components of Input Payload ....................................................................................................6
2.4 Components of Response Payload .............................................................................................7
2.5 Sample Input Payloads ...............................................................................................................9

2.5.1 Search for expected shipments using Purchase Order Header and Line .................................................. 9
2.5.2 Search expected shipments due today and next three days for a supplier ................................................ 9
2.5.3 Search expected shipments due today for an item and all document types ............................................ 10
2.5.4 Search expected shipments due today for all document types ............................................................... 10
2.5.5 Search expected shipments for a Transfer Order number ...................................................................... 10
2.5.6 Re-send receipt advice for a Purchase Order ......................................................................................... 11
2.6 Sample Output Response of Send Receipt Advice ..................................................................11
2.6.1 Receipt Advice response with expected shipments for a Purchase Order .............................................. 11
2.6.1 Receipt Advice response for in-transit shipment with lot and serials .................................................... 13
3. Receive Receipt Confirmation ..........................................................................................................17
3.1 Overview ..................................................................................................................................17
3.2 Service Operations ...................................................................................................................17

3.2.1 processReceiptConfirmations ................................................................................................................ 17
3.3 Components of Input Payload ..................................................................................................17
3.5 Components of Response Payload ...........................................................................................19
3.6 Sample Input Payloads .............................................................................................................20

3.6.1 Receipt Confirmations for a Purchase Order ......................................................................................... 20
3.6.2 Receipt Confirmation for In-transit Shipment........................................................................................ 20
3.6.3 Receipt Confirmation for a Transfer Order Shipment ............................................................................ 21
3.6.4 Receipt confirmation for RMA .............................................................................................................. 22
3.6.5 Receipt Confirmation with all transactions interfaced from Execution System ..................................... 23
3.7 Sample Output Response of Receive Receipt Confirmation Service ......................................25
3.7.1 Sample response when receipt confirmation is interfaced successfully ................................................. 25
4. Transaction Manager Service ...........................................................................................................27
4.1 Overview ..................................................................................................................................27

4.2.1 insertAndProcessInterfaceRows ............................................................................................................ 27
4.2.1.1 Components of Input Payload ................................................................................................................ 27
4.2.1.2 Example of Response Payload ............................................................................................................... 28
4.2.1.3 Sample Input Payloads ........................................................................................................................... 29
4.2.2 processInventoryTransaction ................................................................................................................. 30
4.2.2.1 Components of Input Payload ................................................................................................................ 30
4.2.2.2 Example of Response Payload ............................................................................................................... 30
4.2.2.3 Sample Input Payload ............................................................................................................................ 31
5. Shipment Line Service .......................................................................................................................32
5.1 Overview ..................................................................................................................................32

5.2.1 generateShipmentRequest .................................................................................................................... 32

5.5.1 Select shipment lines using Pick Batch .................................................................................................. 39
5.5.2 Select shipment lines using Organization .............................................................................................. 39
5.5.3 Select shipment lines using Release Rule .............................................................................................. 39
5.6 Sample Output Response of Generate Shipment Request .......................................................40
5.6.1 Generate Shipment Request response with selected Shipment Lines for a Pick Batch .......................... 40
6. Shipment Service ................................................................................................................................45
6.1 Overview ..................................................................................................................................45

6.2.1 createAndConfirm .................................................................................................................................. 45

6.5.1 Shipment Confirmation for Plain Item ................................................................................................... 89
6.5.1 Shipment Confirmation for Plain/Lot/Serial Controlled Item ................................................................ 90
6.6 Sample Output Response of CreateAndConfirm Operation ....................................................92
6.6.1 Sample response when Shipment Confirmation is interfaced successfully ............................................ 92
1. Introduction
This document lists and details relevant external web services provided by Oracle Fusion Logistics in Oracle Fusion
Applications release 11.1.11.0.0 (Release 11) that will help integration with external Execution Systems (such as WMS). Sample
payloads for invoking these web services are provided. The services come from Fusion Logistics products, Receiving, Inventory and
Shipping.
1.1 List of relevant External Services in Fusion Logistics

In Fusion Applications release 11.1.11.0.0, the following external web services relevant for
Execution Systems integration are available from Fusion Logistics:
 Send Receipt Advice
o Service to retrieve eligible expected shipment lines from Fusion Receiving that
need to be interfaced with Execution System.
 Receive Receipt Confirmation
o Service to receive receipt confirmations on expected shipment lines into Fusion

Receiving from Execution System.
 Transaction Manager Service
o Service to process material transactions in Fusion Inventory.
 Shipment Line - generateShipmentRequest
o Service to retrieve eligible expected shipment lines from Fusion Shipping that need
to be interfaced with Execution System.
 Shipment - createAndConfirm
o Service to accept shipment confirmation on shipment lines into Fusion Shipping

from Execution System.
2. Send Receipt Advice
2.1 Overview
The principal intent of the Send Receipt Advice service is to communicate expected shipment lines
to an Execution System, such as WMS system. The service provides users a mechanism to choose
which lines to be transmitted by providing attributes that the user can search on. A Receipt Advice is
an expected shipment line that the external party awaits and maps to a Purchase Order, inter-
organization in-transit shipment, Transfer Order inbound shipment or a RMA. This service constructs
the receipt advice in the SDO (service data object) format and hand it off to the Execution System,
who will also be able to invoke this service with minimal criteria on a frequent basis in which case,
this service will fetch the open expected shipment lines based on criteria like document number,
supplier, due date and send them as a group.
The service provides the following attributes to filter the expected receipt advices on:
 Purchase Order related – Purchase Order Number, PO Line Number, PO schedule Number
 Transfer Order related –Transfer Order number, Transfer order line number
 RMA related – RMA number, RMA line number
 In-transit shipment related – In-transit shipment number, in-transit shipment line number
 Supplier
 Supplier site
 Customer
 Item number
 Receiving location
 Due date
 Carrier
The receiving organization which the expected shipment lines belong to, must be mandatorily
provided. Without the receiving organization the service will not generate
The service does not support blind queries. You need to provide at least one of the following
attributes when invoking the service to fetch the expected shipment lines/receipt advices.
 Purchase Order
 In-transit Shipment
 RMA
 Transfer Order
 Supplier
 Customer
 Item
 Due Date
2.2 Service Operations

The URL for the Send Receipt Advice service is http://<server-name>:<port-
number>/rcvReceiptAdvice/ReceiptAdviceService. This has one operation getReceiptAdviceDetails
and its asynchronous version getReceiptAdviceDetailsAsync.
2.2.1 getReceiptAdviceDetails
The Send Receipt Advice service has one operation getReceiptAdviceDetails and its asynchronous
equivalent is getReceiptAdviceDetailsAsync.
2.3 Components of Input Payload
 ns1:ReceiptAdviceParameter – This node or object represents the criteria of the expected

shipment lines to be included in the outbound receipt advice. The attributes that you
populated as part of this node will be used to filter the open expected shipments and prepare
the response.
 Note: For each attribute, the ReceiptAdviceParameter input payload provides both
Number/Code as well as internal identifiers. Providing internal identifiers is optional. But
when these internal identifiers are provided, the query operation responds faster as
compared to when number/code attributes are provided. Some of the important attributes of
the ReceiptAdviceParameter node are:
o OrganizationCode / OrganizationId – These are mandatory attributes. The expected

shipment lines are filtered by the provided Organization. You can either provide an
Organization Code or Organization Identifier if you know the internal identifier.
o Purchase Order attributes
 PO Number (attribute name PurchaseOrder), PO Line (attribute name

PurchaseOrderLine) and PO schedule (attribute name
PurchaseOrderSchedule) – Using these attributes you can filter the
expected shipments by PO number, line number, schedule number.
 PurchaseOrderHeaderId, PurchaseOrderLineId and

PurchaseOrderLineLocationId – These are internal identifiers that
correspond to a PO header, PO line or PO schedule.
o In-transit Shipment attributes
 In-transit shipment number (attribute name IntransitShipment), In-transit

shipment line number (attribute name IntransitShipmentLine)
 IntransitShipmentHeaderId and IntransitShipmentLineId – Internal

identifiers that correspond to the in-transit shipment header and line.
o Transfer Order attributes
 Transfer Order Header Number (attribute name TransferOrder), Transfer

Order Line Number (attribute name: TransferOrderLine)
 TransferOrderHeaderId and TransferOrderLineId – Internal identifiers
corresponding to TO header and line number.
o RMA attributes
 RMA Number (attribute name RMA), RMA line number (attribute name
RMALine)
 RMAHeaderId and RMALineId – internal identifiers for RMA number

and line number. These distinguish two different RMAs with same
Number created from two different source systems
o Supplier attributes
 Supplier name (attribute name Supplier), Supplier identifier (attribute

name SupplierId)
 Supplier site code (attribute name SupplierSite), supplier site identifier

(attribute name: SuppliersiteId)
o Customer – Customer name (attribute Customer) and Customer identifier (attribute

name CustomerId)
o Item – Item Number (attribute Item) and Item identifier (attribute name ItemId)
o ReceivingLocation – Location Code (attribute name ReceivingLocation) and

Location identifier (attribute name ReceivingLocationId)
o Carrier – Carrier name (attribute name Carrier), Carrier identifier (attribute name
CarrierId)
o DueDate – Due date of the expected shipment line. The value that you provided to
this parameter corresponds to a lookup code which is defined for the standard
lookup “RCV_DUE_DATE_OPTION”. You can access the lookup codes for this
lookup type by navigating to the Manage Standard lookups UI and searching by
this lookup type. Possible values that you can provide to the attribute DueDate are
ALL_PAST_DUE, TODAY, TOMORROW, TWO_DAYS_AHEAD,
THREE_DAYS_AHEAD, ONE_WEEK_AHEAD, ONE_MONTH_AHEAD,
TWO_DAYS_BACK, THREE_DAYS_BACK, ONE_WEEK_BACK,
ONE_MONTH_BACK.
o Resend – This parameter controls whether you want to re-send an already

transmitted receipt advice. The default behavior of the send receipt advice service
is that once a receipt advice has been transmitted, it will not be transmitted again.
However, if you call the service with Resend = “Y” and provide a single document
(PO number, In-transit Shipment number, RMA number or Transfer Order
Number), you can re-transmit the document again. Note that if Resend attribute is
set as Y, then you must provide one of the following in addition - PO number, In-
transit Shipment number, RMA number or Transfer Order Number. Otherwise, the
service does not return a response.
2.4 Components of Response Payload
 ns0:getReceiptAdviceDetailsResponse – Top level node that encompasses the output

response of the send receipt advice service. The receipt advice header and its lines are
contained within this node
 ns2:ReceiptAdvice – Corresponds to the Receipt Advice summary section. It comprises of
when the receipt advice was generated (ns0:creationDate) and the receiving organization to
which the expected shipment lines belong.
 ns0:ReceiptAdviceLine – Represents the individual receipt advice line and corresponds to

the expected shipment line. This node consists of:
o Action Code – Indicates the message type for this receipt advice line.
 CREATE – If this receipt advice line is transmitted for the first time from
fusion receiving to execution partners
 UPDATE – If this receipt advice line was previously transmitted earlier

and is being sent again either because the document was modified after
the previous transmission or if the resend option was set to Y while
invoking the service
o Document Type – PO (Purchase Order), INVENTORY (In-transit shipment),

TRANSFER ORDER (transfer order inbound shipment) and RMA (Return
Material Authorization)
o Receipt source (VENDOR, CUSTOMER, INVENTORY, TRANSFER ORDER),
o Supplier information – Supplier and Supplier Site
o Customer Name
o From Organization – where the material was shipped from in case of in-transit
shipments and transfer order shipments
o Supplier item reference, customer item reference if any
o Item details – Item Number, Item Description, Item Revision, Item category
o Document quantities in both ordered and secondary UOM
o RMA Line Id – RMA Line identifier.. This attribute is used to identify the exact
RMA line row in Fusion Receiving to transact against.
o Receiving controls – Receipt routing, over receipt tolerance percentage, over

receipt action code, early receipt days tolerance, late receipt days tolerance, receipt
date tolerance exception code, allow substitute item receipts indicator and enforce
ship to location code
o RMA references – Original Sales order references and the references from Oracle
Fusion Distributed Order Orchestration if the RMA was created from there.
o Country Of Origin
o Carrier
o Comments, Notes to receiver
 ns0:ReceiptAdviceLineLotNumber – This node represents the lot numbers shipped as part

of the current receipt advice line/expected shipment line and is applicable for in-transit
shipments and transfer order shipments. The components of this node are
o Lot number
o Lot quantity
o Lot quantity in item’s secondary UOM
 ns0:ReceiptAdviceLineSerialNumber – This node represents the serial numbers shipped as

part of the current receipt advice line/expected shipment line. This is applicable for in-
transit shipments and transfer order shipments and is populated for an item that is serial
controlled and is not lot controlled. This node is populated for each serial number that was
shipped.
o SerialNumber – Individual serial number that is part of the current expected

shipment line
 ns0:ReceiptAdviceLineLotSerialNumber – This node represents the serial numbers that

belong to a given lot shipped as part of the current receipt advice line/expected shipment
line. This is applicable for in-transit shipments and transfer order shipments and is
populated for an item that is both serial controlled and lot controlled. This node is populated
for each serial number that was shipped.
o SerialNumber – Individual serial number that is part of the current lot
2.5 Sample Input Payloads
2.5.1 Search for expected shipments using Purchase Order Header and Line
The sample payload below fetches the receipt advice for PO 1000125 and line 1.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:getReceiptAdviceDetails
xmlns:ns1="http://xmlns.oracle.com/apps/scm/receiving/receiptsInterface/receiptAdvice/re
ceiptAdviceService/types/">
<ns1:ReceiptAdviceParameter
ceiptAdviceService/">
<ns2:OrganizationCode>M1</ns2:OrganizationCode>
<ns2:PurchaseOrder>1000125</ns2:PurchaseOrder>
<ns2:PurchaseOrderLine>1</ns2:PurchaseOrderLine>
</ns1:ReceiptAdviceParameter>
</ns1:getReceiptAdviceDetails>
</soap:Body>
</soap:Envelope>
2.5.2 Search expected shipments due today and next three days for a supplier
The sample payload below fetches the shipment lines for supplier Advanced Network Devices and
supplier site FRESNO. Due date has to be mentioned as mentioned in section 8.3
<soap:Body>
<ns2:Supplier>Advanced Network Devices</ns2:Supplier>
<ns2:SupplierSite>FRESNO</ns2:SupplierSite>
<ns2:DueDate>THREE_DAYS_AHEAD</ns2:DueDate>
</soap:Body>
</soap:Envelope>
2.5.3 Search expected shipments due today for an item and all document types
The sample payload below fetches the shipment lines for item RCV-100 that with due date as today.
This will fetch all open Purchase orders schedules, transfer order shipment lines, in-transit shipment
lines and RMA lines that contain the item RCV-100.
<soap:Body>
<ns2:Item>RCV-100</ns2:Item>
<ns2:DueDate>TODAY</ns2:DueDate>
</soap:Body>
</soap:Envelope>
2.5.4 Search expected shipments due today for all document types
The sample payload below fetches all open Purchase orders schedules, transfer order shipment lines,
in-transit shipment lines and RMA lines with current date as the due date.
<soap:Body>
<ns2:DueDate>TODAY</ns2:DueDate>
</soap:Body>
</soap:Envelope>
2.5.5 Search expected shipments for a Transfer Order number
The sample payload below fetches the shipment lines for transfer order 169001 in the organization
M2.
<soap:Body>
<ns2:TransferOrder>169001</ns2:TransferOrder>
</soap:Body>
</soap:Envelope>
2.5.6 Re-send receipt advice for a Purchase Order
If you have transmitted a Purchase order to an execution partner but there was a problem at the end
of the EP receiving the message, then there may be a need to re-send the receipt advice. In that case,
you need to provide the document number that needs to be transmitted and populate the attribute
Resend as Y
<soap:Body>
<ns2:PurchaseOrder>1003068</ns2:PurchaseOrder>
<ns2:PurchaseOrderLine>1</ns2:PurchaseOrderLine>
<ns2:Resend>Y</ns2:Resend>
</soap:Body>
</soap:Envelope>
2.6 Sample Output Response of Send Receipt Advice
2.6.1 Receipt Advice response with expected shipments for a Purchase Order
This sample payload contains the response when the service is called with PurchaseOrder as 1000125
and line 1.
<ns0:getReceiptAdviceDetailsResponse xmlns=""
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
ceiptAdviceService/types/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
1.0.xsd">
<ns2:ReceiptAdvice
ceiptAdviceService/" xmlns:ns1="http://xmlns.oracle.com/adf/svc/types/"
ceiptAdviceService/types/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns0:ReceiptAdvice">
<ns0:CreationDate>2015-05-25T06:31:43.111-07:00</ns0:CreationDate>
<ns0:ReceiptAdviceLine>
<ns0:ActionCode>CREATE</ns0:ActionCode>
<ns0:ReceiptSourceCode>VENDOR</ns0:ReceiptSourceCode>
<ns0:SourceDocumentType>PO</ns0:SourceDocumentType>
<ns0:SoldtoLeName>Vision Operations</ns0:SoldtoLeName>
<ns0:DocumentNumber>1000125</ns0:DocumentNumber>
<ns0:DocumentRevisionNumber>0</ns0:DocumentRevisionNumber>
<ns0:DocumentRevisionDate xsi:nil="true"/>
<ns0:DocumentCreationDate>2009-08-18T13:51:08.867-
07:00</ns0:DocumentCreationDate>
<ns0:DocumentLastUpdateDate>2014-07-02T16:46:49.89076-
07:00</ns0:DocumentLastUpdateDate>
<ns0:ReceiptAdviceLineStatus>OPEN</ns0:ReceiptAdviceLineStatus>
<ns0:ReceivingLocation>M1- Seattle Mfg</ns0:ReceivingLocation>
<ns0:FromOrganization xsi:nil="true"/>
<ns0:CustomerPartyName xsi:nil="true"/>
<ns0:SupplierName>Advanced Network Devices</ns0:SupplierName>
<ns0:SupplierSiteCode>FRESNO</ns0:SupplierSiteCode>
<ns0:Carrier xsi:nil="true"/>
<ns0:FreightTerms>Due</ns0:FreightTerms>
<ns0:NoteToReceiver xsi:nil="true"/>
<ns0:Comments>VamsiPO1</ns0:Comments>
<ns0:DocumentLineNumber>1</ns0:DocumentLineNumber>
<ns0:DocumentScheduleNumber>1</ns0:DocumentScheduleNumber>
<ns0:SourceHeaderNumber xsi:nil="true"/>
<ns0:SourceLineNumber xsi:nil="true"/>
<ns0:SourceFulfilLineNumber xsi:nil="true"/>
<ns0:OriginalSourceHeaderNumber xsi:nil="true"/>
<ns0:OriginalSourceLineNumber xsi:nil="true"/>
<ns0:OrigSrcFulfilLineNumber xsi:nil="true"/>
<ns0:OriginalSalesOrderNumber xsi:nil="true"/>
<ns0:OrigSalesOrderLineNumber xsi:nil="true"/>
<ns0:DocumentLineCreationDate>2009-08-18T13:54:39.105-
07:00</ns0:DocumentLineCreationDate>
<ns0:DocumentLineLastUpdateDate>2015-05-25T01:22:23.0-
07:00</ns0:DocumentLineLastUpdateDate>
<ns0:ItemNumber>RCV-100</ns0:ItemNumber>
<ns0:ItemDescription>Plain Item</ns0:ItemDescription>
<ns0:ItemRevision xsi:nil="true"/>
<ns0:ItemCategory>Miscellaneous_1</ns0:ItemCategory>
<ns0:SupplierItemNumber xsi:nil="true"/>
<ns0:CustomerItemNumber xsi:nil="true"/>
<ns0:UnitOfMeasure>Each</ns0:UnitOfMeasure>
<ns0:Quantity unitCode="Each"
xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/">2000</ns0:Quantity>
<ns0:ExpectedReceiptDate>2009-08-19T13:53:00.0-07:00</ns0:ExpectedReceiptDate>
<ns0:CountryOfOriginCode xsi:nil="true"/>
<ns0:SecondaryUnitOfMeasure xsi:nil="true"/>
<ns0:SecondaryQuantity
xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/">0</ns0:SecondaryQuantity>
<ns0:DaysEarlyReceiptAllowed>5</ns0:DaysEarlyReceiptAllowed>
<ns0:DaysLateReceiptAllowed>5</ns0:DaysLateReceiptAllowed>
<ns0:ReceiptDaysExceptionCode>WARNING</ns0:ReceiptDaysExceptionCode>
<ns0:AllowSubstituteItemReceipt>Y</ns0:AllowSubstituteItemReceipt>
<ns0:EnforceShipToLocationCode>WARNING</ns0:EnforceShipToLocationCode>
<ns0:OverReceiptTolerance>5</ns0:OverReceiptTolerance>
<ns0:OverReceiptExceptionCode>WARNING</ns0:OverReceiptExceptionCode>
<ns0:ReceivingRouting>Standard receipt</ns0:ReceivingRouting>
<ns0:RMALineId xsi:nil="true"/>
</ns0:ReceiptAdviceLine>
</ns2:ReceiptAdvice>
</ns0:getReceiptAdviceDetailsResponse>
2.6.1 Receipt Advice response for in-transit shipment with lot and serials
This sample payload contains the response when the service is called for in-transit shipments and
contains the lot and serials that have been shipped as part of these lines.
<ns0:getReceiptAdviceDetailsResponse xmlns=""
ceiptAdviceService/types/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
1.0.xsd">
<ns2:ReceiptAdvice
ceiptAdviceService/" xmlns:ns1="http://xmlns.oracle.com/adf/svc/types/"
ceiptAdviceService/types/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns0:ReceiptAdvice">
<ns0:CreationDate>2015-05-26T03:38:31.424-07:00</ns0:CreationDate>
<ns0:ReceiptSourceCode>INVENTORY</ns0:ReceiptSourceCode>
<ns0:SourceDocumentType>INVENTORY</ns0:SourceDocumentType>
<ns0:SoldtoLeName xsi:nil="true"/>
<ns0:DocumentNumber>M1M3SH04</ns0:DocumentNumber>
<ns0:DocumentRevisionNumber xsi:nil="true"/>
<ns0:ReceiptAdviceLineStatus>PARTIALLY RECEIVED</ns0:ReceiptAdviceLineStatus>
<ns0:ReceivingLocation xsi:nil="true"/>
<ns0:FromOrganization>M1</ns0:FromOrganization>
<ns0:SupplierName xsi:nil="true"/>
<ns0:SupplierSiteCode xsi:nil="true"/>
<ns0:FreightTerms xsi:nil="true"/>
<ns0:Comments xsi:nil="true"/>
<ns0:DocumentScheduleNumber xsi:nil="true"/>
<ns0:ItemNumber>VC110</ns0:ItemNumber>
<ns0:ItemDescription>VC-Lot Serial Revision</ns0:ItemDescription>
<ns0:ItemRevision>A</ns0:ItemRevision>
<ns0:SecondaryQuantity xsi:nil="true"/>
<ns0:DaysEarlyReceiptAllowed xsi:nil="true"/>
<ns0:DaysLateReceiptAllowed xsi:nil="true"/>
<ns0:ReceiptDaysExceptionCode xsi:nil="true"/>
<ns0:AllowSubstituteItemReceipt xsi:nil="true"/>
<ns0:EnforceShipToLocationCode xsi:nil="true"/>
<ns0:OverReceiptTolerance xsi:nil="true"/>
<ns0:OverReceiptExceptionCode xsi:nil="true"/>
<ns0:ReceiptAdviceLineLotNumber>
<ns0:LotNumber>INTSL2</ns0:LotNumber>
<ns0:LotQuantity unitCode="Each"
xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/">9</ns0:LotQuantity>
<ns0:SecondaryLotQuantity xsi:nil="true"/>
<ns0:ReceiptAdviceLineLotSerialNumber>
<ns0:SerialNumber>INT2S002</ns0:SerialNumber>
</ns0:ReceiptAdviceLineLotSerialNumber>
<ns0:ReceiptAdviceLineSerialNumber>
</ns0:ReceiptAdviceLineLotNumber>
<ns0:ReceiptSourceCode>INVENTORY</ns0:ReceiptSourceCode>
<ns0:SourceDocumentType>INVENTORY</ns0:SourceDocumentType>
<ns0:SoldtoLeName xsi:nil="true"/>
<ns0:DocumentNumber>M1M3SH02</ns0:DocumentNumber>
<ns0:DocumentRevisionNumber xsi:nil="true"/>
<ns0:ReceiptAdviceLineStatus>PARTIALLY RECEIVED</ns0:ReceiptAdviceLineStatus>
<ns0:ReceivingLocation xsi:nil="true"/>
<ns0:FromOrganization>M1</ns0:FromOrganization>
<ns0:SupplierName xsi:nil="true"/>
<ns0:SupplierSiteCode xsi:nil="true"/>
<ns0:FreightTerms xsi:nil="true"/>
<ns0:Comments xsi:nil="true"/>
<ns0:DocumentScheduleNumber xsi:nil="true"/>
<ns0:ItemDescription>Serial @ Receipt Item</ns0:ItemDescription>
<ns0:ItemRevision xsi:nil="true"/>
<ns0:SecondaryQuantity xsi:nil="true"/>
<ns0:DaysEarlyReceiptAllowed xsi:nil="true"/>
<ns0:DaysLateReceiptAllowed xsi:nil="true"/>
<ns0:ReceiptDaysExceptionCode xsi:nil="true"/>
<ns0:AllowSubstituteItemReceipt xsi:nil="true"/>
<ns0:EnforceShipToLocationCode xsi:nil="true"/>
<ns0:OverReceiptTolerance xsi:nil="true"/>
<ns0:OverReceiptExceptionCode xsi:nil="true"/>
</ns0:ReceiptAdviceLineSerialNumber>
</ns2:ReceiptAdvice>
</ns0:getReceiptAdviceDetailsResponse>
3. Receive Receipt Confirmation
3.1 Overview
The Send Receipt Advice service will transmit the expected shipments for a receiving organization as
receipt advices to an external Execution System. The goods are physically received in the Execution
System. To send the details of the confirmation of the receipts in the external Execution System, it
will invoke the Receive Receipt Confirmation service. This service provides the mechanism for
systems to send the material and receiving details for the expected shipment lines received using
those systems. This service will interpret and transform the message, and create the necessary records
in the receiving open interfaces in Fusion Receiving.
An Execution System would be able to invoke this service directly and the receipt confirmation is
expected in the native SDO format. The service then will interpret and convert the messages
appropriately and create the necessary records in the receiving open interface tables. The receiving
interface records will in turn be processed by the receiving transaction processor to automate receipt,
inspection, deliver, return, and correction transactions as necessary by invoking the Manage
Receiving Transactions ESS job.
The receipt confirmation service will have references to the documents (document number, line and
schedule) that were transmitted by the send receipt advice service. The Execution System will
communicate the quantities that were received, accepted, rejected, delivered, corrected and returned
against each document. When the item is lot and/or serial controlled, the payload should contain the
lot and serial numbers that were delivered and/or returned/corrected.

The URL for Receive Receipt Confirmation service is http://<server-name>:<port-
number>/rcvReceiptConfirmation/ReceiptConfirmationService. This has one operation
processReceiptConfirmations and its asynchronous version processReceiptConfirmationsAsync.
3.2.1 processReceiptConfirmations
The Receive Receipt Confirmation service has one operation processReceiptConfirmations and its
asynchronous equivalent is processReceiptConfirmationsAsync.
 ns1:ReceiptAdviceParameter – This node or object represents the criteria of the expected

shipment lines to be included in the outbound receipt advice. The attributes that you
populated as part of this node will be used to filter the open expected shipments and prepare
the response.
 ns1:ReceiptConfirmation – This node or object represents the header of the receipt

confirmation input response.
o ns2:OrganizationCode – Organization Code that groups all the receipt confirmation

messages. All receipt confirmation messages for a single invocation must be part of
the same receiving organization.
o ns2:ReceiptNumber – receipt number from source system. However, this is not

currently used. Each receipt in fusion receiving is created by generating a new
receipt number.
 ns2:StagedReceiptConfirmationLine – This node represents each receipt confirmation line
that is part of the inbound message. Each receipt confirmation line that you interface to this
service is then transformed to receiving interface tables.
o ns2:ItemNumber – Item Number that is to be received and transacted in Fusion

Receiving
o ns2:ItemDescription – Description of the item/Purchase order line that is being

received in Fusion Receiving
o ns2:ItemRevision – Revision of the item that is being received
o ns2:SourceDocumentCode – Document type for the document being

received/transacted in Fusion Receiving. Possible values – PO, TRANSFER
ORDER, INVENTORY and RMA
o ns2:DocumentNumber – Document number. Holds purchase order number (if

SourceDocumentCode is PO), transfer order shipment number (if
SourceDocumentCode is TRANSFER ORDER), in-transit shipment number (if
SourceDocumentCode is INVENTORY) and RMA number (if
SourceDocumentCode is RMA)
o ns2:DocumentLineNumber – Document line number. Holds purchase order line

number (if SourceDocumentCode is PO), transfer order shipment line number (if
SourceDocumentCode is TRANSFER ORDER), in-transit shipment line number
(if SourceDocumentCode is INVENTORY) and RMA line number (if
SourceDocumentCode is RMA)
o ns2:Document Schedule Number – Document schedule number. Holds purchase

order schedule number (if SourceDocumentCode is PO)
o ns2:SoldToLegalEntity – Sold-to legal entity. Used when there are more than one
purchase orders with same purchase order number
o ns2:FromOrganizationCode – Source organization code where the transfer order

shipment or in-transit shipment was shipped from. This attribute is mandatory
when the SourceDocumentCode for the receipt confirmation line is TRANSFER
ORDER or INVENTORY
o ns2:UnitOfMeasure – UOM in which the source system has transacted in. All the
quantities that are transmitted to the receipt confirmation lines node are transacted
in fusion system in the value specified in this element
o ns2:QuantityReceived – Net Quantity that has been Received in EP system for this
document line/schedule
o ns2:QuantityAccepted – Net Quantity that has been Accepted in EP system for this
o ns2:QuantityRejected – Net Quantity that has been Rejected in EP system for this
o ns2:QuantityDelivered – Net Quantity that has been Delivered to inventory in EP

system for this document line/schedule
o ns2:QuantityCorrected – Net Quantity that has been corrected in EP system for this
o ns2:QuantityReturned – Net Quantity that has been returned (to supplier, customer
or organization based on the document type) for this document line/schedule
o ns2:InspectionQuality – Inspection quality code applicable while accepting or
rejecting material. This should correspond to lookup code for the lookup type
“RCV_QUALITY_CODE”
o ns2:ReasonName – Transaction reason name
o ns2:Subinventory – Subinventory where the material is delivered to
o ns2:Location – Storage Locator where the material is delivered to
o ns2:RMALineId – RMA Line identifier. This is mandatory while transmitting

receipt confirmation messages for a RMA line. This attribute is used to identify the
exact RMA line row in Fusion Receiving to transact against. This attribute is part
of the Send Receipt Advice service as well and the EP can read this attribute from
the send receipt advice service.
o ns2:SubstituteItemNumber – Item number of the substitute item, in case substitute

items are being received
o ns2: StagedReceiptConfirmationLotAndSerial – This node is used to transmit the

lot and/or serial numbers that are to be transacted in fusion receiving as part of the
receipt confirmation line. This node has been designed to flatten the lot and serial
hierarchy to facilitate a simpler communication between EP and fusion receiving.
So, if you are delivering Lot “Lot1” and serials “SN001”, “SN002”, you need to
create two rows for ns2: StagedReceiptConfirmationLotAndSerial node. In the first
row, give “Lot1” and “SN001” and for the second row, give “Lot1” and “SN002”,
essentially repeating the lot number in two rows.
 ns2:LotNumber – Lot number that is being delivered, returned or

corrected
 ns2:LotQuantity – Lot quantity. Should be in the same UOM as that of the

receipt confirmation line
 ns2:LotExpirationDate – Lot expiration date. Applicable for items that

have shelf life code as days
 FmSerialNumber – From serial number of the range of serials being

delivered, corrected or returned
 ToSerialNumber – To serial number of the range of serials being

delivered, corrected or returned
 ns2:Subinventory – Subinventory where the material is delivered to. If

you want lot “A” to be delivered to one subinventory and lot “B” to
delivered to another, you can specify those values in this node rather than
specifying subinventory in the ns2:StagedReceiptConfirmationLine node
 ns2:Location – Storage locator where the material is delivered to. If you

want lot “A” to be delivered to one locators and lot “B” to delivered to
another, you can specify those values in this node rather than specifying
subinventory in the ns2:StagedReceiptConfirmationLine node
 ns1:ReceiptConfirmationResponse – This node or object represents the response object

header.
o ns2:groupId – Internal identifier that is generated by Fusion Receiving in order to
group the receipt confirmation lines that have been transmitted in the current
invocation
o ns2:Status – Return Status to indicate whether the message has been received
successfully or there were errors encountered in interfacing these receipt
confirmation lines to receiving open interface. Possible values – SUCCESS,
ERROR
o ns2:ReceiptConfirmationError – This node displays error details when any of the

receipt confirmation lines are in error. It comprises of the following elements:
 ns2:ErrorMessageName – Error message name
 ns2:ErrorMessage – Error message text
3.6.1 Receipt Confirmations for a Purchase Order
The following sample will create receipt confirmation for a Purchase order schedule and interface
these transactions in receiving. The quantities entered in the payload indicate that 5 Each will be
received, all received quantity is accepted and put away to inventory. Out of the 5 Each put away, 2
will be returned to supplier.
<soap:Body>
<ns1:processReceiptConfirmations
xmlns:ns1="http://xmlns.oracle.com/apps/scm/receiving/receiptsInterface/receiptConfirmat
ion/receiptConfirmationService/types/">
<ns1:ReceiptConfirmation
ion/receiptConfirmationService/">
<ns2:OrganizationCode>RCM1</ns2:OrganizationCode>
<ns2:StagedReceiptConfirmationLine>
<ns2:ItemDescription>Plain Item</ns2:ItemDescription>
<ns2:SourceDocumentCode>PO</ns2:SourceDocumentCode>
<ns2:SoldtoLegalEntity>Vision Operations</ns2:SoldtoLegalEntity>
<ns2:QuantityReceived>5</ns2:QuantityReceived>
<ns2:QuantityAccepted>5</ns2:QuantityAccepted>
<ns2:QuantityDelivered>5</ns2:QuantityDelivered>
<ns2:QuantityReturned>2</ns2:QuantityReturned>
<ns2:Subinventory>Stores</ns2:Subinventory>
</ns2:StagedReceiptConfirmationLine>
</ns1:ReceiptConfirmation>
</ns1:processReceiptConfirmations>
</soap:Body>
</soap:Envelope>
3.6.2 Receipt Confirmation for In-transit Shipment
The following sample will create receipt confirmation for an in-transit shipment line and interface
received, all received quantity is put away to inventory. The item is revision controlled, so the
revision being received has to be specified in receipt confirmation line. The lot and serial information
specified as a child of the receipt confirmation line and will be used in creating the DELIVER
transaction for this shipment line.
<soap:Body>
<ns2:ItemRevision>A</ns2:ItemRevision>
<ns2:SourceDocumentCode>INVENTORY</ns2:SourceDocumentCode>
<ns2:Subinventory>ABCSUB01</ns2:Subinventory>
<ns2:Location>ABC1.1.1</ns2:Location>
<ns2:StagedReceiptConfirmationLotAndSerial>
<ns2:LotNumber>INTSL-001</ns2:LotNumber>
<ns2:LotQuantity>5</ns2:LotQuantity>
<ns2:FmSerialNumber>INTSS-001</ns2:FmSerialNumber>
<ns2:ToSerialNumber>INTSS-005</ns2:ToSerialNumber>
<ns2:Subinventory></ns2:Subinventory>
<ns2:Location></ns2:Location>
</ns2:StagedReceiptConfirmationLotAndSerial>
</soap:Body>
</soap:Envelope>
3.6.3 Receipt Confirmation for a Transfer Order Shipment
The following sample will create receipt confirmation for a transfer order shipment and interface
these transactions in receiving. Document Number will correspond to the Transfer order shipment
that was interfaced to EP and not the transfer order. The quantities entered in the payload indicate
that 5 Each will be received, all received quantity is put away to inventory. The item is serial
controlled, and hence, serial information specified as a child of the receipt confirmation line and will
be used in creating the DELIVER transaction for this shipment line.
<soap:Body>
<ns2:FromOrganizationCode>M1</ns2:FromOrganizationCode>
<ns2:SourceDocumentCode>TRANSFER ORDER</ns2:SourceDocumentCode>
<ns2:FmSerialNumber>INTSS-101</ns2:FmSerialNumber>
<ns2:ToSerialNumber>INTSS-105</ns2:ToSerialNumber>
</soap:Body>
</soap:Envelope>
3.6.4 Receipt confirmation for RMA
The following sample will create receipt confirmation for a Purchase order schedule and interface
received, 2 of which are returned to customer and the remaining 3 are delivered to inventory. Since
the same RMA number can be created in fusion receiving from multiple source systems, you need to
specify RMALineId in the service payload to uniquely identify the particular RMA line that needs to
be used to create receiving transactions for.
<soap:Body>
<ns2:SourceDocumentCode>RMA</ns2:SourceDocumentCode>
<ns2:DocumentNumber>SRCSYS1_RMA_001</ns2:DocumentNumber>
<ns2:RMALineId>25909972</ns2:RMALineId>
<ns2:LotNumber>RCONFL-151</ns2:LotNumber>
<ns2:LotQuantity>5</ns2:LotQuantity>
</soap:Body>
</soap:Envelope>
3.6.5 Receipt Confirmation with all transactions interfaced from Execution
System
This sample payload illustrates the use case where the Execution System communicates all the
transactions performed in a single invocation of the receive receipt confirmation service. Single
invocation is efficient compared to invoking the service multiple times for interfacing each
individual transaction. This payload comprises all item flavors supported (no inventory controls, lot
controlled, serial controlled, revision lot and serial controlled). Notice that lot and serials are being
delivered to inventory as well as returned from supplier. For such cases, there should be two separate
receipt confirmation lines for the DELIVER and return transactions, so that fusion receiving
understands what lot/serials have to be delivered and what lot/serials are to be returned. This payload
also covers the case where material is delivered to inventory and subsequently corrected by
specifying which lot/serials are to be recorded for corrections
<soap:Body>
<ns2:ItemRevision></ns2:ItemRevision>
<ns2:LotNumber>RCONF-L5</ns2:LotNumber>
<ns2:LotQuantity unitCode="Ea">3</ns2:LotQuantity>
<ns2:FmSerialNumber></ns2:FmSerialNumber>
<ns2:ToSerialNumber></ns2:ToSerialNumber>
<ns2:LotNumber>RCONF-L5</ns2:LotNumber>
<ns2:FmSerialNumber></ns2:FmSerialNumber>
<ns2:ToSerialNumber></ns2:ToSerialNumber>
<ns2:LotNumber></ns2:LotNumber>
<ns2:LotQuantity unitCode=""></ns2:LotQuantity>
<ns2:FmSerialNumber>RCONF-S013</ns2:FmSerialNumber>
<ns2:ToSerialNumber>RCONF-S015</ns2:ToSerialNumber>
<ns2:QuantityCorrected>-3</ns2:QuantityCorrected>
<ns2:LotNumber></ns2:LotNumber>
<ns2:LotQuantity unitCode=""></ns2:LotQuantity>
<ns2:FmSerialNumber>RCONF-S013</ns2:FmSerialNumber>
<ns2:ToSerialNumber>RCONF-S015</ns2:ToSerialNumber>
<ns2:ItemRevision>0</ns2:ItemRevision>
<ns2:LotNumber>RCONF-LS3</ns2:LotNumber>
<ns2:FmSerialNumber>RCONFLS-013</ns2:FmSerialNumber>
<ns2:ToSerialNumber>RCONFLS-015</ns2:ToSerialNumber>
<ns2:ItemRevision>0</ns2:ItemRevision>
<ns2:LotNumber>RCONF-LS3</ns2:LotNumber>
<ns2:FmSerialNumber>RCONFLS-013</ns2:FmSerialNumber>
<ns2:ToSerialNumber>RCONFLS-015</ns2:ToSerialNumber>
</soap:Body>
</soap:Envelope>
3.7 Sample Output Response of Receive Receipt Confirmation Service
3.7.1 Sample response when receipt confirmation is interfaced successfully
This sample payload comprises the situation where the receipt confirmation lines that were
transmitted through this service are successfully interfaced to fusion receiving open interface schema.
<ns0:processReceiptConfirmationsResponse xmlns=""
ion/receiptConfirmationService/types/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
1.0.xsd">
<ns0:result
ion/receiptConfirmationService/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:ReceiptConfirmationResponse">
<ns1:GroupId>47119</ns1:GroupId>
<ns1:Status>SUCCESS</ns1:Status>
</ns0:result>
</ns0:processReceiptConfirmationsResponse>
4. Transaction Manager Service
4.1 Overview
Transaction Manager Service processes material transactions to maintain onhand balances in Fusion
Inventory. It inserts data in transaction interface table and invokes the manager to process the rows
that are ready for processing.
After the manager completes its processing a result is returned to notify the calling application if the
manager completed successfully or failed. If the manager completes successfully the completed
transaction can be viewed on the Review Completed Transactions UI. However if the transaction
processing fails the error details as well as transaction data can be viewed on the Manage Pending
Transaction UI where the data can be corrected and resubmitted to the manager for reprocessing.

The URL for the Transaction Manager Service is http://<server-name>:<port-
number>/invPendingTransactions/TransactionManagerServiceV2.
This has two operations along with their asynchronous versions:
insertAndProcessInterfaceRows
insertAndProcessInterfaceRowsAsync
processInventoryTransaction
processInventoryTransactionAsync
4.2.1 insertAndProcessInterfaceRows
This operation will insert data into the transaction interface table then call the transaction manager to
process the interface rows.
Payload examples for the following transactions

o Miscellaneous Receipt
o Miscellaneous Issue
4.2.1.1 Components of Input Payload
 ns1: interfaceRows – This node or object represents transaction interface data.
 ns1:headerId – Transaction interface group identifier that is passed to the transaction

manager service to process. This value will be the same as ns2: TransactionHeaderId if
you want to process the transaction rows immediately by invoking the manager.
 ns1:validationLevel – Validation level of the transaction interface data. You should

always pass a value of “1” for this attribute in the payload.
 ns1: tableType – Placeholder for possible future use. You should always pass a value
of “1” for this attribute in the payload.
o ns2: TransactionHeaderId – Transaction interface group identifier.

o ns2: TransactionInterfaceId – Transaction interface line identifier.
o ns2: SourceCode – Transaction interface source identifier. Any code that would
identify the source system.
o ns2: SourceLineId – Transaction source line identifier. Any value that would
identify the line from the source system.
o ns2: SourceHeaderId – Transaction source group identifier. Any value that would
identify the group from the source system.
o ns2: ProcessCode – Indicates the transaction processing status. This value should
always be passed as “1” which indicates that the row is ready for processing.
o ns2:TransactionMode – The mode associated with the transaction. This value

should always be passed in as “3” which indicates that this row is ready to be
processed by the Transaction Manager ESS process.
o ns2: InventoryItemId – Any active inventory item that is defined in Product

Management.
o ns2:OrganizationId – Any valid inventory organization.
o ns2: TransactionQuantity - Quantity of an item transacted in the transaction UOM

with the associated UOM for the Unit Code. The Unit Code can be left NULL as
long as you put a valid value in the TransactionUnitOfMeasure.
o ns2:TransactionUnitOfMeasure – UOM associated with the transactions. Any

valid unit of measure that has been setup using the Manage Units of Measure UI.
(Example: Each)
o ns2:TransactionDate – Date the transaction occurred. The date must be in the

following format: 2015-10-29T00:00:00.000-08:00
o ns2: SubinventoryCode – Defines a physical or logical separation of material

within an organization. Any valid subinventory that has been setup using the
Manage Subinventories and Locators UI.
o ns2: TransactionTypeId – Transaction type identifier. (Example for Miscellaneous

Receipt – 42 and Miscellaneous Issue – 32)
4.2.1.2 Example of Response Payload
The Payload response example below will be the same for all transactions. The result will indicate if
the transaction completed successfully or failed. (Success 0, Failure -1). If the result is -1 to indicate
the transaction manager failed you can view the failed transaction on the Manage Pending
Transaction UI and take the appropriate action to correct and resubmit the transaction for processing.
<ns0:insertAndProcessInterfaceRowsResponse
xmlns:ns0="http://xmlns.oracle.com/apps/scm/inventory/materialTransactions/pendingTransactions/t
ransactionManagerServiceV2/types/">
<result
xmlns="http://xmlns.oracle.com/apps/scm/inventory/materialTransactions/pendingTransactio
ns/transactionManagerServiceV2/types/">0</result>
</ns0:insertAndProcessInterfaceRowsResponse>
4.2.1.3 Sample Input Payloads
Miscellaneous Receipt
The payload below is for a Miscellaneous Receipt Transaction that is a plain item with no additional
inventory controls such as Lot, Serial, Locator or Revision. The values given are just examples and
should be updated based on your inventory setup. The following sample will process a miscellaneous
receipt transaction for item 149 (AS54888), with a quantity of 100 in Organization 207 (Seattle
Manufacturing) and in the FGI Subinventory. After you have invoked the service and the transaction
has been processed successfully you should see an increase in your available on-hand balance for this
item by the quantity passed.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body>
<ns1:insertAndProcessInterfaceRows
<ns1:interfaceRows
xmlns:ns2="http://xmlns.oracle.com/apps/scm/inventory/materialTransactions/pendingTransactions/s
tagedInventoryTransactionServiceV2/">
<ns2:TransactionHeaderId>10000</ns2:TransactionHeaderId>
<ns2:TransactionInterfaceId>10000</ns2:TransactionInterfaceId>
<ns2:SourceCode>S100</ns2:SourceCode>
<ns2:SourceLineId>2000</ns2:SourceLineId>
<ns2:SourceHeaderId>1000</ns2:SourceHeaderId>
<ns2:ProcessCode>1</ns2:ProcessCode>
<ns2:TransactionMode>3</ns2:TransactionMode>
<ns2:InventoryItemId>149</ns2:InventoryItemId>
<ns2:OrganizationId>207</ns2:OrganizationId>
<ns2:TransactionQuantity unitCode="">100</ns2:TransactionQuantity>
<ns2:TransactionUnitOfMeasure>Each</ns2:TransactionUnitOfMeasure>
<ns2:TransactionDate>2015-10-29T00:00:00.000-08:00</ns2:TransactionDate>
<ns2:SubinventoryCode>FGI</ns2:SubinventoryCode>
<ns2:TransactionTypeId>42</ns2:TransactionTypeId>
</ns1:interfaceRows>
<ns1:headerId>10000</ns1:headerId>
<ns1:validationLevel>1</ns1:validationLevel>
<ns1:tableType>1</ns1:tableType>
</ns1:insertAndProcessInterfaceRows>
</soap:Body>
</soap:Envelope>
Miscellaneous Issue
The payload below is for a Miscellaneous Issue Transaction that is a plain item with no additional
inventory controls such as Lot, Serial, Locator or Revision. The values given are just examples and
should be updated based on your inventory setup. The following sample will process a miscellaneous
issue transaction for item 149 (AS54888), with a quantity of -1 in Organization 207 (Seattle
Manufacturing) and in the FGI Subinventory. After you have invoked the service and the transaction
has been processed successfully you should see a decrease in your available on-hand balance for this
item by the quantity passed.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body>

<ns1:insertAndProcessInterfaceRows
<ns1:interfaceRows
xmlns:ns2="http://xmlns.oracle.com/apps/scm/inventory/materialTransactions/pendingTransactions/s
tagedInventoryTransactionServiceV2/">
<ns2:TransactionHeaderId>10000</ns2:TransactionHeaderId>
<ns2:TransactionInterfaceId>10000</ns2:TransactionInterfaceId>
<ns2:SourceCode>S100</ns2:SourceCode>
<ns2:SourceLineId>2000</ns2:SourceLineId>
<ns2:SourceHeaderId>1000</ns2:SourceHeaderId>
<ns2:ProcessCode>1</ns2:ProcessCode>
<ns2:TransactionMode>3</ns2:TransactionMode>
<ns2:InventoryItemId>149</ns2:InventoryItemId>
<ns2:OrganizationId>207</ns2:OrganizationId>
<ns2:TransactionQuantity unitCode="">-1</ns2:TransactionQuantity>
<ns2:TransactionUnitOfMeasure>Each</ns2:TransactionUnitOfMeasure>
<ns2:TransactionDate>2015-10-29T00:00:00.000-08:00</ns2:TransactionDate>
<ns2:SubinventoryCode>FGI</ns2:SubinventoryCode>
<ns2:TransactionTypeId>32</ns2:TransactionTypeId>
</ns1:interfaceRows>
</ns1:insertAndProcessInterfaceRows>
</soap:Body>
</soap:Envelope>
4.2.2 processInventoryTransaction
This operation is used to call the transaction manager for a specific transaction interface header. This
operation would be used to reprocess failed rows once the interface data has been corrected or
unprocessed rows.
4.2.2.1 Components of Input Payload
 ns1:headerId – Transaction interface group identifier that is passed to the transaction

manager service to process.
 ns1:validationLevel – Validation level of the transaction interface data. You should

always pass a value of “1” for this attribute in the payload.
 ns1: tableType – Placeholder for possible future use. You should always pass a value
of “1” for this attribute in the payload.
4.2.2.2 Example of Response Payload
The result will indicate if the transaction completed successfully or failed. (Success 0, Failure -1). If
the result is -1 to indicate the transaction manager failed you can view the failed transaction on the
Manage Pending Transaction UI and take the appropriate action to correct and resubmit the
transaction for processing.
<ns0:processInventoryTransactionResponse
<result
xmlns="http://xmlns.oracle.com/apps/scm/inventory/materialTransactions/pendingTransactio
ns/transactionManagerServiceV2/types/">0</result>
</ns0: processInventoryTransactionResponse >
4.2.2.3 Sample Input Payload
The payload below is to process a specific transaction header that has already been inserted into the
inventory transaction interface table and is ready for processing.
<soap:Body>
<ns1:processInventoryTransaction
</ns1:processInventoryTransaction>
</soap:Body>
</soap:Envelope>
5. Shipment Line Service
5.1 Overview
Shipment Line Service’s operation, generateShipmentRequest, when invoked with the required input
will search and select the shipment lines, build the shipment requests payload, and send the same to
the invoking external Execution System. This provides the get mechanism for systems that subscribe
to the publish shipment request event to acquire the actual shipment requests. For integration
purposes, external Execution Systems will invoke this service when needed.
It also allows external Execution Systems to invoke this service voluntarily at frequent intervals to
fetch the shipment requests without subscribing to any events. In such blind invocation scenario, the
service expects the minimum criteria – organization, release rule, or shipment request batch number.
This service will consider the following rules when the shipment lines are interfaced to an external
system.
 Only ready to release and backordered shipment lines are eligible for this processing.
 Shipment lines are not assigned to any shipment.
 Shipment lines are not packed into any container.
 Log exceptions for the lines that were selected but not interfaced because they were
assigned to a shipment or packed into a container.

The URL for the Shipment Line Service is http://<server-name>:<port-
number>/wshDeliveriesLinesService/ShipmentLineService. This has an operation
generateShipmentRequest and its asynchronous version generateShipmentRequestAsync.
5.2.1 generateShipmentRequest
The Shipment Line Service has an operation generateShipmentRequest and its asynchronous
equivalent is generateShipmentRequestAsync.
 ns1:inputParams – This node represents the criteria used to select Shipment lines to be sent
to External Partner. This node is comprised of the following 3 parameters(one of these has
to be specified) :
o PickBatchName - This is the name of the pick batch that holds the filter criteria
that the service uses to select the appropriate shipment lines.
o OrganizationCode - This is the Organization Code. You will use this parameter if
you want to select all shipment lines that are ready to interface for an organization.
o ReleaseRuleName - This is a Pick Wave Release Rule Name. You will use this
parameter if you wish to filter the shipment lines by a previously defined Release
Rule.
.
 ns0: GenerateShipmentRequestResponse – Top level node that encompasses the output

response of the generateShipmentRequest operation of Shipment Line service.
o ns2:result encapsulates the Value
 ns1:Value
 ns1:ShipmentRequest - Unique identifier for the shipment

request
 ns1:SourceSystemName - Identifier for the source system
 ns1:ShipFromOrganizationCode - Identifier for ship from

organization
 ns1:ShipFromOrganizationName - Name for inventory

organization
 ns1:ReturnStatus - Status of the request
 ns1:Message - An object to store message details from the

actions taken on a shipment line
 ns1:OutboundShipmentOrder - Identifier for an order
o ns1:SalesOrder - Identifier for sales order from order

capture system
o ns1:ShipToName - Name of the party to whom the sales

order line to be shipped
o ns1:ShipToContactName - Person to be contacted at

ship-to customer
o ns1:ShipToPhone - Telephone number for the person to

be contacted at ship-to customer
o ns1:ShipToURL - URL for ship-to customer
o ns1:ShipToFaxNumber - Fax number for the ship-to

customer
o ns1:SoldToPartyName - Name of the party to whom the

sales order line to be sold
o ns1:SoldToContactName - Person to be contacted at

sold-to customer
o ns1:SoldToPhoneNumber - Telephone number for the

person to be contacted at sold-to customer
o ns1:SoldToURL - URL for sold-to customer
o ns1:SoldToFaxNumber - Fax number for the sold-to

customer
o ns1:BillToPartyName - Name of the party to whom the
sales order line to be billed
o ns1:BillToContactName - Person to be contacted at bill-

to customer
o ns1:BillToPhoneNumber - Telephone number for the

person to be contacted at bill-to customer
o ns1:BillToURL - URL for bill-to customer
o ns1:BillToFaxNumber - Fax number for the bill-to

customer
o ns1:CarrierName - A company that transports goods

from one point to another by land, sea, or air
o ns1:ServiceLevel - Priority of transportation that affects

how quickly goods are transported.
o ns1:ModeOfTransport - Various modes of

transportation used for the movement of goods.
o ns1:FOBCode - Freight on board code
o ns1:FreightTermsCode - An agreement indicating who

(the buyer or the seller) pays the shipping costs of an
order and when payment is due
o ns1:CurrencyCode - Currency code
o ns1:ConversionType - Currency conversion type to be

used in case the shipping cost is in a different currency
from the order currency
o ns1:ConversionDate - Conversion date to be used for

the currency conversion
o ns1:ConversionRate - Conversion rate to be used for the

currency conversion
o ns1:ShipToAddressFirstLine - First line of ship-to

customer address
o ns1:ShipToAddressSecondLine - Second line of ship-to

customer address
o ns1:ShipToAddressThirdLine - Third line of ship-to

customer address
o ns1:ShipToAddressFourthLine - Fourth line of ship-to

customer address
o ns1:ShipToCity - City of ship-to customer address
o ns1:ShipToCounty - County of ship-to customer address
o ns1:ShipToPostalCode - Postal code of ship-to customer

address
o ns1:ShipToRegion - Region of ship-to customer address
o ns1:ShipToState - State of ship-to customer address
o ns1:ShipToCountry - Country of ship-to customer

address
o ns1:BillToAddressFirstLine - First line of bill-to

customer address
o ns1:BillToAddressSecondLine - Second line of bill-to

customer address
o ns1:BillToAddressThirdLine - Third line of bill-to

customer address
o ns1:BillToAddressFourthLine - Fourth line of bill-to

customer address
o ns1:BillToCity - City of bill-to customer address
o ns1:BillToCounty - County of bill-to customer address
o ns1:BillToPostalCode - Postal code of bill-to customer

address
o ns1:BillToRegion - Region of bill-to customer address
o ns1:BillToState - State of bill-to customer address
o ns1:BillToCountry - Country of bill-to customer address
o ns1:ActionType - Indicates the action to be performed.

Valid values is CREATE.
o ns1:OutboundShipmentLine
 ns1:ShipmentLine- Identifier for a shipment

line
 ns1:SalesOrderLine - Identifier for sales order

line from order capture system
 ns1:SalesOrderSchedule - Identifier for sales

order schedule from order capture system
 ns1:ItemNumber - Identifier for an item
 ns1:ItemDescription – Inventory Item

description
 ns1:UnitPrice - Price of item per unit
 ns1:SellingPrice - Actual selling price of the

item
 ns1:OrderedQuantity - Quantity of the item

requested on a sales order line in primary
UOM
 ns1:OrderedQuantityUOMName - Primary
UOM for ordered quantity
 ns1:SecondaryOrderedQuantity - Quantity of
the item requested on a sales order line in
secondary UOM
 ns1:SecondaryOrderedQuantityUOM -
Secondary UOM unit of measure for ordered
quantity
 ns1:CarrierName - A company that transports

goods from one point to another by land, sea,
or air
 ns1:ServiceLevel - Priority of transportation

that affects how quickly goods are transported
 ns1:ModeOfTransport - Various modes of

transportation used for the movement of goods
 ns1:FOBCode - Freight on board code
 ns1:FreightTermsCode - An agreement
indicating who (the buyer or the seller) pays
the shipping costs of an order and when
payment is due
 ns1:ShipmentPriorityCode - Indicates the

priority of the demand lines to be shipped
 ns1:PreferredGrade - Preferred grade of the

item
 ns1:CurrencyCode - Currency code
 ns1:ShipSetName - Ship set identifier to which

the order line belongs
 ns1:ArrivalSetName - Arrival set identifier to

which the order line belongs
 ns1:CustomerPONumber - Customer purchase

order identifier
 ns1:CustomerItemNumber - Customer item

number
 ns1:PackingInstructions - A document or text

that contains information concerning the
packing of an item
 ns1:ShippingInstructions - A document or text

that contains information concerning the
shipping of an item
 ns1:DateRequested - Date on which the sales

order line is either shipped or arrived
 ns1:DateScheduled - Date on which the sales
order line is scheduled to be shipped
 ns1:RequestDateTypeCode - Indicates whether

the requested date is when the material to be
shipped or to arrive
 ns1:ShipToParty - Name of the party to whom

the sales order line to be shipped
 ns1:ShipToContactName - Person to be
contacted at ship-to customer
 ns1:ShipToPhone - Telephone number for the

person to be contacted at ship-to customer
 ns1:ShipToURL - URL for ship-to customer
 ns1:ShipToFaxNumber - Fax number for the

ship-to customer
 ns1:ShipToAddressFirstLine - First line of

ship-to customer address
 ns1:ShipToAddressSecondLine - Second line

of ship-to customer address
 ns1:ShipToAddressThirdLine - Third line of

 ns1:ShipToAddressFourthLine - Fourth line of

 ns1:ShipToCity - City of ship-to customer

address
 ns1:ShipToCounty - County of ship-to

customer address
 ns1:ShipToPostalCode - Postal code of ship-to

customer address
 ns1:ShipToRegion - Region of ship-to

customer address
 ns1:ShipToState - State of ship-to customer

address
 ns1:ShipToCountry - County of ship-to

customer address
 ns1:SoldToParty - Name of the party to whom

the sales order line to be sold
 ns1:SoldToContactName - Person to be
contacted at sold-to customer
 ns1:SoldToPhone - Telephone number for the

person to be contacted at sold-to customer
 ns1:SoldToURL - URL for sold-to customer
 ns1:SoldToFaxNumber - Fax number for the

sold-to customer
 ns1:BillToParty - Name of the party to whom

the sales order line to be billed
 ns1:BillToContactName - Person to be
contacted at bill-to customer
 ns1:BillToPhoneNumber - Telephone number

for the person to be contacted at bill-to
customer
 ns1:BillToURL - URL for bill-to customer
 ns1:BillToFaxNumber - Fax number for the

bill-to customer
 ns1:BillToAddressFirstLine - First line of bill-

to customer address
 ns1:BillToAddressSecondLine - Second line of

bill-to customer address
 ns1:BillToAddressThirdLine - Third line of

 ns1:BillToAddressFourthLine - Fourth line of

 ns1:BillToCity - City of bill-to customer

address
 ns1:BillToCounty - County of bill-to customer

address
 ns1:BillToPostalCode - Postal code of bill-to

customer address
 ns1:BillToRegion - Region of bill-to customer

address
 ns1:BillToState - State of bill-to customer

address
 ns1:BillToCountry - Country of bill-to

customer address
 ns1:Subinventory - Subinventory from which

the item to be shipped
 ns1:DoNotShipBeforeDate - Date before which

the item should not be shipped
 ns1:DoNotShipAfterDate - Date after which

the item should not be shipped
 ns1:ShipToleranceAbove - Percentage
tolerance allowed to ship over the requested
quantity
 ns1:ShipToleranceBelow - Percentage
tolerance allowed to ship below the requested
quantity
 ns1:ActionType - Indicates the action to be

performed. Valid values is CREATE
5.5.1 Select shipment lines using Pick Batch
The sample payload below fetches the eligible Shipment Lines based on the filter criteria specified
using Picking Batch “5390900”.
<soap:Body>
<ns1:GenerateShipmentRequest
xmlns:ns1="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentLineService/types/">
<ns1:inputParams xmlns:ns2="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentLineService/">
<ns2:PickBatchName>5390900</ns2:PickBatchName>
<ns2:OrganizationCode></ns2:OrganizationCode>
<ns2:ReleaseRuleName></ns2:ReleaseRuleName>
</ns1:inputParams>
</ns1:GenerateShipmentRequest>
</soap:Body>
</soap:Envelope>
5.5.2 Select shipment lines using Organization
The sample payload below fetches the eligible Shipment Lines for the Organization criteria specified
using Organization Code “M1”.
<soap:Body>
<ns2:PickBatchName></ns2:PickBatchName>
<ns2:ReleaseRuleName></ns2:ReleaseRuleName>
</ns1:inputParams>
</soap:Body>
</soap:Envelope>
5.5.3 Select shipment lines using Release Rule
The sample payload below fetches the eligible Shipment Lines based on the selection criteria
specified using Release Rule “RR1”.
<soap:Body>
<ns2:PickBatchName></ns2:PickBatchName>
<ns2:OrganizationCode></ns2:OrganizationCode>
<ns2:ReleaseRuleName>RR1</ns2:ReleaseRuleName>
</ns1:inputParams>
</soap:Body>
</soap:Envelope>
5.6 Sample Output Response of Generate Shipment Request
5.6.1 Generate Shipment Request response with selected Shipment Lines for a
Pick Batch
This sample payload contains the response when the service is called with Pick Batch “5390900”.
<ns0:GenerateShipmentRequestResponse
<ns2:result xmlns:ns0="http://xmlns.oracle.com/adf/svc/types/"
xmlns:ns1="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentLineService/"
xmlns:ns2="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentLineService/types/"
xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:OutboundShipmentHeaderResult">
<ns1:Value>
<ns1:ShipmentRequest>5390900</ns1:ShipmentRequest>
<ns1:SourceSystemName>Product Information Management Data Hub</ns1:SourceSystemName>
<ns1:ShipFromOrganizationCode>M1</ns1:ShipFromOrganizationCode>
<ns1:ShipFromOrganizationName>Seattle Manufacturing</ns1:ShipFromOrganizationName>
<ns1:ReturnStatus>SUCCESS</ns1:ReturnStatus>
<ns1:Message xsi:nil="true"/>
<ns1:OutboundShipmentOrder>
<ns1:SalesOrder>HLG-OCT22-M1-001</ns1:SalesOrder>
<ns1:ShipToName>World of Business</ns1:ShipToName>
<ns1:ShipToContactName>World of Business</ns1:ShipToContactName>
<ns1:ShipToPhone>5558355</ns1:ShipToPhone>
<ns1:ShipToURL xsi:nil="true"/>
<ns1:ShipToFaxNumber xsi:nil="true"/>
<ns1:SoldToPartyName>World of Business</ns1:SoldToPartyName>
<ns1:SoldToContactName>World of Business</ns1:SoldToContactName>
<ns1:SoldToPhoneNumber>5558355</ns1:SoldToPhoneNumber>
<ns1:SoldToURL xsi:nil="true"/>
<ns1:SoldToFaxNumber xsi:nil="true"/>
<ns1:BillToPartyName>World of Business</ns1:BillToPartyName>
<ns1:BillToContactName>World of Business</ns1:BillToContactName>
<ns1:BillToPhoneNumber>5558355</ns1:BillToPhoneNumber>
<ns1:BillToURL xsi:nil="true"/>
<ns1:BillToFaxNumber xsi:nil="true"/>
<ns1:CarrierName xsi:nil="true"/>
<ns1:ServiceLevel xsi:nil="true"/>
<ns1:ModeOfTransport xsi:nil="true"/>
<ns1:FOBCode xsi:nil="true"/>
<ns1:FreightTermsCode xsi:nil="true"/>
<ns1:CurrencyCode>USD</ns1:CurrencyCode>
<ns1:ConversionType xsi:nil="true"/>
<ns1:ConversionDate xsi:nil="true"/>
<ns1:ConversionRate xsi:nil="true"/>
<ns1:ShipToAddressFirstLine>2391 L Street</ns1:ShipToAddressFirstLine>
<ns1:ShipToAddressSecondLine xsi:nil="true"/>
<ns1:ShipToAddressThirdLine xsi:nil="true"/>
<ns1:ShipToAddressFourthLine xsi:nil="true"/>
<ns1:ShipToCity>San Jose</ns1:ShipToCity>
<ns1:ShipToCounty>Santa Clara</ns1:ShipToCounty>
<ns1:ShipToPostalCode>95106</ns1:ShipToPostalCode>
<ns1:ShipToRegion xsi:nil="true"/>
<ns1:ShipToState>CA</ns1:ShipToState>
<ns1:ShipToCountry>United States</ns1:ShipToCountry>
<ns1:BillToAddressFirstLine>2391 L Street</ns1:BillToAddressFirstLine>
<ns1:BillToAddressSecondLine xsi:nil="true"/>
<ns1:BillToAddressThirdLine xsi:nil="true"/>
<ns1:BillToAddressFourthLine xsi:nil="true"/>
<ns1:BillToCity>San Jose</ns1:BillToCity>
<ns1:BillToCounty>Santa Clara</ns1:BillToCounty>
<ns1:BillToPostalCode>95106</ns1:BillToPostalCode>
<ns1:BillToRegion xsi:nil="true"/>
<ns1:BillToState>CA</ns1:BillToState>
<ns1:BillToCountry>United States</ns1:BillToCountry>
<ns1:ActionType>CREATE</ns1:ActionType>
<ns1:OutboundShipmentLine>
<ns1:ShipmentLine>3518004</ns1:ShipmentLine>
<ns1:SalesOrderLine>3</ns1:SalesOrderLine>
<ns1:SalesOrderSchedule xsi:nil="true"/>
<ns1:ItemNumber>INV-102</ns1:ItemNumber>
<ns1:ItemDescription>Serial @ Receipt Item</ns1:ItemDescription>
<ns1:UnitPrice currencyCode="USD">100</ns1:UnitPrice>
<ns1:SellingPrice xsi:nil="true"/>
<ns1:OrderedQuantity unitCode="Each">3</ns1:OrderedQuantity>
<ns1:OrderedQuantityUOMName>Each</ns1:OrderedQuantityUOMName>
<ns1:SecondaryOrderedQuantity xsi:nil="true"/>
<ns1:SecondaryOrderedQuantityUOM xsi:nil="true"/>
<ns1:ShipmentPriorityCode xsi:nil="true"/>
<ns1:PreferredGrade xsi:nil="true"/>
<ns1:ShipSetName xsi:nil="true"/>
<ns1:ArrivalSetName xsi:nil="true"/>
<ns1:CustomerPONumber xsi:nil="true"/>
<ns1:PackingInstructions xsi:nil="true"/>
<ns1:ShippingInstructions xsi:nil="true"/>
<ns1:DateRequested>2014-04-11</ns1:DateRequested>
<ns1:DateScheduled>2014-04-11</ns1:DateScheduled>
<ns1:RequestDateTypeCode xsi:nil="true"/>
<ns1:ShipToParty>World of Business</ns1:ShipToParty>
<ns1:SoldToParty>World of Business</ns1:SoldToParty>
<ns1:SoldToPhone>5558355</ns1:SoldToPhone>
<ns1:BillToParty>World of Business</ns1:BillToParty>
<ns1:Subinventory xsi:nil="true"/>
<ns1:DoNotShipBeforeDate xsi:nil="true"/>
<ns1:DoNotShipAfterDate xsi:nil="true"/>
<ns1:ShipToleranceAbove xsi:nil="true"/>
<ns1:ShipToleranceBelow xsi:nil="true"/>
</ns1:OutboundShipmentLine>
<ns1:ItemNumber>AS54888</ns1:ItemNumber>
<ns1:ItemDescription> Sentinel Standard Desktop TPDS </ns1:ItemDescription>
<ns1:ItemNumber> INV-101</ns1:ItemNumber>
<ns1:ItemDescription> Lot Item </ns1:ItemDescription>
</ns1:OutboundShipmentOrder>
</ns1:Value>
</ns2:result>
</ns0:GenerateShipmentRequestResponse>
6. Shipment Service
6.1 Overview
Shipment Service’s operation, createAndConfirm, when invoked with the required input will receive
and process the shipment confirmation messages. This provides mechanism for external Execution
Systems to send the material and shipping details for the shipment lines fulfilled using those systems.
For integration purposes, external Execution Systems will invoke this service when needed.
This service will interpret and transform the message, and create the necessary records in the
shipping open interface tables. This service will expect the shipment confirmation along the
following details/limitations:
 The content and structure of the message will be as detailed in the shipment confirmation
message payload spreadsheet linked in the document references section
 Some level of customization/manual intervention will be needed on the external systems to
interpret and populate the lookup based attribute values and flexfield based attribute values.
 Any id attributes such as transaction id, lpn id etc., will not be expected as they will be
generated internally.
This method accepts an input payload with shipment information. It then inserts this information
into shipping interface tables for further processing.

The URL for Shipment Service is http://<server-name>:<port-
number>/wshDeliveriesService/ShipmentService. This has an operation createAndConfirm and its
asynchronous version createAndConfirmAsync.
6.2.1 createAndConfirm
The send receipt advice service has one operation processReceiptConfirmations and its asynchronous
equivalent is processReceiptConfirmationsAsync.
 ns1:shipment - This node or object represents the header of the Shipment
o ns2:ShipmentName - Unique identifier for the shipment
o ns2:Description - Description for the shipment
o ns2:OrganizationCode - Unique identifier for a ship-from organization
o ns2:InitialPickupDate - Date on which the shipment is planned to be shipped
o ns2:BillOfLadingNumber - A receipt given by the carrier to the shipper

acknowledging receipt of the goods being shipped and specifying the terms of
shipment
o ns2:GrossWeight - Gross weight for the shipment
o ns2:NetWeight - Net weight for the shipment

o ns2:WeightUOMName - Unit of measure for weight
o ns2:Equipment - Indicates the registration number of vehicle or equipment that is

use to transport the shipment
o ns2:EquipmentType - Represents the type of vehicle or equipment, which

transports the shipment
o ns2:SealNumber - A device used for packing units, lockers, or trucks to prove to

relevant parties that they have remained closed during transport
o ns2:Volume - Volume of the shipment
o ns2:VolumeUOMName - Unit of measure for volume of the shipment
o ns2:CarrierName - Name of the party that transports the shipment
o ns2:ServiceLevel - Priority of transportation that affects how quickly goods are

transported
o ns2:ModeOfTransport - Various modes of transportation used for the movement of

goods
o ns2:Waybill - Non-negotiable document describing the contract for transporting

cargo
o ns2:PackingSlipNumber - Document that itemizes in detail the contents of the

shipment
o ns2:ActualShipDate - The date the shipment was actually sent
o ns2:UltimateDropoffDate - Ultimate Dropoff date
o ns2:FreightTermsCode - An agreement indicating who (the buyer or the seller)

pays the shipping costs of an order and when payment is due
o ns2:RoutingInstructions - Document or text that contains information concerning

the shipping route of a shipment
o ns2:ShippingMarks - Identifications shown on individual packages in order to help

in moving it without delay or confusion to its final destination and to enable the
checking of cargo against documents.
o ns2:FOBCode - Freight On Board. Indicates the ownership of the goods in-transit
o ns2:FOBAddress1 - Freight on Board Address Line 1
o ns2:FOBCity - Freight on Board City
o ns2:FOBCountry - Freight on Board Country
o ns2:FOBPostalCode - Freight on Board Postal Code
o ns2:FOBCounty - Freight on Board County

o ns2:FOBState - Freight on Board State
o ns2:FOBRegion - Freight on Board Region
o ns2:DockCode - Indicates the place of loading for the shipment
o ns2:CODAmount currencyCode – COD Amount
o ns2:CODCurrencyCode – Currency Code
o ns2:CODPaidBy – COD Paid By
o ns2:CODRemitTo – COD Remit To
o ns2:ASNDateSent – Date on which ASN was sent
o ns2:ConfirmedDate – Date on which Shipment was Confirmed
o ns2:ConfirmedBy – Person who performed Ship Confirm
o ns2:LoadingSequenceRule - Represents the rule to be applied on shipment lines for

loading into the truck
o ns2:ProblemContactReference – Problem Contact Reference
o ns2:AttributeCategory - Descriptive flexfield structure definition
o ns2:Attribute1 - Descriptive flexfield segment 1

o ns2:AttributeDate1 - Descriptive flexfield date segment 1
o ns2:AttributeNumber1 - Descriptive flexfield number segment 1
o ns2:AttributeTimestamp1 - Descriptive flexfield timestamp segment 1
o ns2:GlobalAttribute1 – Global Descriptive flexfield segment 1
o ns2:GlobalAttribute2 - Global Descriptive flexfield segment 2

o ns2:GlobalAttributeDate1 – Global Descriptive flexfield date segment 1
o ns2:GlobalAttributeDate2 - Global Descriptive flexfield date segment 2
o ns2:GlobalAttributeNumber1 - Global Descriptive flexfield number segment 1
o ns2:TransportationReason – Reason of Transport
o ns2:PackingUnit – Packing Unit to physically group the Shipment Lines
 ns2:LicensePlateNumber - Unique number to identify the packing unit
 ns2:TrackingNumber - Unique identifier for tracking the packing unit
 ns2:MasterSerialNumber - Master serial number for the packing unit
 ns2:SealNumber – Seal Number

 ns2:ContainerItemName - Identifier for the item of the packing unit
 ns2:ContainerVolume - Volume of material that a packing unit can hold
 ns2:ContainerVolumeUOMName - Unit of measure for container volume

for the packing unit
 ns2:FOBCode - Freight On Board. Indicates the ownership of the goods

in-transit
 ns2:GrossWeight - Weight of the packing unit including its contents
 ns2:GrossWeightUOMName - Unit of measure for the gross weight for

the packing unit
 ns2:TareWeight - Weight of the container of the packing unit
 ns2:TareWeightUOMName - Unit of measure code for the tare weight of

the packing unit
 ns2:PackingInstructions - Document or text that contains information

conerning the packing of material in the packing unit
 ns2:ShippingInstructions – Shipping Instructions
 ns2:AttributeCategory - Descriptive flexfield structure definition
 ns2:Attribute1 - Descriptive flexfield segment 1

 ns2:AttributeDate1 - Descriptive flexfield date segment 1
 ns2:AttributeNumber1 - Descriptive flexfield number segment 1
 ns2:AttributeNumber3- Descriptive flexfield number segment 3
 ns2:AttributeTimestamp1 - Descriptive flexfield timestamp segment 1
 ns2:ShippingCost (associated with Packing Unit)
 ns2:FreightCostName - Indicates the cost type predefined in the

system
 ns2:UnitAmount currencyCode - Amount for the shipping cost

per unit
 ns2:CurrencyCode - Currency code for the unit amount

 ns2:ConversionRate - Conversion rate to be used for the currency
conversion
 ns2:ConversionDate - Conversion date to be used for the

currency conversion
 ns2:ConversionTypeCode - Type for currency conversion
 ns2:AttributeCategory - Descriptive flexfield structure definition
 ns2:Attribute1 - Descriptive flexfield segment 1
 ns2:AttributeDate1 - Descriptive flexfield date segment 1

 ns2:AttributeNumber1 - Descriptive flexfield number segment 1
 ns2:AttributeNumber3- Descriptive flexfield number segment 3
 ns2:AttributeNumber10 - Descriptive flexfield number segment

10
 ns2:AttributeTimestamp1 - Descriptive flexfield timestamp

segment 1

segment 2

segment 1

segment 4

segment 5
 ns2:ShipmentLine (included in Packing Unit) - An object to store the

detailed shipment line information for a shipment
 ns2:DeliveryDetailId - Unique identifier for a shipment line
 ns2:ItemNumber - Unique identifier for the item
 ns2:Revision - Revision of item
 ns2:Subinventory - Subinventory from where the material is

shipped
 ns2:Locator - Concatenated inventory locator name from where

the material is shipped
 ns2:ShippedQuantity unitCode - Shipped quantity in requested

quantity unit of measure
 ns2:NetWeight - Net weight for the shipment line

 ns2:GrossWeight - Gross weight for the shipment line
 ns2:WeightUOMName - Unit of measure for weight
 ns2:Volume - Volume of the material for the shipment line
 ns2:VolumeUOMName - Unit of measure for volume
 ns2:LoadingSequence - Indicates the sequence of loading for the

shipment line
 ns2:PackingInstructions - Document or text that contains

information conerning the packing of material for the shipment
line
 ns2:ShippingInstructions - Shipping instructions
 ns2:DefaultTaxationCountry - Default taxation country
 ns2:TransactionBusinessCategory - Transactions category

assigned by user
 ns2:DocumentSubType - Classification to categorize a document

associated with a transaction for tax. This affects the taxability
of the transaction.
 ns2:UserDefinedFiscalClassification - Fiscal classification
 ns2:ProductFiscClassification – Product Fiscal Classification
 ns2:IntendedUse - Intended use of the material
 ns2:ProductCategory - Identifies the taxable nature of a

noninventory based item for tax determination or tax reporting
 ns2:LocationOfFinalDischarge - Final discharge location code
 ns2:TaxClassificationCode - A classification of a charge imposed

by a government through a fiscal or tax authority
 ns2:ProductType - Type of product. Possible values are: Goods,

Service
 ns2:FirstPartyTaxRegistrationNumber - First party tax

registration identifier
 ns2:ThirdPartyTaxRegistrationNumber - Third party registration

identifier
 ns2:TaxInvoiceNumber - Tax invoice number
 ns2:TaxInvoiceDate - Tax invoice date
 ns2:AssessableValue - User-enterable amount to be used as

taxable basis
 ns2:ExemptCertificateNumber - Specifies the Exemption

Number to be used during tax calculation
 ns2:ExemptReasonCode - Reason code associated with the Tax
Exemption Number


10

segment 1

segment 2

segment 3

segment 4

segment 5
 ns2:ShippingCost (associated with Shipment Line)
o ns2:FreightCostName - Indicates the cost type

predefined in the system
o ns2:UnitAmount currencyCode - Amount for the

shipping cost per unit
o ns2:CurrencyCode - Currency code for the unit amount
o ns2:ConversionRate - Conversion rate to be used for the

currency conversion
o ns2:ConversionDate - Conversion date to be used for

the currency conversion
o ns2:ConversionTypeCode - Type for currency

conversion
o ns2:AttributeCategory - Descriptive flexfield structure

definition

o ns2:AttributeDate1 - Descriptive flexfield date segment

1

2

3

4

5
o ns2:AttributeNumber1 - Descriptive flexfield number

segment 1

segment 2
o ns2:AttributeNumber3- Descriptive flexfield number

segment 3
segment 4

segment 5

segment 6

segment 7

segment 8

segment 9

segment 10
o ns2:AttributeTimestamp1 - Descriptive flexfield

timestamp segment 1

timestamp segment 2

timestamp segment 1

timestamp segment 4

timestamp segment 5
 ns2:Lot - An object to store information about a particular Lot in

a shipment
o ns2:LotNumber - Lot number of item
o ns2:SubinventoryCode - Subinventory from where the

material is shipped
o ns2:Locator - Concatenated inventory locator name

from where the material is shipped
o ns2:Serials – An object to store Serial Number

information about a particular item
 ns2:FromSerialNumber - From serial number

of the range of serial numbers for the item
shipped
 ns2:ToSerialNumber - To serial number of the

range of serial numbers for the item shipped
 ns2:SubinventoryCode - Subinventory from

where the material is shipped
 ns2:Locator - Concatenated inventory locator
name from where the material is shipped
 ns2:Serials - An object to store Serial Number information about

a particular item
o ns2:FromSerialNumber - From serial number of the

o ns2:ToSerialNumber - To serial number of the range of

serial numbers for the item shipped
o ns2:SubinventoryCode - Subinventory from where the

material is shipped

o ns2:ShippingCost (associated with Shipment)
 ns2:FreightCostName - Indicates the cost type predefined in the system
 ns2:UnitAmount currencyCode - Amount for the shipping cost per unit
 ns2:CurrencyCode - Currency code for the unit amount
 ns2:ConversionRate - Conversion rate to be used for the currency

conversion
 ns2:ConversionDate - Conversion date to be used for the currency

conversion
 ns2:ConversionTypeCode - Type for currency conversion
 ns2:AttributeCategory - Descriptive flexfield structure definition

o ns2:ShipmentLine (unpacked) - An object to store the detailed shipment line

information for a shipment
 ns2:Subinventory - Subinventory from where the material is shipped
 ns2:Locator - Concatenated inventory locator name from where the

material is shipped
 ns2:ShippedQuantity unitCode - Shipped quantity in requested quantity

unit of measure
 ns2:LoadingSequence - Indicates the sequence of loading for the shipment

line
 ns2:PackingInstructions - Document or text that contains information on

the packing of material for the shipment line
 ns2:TransactionBusinessCategory - Transactions category assigned by

user
 ns2:DocumentSubType - Classification to categorize a document

associated with a transaction for tax. This affects the taxability of the
transaction.
 ns2:ProductFiscClassification - Product Fiscal Classification
 ns2:ProductCategory - Identifies the taxable nature of a noninventory

based item for tax determination or tax reporting
 ns2:LocationOfFinalDischarge - Final discharge location code
 ns2:TaxClassificationCode - A classification of a charge imposed by a

government through a fiscal or tax authority
 ns2:ProductType - Type of product. Possible values are: Goods, Service

 ns2:FirstPartyTaxRegistrationNumber - First party tax registration
identifier
 ns2:ThirdPartyTaxRegistrationNumber - Third party registration identifier
 ns2:AssessableValue - User-enterable amount to be used as taxable basis
 ns2:ExemptCertificateNumber - Specifies the Exemption Number to be

used during tax calculation
 ns2:ExemptReasonCode - Reason code associated with the Tax

Exemption Number

 ns2:AttributeTimestamp1 - Descriptive flexfield timestamp segment 1
 ns2:ShippingCost (Shipment Line)
 ns2:FreightCostName - Indicates the cost type predefined in the

system
 ns2:UnitAmount currencyCode - Amount for the shipping cost

per unit
 ns2:CurrencyCode - Currency code for the unit amount
 ns2:ConversionRate - Conversion rate to be used for the currency

conversion
 ns2:ConversionDate - Conversion date to be used for the

currency conversion
 ns2:ConversionTypeCode - Type for currency conversion



10

segment 1

segment 2

segment 3

segment 4

segment 5
 ns2:Lot
o ns2:LotNumber
o ns2:SubinventoryCode
o ns2:Locator
o ns2:Serials
 ns2:FromSerialNumber
 ns2:ToSerialNumber
 ns2:SubinventoryCode
 ns2:Locator
 ns2:Serials
o ns2:FromSerialNumber
o ns2:ToSerialNumber
o ns2:SubinventoryCode
o ns2:Locator
 ns0:createAndConfirmResponse – Top level node that encompasses the output response of

the createAndConfirm operation of Shipment service.
 ns2:result encapsulates the Value
 ns1:Value
o ns1:ShipmentName - Unique identifier for the shipment
o ns1:Description - Description for the shipment
o ns1:OrganizationCode - Unique identifier for a ship-from

organization
o ns1:InitialPickupDate - Date on which the shipment is planned to be

shipped
o ns1:BillOfLadingNumber - A receipt given by the carrier to the

shipper acknowledging receipt of the goods being shipped and
specifying the terms of shipment
o ns1:GrossWeight - Gross weight for the shipment
o ns1:NetWeight - Net weight for the shipment
o ns1:WeightUOMName - Unit of measure for weight
o ns1:Equipment - Indicates the registration number of vehicle or

equipment that is use to transport the shipment
o ns1:EquipmentType - Represents the type of vehicle or equipment,

which transports the shipment
o ns1:SealNumber - A device used for packing units, lockers, or trucks

to prove to relevant parties that they have remained closed during
transport
o ns1:Volume - Volume of the shipment
o ns1:VolumeUOMName - Unit of measure for volume of the shipment
o ns1:CarrierName - Name of the party that transports the shipment
o ns1:ServiceLevel - Priority of transportation that affects how quickly

goods are transported
o ns1:ModeOfTransport - Various modes of transportation used for the

movement of goods
o ns1:Waybill - Non-negotiable document describing the contract for

transporting cargo
o ns1:PackingSlipNumber - Document that itemizes in detail the

contents of the shipment
o ns1:ActualShipDate - The date the shipment was actually sent
o ns1:UltimateDropoffDate - Ultimate Dropoff date
o ns1:FreightTermsCode - An agreement indicating who (the buyer or

the seller) pays the shipping costs of an order and when payment is
due
o ns1:RoutingInstructions - Document or text that contains information

concerning the shipping route of a shipment
o ns1:ShippingMarks - Identifications shown on individual packages in

order to help in moving it without delay or confusion to its final
destination and to enable the checking of cargo against documents.
o ns1:FOBCode - Freight On Board. Indicates the ownership of the

goods in-transit
o ns1:FOBCity - Freight on Board City
o ns1:FOBCountry - Freight on Board Country
o ns1:FOBPostalCode - Freight on Board Postal Code
o ns1:FOBCounty - Freight on Board County
o ns1:FOBState - Freight on Board State
o ns1:FOBRegion - Freight on Board Region
o ns1:DockCode - Indicates the place of loading for the shipment
o ns1:CODAmount currencyCode – COD Amount
o ns1:CODCurrencyCode – Currency Code
o ns1:CODPaidBy – COD Paid By
o ns1:CODRemitTo – COD Remit To
o ns1:ASNDateSent – Date on which ASN was sent
o ns1:ConfirmedDate – Date on which Shipment was Confirmed
o ns1:ConfirmedBy – Person who performed Ship Confirm
o ns1:LoadingSequenceRule - Represents the rule to be applied on

shipment lines for loading into the truck
o ns1:ProblemContactReference – Problem Contact Reference

o ns1:AttributeCategory - Descriptive flexfield structure definition

o ns1:AttributeTimestamp1 - Descriptive flexfield timestamp segment

1

2

3

4

5
o ns1:GlobalAttribute1 – Global Descriptive flexfield segment 1

o ns1:GlobalAttributeDate1 – Global Descriptive flexfield date

segment 1
o ns1:GlobalAttributeDate2 - Global Descriptive flexfield date segment

2

3

4

5
o ns1:GlobalAttributeNumber1 - Global Descriptive flexfield number

segment 1

segment 2

segment 3

segment 4

segment 5
o ns1:TransportationReason – Reason of Transport
o ns1:PackingUnit – Packing Unit to physically group the Shipment

Lines
 ns1:LicensePlateNumber - Unique number to identify the

packing unit
 ns1:TrackingNumber - Unique identifier for tracking the

packing unit
 ns1:MasterSerialNumber - Master serial number for the

packing unit
 ns1:SealNumber – Seal Number
 ns1:ContainerItemName - Identifier for the item of the

packing unit
 ns1:ContainerVolume - Volume of material that a packing

unit can hold
 ns1:ContainerVolumeUOMName - Unit of measure for
container volume for the packing unit
 ns1:FOBCode - Freight On Board. Indicates the ownership

of the goods in-transit
 ns1:GrossWeight - Weight of the packing unit including its

contents
 ns1:GrossWeightUOMName - Unit of measure for the gross

weight for the packing unit
 ns1:TareWeight - Weight of the container of the packing

unit
 ns1:TareWeightUOMName - Unit of measure code for the

tare weight of the packing unit
 ns1:PackingInstructions - Document or text that contains

information conerning the packing of material in the packing
unit
 ns1:ShippingInstructions – Shipping Instructions
 ns1:AttributeCategory - Descriptive flexfield structure

definition

 ns1:AttributeNumber1 - Descriptive flexfield number

segment 1

segment 2
 ns1:AttributeNumber3- Descriptive flexfield number

segment 3

segment 4

segment 5

segment 6

segment 7

segment 8

segment 9

segment 10
 ns1:AttributeTimestamp1 - Descriptive flexfield timestamp

segment 1

segment 2

segment 1

segment 4
segment 5
 ns1:ShippingCost (associated with Packing Unit)
 ns1:FreightCostName - Indicates the cost type

 ns1:UnitAmount currencyCode - Amount for the

 ns1:CurrencyCode - Currency code for the unit

amount
 ns1:ConversionRate - Conversion rate to be used

for the currency conversion
 ns1:ConversionDate - Conversion date to be used

 ns1:ConversionTypeCode - Type for currency

conversion
 ns1:AttributeCategory - Descriptive flexfield

structure definition

 ns1:AttributeDate1 - Descriptive flexfield date

segment 1

segment 2

segment 3

segment 4

segment 5
 ns1:AttributeNumber1 - Descriptive flexfield

number segment 1

number segment 2
 ns1:AttributeNumber3- Descriptive flexfield

number segment 3

number segment 4

number segment 5

number segment 6

number segment 7

number segment 8

number segment 9

number segment 10
 ns1:AttributeTimestamp1 - Descriptive flexfield

timestamp segment 1

timestamp segment 2
timestamp segment 1

timestamp segment 4

timestamp segment 5
 ns1:ShipmentLine (included in Packing Unit) - An object to

store the detailed shipment line information for a shipment
 ns1:DeliveryDetailId - Unique identifier for a

shipment line
 ns1:Subinventory - Subinventory from where the

material is shipped
 ns1:Locator - Concatenated inventory locator name

 ns1:ShippedQuantity unitCode - Shipped quantity

in requested quantity unit of measure
 ns1:GrossWeight - Gross weight for the shipment

line
 ns1:WeightUOMName - Unit of measure for

weight
 ns1:Volume - Volume of the material for the

shipment line
 ns1:VolumeUOMName - Unit of measure for

volume
 ns1:LoadingSequence - Indicates the sequence of

loading for the shipment line
 ns1:PackingInstructions - Document or text that

contains information conerning the packing of
material for the shipment line
 ns1:DefaultTaxationCountry - Default taxation

country
 ns1:TransactionBusinessCategory - Transactions
category assigned by user
 ns1:DocumentSubType - Classification to
categorize a document associated with a transaction
for tax. This affects the taxability of the
transaction.
 ns1:UserDefinedFiscalClassification - Fiscal
classification
 ns1:ProductFiscClassification – Product Fiscal

Classification
 ns1:ProductCategory - Identifies the taxable nature

of a noninventory based item for tax determination
or tax reporting
 ns1:LocationOfFinalDischarge - Final discharge

location code
 ns1:TaxClassificationCode - A classification of a
charge imposed by a government through a fiscal or
tax authority
 ns1:ProductType - Type of product. Possible values

are: Goods, Service
 ns1:FirstPartyTaxRegistrationNumber - First party

tax registration identifier
 ns1:ThirdPartyTaxRegistrationNumber - Third
party registration identifier
 ns1:AssessableValue - User-enterable amount to be

used as taxable basis
 ns1:ExemptCertificateNumber - Specifies the

Exemption Number to be used during tax
calculation
 ns1:ExemptReasonCode - Reason code associated

with the Tax Exemption Number



segment 1

segment 2

segment 3

segment 4

segment 5

number segment 1

number segment 2

number segment 3

number segment 4
number segment 5

number segment 6

number segment 7

number segment 8

number segment 9

number segment 10

timestamp segment 1

timestamp segment 2

timestamp segment 3

timestamp segment 4

timestamp segment 5
 ns1:ShippingCost (associated with Shipment Line)
o ns1:FreightCostName - Indicates the cost

type predefined in the system
o ns1:UnitAmount currencyCode - Amount

for the shipping cost per unit
o ns1:CurrencyCode - Currency code for the

unit amount
o ns1:ConversionRate - Conversion rate to

be used for the currency conversion
o ns1:ConversionDate - Conversion date to

be used for the currency conversion
o ns1:ConversionTypeCode - Type for

currency conversion
o ns1:AttributeCategory - Descriptive
flexfield structure definition
o ns1:Attribute1 - Descriptive flexfield

segment 1
segment 2

segment 3

segment 4

segment 5

segment 6

segment 7

segment 8

segment 9

segment 10

segment 11

segment 12

segment 13

segment 14

segment 15

segment 16

segment 17

segment 18

segment 19

segment 20
o ns1:AttributeDate1 - Descriptive flexfield

date segment 1
date segment 2

date segment 3

date segment 4

date segment 5
o ns1:AttributeNumber1 - Descriptive
flexfield number segment 1
o ns1:AttributeNumber3- Descriptive
o ns1:AttributeTimestamp1 - Descriptive
flexfield timestamp segment 1
 ns1:Lot - An object to store information about a

particular Lot in a shipment
o ns1:SubinventoryCode - Subinventory
o ns1:Locator - Concatenated inventory

locator name from where the material is
shipped
o ns1:Serials – An object to store Serial

Number information about a particular
item
 ns1:FromSerialNumber - From
serial number of the range of
serial numbers for the item
shipped
 ns1:ToSerialNumber - To serial
number of the range of serial
numbers for the item shipped
 ns1:SubinventoryCode -
Subinventory from where the
material is shipped
 ns1:Locator - Concatenated
inventory locator name from
 ns1:Serials - An object to store Serial Number

information about a particular item
o ns1:FromSerialNumber - From serial

number of the range of serial numbers for
the item shipped
o ns1:ToSerialNumber - To serial number of

the range of serial numbers for the item
shipped
o ns1:SubinventoryCode - Subinventory
o ns1:Locator - Concatenated inventory

shipped
o ns1:ShippingCost (associated with Shipment)
 ns1:FreightCostName - Indicates the cost type predefined in

the system
 ns1:UnitAmount currencyCode - Amount for the shipping

cost per unit
 ns1:CurrencyCode - Currency code for the unit amount
 ns1:ConversionRate - Conversion rate to be used for the

currency conversion
 ns1:ConversionDate - Conversion date to be used for the
currency conversion
 ns1:ConversionTypeCode - Type for currency conversion
 ns1:AttributeCategory - Descriptive flexfield structure

definition

segment 1

segment 2

segment 3

segment 4

segment 5

segment 6

segment 7

segment 8

segment 9

segment 10

segment 1

segment 2

segment 3

segment 4

segment 5
o ns1:ShipmentLine (unpacked) - An object to store the detailed

shipment line information for a shipment
 ns1:Subinventory - Subinventory from where the material is

shipped
 ns1:Locator - Concatenated inventory locator name from

 ns1:ShippedQuantity unitCode - Shipped quantity in
requested quantity unit of measure
 ns1:LoadingSequence - Indicates the sequence of loading for

the shipment line
 ns1:PackingInstructions - Document or text that contains

information conerning the packing of material for the
shipment line
 ns1:TransactionBusinessCategory - Transactions category

assigned by user
 ns1:DocumentSubType - Classification to categorize a

document associated with a transaction for tax. This affects
the taxability of the transaction.
 ns1:ProductFiscClassification - Product Fiscal Classification
 ns1:ProductCategory - Identifies the taxable nature of a

noninventory based item for tax determination or tax
reporting
 ns1:LocationOfFinalDischarge - Final discharge location

code
 ns1:TaxClassificationCode - A classification of a charge

imposed by a government through a fiscal or tax authority
 ns1:ProductType - Type of product. Possible values are:

Goods, Service
 ns1:FirstPartyTaxRegistrationNumber - First party tax

 ns1:ThirdPartyTaxRegistrationNumber - Third party


 ns1:AssessableValue - User-enterable amount to be used as

taxable basis
 ns1:ExemptCertificateNumber - Specifies the Exemption

Number to be used during tax calculation
 ns1:ExemptReasonCode - Reason code associated with the

Tax Exemption Number
 ns1:AttributeCategory - Descriptive flexfield structure

definition

 ns1:AttributeNumber1 - Descriptive flexfield number

segment 1

segment 2

segment 3

segment 4

segment 5

segment 6

segment 7

segment 8

segment 9

segment 10

segment 1

segment 2

segment 3

segment 4

segment 5
 ns1:ShippingCost (Shipment Line)
 ns1:FreightCostName - Indicates the cost type

 ns1:UnitAmount currencyCode - Amount for the

 ns1:CurrencyCode - Currency code for the unit
amount
 ns1:ConversionRate - Conversion rate to be used

 ns1:ConversionDate - Conversion date to be used

 ns1:ConversionTypeCode - Type for currency

conversion


segment 1
segment 2

segment 3

segment 4

segment 5

number segment 1

number segment 2

number segment 3

number segment 4

number segment 5

number segment 6

number segment 7

number segment 8

number segment 9

number segment 10

timestamp segment 1

timestamp segment 2

timestamp segment 3

timestamp segment 4

timestamp segment 5
 ns1:Lot
o ns1:SubinventoryCode - Subinventory from where


o ns1:Serials
 ns1:FromSerialNumber - From serial

number of the range of serial numbers for
the item shipped
 ns1:ToSerialNumber - To serial number of

the range of serial numbers for the item
shipped
 ns1:SubinventoryCode - Subinventory
 ns1:Locator - Concatenated inventory

shipped
 ns1:Serials
o ns1:FromSerialNumber - From serial number of the

o ns1:ToSerialNumber - To serial number of the

o ns1:SubinventoryCode - Subinventory from where

o ns1: Locator - Concatenated inventory locator name

6.5.1 Shipment Confirmation for Plain Item
The following sample will create shipment confirmation for associated Shipment Lines and interface
these transactions in Shipping. The quantities entered in the payload indicate that 3 Each will be
shipped.
<ns1:createAndConfirm
xmlns:ns1="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentService/types/">
<ns1:shipment
xmlns:ns2="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentService/">
<ns2:ShipmentName>HLG-OCT22-MULTIPACK1-DEL</ns2:ShipmentName>
<ns2:GrossWeight>1000</ns2:GrossWeight>
<ns2:NetWeight>500</ns2:NetWeight>
<ns2:WeightUOMName>Pounds</ns2:WeightUOMName>
<ns2:Volume>2000</ns2:Volume>
<ns2:VolumeUOMName>Cubic foot</ns2:VolumeUOMName>
<ns2:ShipmentLine>
<ns2:DeliveryDetailId>3503638</ns2:DeliveryDetailId>
<ns2:Subinventory>EACH</ns2:Subinventory>
<ns2:Locator>E1.1.1</ns2:Locator>
<ns2:ShippedQuantity unitCode="Each">3</ns2:ShippedQuantity>
</ns2:ShipmentLine>
</ns1:shipment>
</ns1:createAndConfirm>
6.5.1 Shipment Confirmation for Plain/Lot/Serial Controlled Item
The following sample will create shipment confirmation for associated Shipment Lines and interface
these transactions in Shipping. The payload includes Packing Unit, Shipping Costs, Shipment Line,
Lot, Serial attributes for a Shipment.
<ns1:createAndConfirm
<ns1:shipment
xmlns:ns2="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentService/">
<ns2:PackingUnit>
<ns2:LicensePlateNumber>HLG-OCT22-MULTIPACK1-LPN</ns2:LicensePlateNumber>
<ns2:ContainerItemName>WMC555</ns2:ContainerItemName>
<ns2:ContainerVolume>10</ns2:ContainerVolume>
<ns2:ContainerVolumeUOMName>Cubic foot</ns2:ContainerVolumeUOMName>
<ns2:GrossWeightUOMName>Pounds</ns2:GrossWeightUOMName>
<ns2:TareWeight>1</ns2:TareWeight>
<ns2:TareWeightUOMName>Pounds</ns2:TareWeightUOMName>
<ns2:ShippingCost>
<ns2:FreightCostName>Handling</ns2:FreightCostName>
<ns2:UnitAmount currencyCode="USD">200</ns2:UnitAmount>
</ns2:ShippingCost>
<ns2:ShipmentLine>
<ns2:ShippingCost>
</ns2:ShippingCost>
</ns2:ShipmentLine>
<ns2:ShipmentLine>
<ns2:AssessableValue>2000</ns2:AssessableValue>
<ns2:Serials>
<ns2:FromSerialNumber>SS1257</ns2:FromSerialNumber>
<ns2:ToSerialNumber>SS1259</ns2:ToSerialNumber>
<ns2:SubinventoryCode>EACH</ns2:SubinventoryCode>
</ns2:Serials>
<ns2:ShippingCost>
<ns2:UnitAmount>1000</ns2:UnitAmount>
</ns2:ShippingCost>
</ns2:ShipmentLine>
<ns2:ShipmentLine>
<ns2:Lot>
<ns2:LotNumber>LL0000</ns2:LotNumber>
<ns2:TransactionQuantity unitCode="Each">3</ns2:TransactionQuantity>
</ns2:Lot>
<ns2:ShippingCost>
<ns2:UnitAmount>1000</ns2:UnitAmount>
</ns2:ShippingCost>
</ns2:ShipmentLine>
</ns2:PackingUnit>
</ns1:shipment>
</ns1:createAndConfirm>
6.6 Sample Output Response of CreateAndConfirm Operation
6.6.1 Sample response when Shipment Confirmation is interfaced successfully
This sample payload comprises the situation where the Shipment confirmation that were transmitted
through this service are successfully interfaced to fusion shipping open interface schema.
<ns0:createAndConfirmResponse
<ns2:result xmlns:ns0="http://xmlns.oracle.com/adf/svc/types/"
xmlns:ns1="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentService/"
xmlns:ns2="http://xmlns.oracle.com/apps/scm/shipping/shipConfirm/deliveries/shipmentService/types/"
xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:ShipmentInterfaceResult">
<ns1:Value>
<ns1:Description xsi:nil="true"/>
<ns1:InitialPickupDate xsi:nil="true"/>
<ns1:BillOfLadingNumber xsi:nil="true"/>
<ns1:Equipment xsi:nil="true"/>
<ns1:EquipmentType xsi:nil="true"/>
<ns1:SealNumber xsi:nil="true"/>
<ns1:Waybill xsi:nil="true"/>
<ns1:PackingSlipNumber xsi:nil="true"/>
<ns1:ActualShipDate xsi:nil="true"/>
<ns1:UltimateDropoffDate xsi:nil="true"/>
<ns1:RoutingInstructions xsi:nil="true"/>
<ns1:ShippingMarks xsi:nil="true"/>
<ns1:FOBAddress1 xsi:nil="true"/>
<ns1:FOBCity xsi:nil="true"/>
<ns1:FOBCountry xsi:nil="true"/>
<ns1:FOBPostalCode xsi:nil="true"/>
<ns1:FOBCounty xsi:nil="true"/>
<ns1:FOBState xsi:nil="true"/>
<ns1:FOBRegion xsi:nil="true"/>
<ns1:DockCode xsi:nil="true"/>
<ns1:CODAmount xsi:nil="true"/>
<ns1:CODCurrencyCode xsi:nil="true"/>
<ns1:CODPaidBy xsi:nil="true"/>
<ns1:CODRemitTo xsi:nil="true"/>
<ns1:ASNDateSent xsi:nil="true"/>
<ns1:ConfirmedDate xsi:nil="true"/>
<ns1:ConfirmedBy xsi:nil="true"/>
<ns1:LoadingSequenceRule xsi:nil="true"/>
<ns1:ProblemContactReference xsi:nil="true"/>
<ns1:AttributeCategory xsi:nil="true"/>
<ns1:Attribute1 xsi:nil="true"/>
<ns1:AttributeDate1 xsi:nil="true"/>
<ns1:AttributeNumber1 xsi:nil="true"/>
<ns1:AttributeTimestamp1 xsi:nil="true"/>
<ns1:GlobalAttribute1 xsi:nil="true"/>
<ns1:GlobalAttributeCategory xsi:nil="true"/>
<ns1:GlobalAttributeDate1 xsi:nil="true"/>
<ns1:GlobalAttributeNumber1 xsi:nil="true"/>
<ns1:TransportationReason xsi:nil="true"/>
<ns1:PackingUnit>
<ns1:LicensePlateNumber>HLG-OCT22-MULTIPACK1-LPN</ns1:LicensePlateNumber>
<ns1:TrackingNumber xsi:nil="true"/>
<ns1:MasterSerialNumber xsi:nil="true"/>
<ns1:SealNumber xsi:nil="true"/>
<ns1:ContainerItemName>WMC555</ns1:ContainerItemName>
<ns1:ContainerVolume>10</ns1:ContainerVolume>
<ns1:ContainerVolumeUOMName>Cubic foot</ns1:ContainerVolumeUOMName>
<ns1:GrossWeightUOMName>Pounds</ns1:GrossWeightUOMName>
<ns1:TareWeight>1</ns1:TareWeight>
<ns1:TareWeightUOMName>Pounds</ns1:TareWeightUOMName>
<ns1:ShippingCost>
<ns1:ConversionTypeCode xsi:nil="true"/>
</ns1:ShippingCost>
<ns1:ShipmentLine>
<ns1:Revision xsi:nil="true"/>
<ns1:SecondaryShippedQuantity xsi:nil="true"/>
<ns1:NetWeight xsi:nil="true"/>
<ns1:GrossWeight xsi:nil="true"/>
<ns1:WeightUOMName xsi:nil="true"/>
<ns1:Volume xsi:nil="true"/>
<ns1:VolumeUOMName xsi:nil="true"/>
<ns1:LoadingSequence xsi:nil="true"/>
<ns1:DefaultTaxationCountry xsi:nil="true"/>
<ns1:TransactionBusinessCategory xsi:nil="true"/>
<ns1:DocumentSubType xsi:nil="true"/>
<ns1:UserDefinedFiscalClassification xsi:nil="true"/>
<ns1:ProductFiscClassification xsi:nil="true"/>
<ns1:IntendedUse xsi:nil="true"/>
<ns1:ProductCategory xsi:nil="true"/>
<ns1:LocationOfFinalDischarge xsi:nil="true"/>
<ns1:TaxClassificationCode xsi:nil="true"/>
<ns1:ProductType xsi:nil="true"/>
<ns1:FirstPartyTaxRegistrationNumber xsi:nil="true"/>
<ns1:ThirdPartyTaxRegistrationNumber xsi:nil="true"/>
<ns1:TaxInvoiceNumber xsi:nil="true"/>
<ns1:TaxInvoiceDate xsi:nil="true"/>
<ns1:AssessableValue xsi:nil="true"/>
<ns1:ExemptCertificateNumber xsi:nil="true"/>
<ns1:ExemptReasonCode xsi:nil="true"/>
<ns1:ShippingCost>
</ns1:ShippingCost>
</ns1:ShipmentLine>
<ns1:ShipmentLine>
<ns1:Locator xsi:nil="true"/>
<ns1:ShippingCost>
</ns1:ShippingCost>
<ns1:Serials>
<ns1:FromSerialNumber>SS1257</ns1:FromSerialNumber>
<ns1:ToSerialNumber>SS1259</ns1:ToSerialNumber>
</ns1:Serials>
</ns1:ShipmentLine>
<ns1:ShipmentLine>
<ns1:Locator xsi:nil="true"/>
<ns1:ShippingCost>
</ns1:ShippingCost>
<ns1:Lot>
<ns1:LotNumber>LL0000</ns1:LotNumber>
<ns1:TransactionQuantity unitCode="Each">3</ns1:TransactionQuantity>
<ns1:SecondaryTransactionQuantity xsi:nil="true"/>
</ns1:Lot>
</ns1:ShipmentLine>
<ns1:PackingUnit>
</ns1:Value>
</ns2:result>
</ns0:createAndConfirmResponse>

Oracle Fusion Logistics: Web Services For Integration With Execution Systems

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Fusion Logistics: Web Services For Integration With Execution Systems

Uploaded by

Copyright:

Available Formats

Oracle Fusion Logistics

1.1 List of relevant External Services in Fusion Logistics ..............................................................4

2. Send Receipt Advice ............................................................................................................................5

2.1 Overview ....................................................................................................................................5

2.2 Service Operations .....................................................................................................................6

2.4 Components of Response Payload .............................................................................................7

2.5 Sample Input Payloads ...............................................................................................................9

3. Receive Receipt Confirmation ..........................................................................................................17

3.1 Overview ..................................................................................................................................17

3.2 Service Operations ...................................................................................................................17

3.4 Components of Input Payload ..................................................................................................17

3.5 Components of Response Payload ...........................................................................................19

3.6 Sample Input Payloads .............................................................................................................20

4.1 Overview ..................................................................................................................................27

4.2 Service Operations ...................................................................................................................27

5. Shipment Line Service .......................................................................................................................32

5.1 Overview ..................................................................................................................................32

5.2 Service Operations ...................................................................................................................32

5.4 Components of Response Payload ...........................................................................................33

5.5 Sample Input Payloads .............................................................................................................39

6. Shipment Service ................................................................................................................................45

6.1 Overview ..................................................................................................................................45

6.2 Service Operations ...................................................................................................................45

6.4 Components of Response Payload ...........................................................................................66

6.5 Sample Input Payloads .............................................................................................................89

1.1 List of relevant External Services in Fusion Logistics

 Send Receipt Advice

 Receive Receipt Confirmation

o Service to receive receipt confirmations on expected shipment lines into Fusion

 Transaction Manager Service

o Service to process material transactions in Fusion Inventory.

 Shipment Line - generateShipmentRequest

o Service to accept shipment confirmation on shipment lines into Fusion Shipping

 RMA related – RMA number, RMA line number

2.2 Service Operations

2.3 Components of Input Payload

 ns1:ReceiptAdviceParameter – This node or object represents the criteria of the expected

o OrganizationCode / OrganizationId – These are mandatory attributes. The expected

o Purchase Order attributes

 PO Number (attribute name PurchaseOrder), PO Line (attribute name

 PurchaseOrderHeaderId, PurchaseOrderLineId and

o In-transit Shipment attributes

 In-transit shipment number (attribute name IntransitShipment), In-transit

 IntransitShipmentHeaderId and IntransitShipmentLineId – Internal

o Transfer Order attributes

 Transfer Order Header Number (attribute name TransferOrder), Transfer

 RMAHeaderId and RMALineId – internal identifiers for RMA number

 Supplier name (attribute name Supplier), Supplier identifier (attribute

 Supplier site code (attribute name SupplierSite), supplier site identifier

o Customer – Customer name (attribute Customer) and Customer identifier (attribute

o ReceivingLocation – Location Code (attribute name ReceivingLocation) and

o Resend – This parameter controls whether you want to re-send an already

2.4 Components of Response Payload

 ns0:getReceiptAdviceDetailsResponse – Top level node that encompasses the output

 ns0:ReceiptAdviceLine – Represents the individual receipt advice line and corresponds to

 UPDATE – If this receipt advice line was previously transmitted earlier

o Document Type – PO (Purchase Order), INVENTORY (In-transit shipment),

o Receipt source (VENDOR, CUSTOMER, INVENTORY, TRANSFER ORDER),

o Supplier information – Supplier and Supplier Site

o Supplier item reference, customer item reference if any

o Document quantities in both ordered and secondary UOM

o Receiving controls – Receipt routing, over receipt tolerance percentage, over

o Comments, Notes to receiver