Oracle Carrier Manifesting Partner

Integration: Specifications

Version : Final
Prepared By : Product Management, Oracle Shipping Execution
Control Ref : manifestptnrint.rtf
Last Updated : 23-Oct-06

Manifestptnrint.doc Oracle Confidential - For internal use only

Contents

Overview.................................................................................................................................................................... 4

Process Flows ............................................................................................................................................................ 5

Manifesting Flow at Ship Time .............................................................................................................................. 6
End of Day Manifest Flow...................................................................................................................................... 7
Manifesting Process Flow....................................................................................................................................... 8

Major Features.......................................................................................................................................................... 9
Interface with Manifest Partner Application........................................................................................................... 9
Shipment Data Update .......................................................................................................................................... 10
Error Message Processing..................................................................................................................................... 12

Partner Requirements ............................................................................................................................................ 16

Manifest Setup ........................................................................................................................................................ 17

Shipping Execution Setup..................................................................................................................................... 17
Inventory Setup..................................................................................................................................................... 19
Oracle XML Gateway Setup................................................................................................................................. 20
Oracle Workflow Agent Listener Setup................................................................................................................ 23

Manifest Integration Test Suggestions.................................................................................................................. 25

Test Objectives ..................................................................................................................................................... 25
Setup ..................................................................................................................................................................... 25
Test Flow .............................................................................................................................................................. 25
Validate Test Flow................................................................................................................................................ 26
Troubleshooting .................................................................................................................................................... 26

Appendix A – Shipment Request XML................................................................................................................. 28

Appendix B – Shipment Advice XML................................................................................................................... 37

Appendix C – Manifest Integration FAQ ............................................................................................................. 38

Appendix D – Supporting Documentation............................................................................................................ 40

Manifestptnrint.doc Oracle Confidential - For internal use only 2

Figures & Tables

Fig 1: Manifest Process Flow .................................................................................................................................6

Fig 2: Carrier End of Day Manifest Process Flow..................................................................................................7
Fig 3: Manifest Messaging Overview.....................................................................................................................9
Table 1: ShowShipment Request DTD.................................................................................................................10
Table 2: ShowShipment Advice DTD ..................................................................................................................10
Fig 4: Shipment Data Update Table......................................................................................................................11
Fig 5: LPN/Container Tracking Number ..............................................................................................................12
Fig 6: Shipping Transactions Form -View Message History................................................................................12
Fig 7: Shipment Message Corrections Form.........................................................................................................13
Fig 8: Transaction Monitor – Outbound ShowShipment Request ........................................................................14
Fig 9: Transaction Monitor – Inbound ShowShipment Advice ............................................................................14
Fig 10: Workflow Status Monitor.........................................................................................................................15
Fig 11: Carrier Setup Form...................................................................................................................................17
Fig 12: Automated Carrier Manifesting Interface.................................................................................................18
Fig 13: Organization Parameter Setup Form ........................................................................................................19
Fig 14: Trading Partner Setup Form .....................................................................................................................22
Fig 15: Trading Partner Code Conversion Form ..................................................................................................23
Fig 16: Workflow Agent Listener Request ...........................................................................................................24

Manifestptnrint.doc Oracle Confidential - For internal use only 3

Overview

The purpose of this document is to cover in detail Oracle’s Manifest Integration. This document
will serve as a guide to manifest partners, implementers, and users of Oracle’s Manifest
Integration.

Oracle’s Manifest Integration enables Oracle E-Business Suite to integrate with manifest partner
applications. The integration allows shipment information to be communicated between Oracle
Order Management/Shipping Execution and the manifest partner application. The integration uses
XML messaging to send and receive shipment information between Order Management/Shipping
Execution and the manifest partner application. A shipment request message is sent to the manifest
partner application communicating the necessary details to process the shipment. Once the
shipment has been processed, a shipment advice message is sent from the manifest partner
application to update the delivery attributes.

Another feature of Oracle’s Manifest Integration is the ability to identify and process error
messages. The status of the outbound shipment request message can be viewed within the
Shipping Execution application. Furthermore, users can access the Shipment Message Corrections
form and correct those inbound shipment advice transactions that have failed. The document will
also cover the Workflow Transaction Monitor and Workflow Status Monitor, which provide
additional capabilities to identify issues and take corrective action.

The document details the steps necessary to implement Oracle’s Manifest Integration. Setup in
Oracle Shipping Execution, Oracle Inventory, Oracle XML Gateway, and Oracle Workflow are
covered.

Oracle’s Manifest Integration provides two separate process flows. The Automated Carrier
Manifesting interface allows users to automatically send outbound shipment requests to the
manifest partner application for processing. A manual manifesting process flow is also available
where users can manually select delivery lines and send them to the manifest partner application
for processing.

Additional topics covered in the document are manifest partner requirements needed to implement
Oracle’s Manifest Integration and integration test suggestions. The integration test suggestions are
designed to assist implementers with suggested methods of integration testing.

The document concludes with an appendix. The appendix provides the ShowShipment message
structure and element description. A table is provided with a description of each element/attribute
in the ShowShipment message. Additionally, the appendix includes a listing of the primary
attributes that would be updated by the manifest partner. Lastly, the document concludes with a
manifest integration FAQ. The FAQ is intended to guide users on those areas that may require
additional attention during implementing and usage.

Manifestptnrint.doc Oracle Confidential - For internal use only 4

 Process Flows
This section outlines the manifesting process flows. Manifesting occurs at ship time throughout
the course of the day. The manifest close out procedure occurs at the end of the day upon carrier
pickup. The process at ship time is triggered by every shipment request and involves
communication between Oracle E-Business Suite and the manifest partner application. The end of
the day process, on the other hand, involves transmission of manifest data from the manifest
partner application to the carrier host system.

Manifestptnrint.doc Oracle Confidential - For internal use only 5

 Manifesting Flow at Ship Time

Diagram Note: The shipper selects a delivery, picks and

Solid Lines indicate packs it, assigns a ship method to it, and
Prepare shipment generates a pick slip for it.
activities performed in
Oracle
Dashed Lines indicate
activities performed in
Manifest Partner
Application
The shipper sends an outbound shipment
Send outbound request message to the manifest partner
shipment request application. The message includes delivery
message name, customer, carrier, service level, ship
to, pick up/drop off date and time, freight
terms, etc.

The manifest partner application receives

the shipment request, optionally weighs it,
Manifest applies freight rates, prints shipment
documents such as shipment address label,
and assigns a tracking number to the
delivery, and then sends a shipment advice
message back to Oracle E-Business Suite

The shipper receives the inbound shipment

Receive inbound advice message causing the delivery to get
shipment advice ship confirmed. The message includes
message delivery name, carrier, service level, ship
date, freight cost, tracking number, etc.

The relevant modules of the E-Business

Suite are updated with the information
Update Oracle E- contained in the inbound shipment advice
Business Suite message.

Fig 1: Manifest Process Flow

Manifestptnrint.doc Oracle Confidential - For internal use only 6

 End of Day Manifest Flow

Diagram Note: The manifest partner application closes out

Solid Lines indicate for the day.
Close out
activities performed in
Oracle
Dashed Lines indicate
activities performed in
Manifest Partner
Application
The manifest partner application prints daily
report of shipping activity for shipper’s
Print record.

The manifest partner application transmits

manifest data to the carrier host systems.
Transmit manifest
data to carrier The carriers then issue freight bills to the
host system shipper, based on manifest data they receive.

Fig 2: Carrier End of Day Manifest Process Flow

Manifestptnrint.doc Oracle Confidential - For internal use only 7

Manifesting Process Flow
The following steps describe the manifest process.

1. The Oracle Order Management/Shipping Execution user selects the lines that are going to be
shipped that require carrier manifesting by manually selecting the sales order lines on the
Shipping Transactions form. The user will assign the lines to a delivery, pick and pack the
delivery. The user selects the action “Send Outbound Message”, and then selects Shipment
Request. The Delivery will be flagged as “Interfaced, Waiting for Response” so that it cannot
be shipped until the response is received from the partner manifesting system.

2. A business event is raised that will in turn trigger the workflow to extract the data from WSH
tables and create the XML message. The data that is extracted is the data needed by the
manifest partner application to rate the shipment, choose the carrier, calculate the total freight
costs, and generate the required labels and shipping documents. This message is sent through
the XML Gateway to the Oracle Transport Agent (OTA). The OTA at the manifest partner
instance picks up the message and sends it to the partner manifest application. The manifest
partner application obtains the XML message, and processes it.

NOTE: The Shipment Request can be canceled provided the manifest partner
application has not processed the request. To cancel the request, navigate to the
Shipping Transactions form and select the Action ‘Send Outbound Message’. In the
Send Outbound Message dialog box, select ‘Send Shipment Cancellation’ and click the
OK button. Once the cancellation has been processed the delivery status will change
from ‘Shipment Requested’ to ‘Open’. In addition to sending the sending the shipment
cancellation request, the delivery must also be cancelled or voided in the manifest
partner application.

The warning message below will be displayed when the Shipment Cancellation has been
initiated.

“Warning: Shipment Request Cancellation has been initiated. Delivery 908240 must
also be cancelled or voided in the Manifesting Application to complete the cancellation
process”

3. The manifest partner application creates a response transaction. This response will include
shipment header level information, such as the carrier, ship method, freight terms, and so on.
The manifest partner application creates an XML Shipment Advice transaction to be
transferred to Oracle Order Management/Shipping Execution.

4. The XML Gateway Engine at the manifest partner instance consumes the message, and it
loads the data into the WSH INTERFACE tables. Then, the appropriate Shipping APIs are
called to populate the WSH Base tables.

5. The Shipping APIs update the delivery with the shipment information and the item details,
and Confirms the shipment. The Order Management Interface and, if the item is transactable,
the Inventory Interface are submitted to complete the shipping process.

Manifestptnrint.doc Oracle Confidential - For internal use only 8

Major Features
Oracle’s Manifest Integration enables communication between Oracle Order
Management/Shipping Execution and manifest partner applications. The primary feature is the
ability to seamlessly integrate with manifest partner applications. Additional features include the
automatic receipt and update of shipment information in Oracle E-Business Suite and the ability to
identify transactional errors and make corrections.

