DSNO 856 Information EC_SHIP

R11i E-Commerce Gateway Implementation Guideline

Imp Guide Outline Page 1

R11i e-Commerce Gateway

Implementation Manual Update for

Shipping Execution Transactions

Please send comments and updates [email protected]

(updated November 16, 2000)



Contents

Implementation Manual Update for Shipping Execution Transactions ............................................................................... 3

Oracle Shipping Execution ................................................................................................................................................... 4

Current Information ............................................................................................................ 4

Outbound Shipment Notice/Manifest (DSNO/856/DESADV).................................................. 5

Trading Partner Link to Oracle e-Commerce Gateway....................................................... 5Relevant Oracle Shipping Execution Profiles and Set Ups................................................ 5Extract Criteria ................................................................................................................... 5Columns Updated Upon Extraction .................................................................................... 6

Appendix: Shipping Execution Transaction Summaries........................................................... 7

Oracle Shipping Execution Transaction Summaries........................................................... 7Current Information................................................................................................................... 7

Outbound Ship Notice/Manifest ......................................................................................... 8(DSNO/856/DESADV) ...................................................................................................... 8

User Guide Update for Shipping Execution Transactions ................................................................................................... 13

Running the Ship Notice/Manifest Outbound (DSNO) Extract Program ......................... 14



Implementation Manual Update for Shipping Execution Transactions

Note about this manual:

It is not intended to repeat all the details about the Shipping Execution applicationand processes. Refer to the Shipping Execution manual for detail about their dataelements and codes.



Oracle Shipping Execution

The implementation of any transaction requires some set up in Oracle Applicationsas well as Oracle e-Commerce Gateway. This chapter focuses on the application setups necessary to implement a transaction that integrates with Oracle ShippingExecution.

The following transaction integrates with Oracle Shipping Execution.

Transaction Name Direction TransactionCode

ASCX12

EDIFACT

Shipment Notice/Manifest Outbound DSNO 856 DESADV

The topics covered for outbound transactions include the following:

• Trading Partner Link to Oracle e-Commerce Gateway

• Relevant Oracle Shipping Execution Set Ups

• Extract Criteria

• Columns Updated Upon Extraction

Current Information

The transaction requirements may change when enhancements are made such asadditional data added to the transaction.

Current transaction details can be found on Oracle Support’s web site.

Current detail record layouts are reported via the Transaction Layout DefinitionReport and the Interface File Data Report.

Refer to Oracle Shipping Execution appendix in the supplemental Oracle e-Commerce Gateway Implementation Manual for a diagram of the record hierarchy andrecord looping structure, and record summaries.



Outbound Shipment Notice/Manifest (DSNO/856/DESADV)

Trading Partner Link to Oracle e-Commerce Gateway

Customers and Customer sites are defined in either Oracle Order Management orOracle Received. Included in the definition is the EDI location code that tradingpartners agree to exchange to represent the full detailed address. Often they do notsend the full address, but just the EDI location code. This is a critical data field toOracle e-Commerce Gateway.

The EDI location code is the link between a Customer/Customer site in OracleApplications and the trading partner site definition in Oracle e-CommerceGateway. This allows Oracle e-Commerce Gateway to access the detailed dataabout the Customer or Customer site in the base Oracle applications withoutmaintaining the detail data in Oracle e-Commerce Gateway.

To ensure that the trading partner link between Oracle e-Commerce Gateway andOracle Applications is set up properly, verify that the Customer/Customer site andthe EDI location code in Oracle Applications is the correct Customer/Customer siteselected for the Trading Partner definition in Oracle e-Commerce Gateway. Theselected Customer/Customer site and the EDI location code defined in OracleApplications are displayed in the Define Trading Partners window, Assignmenttab. If the data is not what you intend it to be, you must make the appropriatechanges for the transaction to be extracted for the correct trading partner. Thiscould involve either altering the Customer/ Customer site in the base Oracleapplication, or assigning a different Customer/Customer site to that location codein Oracle e-Commerce Gateway.

Refer to the Trading Partner chapter for recommendations on selecting the correcttrading partner EDI location code for the control record 0010 for the transaction inthe transaction interface file.

