Sei sulla pagina 1di 15

R11i E-Commerce Gateway Implementation Guideline

R11i e-Commerce Gateway Implementation Manual Update for Shipping Execution Transactions Please send comments and updates to EDISIG@us.oracle.com (updated November 16, 2000)

Imp Guide Outline

Page 1

R11i E-Commerce Gateway Implementation Guideline

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....................................................... 5 Relevant Oracle Shipping Execution Profiles and Set Ups................................................ 5 Extract Criteria ................................................................................................................... 5 Columns Updated Upon Extraction .................................................................................... 6 Appendix: Shipping Execution Transaction Summaries........................................................... 7 Oracle Shipping Execution Transaction Summaries........................................................... 7
Current 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

Imp Guide Outline

Page 2

R11i E-Commerce Gateway Implementation Guideline

Implementation Manual Update for Shipping Execution Transactions


Note about this manual: It is not intended to repeat all the details about the Shipping Execution application and processes. Refer to the Shipping Execution manual for detail about their data elements and codes.

Imp Guide Outline

Page 3

R11i E-Commerce Gateway Implementation Guideline

Oracle Shipping Execution


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

The following transaction integrates with Oracle Shipping Execution.

Transaction Name Shipment Notice/Manifest

Direction Outbound

Transaction Code DSNO

ASC X12 856

EDIFACT 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 as additional data added to the transaction. Current transaction details can be found on Oracle Supports web site. Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report. Refer to Oracle Shipping Execution appendix in the supplemental Oracle eCommerce Gateway Implementation Manual for a diagram of the record hierarchy and record looping structure, and record summaries.

Imp Guide Outline

Page 4

R11i E-Commerce Gateway Implementation Guideline

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 or Oracle Received. Included in the definition is the EDI location code that trading partners agree to exchange to represent the full detailed address. Often they do not send the full address, but just the EDI location code. This is a critical data field to Oracle e-Commerce Gateway. The EDI location code is the link between a Customer/Customer site in Oracle Applications and the trading partner site definition in Oracle e-Commerce Gateway. This allows Oracle e-Commerce Gateway to access the detailed data about the Customer or Customer site in the base Oracle applications without maintaining the detail data in Oracle e-Commerce Gateway. To ensure that the trading partner link between Oracle e-Commerce Gateway and Oracle Applications is set up properly, verify that the Customer/Customer site and the EDI location code in Oracle Applications is the correct Customer/Customer site selected for the Trading Partner definition in Oracle e-Commerce Gateway. The selected Customer/Customer site and the EDI location code defined in Oracle Applications are displayed in the Define Trading Partners window, Assignment tab. If the data is not what you intend it to be, you must make the appropriate changes for the transaction to be extracted for the correct trading partner. This could involve either altering the Customer/ Customer site in the base Oracle application, or assigning a different Customer/Customer site to that location code in Oracle e-Commerce Gateway.

Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI location code for the control record 0010 for the transaction in the 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 trip may be a truck load containing x number of items in y number of boxes defined and in z number of pallets. After the trip is closed, the shipping process initiates the transaction through the Oracle e-Commerce Gateway. This transaction is eventdriven by the shipping process; 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. Imp Guide Outline Page 5

R11i E-Commerce Gateway Implementation Guideline The outbound Shipment Notice/Manifest transaction is formed by the following seven database views that are defined according to the Oracle Shipping Execution data 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 Shipment Notice/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 the WSH_ECE_VIEW_DEF_UPDATE_DEL_ASN_INFO procedure that is executed after the transaction data is extracted.

Table WSH_NEW_DELIVERIES

Column ASN_SEQ_NUMBER ASN_DATE_SENT

Value SYSDATE

Imp Guide Outline

Page 6

R11i E-Commerce Gateway Implementation Guideline

Appendix: Shipping Execution Transaction Summaries


Oracle Shipping Execution Transaction Summaries
The following Oracle Shipping Execution transaction is summarized in this appendix. Transaction Name Ship Notice/Manifest Direction Outbound Transaction Code DSNO ASC X12 856 EDIFACT DESADV