Interface with Manifest Partner Application

Oracle’s Manifest Integration supports XML based communication capabilities with the manifest
partner application. The manifest partner application must be able to receive an XML
ShowShipment Request message and respond with an XML ShowShipment Advice message.

ShowShipment Request XML

Oracle Order Manifest
Management / Partner
ShowShipment Advice XML
Shipping
Application
Execution

Fig 3: Manifest Messaging Overview

ShowShipment Request Message

The purpose of the ShowShipment Request message is to communicate shipment information to
the manifest partner application. The ShowShipment Request transaction (the XML equivalent of
the ASC X12 940 transaction) is a modified version of the Open Applications Group (OAG)
document type definition (DTD) show_shipment_005. This DTD is used to send shipment
information from Oracle to the manifest partner application.

Shipment information can include Ship From Location, Ship to Location, Delivery Weight,
Carrier, Service Level, etc. A Shipment Advice XML message is expected from the manifest
partner application. The ShowShipment Request DTD, its structure and element description are
provided in Appendix A.

ShowShipment Advice Message

The purpose of the ShowShipment Advice message is to communicate shipment information from
the manifest partner application to Oracle Order Management/Shipping Execution. The
ShowShipment Advice transaction (the XML equivalent of the ASC X12 945 transaction) is a
modified version of the OAG DTD show_shipment_005. The ShowShipment Advice message
updates delivery information such as actual carrier and service level used for the shipment,
tracking numbers, total weight, and freight cost amount.
Table 1 and Table 2 below summarizes each of the supported DTDs:

Manifestptnrint.doc Oracle Confidential - For internal use only 9

 Request DTDs Supported

ShowShipment Request DTD DTD Details

ShowShipment Request ShowShipment Request XML Appendix A

Table 1: ShowShipment Request DTD

Response DTDs Supported

ShowShipment Advice DTD DTD Details

ShowShipment Advice ShowShipment Advice XML Appendix B

Table 2: ShowShipment Advice DTD

Shipment Data Update

One of the primary functions of the manifest partner application is to capture data at the time of
shipment. The ShowShipment Advice message is used to communicate shipment information back
to Oracle E-Business Suite for update. The manifest partner application captures this data at the
time of shipment. Shipment data can include the carrier tracking number, freight charges, carrier,
carrier service level, and weight.

Once the manifest partner application has processed the shipment, the ShowShipment Advice
message is sent to Oracle E-Business Suite. Upon successful receipt of the ShowShipment Advice
message, the delivery attributes are automatically updated. Some of the typical delivery attributes
updated are carrier, service level, ship date, weight, tracking number, freight charges, and weight.
For example, the carrier tracking number is typically assigned when the shipment is manifested.
The ShowShipment Advice message would be sent to Oracle E-Business Suite with the attribute
<TRACKINGID> populated for the element <SHIPUNIT>. When the ShowShipment Advice is
received the field Tracking Number is automatically updated for the LPN/Container.

The manifest partner is required to make the following changes to the XML document.

- Remove all occurrences of <SHIPITEM>...... </SHIPITEM>

- Change "SR" to "SA" in <DOCTYPE>SR</DOCTYPE>

- Change DocumentId to some new value in <DOCUMENTID>351-I</DOCUMENTID>

- Give a value to "ORACLE.ORIG_DOCID" using the value in <DOCUMENTID> that

was present in the corresponding outbound XML message. For example,
<ORACLE.ORIG_DOCID/> should become
"<ORACLE.ORIG_DOCID>351</ORACLE.ORIG_DOCID>". The value 351 is taken
from the element/attribute <DOCUMENTID> contained in the outbound XML message.

- Charges can be entered for the SHIPMENT and SHIPUNIT. It is important to note the
<CHARGE> segment is not included in the ShowShipment Request message. This
segment needs to be inserted by the manifest partner. This segment is required provided
there are charges associated with the SHIPMENT or SHIPUNIT.

Manifestptnrint.doc Oracle Confidential - For internal use only 10

 The table in Fig 4 indicates the field updated in Oracle E-Business Suite based on the attribute
value supplied by the manifest partner application. The intent of this table is to show several of the
primary attributes captured by the manifest partner application at the time of shipment. The table
also shows the corresponding shipment data field updated in Oracle E-Business Suite.
Field Updated in Oracle Attribute Supplied by Manifest Partner

Carrier The field Carrier on the Delivery is updated from the attribute
SHIPMENT.CARRIER
Service Level The field Service Level on the Delivery is updated from the
attribute SHIPMENT.CARRSRVLVL
Waybill The field Waybill on the Delivery is updated from the
SHIPMENT.USERAREA ORACLE.WAYBILL
Tracking Number The field Tracking Number on the Line/LPN is updated from the
attribute SHIPUNIT.TRACKINGID
Delivery Gross Weight The field Gross Weight on the Delivery is updated from the
attribute SHIPMENT.QUANTITY (TOTWEIGHT)
LPN/Container Gross The field Gross Weight on the LPN is updated from the attribute
Weight SHIPUNIT.QUANTITY (TOTWEIGHT)
Delivery Freight Cost The Delivery freight cost amount is updated from the attribute
Amount CHARGE.OPERAMT (EXTENDED) (T) for the SHIPMENT
Delivery Freight Cost The Delivery freight cost name is updated from the attribute
Name CHARGE.CHARGEID for the SHIPMENT
LPN Freight Cost Amount The LPN freight cost amount is updated from the attribute
CHARGE.OPERAMT (EXTENDED) (T) for the SHIPUNIT
LPN Freight Cost Name The LPN freight cost name is updated from the attribute
CHARGE.CHARGEID for the SHIPUNIT

Fig 4: Shipment Data Update Table

Fig 5 below depicts the update of the Tracking Number field for the LPN/ Container.

Manifestptnrint.doc Oracle Confidential - For internal use only 11

 Fig 5: LPN/Container Tracking Number

Error Message Processing

Oracle E-Business Suite provides users with the ability to identify and process errors. The status
of the outbound shipment request can be viewed in Shipping Execution. Corrective action can be
taken in Shipping Execution to make message corrections for failed inbound message transactions.
The Workflow Transactions Monitor allows users to view the delivery status for both the
ShowShipment Request and ShowShipment Advice messages. Finally, the Workflow Status
Monitor allows users to view any issues processing the Supplier Instance Workflow.

View Message History Form

Oracle Shipping Execution provides the ability to view the message history. Selecting the action
‘View Message History’ within the Shipping Transactions Form allows users to view the status of
the Shipment Request message. In the example depicted below the Shipment Request status is
‘Sent’ for delivery 908237.

Navigation: Shipping > Transactions > Query Delivery >Select Action View Message History

Fig 6: Shipping Transactions Form -View Message History

Shipment Message Corrections Form

The Shipment Message Corrections form displays those shipment advice transactions that are in
the transaction status ‘Error’. Clicking on the ‘Error’ button depicted in Fig 7 will allow the error
message to be viewed. The form allows you to make corrections and re-submit the shipment
advice transaction for processing.

Manifestptnrint.doc Oracle Confidential - For internal use only 12

 For example, if the carrier is changed in the partner manifest application to a non-manifest enabled
carrier, the shipment advice transaction will fail. The following error message will be displayed
“Error in API Process_Interfaced_Deliveries, Action=UPDATE , Carrier specified in the
Shipment Advice document sent by the Manifesting System is not manifest enabled”. At this point
the user can correct the message and click on the ‘Process’ button under the Message History tab.
The shipment advice message would be reprocessed with the corrected data.

Navigation: Shipping > Interfaces > Interface Message Corrections

Fig 7: Shipment Message Corrections Form

Workflow Transaction Monitor

Errors related to processing XML transactions can be identified by logging into responsibility
Workflow Administrator Web Applications. The Workflow Transaction Monitor indicates the
delivery status of the message. Both the ShowShipment Request and ShowShipment Advice
message status can be viewed in the Workflow Transaction Monitor. The XML message can be
viewed in its entirety by clicking on the Document ID link.

Navigation: Workflow Administrator Web Applications > Transaction Monitor > Select Inbound
or Outbound Messages

Manifestptnrint.doc Oracle Confidential - For internal use only 13

 Fig 8: Transaction Monitor – Outbound ShowShipment Request

Fig 9 depicts the Workflow Transaction Monitor for the Inbound ShowShipment Advice
transaction. Two transactions are displayed, one in status ‘Warning’ and one in status ‘Success’.

Fig 9: Transaction Monitor – Inbound ShowShipment Advice

Workflow Status Monitor

The Workflow Status Monitor is designed to provide information on the status of the workflow.
The Workflow Type for manifest integration is the Supplier Instance Workflow. The Workflow
Status Monitor will indicate the failed activity. In the Supplier Instance Workflow depicted in Fig
10 the failed activity is ‘Process Inbound Delivery’. In addition to the Workflow Diagram users
can also view detailed information on each activity within the workflow.

Navigation: Workflow Administrator Web Applications > Administrator Workflow > Status
Monitor> Workflow Type: Supplier Instance Workflow

Manifestptnrint.doc Oracle Confidential - For internal use only 14

 Fig 10: Workflow Status Monitor

Manifestptnrint.doc Oracle Confidential - For internal use only 15

Partner Requirements
The following are the main requirements for the partner manifest application to integrate with
Oracle E-Business Suite.

• Ability to process inbound ShowShipment Request XML in Oracle’s published DTD

• Ability to produce a valid ShowShipment Response XML in Oracle’s published DTD

• Manifest partner provided user interface for processing parcel shipments

The functionality listed below will be provided by the manifest partner application:

• The manifest partner will provide the user interface for processing parcel shipments. The user
interface should include the necessary fields in order to process the shipment. Additionally,
the user interface should allow selection of additional services provided by the carrier. These
services can include Hold for Pickup, Residential Service, Oversize, Declared Value, COD,
etc.

• The manifest partner application should provide the ability to change the carrier and carrier
service level at time of shipment. This allows users to change the original carrier and carrier
service level sent in the ShowShipment Request message. This provides flexibility to make
last minute changes. The changed carrier and service level will be sent to Oracle E-Business
Suite in the ShowShipment Advice message.