Relevant Oracle Shipping Execution Profiles and Set Ups

There are no required setups in Oracle Shipping Execution for this transaction.

Extract Criteria

Once the shipment is confirmed, define a trip to specify the exact contents. A tripmay be a truck load containing x number of items in y number of boxes defined andin z number of pallets.

After the trip is closed, the shipping process initiates the transaction through theOracle e-Commerce Gateway. This transaction is event–driven by the shippingprocess; it is not usually driven by a scheduled concurrent manager request.However, Oracle e-Commerce Gateway can be used to extract the transaction again,if necessary.



The outbound Shipment Notice/Manifest transaction is formed by the followingseven database views that are defined according to the Oracle Shipping Executiondata model for the Shipment Notice/Manifest transaction.

• WSH_DSNO_ALLOWANCE_CHARGES_V

• WSH_DSNO_CONTAINERS_V

• WSH_DSNO_DELIVERIES_V (header)

• WSH_DSNO_DELIVERY_ATTRIBS_V (header level)

• WSH_DSNO_ITEM_DETAILS_V

• WSH_DSNO_ITEMS_V

• WSH_DSNO_ORDERS_V

The ECE_DSNO_DELIVERIES_V view is used to identify which ShipmentNotice/Manifest is eligible for extraction.

The extract criteria is the following:

• Trading partner is defined

• Transaction type enabled for the trading partner

• The Stop is closed

Columns Updated Upon Extraction

The following is a list of fields updated by theWSH_ECE_VIEW_DEF_UPDATE_DEL_ASN_INFO procedure that is executedafter the transaction data is extracted.

Table Column ValueWSH_NEW_DELIVERIES ASN_SEQ_NUMBER

ASN_DATE_SENT SYSDATE



Appendix: Shipping Execution Transaction Summaries

Oracle Shipping Execution Transaction Summaries

The following Oracle Shipping Execution transaction is summarized in thisappendix.

Transaction Name Direction TransactionCode

ASCX12

EDIFACT

Ship Notice/Manifest Outbound DSNO 856 DESADV

Current Information

The transaction file may change when enhancements are made such as additionaldata added to the transaction.

Current transaction summaries can be found on Oracle Support’s web site.

Current detail record layouts are reported via the Transaction Definition LayoutReport and the Interface File Data Report.



Outbound Ship Notice/Manifest

(DSNO/856/DESADV)

The receiver of a Ship Notice/Manifest transaction may use the data for more thanone purpose. The manner in which the data is organized and structured plays alarge part in determining its usefulness for a particular function. For example, aShip Notice modeled in a Delivery-Container-Item organization would facilitate thereceiving and inspection process, where the focus is on verifying the number ofcontainers (pallets, bins, racks, etc.) received, and the number and type of items ineach container. Conversely, a Ship Notice modeled in a Delivery-Order-Itemorganization would be better suited to the process of reconciling received goodsagainst orders, where information such as total item quantities, order numbers, lotnumbers and/or serial numbers are more useful.

The Oracle e-Commerce presents the data for the Ship Notice/Manifest from theDelivery-Container-Item perspective. Container items are associated with theircorresponding Order and Detail data so that the EDI translator may invert thelevels in the transaction to meet the trading partner’s specific needs.

Shipment Notice/Manifest Data Model

Delivery

Container

Order

PackedItems

ItemDetails

Container entity will not be present for orders/items that are not packed intocontainers.



Outbound Ship Notice/Manifest(DSNO/856/DESADV)

(DSNO) Shipment Notice Structure

Delivery

DeliveryLevel

RecordNumbers

(1000-2999)

denotes a hierarchical level or loop that may repeat within the transacton file

Container

Delivery FlexfieldsOptionalFlexsLoop

(3000-3999)

s(4000-4999)Allowances & ChargesOptional

A/CLoop

Outer Container

Outer

Level

Allowances & ChargesOptionalA/CLoop

Items (packed)

Item DetailsItem

DetailLevel

ItemLevel

InnerContainer

Level

Inner Container

OrderLevel

Orders (packed)

OrderLevel

Orders (packed)

Allowances & ChargesOptional

A/CLoop

Items (packed)

Item Details

ItemLevel