Current Information
The transaction file may change when enhancements are made such as additional data added to the transaction. Current transaction summaries can be found on Oracle Supports web site. Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report.

Imp Guide Outline

Page 7

R11i E-Commerce Gateway Implementation Guideline

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

The receiver of a Ship Notice/Manifest transaction may use the data for more than one purpose. The manner in which the data is organized and structured plays a large part in determining its usefulness for a particular function. For example, a Ship Notice modeled in a Delivery-Container-Item organization would facilitate the receiving and inspection process, where the focus is on verifying the number of containers (pallets, bins, racks, etc.) received, and the number and type of items in each container. Conversely, a Ship Notice modeled in a Delivery-Order-Item organization would be better suited to the process of reconciling received goods against orders, where information such as total item quantities, order numbers, lot numbers and/or serial numbers are more useful. The Oracle e-Commerce presents the data for the Ship Notice/Manifest from the Delivery-Container-Item perspective. Container items are associated with their corresponding Order and Detail data so that the EDI translator may invert the levels in the transaction to meet the trading partners specific needs.
Shipment Notice/Manifest Data Model

Delivery

Container

Order Packed Items Item Details

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

Imp Guide Outline

Page 8

R11i E-Commerce Gateway Implementation Guideline

Outbound Ship Notice/Manifest


(DSNO/856/DESADV)

(DSNO) Shipment Notice Structure


Delivery
Optional Flex Loop s Optional A/C Loop s

Record Numbers (1000-2999) (3000-3999) (4000-4999) (4000-4900) (4500) (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)

Delivery Flexfields Allowances & Charges Orders (for unpacked items) Items (unpacked items)

Order Level

Item Level

Optional A/C Loop Item Detail Level

Allowances & Charges Item Details

Outer Container
Delivery Level

Orders (packed) Items (packed)


Order Level Item Level Optional A/C Loop Item Detail Level Outer Level Container

Allowances & Charges Item Details

Inner Container Orders (packed) Items (packed)


Inner Container Order Level Level Item Level Optional A/C Loop Item Detail Level

Allowances & Charges Item Details

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

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

Imp Guide Outline

Page 9

R11i E-Commerce Gateway Implementation Guideline

Outbound Ship Notice/Manifest


(DSNO/856/DESADV)

Record occurrences within the transaction:


Records 0010 0020-0050 0060-0070 1000-2999 3100-3900 4000-4900 4500 5100-5180 5500 5510-5599 5600 5700-5790 6000-6400 7000-7699 8000-8199 9000-9199 Record Content Control TP Header flexfields TP Detail flexfields Delivery Delivery Flexfields Orders Order Items Item Freight Charges Delivery Item Detail Records Delivery Item Detail (Flexfields) Container Hierarchy Delivery Containers Orders Order Items Item Freight Charges Item Details Loop Ocurrences Only one record occurrence per transaction Only one set occurrence per transaction Only one set occurrence per transaction Only one record occurrence per transaction One set per order. (only unpacked orders). One set per item within the order. (unpacked). One set per item within the order. (unpacked). One set per A/C within the item One set per item detail within the item with this loop One set per item detail within the item with this loop Indicates parent/child relationship of Containers. One set per order within this Container. One set per order within the container. One set per item within the order within the container One set per A/C within the item within this loop One set per item detail within the item with this loop

Header Header Unpacked Items Unpacked Items Unpacked Items Unpacked Items Unpacked Items Container Container Container Container Container Container