• Carrier rate tables and rate calculation logic will reside in the manifest partner application.
The manifest partner application will calculate and apply carrier freight rates based on the
shipment attributes sent from Oracle E-Business Suite. Rate accuracy and calculation logic
should be in accordance with the carrier’s rating procedures.

• Document generation will be provided by the manifest partner application. The manifest
partner application is responsible for producing carrier compliant shipping labels and end-of-
day manifest.

• The manifest partner application will provide scale integration allowing users to capture
shipment/container weight at time of shipping. The scale weight would be used in the event
the ShowShipment message did not have the shipment weight specified or the user has
overridden the weight at time of shipping. The scale weight should be sent to Oracle E-
Business Suite in the ShowShipment Advice message.

• The carrier tracking number assignment will be provided by the manifest partner application.
The carrier tracking number generation should meet carrier requirements. The manifest
partner applications should be able to provide carrier supported tracking at both container and
shipment level.

• The manifest partner application will print and transmit the end-of-day manifest. The manifest
should be electronically transmitted in accordance with the carrier Manifest Setup

Manifestptnrint.doc Oracle Confidential - For internal use only 16

Manifest Setup
Oracle’s Manifest Integration requires setup in Oracle Shipping Execution, Oracle Inventory,
Oracle XML Gateway, and Oracle Workflow. The following forms depict the needed setup to
enable manifest integration between Oracle E-Business Suite and the manifest partner
application.

Shipping Execution Setup

Enable manifesting for the carrier: Order Management Super User/Shipping/Setup/Freight
Carriers, Cost Types/Freight Carriers, find the carrier, and at the Rating, Payment tab check
the “Enable Manifesting” checkbox.

Fig 11: Carrier Setup Form

Oracle’s Manifest Integration provides ability to enable automated carrier manifesting. To set up
the Automated Carrier Manifesting interface navigate: Order Management Super
User/Shipping/Interfaces/Run. Select ‘Single Request’ and click ‘OK’. Enter ‘Automated Carrier
Manifesting’ in the ‘Name’ field, and fill in the fields as appropriate in the ‘Parameters’ dialog
box. The button ‘Schedule’ allows you to automatically run the request at scheduled intervals.

Manifestptnrint.doc Oracle Confidential - For internal use only 17

 Fig 12: Automated Carrier Manifesting Interface

Manifestptnrint.doc Oracle Confidential - For internal use only 18

Inventory Setup
Enable manifesting for the ship from org: Order Management Super
User/Shipping/Setup/Organization Parameters, find the shipping org, click on tab “ATP, Pick,
Item-Sourcing”, and check “Carrier Manifesting Organization” checkbox.

Fig 13: Organization Parameter Setup Form

Manifestptnrint.doc Oracle Confidential - For internal use only 19

Oracle XML Gateway Setup
Oracle XML Gateway is a set of services that enables integration with Oracle Applications to
support XML messaging. Open Applications Group (OAG) Data Type Definitions (DTDs) are
used to map the XML messages. These DTDs are modified to meet Oracle-specific requirements
and are seeded within the Oracle XML Gateway. You select the DTDs (or Maps in the Trading
Partner Setup window) and assign them to each transaction during the trading partner setup.

Oracle XML Gateway processes events raised by the Oracle Applications and subscribes to
inbound events for processing. Oracle XML Gateway uses Oracle Advanced Queuing to integrate
with the Oracle Transport Agent to deliver messages to and receive messages from other
applications.

Any application that receives XML messages from Oracle Order Management/Shipping Execution
or sends XML messages to Oracle Order Management/Shipping Execution must be defined as a
trading partner within Oracle XML Gateway.

You select XML transactions and enable them for each trading partner during the trading partner
setup.

Code conversions are also seeded and defined in Oracle XML Gateway. Code conversions enable
you to effectively communicate with trading partners by converting your codes (such as TON) into
your trading partners’ codes (such as TONS) bycross-referencing the codes.

Trading Partner Definition

You must define trading partners in Oracle XML Gateway before their XML transactions can be
processed.

Trading partner data is used to:

• Link a particular address location in Oracle E-Business Suite to the trading partner
definition in Oracle XML Gateway

• Provide a means of telling the execution engine which trading partner message map to use

Note: A message map represents the relationship between the DTD and the XML message

• Enable specific transactions for trading partners

• Determine how to deliver the message

To define your trading partner: Switch Responsibility to XML Gateway: Setup/Define Trading
Partners.

At the Trading Partner Setup window select the following:

- Trading Partner Type: Internal

- Trading Partner Name: (name of org, e.g. V1)

- Trading Partner Site: (defaults based on above entry)

- Company Admin Email: (contact person’s email address)

- In Trading Partner Details area, enter:

Manifestptnrint.doc Oracle Confidential - For internal use only 20

 - Transaction Type: FTE/SSNI

- Map: WSH_SSNI_OAG721_IN

- Source Trading Partner Location Code: (create a name)

Enter the following values on a second line:

- Transaction Type: FTE/SSNO

- Map: WSH_SSNO_OAG721_OUT

- Connection/Hub: DIRECT

Note: DIRECT enables you to communicate with a carrier manifesting application directly. A hub
is an integration point within your network (either your intranet of the Internet). If you choose to
connect to a carrier manifesting application using Direct, the XML Gateway will require that you
provide information in the following fields:

- Protocol Type: HTTP-OXTA

- Username: (enter username provided by manifest partner)

- Password: (enter password provided by manifest partner. Note: the manifest partner may
not require a username/password. In this case, enter anything here)

- Protocol Address: (URL for your manifest partner’s processor)

- Source Trading Partner Location Code: (create a name)

Note: If you choose to connect to a carrier manifesting application using a hub, Oracle XML
Gateway will require that you select only a Username from the list of values. The rest of the
information will default based on the information entered the creation of the hub. If you are using
a predefined hub, the Source Trading Partner Location Code is automatically populated. The
Connection/Hub field is only required when the direction of the XML is OUT.

See: Oracle XML Gateway User’s Guide for detailed information on defining a hub.

Manifestptnrint.doc Oracle Confidential - For internal use only 21

 Fig 14: Trading Partner Setup Form

Trading Partner Code Conversions

Oracle XML Gateway code conversion function provides a method to cross–reference the codes
defined in Oracle E-Business Suite, for example Service Level, to codes used by trading partners,
the XML standard, or other standard codes in the transactions.

Define your code conversions: Switch Responsibility to XML Gateway: Setup/Define Trading
Partners

Setup Code Conversions for the trading partner: select the code conversion button. Code
conversions allow the Oracle server to exchange information with the manifesting partner’s server
such that the codes have a one-to-one relationship. For example, the service level code for Next
Day Air within the Oracle application is 1DA and the corresponding code for this service level at
the manifest partner is NDA. Code conversions allow the servers to decipher this translation, and
hence, the need for conversion codes.

Oracle E-Business Suite provides seeded code conversion categories. The following Categories
should be considered for code conversions:

- Carrier Service Levels: SERVICE_LEVEL

- Freight Terms: FREIGHT_TERMS
- Freight Cost Type: CHARGE_TYPE
- Currency: CURRENCY_CODE
- Container Type: CONTAINER_TYPE

Manifestptnrint.doc Oracle Confidential - For internal use only 22

 Note: When your data element’s code name is identical to that of the manifest partner, then it is
NOT necessary to create a code conversion. For example, if you have set up the service level code
for DHL USA 2nd Day as 2ND and the manifest partner’s code for DHL USA 2nd Day is 2ND,
then there is no need to set up a conversion code for this particular service level.
The capitalized text for the three elements above represents the corresponding Category Code
name. In the Trading Partner Code Conversion form, you must find the desired Category Code
prior to entering the conversion codes.

Contact the manifest partner and discuss which codes are needed to conduct manifesting. Consider
initiating this exchange of information with the manifest partner by providing them with a list of
the data elements codes that you have set up in Oracle E-Business Suite.

Refer to Oracle XML Gateway User’s Guide for more information on defining code conversions
and code conversion categories.

Fig 15: Trading Partner Code Conversion Form

Oracle Workflow Agent Listener Setup

Oracle Workflow Agent Listeners must be started before the XML transactions can execute. This
will ensure that XML messages are processed through the XML Gateway on a timely basis.

To enable the workflow listeners:

Manifestptnrint.doc Oracle Confidential - For internal use only 23

 Switch Responsibility to System Administrator. Then navigate: Requests/Run. In the Run This
Request field, select Workflow Agent Listener. The request must be run for the following three
agent names. Schedule the run request for every minute.

• ECX_INBOUND: Holds all messages that enter the process through the transport agent, or
are placed directly on the queue by an API.

• ECX_TRANSACTION: Agent for inbound messages originating from within the

enterprise.

• WF_DEFERRED: Agent for outbound messages sent in deferred mode.

Fig 16: Workflow Agent Listener Request

Manifestptnrint.doc Oracle Confidential - For internal use only 24

Manifest Integration Test Suggestions
The purpose of this section is to exercise the steps required to test the transaction of data
between Oracle E-Business Suite and the manifest partner application.

Test Objectives
The objective of the test is to successfully transact data between Oracle E-Business Suite and the
manifest partner application. The test will use XML messaging to send and receive shipment data.

The test should validate that the following functionality is working successfully:
• Send XML ShowShipment Request outbound message to manifest partner application
• Receive XML ShowShipment Advice message from manifest partner application
• Validate that the XML ShowShipment Advice message successfully updates Shipping
Execution

Setup
In order to test the manifest integration the following setup needs to be completed. See also
Manifest Setup Section

Oracle Order Management & Oracle Shipping Execution Setup

• Inventory Organization
• Customers / Carriers / Containers / Items
• Sales Orders / Deliveries
Oracle XML Gateway Setup
• Trading Partners
• Code Conversions
Oracle Workflow Agent Listener Setup

Test Flow
The following are the steps for the carrier manifesting test flow:
Sending outbound XML ShowShipment Request message
• Create Sales Order and Book it
• Pick Release order and AutoCreate Delivery
• Ensure manifest enabled carrier is assigned to the delivery
• Select Action ‘Send Outbound Message’ in Shipping Transactions Form

Manifestptnrint.doc Oracle Confidential - For internal use only 25

 • Select option ‘Send Shipment Request’
