This chapter covers the following topics:
Oracle Shipping Execution provides you with a variety of flexible and easy-to-use reports that help to improve productivity and increase control. Text attachments can be used with reports and processes to print shipping application data. For example, unpacking instructions entered on a delivery line can be printed on the Packing Slip.
Using an XML Publisher-enabled shipping document, you can define your own report layouts, include additional fields, and print the document in PDF format.
Note: A printer must be assigned to the reports. This is set up in the Choose Printers for Shipping Documents window. See Oracle Order Management Implementation Manual.
Oracle Shipping Execution reports are visible (depending on the user role) from the Shipping Reports and Documents window. Using the list of values in the Name field, select the report that you want to run. Once selected, the Parameters window is displayed for the report. The parameters must be defined where applicable.
Note: Depending on the report you are running, some parameters are required, some are optional, and some reports do not require any parameters.
See: Oracle E-Business Suite User's Guide
Super User and Business User are typical Oracle Application user types that enable different levels of access to the applications.
A super user is typically the System Administrator / IT Engineer. This user may define and extend the Oracle XML Publisher layout templates for shipping documents as part of the application setup.
The business user typically includes most manager roles, including Sales Managers, Sales Representatives, Customer Service Managers, Customer Service Representatives, Contract Administrators / Negotiators, and well as other business managers. This user has extensive business domain knowledge, including business document authoring, negotiation, and approval. This user is typically responsible for defining the layouts of the business document and working with super users to define or update the layout templates to generate business documents in the appropriate format.
Document sets can be printed as part of the pick release process through the Release Sales Orders for Picking window. The field Document Set is in the header region. Use the list of values to select the document set that you want printed with the pick release process.
Any XML Publisher enabled Shipping document can also be included in a document set. Once included, the document is automatically printed with other documents in the document set.
See: Oracle Order Management Implementation Manual for information on document sets.
Document sets can be printed per release rules. Defining release rules enables you to specify a Document Set (within the Shipping tab of the Release Rules window). Use the list of values to select the document set that you want printed when your release rule is used, for example during ship confirm.
Any XML Publisher enabled Shipping document can also be included in a document set. Once included, the document is automatically printed with other documents in the document set.
See: Oracle Order Management Implementation Manual for information on defining release rules.
Document sets can be printed for trips and deliveries through the Shipping Transactions window, the Quick Ship window, or the Shipping Execution Simplified User Interface.
After querying the delivery or trip in the Shipping Transactions window or in the Quick Ship window, click Print Document Set and, if more than one document set exists, select a document set from the list.
In the Shipping Execution Simplified User Interface, query the delivery or the trip and then select the Print Document Set from the Actions menu and, if more than one document set exists, select a document set from the list.
Any XML-Publisher-enabled Shipping document can also be included in a document set. Once included, the document is automatically printed with other documents in the document set.
Oracle XML Publisher enables you to extend various Oracle Shipping Execution reports to suit your business needs. The following list represents those seeded Oracle Shipping Execution report templates within Oracle XML Publisher:
Bill of Lading
Commercial Invoice
Mailing Label
Master Bill of Lading
Packing Slip
Pick Slip
Vehicle Load Sheet Summary
Once defined or modified, these templates can be used when printing reports from the Reports and Processes window, the Shipping Transactions window, the Quick Ship window, the Shipping Execution Simplified User Interface, and through document sets.
The management of shipping document templates is performed in Oracle XML Publisher.
Note: Editing software can be used to modify and customize templates. For example, Microsoft Word and Adobe Acrobat.
See: Oracle XML Publisher User's Guide
See: Oracle Order Management Implementation Manual for information on document sets.
Oracle Shipping Execution along with Oracle XML Publisher, enable you to print various reports in the Adobe PDF format. PDF format enabled reports are run in exactly the same way as other shipping reports. (See: Oracle E-Business Suite User's Guide for information on report printing procedures). You must, however, enable PDF printing within Oracle Shipping Execution on the Shipping Document Sets window or through the use of concurrent requests. See: Oracle Order Management Implementation Manual for information on defining document sets.
Seeded concurrent requests, that enable PDF printing include the following:
Pick Slip PDF
Packing Slip PDF
Mailing Label PDF
Bill of Lading PDF
Master Bill of Lading PDF
Commercial Invoice PDF
Vehicle Load Sheet Summary PDF
The chosen template for each report (within Oracle XML Publisher) is the template used when executing the concurrent request for each report.
Multiple Templates: Multiple templates can be created for each report. If your report has multiple templates, then you select which layout to use when printing. Within the Shipping Reports and Documents window, Upon Completion region, click Options to select the layout template to be used.
The Auto-pack Report is designed to provide visibility to batches that have been successfully packed by the Auto Pack concurrent program.
Submission
In the Shipping Reports and Documents window, select Auto-pack Report in the Name field.
Note: This report is automatically printed as a result of the Auto Pack concurrent process.
Parameters
When you request a Auto-pack Report, Shipping Execution provides you with the following parameters:
Auto-pack Batch: Select the Auto-pack Batch from this required field.
Delivery From/Delivery To: Optionally, select the range of deliveries to be queried.
BOL From/BOL To: Optionally, select the range of bill of ladings to be queried.
Consignee: Optionally, select a customer or supplier. For an ISO return delivery, select a ship-to organization in this field..
Ship From/Ship To: Optionally, select a ship from and/or ship to address.
Pick-up Date From/Pick-up Date To: Optionally, select a pick up date range for the query.
Drop-off Date From/Drop-off Date To: Optionally, select a drop off date range for the query.
Firm Status: Optionally, select a status to query the deliveries.
Ship Method: Optionally, select a shipping method for the query.
Pick Release Batch: Optionally, select a pick release batch for the query.
Exceptions Only: Optionally, select whether you want to have only exceptions reported in this query.
Note: Warnings and error messages will only be displayed if the Shipping exception WSH_BATCH_MESSAGE is enabled. See: Oracle Shipping Execution Setup chapter of the Oracle Order Management Implementation Manual.
The Auto Ship Confirm Report is designed to provide visibility to batches that have been successfully ship confirmed by Auto Ship Confirm concurrent program.
Submission
In the Shipping Reports and Documents window, select Auto Ship Confirm Report in the Name field.
Note: This report is automatically generated as a result of ship confirmation.
Parameters
When you request a Auto Ship Confirm Report, Shipping Execution provides you with the following parameters:
Ship Confirm Batch: Select the Ship Confirm Batch from this required field.
Ship Confirm Rule: Optionally, select a Ship Confirm Rule.
Delivery From/Delivery To: Optionally, select the range of deliveries to be queried.
Bill of Lading From/Bill of Lading To: Optionally, select the range of bill of ladings to be queried.
Consignee: Optionally, select a customer or supplier. For an ISO return delivery, select a ship-to organization in this field.
Ship From Address/Ship To Address: Optionally, select a ship from and/or ship to address.
Pick-up Date From/Pick-up Date To: Optionally, select a pick up date range for the query.
Drop-off Date From/Drop-off Date To: Optionally, select a drop off date range for the query.
Firm Status: Optionally, select a status to query the deliveries.
Ship Method: Optionally, select a shipping method for the query.
Pick Release Batch: Optionally, select a pick release batch for the query.
Exceptions Only: Optionally, select whether you want to have only exceptions reported in this query.
Note: Warnings and error messages will only be displayed if the Shipping exception WSH_BATCH_MESSAGE is enabled. See: Oracle Shipping Execution Setup chapter of the Oracle Order Management Implementation Manual.
The Backorder Detail Report prints details about backordered items for your organization and displays the information based on the report parameters.
Submission
In the Shipping Reports and Documents window, select Backorder Detail Report in the Name field.
Parameters
When you request a Backorder Detail Report, Shipping Execution provides the following parameters for you to enter. If you leave any of the non-required parameters blank, this report includes all orders that meet your other parameter criteria.
Source System: Select the source system where the line has been imported to Shipping. This is a mandatory field.
Warehouse: Optionally, select the warehouse containing the backordered picking line items you want printed in this report.
Item: Optionally, select the item you want printed in this report.
Item Category Set: Optionally, select the item category set you want printed in this report. If you make a selection for this parameter, select a specific item category.
Item Category: Optionally, select the item category you want printed in this report. This field is available when Item Category Set is entered.
Customer: Optionally, select a customer name.
Source Header Type: Optionally, select an order source type. If this option is selected, Source Header Number From and To fields will become available.
Source Header Number From: Optionally, select the source header number (based on the Source Header Type option) that you want to report from.
Source Header Number To: Optionally, select the source header number (based on the Source Header Type option) that you want to report to.
Item Display: Select one of the following as the Item Display (mandatory):
Both: Print both item description and flexfield
Description: Print item description only
Flexfield: Print item flexfield only
Created By: Optionally, select the name of the person that created the delivery detail.
Ship To Country: Optionally, select the ship to country.
Sort By: Optionally, select one of the following to sort the report by:
Customer (default)
Order Number
Warehouse
The Backorder Summary Report prints a list of all unshipped orders and includes only open orders that include pick release. Multiple orders and their back ordered lines are displayed on the same page. It displays order information such as the order type, order numbers, warehouse, last shipped date, monetary value of items ordered, and the quantity of items outstanding and shipped. These amounts involve totals for shippable items only because the Backorder Summary Report does not account for non-shippable items.
Submission
In the Shipping Reports and Documents window, select Backorder Summary Report in the Name field.
Parameters
When you request a Backorder Summary Report, Shipping Execution provides you with the following parameters. If you leave any parameters blank, this report includes all unshipped orders that meet your other parameter criteria.
Transaction Type: Select the transaction type that you want printed.
Sales Order Number (Low/High): Select the order number(s) that you want printed in this report.
Note: You must select a transaction type before entering a sales order number(s).
Warehouse: Select the warehouse for which you want the report printed.
Item Display: Select Description, Flexfield, or Both depending on whether you want the item name, description, or both the item name and description to be printed in this report.
The Bill of Lading prints (on preprinted forms) all sales orders that have been confirmed from a selected delivery. This document lists the ship date, carrier, bill of lading number, delivery name, shipper, ship-to address, carrier name, waybill number, quantity and description of unpacked items, quantity and total of items packed in containers, total quantity of items, and weight/volume information defined in shipping. Any shipping notes you may have created are also printed.
XML Publisher Enabled
This report is XML Publisher enabled and can be printed in PDF. An XML Publisher enabled Shipping document enables the flexibility to define your own report layouts, include additional fields, and print the document in PDF format. See: XML Publisher Enabled Shipping Documents
Submission
In the Shipping Reports and Documents window, select Bill of Lading in the Name field. This report can also be executed from an Action list, a button (on the Shipping Transactions window, the Quick Ship window, or the Shipping Execution Simplified User Interface, for example), or could be included in a document set.
Parameters
When you request a Bill of Lading, Shipping Execution provides you with the following parameters. If you leave any of the non-required parameters blank, this document includes all picking lines that meet your other parameter criteria.
Warehouse: Select the warehouse for which you want the report printed.
Delivery Date (Low and High): Enter the range of delivery dates to be included in the shipping report.
Freight Carrier: Select the freight carrier you want printed in this shipping report.
Delivery Name: Select the delivery you want printed in this shipping report.
Trip Name: Select the trip you want printed in this shipping report.
Bill of Lading Number: Select the Bill of Lading Number you want printed in this shipping report.
Item Display: Select Description, Flexfield, or Both depending on whether you want the item name, description, or both the item name and description to be printed in this report under the Item column heading.
The Commercial Invoice Report lists all confirmed shipped items in a delivery. If you specify only a delivery name when defining the parameters of this report, Shipping Execution prints one commercial invoice per delivery within the trip.
This report lists ship date, commercial invoice ID (same as the delivery name), shipper/exporter, ship-to address, exporter identification number, freight carrier, all confirmed items within each delivery (including purchase order number, order number, quantity, unit of measure, unit value, and extended value for the items), total packages, total weight, and total value. Country of origin is for future use.
You can print order and line level notes on the commercial invoice. However, Shipping Execution maintains a two line maximum for notes at the header or footer to allow space for the fixed footer information that prints at the bottom of this report.
This report does not show tax or freight charges.
XML Publisher Enabled
This report is XML Publisher enabled and can be printed in PDF. An XML Publisher enabled Shipping document enables the flexibility to define your own report layouts, include additional fields, and print the document in PDF format. See: XML Publisher Enabled Shipping Documents
Submission
In the Shipping Reports and Documents window, select Commercial Invoice in the Name field.
Parameters
When you request a Commercial Invoice, Shipping Execution provides you with the following parameters. If you leave any of the non-required parameters blank, this document includes all picking lines that meet your other parameter criteria.
Trip Stop: Select the trip stop code.
Stop Planned Depart Date (Low and High): Enter the range of departure dates for the trip(s) and/or delivery(s) to be printed in this report. If you do not enter a value for this parameter, it is the equivalent of choosing all.
Freight Carrier: Select the freight carrier you want printed in this report.
Warehouse: Select the warehouse for which you want the report printed.
Delivery Name: Select the delivery.
Item Display: Select Description, Flexfield, or Both depending on whether you want the item name, description, or both the item name and description to be printed in this report.
Currency Code: Though you can select the currency code for the document, it is not considered in the report.
Print Customer Item: Select if you want customer item information included in the document.
Location to Region Mapping Concurrent Process processes locations (addresses) and submits a report of location data that cannot be matched to existing regions. Optionally, it can insert new region data into the regions interface table.
Submission
Navigate to the Shipping Interfaces form. If the process is not listed in the Name list of values, have your system administrator add it to the All Shipping Interfaces request group.
Parameters
Insert Flag: Yes
Number of Regions to Process: Enter a suitable number. The concurrent program processes the bulk information in this number of batches.
Location Start Date and Location End Dates: The concurrent process maps locations from the starting date to the ending date.
The Mailing Label Report consists of labels that print at document generation for identifying the ship-to address of the shipment. You can print mailing labels before Ship Confirm for LPNs since containers can be created without having to be associated to a Delivery. If delivery and trip information is available, it also appears on the mailing label, for example, customer name, ship to address, carrier name, waybill number, number of packages in the shipment, delivery number, container number, order number, and tracking number.
XML Publisher Enabled
This report is XML Publisher enabled and can be printed in PDF. An XML Publisher enabled Shipping document enables the flexibility to define your own report layouts, include additional fields, and print the document in PDF format. See: XML Publisher Enabled Shipping Documents
Submission
In the Shipping Reports and Documents window, select Mailing Label in the Name field.
Parameters
When you request a Mailing Label, Shipping Execution provides you with the following parameters. If you leave any of the non-required parameters blank, this report includes all customer addresses that meet your other parameter criteria.
Trip Stop: Select the trip stop for which you want labels printed.
Stop Planned Depart Date (Low and High): Enter the range of dates containing the delivery/deliveries for which labels are printed.
Freight Carrier: Select the freight carrier for the report you want to print.
Warehouse: Select the warehouse for the report.
Delivery Name: Select the delivery name for which you want labels printed.
LPN: Select the LPN for which you want labels printed.
The master bill of lading is a record of the physical bills of lading and prints the ship confirmed deliveries for a trip. It includes origin, final destination, stop off points, container description, and trailer weight.
The Master Bill of Lading report shows information when a trip has multiple deliveries from the origin.
XML Publisher Enabled
This report is XML Publisher enabled and can be printed in PDF. An XML Publisher enabled Shipping document enables the flexibility to define your own report layouts, include additional fields, and print the document in PDF format. See: XML Publisher Enabled Shipping Documents
Submission
In the Shipping Reports and Documents window, select Master Bill of Lading in the Name field
From the Shipping Transactions window, at the Trip tab, select Print Master BOL from the Actions menu
When ship confirming a trip, select the Create Master Bill of Lading check box
Within the Trip window, select the Action Print Master BOL
Within the Trips page, the Search Trips page, or the Trip page in the Shipping Execution Simplified User Interface, select the action Print Master BOL.
Parameters
Trip: Select the trip that you want printed in this shipping report. This field is required.
Print BOLs: Select Yes if you want the corresponding BOLs to be printed at the same time as the Master BOL. Otherwise, select No.
Use the Open Deliveries Report to view deliveries that you have not recorded as ship-confirmed or shipped.
Use it as:
A list of all deliveries that need processing and need ship-confirm
A list of the customer orders that the warehouse is processing
A list of pending orders that need processing at the end of a fiscal period to recognize revenue
A list of deliveries with assigned lines that you need to lock in (status Firm)
A list of deliveries that you may need to close
Submission
In the Shipping Reports and Documents window, select Open Deliveries Report in the Name field.
Parameters
Batch Name: A picking batch.
Consignee: The customer's or supplier's name for whom you are running the report. For an ISO return delivery, enter a ship-to organization in this field.
Creation Date(Low) and Creation Date(High): Enter only a range of dates. The report shows deliveries from 00:00:00 of the from date to 23:59:59 of the to date.
Item Display is required:
Description: The report shows the item descriptions. This is the default.
Flexfields: The report shows the item flexfield data. Some information may appear truncated.
Both: The report shows the item descriptions and the item flexfield data. Some flexfield information may appear truncated.
Warehouse (required): If a value initially appears, it is from the PO: MFG Organization ID profile option.
Ship Method: The ship method used.
Ship To: The ship to address.
Sort Order is required:
Batchname, Delivery: Batch Name ascending/descending; within Delivery, Source Ref. Number ascending.
Creation Date, Delivery: Creation Date ascending/descending; within Delivery, Source Ref. Number ascending.
Delivery: Delivery ascending; within Delivery, Source Ref. Number ascending.
Ship Method, Delivery: Ship Method ascending/descending; within Delivery, Source Ref. Number ascending.
Shipment Priority, Delivery: Shipment Priority ascending/descending; within Delivery, Source Ref. Number ascending.
The Global Packing Slip Report lists the goods that are in transit and is used to show that the goods do not belong to the carrier. The goods transported can be from sales orders, internal sales orders or transfers, project contract lines, and return order lines for return to vendor or ISO return transactions. In some countries, the packing slip is optional while in others, it is required.
The Packing Slip Report prints the following information: the customer's name with both the ship-to and bill-to addresses, ship date, sublot, freight and payment terms, order date, cumulative quantity, and salesperson. Also included are the waybill number, freight type, freight weight, FOB point, freight carrier, and unit of measure.
Note: Set the profile option RLM: Print Cum Data on Shipping Documents to Yes to print the cumulative quantity (CUM Qty field) on the packing slip.
The Packing Slip lists each ordered item including the line level ship-to contact or order level contact, the purchase order number, the unit of measure, the quantities ordered, shipped, and backordered.
The Packing Slip layout and format contain the following:
The contact names are included.
The back ordered quantity is included as part of the Total Unshipped Quantity and appears separately in the Unshipped Quantity column.
You can choose to display or not display the Unshipped Details in the Packing Slip Report by selecting Yes or No in the Display Unshipped Items field in the set-up parameters for this report.
Shipping and packing instructions entered for an order line display on the report.
Country names appear in the last line of the address: Ship From address, Ship to address and Bill To addresses.
Note: If a move order line has been purged and you attempt to print the associated packing slip, then a message No Data Found will be displayed.
For internal sales orders, Shipping Execution defaults the internal sales order number and requestor name to the Packing Instructions column.
Note: The Packing Slip Report cannot be printed from a third-party warehouse instance. The Packing Slip Report requires Bill to Location information that is stored in Order Management Order Lines and not in Shipping Delivery Details. This information cannot be transmitted from the supplier instance to the third party instance.
XML Publisher Enabled
This report is XML Publisher enabled and can be printed in PDF. An XML Publisher enabled Shipping document enables the flexibility to define your own report layouts, include additional fields, and print the document in PDF format. See: XML Publisher Enabled Shipping Documents. Use the Packing Slip Report (XML) to view information about the ISO return transactions.
Submission
In the Shipping Reports and Documents window, select Packing Slip Report in the Name field.
Parameters
When you request a Packing Slip Report, Oracle Shipping Execution provides you with the following parameters. If you leave any of the non-required parameters blank, this report includes all picking lines that meet your other parameter criteria.
Warehouse: Select the warehouse for the report.
Delivery Name: Select the name of the delivery for which you want to run the report.
Print Customer Item: Select if you want the customer item names printed on the report.
Item Display: Select Description, Flexfield, or Both depending on whether you want the item name, description, or both the item name and description to be printed in this report under the Item column heading.
Print Mode: Select if you want to print a draft or final version of the Packing Slip Report.
Print All Option: Select if you want to print separate packing slips (a report for each container), a single consolidated packing slip (for all containers), or both separate and consolidated packing slips.
Sort by: The information on the packing slip is first sorted by Header ID. Within the Header ID, you can specify to sort by inventory item number or customer item number.
Delivery Date (Low and High): Enter the range of dates for the trip(s)/delivery(s) to be included in your report.
Display Unshipped Items: Select if you want to list unshipped items on the packing slip.
The Pick Slip Report prints all picking line details in a picking batch. This report is used by warehouse personnel to collect all items included in shipments.
The pick slip displays the following sections:
Pick slip header: Lists report date, warehouse, pick slip number, and pick batch number.
Release criteria: Lists pick slip grouping rule name and criteria used in grouping the pick slip such as customer, ship-to address, delivery name, trip stop address, order number, shipment priority, carrier, subinventory, and requisition number.
Note: The criteria defined on the selected pick slip grouping rule displays on the pick slip. For example, customer name and carrier display on the pick slip if the pick slip grouping rule with this criteria is selected for pick release.
Pick slip list: The Pick Slip lists each item as well as the line number, unit of measure, quantity requested, quantity shipped, sales order number, sales order line, ship set, trip, delivery, task id, lot number, serial number from, serial number to, revision, pick from location, and whether the item is required for shipment. The requested quantity shows the total quantity.
This report also lists each sales order, including customer name, shipping address, order number and order date, purchase order number, freight and payment terms, and salesperson associated with the items. Also included are the pick slip number, FOB point, planned freight carrier, requisition number, requestor.
The Pick Slip displays separately the quantity of items picked from various lots: the Transaction Quantity from each lot displays separately under Quantity.
Shipping notes: Lists any associated shipping notes.
XML Publisher Enabled
This report is XML Publisher enabled and can be printed in PDF. An XML Publisher enabled Shipping document enables the flexibility to define your own report layouts, include additional fields, and print the document in PDF format. See: XML Publisher Enabled Shipping Documents
Submission
The Pick Slip report is a pick release document that prints as a result of the pick release process.
Parameters
When you request a Pick Slip Report, Shipping Execution provides you with the following parameters:
Pick Slip Number (Low/High): Select the range of pick slip numbers to be included on the report.
Sales Order Type: Select the sales order type to be included in the report.
Sales Order Number (Low/High): Select the range of sales order numbers to be included on the report.
Move Order Number (Low/High): Select the range of move order numbers to be included on the report.
Freight Carrier: Select the freight carrier for the report you want printed.
Warehouse: Select the warehouse for which you want the report printed.
Customer: Select the customer for which you want the pick slip number printed.
Line Status: Select the status of the delivery lines: All, Picked, or Un-picked.
Detailing Date (Low/High): Enter a date range that for the detailed lines.
Item Display: Select an item display: Description, Flexfield, or Both.
Note: The document set named Pick Slip Report can be used to print this report automatically during the pick release process. The Shipping Parameter for Print Pick Slip determines when to initiate printing. If the parameter is set to Immediate, then the program looks at the parameter for Number of Pick Slip Lines to determine the number lines to process before printing begins. The pick slip will then immediately print after the system finds for pick release the number of pick slip lines specified by the Number of Pick Slip Lines parameter and include that number of lines on the pick slip. The pick release process will continue, then print the next pick slip when that number of lines is again identified. For example, if the Print Pick Slip parameter is set to Immediate and the Number of Pick Slip Lines is set at 20, then when the pick release process is initiated, a pick slip report will be generated immediately after the system finds 20 lines for release. This setup enables warehouse personnel to begin picking the first 20 lines without having to wait until the system completes the full pick release.
Note: If the Print Pick Slip parameter is set to At the End, then the pick slip report will be generated when the system completes the review of all eligible lines for pick release. The Shipping Parameter for Number of Pick Slip Lines is ignored if the Pick Slip Report parameter is set to At the End.
Note: The most common method of submitting the Pick Slip Report is to enable it through the seeded document set for Pick Slip Report. If you choose to enable the report in the seeded document set, then you should not submit it as a standard document set. If the Pick Slip Report is submitted in the seeded document set and in a standard document set, then duplicate copies of the report will be printed. The seeded document set should not include any report except for the Pick Slip Report, otherwise the report will be ignored.
Use the Shipped Delivery Lines report to display all delivery lines that have been shipped. This report includes each shipped delivery line that satisfies your parameter criteria. With this report you can also print totals for the released and shipped quantities and the number of delivery lines that meet your parameter criteria.
Use the Shipped Delivery Lines Report (XML) to view information about the ISO return transactions.
The report will generate a released number that is greater than the shipped number in order to compare released versus shipped quantities. This typically occurs when an order has been partially backordered. For example, you have order number 590221 for 10 each of item AS33490. If a backorder of 6 occurs, then the Shipped Delivery Lines Report will display the following:
Order 590221
Line 1.1 quantity released 10 quantity shipped 4
Line 1.2 quantity released 10 quantity shipped 6
Total: Released 20 Shipped 10
Using this report, you can print information relative to all the delivery lines that have passed the ship confirm process (status: Interfaced) like order number, released, and shipped quantity, and so on. Delivery lines are selected based on the parameters used to generate the report.
You can use this report in several ways, including the following:
A management report at the month end and quarter end for Accounts Receivables to assure that all shipments had completed and Auto Invoiced.
As a tool to identify possible re-calls or to identify the customers that a particular item has been sent to.
A management report by distribution management to compare the items that were released and shipped for a particular time period. It helps in determining picking and shipping performance metrics.
Submission
Submission parameters are displayed on the cover page and critical parameters are repeated on the other pages. The report has two breaks by level, including the following: Operating Unit and Ship From Organization. There is a page break at each new Operating Unit and Ship From organization. Within each, delivery lines appear as a list and the change of page is made when the maximum possible lines per page are reached.
Parameters
Ship From Organization: This required parameter indicates the ship from organization on the delivery lines that are selected for printing.
Source System: Select the delivery lines to be printed based on a particular source system. Select Returns to enable the Consignee Type parameter.
Source Type: Select a Source Type if you selected a Source System.
Source Number From/Source Number To: You can specify a Source Number From and a Source Number To if you selected a Source Type.
Delivery From/Delivery To: Optionally, select delivery lines to be printed based on a range of deliveries.
Item: Optionally, select the Item to be reported.
Item Display: This required parameter indicates how to print the item related information on the report. The possible values are:
Item Description: Print the item description only.
Item FlexField: Print the item flexfield only.
Both: Print the item description and flexfield.
Customer From/Customer To: Optionally, select delivery lines to be printed based on a range of customers or suppliers.
Ship Date From/Ship Date To: Optionally, select the range of shipping dates on delivery lines that are printed.
Ship method: Optionally, select delivery lines to be printed based on a particular ship method.
Sort By 1, Sort By 2, Sort By 3: You can sort this report based on three sorting criteria. Possible sorting criteria include the following:
Customer name
Delivery
Item
Ship Date
Ship Method
Note: The Operating Unit and Ship From Organization are major criteria of sorting. For example, if you select Sort By 1 = Customer, Sort By 2 = Ship Date, and Sort By 3 = Delivery, then the report will be sorted by Operating Unit, Ship From Organization, then Customers, By Ship Date within the Customers, and finally by Delivery within the Ship Dates.
The Shipping Exceptions Report provides all the exception details from Shipping Execution.
For more information on defining shipping exceptions, see Shipping Execution Setup, Defining Shipping Exceptions in Oracle Order Management Implementation Manual.
Submission
You can print this report by running it through either SRS or during Pick Release processing.
Parameters
When you request a Shipping Exceptions Report, Shipping Execution provides you with the following parameters:
Exception Name: Identifies the exception encountered in processing.
Request ID: Identifies the exception request.
Logging Entity: Displays exceptions for a selected log-on entity: shipper, receiver, or transportation carrier.
Exception Location Name: Identifies the location where the shipping exception occurred.
Ship From Location Name: Identifies the location where the exception report was run (logged location may be different from where the shipping exception occurred).
Creation Date Low/High: Identifies the range of creation dates for exceptions in the report.
Last Update Date Low/High: Identifies the range of update dates for exceptions in the report.
Severity:
Information Only: To query shipping entities with exceptions that are provided as information only and do not require resolution.
Warning: To query shipping entities with exceptions that cause a warning.
Error: To query shipping entities with exceptions that cause an error.
Status: Describes the current status of the exception:
Open: To query shipping entities with exceptions that have not been resolved.
Closed: To query shipping entities with exceptions that have been resolved.
No Action Required: No handling required for this exception.
Trip From/To: Identifies the range of trip IDs included in the report.
Delivery From/To: Identifies the range of delivery IDs in the report.
Move Order Number High/Low: Defines the move order number(s) for the report.
Sort By: Defines how the report will be sorted.
The Vehicle Load Details report prints the loading sequence of items within a delivery. The report header includes the following: name of the report, the date the report is created, trip number, vehicle type, vehicle number, carrier, trip status, prior trip, and instructions.
This report prints the following information for the delivery: stop information for the delivery, planned arrival and departure date, consignee, delivery name, loading sequence number for the delivery, gross weight and net weight of the delivery, waybill number, customer production line to which the delivery is to be shipped, and final ship-to destination. This report also prints the following delivery line information for the delivery: master or detail container name, loading sequence, production sequence, customer sequence number, customer job number, item number, and item description.
Submission
In the Shipping Reports and Documents window, select Vehicle Load Sheet Details in the Name field.
Parameters
When you request a Vehicle Load Sheet Details Report, Shipping Execution, you are required to select the Trip to be printed.
The Vehicle Load Sheet Summary Report prints a list of all deliveries assigned to a specific trip. This report prints the following header information: report name, report date, and trip number.
This report contains the following trip information: trip date, initial ship from date, whether the trip follows another trip, freight carrier, vehicle type, and vehicle number.
The report contains the following delivery information within the trip: order in which the deliveries are to be loaded in the trip (load sequence), delivery name, gross weight and net weight of each delivery, waybill number, and customer name.
XML Publisher Enabled
This report is XML Publisher enabled and can be printed in PDF. An XML Publisher enabled Shipping document enables the flexibility to define your own report layouts, include additional fields, and print the document in PDF format. See: XML Publisher Enabled Shipping Documents
Submission
In the Shipping Reports and Documents window, select Vehicle Load Sheet Summary in the Name field.
Parameters
When you request a Vehicle Load Sheet Summary, Shipping Execution provides you with the following parameter:
Trip: Select the trip to be printed in this document.
The Interface Trip Stop-SRS process runs the interface to initiate Oracle Order Management and Oracle Inventory interfaces as well as initiate the process for generating Departure Ship Notice Outbound (DSNO). This functionality is detailed within the topic Interface Trip Stop-SRS.
The International Trade Management (ITM) reports and processes enable you to submit transactions to the ITM Adapter. The ITM Adapter then communicates the transactions to the partner ITM application. See: International Trade Management topic in the Oracle Shipping Execution Setup chapter of the Oracle Order Management Implementation Manual.
If your current responsibility does not enable you to navigate to International Trade Management Reports and Processes, change responsibility to ITM Adapter Super User responsibility.
Oracle Shipping Execution provides you with various processes, including:
If your business process requires manifesting a significant volume of deliveries, then you can use the Automated Carrier Manifesting concurrent program to complete this task systematically. This program searches for open deliveries with assigned lines that are staged and packed then it sends the Shipment Request automatically. Additionally, if the concurrent program parameter for autopack is set to Yes, then this program searches for open deliveries with staged lines regardless of whether they are packed. Packing is systemically performed prior to manifesting since only packed delivery lines can be manifested.
Submission
Navigate to the Shipping Interfaces window and, after verifying the correctness of the parameters data, click Submit.
Parameters
Organization: Select your organization.
Carrier: Optionally, select a carrier.
Customer: Optionally, select a customer.
Customer Ship To: Optionally, enter a customer ship to address
Scheduled From and To Dates: Optionally, enter a range of scheduled ship dates.
Note: A delivery can have multiple scheduled ship dates. If one of the delivery lines has a scheduled ship date within the range that you specify, then the entire delivery will be extracted.
AutoPack: Select either Yes or No to determine whether autopacking should execute with your process.
If you select Yes, then unpacked lines that are staged and assigned to an open delivery will be packed and submitted for manifesting. A prerequisite for automated packing is that a container-item relationship must exist for any item considered during this process.
Log Level: Enter 1 to turn debugging on and 0 to turn debugging off.
The Create Batches for Transportation Planning concurrent program groups delivery details for the selected parameters into a transportation batch and subbatches. A transportation batch can contain delivery details from multiple sales orders or from a Oracle Warehouse Management wave. The subbatches are created based on the Ship-From and Ship-To locations of the sales order lines. If you select Cancel Unshipped Lines check box in the sales order header, then different subbatches are created for each sales order.
The following batch group attributes are mandatory:
Ship-From Location
Ship-To Location
The following batch group attributes are optional:
Customer
Freight Terms
FOB Code
Ship Method
Transportation sub-batches are sent to OTM for transportation planning. A transportation sub-batch name is equivalent to an order release in OTM. Using the order release, OTM can plan and create single or multiple shipments that are then sent back to Oracle Shipping Execution to create trips.
When entering the parameters for the Create Batches for Transportation Planning concurrent program, you can select whether you want the concurrent program to send the transportation batch immediately to OTM after the batch is created or if you want to send the batch at a later date. If you set the Submit Outbound Request parameter to Yes, the system automatically runs the Shipping-Transportation Outbound Interface concurrent program after the transportation batch is created. If you select No, you must manually run or have the system periodically run the Shipping-Transportation Outbound Interface concurrent program.
Submission
Navigate to the Shipping Interfaces window.
In the Name field, select Create Batches for Transportation Planning.
Enter the parameters.
Click OK.
Click Submit.
Parameters
Enter values in the following parameters:
Source System: Select a source system.
Organization: (Optional) Select the organization.
Wave: Optionally, select the Oracle Warehouse Management wave.
If you select a wave, the other parameters become unavailable for entry.
Consignee Type: (Optional) Select Internal or Vendor.
Consignee/Customer: (Optional) Select a customer or supplier. For an ISO return delivery line, select a ship-to organization.
Ship To Location: (Optional) Select a consignee's or customer's ship-to address.
Source Header Type: (Optional) Select the source header type.
Source Header Number (Low/High): (Optional) Select the range of source header numbers.
Request Date (Low/High): (Optional) Select the range of request dates.
Schedule Date (Low/High): (Optional) Select the range of schedule dates.
Shipment Priority: (Optional) Select the shipment priority.
Line Status: (Optional) Select the line status.
Submit Outbound Request: Select Yes to have the system automatically run the Shipping-Transportation Outbound Interface concurrent program after the batch is successfully created. Select No if you do not want the system to run the Shipping-Transportation Outbound Interface concurrent program. Yes is the default.
Log Level: Select 1 to turn debugging on and 0 to turn debugging off.
Output File
After the concurrent program completes successfully, you can view the transportation batch number and the sub-batches created through the output file.
To view the output file:
Navigate to the Requests window.
Select the Request ID associated with the Create Batches for Transportation Planning concurrent program.
Click View Output.
Create Shipment Batches for Fulfillment concurrent program groups eligible delivery lines for the selected parameters into shipment batches based on grouping criteria.
The following grouping criteria are mandatory:
Customer
Ship From Organization
ShipTo Site
Operating Unit
Currency Code
The following grouping criteria are optional:
InvoiceTo Site
DeliverTo Site
ShipTo Contact
InvoiceTo Contact
DeliverTo Contact
Ship Method
Freight Terms
FOB Code
Within Order
Submission
Navigate to the Create Shipment Batches for Fulfillment window and enter the necessary parameters. Click Submit.
Parameters
Enter applicable values for the following parameters:
Organization: Select your organization.
Consignee/Customer: Optionally, select a customer.
ShipTo Location: Optionally, enter a customer ship to address.
Sales Order Type: Optionally, select the sales order type.
Sales Order Number (Low/High): Optionally, select the range of sales order numbers.
Request Date (Low/High): Optionally, select the range of request dates.
Schedule Date (Low/High): Optionally, select the range of schedule dates.
Shipment Priority: Optionally, select the shipment priority.
Include Internal Sales Orders: To include internal sales orders while creating shipment batch.
Log Level: Enter 1 to turn debugging on and 0 to turn debugging off.
Note: This concurrent program creates shipment batches even if the delivery detail's organization is not set up as 'Distributed Organization' in Organization Parameters window, ATP, Pick, Item Sourcing tabbed region.
This program imports location data into shipping. You must run the program in one of the following conditions:
You create new regions.
You create new locations and you are not using the trading community architecture (TCA) business events that automatically propogate location changes to shipping.
If you encounter issues with new locations that are not being mapped to regions.
Submission
Navigate to the Import Shipping Locations program and enter the necessary parameters. Click Submit.
Parameters
Map Regions: Set to Yes to enable all the available-to-promise transit time calculations.
This is an optional program. You do not need to run this program if you have an alternative source of region data that you can enter using the interface table or the Regions and Zones window.
This program, which is typically run only once, examines all the existing location data, and lists any regions you require in the Regions Interface table. Review the suggested regions using the Regions Interface window, and correct errors present from the original location information. After you are satisfied that the entries are correct, you can run the Region Interface program (WSHRGINT).
Submission
Navigate to the Location to Region Mapping program and enter the necessary parameters. Click Submit.
Use this process to run a specific release at the same time every day. SRS runs pick release in the background and the program can be run multiple times daily. This concurrent process is also called Pick Selection List Generation – SRS.
Submission
Navigate to the Pick Release window and enter the necessary parameters. Click Submit.
Parameters
Operating Unit: Select an operating unit.
Organization: Select your organization.
Release Rule Name: Enter the release rule to be used for this pick release.
Batch Prefix: Enter a prefix for the pick release batch.
Debug Level: 0 is Off, 1 is On.
Actual Departure Date: Enter the actual date that the shipment departed, if the defaulted date is incorrect.
Actual Departure Date is only applicable when the Release Rule that is specified in the SRS Parameter window contains a Ship Confirm Rule. If it does not, then the Actual Departure Date is ignored.
When lines being pick released are also being auto ship confirmed, the actual day of shipping might be one or two days from now. In that case, you can enter the Actual Departure Date for two days from now even though the ship confirm runs automatically today.
Number of Child Processes: Enter the number of pick release processes that you want to run in parallel, which increases the speed of the process run time by spreading the load to multiple processors. The default number of child processes is based on the profile option WSH: Number of Pick Release Child Processes, which has no default. Changing the profile option changes the default to that number of child processes. IF no value is entered in this profile option, then pick release submits a single process.
Related Topics
The Planned Shipment Interface concurrent program picks up the shipments that were created in Oracle Transportation Management and places them in Oracle Shipping Execution. You can automatically run the Planned Shipment Interface request every time a planned shipment is received from Oracle Transportation Management. However, for situations that may result in too many Planned Shipment Interface concurrent requests being run simultaneously, you may want to run this request either manually or on a scheduled interval. Several concurrent requests running at the same time may reduce system performance.
The Defer Planned Shipment Interface check box on the Global Parameters window (General tab) controls the default setting for running the Planned Shipment Interface concurrent program. Select this check box if you want to run the program manually (or to schedule it), or clear this check box if you want to run the request automatically every time the planned shipment is received from Oracle Transportation Management.
For multi-leg shipments, the Planned Shipment Interface concurrent program does the following:
Creates multi-leg trips in EBS
Creates or assigns delivery to multi-leg trips
Assigns freight cost information at the trip level
Processes trip updates that are already received in EBS
Submission
Navigate to the Shipping Interfaces window.
Select Planned Shipment Interface in the Name field.
Enter the parameters and click OK.
Click Submit.
Parameters
Process Latest Version Only: Determines whether the latest version of the deliveries or transportation batches must be selected for processing. The default value is Yes.
Yes: Processes all deliveries or transportation batches for a trip (even if only one delivery is to be processed in the list of parameters).
No: The concurrent request processes the earlier versions of the deliveries or transportation batches (the current status of the delivery or transportation batch in the E-Business Suite should be in Open status waiting for an Update status from Oracle Transportation Management).
Note: The incoming trip can have deliveries or transportation batches (releases) belonging to one or more organizations.
Interface Basis: This field appears by default from the selection you made in the WSH: Delivery Based OTM Integration profile option. Delivery is displayed for delivery based integration and Batch is displayed for batch based integration.
Transportation Plan Name (Low/High): The range of transportation plan names
Client: The client name if you have set logistics service provider (LSP) mode as the value for profile option WMS: Deployment Mode. See Oracle Inventory User's Guide for setting up client.
Organization: The OTM-enabled inventory organization
Delivery Name (Low/High): The range of delivery names
Delivery Pick Up Date (Low/High): The range of delivery pick-up dates
Transportation Batch Name (Low/High): The range of transportation batches to be submitted. These fields are not available if the Interface Basis parameter is set to Delivery.
Transportation Batch Creation Date (Low/High): The range of transportation batch creation dates to be submitted. These fields are not available if the Interface Basis parameter is set to Delivery.
Use this process to append deliveries and/or autocreate deliveries with unassigned delivery lines or to auto create trips with delivery groups according to the grouping parameters and compatibility constraints.
This process can be limited in the execution of the request to particular delivery lines status, delivery status, date ranges, ship method or customer.
This program is applicable only to outbound delivery lines and deliveries.
Note: Process Deliveries concurrent program does not support ship set enforcement.
Submission
Navigate to the Process Deliveries SRS window and enter the necessary parameters. Click Submit.
Note: If you click Cancel within the Parameters window, then you must also click Cancel within the Process Deliveries Concurrent Program window. Otherwise, the process will run using the default parameters.
Parameters
Processed Entities: Choose either Deliveries Only or Delivery Lines Only
Delivery Lines Status: Indicate what status of unassigned delivery lines will be processed by the concurrent request.
Deliveries Status: Indicate what delivery status will be processed by the concurrent request.
Delivery Lines, Scheduled Ship Date Start: Enter a starting scheduled ship date
Delivery Lines, Scheduled Ship Date End: Enter an ending scheduled ship date
Delivery Lines, Source System: Indicate what type of source system is considered in the process
Delivery Lines, Direction: Select the type of sales order. You can select Inbound, Outbound, or Both.
Deliveries, Pick Up Date Start: Enter a starting pick up date
Deliveries, Pick Up Date End: Enter an ending pick up date
Deliveries, Drop Off Date Start: Enter a starting drop off date
Deliveries, Drop Off Date End: Enter an ending drop off date
Client: Select the client name from the list if you have set LSP mode as the value for WMS: Deployment Mode profile option. See Oracle Inventory User's Guide for setting up client.
Ship From Organization: Choose the Organization
Customer: Choose the customer name, supplier name, or organization
Ship to Location: Enter the ship to location
Ship Method: Enter a ship method
Auto Create Deliveries: Yes or No
Auto Create Delivery Criteria: Select a criteria
Append Deliveries: Yes or No (Appending Limit in the Shipping Parameters window must be anything other than Do Not Append, the Delivery Line Status parameter must be Ready to Release or Released to Warehouse, the Delivery Lines and Source System parameters must be Order Management, the Ship From Organization parameter must be specified, the Auto Create Delivery parameter must be Yes, and the Auto Create Delivery Criteria parameter must be Across Orders.)
Group Deliveries by Ship Method: Yes or No
Group Deliveries by Ship From: Yes or No
Max Number of Deliveries per Trip: Enter the maximum number of deliveries for the trip
Log Level: Enter 1 to turn debugging on and 0 to turn debugging off.
The Process Move Order for Backordered Materials concurrent program allocates or transacts the move orders that are created when a delivery or a trip is backordered or when delivery details are backordered during ship confirm. This program transfers the backordered material from the staging inventory to the source subinventory. However, for WMS-enabled organizations, the location to which the backordered material is transferred is determined by the rules setup.
In the Shipping Transaction tab of the Shipping Parameters window, select a value for the Automate Backorder Move list. For WMS-enabled organizations, the possible values are Auto Allocate and None. For organizations that are not WMS enabled, the possible values are Auto Allocate, Auto Transact, and None. Move orders are allocated or transacted by the concurrent program Process Move Order for Backordered Materials. If you select None or Null, the system does not create move orders for backordering the material.
This program is triggered automatically during a delivery or trip confirm when at least one of the details is backordered. If an issue arises during the automated processing of move orders, you can submit this program manually for the affected move orders.
Submission
In the Shipping Interfaces window, navigate to the concurrent program Process Move Order for Backordered Materials and enter the necessary parameters. Click Submit.
Parameters
Warehouse: Select the warehouse from which the material needs to be backordered. By default, the parameter value is the manufacturing organization for the responsibility with which you have logged in to the application. If you do not select a value for this parameter, all eligible organizations are processed.
Move Order Num From or To: Select a range of move order numbers for processing.
The Process Shipment Advices concurrent program validates shipment advice interface data, creates, and ship confirms the delivery.
Submission
Navigate to the Process Shipment Advices window and enter the necessary parameters. Click Submit.The concurrent program first checks the Defer Interface check box. In the Global Parameters window, if you select the Defer Interface check box, the program Process Shipment Advices initiates the program Interface Trip Stop at the end of ship confirm.
Parameters
Shipment Advice Status: Select it from list "AP" is Awaiting Processing, "ER" is Error.
Shipment Advice Number Low/High: Optionally, select the range of shipment request document numbers.
Shipment Advice Creation Date Low/High: Optionally, select the range of shipment advice creation date.
Debug Level: Enter 1 to turn debugging on and 0 to turn debugging off.
Note: This process validates customer number if it is populated; else the process validates the customer name. If both the values are populated, then the process validates only the customer number.
This program processes shipment request data from the Shipping Interface tables. Use this shipment request process to create, update, or cancel shipment request lines in Oracle Warehouse Management System instance with deployment as Distributed mode or LSP mode (set as the value of WMS: Deployment Mode profile option) based on data populated in the Shipping interface tables.
Submission
Navigate to the Process Shipment Requests window and enter the necessary parameters. Click Submit.
Parameters
Enter applicable values for the following parameters:
Shipment Request Status: Use the list of values to select either AP (Awaiting Processing) or ER (Error) to process respective requests.
Client: Select the client name from the list if you have set LSP mode as the value for WMS: Deployment Mode profile option. See Oracle Inventory User's Guide for setting up client.
Shipment Request Number Low/Shipment Request Number High: Optionally, select the range of Shipment Request Numbers to be processed.
Shipment Request Creation Date Low/Shipment Request Creation Date Low: Optionally, select a Shipment Request Creation Date range for which SRs are to be processed.
Debug level: Enter 1 to turn debugging on and 0 to turn debugging off.
Note: This process validates customer number if it is populated; else the process validates the customer name. If both the values are populated, then the process validates only the customer number.
Use this process to load bulk geographical information from the regions interface table to Oracle Shipping Execution. This enables you to filter the data that you are loading so that you can repeat the process without loading all of the geographical information each time. The filters are country, country code, province/state, city, city code, and postal code.
Submission
Navigate to the Regions Interface window and, after verifying the correctness of the data, click Load All Regions. If the process does not start, have your system administrator add it to the All Shipping Interfaces request group.
Parameters
None
Ship Confirm Deliveries SRS enables you to utilize the Auto Ship Confirm functionality within Oracle Shipping Execution. This functionality is detailed within the topic Executing the Auto Ship Confirm Process Concurrently .
Shipping Purge concurrent process is used to review records that could be purged (based on prerequisite criteria, such as an open delivery), report on (by printing) records that would be candidates for purge, or both purge and report the records that have been purged. Entities that can be purged are trips, trip stops, deliveries, delivery details (lines), and LPNs/containers.
The following is a list of exceptions to purging Shipping Execution entities:
Shipping Execution entities generated through Oracle Project Contracts cannot be purged.
Any Shipping Execution entity that is tied to an Oracle Purchase order can only be purged after the purchase order is purged.
Oracle Order Management generated Shipping Execution entities can only be purged if the order has been purged and no freight charges are open.
In a WMS Enabled organization, delivery information cannot be purged until verification exists that there are no activities on Oracle Warehouse Management LPNs.
Submission
Select Shipping > Purge SRS from the Navigator window. The Shipping Purge Parameters window opens automatically. Enter your data into the parameters and click OK.
Parameters
Execution Mode: Use the list of values to select either of the following:
Purge: The Oracle Shipping Execution data is purged based on the information you provide in the remaining parameters. A report is then generated detailing the data that has been purged.
View Purge Selection: The data is not purged. View Purge Selection generates a report, based on the information you provide in the remaining parameters, of data that is eligible for purge.
Source System: Select the source system from which you want to select the entities to be purged:
All: Eligible shipping data will be purged from all sources.
Order Management: Only eligible Order Management shipping data will be purged.
Purchasing: Only eligible Purchasing shipping data will be purged.
Returns: Only eligible shipping data for Return transactions will be purged.
Shipping: Only eligible Shipping Execution shipping data will be purged.
Ship From Org: Use the list of values to select the organization of the entities to be purged.
Order Number From/To: Use the list of values to select a range of order numbers containing entities to be purged.
Order Type: Use the list of values to select the order type containing entities to be purged.
Ship Date From/To: Enter a range of dates containing entities to be purged. The Ship Date refers to the initial pick up date on the delivery.
Delete Beyond X Ship Days: Enter the number of ship days beyond which data is to be purged. For example, delete all Shipping data that is 90 ship days or older.
Purge "In Transit" Trips: Yes or No. If Yes, then trips that are In Transit are purged. If No, then they are not purged.
Delete Empty Records: Yes or No. If Yes, then empty records (for instance, deliveries with no data or LPNs with no data) are purged. If No, then empty records are not purged.
Creation Date From/To: Use the list of values to select a creation date range containing entities to be purged. This parameter is used only when the Delete Empty Records parameter is set to Yes.
Delete Beyond X Creation Days: Enter the number of creation days beyond which data is to be purged. For example, delete all empty deliveries that were created more than 120 days ago. This parameter is used only when the Delete Empty Records parameter is set to Yes.
Sort Per Criteria: Select the sorting criteria for the report. Select from the following:
Delivery: The report is sorted by delivery number
Order: The report is sorted by order number
Trip: The report is sorted by trip number
Print Detail: Select the detail of the report. Select from the following:
Detail: The report is printed with a summary page and detailed pages for deliveries, trips, and orders to be purged or that have been purged.
Detail with LPN: The report is printed with a summary page and detailed pages, including LPN information, for deliveries, trips, and orders to be purged or that have been purged.
Summary: The report is printed as a summary
Carriers and carrier sites are defined in Oracle Shipping Execution. However, the implementation of Oracle Transportation Management includes changes to the Carrier form. The following changes are part of the integration of Oracle Transportation Management:
When Oracle Transportation Management is not installed, all fields on the Rating, Payment tab are disabled with the exception of the Enable Manifesting field.
When Oracle Transportation Management is installed, all fields on the Rating, Payment tab are disabled with the exception of the fields in the Freight Payment and Audit region (that is, the Supplier and Default Supplier Site fields).
When Oracle Transportation Management is installed, the Mode Limits tab is disabled.
When Oracle Transportation Management is installed, the Mode Limits tab, within the Services tab is disabled.
When Oracle Transportation Management is installed, the Transportation tab within the Addresses/Sites tab is disabled with the exception of the Supplier Site field.
The Shipping - Transportation Carriers Synchronization concurrent program enables Oracle E-Business Suite to communicate carrier and carrier site information to Oracle Transportation Management through the Location XML transaction. The carrier and carrier site information from the Oracle E-Business Suite tables and columns is interfaced to Oracle Transportation Management tables and columns through the concurrent program.
During the implementation of Oracle Transportation Management, the Shipping - Transportation Carriers Synchronization concurrent program is run to move all carrier and carrier site data from the Oracle E-Business Suite tables and columns to the Oracle Transportation Management tables and columns. After the implementation is complete, the concurrent program can be run whenever a Carrier or Carrier Site is updated or new Carriers and Carrier Sites are created.
BPEL is used to control the flow of data sent by the concurrent program.
Interface Parameters
The Shipping-Transportation Carriers Synchronization concurrent program is submitted from the Interfaces menu. The program includes the following parameters:
Carrier Name From: Carrier name range low.
Carrier Name To: Carrier name range high.
Last Date Update From: If left blank, then the program will apply to all carriers within the restrictions of the other parameters defined.
Last Date Update To: If left blank, then the program will apply to all carriers within the restrictions of the other parameters defined.
Transferred Carrier Data
The following table details all carrier data, whether EBS or OTM owns the data, and details how (if at all) the data is transferred from one to the other.
| EBS Entity | OTM Entity | Owner | Transfer Data Method |
|---|---|---|---|
| Vehicle Types | Equipment Types / Groups | OTM | None |
| Carrier Commitments | Carrier Commitments | OTM | None |
| Vehicle Availability | Carrier Capacity | OTM | None |
| Carriers | Corporation ID | EBS | From EBS to OTM |
| Carrier Sites | Location ID | EBS | From EBS to OTM |
| Service Levels | Rate Service | EBS | Manual |
| Modes | Mode | EBS | Manual |
| Calendars (Shipping, Receiving, and Carrier) | Calendars | OTM | None |
The Shipping-Transportation Locations Synchronization concurrent program synchronizes the locations between EBS and OTM. You must create the location in EBS and then use this concurrent program to synchronize the EBS locations with OTM. After you run this concurrent program, OTM can use the new locations for itineraries and setup data.
Interface Parameters
The Shipping-Transportation Locations Synchronization concurrent program is submitted from the Interfaces menu. The program includes the following parameters:
Organization: OTM-enabled inventory organization
Location Name: The name of the internal location associated with the inventory organization set in the Organization parameter
Last Update Date From and To: The date range during which the internal location was last updated