ItemDetailLevel

Allowances & Charges

Items (unpacked items)

Item DetailsItemDetailLevel

ItemLevel

OrderLevel

Orders (for unpacked items)

OptionalA/CLoop

(4500)

(4000-4900)

(5100-5180)

(5500-5599)

(5600- Container IDs)(5700-5790)

(6400)

(7000-7699)

(8000-8199)

(9000-9199)

(5600- Container IDs)(5700-5790)

(6400)

(7000-7699)

(8000-8199)

(9000-9199)

One output file is created for each Trip Stop. It includes all eligible Deliveries. While only twolevels of containers are shown in the example, containers may be nested to any level.



Outbound Ship Notice/Manifest(DSNO/856/DESADV)

Record occurrences within the transaction:

Records Record Content Loop Ocurrences0010 Control Only one record occurrence per transaction0020-0050 TP Header flexfields Only one set occurrence per transaction0060-0070 TP Detail flexfields Only one set occurrence per transaction1000-2999 Delivery Header Only one record occurrence per transaction3100-3900 Delivery Flexfields Header One set per order. (only unpacked orders).4000-4900 Orders Unpacked Items One set per item within the order. (unpacked).4500 Order Items Unpacked Items One set per item within the order. (unpacked).5100-5180 Item Freight Charges Unpacked Items One set per A/C within the item5500 Delivery Item Detail Records Unpacked Items One set per item detail within the item with this loop5510-5599 Delivery Item Detail

(Flexfields)Unpacked Items One set per item detail within the item with this loop

5600 Container Hierarchy Container Indicates parent/child relationship of Containers.5700-5790 Delivery Containers Container One set per order within this Container.6000-6400 Orders Container One set per order within the container.7000-7699 Order Items Container One set per item within the order within the container8000-8199 Item Freight Charges Container One set per A/C within the item within this loop9000-9199 Item Details Container One set per item detail within the item with this loop

Record Summary:

Seq Record Data Level RecordNumber

1 Control RecordControl Record

0010

2 Trading Partner Header Flexfileds TP header flexfields 0020-0050 Flexfields3 Trading Partner Detail Flexfileds TP Detail flexfields 0060-0070 Flexfields

4 Trip Stop/Delivery Data (Key Data) Delivery 10005 Carrier Delivery 10106 Weights, Volume Delivery 10157 Routing Instructions Delivery 10308 Warehouse Address Delivery 20009 Warehouse Contact data Delivery 201010 Pooled Address Data Delivery 210011 Pooled Contact Data Delivery 211012 Consignee Address Data Delivery 220013 Consignee Contact Data Delivery 221014 Delivery Address Data Delivery 230015 Delivery Contact Data Delivery 231016 Destination Address Data Delivery 240017 Destination Contact Date Delivery 241018 Warehouse Flexfields Delivery Flexfields 3060-3095 Flexfields19 Destination Flexfields Delivery Flexfields 3100-3150 Flexfields20 Customer Flexfields Delivery Flexfields 3200-3230 Flexfields21 Customer Global Flexfields Delivery Flexfields 3300-3340 Flexfields22 Delivery Flexfields Delivery Flexfields 3600-3630 Flexfields23 Delivery Trading Partner Flexfields Delivery Flexfields 3700-3730 Flexfields24 Delivery Global Flexfield Delivery Flexfields 3800-3840 Flexfields25 Purchase Order Data Order (Unpacked) 400026 Purchase Order Data (Tax Data) Order (Unpacked) 401027 Purchase Order Data

(Payment Terms Data, Currency)Order (Unpacked) 4020

28 Purchase Order Data (FOB Data) Order (Unpacked) 403029 Order By Address Data Order (Unpacked) 4100