• Select Action ‘View Message History’ to view message status
• Message will be in ‘Sent’ status when successfully processed

The following are required changes that need to be made by the manifest partner to the
XML ShowShipment Request document:
• Remove all occurrences of <SHIPITEM>……..</SHIPITEM>
• Change “SR” to “SA” in <DOCTYPE>SR</DOCTYPE>
• Change DocumentID to a new value in <DOCUMENTID>351-I</DOCUMENTID>
• Enter a value to “ORACLE.ORIG_DOCID” using the old value in < DOCUMENTID>
For example,
“<ORACLE.ORIG_DOCID>351</ORACLE.ORIG_DOCID>”

The following are suggested changes that can be made by the manifest partner to the XML
ShowShipment Advice document:
• Populate attributes for the ShowShipment Advice message to update: Typical attributes
updated by the partner manifest would include “trackingid”. The “trackingid” is updated at
the element SHIPUNIT (i.e. carrier tracking number for the container)
<TRACKINGID>1Z1536100362391710</TRACKINGID>
• Another suggested attribute for update are the freight charges. Charges can be updated for
the element SHIPMENT or SHIPUNIT. (i.e. carrier transport charge for the container).
Charges are entered into the element <CHARGE>…….</CHARGE>. Within this element
you can enter a charge for a specific charge type.

Validate Test Flow

The final step of the test flow is to ensure that the delivery has been successful updated and
the ship confirmed.
• Validate that the delivery has been updated with the data contained in the ShowShipment
Advice message. Navigate to the Shipping Transaction form and query the delivery. Check
to ensure the attributes specified in the ShowShipment Advice message have been
successfully updated. Some of the typical delivery attributes that should be considered for
updates are carrier, service level, ship date, weight, tracking number, and freight charges.
Fig 5 illustrates the update of the Tracking Number field for the LPN/Container.
• To ensure the delivery has been ship confirmed the delivery should be in status ‘Closed’.
Also, the delivery line status should be ‘Interfaced’.

Troubleshooting
The following are troubleshooting steps that can be performed in the event the messages
have not been successfully sent and received:
• To check the status of the shipment request message navigate to the Shipping Transactions
Form in Oracle Shipping Execution. Select the action ‘View Message History’ for the

Manifestptnrint.doc Oracle Confidential - For internal use only 26

 delivery. If the message has been successfully sent the Shipment Request status will be
‘Sent’ for the delivery.

Navigation: Shipping > Transaction > Select Action ‘View Message History’

• To identify errors related to processing XML transactions, switch responsibility to

Workflow Administrator Web Applications. The Workflow Transaction Monitor indicates
the delivery status of the message. Both the ShowShipment Request and ShowShipment
Advice message status can be viewed in the Workflow Transaction Monitor. The XML
message can be viewed in its entirety by clicking on the Document ID link.

Navigation: Workflow Administrator Web Applications > Transaction Monitor > Select
Inbound or Outbound Messages
• To check the status of the workflow, navigate to the Workflow Status Monitor. The
Workflow Type for manifest integration is the Supplier Instance Workflow. The Workflow
Status Monitor will indicate the failed activity.

Navigation: Workflow Administrator Web Applications > Administrator Workflow >

Status Monitor> Workflow Type: Supplier Instance Workflow
• To identify failed shipment advice transactions, navigate to the Shipment Message
Corrections form. This form will display those shipment advice transactions that are in the
transaction status ‘Error’. The form allows you to make corrections and re-submit the
shipment advice transaction for processing.

Navigation: Shipping > Interfaces > Interface Message Corrections

Manifestptnrint.doc Oracle Confidential - For internal use only 27

 Appendix A – Shipment Request XML
The OAG’s SHOW SHIPMENT DTD is used as a basis for this transaction. The purpose of the
Shipment Request XML is to communicate all the manifest relevant delivery attributes to the
partner application.

The following table lists each of the ShowShipment elements/attributes, whether they are required
or optional, and whether they are used for inbound, outbound, or both.

The Required column indicates whether the element/attribute is required or optional for
INBOUND (I), OUTBOUND (O), or BOTH (B).

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

Required (B) CNTROL AREA The fields included in this area provide
information about the XML document

Required (B) BSR Shows the Business Service Request name per
OAGI
Required (B) VERB Value is SHOW
Required (B) NOUN Value is SHIPMENT
Required (B) REVISION Value is 006
Required (B) SENDER Provides information on the system that
sends the document
Required (B) LOGICALID Sender system identifier
Required (B) COMPONENT Sender application name. Value is FTE
Required (B) TASK Event or Action
Required (B) REFERENCE ID Unique reference ID for this document
Required (B) CONFIRMATION Confirmation when document is received
Required (B) LANGUAGE Language in which the text fields are transmitted
Required (B) CODEPAGE Character set used in this XML document
Required (B) AUTHID System ID of sender. Value is APPS
Required (B) DATETIME (CREATION) (T) Creation date and time of the XML document
Required (B) DATAAREA.SHOW_SHIPMENT.SHIP Contains the general document information for
MENT goods being transported to a particular partner
destination
Required (B) SHIPMENT.DATETTIME Sys date time Contains date and time stamp of the latest
update to the XML document
Required (B) SHIPMENT.DOCUMENTID (Shipment) WSH_TRANSACTIONS_HISTORY.DOCUM Shipment document ID
ENT_ID
Required (B) SHIPMENT.SHIPPERID LOCATION_CODE from Ship From ID
HR_LOCATIONS_ALL_TL based on the
WSH_NEW_DELIVERIES.INITIAL_PICKUP
_LOCATION_ID
Required (B) SHIPMENT.SYNCID XML: “A” = Add, “D” = Delete “C” = Change
EDI: “N” for Add, “F” for Delete
EDI code conversions: “N” for Add, “R” for
Change, “F” for Cancel
Not Used SHIPMENT.AMOUNT Not Used Not Used
(DECLAREVAL)
Not Used SHIPMENT.AMOUNT (DOCUMENT) Not Used Not Used
(T)
Not Used SHIPMENT.AMOUNT (ESTFREIGHT) Not Used Not Used
Not Used SHIPMENT.AMOUNT (FREIGHT) (T) WSH_FREIGHT_COSTS.TOTAL_AMOUNT Total freight charge
Not Used SHIPMENT.AMOUNT (ITEM) (T) Not Used Not Used
Required (B) SHIPMENT.CARRIER PARTY_NAME FROM HZ_PARTIES based Carrier ID
on the column WSH_NEW_DELIVERIES.
CARRIER_ID
Optional (B) SHIPMENT.CARRIERSRVLVL WSH_NEW_DELIVERIES.SERVICE_LEVEL Carrier service level
Required (O) SHIPMENT.COUNTRYDST WSH_NEW_DELIVERIES. ULTIMATE_DRO Destination country
POFF_LOCATION_ID

Manifestptnrint.doc Oracle Confidential - For internal use only 28

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

Not Used SHIPMENT.COUNTRYORG Not Used Not Used

Required (O) SHIPMENT.DATETIME (CREATION) WSH_NEW_DELIVERIES.CREATION_DAT Creation date and time
E
Optional (I) SHIPMENT.DATETIME (DELIVACT) WSH_TRIP_STOPS.ACTUAL_ARRIVAL_DA Actual delivery date
TE
Optional (B) SHIPMENT.DATETIME WSH_NEW_DELIVERIES.ULTIMATE_DRO Delivery scheduled date and time
(DELIVSCHED) POFF_DATE
Not Used SHIPMENT.DATETIME Not Used Not Used
(EARLSTSHIP)
Not Used SHIPMENT.DATETIME (LOADING) Not Used Not Used
Optional (O) SHIPMENT.DATETIME (NEEDDELV) WSH_NEW_DELIVERIES.ULTIMATE_DRO Date and time the delivery is needed
POFF_DATE
Not Used SHIPMENT.DATETIME (PROMDELV) Not Used Not Used
Not Used SHIPMENT.DATETIME (PROMSHIP) Not Used Not Used
Optional (I) SHIPMENT.DATETIME (SHIP) WSH_TRIP_STOPS.ACTUAL_DEPARTURE_ Actual ship date and time
DATE
Optional (O) SHIPMENT.DATETIME (SHIPSCHED) WSH_NEW_DELIVERIES.INITIAL_PICKUP Shipment scheduled date and time
_DATE
Optional (B) SHIPMENT.DESCRIPTN WSH_NEW_DELIVERIES.DESCRIPTION Shipment description
Not Used SHIPMENT.DISTCENTER Not Used Not Used
Not Used SHIPMENT.DOCKID Not Used Not Used
Required (B) SHIPMENT.DOCTYPE ‘SR’ ( SHIPMENT REQUEST FOR The OAG document name SR (SHIPMENT
OUTBOUND) AND ‘SA’ (SHIMENT ADV REQUEST) outbound transactions and SA
ICE FOR INBOUND) at the Supplier Instance. (SHIPMENT ADVICE) for inbound transactions
Optional (B) SHIPMENT.DOCUMENTRV Revision number of this document
‘001’ for ‘Add’ and
‘002’ for ‘Delete’
Not Used SHIPMENT.DROPSHIP Not Used Not Used
Not Used SHIPMENT.EXPORTLIC Not Used Not Used
Not Used SHIPMENT.FRGHTCLS Not Used Not Used
Optional (B) SHIPMENT.FRGHTTERMS WSH_NEW_DELIVERIES.FREIGHT_TERMS Describes how the freight cost for a shipment of
_CODE goods should be billed
Not Used SHIPMENT.HAZRDMATL Not Used Not Used
Not Used SHIPMENT.HDRSTATUS Not Used Not Used
Not Used SHIPMENT.IMPORTLIC Not Used Not Used
Not Used SHIPMENT.LOADPOINT Not Used Not Used
Not Used SHIPMENT.NOTES1 – NOTES9 Not Used Not Used
Not Used SHIPMENT.PARTIALSHP Not Used Not Used
Not Used SHIPMENT.PRIORITY Not Used Not Used
Optional (B) SHIPMENT.QUANTITY WSH_NEW_DELIVERIES.GROSS_WEIGHT The estimated weight of an item or container
(ESTWEIGHT) WSH_NEW_DELIVERIES.WEIGHT_UOM_C
ODE
Optional (B) SHIPMENT.QUANTITY Calculate using The net weight at the loading time of the
(LOADINGWT) WSH_NEW_DELIVERIES.GROSS WEIGHT container in which the materials are being
– WSH_NEW_DELIVERIES.NET WEIGHT shipped
Optional (B) SHIPMENT.QUANTITY WSH_NEW_DELIVERIES.NET_WEIGHT The net weight of the goods or materials being
(NETWEIGHT) WSH_NEW_DELIVERIES.WEIGHT_UOM_C shipped
ODE
Optional (B) SHIPMENT.QUANTITY (SHIPUNIT) WSH_NEW_DELIVERIES.NUMBER_OF_LP This segment contains the quantity of units
N shipped. This represents the container(s), not the
product shipped. An example of this is “4 truck
loads” or “2 wooden crates”.
Optional (B) SHIPMENT.QUANTITY WSH_NEW_DELIVERIES.GROSS_WEIGHT This segment quantities the total weight of
(TOTWEIGHT) WSH_NEW_DELIVERIES.WEIGHT_UOM an item, or shipment
Optional (B) SHIPMENT.QUANTITY (VOLUME) WSH_NEW_DELIVERIES.VOLUME This segment quantifies the volume, or amount
WSH_NEW_DELIVERIES.VOLUME_UOM of space, that is occupied by an item, container
or
shipment
Not Used SHIPMENT.ROUTEID Not Used Not Used
Not Used SHIPMENT.RELEASENUM Not Used Not Used
Not Used SHIPMENT.RELEASENUMTOT Not Used Not Used
Not Used SHIPMENT.ROUTETYPE Not Used Not Used
Optional (B) SHIPMENT.SHIPNOTES WSH_NEW_DELIVERIES.SHIPPING_MARK This is a free form area that contains special
S instructions
Optional (B) SHIPMENT.SHIPPOINT LOCATION FROM Indicates the ship to location