Record Summary:
Seq 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 Record Control Record Control Record Trading Partner Header Flexfileds Trading Partner Detail Flexfileds Trip Stop/Delivery Data (Key Data) Carrier Weights, Volume Routing Instructions Warehouse Address Warehouse Contact data Pooled Address Data Pooled Contact Data Consignee Address Data Consignee Contact Data Delivery Address Data Delivery Contact Data Destination Address Data Destination Contact Date Warehouse Flexfields Destination Flexfields Customer Flexfields Customer Global Flexfields Delivery Flexfields Delivery Trading Partner Flexfields Delivery Global Flexfield Purchase Order Data Purchase Order Data (Tax Data) Purchase Order Data (Payment Terms Data, Currency) Purchase Order Data (FOB Data) Order By Address Data Data Level Record Number 0010 0020-0050 0060-0070 1000 1010 1015 1030 2000 2010 2100 2110 2200 2210 2300 2310 2400 2410 3060-3095 3100-3150 3200-3230 3300-3340 3600-3630 3700-3730 3800-3840 4000 4010 4020 4030 4100 Flexfields Flexfields

TP header flexfields TP Detail flexfields


Delivery Delivery Delivery Delivery Delivery Delivery Delivery Delivery Delivery Delivery Delivery Delivery Delivery Delivery Delivery Flexfields Delivery Flexfields Delivery Flexfields Delivery Flexfields Delivery Flexfields Delivery Flexfields Delivery Flexfields Order (Unpacked) Order (Unpacked) Order (Unpacked) Order (Unpacked) Order (Unpacked)

Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields

Imp Guide Outline

Page 10

R11i E-Commerce Gateway Implementation Guideline