30 Order By Contact Data Order (Unpacked) 411031 Invoice Address Data Order (Unpacked) 415032 Invoice Contact Data Order (Unpacked) 416033 Order Header Flexfields Order (Unpacked) 4200-4230 Flexfields34 Order Header Global Flexfields Order (Unpacked) 4300-4340 Flexfields35 Order Header Trading Partner Flexfields Order (Unpacked) 4360-43936 Item Data Items (Unpacked) 450037 Item Data (more) Items (Unpacked) 451038 Item Data (Quantity, Price) Items (Unpacked) 452039 Hazardous Data Items (Unpacked) 453040 Item Data from Release Management Items (Unpacked) 4540-455041 Industry Flexfields Items (Unpacked) 4600-4625 Flexfields42 Delivery Detail Flexfields Items (Unpacked) 4630-4650 Flexfields43 Order Line Flexfields Items (Unpacked) 4660-4690 Flexfields44 Order Line Global Flexfields Items (Unpacked) 4700-4740 Flexfields45 Line Part Flexfields Items (Unpacked) 4750-4780 Flexfields46 Order Line Trading Partner Flexfields Items (Unpacked) 4790-4820 Flexfields47 Order Line Pricing Flexfields Items (Unpacked) 4830-4850 Flexfields48 Release Management Flexfields Items (Unpacked) 4860-4890 Flexfields49 AC and currency data Item Freight Charges (Unpacked) 510050 Freight Charge Flexfields Item Freight Charges (Unpacked) 5150-5180 Flexfields51 Lot, serial, production sequence Item Detail (Unpacked) 550052 Delivery Detail Trading Partner

FlexfieldsItem Detail (Unpacked) 5510-5540 Flexfields

53 Delivery Detail Flexfields Item Freight Charges (Unpacked) 5545-5570 Flexfields54 Container: Outer and Inner Container

RelationshipContainer Hierarchy 5600

55 Container Data, Weights Container 570056 Container Flexfields Container 5710-5740 Flexfields57 Container Trading Partner Flexfields Container 5750-5790 Flexfields58 Purchase Order Data Orders (Containerized) 600059 Purchase Order Data (Tax Data) Orders (Containerized) 601060 Purchase Order Data

(Payment Terms Data, Currency)Orders (Containerized) 6020

61 Purchase Order Data (FOB Data) Orders (Containerized) 603062 Order By Address, Data Orders (Containerized) 610063 Order By Contact Data Orders (Containerized) 611064 Invoice Address Data Orders (Containerized) 615065 Invoice Contact Data (more) Orders (Containerized) 616066 Order Header Flexfields Orders (Containerized) 6200-6230 Flexfields67 Order Header Global Flexfields Orders (Containerized) 6300-6340 Flexfields68 Order Header Trading Partner Flexfields Orders (Containerized) 6360-6390 Flexfields69 Item Data Items (Containerized) 700070 Item Data (more) Items (Containerized) 701071 Item Data (Quantity, Price) Items (Containerized) 702072 Hazardous Data Items (Containerized) 703073 Item Data from Release Management Items (Containerized) 7040-705074 Industry Flexfields Items (Containerized) 7100--7130 Flexfields75 Order Line Pricing Flexfields Items (Containerized) 7200-7220 Flexfields76 Order Line Flexfields Items (Containerized) 7240-7270 Flexfields77 Order Line Global Flexfields Items (Containerized) 7320-7360 Flexfields78 Delivery Detail Flexfields Items (Containerized) 7370-7400 Flexfields79 Line Part Flexfields Items (Containerized) 7460-7490 Flexfields80 Order Line Trading Partner Flexfields Items (Containerized) 7510-7540 Flexfields81 Release Management Flexfields Items (Containerized) 7570-7600 Flexfields82 AC and Currency data Item Freight Charges

(Containerized)8000

83 Freight Charge Flexfields Item Freight Charges(Containerized)

8050-8080 Flexfields

84 Lot, serial, production sequence Item Details (Containerized) 900085 Delivery Detail Trading Partner

FlexfieldsItem Details (Containerized) 9010-9040 Flexfields



86 Delivery Detail Flexfields Item Details (Containerized) 9045-9070 Flexfields

The following pairs of records have equivalent record layouts.

Record Data UnpackedRecord

Number

PackedRecord

Number1 Purchase Order Data Order 4000 60002 Purchase Order Data (Tax Data) Order 4010 60103 Purchase Order Data

(Payment Terms Data, Currency)Order 4020 6020