Manifestptnrint.doc Oracle Confidential - For internal use only 29

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

HZ_CUST_SITE_USES_ALL based on the

Not Used SHIPMENT.SHIPPRIOR
Optional (B) SHIPMENT.SHIPSRVLVL
Not Used SHIPMENT.SPECIALHND
Not Used SHIPMENT.STAGEPOINT
Not Used SHIPMENT.TEMPRATURE (ACTUAL)
Not Used SHIPMENT.TEMPRATURE
(DELIVERY)
Not Used SHIPMENT.TEMPRATURE
(LOADING)
Optional (B) SHIPMENT.TRANSMETHD
Optional (B) SHIPMENT.TRANSTERMS
Optional (B) SHIPMENT.WAREHOUSE
Required (B) SHIPMENT.USERAREA
ORACLE.DELIVERY_NAME
ORACLE.LOADING_SEQUENCE
ORACLE.VEHICLE_NUM_PREFIX
ORACLE.VEHICLE_NUMBER
ORACLE.ROUTE_ID
ORACLE.ROUTING_INSTRUCTIONS
ORACLE.DEPARTURE_SEAL_CODE
ORACLE.ORIG_DOCID
ORACLE.CUSTOMER_NAME
ORACLE.CUSTOMER_NUMBER
ORACLE.WAYBILL
ORACLE.INTMED_SHIP_TO_LOCATI
ON
ORACLE.MANUAL_WV
ORACLE.SHIPMENT_DIRECTION
ORACLE.OPERATOR
ORACLE.DESCRIPTIVE_FLEXFIELS
Required (O) PARTNER.
Required (O) PARTNER.NAME
WSH_NEW_DELIVERIES.ULTIATE_DROPO
FF_LOCATION_ID converted to code
Not Used
WSH_NEW_DELIVERIES.SHIP_SERVICE_L
EVEL
Not Used
Not Used
Not Used
Not Used
Not Used
WSH_NEW_DELIVERIES.MODE_OF_TRAN
SPORT
WSH_NEW_DELIVERIES.FOB_CODE
WSH_NEW_DELIVERIES.ORGANIZATION_
ID converted to code
WSH_NEW_DELIVERIES.DELIVERY_
NAME (required)
WSH_NEW_DELIVERIES.LOADING_
SEQUENCE
WSH_TRIPS.VEHICLE_NUM_PREFIX
WSH_TRIPS.VEHICLE_NUMBER
WSH_TRIPS.ROUTE_ID
WSH_TRIPS.ROUTING_INSTRUCTIONS
WSH_TRIP_STOPS.DEPARTURE_SEAL_
CODE
WSH_TRANSACTIONS_HISTORY.OR
IG_DOCUMENT_NUMBER storing
the parent message’s DOCUMENTID (Required
for Inbound)
HZ_PARTIES.PARTY_NAME based on the
WSH_NEW_DELIVERIES.CUSTOMER_ID
HZ_CUST_ACCOUNTS.ACCOUNT_NUMBE
R based on the WSH_NEW_DELIVERIES.
customer_id
WSH_NEW_DELIVERIES.WAYBILL
LOCATION FROM
HZ_CUST_SITE_USES_ALL based on
the WSH_NEW_DELIVERIES.INTMED_SH
IP_TO_LOCATION_ID
WSH_NEW_DELIVERIES.WV_FROZEN_
FLAGWSH_NEW_DELIVERIES.SHIPMENT_
DIRECTIONWSH_TRIPS.OPERATOR
WSH_NEW_DELIVERY descriptive flexfields
If this partner segment is the Ship To segment,
get the HZ_PARTIES.NAME for the
WSH_NEW_DELIVERIES.ULTIMATE_DRO
POFF_LOCATION_ID
Not Used
Shipment Service Level
Not Used
Not Used
Not Used
Not Used
Not Used
Identifies the general type of carrier
transportation used to deliver goods
Ownership transfer terms
The storage facility for inventory
The element ORACLE.DELIVERY_NAME
is required for both Outbound and Inbound
The USERAREA is defined by embedding
elements and attributes for each new Field
Identifier or Segment needed within the
USERAREA. When a new Field Identifier
or a new Segment is determined to be necessary,
and it is not included in the OAGIS
specification, new tags can be developed by
the project team for the specific integration
project. These new tags can then be used
to describe the fields and segments within
the USERAREA. The USERAREA may
contain multiple fields or segments coded in
this way. These are all embedded within the
one special field called USERAREA.
This area is for the partner information
Corporate name of a business entity in the
shipment address

If this partner segment is the Ship from segment,

get the HZ_PARTIES.NAME for the
WSH_NEW_DELIVERIES.ORGANIZAT
ION_ID

If this partner segment is the Customer segment,

get the HZ_PARTIES.NAME for the
WSH_NEW_DELIVERIES.CUSTOMER_
ID

If this partner segment is the Supplier segment,

get the HZ_PARTIES.NAME for the
WSH_NEW_DELIVERIES.ORGANIZAT
ION_ID

Manifestptnrint.doc Oracle Confidential - For internal use only 30

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

Not Used PARTNER.ONETIME Not Used Not Used

Required (O) PARTNER.PARTNRID LOCATIONFROM The partner ID
HZ_CUST_SITE_USES_ALL based on
WSH_NEW_DELIVERIES.ULTIMATE_DRO
POFF_LOCATION_ID converted to external
value, or LOCATION_CODE FROM HR_
LOCATIONS_ALL_TL based on WSH_
NEW_DELIVERIES.INITIAL_PICKUP_
LOCATION_ID AND ORGANIZATION_ID
converted to external value.
Required (O) PARTNER.PARTNRTYPE WSH_LOOKUPS.MEANING based on Indicates the type of partner entity
lookup type = ’WSH_PARTNER_TYPE’
(Values are ‘Ship From’ or ‘Ship To’)
Not Used PARTNER.ACTIVE Not Used Not Used
Optional (O) PARTNER.CURRENCY Optional Outbound Optional Outbound
Not Used PARTNER.DESCRIPTN Not Used Not Used
Not Used PARTNER.DUNSNUMBER Not Used Not Used
Not Used PARTNER.GLENTITYS Not Used Not Used
Not Used PARTNER.NAME2-NAME9 Not Used Not Used
Not Used PARTNER.PARENTID Not Used Not Used
Not Used PARTNER.PARTNIDX Not Used Not Used
Not Used PARTNER.PARTNRRATG Not Used Not Used
Not Used PARTNER.PARTNRROLE Not Used Not Used
Not Used PARTNER.PAYMETHOD Not Used Not Used
Not Used PARTNER.TAXEXEMPT Not Used Not Used
Not Used PARTNER.TAXID Not Used Not Used
Not Used PARTNER.TERMID Not Used Not Used
Optional (O) PARTNER.USERAREA WSH_NEW_DELIVERIES.INTMED_SHIP_T
O_LOCATION_ID
WSH_
NEW_DELIVERIES.POOLED_SHIP_TO_LO
CATION_ID
HZ_CUST_SITE_USES_ALL.SITE_USE_ID
HZ_CUST_SITE_USES_ALL.LOCATION

Required (O) PARTNER – ADDRESS. This area is for the partner address information
Required (O) PARTNER – ADDRESS.ADDRLINE1- Extracted from the WSH_LOCATIONS using Partner address
ADDRLINE9 the location id that matches the Ship From, Ship
TO, Customer and Supplier from the
WSH_NEW_DELIVERIES table.
Not Used PARTNER – ADDRESS.ADDRTYPE Not Used Not Used
Required (O) PARTNER – ADDRESS.CITY Extracted from the WSH_LOCATIONS using Partner city
the location id that matches the Ship From, Ship
TO, Customer and Supplier from the
WSH_NEW_DELIVERIES table.
Required (O) PARTNER – ADDRESS.COUNTRY Extracted from the WSH_LOCATIONS using Partner country
the location id that matches the Ship From, Ship
TO, Customer and Supplier from the
WSH_NEW_DELIVERIES table.
Optional (O) PARTNER – ADDRESS.COUNTY Extracted from the WSH_LOCATIONS using Partner county
the location id that matches the Ship From, Ship
TO, Customer and Supplier from the
WSH_NEW_DELIVERIES table.
Not Used PARTNER – ADDRESS.DESCRIPTN Not Used Not Used
Optional (O) PARTNER – ADDRESS.FAX1-FAX9 HZ_CONTACT_POINTS.RAW_PHONE_ Partner fax numbers
NUMBER for the PARTY_ID, and
CONTACT_POINT_TYPE = “FAX”
for “Ship To” and HR_LOCATIONS_
ALL.TELEPHONE_NUMBER_2 for “Ship
From”