30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 Order By Contact Data Invoice Address Data Invoice Contact Data Order Header Flexfields Order Header Global Flexfields Order Header Trading Partner Flexfields Item Data Item Data (more) Item Data (Quantity, Price) Hazardous Data Item Data from Release Management Industry Flexfields Delivery Detail Flexfields Order Line Flexfields Order Line Global Flexfields Line Part Flexfields Order Line Trading Partner Flexfields Order Line Pricing Flexfields Release Management Flexfields AC and currency data Freight Charge Flexfields Lot, serial, production sequence Delivery Detail Trading Partner Flexfields Delivery Detail Flexfields Container: Outer and Inner Container Relationship Container Data, Weights Container Flexfields Container Trading Partner Flexfields Purchase Order Data Purchase Order Data (Tax Data) Purchase Order Data (Payment Terms Data, Currency) Purchase Order Data (FOB Data) Order By Address, Data Order By Contact Data Invoice Address Data Invoice Contact Data (more) Order Header Flexfields Order Header Global Flexfields Order Header Trading Partner Flexfields Item Data Item Data (more) Item Data (Quantity, Price) Hazardous Data Item Data from Release Management Industry Flexfields Order Line Pricing Flexfields Order Line Flexfields Order Line Global Flexfields Delivery Detail Flexfields Line Part Flexfields Order Line Trading Partner Flexfields Release Management Flexfields AC and Currency data Freight Charge Flexfields Lot, serial, production sequence Delivery Detail Trading Partner Flexfields Order (Unpacked) Order (Unpacked) Order (Unpacked) Order (Unpacked) Order (Unpacked) Order (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Items (Unpacked) Item Freight Charges (Unpacked) Item Freight Charges (Unpacked) Item Detail (Unpacked) Item Detail (Unpacked) Item Freight Charges (Unpacked) Container Hierarchy Container Container Container Orders (Containerized) Orders (Containerized) Orders (Containerized) Orders (Containerized) Orders (Containerized) Orders (Containerized) Orders (Containerized) Orders (Containerized) Orders (Containerized) Orders (Containerized) Orders (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Items (Containerized) Item Freight Charges (Containerized) Item Freight Charges (Containerized) Item Details (Containerized) Item Details (Containerized) 4110 4150 4160 4200-4230 4300-4340 4360-439 4500 4510 4520 4530 4540-4550 4600-4625 4630-4650 4660-4690 4700-4740 4750-4780 4790-4820 4830-4850 4860-4890 5100 5150-5180 5500 5510-5540 5545-5570 5600 5700 5710-5740 5750-5790 6000 6010 6020 6030 6100 6110 6150 6160 6200-6230 6300-6340 6360-6390 7000 7010 7020 7030 7040-7050 7100--7130 7200-7220 7240-7270 7320-7360 7370-7400 7460-7490 7510-7540 7570-7600 8000 8050-8080 9000 9010-9040

Flexfields Flexfields

Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields

Flexfields Flexfields

Flexfields Flexfields Flexfields

Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields Flexfields

Flexfields

Flexfields

Imp Guide Outline

Page 11

R11i E-Commerce Gateway Implementation Guideline


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

The following pairs of records have equivalent record layouts.


Record Data Unpacked Record Number 4000 4010 4020 4030 4500 4510 4520 4530 4540-4550 5100 5500 Packed Record Number 6000 6010 6020 6030 7000 7010 7020 7030 7040-7050 8000 9000

1 2 3 4 5 6 7 8 9 10 11

Purchase Order Data Purchase Order Data (Tax Data) Purchase Order Data (Payment Terms Data, Currency) Purchase Order Data (FOB Data) Item Data Item Data (more) Item Data (Quantity, Price) Hazardous Data Item Data from Release Management AC and currency data Lot, serial, production sequence

Order Order Order Order Items Items Items Items Items Item Freight Charges Item Detail

Imp Guide Outline

Page 12

R11i E-Commerce Gateway Implementation Guideline

User Guide Update for Shipping Execution Transactions

Imp Guide Outline

Page 13

R11i E-Commerce Gateway Implementation Guideline

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


Use this transaction to list the contents of a shipment including trip and delivery data such as carrier, parties involved with the shipment, container, order; product data such as description, physical characteristics, type of packaging, lot and serial numbers; and allowances and charges. This transaction is initiated by the Oracle Shipping Execution application or by Oracle e-Commerce Gateway if necessary. Use Oracle Order Management to enter and maintain customer orders. Alternately, Order Managements Order Import open interface can be used to import customer orders from nonOracle order management systems and EDI transactions. After the customer order is entered, use Order Management to book, approve, and then use Shipping Execution to schedule shipments. During the shipment preparation process, inventory is released, pick slips are printed, shipping documents are prepared, and the shipment is confirmed.

Prerequisite Setup in Oracle Shipping Execution


Once the delivery is ship confirmed and the pick up stop is closed a DSNO is automatically generated. A DSNO may be manually generated by choosing a stop that has already been closed. A delivery may be a truck load containing x number of 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 transaction through the Oracle e-Commerce Gateway. This transaction is eventdriven by the shipping 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: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual, Release 11i. Define the ECE: Output file path profile option. See: e-Commerce Gateway Profile Options, Oracle e-Commerce Gateway Implementation Manual, Release 11i. Define trading partner relationships and enable EDI transactions for the trading partner. See: Defining Trading Partner Data on page 3-4 in the Oracle e-Commerce Gateway Users Guide Define code conversions. See: Defining Code Conversion Categories on page 48, Assigning Categories on page 4-10, and Defining Code conversion Values on page 4-15 in the Oracle e-Commerce Gateway Users Guide Customise interface data file layout, if necessary. See: Changing the Interface Data File Record Layout on page 5-2 in the Oracle e-Commerce Gateway Users Guide

Imp Guide Outline

Page 14

R11i E-Commerce Gateway Implementation Guideline

To run the Ship Notice/Manifest outbound extract program:


Note: Performing this procedure from e-Commerce Gateway is only necessary if you need to extract the shipment notice again. 1. 2. 3. 4. Navigate to the Extract Program window Select Request to submit an individual request. Select the OUT: Ship Notice/Manifest (856/DESADV) request. 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 eCommerce 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 log file. 2 = MEDIUM: Medium level debug information is written to the concurrent manager log file. 3 = HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.) 5. 6. See Also Outbound Invoice, Oracle e-Commerce Gateway Implementation Manual, Release 11i Submitting a Request, Oracle Applications Users Guide Viewing the Status of Concurrent Programs on page 9-7 in the Oracle e-Commerce Gateway Users Guide When finished, choose OK in the Parameters window. Choose Submit and note the Request ID returned.

Imp Guide Outline

Page 15