4 Purchase Order Data (FOB Data) Order 4030 60305 Item Data Items 4500 70006 Item Data (more) Items 4510 70107 Item Data (Quantity, Price) Items 4520 70208 Hazardous Data Items 4530 70309 Item Data from Release Management Items 4540-4550 7040-7050

10 AC and currency data Item Freight Charges 5100 800011 Lot, serial, production sequence Item Detail 5500 9000



User Guide Update for Shipping Execution Transactions



Running the Ship Notice/Manifest Outbound (DSNO) Extract Program

Use this transaction to list the contents of a shipment including trip and deliverydata such as carrier, parties involved with the shipment, container, order; productdata such as description, physical characteristics, type of packaging, lot and serialnumbers; and allowances and charges.

This transaction is initiated by the Oracle Shipping Execution application or byOracle e-Commerce Gateway if necessary.

Use Oracle Order Management to enter and maintain customer orders. Alternately,Order Management’s Order Import open interface can be used to import customerorders from non–Oracle order management systems and EDI transactions.

After the customer order is entered, use Order Management to book, approve, andthen use Shipping Execution to schedule shipments. During the shipmentpreparation process, inventory is released, pick slips are printed, shippingdocuments are prepared, and the shipment is confirmed.

Prerequisite Setup in Oracle Shipping ExecutionOnce the delivery is ship confirmed and the pick up stop is closed a DSNO isautomatically generated. A DSNO may be manually generated by choosing a stopthat has already been closed. A delivery may be a truck load containing x numberof items in y number of boxes defined and in z number of pallets.

After the pick up stop is closed, the shipping process initiates the transactionthrough the Oracle e-Commerce Gateway. This transaction is event–driven by theshipping process; it is not driven by a scheduled concurrent manager request.

Oracle e-Commerce Gateway can be used to reinitiate the process, if necessary.This section documents how to extract the transaction again as needed

Note: Descriptive flexfields may be needed for some data elements.

Prerequisites in Oracle e-Commerce Gateway❏ Create the outbound directory and update the INIT.ORA file. See: DefiningData File Directories, Oracle e-Commerce Gateway Implementation Manual, Release 11i.

❏ Define the ECE: Output file path profile option. See: e-Commerce GatewayProfile Options, Oracle e-Commerce Gateway Implementation Manual, Release 11i.

❏ Define trading partner relationships and enable EDI transactions for the tradingpartner. See: Defining Trading Partner Data on page 3-4 in the Oracle e-CommerceGateway User’s Guide

❏ Define code conversions. See: Defining Code Conversion Categories on page 4-8, Assigning Categories on page 4-10, and Defining Code conversion Values onpage 4-15 in the Oracle e-Commerce Gateway User’s Guide

❏ Customise interface data file layout, if necessary. See: Changing the InterfaceData File Record Layout on page 5-2 in the Oracle e-Commerce Gateway User’s Guide



To run the Ship Notice/Manifest outbound extract program:

Note: Performing this procedure from e-Commerce Gateway is onlynecessary if you need to extract the shipment notice again.

1. Navigate to the Extract Program window

2. Select Request to submit an individual request.

3. Select the OUT: Ship Notice/Manifest (856/DESADV) request.

4. In the Parameters window, enter the following:

• Enter the stop identifier.

• Specify an output directory path, if not using the default.

• Specify an output data file name, if not using the default.

Note: The file name generated by Oracle Shipping Execution may be different

than the one generated by the request submitted within the Oracle e-

Commerce Gateway.

• Set the debug mode to report on debug information. Debug information is

written to the concurrent manager log file:

0 = OFF: No debug information is generated.

1 = LOW: Summary debug information is written to the concurrent manager logfile.

2 = MEDIUM: Medium level debug information is written to the concurrentmanager log file.

3 = HIGH: High level debug information is written to the concurrent manager log

file. (This option generates much information.)

5. When finished, choose OK in the Parameters window.

6. Choose Submit and note the Request ID returned.

See Also

Outbound Invoice, Oracle e-Commerce Gateway Implementation Manual, Release 11i

Submitting a Request, Oracle Applications User’s Guide

Viewing the Status of Concurrent Programs on page 9-7 in the Oracle e-Commerce GatewayUser’s Guide

Documents

DSNO 856 Information EC_SHIP