Required (O) PARTNER – ADDRESS.POSTALCODE Extracted from the WSH_LOCATIONS Partner postal code
using the locationid that matches the Ship From,
Ship TO, Customer and Supplier from the
WSH_NEW_DELIVERIES table.
Optional (O) PARTNER – ADDRESS.REGION Extracted from the WSH_LOCATIONS Partner region

Manifestptnrint.doc Oracle Confidential - For internal use only 31

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

using the location id that matches the

Ship From, Ship TO, Customer and Supplier
from the WSH_NEW_DELIVERIES table.

Required (O) PARTNER – ADDRESS.STATEPROVN Extracted from the WSH_LOCATIONS using Partner state or province
the location id that matches the Ship From, Ship
TO, Customer and Supplier from the
WSH_NEW_DELIVERIES table.
Not Used PARTNER – ADDRESS.TAXJRSDCTN Not Used Not Used
Optional (O) PARTNER – ADDRESS.TELEPHONE1- HZ_CONTACT_POINTS.RAW_PHONE_ Partner telephone numbers
TELEPHONE9 NUMBER for the PARTY_ID, and
CONTACT_POINT_TYPE = “GEN” for “Ship
To” and
HZ_LOCATIONS_ALL.TELEPHONE_NUMB
ER_1 for “Ship From”.

Optional (O) PARTNER – ADDRESS.URL HZ_CONTACT_POINTS.URL for the Partner web site URL
PARTY_ID and CONTACT_POINT_TYPE =
“GEN” for “Ship To”
Not Used PARTNER – ADDRESS.USERAREA Not Used Not Used
Optional (O) PARTNER – CONTACT. Partner contact information
Optional (O) PARTNER – CONTACT.NAME1 HZ_PARTIES.PERSON_FIRST_NAME + Partner contact name
PERSON_MIDDLE_NAME+PERSON_LAST_
NAME based on customer and ship to location
on WSH_NEW_DELIVERIES and based on
SHIP_TO_CONTACT_ID on
WSH_DELIVERY_DETAILS.
Not Used PARTNER – Not Used Not Used
CONTACT.CONTCTTYPE
Not Used PARTNER – CONTACT.DESCRIPTN Not Used Not Used
Not Used PARTNER – CONTACT.EMAIL Not Used Not Used
Not Used PARTNER – CONTACT.FAX1 - FAX9 Not Used Not Used
Not Used PARTNER – CONTACT.NAME2 - Not Used Not Used
NAME9
Optional (O) PARTNER – CONTACT.TELEPHONE1 HZ_CONTACT_POINTS.RAW_PHONE_ Partner contact phone numbers
-TELEPHONE9 NUMBER based on customer and ship to
location on WSH_NEW_DELIVERIES and
based on SHIP_TO_CONTACT_ID
on WSH_DELIVERY_DETAILS.
Not Used PARTNER – CONTACT.USERAREA Not Used Not Used

Required (O) DOCUMNTREF. This area contains the details of the document
type
Required (O) DOCUMNTREF.DOCTYPE ‘SR’ (SHIPMENT REQUEST FOR The document type.
OUTBOUND) AND ‘SA’ (SHIMENT ADV SHIPMENT REQUEST
ICE FOR INBOUND) at the Supplier Instance.

Required (O) DOCUMNTREF.DOCUMENTID WSH_TRANSACTIONS_HISTORY.ORIG_D The document ID

OCUMENT_NUMBER
Required (O) DOCUMNTREF.PARTNRID ORGANIZATION_CODE based on WSH_ The partner ID
NEW_DELIVERIES.ORGANIZATION_ID
Not Used DOCUMNTREF.PARTNRTYPE Not Used Not Used
Not Used DOCUMNTREF.DESCRIPTN Not Used Not Used
Not Used DOCUMNTREF.DOCUMENTRV Not Used Not Used
Not Used DOCUMNTREF.LINENUM Not Used Not Used
Not Used DOCUMNTREF.NOTES1 – NOTES9 Not Used Not Used
Not Used DOCUMNTREF.SCHLINENUM Not Used Not Used
Not Used DOCUMNTREF.SUBLINENUM Not Used Not Used
Not Used DOCUMNTREF.USERAREA Not Used Not Used

Required (O) SHIPITEM. Represents the request to ship specific quantity

of goods. The SHIPITEM element is required
for the outbound message, however this element
is not required for the inbound message.
Required (O) SHIPITEM.ITEM (REQUIRED) WSH_DELIVERY_DETAILS.INVENTORY_I
TEM_ID (foreign key to

Manifestptnrint.doc Oracle Confidential - For internal use only 32

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

MTL_SYSTEM_ITEMS)

Derive Item_Number from

MTL_SYSTEM_ITEMS
Required (O) SHIPITEM.QUANTITY (ITEM) WSH_DELIVERY_DETAILS.REQUESTED_
QUANTITY
Not Used SHIPITEM.AMOUNT (EXTENDED) Not Used Not Used
Not Used SHIPITEM.AMOUNT (ITEM) Not Used Not Used
Optional (O) SHIPITEM.COUNTRYORG WSH_DELIVERY_DETAILS.COUNTRY_OF Country of origin
_ORIGIN
Not Used SHIPITEM.DISPOSITN Not Used Not Used
Not Used SHIPITEM.EXPORTLIC Not Used Not Used
Optional (O) SHIPITEM.FRGHTCLS MTL_CATEGORY_SETS_VL.CATEGORY_S Qualifies goods for purposes of freight cost
ET_NAME based on WSH_DELIVERY_ calculation
DETAILS.FREIGHT_CLASS_CAT_ID
Not Used SHIPITEM.FRGHTITEM Not Used Not Used
Optional (O) SHIPITEM.HAZRDMATL PO_HAZARD_CLASSES_VL.HAZARD_CLA Contains a hazardous material code or
SS based on WSH_DELIVERY_DETAILS. description that can be a free form area or an
HAZARD_CLASS_ID agreed upon set of codes for the applications
Not Used SHIPITEM.IMPORTLIC Not Used
Optional (O) SHIPITEM.ITEMDESC WSH_DELIVERY_DETAILS.ITEM_DESCRI
PTION
Optional (O) SHIPITEM.ITEMRV WSH_DELIVERY_DETAILS.REVISION
Optional (O) SHIPITEM.ITEMX WSH_DELIVERY_DETAILS.CUSTOMER_IT
EM_ID
Converted to Item_number by joining to
mtl_customer_items
Optional (O) SHIPITEM.NOTES1 – NOTES9 WSH_DELIVERY_DETAILS.PACKING_INS Item Notes
TRUCTIONS
Optional (O) SHIPITEM.OWNRSHPCDE WSH_DELIVERY_DETAILS.FOB_CODE Used to identify who or which organization
owns the item or part. The content of this Field
ID is user defined based on a specific Customer
or Supplier
Not Used SHIPITEM.PACKING Not Used Not Used
Optional (O) SHIPITEM.PARTIALSHIP “0” – means partial shipment not allowed (i.e.
when ship_set_id is not null)
“1” – means partial shipment is allowed (i.e.
when ship_set_id is null)
Optional (O) SHIPITEM.QUANTITY WSH_DELIVERY_DETAILS.BACKORDERE Quantity of items backordered
(BACKORDERD) D_QUANTITY
Not Used SHIPITEM.QUANTITY (OPEN) Not Used Not Used
Required (O) SHIPITEM.QUANTITY (ORDERED) WSH_DELIVERY_DETAILS.SRC_REQUEST
ED_QUANTITY
Optional (O) SHIPITEM.QUANTITY (SHIPPED) WSH_DELIVERY_DETAILS.SHIPPED_QUA This represents the actual quantity shipped
NTITY
Optional (O) SHIPITEM.QUANTITY (VOLUME) WSH_DELIVERY_DETAILS.VOLUME The volume, or amount of space, that is
occupied by an item, container or shipment
Optional (O) SHIPITEM.QUANTITY (WEIGHT) WSH_DELIVERY_DETAILS.NET_WEIGHT The weight of an item, container, or shipment
Not Used SHIPITEM.SHIPMATLID Not Used Not Used
Optional (O) SHIPITEM.SHIPNOTES WSH_DELIVERY_DETAILS.SHIPPING_INS Notes area used for any additional information
TRUCTIONS
Not Used SHIPITEM.SHIPPRIOR Not Used Not Used
Not Used SHIPITEM.SHIPMTLDESC Not Used Not Used
Not Used SHIPITEM.UPC Not Used Not Used
Required (O) SHIPITEM.USERAREA Use this to store: The element
WSH_DELIVERY_DETAILS.DELIVERY_ ORACLE.DELIVERY_DETAIL_NUMBER
ORACLE.DELIVERY_DETAIL_NUMB DETAIL_ID is required for Outbound only
ER WSH_DELIVERY_ASSIGNMENTS.PARENT
ORACLE.PARENT_DELIVERY_DETA _DELIVERY_DETAIL_ID
IL_NUMBER WSH_DELIVERY_DETAILS.SHIP_TOLERA
ORACLE.SHIP_TOLERANCE_ABOVE NCE_ABOVE
ORACLE.SHIP_TOLERANCE_BELOW WSH_DELIVERY_DETAILS.SHIP_TOLERA
ORACLE.LOAD_SEQUENCE_NUMBE NCE_BELOW
R WSH_DELIVERY_DETAILS.LOAD_SEQUE
ORACLE.SHIP_SET_NUMBER NCE_NUMBER
ORACLE.SUBINVENTORY WSH_DELIVERY_DETAILS descriptive

Manifestptnrint.doc Oracle Confidential - For internal use only 33

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

ORACLE.TOP_MODEL_LINE_NUMB
ER
ORACLE.SHIP_MODEL_COMPLETE_
FLAG
ORACLE.COMMODITY_CODE_CATE
GORY
ORACLE.SHIPMENT_PRIORITY_CO
DE
ORACLE.DELIVER_TO_LOCATION
ORACLE.CUSTOMER_NAME
ORACLE.CUSTOMER_NUMBER
ORACLE.TXN_SRC_LINE_NUMBERQ
UANTITY(TOTWEIGHT)
ORACLE.MANUAL_WV
ORACLE.LINE_DIRECTION
ORACLE.REQUEST_DATE_TYPE_CO
DE
DATETIME (ORACLE.EARLSTPICK)
DATETIME (ORACLE.LATESTPICK)
DATETIME (ORACLE.EARLSTDROP)
DATETIME (ORACLE.LATESTDROP)
DATETIME (ORACLE.SCHEDULED)
DATETIME(ORACLE.REQUESTED)C
ONTACT Segment
flexfields
WSH_DELIVERY_DETAILS.SHIP_SET_
ID
WSH_DELIVERY_DETAILS.SUBINVENTO
RY
WSH_DELIVERY_DETAILS.TOP_MODEL_
LINE_ID
WSH_DELIVERY_DETAILS.SHIP_MODEL_
COMPLETE_FLAG
WSH_DELIVERY_DETAILS.COMMOD
ITY_CODE_CAT_ID converted to code
WSH_DELIVERY_DETAILS.SHIPMENT_PR
IORITY_CODE converted to “01”, “02”, or
“03” for XML
WSH_DELIVERY_DETAILS.DELIVER_
TO_LOCATION_ID CONTACT segment
sends CONTACT NAME and PHONE
NUMBER of the contact based on the
ship_to_contact_id on wsh_delivery_details.

Required (I) CHARGE. The CHARGE element is used for charges

associated with the SHIPMENT or SHIPUNIT.
The CHARGE element is required provided
there are charges associated with the
SHIPMENT or SHIPUNIT.
Required (I) CHARGE.CHARGEID WSH_FREIGHT_COST_TYPES.NAME based Charge ID
on
WSH_FREIGHT_COSTS.FREIGHT_COST_T
YPE_ID converted to external value
Required (I) CHARGE.OPERAMT (EXTENDED) (T) WSH_FREIGHT_COSTS.UNIT_AMOUNT Extended operating cost amount
WSH_FREIGHT_COSTS.CURRENCY_CODE
Not Used CHARGE.AMOUNT (EXTENDED) (T) Not Used Not Used
Optional (I) CHARGE.CHARGETYPE WSH_FREIGHT_COST_TYPES.NAME based Charge type
on
WSH_FREIGHT_COSTS.FREIGHT_COST_T
YPE_ID
Not Used CHARGE.CHGLINENUM Not Used Not Used
Not Used CHARGE.DESCRIPTN Not Used Not Used
Optional (I) CHARGE.USERAREA WSH_FREIGHT_COSTS descriptive flexfields User Area
Optional (O) INVDETAIL. Inventory item attribute detail associated with
the SHIPITEM
Optional (O) INVDETAIL.DESCRIPTN WSH_DELIVERY_DETAILS.ITEM_DESCRI
PTION
Not Used INVDETAIL.DISPOSITN Not Used Not Used
Not Used INVDETAIL.LOTLEVEL1 – WSH_DELIVERY_DETAILS.LOT_NUMBER
LOTLEVEL2
WSH_DELIVERY_DETAILS.SUBLOT_NUM
BER

Not Used INVDETAIL.NOTES1 - NOTES9 Not Used Not Used

Optional (O) INVDETAIL.QUANTITY (ITEM) WSH_DELIVERY_DETAILS.REQUESTED
QUANTITY/WSH_DELIVERY_DETAILS.RE
QUESTED_QUANTITY_UOM
Optional (O) INVDETAIL.SERIALNUM WSH_DELIVERY_DETAILS.SERIAL_NUMB
ERWSH_DELIVERY_DETAILS.REQUESTE
D
QUANTITY/WSH_DELIVERY_DETAILS.RE
QUESTED_QUANTITY_UOM
Optional (O) INVDETAIL.USERAREA WSH_DELIVERY_DETAILS.TO_SERIAL_N
UMBER
WSH_DELIVERY_DETAILS.PREFERRED_G
RADE

Manifestptnrint.doc Oracle Confidential - For internal use only 34

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

WSH_DELIVERY_DETAILS.SERIAL_NUMB
ER

Required (B) SHIPUNIT. Represents a single trackable shipping unit. A

shipping unit is a uniquely identifiable assembly
or container that holds one or more items to be
shipped
Required (B) SHIPUNIT.CARRIER WSH_DELIVERY_DETAILS.CARRIER_ID Carrier of the ship unit
converted to external value
Required (I) SHIPUNIT.SHIPPERID WSH_DELIVERY_DETAILS.SHIP_FROM_L The identifier of the partner who is responsible
OCATION_ID converted to external value. for packaging inventory goods for shipment
Optional (B) SHIPUNIT.TRACKINGID WSH_DELIVERY_DETAILS.TRACKING_N A unique identifier for the purpose of tracking
UMBER an individual package or shipment
Not Used SHIPUNIT.AMOUNT (DECLAREVAL) Not Used Not Used
Not Used SHIPUNIT.AMOUNT (FREIGHT) (T) Not Used Not Used
Not Used SHIPUNIT.AMOUNT (ITEM) (T) Not Used Not Used
Not Used SHIPUNIT.AMOUNT (TOTAL) (T) Not Used Not Used
Optional (B) SHIPUNIT.CARRSRVLVL WSH_NEW_DELIVERIES.SERVICE_LEVEL Service level for the ship unit
Optional (B) SHIPUNIT.CONTAINRID WSH_DELIVERY_DETAILS.DELIVERY_DE
TAIL_ID
Optional (B) SHIPUNIT.CONTNRSEAL WSH_DELIVERY_DETAILS.SEAL_CODE Seal number on the ship unit
SHIPUNIT.CONTRTYPE WSH_DELIVERY_DETAILS.CONTAINER_T
YPE_CODE
WSH_DELIVERY_DETAILS.SEAL_CODE
Not Used SHIPUNIT.COUNTRYDST Not Used Not Used
Optional (B) SHIPUNIT.COUNTRYORG WSH_DELIVERY_DETAILS.COUNTRY_OF Container country of origin
_ORIGIN
Optional (B) SHIPUNIT.DATETIME (DELIVACT) WSH_TRIP_STOPS.ACTUAL_ARRIVAL_DA Actual delivery date and time
TE
Optional (I) SHIPUNIT.DATETIME WSH_DELIVERY_DETAILS.DATE_SCHED Delivery scheduled date and time
(DELIVSCHED) ULED
Not Used SHIPUNIT.DATETIME (LOADING) Not Used Not Used
Not Used SHIPUNIT.DATETIME (SHIP) Not Used Not Used
Not Used SHIPUNIT.DESCRIPTN Not Used Not Used
Not Used SHIPUNIT.EXPORTLIC Not Used Not Used
Optional (B) SHIPUNIT.FRGHTCLS MTL_CATEGORY_SETS_VL.CATEGORY_S Freight class of the ship unit
ET_NAME based on
WSH_DELIVERY_DETAILS.FREIGHT_CLA
SS_CAT_ID converted to external value
Not Used SHIPUNIT.FRGHTITEM WSH_DELIVERY_DETAILS.FREIGHT_CLA
SS_CAT_ID converted to external value
Optional (B) SHIPUNIT.FRGTHTERMS WSH_DELIVERY_DETAILS.FREIGHT_TER Ship unit freight terms
MS_CODE converted to external value
Optional (B) SHIPUNIT.HAZRDMATL WSH_DELIVERY_DETAILS.HAZARD_CLA Contains a hazardous material code or
SS_ID converted to external description that can be a free form area or an
agreed upon set of codes for the applications
involved in an integration scenario

Not Used SHIPUNIT.IMPORTLIC Not Used Not Used

Not Used SHIPUNIT.LOADPOINT Not Used Not Used
Not Used SHIPUNIT.NOTES1 - NOTES9 Not Used Not Used
Not Used SHIPUNIT.OPERAMT (FREIGHT) (T) Not Used Not Used
Not Used SHIPUNIT.PACKING Not Used Not Used
Not Used SHIPUNIT.PACKINGDESC Not Used Not Used
Not Used SHIPUNIT.QUANTITY (ESTWEIGHT) Not Used Not Used
Optional (O) SHIPUNIT.QUANTITY (HEIGHT) Populate from MTL_SYSTEM_ITEMS Height of the ship unit
Optional (O) SHIPUNIT.QUANTITY (LENGTH) Populate from MTL_SYSTEM_ITEMS Length of the ship unit
Not Used SHIPUNIT.QUANITTY (LOADINGWT) Calculate Loading weight of the ship unit
WSH_DELIVERY_DETAILS.GROSS
WEIGHT - WSH_DELIVERY_DETAILS.NET
WEIGHT
Optional (B) SHIPUNIT.QUANTITY (NETWEIGHT) WSH_DELIVERY_DETAILS.NET_WEIGHT Net weight of the ship unit
+
WSH_DELIVERY_DETAILS.WEIGHT_UOM
_CODE for delivery lines = container item

Manifestptnrint.doc Oracle Confidential - For internal use only 35

Required Element/Attribute Oracle Shipping Tables – Source/Target Description

Required (B) SHIPUNIT.QUANTITY (TOTWEIGHT) WSH_DELIVERY_DETAILS.GROSS_WEIG Total weight of the ship unit
HT +
WSH_DELIVERY_DETAILS.WEIGHT_UOM
_CODE
Optional (B) SHIPUNIT.QUANTITY (VOLUME) WSH_DELIVERY_DETAILS.VOLUME + Volume of the ship unit
WSH_DELIVERY_DETAILS.VOLUME_UO
M_CODE for delivery lines = container item
Not Used SHIPUNIT.QUANTITY (WIDTH) Not Used Not Used
Optional (B) SHIPUNIT.SHIPMATLID WSH_DELIVERY_DETAILS.INVENTORY_I The delivery detail id of the container record
TEM_ID converted to Item Number by joining
to mtl_system_items
Optional (B) SHIPUNIT.SHIPNOTES WSH_DELIVERY_DETAILS.SHIPPING_INS Shipping instructions or notes
TRUCTIONS
Optional (B) SHIPUNIT.SHIPPOINT WSH_DELIVERY_DETAILS.DELIVER_TO_ Identifies the location the goods are to be
LOCATION_ID shipped
Optional (B) SHIPUNIT.SHIPSRVLVL WSH_DELIVERY_DETAILS.SHIP_METHOD A generic code that specifies a particular type or
_CODE quality of carrier delivery service to be used
for transporting goods
Optional (B) SHIPUNIT.SHPMTLDESC WSH_DELIVERY_DETALS.ITEM_DESCRIP Describes the material or container a
TION product or item is shipped in
Not Used SHIPUNIT.SHPUNITSEQ Not Used Not Used
Not Used SHIPUNIT.SHPUNITSTS Not Used Not Used
Not Used SHIPUNIT.SHPUNITTOT Not Used Not Used
Not Used SHIPUNIT.SPECIALHND Not Used Not Used
Not Used SHIPUNIT.STAGEPOINT Not Used Not Used
Not Used SHIPUNIT.TEMPRATURE (ACTUAL) Not Used Not Used
Not Used SHIPUNIT.TEMPRATURE Not Used Not Used
(DELIVERY)
Not Used SHIPUNIT.TEMPRATURE (LOADING) Not Used Not Used
Not Used SHIPUNIT.TRACKINGIDTYPE Not Used Not Used
Optional (B) SHIPUNIT.TRANSMETHD WSH_DELIVERY_DETAILS.MODE_OF_TR Transportation method
ANSPORT
Optional (B) SHIPUNIT.TRANSTERMS WSH_NEW_DELIVERIES.FOB_CODE A contractual code used to describe the point
where delivery occurs (goods ownership is
transferred) in a contract of sale
Required (B) SHIPUNIT.USERAREA WSH_DELIVERY_DETAILS.DELIVERY_ User area for the ship unit
DETAIL_ID (To be called as
DELIVERY_DETAIL_NUMBER)
WSH_DELIVERY_DETAILS.PACKING_INS
TRUCTIONS
WSH_DELIVERY_DETAILS.DESCRIPTIVE_
FLEXFIELDS
WSH_DELIVERY_DETAILS.LOT_NUMBER
WSH_DELIVERY_DETAILS.SUBLOT_NUM
BER
WSH_DELIVERY_DETAILS.REVISION
WSH_DELIVERY_DETAILS.SERIALNUMB
ER
WSH_DELIVERY_DETAILS.TO_SERIALNU
MBER

Manifestptnrint.doc Oracle Confidential - For internal use only 36

Appendix B – Shipment Advice XML
The OAG’s SHOW SHIPMENT DTD is used as a basis for this transaction. The purpose of the
ShowShipment Advice XML is to communicate relevant delivery attributes once the shipment has
been processed by the manifest partner application.

The manifest partner is required to make the following changes to the XML document.

- Remove all occurrences of <SHIPITEM>...... </SHIPITEM>

- Change "SR" to "SA" in <DOCTYPE>SR</DOCTYPE>

- Change DocumentId to some new value in <DOCUMENTID>351-I</DOCUMENTID>

- Give a value to "ORACLE.ORIG_DOCID" using the value in <DOCUMENTID> that

was present in the corresponding outbound XML message. For example,
<ORACLE.ORIG_DOCID/> should become
"<ORACLE.ORIG_DOCID>351</ORACLE.ORIG_DOCID>". The value 351 is taken
from the element/attribute <DOCUMENTID> contained in the outbound XML message.

- Charges can be entered for the SHIPMENT and SHIPUNIT. It is important to note the
<CHARGE> segment is not included in the ShowShipment Request message. This
segment needs to be inserted by the manifest partner. This segment is required provided
there are charges associated with the SHIPMENT or SHIPUNIT.

The table below depicts several of the primary elements/attributes that would be updated by the
carrier manifest partner. The Required/Optional column indicates whether the element/attribute is
required or optional for the inbound ShowShipment Advice message.

Note: For the complete list of elements/attributes please review the detailed table starting on
page 28. The table on page 28 lists each of the ShowShipment elements/attributes, whether
they are required or optional, and whether they are used for inbound, outbound, or both.

Required/ Element/Attribute Description

Optional
Required SHIPMENT.CARRIER Name of carrier transporting the shipment
Optional SHIPMENT.CARRSRVLVL Carrier service level
Required SHIIPMENT.DOCTYPE The OAG document name SR (SHIPMENT REQUEST) outbound transactions and
SA (SHIPMENT ADVICE) for inbound transactions
Optional SHIPMENT. FRGHTTERMS Indicates how the freight costs for a shipment of goods should be billed
Optional SHIPMENT.QUANTITY This segment quantifies the total weight of an item or shipment
(TOTWEIGHT)
Optional SHIPMENT.USERAREA The attribute ORACLE.WAYBILL would be used to enter the Waybill or Tracking
(ORACLE.WAYBILL) Number for the shipment
Required CHARGE.ID The Charge ID
Required CHARGE.OPERAMT Extended operating cost amount
(EXTENDED) (T)
Optional CHARGE.CHARGETYPE Charge Type such as Handling
Required SHIPUNIT.CARRIER Carrier transporting the ship unit
Optional SHIPUNIT.TRACKINGID Unique identified for tracking an individual ship unit/container
Optional SHIPUNIT.CARRSRVLVL Carrier service level for the ship unit
Required SHIPUNIT.QUANTITY Total weight of the ship unit
(TOTWEIGHT)

Manifestptnrint.doc Oracle Confidential - For internal use only 37

Appendix C – Manifest Integration FAQ
1. At what levels can the carrier tracking and waybill number be updated?

The carrier tracking number can be entered for the attribute SHIPUNIT.TRACKINGID. This
is equivalent to a carrier tracking number for a specific container. The waybill number can be
entered in the SHIPMENT.USERAREA.

2. At what levels can the carrier charges be updated?

Charges can be entered for the element SHIPMENT and SHIPUNIT. It is important to note
that the <CHARGE> segment is not included in the ShowShipment Request message. This
segment needs to be inserted by the manifest partner.

3. What are the valid charge types accepted in the ShowShipment Advice message?

The element <CHARGETYPE> in the ShowShipment Advice message is validated against

the Freight Cost Types defined in Oracle Shipping. To navigate to the freight cost types
Shipping > Setup > Freight Carriers, Cost Types > Freight Cost Types.

4. Can the ship method be updated once the ShowShipment Request has been sent to the
manifest partner?

The manifest partner in the ShowShipment Advice message can update the attributes
SHIPMENT.CARRIER, SHIPMENT.CARRIERSRVLVL, and
SHIPMENT.TRANSMETHD.

5. Can the container weight be updated based on the scale weight?

The shipment/container weight can be updated at the time of shipment based on the scale
weight. The scale weight would override the weight if specified in the shipment request
message.

6. What is the required delivery status needed to send the outbound shipment request to
the manifest partner?

The delivery must be in the status ‘Staged/Pick Confirmed’ in order to send the
ShowShipment Request to the manifest partner.

7. How can I view the XML document and validate that it has been successfully sent and
received?

The responsibility Workflow Administrator Web Applications provides a transaction monitor

allowing uses to view the status of both inbound and outbound messages.

Navigation: Workflow Administrator Web Applications > Transaction Monitor > Select
Inbound or Outbound Messages

8. I have successfully sent the Shipment Request message, however I’m not seeing it in the
Workflow Transaction Monitor?

Oracle Workflow Agent Listeners must be started before the XML transactions can execute.

To enable the workflow listeners:

Manifestptnrint.doc Oracle Confidential - For internal use only 38

 Switch Responsibility to System Administrator. Then navigate: Requests/Run. In the Run
This Request field, select Workflow Agent Listener. The request must be run for the
following three agent names. Schedule the run request for every minute.

• ECX_INBOUND
• ECX_TRANSACTION
• WF_DEFERRED

9. The Transaction Monitor indicates ShowShipment Advice message was processed

successfully, however my delivery has not been updated or ship confirmed?

To identify failed shipment advice transactions, navigate to the Shipment Message

Corrections form. This form will display those shipment advice transactions that are in the
transaction status ‘Error’. The form allows you to make corrections and re-submit the
shipment advice transaction for processing.

Navigation: Shipping > Interfaces > Interface Message Corrections

10. Can I cancel the Shipment Request once it has been sent to the manifest partner?

The Shipment Request can be canceled provided the Carrier Manifesting System has not
processed the request. To cancel the request, navigate to the Shipping Transactions form and
select the Action ‘Send Outbound Message’. In the Send Outbound Message dialog box,
select ‘Send Shipment Cancellation’ and click the OK button. Once the cancellation has been
processed the delivery status will change from ‘Shipment Requested’ to ‘Open’.

The warning message below will be displayed when the Shipment Cancellation has been
initiated.

“Warning: Shipment Request Cancellation has been initiated. Delivery 908240 must also be
cancelled or voided in the Manifesting Application to complete the cancellation process”

11. How do I know which attributes in the XML Request and Advice messages are optional
and mandatory?

The table in Appendix A lists each of the ShowShipment elements/attributes, whether they are
required or optional, and whether they are used for inbound, outbound, or both.

The Required column indicates whether the element/attribute is required or optional for
INBOUND (I), OUTBOUND (O), or BOTH (B).

12. Which party is responsible for communicating end of day shipping information to the
carrier?

The manifest partner is responsible for the end of day manifest closing procedure and
communication of shipment data to the carrier host system.

Manifestptnrint.doc Oracle Confidential - For internal use only 39

Appendix D – Supporting Documentation
• Oracle Transportation Execution User’s Guide, Part No. B10666-03 March 2005

https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=295186.1

• Oracle Transportation Execution Implementation Guide, Part No. B10670-04 August

2005

https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=295186.1

• Oracle Transportation Carrier Manifesting – A Topical Essay

https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id
=NOT&p_id=113492.1

• Oracle XML Gateway User’s Guide, Release 11.5.10, Part No. B10665-03 July 2005

• Oracle Workflow User’s Guide. Release 2.6.4, Part No. B15854-03 July 2005

Manifestptnrint.doc Oracle Confidential - For internal use only 40