Skip Headers

Oracle Order Management Implementation Manual
Release 12.1
Part Number E13406-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Shipping Execution Setup

This chapter covers the following topics:

Overview of Setup

Some of the setup steps are required and some are optional:

Setup Steps

Step 1: Set Up System Administrator

This step involves the following tasks:

Step 2: Set Up Flexfields

Define key and descriptive flexfields to capture additional information about orders and transactions. See: Oracle E-Business Suite User's Guide.

Step 3: Perform Oracle Inventory Setup

Perform all setup steps required for Oracle Inventory, then perform the following.

Organizations

Define at least one of the following:

Your item validation organization can be the same as your inventory source or your logical receiving organization, but you cannot use one organization for all three purposes.

Note: If you change the location of your organization, after delivery details have been created, then the new location will not take effect as the ship from location until new transactions are created. Each delivery detail needs to be updated with the new location if the ship from location needs to be changed on current deliveries.

Pick Confirmation

The Pick Confirmation Required check box affects the behavior of the picking process in Shipping Execution. Navigate: Oracle Shipping > Set up > Organization Parameters > ATP, Picking, Item- Sourcing tab.

If the Pick Confirmation Required check box is selected, then the system requires you to navigate to Inventory forms or Pick Confirm using a mobile device to perform a manual pick confirmation of the move order that was generated as a result of the Pick Release process. The pick confirmation process acknowledges the transfer of the item being picked from its source location to the default staging location.

If the Pick Confirmation Required check box is deselected (the default) for new installs, the system performs the pick confirmation process automatically based on sourcing rules set up in Oracle Inventory.

Organization Parameters Window - ATP, Pick, Item-Sourcing Tab

the picture is described in the document text

Staging Subinventory

Create at least one staging subinventory for each organization. Move orders record the movement of pick released material to staging subinventories. Staging subinventories should be reservable.

Step 4: Define Profile Options

Define profile options to specify certain implementation parameters, processing options, and system options. See: Profile Options.

Step 5: Define Lookups

Define lookups that provide custom values for many lists of values throughout Oracle Shipping Execution, including Shipping Workflow specific lookups. See: Shipping Execution Workflows.

Step 6: Define Roles and Users

Assign roles to users that control access (edit or view privileges) to shipping entities in the Shipping Transactions form and Quick Ship window. See: Roles and Users.

Step 7: Define Global Parameters

Define default Global Parameters. See: Defining Global Parameters.

Step 8: Define Shipping Parameters

Define default Shipping Parameters. See: Shipping Parameters.

Step 9: Define Freight Carriers, Cost Types

Define freight carriers, services, and freight costs to specify on orders. Assign carrier services to organizations. See: Defining Freight Carrier Ship Method Relationships.

Define freight costs to specify on orders. See: Defining Freight Costs.

Step 10: Define Documents and Choose Printers

Define groups of shipping documents that can print to specified printers when you pick release and confirm shipments.

To set up document sequencing perform the following tasks:

Step 11: Define Pick Slip Grouping Rules

Define pick slip grouping rules to determine how released picking lines are grouped onto pick slips. See: Defining Pick Release Parameters

Step 12: Define Release Rules and Release Sequence Rules

Define the order in which picking lines are allocated to inventory. See: Defining Release Sequence Rules and Defining Release Rules.

Step 13: Defining Transportation Calendars

Assign a calendar that you created in the Bill of Materials (BOM) application to a shipper, receiver, or carrier. See: Oracle Bills of Material User's Guide and Defining Transportation Calendars.

Step 14: Define Shipping Exceptions

You can define exceptions, define processes for exception handling and relate them to appropriate exceptions, log exceptions, associate status with exceptions at various stages in the logging and handling process, start exception handling, and view and track exceptions. See: Defining Shipping Exceptions.

Step 15: Define Container-Item Relationships

Define the relationship between container items and load items to specify the preferred container to use for automated packing and to specify the maximum quantity, weight, or volume of the load item that can be packed into a container item. See: Defining Container-Item Relationships.

Step 16: Define LPN Name Defaults

Define the default naming convention of LPNs for your organization. Specify the Prefix, Suffix, Starting Number, Pad to Width, and UCC-128 Suffix.

Profile Options

During implementation, you set a value for each user profile option to specify how Shipping Execution controls access to and processes data.

Generally, the system administrator sets and updates profile values. See: Setting Profile Options, Oracle E-Business Suite System Administrator's Guide - Maintenance.

Implementing Profile Options Summary

The following table indicates whether you (the “User”) can view or update the profile option and at which System Administrator level the profile options can be updated. The System Administrator level includes User, Responsibility, Application, and Site levels.

The table also displays if the profile option is optional or required:

The following terms are used in the table to identify if you can view or update the profile option information:

WSH: Bulk Batch Size

This profile option enables you to specify how many lines are to be interfaced to Oracle Order Management per call, and to specify the batch size that is inserted in the Oracle Inventory tables. If the value is set to null, the batch size passed to Oracle Order Management and Oracle Inventory will not be limited.

However, if your system experiences out-of-process memory or rollback segment errors when processing a large number of order lines, then you may need to restrict the batch size by setting the minimum batch size to 1000.

WSH: DSNO Output File Extension

This profile option enables you to select the file extension for your DSNO output file. Select from DOC, TXT, RTF, and DAT.

WSH: Debug Enabled

Select from the Debug Enabled LOV either YES or NO to activate the debug feature. The default is NO.

WSH: Debug File Prefix

The naming convention for the debug file is <Debug File Prefix Profile>_sessionid.dbg If value of profile is null, naming convention is wsh_<username>_<sessionid>.dbg Where: <username> is Application user name. If application context is not established, it will be defaulted to dbuser: <dbusername>.

<sessionid> is Database session id.

WSH: Debug Level

The value entered for this profile option will determines the level of the Shipping Debugger. Default value: Procedure.

WSH: Debug Log Directory

The value entered for this profile option must be specified as a UTL_FILE parameter value.

WSH: Debug Module

The Module describes where to find the log message within the code. This profile indicates that debug messages from only those modules with names beginning with the profile value will be logged. The naming convention for Module is: <application short name>.<directory>.<package>.<routine>.<label> e.g. wsh.plsql.WSH_WV_UTILS.convert_uom.

WSH: Defer Inventory Process

When this profile option value is set to YES, then Oracle Inventory's Process Online API call will be deferred. If the value is set to either NULL or NO, then the process online API will be called in online mode.

WSH: Distributed Source Entity

The value of this profile option determines the way shipment requests are sent to the Distributed WMS system. If it is set to Shipment Delivery, then Shipment Requests can be generated for Delivery. If set to Fulfillment Batch, then Shipment Requests can be generated for Shipment Batch. The default is Shipment Delivery.

WSH: Enable Delivery Merge

This profile option is used to enable delivery merge in Shipping Execution.

WSH: Express Pick

If this profile is enabled (YES), then the Pick Release process will skip move order line creation, allocations, and the pick confirm process if the following conditions are met:

If the above conditions are met then the lines will not be staged if:

No Pick slips can be generated for lines processed as part of Express Pick. The subinventory where reservation was created (before pick release) will be used for storage of material and staging. The Staging subinventory and locator entered on the Release Sales Order window is always ignored.

WSH: Ignore Weight/Volume Conversion Errors

This profile option enables you to determine whether Shipping Execution should ignore weight and volume conversion errors when updating an LPN. Default is Yes.

WSH: Internet Proxy URL

This enables the system to access UPS servers for United Parcel Service integration. If no firewall is installed at your site, you do not need to set the profile. This profile can only be modified by the System Administrator at the site level.

WSH: Number of Pick Release Child Processes

This profile enables you to specify the default number of child processes that are run when pick release is executed.

WSH: Overpicking Enabled

Enter Yes to enable overpicking. Overpicking is using the pick confirm transaction to pick more than the requested quantity of a delivery, up to the overshipment tolerance.

WSH: Override Ship to Deliver Workflow

This profile enables you to specify whether the Ship to Delivery workflow can be overridden or not. If it is set to Yes, then you can override the workflow process if a problem occurs. If set to No, then you cannot override the workflow process.

WSH: Pick Release Batch Size

This profile option enables you to change the batch size from 3 to 1000. Any value less than 3 is interpreted as 3 and any value greater than 1000 is interpreted as 1000.

WSH: Populate Latest Ship/Delivery Date

This profile enables you to determine whether Shipping Execution should populate the Latest Ship Date and Latest Delivery Date.

WSH: Quick Ship Default View

This profile option enables you to determine the default view of the Quick Ship window. The default is the Delivery Confirm view.

WSH: Retain ATO Reservations

This profile option enables you to avoid the redundancy of re-reserving an item. If set to Yes, then the inventory system retains the reservation and the reservation status changes from Staged to Unstage, while the delivery line status changes to Backordered.

WSH: Run PL/SQL Profiler

This profile option enables you to determine whether or not to run the PL/SQL Profiler. Select from YES or NO. The default is NO.

Roles and Users

Shipping Execution provides data access controls called roles that control users' access to the Actions list and Tools menu in the Shipping Transactions form and the Quick Ship window. Roles also control ship confirm error and warning messages for breaking ship sets, missing inventory controls, and breaking proportionality of ship model complete. Roles are assigned to users using grants that control access to view or edit specific shipping data or actions.

This is useful, for example, if you want to assign a grant to inexperienced users that provides view-only access or assign grants that prevent unwanted actions such as unintentional pick releases across multiple organizations.

Note: Roles provide data access controls for the Shipping Transactions form and the Quick Ship window. If you want to restrict user access to other windows like the Pick Release or setup windows, you can edit the Shipping menus in Shipping Administration.

For each role, select the following data access controls that control Edit and View access to shipping entities:

A role can provide either view-only, edit-only, or a combination of view and edit access depending on how you setup the role. You can create customized roles by defining the access controls you want. During the setup for each role, you enable or disable actions by selecting or deselecting the check box next to each action.

Note: If no data access control is selected, the user cannot edit or view the selected action.

Note: Ship confirm error and warning message configuration, on the Message tab, does not use data access.

After you have defined a role you can assign it to a user through a grant. A grant defines both the user's role and related information about the grant including the date, and the organization(s) to which the grant applies.

The system administrator or super user is responsible for defining roles and assigning the grants to users.

Defining a New Role

Shipping Execution enables you to define new roles by selecting the data access controls that you want. You can define a new role by:

After you have created the new role you can assign it by grant to a user.

To define a new role:

  1. Navigate to the Shipping Execution Role Definition window.

    Shipping Execution Role Definition Window

    the picture is described in the document text

  2. Enter the Name of the role.

  3. Enter a Description for the role.

  4. In the Trips tab, in the Data Access field, select:

  5. Enable each action that you want the user to have permission to perform.

    Note: As a shortcut, choose the Disable Actions button to disable all the actions or the Enable Actions button to enable all the actions.

  6. Select the Stops tab.

    Shipping Execution Role Definition Window - Stops Tab

    the picture is described in the document text

  7. In the Data Access field, select:

  8. Enable each action that you want the user to have permission to perform.

    Note: As a shortcut, choose the Disable Actions button to disable all the actions or the Enable Actions button to enable all the actions.

  9. Select the Deliveries tab.

    Shipping Execution Role Definition Window - Deliveries Tab

    the picture is described in the document text

  10. In the Data Access field, select:

  11. Enable each action that you want the user to have permission to perform.

    Note: As a shortcut, choose the Disable Actions button to disable all the actions or the Enable Actions button to enable all the actions.

  12. Select the Lines/LPNs tab.

    Shipping Execution Role Definition Window - Lines/LPNs Tab

    the picture is described in the document text

  13. In the Data Access field, select:

  14. Enable each action that you want the user to have permission to perform.

    Note: As a shortcut, choose the Disable Actions button to disable all the actions or the Enable Actions button to enable all the actions.

  15. Select the General tab.

    Shipping Execution Role Definition Window - General Tab

    the picture is described in the document text

  16. Enable each action that you want the user to have permission to perform.

  17. Select the Message tab.

    The Message tab enables you to configure ship confirm messages for Breaking Proportionality of Ship Model Complete, Breaking Ship Sets, and Missing Inventory Controls. See: Message Configuration in the Shipping Execution chapter of the Oracle Order Management Implementation Manual.

    the picture is described in the document text

  18. From the Activity list of values, select Ship Confirm.

  19. For each Message, select either Error or Warning depending on your business needs.

    Note: The System Defaults are Warning for each Message.

  20. Save your work.

Copying an Existing Role

Copying a role is useful for creating a new role based on the privileges of an exiting role. Because copying automatically duplicates the original role, it saves you time from manually entering all the control privileges of the original.

You can edit the privileges of the copied role, save the role with a new name, and assign it to users.

To copy an existing role:

  1. Navigate to the Shipping Execution Role Definition window.

  2. Find the role that you want to copy.

  3. Click New Record to create a new record.

  4. From the Edit menu, select Duplicate—Record Above to create a new role based on the privileges of the original.

  5. Save the new role.

Granting a Role to a User

You can grant a user a role in one organization or all organizations for a period of time. The role is assigned to a user by a grant. The grant is specific to a particular user and defines the role(s) assigned to the user, the organization where the grant is effective, the start date and optionally, an end date.

More than one grant can be assigned if the user requires different access controls to more than one organization. The start and end dates for grants can overlap.

For example, if a user requires full-access privileges to three organizations and view-only access to a fourth, the user must be assigned four grants—one for each respective organization (three full-access and one view-only grant). However, if only one grant is assigned, that grant becomes the default grant for the user.

In addition, the grant has the following requirements:

A role can be assigned to a user that spans all organizations instead of granting a unique grant per organization. If an organization is not specified, the grant is applicable to all organizations.

Warehouse Organization

A grant can have one or all inventory organizations. If an organization is not specified, the grant is applicable to all organizations.

For example, you can use grants to prevent a shipping clerk from assigning freight costs or planning a delivery in one or all organizations.

Note: Use caution when creating grants for all organizations (when no specific organization is selected). For example, if a user has a grant to view all organizations and a grant to perform actions on one organization, the union of these grants will enable the user to perform actions in all organizations.

Changing Organizations in the Shipping Transactions Form

If a user's effective grants are single organization, the user can select an organization when opening the Shipping Transactions form or from the Tools menu—Choose Organization. If all effective grants are in the same organization, the Shipping Transactions form defaults to that organization.

Effective Dates for a Grant

Optionally, in the Start and End Date fields, you can enter a start and end date for the grant to assign it for a specific period. For example, you can assign temporary employees a grant that is effective for the duration of their assignment. The date status for a grant can be endless, future or expired:

To grant a role to a user:

  1. Navigate to the Shipping Execution Grants window.

    Shipping Execution Grants Window

    the picture is described in the document text

  2. In the User field, select the user's name.

  3. In the Role field, select the role that you want assigned to the user.

    Note: To view the available privileges for a selected role, click Edit Role to display the Shipping Execution Role Definition window.

  4. In the Org field, select the organization to which the grant is assigned (optional). A user can be assigned only role per warehouse (organization). However, you can assign a different role to a different warehouse.

  5. In the Start Date field, enter the date that you want the role to start.

  6. In the End Date field, enter the date that you want the role to end. If you do not want the role to end, leave the field blank.

    Once the grant is saved, only the end date can be updated. However, the date cannot be updated once it has expired.

  7. Save your work to activate the role.

Finding Grants and Roles

You can perform a search to find current or expired grants, find users and their assigned grants, or find active grants for an organization(s).

You can also perform a search to find existing roles.

To find grants and roles:

  1. Navigate to the Shipping Execution Grants window.

  2. Click the Find icon to display the Find Grants window.

    Find Grants Window

    the picture is described in the document text

  3. Enter the User Names to find the users and their assigned roles.

  4. Enter the Role name to find the available roles and the users assigned to them.

  5. In the Org Span field, select:

  6. Enter the Organization if you selected Single Organization for the Org Span, or leave blank if you left the Org Span blank.

  7. Select the Effectivity for the role you are searching for. Select from:

  8. Select the Start dates or a range for the start dates.

  9. Select the End dates or a range for the end dates.

  10. Click Find to display the search results in the Shipping Execution Grants window.

  11. Save your work.

To find a role definition

  1. Navigate to the Shipping Execution Role Definition window.

  2. Click the Find icon to display the Find a Role Definition window.

    Find a Role Definition Window

    the picture is described in the document text

  3. Enter the name of the role and click Find.

    The search results display in the Name column.

  4. Select the role and click OK to display the role in the Shipping Execution Role Definition window.

Updating a User's Grant

At times, a user's assigned grant may need to be updated. For example, if the user is promoted and requires a different set of privileges, the assigned role needs to be updated for the user's organization to reflect the changed responsibilities.

To change the role, you must end the user's existing role and assign a new role with the new privileges.

If you want to change the end date for a grant that has not expired, you can update the end date and saving the changes. If the date and grant has expired, the user must be granted a new grant (role).

Note: You cannot change a role by editing the role's parameters and saving the changes.

Updating a user's grant only affects that user, not all users assigned with the role.

To update a user's grant:

  1. Navigate to the Shipping Execution Grants window.

  2. Find the user whose role you want to update. The user and current role assignments display in the Shipping Execution Grants window.

  3. If you are just updating the End Date, enter a new date in the End Date column and save the changes.

  4. If you are ending a user's role and assigning another role, enter an end date in the End Date column of the role you want to end.

  5. Select the new role, the organization to which the new role is assigned, and the start and end dates of the new role.

    The start date must follow the end date of the role that you are updating. The new role is effective when it reaches its start date.

  6. Save your work.

Defining Global Parameters

Global General parameters enable you to define miscellaneous parameters, Oracle Workflow parameters, and unit of measure (UOM) defaults for all of your organizations.

To define global miscellaneous parameters and UOM defaults

  1. Navigate to the Global Parameters window.

    Global Parameters Window

    the picture is described in the document text

  2. Select the Enforce Ship Method check box to enforce that a ship method (carrier) is entered and recorded for each shipment.

    This is recommended if your business practices require a record of the ship method/carrier for each shipment.

  3. Select or clear Allow Future Ship Date.

  4. Select the Defer Interface check box to defer shipping interfaces from initiating updates to the Oracle Order Management and Oracle Inventory interface tables.

  5. Select Consolidate Backordered Lines if you want to consolidate a line that was split and subsequently backordered. The line will be automatically consolidated with other backordered lines that it was part of originally.

  6. The Defer Planned Shipment Interface parameter controls the default setting for running the Planned Shipment Interface concurrent request. Select Yes to run the request manually (or to schedule it), or No to run the request automatically every time the planned shipment is received from Oracle Transportation Management.

  7. Within the Global UOM Defaults region, define the default Weight Class.

    The Weight Class default controls:

  8. Define the default Volume Class.

    The Volume Class default controls:

  9. Define the default Distance Class.

    The Distance Class default controls the default distance UOM in the Carrier/Carrier Services Rating/Mode Limits tab.

  10. Define the default Dimension Class.

    The Dimension Class default controls the default dimension UOM in the Carrier/Carrier Services Rating/Mode Limits tab.

  11. Define the default Time Class.

    The Time Class default controls the default time UOM in the Carrier/Carrier Services Rating/Mode Limits and carrier sites transportation tab.

  12. Define the default Currency.

    The Currency default controls the default currency used for Carrier Services Rating.

  13. Within the Workflow region, use the list of values in the Enable Workflows field to select the Shipping entities for which you want Oracle Workflow to be enabled. These fields are optional and include:

Related Topics

For more information on Oracle Shipping Execution workflows, and using Oracle Workflow with Oracle Shipping Execution, see Oracle Workflow User's Guide.

Shipping Parameters

You define the default values for basic shipping information such as units of measurement, pick release rules, weight and volume calculations, and delivery grouping rules. Shipping parameters are organization specific.

The parameters are arranged into the following tabbed regions in the Shipping Parameters window:

Defining Shipping Parameters

On the General tab, you define general Shipping Execution parameters such as weight and volume unit of measure (UOM) class parameters, criteria for percent fill basis calculations, International Trade Management (ITM) screening generation, and Oracle Workflow settings.

To define shipping parameters

  1. Navigate to the Shipping Parameters window.

    Shipping Parameters Window - General Tab

    the picture is described in the document text

  2. Select the General tab.

  3. Select the default Weight UOM Class from the valid UOM classes.

  4. Select the Volume UOM Class from the valid UOM classes.

    Note: The seeded values shown in the UOM class are created in Oracle Inventory.

  5. Select the default unit of measure for the Percent Fill Basis of a container. You can select Weight, Volume, or Quantity.

    Percent Fill Basis is used to determine if containers have met their minimum fill percentage requirements.

    If you select Weight or Volume, the calculation uses the item and container physical attributes in Oracle Inventory.

    If you select Quantity, the calculation uses the Container Load Relationship details to determine the maximum number of items that will fit into the container.

  6. In the Export Compliance Screening field, select one of the following: (Requires ITM Partnership Integration)

  7. Enable Workflows by selecting whether you want Delivery workflows or None of the workflows enabled.

    Specific tasks and output are enabled through the use of customized business objects. For example, the workflow can be configured so that specific users receive a notification email when an overship or backorder occurs.

  8. Depending on your business needs, select the Raise Business Events check box.

    Business events are optional. Individual Business Events can be enabled via the Business Events definition window. See: Shipping Execution Workflows and Oracle Workflow User’s Guide.

  9. Save your work.

Defining Pick Release Parameters

You can define default picking criteria that is used at pick release. You can also select the default settings for auto-detailing and auto-creating deliveries.

To define pick release parameters

  1. Navigate to the Shipping Parameters window.

    Shipping Parameters Window - Pick Release Tab

    the picture is described in the document text

  2. Select the Pick Release tab.

  3. Select the Release Sequence Rule.

    During pick release, this rule determines the order in which delivery lines are allocated to inventory. It appears as the default release sequence rule in the Release Sales Order window.

    Note: It is recommended that you select the most frequently used release sequence rule; although it becomes the default, you can change it any time you launch pick release.

  4. Select the Pick Slip Grouping Rule.

    This rule dictates how the released delivery lines are grouped on pick slips and how the pick slip number is generated by pick release. It appears as the default pick slip grouping rule in the Release Sales Order form.

    Note: It is recommended that you select the most frequently used pick slip grouping rule; although it becomes the default, you can change it any time you launch pick release.

  5. From the Print Pick Slip list of values, select when you want the pick slips printed.

  6. Enter the Number of Pick Slip Lines to print on each pick slip.

    If Print Pick Slip is Immediate, enter the maximum Number of Pick Slip Lines to print on each pick slip. For example, if Number of Pick Slip Lines is 25 and pick release selects 40 lines, it prints two pick slips, one with 25 lines and the other with 15 lines.

  7. Select the Default Pick Release Document set to be printed at pick release.

  8. Select the Default Stage Subinventory.

    The process of Pick Confirmation transfers move orders to this staging subinventory. The list of values displays all subinventories in the organization. Staging subinventories should be reservable.

  9. Select the Default Stage Locator.

    Move orders move material to this locator. The list of values displays all locators in the Default Stage Subinventory.

  10. Select the Autocreate Deliveries option to specify your preference for delivery creation. You can override this preference at pick release execution.

    Note: There are six descriptive flex field defaulting types supported when auto-creating deliveries: SQL Statement (Not having references to:$FLEX$.<VALUE_SET_NAME> and:block.field), Constant, Current Date, Current Time, Previous Segment, and Profile Option value.

  11. Select Auto Allocate to automatically allocate delivery lines at pick release.

  12. Select Enforce Ship Sets and Ship Models to enforce that all lines in the Ship Set or Ship Model are released together.

    Note: Ship sets for non-transactable delivery lines are validated during ship confirm. However, a ship set for non-transactable delivery lines is not validated during pick release because the item(s) are not picked from inventory.

  13. Select Plan Tasks if Oracle Warehouse Management is enabled within your organization. See: Oracle Warehouse Management User's Guide.

  14. Select Pull Replenishment to enable the pull replenishment process to fill up a locator up to a maximum capacity when a shortfall is detected during order release.

    Note: This field supports the Forward Pick Replenishment feature in Oracle Warehouse Management System (WMS).

  15. Select Retain Unstaged Quantity during Overpick if you do not want delivery details to be cancelled during overpicking; however, if deselected, then only the non-staged delivery details will be cancelled during overpicking.

    For move order lines: When overpicking a move order line (in the Transact Move Order window or Mobile Picking window), you can transact a maximum of the over-tolerance quantity minus the total of all the staged/shipped/allocated Released to Warehouse quantity for the current order line. Depending on the quantity that is overpicked, the remaining non-staged details of the requested quantity is adjusted so that the sum of shipped quantity on shipped/staged details and the requested quantity on the non-staged details does not exceed the total allowed tolerance quantity.

Defining Shipping Transaction Parameters

You can define parameters for your shipping transactions such as default ship confirm document set, ship confirm rule, auto-pack options, goods dispatched account and whether to enforce packing into containers.

To define shipping transaction parameters

  1. Navigate to the Shipping Parameters window.

    Shipping Parameters Window - Shipping Transaction Tab

    the picture is described in the document text

  2. Select the Shipping Transaction tab.

  3. Select the Default Ship Confirm Document Set that prints as part of the ship confirm process.

    The list of values displays the valid delivery document sets. See: Defining Shipping Document Sets .

  4. Select a Ship Confirm Rule that your organization will use as a default for auto ship confirming.

    Note: If you want to define a default ship confirm rule, then you must select Ship All as your option when you define your ship confirm rules in the Ship Confirm window.

  5. Select your Autopack Options. From the list of values, select either No, Yes, or Autopack Master.

    You can autopack delivery lines for a delivery into LPNs (containers). When you autopack a delivery, the delivery lines are grouped together by shared attributes such as the Ship To location, and are packed into LPNs based on the delivery grouping rules.

    Once a delivery is packed, the delivery line information cannot be changed until you unpack the delivery. The weight and volume is calculated at ship confirm automatically.

  6. Select a default Goods Dispatched Account.

    Use the Cost of Goods Sold (COGS) account for this organization. The sales order issue transaction uses this account if the Oracle Order Management workflow cannot determine one.

  7. Select a value for Enforce Packing in Containers:

  8. Save your work.

Defining Delivery Parameters

Delivery parameters enable you to define how to group delivery lines for a delivery. The mandatory default attributes are Ship From Location and Ship To Location; however, you can select additional optional grouping parameters that include:

The delivery attributes determine how delivery lines are grouped into deliveries when auto-creating deliveries. For example, if the grouping attribute Customer is selected, the delivery lines are grouped into deliveries by customer: for example, deliveries for Customer A are grouped into Delivery A, deliveries for Customer B are grouped into Delivery B.

You can select more than one grouping attribute to refine your grouping criteria further: for example, if you select Customer and Ship Method as grouping criteria, delivery lines with the same customer and carrier criteria are grouped into deliveries.

If each optional grouping attribute is checked, the delivery's corresponding field cannot be updated if delivery lines are assigned to the delivery. This ensures that the delivery lines' grouping criteria is not broken by a different attribute value: for example, if someone tries to select a different ship method.

If each optional grouping attribute is unchecked, its field in the delivery record can be updated until the ship confirm stage.

For example, if you want to change the Ship Method in the delivery and do not need to enforce it as a grouping attribute, you can deselect Ship Method.

Do not change these options if you have deliveries that are not ship confirmed.

To define delivery parameters

  1. Navigate to the Shipping Parameters window.

    Shipping Parameters Window - Delivery Tab

    the picture is described in the document text

  2. Select the Delivery tab.

  3. Choose the attributes for grouping the delivery lines.

  4. Optionally, select Autocreate Delivery Criteria if you enabled the Autocreate Delivery option on the Pick Release tab.

  5. Select an Appending Limit.

    The appending limit enables you to indicate the point at which you want to stop the system from adding lines to a delivery (the point that ends the ability to merge deliveries). You must set the appending limit to a value other than Do Not Append in order to use the Append Deliveries option within Release Rules and the Process Deliveries SRS.

    The Appending Limits include:

  6. Select Dock Appointment Scheduling to receive dock appointment information from Oracle Transportation Management (OTM) to Oracle E-Business Suite (EBS) as part of the planned shipment interface. The following prerequisites are required to select the Dock Appointment Scheduling option:

  7. Save your work.

Defining Freight Carriers and Ship Methods

A freight carrier is a commercial company that transports shipments to and from customers, suppliers, and internal organizations. You must set up each carrier's information as a party in Oracle Shipping Execution before shipping goods; you should assign a carrier to each delivery. You also must associate a general ledger account with each carrier to collect associated costs.

Before you set up the carriers:

To define a freight carrier

  1. Navigate to the Carriers window.

    Carriers Window

    the picture is described in the document text

  2. Enter the Name and Short Name for the carrier.

  3. Enable the Active check box and Generic check box, if applicable.

    Note: You can only define one generic carrier. The generic carrier is used to quote transit times based on a mode of transportation and service level when the final carrier is not yet assigned. See: Defining a Generic Freight Carrier.

  4. Optionally, enter the standard carrier alpha code (SCAC).

  5. Within the Services tab, select the Service Level for this carrier.

    Examples of service level include: next day air, ground, and next day air early AM.

  6. Select the Mode (of transportation) for the carrier.

    After you enter each service level and mode combination, Oracle Shipping Execution assigns a ship method and displays it in the Ship Method field. The format of the generated ship method is <carrier short name>-<transportation mode>-<service level>, for example, Truck-LTL-Ground.

    Note: You can change the name of the generated Ship Method after it has been generated as long as it is unique.

  7. Optionally, enter Service Times.

    Certain carriers offer services with time estimates or guarantees. Record this information in the Service Times fields and then use it later for reference when deciding which of this carrier's many services to use for a certain delivery.

    Note: Assemble the times so that both of them are in the same unit of time. Enter the best case time in Service Times Min, enter the worst case time in Service Times Max, and select the unit of time of both of them in Service Times Period.

  8. Select Enable if you will be assigning this ship method to organizations and to deliveries in Oracle Shipping Execution.

  9. Select Web Enable if you will be assigning this ship method in Oracle iStore.

  10. Save your work.

  11. Click Define Service Levels if you need to define a new Service Level that is not identified.

    The Oracle Shipping: Carrier Service Levels Lookup window displays the carrier service levels lookups.

  12. Select any line and the New icon on the toolbar.

  13. Enter a unique Code for your lookup.

  14. Enter a Meaning and Description for your lookup code.

  15. Optionally, enter a Tag number.

  16. The From Effective Date will default to the current date.

    You can modify this field to another future date if needed.

  17. Optionally, enter a To Effective Date that will disable your lookup.

  18. Verify that the Enabled check box is selected.

    Oracle Shipping: Carrier Service Levels Lookups Window

    the picture is described in the document text

  19. Save your work and return to the Carriers window, Services tab.

  20. From the Services tab, click Details to view, update, or define the service level attributes specific to your carrier.

    Note: If the value is set differently at the carrier and service levels, then service level values take precedence. The carrier level attributes will take precedence only if something is undefined (blank/null) at the service level.

    Service Attributes Window

    the picture is described in the document text

  21. The General tab displays the following:

    Note: You must enable the service level in the Carrier Service Levels Lookup window when you define the service level. You cannot enable it from within the Service Attributes window.

  22. Navigate to the Rating tab.

    Service Attributes Window - Rating Tab

    the picture is described in the document text

  23. Within the UOMs region, the following fields are displayed:

  24. Within the TL Rating Attributes region, the following fields are displayed:

  25. Click Organization Assignments.

    Organization Assignments-Carrier Service Window

    the picture is described in the document text

  26. Select Assigned to assign the ship method to the organization(s) that use it.

    You can assign the ship method to more than one organization.

    Note: If you want to assign the ship method to all of your organizations, click Assign All to have all organizations' Assigned field selected. If you want to begin again with your assignments, click Unassign All to have all organizations' Assigned field cleared.

  27. Click Done.

  28. Save your work.

To define and edit carrier address/site

  1. From the Carriers window, select the Addresses/Sites tab.

    The information on the Addresses/Sites tab pertains to contacts at the local carrier site, such as a dispatch center. Existing addresses and contacts will be displayed if they exist. You can edit an existing site using the Edit button, or you can create a new Address/Site by clicking New.

  2. Click New to create a site or Edit to edit an existing site, depending on your business needs.

    Note: This documentation covers the details of creating a new carrier address/site. To edit an existing address/site, you edit the fields that require an update.

  3. Select the Country from the list of values.

  4. Enter a unique Site Number.

  5. Enter the Address, City, State, County, Postal Code, and Province as required.

    Carrier Site Details Window - Address Tab

    the picture is described in the document text

  6. Select the Contacts tab.

    The information on the Contacts tab pertains to contacts at the local carrier site, such as a dispatch center.

  7. Optionally, enter a contact Number.

  8. Enter the Last Name, First Name, Title, Job Title, and Email Address as needed.

  9. Select the Active check box to indicate whether or not the contact is a current employee.

  10. Under Contact Telephones, enter the Country Code, Area Code, Telephone Number, Extension, and Type as needed.

    Note: Contacts cannot be deleted.

    Carrier Site Details Window - Contacts Tab

    the picture is described in the document text

  11. Save your work.

  12. To enter distribution accounts, return to the Carriers window, place your cursor in the Name field and, from the Tools menu, select Distribution Accounts.

    Freight Carriers - Distribution Accounts Window

    the picture is described in the document text

  13. For each organization to which the carrier is assigned, enter the Distribution Account.

    If the Inactive After field displays a date, then it is the date that the carrier became inactive in the organization (the Organization Assignments form, Active checkbox is cleared).

  14. Save your work and close the Distribution window.

To define carrier contacts

  1. From the Carriers window, select the Contacts tab.

  2. Enter the contact information for the carrier's centralized corporate contracts, such as, sales representative, pricing manager, and customer service rep.

  3. Mark the current contact as Active, mark the current telephone numbers of each contact as Active, and select one telephone number for each contact as the Primary.

To define carrier classifications

  1. From the Carriers window, select the Classification tab.

  2. Select the class Category that the carrier belongs to.

  3. Save your work.

To define a generic carrier

  1. Navigate to the Carriers window.

  2. Enter the Name of the generic carrier.

    Note: A generic carrier cannot be an existing carrier. You must define a new carrier to be the generic carrier.

  3. Enter a Short Name for the generic carrier.

  4. Select the Active check box.

  5. Select the Generic check box.

    Note: Each organization can have only one generic carrier. If a generic carrier has already been defined for your organization, an error will display notifying you that a generic carrier has been defined.

    Note: The Services tab is the only tab that is active for a generic carrier.

  6. Enter a Service Level.

  7. Enter a Mode.

  8. Save your work.

Ship Method

Upgrade Processing

At upgrade, the information in ORG_FREIGHT will be upgraded to FND_LOOKUP_VALUES. You should not have to maintain freight carrier and ship method information immediately after the upgrade; you can then begin to maintain any changes after this point.

Ship Method Defaulting Rule

For the ship method to pass from the sales order to the Shipping Transactions form, it must appear at the line level. To accomplish this, create a defaulting rule such that ship method defaults automatically from the sales order header to all sales order lines. The procedure appears later in this section.

Default Ship Method Example

the picture is described in the document text

To create a ship method defaulting rule

  1. Navigate to the Defaulting Setup - Entity Attributes window.

  2. Choose the flashlight icon to display the Entity window.

  3. Select Order Line as the entity and click OK.

  4. From the attribute list, select Shipping Method.

  5. Click Defaulting Rules.

  6. In the Defaulting Conditions section, enter 1 as the precedence and select Always as the defaulting condition.

  7. In the Default Sourcing Rules section, enter 1 as the sequence and select Related Record as the source type.

  8. In the Default Source/Value section, select Order Header.Shipping Method.

  9. Save your work.

  10. Enter a sales order to verify that the defaulting rule is working properly. Select a ship method in the order header, enter a sales order line, then verify that the line ship method matches the header ship method.

Defining Freight Costs

You can define allowable freight costs and suggested amounts for shipments. These amounts are applied at ship confirm or once a delivery line is planned. You can add multiple freight costs to a shipment from the list of allowable freight cost types that you define.

Note: If necessary, you can override the freight costs and suggested freight amounts at ship confirm.

You can also define multiple freight costs for a specific freight cost type. For example, if you want to track different types of insurance, you can create different insurance costs under the insurance freight cost type such as liability insurance or shipping insurance.

When you add freight costs at ship confirmation for a foreign currency order, you can use either your functional currency or the order's foreign currency. If you use your functional currency, the freight charges are converted to the order currency through Oracle Receivables.

Note: You should define all your freight costs in your functional currency for uniformity. You can then modify the currency to match the order, and modify the amount on the Confirm Shipments window, as necessary.

Prerequisites

To define freight costs

  1. Navigate to the Freight Cost Types window.

    Freight Cost Types Window

    the picture is described in the document text

  2. Enter a Name for the freight cost.

  3. Select the Type of freight cost.

  4. Select a Currency for the freight cost.

  5. Enter the Amount for the freight cost.

    You can change this amount during ship confirmation. You can enter 0 as the amount.

  6. Optionally, enter Effective dates for the freight cost.

  7. Save your work.

Related Topics

Oracle Pricing User's Guide

Defining Shipment Transit Times

Within the Inter-Org Shipping Methods window, you can specify the ship method, intransit times, load weight and the volume capacity for any movement between two location types.

Note: Within Oracle Inventory, you must set up the relationship between organizations before using this window. You must also specify the Ship Method and other associated parameters for the interlocation movement of the goods.

To enter ship methods

  1. Navigate to the Transit Times window.

    Transit Times Window

    the picture is described in the document text

  2. Click the New icon in the tool bar.

  3. In the Origin Type column, select one of the following:

  4. In the From Location column, select where the shipment will ship from.

  5. In the Destination Type column, select Internal Location, External Location, Region, or Zone depending on the scenario for which you are defining the transit times and other information.

    Note: The destination type you select will determine the outcome in the Destination column. For example, if you select Internal Location, then the Destination list of values will contain only internal organizations. If you select Region as the Destination Type, then click the Destination field and the Select Regions window displays to enable you to find a defined region.

  6. In the Destination column, select a location that the shipment is destined for.

  7. Within the Ship Methods region, select a Ship Method.

    Note: If a ship method is not defined for an internal location, then the lead-time will not be taken into consideration for internal requisitions.

  8. Enter an Intransit Time.

    Note: For a given ship method, ASCP/GOP will use the transit time to calculate ship or arrival date.

  9. Enter Daily Capacity to define the maximum allowable daily load weight capacity that may be transported via this ship method.

    Note: Daily Capacity serves as a parameter in Oracle Advance Planning applications and a penalty factor may be associated with exceeding the daily capacity.

  10. Enter UOM for the weight unit of measure used for daily capacity, for example pounds, tons, or kilograms.

  11. Enter Cost Per Unit for goods transported using this ship method for the specified From Location and Destination Type.

  12. Enter the Currency associated with the cost per unit.

  13. Enter the Daily Capacity to define the maximum allowable daily volume capacity that may be transported using this ship method.

    Note: Daily capacity serves as a parameter in Oracle Advance Planning applications and a penalty factor may be associated with exceeding the daily capacity.

  14. Enter UOM for the volume unit of measure used for daily capacity, for example cubic feet or cubic meter.

  15. Select Default Method if you want this ship method to default into the Sales Order pad for this combination of From Location and Destination Type when Oracle Advanced Planning and Scheduling is installed.

    Global Order Promising will use the default ship method and its associated transit time if no shipment is specified on the sales order.

  16. Save your work.

To find and modify information related to ship methods:

  1. Navigate to the Transit Times window.

  2. Click the Find icon in the tool bar.

  3. Enter the From and To criteria and click Find.

  4. Within the Ship Methods region, add another Ship Method and the supporting information or modify the information for an existing ship method.

Defining Document Sequences

You can define document sequences to generate a unique numbering sequence for documents in an Oracle Applications product. For example, document sequencing can be used to uniquely number invoices generated by Oracle Receivables and bills of lading and packing slips in Oracle Shipping Execution.

Using the Sequence Assignments window, you assign your sequence to number only those documents that satisfy rules you define. Document sequences ensure that every document your users create can be accounted for.

To define document sequences

  1. Navigate to the Document Sequences window.

    Document Sequences Window

    the picture is described in the document text

  2. Define the document sequence Name and Application.

    Note: Once the sequence name and application are selected, they cannot be changed.

  3. Select an Effective From and To date.

    The From field automatically defaults to the current date, and once a sequence is defined, the start date cannot be changed. If you leave the To field blank, your document sequence does not expire; and if you enter an end date and define your sequence, the end date cannot be modified later. If there is no end date defined and there are no active assignments for a sequence, you can disable the sequence by entering the current date as the end date.

  4. In the Type field, select Automatic. If you have certain localizations, select Gapless only under the direction of Oracle Support.

  5. Enable the Message box to have each document display a message to inform the user of the sequence name and value (number).

    The message displays in the message line near the bottom of the window.

    Note: This check box only applies to sequences with the automatic type of numbering. Messages appear only on form displays, and are not written to a request's log file. Once a sequence is defined, the message choice cannot be changed.

  6. Enter an Initial Value for the first document in your sequence. This field only applies to sequences with automatic or gapless numbering type.

    If you leave this field blank, the first document is automatically assigned a value of 1. Once a sequence is defined, this initial value cannot be changed.

    You can assign valid operating dates for document sequences, and set them to run manually or automatically during ship confirm and pick release. See: Application Object Library.

Defining Document Categories

You can create a document category for shipping documents such as a bill of lading (BOL) and assign it to a location or all locations. You can create more than one document category for a document, for example, if you want each carrier to have its own bill of lading number series, you can set up a unique document category to accommodate this requirement.

You must define a category for each bill of lading and packing slip that you want to create. You can create a bill of lading category for each ship method/carrier or define a single bill of lading category for all. When you use a different bill of lading sequence for each carrier, you can easily identify the carrier by looking at the bill of lading number.

In addition, you can tie a category to a specific location and have a different BOL sequence for the same carrier departing from a different location. For example:

When defining a document sequence for the packing slip, you can create a category for every location or one category for all locations. The document category is specific to a document type and location. The document category is also specific to the application and responsibility from which you accessed the form. If you create a document category called Viking BOL for WH1 in responsibility Oracle Order Management Super User, you must be working as Oracle Order Management Super User to have visibility of this category when assigning document sequences to it.

To view existing document categories

  1. Navigate to the Document Categories - Summary window.

    Document Categories - Summary Window

    the picture is described in the document text

  2. Click the Find icon to display the list of existing document categories.

  3. Select the document category, and click OK to display it in the Document Categories Summary window.

  4. Select the document category and click Open.

To define a document category

  1. Navigate to the Document Categories window.

    Document Categories Window

    the picture is described in the document text

  2. Enter a Category Name and Description.

  3. Select the Document assigned to the category; for example, Bill of Lading or Packing Slip.

    Note: You can override this selection when you create documents; however, selecting a default here provides faster document definitions.

  4. Within the Category Includes region, select the Ship Methods and Locations for the document types:

  5. In the Sequence region, enter the Prefix, Suffix, and Delimiter for the sequence number to be printed on the document.

  6. Preview the sequence name in Default Appearance.

    Note: Enter any alphanumeric values for Prefix and Suffix. Typically, enter a value that identifies the location, carrier, or date in which document is generated. The delimiter separates the prefix and suffix from the generated number and can be any character.

  7. Save your work.

Assigning Document Sequences to Document Categories

After defining document sequences and categories, assign document sequences to document categories. Assigning sequences is application and category specific.

You cannot change a document category definition. If you find incorrect information, create a new category with the correct information, re-assign document sequences to the new category, and disable the old category.

Either leave alone the existing Category or Disable it cautiously since it may affect other documents using the setting. For that reason disabling cannot be undone.

To assign document sequences to document categories

  1. Navigate to the Sequence Assignments window.

  2. Select Oracle Shipping as Application.

  3. Select the Document Category.

  4. Select the ledger.

  5. Select the Method:

    Within the Assignment tab:

  6. Enter the Start and End Dates.

  7. Choose the Document Sequence.

Defining Shipping Document Sets

You can group related shipping documents and other reports in a set that can be printed at pick release or ship confirm. You can include a variety of shipping documents in a set such as a Bill of Lading and Packing Slip Report and determine the print sequence.

Shipping Execution provides three pre-defined (seeded) document sets:

To define document sets

  1. Navigate to the Shipping Document Sets window.

    Shipping Document Sets Window

    the picture is described in the document text

  2. Enter a Name and Description for the new document set.

  3. Select the Usage for the document set:

  4. Optionally, enter the Effective Dates for the document set.

  5. The default Printing Method is parallel. This submits the reports for printing separately, each with a different request ID. If one of the reports in the document set fails to print, the other reports will print.

  6. Enter a Sequence number.

  7. Select Shipping Execution as the Application.

  8. Select the Report Name to be included in the document set.

    Selecting a report with PDF Output enables you to select a layout template. If you select a report without PDF Output, then the Layout Template field is not updatable.

  9. If you selected a report with PDF Output, then use the list of vales to select a Layout Template for your report.

    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 layout templates within Oracle XML Publisher:

  10. Enter the number of Copies that you want.

    If number of copies for a document is specified in the document set form, then copy count is used. If it is not specified (that is, it is null), then the profile option Concurrent: Report Copies is used. If the profile option Concurrent: Report Copies is also null, then 1 copy is printed.

  11. Save your work.

To edit document sets

  1. Navigate to the Shipping Document Sets window.

  2. Query an existing document set.

  3. Edit the existing Effective Dates, Sequence of documents, or documents contained within the document set.

  4. Save your work.

Choosing Printers for Shipping Documents and Labels

You can assign shipping documents and selected reports to specific printers for multiple levels. The levels are:

For example, you can assign pick slips and pack slips to your warehouse tractor feed printer, your mailing labels to a tractor feed printer stocked with blank labels, and other documents to a laser printer in your order entry office.

The window consists of a Document and a Printer tab: the Documents tab displays all the documents assigned to a printer, while the Printers tab displays all printers assigned to a document.

If a user or responsibility is not specified, Shipping Execution uses the printer assigned to the application.

To assign documents to a printer

  1. Navigate to the Choose Document and Label Printers window.

    Choose Document and Label Printers Window

    the picture is described in the document text

  2. Choose the Documents icon to display documents currently assigned to printers.

  3. Select the document from the Documents list.

    If the document is not listed, select New from the File menu to display documents not yet assigned to a printer. Select the document and click OK. The document is added to the Documents list and you can start assigning printers to it.

  4. In the Printer field, select the printer that you want assigned to the document.

  5. In the Level field, select the operational level for the printer. You can choose from the following:

    Format is used for Radio Frequency Identification (RFID) and Electronic Product Code (EPC) compliant label printing. EPC information is also included on the Departure Shipment Notice Outbound (DSNO) file. This option is used with Oracle Warehouse Management only.

    RFID EPC compliance enables the recognition and tracking of products using the RFID EPC label. Customers would use this feature before ship confirm at the line, box, or pallet level. The benefit is the ability to track the shipment before and after it leaves the shipper.

    See Oracle Warehouse Management User's Guide for more information on RFID EPC usage.

    Note: You must assign the shipping document to at least one printer at the Application level.

    Note: Use Zone/Subinventory and Format when Oracle Warehouse Management is installed.

    Note: There is one document printing exception. Pick Slip can be printed at the Subinventory level.

  6. Optionally, enter any comments.

  7. Click Enabled to activate the printer assignment.

  8. Enable the Default box if you want this printer as the default.

    Only one printer can be used as the default. For example, if a document is printed in multiple printers by one user, only one printer should be assigned as the default.

    Note: The default printer check box is visible only in the Document tab.

  9. Save your work.

To assign printers to documents

  1. Navigate to the Choose Document and Label Printers window.

    Choose Document and Label Printers Window - Printers Tab

    the picture is described in the document text

  2. Choose the Printers icon to display printers currently assigned to documents.

  3. Select the printer from the list.

    If the printer is not listed, select New from the File menu to display new printers. Select the printer and click OK. The printer is added to the Printers list and you can start assigning documents to it.

  4. In the Document field, select the document to be assigned to the printer.

  5. In the Level field, select the operational level for the printer. You can choose from Application, Site, Responsibility, User, Zone/Subinventory (with Oracle Warehouse Management), Organization, and Format (with Oracle Warehouse Management).

    See: Oracle Warehouse Management User's Guide

  6. Optionally, enter any comments.

  7. Enable the Enabled box to activate the document/printer assignment.

  8. Save your work.

Defining Pick Slip Grouping Rules

You can create grouping rules to organize how picking lines for released sales orders are grouped on to pick slips. For example, if you select Delivery as a grouping criteria, all picking lines for the same delivery are grouped together on a pick slip. If there are multiple deliveries, multiple pick slips are created.

You can also define your grouping criteria further by selecting additional grouping attributes. For example, if you select Delivery and Carrier as grouping criteria, picking lines for the same delivery and carrier are grouped together on a pick slip.

Related Topics

Oracle Inventory User's Guide.

Defining Release Rules

You can create default pick release rules that are applied at pick release in the Release Sales Orders window. Each rule can be set up with its own set of unique pick release parameters depending on the pick release criteria required.

When pick release is run, the pick release is performed based on the parameters set up in the selected pick release rule. For example, you can create a specific rule that pick releases only backordered lines.

Note: Although you can also enter the pick release criteria at pick release time without creating a rule, creating a rule is more efficient if you frequently run the same pick release. Also, note that it is required when releasing using SRS or when using the Auto Pick Pack and Ship features.

To define release rules

  1. Navigate to the Release Rules window.

    Release Rules Window - Order Tab

    the picture is described in the document text

  2. Enter a Rule name and the Effective dates.

    Within the Order tab, select one or more of the following criteria for your query. Select only the criteria that you want for the pick release:

  3. Select the Orders and Order Types that you want included in the pick release:

  4. Enter the Order Number.

  5. Select the Ship Set.

  6. 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 client setup.

  7. Optionally, select the Prior Reservations Only check box if you only want to pick release already reserved quantity for lines. This is allowed only for the allocation method of Inventory Only.

  8. Select the Destination Type:

  9. Select the Customer and the Ship-To location for the customer.

  10. Within the Item region select a Category Set, Category, and Item Number

  11. Select the range of Scheduled Ship Dates and/or Requested Dates.

    You can indicate whether you want the system to look at the scheduled ship date or the requested date. You can then enter the number of days in the past or future, as well as the time, relative to current system date that you want included in the release criteria. This means that it is possible to set up a desired release window in terms of number of days rather than only static dates. If your organization has a calendar assigned, then the release rule will honor non-working days (for example, Saturday, Sunday) to select delivery lines for pick release. If the rule shown were applied to Organization V1 and that Organization has Saturday and Sunday as non-working days on their organization calendar, then the following would occur: If pick release is run on Thursday, the delivery lines for Thursday, Friday, Monday, and Tuesday (system date + 3 working days) are selected for pick release. A negative value may be used in the Days field to include past dates which enables backordered lines to be considered for pick release.

    Alternatively, you can create a pick release rule using static dates by selecting the options Start On and End On in the Scheduled Ship Dates region and the Requested Dates region.

    Release Rules Window - Shipping Tab

    the picture is described in the document text

  12. Select the Ship Method to pick release by a certain ship method.

  13. Select the Shipment Priority, and Ship From location.

  14. Enable the Include Assigned Lines box if you want to include assigned lines in the pick release.

  15. Select a Document Set to be printed during pick release.

  16. Select a Release Sequence Rule if required.

  17. From the list of values, select either Yes or No to Autocreate Deliveries.

  18. If you selected Yes to Autocreate Deliveries, then in the Autocreate Delivery Criteria field select either Across Orders or Within an Order.

  19. Select either Yes or No in the Auto Pick Confirm field. Auto pick confirm is not allowed for the allocation method of Cross Dock.

  20. From the Autopack Deliveries list of values, select No if you do not want to utilize autopacking, select Yes to enable autopacking, or select Auto Pack Master if you want to utilize autopacking the item into its primary container and additionally automatically packing the primary container into a defined master container.

    You must setup container-item relationships to support the functionality for auto pack or auto pack master. See: Oracle Inventory User's Guide.

  21. Select a Ship Confirm Rule, if you want to utilize auto ship confirming.

  22. Select Yes or No to Append Deliveries (consolidate delivery lines.)

    Note: The appending limit must be defined as a value other than Do Not Append in the Shipping Parameters window before you can append deliveries within a release rule. Additional prerequisites for setting Append Deliveries flag include:

    Release Rules Window - Inventory Tab

    the picture is described in the document text

  23. Select the Warehouse (organization code) and default Pick Slip Grouping Rule for grouping the pick slips.

  24. Optionally, enter a specific Subinventory for your rule.

    This value determines which lines are considered for picking based on the subinventory name assigned to the sales order line.

  25. If Oracle Project Manufacturing is installed, specify a Project and Task for your rule.

  26. If Oracle Warehouse Management is installed, then you can select an Allocation Method to be used:

    The Allocation Method field cannot be updated unless Oracle Warehouse Management is installed.

    See: Oracle Warehouse Management User's Guide and Oracle Warehouse Management Implementation Guide for more information.

  27. If Oracle Warehouse Management is installed and if you selected Cross Dock Only or Prioritize Cross Dock in the Allocation Method, then select a Cross Dock Criteria.

    Enables a rule to be named, which limits the cross docking criteria. This field is disabled if the organization is not WMS Enabled, or the Allocation Method is Inventory Only.

    See: Oracle Warehouse Management User's Guide and Oracle Warehouse Management Implementation Guide for more information.

  28. Select Auto Allocate if you want to allocate the order lines automatically at pick release.

    If Auto Allocate is selected, order lines are automatically allocated and reserved. If not selected, you must allocate the lines and create reservations using the Inventory Transact Move Orders window.

  29. Select either Yes or No to Enable Plan Tasks if Oracle Warehouse Management is installed and you choose to utilize the Plan Tasks feature.

  30. Enter a Task Priority.

  31. Select whether you want to include order lines with the status of pull replenishment.

    Note: You cannot select the pull replenishment value if the Allocation Method value is Cross Dock Only or Prioritize Inventory. For more information, see the Oracle Warehouse Management User's Guide, Multi-Step Putaway and Replenishment.

  32. In the Pick From region, select the Subinventory and Locator of the default picking location.

    Pick From Subinventory determines where the line items are picked/allocated from.

  33. In the Default Stage region, select the Subinventory and Locator of the default staging area.

  34. Save your work.

Defining Release Sequence Rules

You can define release sequence rules to specify the order in which eligible picking lines are allocated to Inventory during pick release. You can release the picking lines by:

You can assign a priority level to one or more attributes with 1 being the highest priority and 5 being the lowest. You can also define whether you want the picking lines released in ascending or descending order.

For example, if you select the Ascending button for Order, picking lines are released by ascending order number--Order 1 is released first, then Order 2, Order 3, and so on. If the Descending button is selected, the picking lines are released by descending Order number from highest to lowest--Order 4 is released first, then Order 3, Order 2, and Order 1.

Note: You can define either the Outstanding Invoice Value attribute or the Order attribute for the release sequence rule, but you cannot select both for the same rule. No two attributes can be given the same priority.

You can edit existing release sequence rules, but you cannot change the name of an existing release sequence rule.

To define release sequence rules

  1. Navigate to the Release Sequence Rules window.

    Release Sequence Rules Window

    the picture is described in the document text

  2. In the Rule field, enter a name for your rule.

  3. Enter a Description.

  4. Enter the Effective Dates for the rule.

  5. Within the Release Priority region, specify a Priority (1, 2, 3, 4, or 5 where 1 is the highest priority and 5 is the lowest) for one or all of the following attributes:

  6. Select the Ascending or Descending toggle next to each attribute.

    If you select the Ascending toggle next to the Scheduled Date attribute, for example, the picking lines with the earliest Scheduled Date are released first. If you select the Descending toggle, the picking lines with the most recent Scheduled Date are released last.

  7. Save your work.

Defining Transportation Calendars

You can use a transportation calendar to define valid shipping days and hours for a shipper, receiver, and carrier. Using these calendars is optional.

The shipping and receiving calendars are used to designate when your customers, customer sites, suppliers, supplier sites, and internal organizations can ship and receive.

Note: The ship confirm process uses these calendars to warn you of invalid shipping days and hours.

The calendars do not affect scheduling performed by Oracle Advanced Planning and Scheduling.

For example, if you are shipping a delivery on Tuesday to arrive at your customer's site on Wednesday, ship confirm checks the calendars to confirm the following:

Note: If the transportation calendars are not defined, every day and time is assumed to be valid for shipping and receiving.

During Ship confirm, the application validates the actual departure against the following:

Prerequisites

A calendar must be created and defined in the Oracle Bills of Material (BOM) application as a Workday calendar before it can be assigned to a shipper, receiver, or carrier.

Note: The start and end dates for the calendar and the location's shipping and non-shipping patterns must be defined.

To define a transportation calendar

  1. Navigate to the Assign Calendars window.

    Assign Calendars Window

    the picture is described in the document text

  2. Select the role of the Trading Partner: Supplier, Customer, Organization, or Carrier. For example, if the trading partner is a customer, then click Customer.

    If you selected Carrier as the trading partner, you must select whether the carrier is used for pick up/delivery to a supplier, customer, or organization and then select the name of the supplier, customer, or organization in the Used For fields.

  3. Select the Trading Partner Name to whom you are assigning the calendar.

  4. Select the Calendar Usage.

    The calendar usage depends on the trading partner you selected. For example, if the trading partner is receiving your goods, create a Receiving Calendar.

  5. Select the Default Calendar Code.

    You can override the default calendar code by selecting a new calendar code for each site as described below.

  6. Click Show Candidates to display the sites for the selected trading partner.

  7. If you want to override the default calendar code, then select the new calendar code in the Calendar Code field.

  8. Select the Enabled box to activate the calendar for that site.

  9. Save your work.

Defining Shipping Exceptions

During the shipping and transportation of goods, unforeseen shipping exceptions can occur that conflict with the actual requirements of the shipper, transportation carrier, or customer.

If these exceptions are not handled promptly or properly, it could result in reduced customer satisfaction and loss of business and revenue for a company. Tracking exceptions can also be helpful to identify and correct defects in the business process.

The seeded exceptions are logged automatically against delivery lines, LPNs, deliveries, and trip stops when specific events occur. The events are shown in the descriptions below:

Seeded Exceptions
Exception Name Description
WSH_BATCH_MESSAGE Logged against a delivery, trip stop, or batch to store the messages generated during the automated shipping processes such as auto-pack and ship-confirm. The seeded value is INFO. If this is changed to ERROR, the exceptions generated, even though they are coded as ERROR, will not stop a shipment. It is suggested that you leave this exception as INFO to avoid any confusion.
WSH_CARRIER_CREATE_DEL Failed to auto apply routing rules at delivery creation.
WSH_CHANGED_QUANTITY Logged when quantity is changed and line is staged OR packed OR a planned delivery. Reasons can be:
WSH_CANCELED_PACKED
WSH CANCELED_PLANNED
WSH_CANCELED_RELEASED
Exception can be logged against delivery or container or line itself.
If the line is packed, then the exception is logged against the LPN record.
WSH_CHANGED_SHIP_METHOD Logged if the Document Category for generating a bill of lading is defined so that a different document numbering sequence is established for each ship method (i.e. Ship Method radio button for One is selected). If so, the exceptions is logged against trip when changing ship method of trip causes delivery legs' BOL numbers to become deleted.
WSH_CHANGE_DEL_GROUP Logged against delivery or LPN when a delivery grouping attribute (mandatory or enforced) is changed that causes the delivery line to become unpacked from its LPN or unassigned from delivery or both.
WSH_CHANGE_SCHEDULE Logged against delivery or LPN when the organization is changed or when order line is unscheduled and the delivery line is released to warehouse or staged and is assigned to delivery or LPN or both.
WSH_CHANGE_SCHED_DATE Logged against delivery line when order line's scheduled date is moved into future. Rationale: we do not want to ship the line early.
WSH_CUSTOMER_MERGE_CHANGE Logged against delivery when a customer merge occurs that affects delivery details within the delivery for one of the merge customers. The exception could be caused by a change in Ship To address.
WSH_DELIVERY_APPENDED Logged if an appending delivery takes place. This exception is logged only if appending has taken place on a delivery created in a previous batch.
WSH_DEL_SCPOD_PURGED Logged when the Ship to Delivery workflow has been purged.
WSH_EXPORT_COMPL_FAILED Logged when the export compliance screening failed for the delivery.
WSH_EXPORT_COMPL_SKIP Logged when the export compliance screening is skipped for the delivery.
WSH_HONOR_PICK_FROM Logged when pick release completes with a Warning.
WSH_IB_DELIVERY_CHANGE Logged whenever ship to location is changed on the purchase order and the delivery details are assigned to a delivery, or whenever shipping control is changed from Buyer to Supplier on the purchase order and the Routing Response has not been sent, or whenever the requested quantity for assigned delivery detail is changed on the purchase order and the Routing Response has been sent and the delivery firm status is Contents Firm.
WSH_IB_DEL_ATT_CHANGE Logged against a delivery, whenever the exception WSH_IB_DETAIL_CHANGE is logged against an assigned delivery detail line.
WSH_IB_DEL_DATE_EXCP Logged against a delivery whenever the earliest delivery detail line date is greater than the ultimate drop off date of the delivery, or the latest delivery detail line date is less than the ultimate drop off date of the delivery.
WSH_IB_DETAIL_CHANGE Logged against delivery details whenever Ship To location is changed and Routing Response has been sent, or whenever request date is changed on the purchase order and Routing Response has been sent, or whenever Requested Quantity is changed on the purchase order and Routing Response has been sent.
WSH_IB_RR_NUMBER_CHG Logged when a routing request number has changed during Vendor Merge.
WSH_IB_SF_LOCN_CODE_CHG Logged when Ship From Location code has changed during Vendor Merge.
WSH_IB_TS_DATE_EXCP Logged against Trip Stops whenever the earliest delivery detail line date is greater than the planned arrival date of the trip stop or the latest delivery detail line date is less than the planned arrivals date of the trip stops.
WSH_INVALID_DELIVERY_PLANNING Logged if WSH cancels/deletes delivery line that is in a planned delivery (This could happen because order line is canceled, or its quantity is reduced).
WSH_INVALID_PACKING Logged against LPN when a delivery grouping attribute (mandatory or enforced) is changed that causes the delivery line to become unpacked from its LPN.
WSH_INVALID_PACKING_PLANNING Invalid Packing Contents Firming: Contents Firmed packing has changes.
WSH_INV_EXPECTED_ERROR Logged from Pick Release when Inventory returns error.
WSH_LAUNCH_WF_FAILED Logged when Ship to Deliver workflow could not be launched for the entity.
WSH_LOCATION_REGIONS_1 Location regions mapping failure - no non-country regions mapped to location.
WHS_LOCATION_REGIONS_2 Location regions mapping - number of regions mapped to locations has changed.
WSH_PARTY_MERGE_CHANGE Logged when there are changes to a delivery detail due to party merge.
WSH_PICK_BACKORDER Logged against batch during Pick Release for any of these cases:
Other lines in Ship Set/SMC being backordered due to one line being backordered.
Other lines in Ship Set/SMC being backordered due to insufficient quantities for one line.
Normal line being backordered.
WSH_PICK_HOLD Logged against the concurrent request ID or the batch during Pick Release when holds are found.
WSH_PICK_PRIOR_RSV Logged against the delivery lines if Prior Reservations is specified during Pick Release but quantity is not reserved or Ship Set or Ship Model Complete line is partially reserved.
WSH_PICK_XDOCK Logged when supply is not found at picking time.
WSH_PICK_XDOCK_NR Logged when a non-reservable line is skipped for cross-docking.
WSH_PLAN_DELIVERY_FAIL Logged when the system failed to firm contents of the delivery at end of append delivery.
WSH_PR_REQ_EXPORT_COMPL Delivery requires export compliance screening before ship confirmation.
WSH_PR_SUB_EXPORT_COMPL Delivery submitted for export compliance screening before ship confirmation.
WSH_RATE_CREATE_DEL Logged when the system failed to calculate the freight rate at delivery creation.
WSH_RATE_MIXED_TRIP Logged when a trip has deliveries both eligible and ineligible for freight rating.
WSH_ROUTE_TRIP_FAIL Logged when there are no routing guide rules found for the trip.
WSH_SC_REQ_EXPORT_COMPL Delivery requires export compliance screening at ship confirmation.
WSH_SC_SUB_EXPORT_COMPL Delivery submitted for export compliance screening at ship confirmation.
WSH_SHPST_IGNRE_FR_PLNG Logged when Ignore for Planning status for the line is different than other ship set lines.
WSH_UNPACK_ITEM This is a packing exception.

You can also define unique exceptions and processes for exception handling in the Define Shipping Exceptions window.

To define shipping exceptions

  1. Navigate to the Define Shipping Exceptions window.

    Define Shipping Exceptions Window

    the picture is described in the document text

  2. Enter a unique Exception Name to identify the exception.

  3. Enter a Description.

  4. Select the Exception Type that you want to create: Batch, Delivery, Picking, or Trip exception.

  5. Select one of the following default Exception Behavior settings:

  6. Enable the exception.

  7. Select Raise Business Events to use Oracle Workflow for notification and exception handling.

  8. Save your work.

Defining Containers and Vehicles

You define containers and vehicles in Oracle Inventory, as inventory items.

To define containers and vehicles in Oracle Inventory

  1. Navigate to the Items window.

  2. In the Inventory tabbed region, select Transactable.

  3. Within the Physical Attributes tab, Container region, complete the following:

  4. Within the Physical Attributes tab, Weight region and Volume region, enter the Unit of Measure and Unit Weight of the empty container.

Defining Container-Item Relationships

When setting up container-item relationships, you define the maximum quantity of load items (delivery lines) that can be packed into a container: for example, defining that a maximum of 12 items can be packed into a small box. These relationships are used to:

In addition to packing delivery lines in containers, Oracle Shipping Execution features an Auto-pack Master function that enables you to auto-pack delivery line items into containers, and then auto-pack these containers into master containers such as pallets or railway boxcars.

The innermost container is considered the detail container item, and the pallet or boxcar is the master (outermost) container. If you want to use the auto-pack master feature, you must set up a relationship that relates the container (the load item) to a master container such as a pallet (the container item).

In the following example, auto-pack master would create one box for up to five engines and pack up to four boxes onto a pallet.

Auto-Pack Master Example
Load Item Container Item Max Load Qty Preferred
Engine Box 5 Y
Container Pallet 4 Y

To define container-item relationships

  1. Navigate to the Container-Item Relationships window.

  2. Select the Container Item from the list of values.

  3. Select the load item that you want to place in the container item.

  4. Define the maximum quantity of items that can be placed in the container item.

  5. If the container-item relationship is a common shipping configuration in that inventory organization, then select the Preferred flag.

  6. Save your work.

Related Topics

Auto-packing delivery Lines into Containers, Oracle Shipping Execution User's Guide.

Finding Container-Item Relationships

You can search existing container-item relationships to find:

For example, a shipper may search for container-item relationships to find what load items packed in a certain type of container, or the type of container used to pack a particular load item.

If one or more relationships for the selected item, container, or container type are found, the relationships display in the Container-Item Relationships window.

The Preferred Flag box in the Container-Item Relationships window indicates the preferred relationship that is used when auto-packing LPNs. See: Auto-packing delivery Lines into Containers, Oracle Shipping Execution User's Guide.

To find container-item relationships

  1. Navigate to the Container-Item Relationships window.

  2. Click the Find icon to display the Find Customer-Item Relationships window.

  3. Enter only the criteria required for your search:

  4. Click Find to display the relationships in the Container-Item Relationships window.

  5. Optionally, click New to create a new container-load relationship.

Using LPNs/Containers in Shipping Execution

There are a number of ways that you can pack items into License Plate Numbers (LPNs)/containers. Auto-Pack enables you to automatically pack items into specific types of containers. Auto-Pack Master enables you to automatically pack items into a specific LPN/container type and automatically pack the LPN/container into another type of LPN/container. You can manually pack items into previously created containers. You can also pack items into previously created LPNs/containers using the Packing Workbench, that allows for packing equal quantities of lines into multiple containers and also for packing full quantities of lines into one LPN/container at a time.

Aside from the actual packing of line items into LPNs/containers, you can also:

Oracle Warehouse Management (WMS) handles other LPN/container functionality not available in Shipping Execution, including:

LPN/Container Setup Steps

Before you can begin packing lines into LPNs/containers, you need to perform the following setup steps, in the following sequence:

  1. Weights and volumes for the items that will be involved in the packing process. See: Oracle Inventory User's Guide.

  2. Container types See: Oracle Inventory User's Guide

  3. Vehicle types See: Oracle Inventory User's Guide

  4. Container-load relationships

  5. Shipping parameters

  6. Optionally define default Master and Detail containers for customer items

  7. Optionally, define LPN name defaults.

Defining LPN Name Defaults

You define LPN name defaults in Oracle Inventory organization parameters. See Oracle Inventory User's Guide for more information.

To define LPN name defaults

  1. Navigate to the Oracle Inventory Organization Parameters window, Revision, Lot, Serial and LPN tab.

  2. Within the LPN Generating Option region, enter the following:

Setup Container-Load Relationships for Containers and Items

You set up Container-Load Relationships if you intend to use auto-pack functionality. The relationship determines the product items that can be automatically packed into specified containers, and in what quantity.

To setup container-load relationships for containers and items

  1. Navigate to the Container-Item Relationships window.

    Note: The purpose of setting the container-load relationship is to establish a link between item and container type, or container and container. This allows the Auto-Pack and Auto-Pack Master functionality to perform automatic packing.

    Container Item Relationships

    the picture is described in the document text

  2. Select the Container Item.

  3. Select the Load Item.

  4. Define the Maximum Quantity of the of the Load Item that should be placed in the Container Item.

    Note: You can specify container-item relationships or container-container relationships.

    Continue creating container-load relationships for all containers and items you plan to use. Container-load relationships are used for packing whenever the Percent Fill Basis Shipping Parameter is set to Quantity and also when you use the Auto-Pack and Auto-Pack Master features to pack items into containers.

  5. Select the Preferred Flag toggle to use the container-load relationship as the preferred relationship between items and containers (and containers and containers).

    You could potentially have multiple load-relationships between items and different containers. When you select the Preferred Flag toggle for a container-load relationship, Auto-Pack and Auto-Pack Master will use the Preferred relationship when packing that item. For example, if you have two container-load relationships for Item A—one with Container A, which is the preferred LPN/container, and one with Container B—the maximum load defined in the relationship with Container A will be used when you select Auto-Pack or Auto-Pack Master for packing Item A. You must set the Preferred Flag for one of the Container-Load Relationships you have for an item in order to use Auto-Pack or Auto-Pack Master for that item. If you do not set the Preferred Flag for one of the relationships for an item, you will receive an error message.

  6. Save your work.

To define LPN/container related shipping parameters

  1. Navigate to the Shipping Parameters window.

    Shipping Parameters

    the picture is described in the document text

  2. Select the Percent Fill Basis. Select from Quantity, Weight, or Volume.

    This is used to determine whether or not containers have met their minimum fill percentage and also used to determine how autopack should work based on quantity, weight, or volume.

    For example, if you define a container-load relationship in which CONTAINER A can hold quantity 5 of ITEM A, you select Quantity in this field, and you define the minimum fill percentage for CONTAINER A to be 75 percent, you must have at least quantity 4 of ITEM A in CONTAINER A to meet your minimum fill percentage. If you select Weight or Volume, the Percent Fill is calculated based on the weight or volume (physical attributes) you have defined for your items.

    Shipping Parameters: Shipping Transaction

    the picture is described in the document text

  3. From the Shipping Transaction tab, set the Enforce Packing in Containers display list to Yes if you want Shipping Execution to display an error message during Ship Confirm when you try to ship a delivery that contains unpacked delivery lines.

    Note: You must define shipping parameters for each warehouse.

  4. Save your work.

    See: Oracle Shipping Execution User's Guide

    Oracle Inventory User's Guide

    Defining Shipping Parameters

Creating LPNs/Containers

You can automatically or manually create containers. Containers are created automatically when using the Auto-Pack and Auto-Pack Master functionality by using a defined Container-Load Relationship between a type of LPN/container and an item. Shipping Execution uses the container type, the item, and the defined maximum quantity of the item that will fit in the LPN/container and then automatically creates the required number of containers with automatically generated names. Grouping attributes are also taken into consideration when packing. See: Defining Delivery Parameters.

However, to manually pack items into LPNs/containers using the Pack and Packing Workbench functionality, you must manually create LPNs/containers.

To manually create LPNs:

  1. Navigate to the Shipping Transactions form and find your Lines.

  2. Select the action Create LPNs.

    Create LPNs Window

    the picture is described in the document text

  3. Enter your Organization.

  4. From the list of values, select the Container Item.

    The Container Item is the container itself. Container items are created in Oracle Inventory.

  5. Enter a Count for the number of container instances you want to create.

  6. Within the Name Generation region, enter your Name Prefix.

    The Prefix is defaulted if you specify it in the Prefix field within the Organization Parameters window/Revision, Lot, Serial and LPN tab.

  7. Enter a Base Number.

    The numbering starts from the base number and increments by 1. For example, if you enter 100 as the base number for the first instance of a container, the second is numbered 101, the third 102, and so on. The Base Number is defaulted if you specify it in the Starting LPN Number field within the Organization Parameters window/Revision, Lot, Serial and LPN tab.

  8. Enter the Pad to Width.

    The default Pad to Width is the total number of digits in the base number. For example, the default Pad to Width for the container name VIS100BOX is 3.

  9. Select the UCC-128 Suffix option if you want to enable the Uniform Code Council, 128 ASCII character set suffix functionality.

    If you select the UCC-128 Suffix option (selected is Yes, deselected is No), then you will not be able to specify the Name Suffix. The default suffix for UCC-128 is "No." The UCC-238 Suffix is defaulted if you enable it by selecting the UCC-128 Suffix (Modulo-10) check box within the Organization Parameters window/Revision, Lot, Serial and LPN tab.

  10. Enter a Name Suffix for the container name.

    The Name Suffix is defaulted if you specify it in the Suffix field within the Organization Parameters window/Revision, Lot, Serial and LPN tab.

  11. Click OK to create the container instances.

  12. Save your work.

    Once created, you can select the containers from a list of values that displays when you choose the Pack option in the Shipping Transactions form. You can also query up existing (created) containers using the Query Manager (via the LPNs or Lines and LPNs options).

Define Default Containers for Customer Items

This section does not apply to standard items. Use the information in this section if you are using customer items.

To define default containers for customer items:

  1. Navigate to the Customer Items Summary window.

    Customer Items Summary

    the picture is described in the document text

  2. Query your customer item and define default Master and Detail containers in the Containers tab.

    These containers will default in the Master and Detail fields in the Shipping Transactions form when you query the item associated with your customer item. When you Auto-Pack, these containers will be used to pack the items. If a container-load relationship is defined for the item and the detail LPN/container (and for the detail and master containers) and the Percent Fill Basis is set to Quantity, Shipping Execution will use the Container-Load Relationship to determine the required number of containers. If no relationship is defined, the weight and volume of the items and the maximum load weight or volume for the LPN/container will determine how the items are packed into containers (and containers into containers.)

  3. Save your work.

Packing Items into LPNs/Containers

You can pack items into LPNs/containers in the following ways:

Manual Packing

Manual packing involves packing items into LPNs/containers that have already been created using the Create LPN action in the Lines and LPNs tab in the Shipping Transactions form. Manual packing can be accomplished by selecting the line (in the Lines and LPNs tab in the Shipping Transactions form) that you want to pack into the LPN/container and selecting the Pack option from the Actions list, which displays a list of values containing previously created LPNs/containers.

Manual packing does not use a container-load relationship when packing, but the weight, volume, and percent fill (based on the setting for the Percent Fill Basis Shipping parameter) are calculated to determine whether or not the items will fit into the LPN/container. A warning message will display if the total weight and volume of the items is greater than the available capacity of the LPN/container. A warning will also display if the minimum fill percentage is not attained.

You might want to use this method of packing if you have several items (maybe pencils, paper clips, and pads of paper) that are heading to the same customer and the customer does not care about what type of LPN/container is used. So, you could query up your delivery lines in the Shipping Transactions form (using the Query Manager), multi-select your lines, choose Pack from the Actions list, and then select the LPN/container you have created from the resulting list of values.

Auto-Packing Standard Items

Auto-Pack is an option on the Actions list in the Lines and LPNs tab in the Shipping Transactions form that will automatically calculate and create the number of LPNs/containers required to pack all of the items and then pack all of the items into the created LPNs/containers.

Auto-Pack Master behaves identically to Auto-Pack except that it goes one step further and packs the created detail LPNs/containers into one or more parent (master) LPN/container. If you have multiple container-load relationships set up for the same item (with different LPNs/containers), Auto-Pack will look at the Preferred toggle on the Container-Item Relationships window to determine which relationship to use. You must define one of the container-load relationships for your items as the preferred relationship. If you do not toggle on the Preferred Flag for one of your container-load relationships, then you will receive an error when you try to use Auto-Pack or Auto-Pack Master for that item.

For any other type of item you are Auto-Packing, you must have a container-load relationship set up. If you try to Auto-Pack items into a LPN/container and no container-load relationship is established, then you will receive an error message. Auto-Pack will use the container-load relationship to determine the type of LPN/container needed to pack the item. The setting of the Percent Fill Basis Shipping parameter is used to determine how many containers are going to be needed to pack all of the items. If the Percent Fill Basis Shipping parameter is set to Quantity, then the Maximum Quantity defined for the container-load relationship (being used to determine the type of LPN/container) will be used to calculate the necessary number of LPNs/containers. If the Percent Fill Basis is set to Weight or Volume, then the physical attributes (weight or volume) that are defined for the item and LPN/container are used to calculate the total number of required LPNs/containers. Once the type of LPN/container is determined and the required number of LPNs/containers are calculated, Auto-Pack/Auto-Pack Master creates those LPNs/containers and systematically packs the items into the LPNs/containers. For example, let's say you had a Container-Load Relationship set up so that 6 of Item A fit into Container A and Percent Fill Basis was set to Quantity. If you have a delivery line with a quantity of 12 of Item A and you run Auto-Pack, Shipping Execution will create two LPNs/containers, split the line into two lines with a requested quantity of 6, and pack the first split line into the first container and pack the second split line into the second LPN/container.

Auto-Pack Master packs not only an item into a LPN/container (detail container in this scenario), but it will also pack the detail container into a master container. For example, you have a delivery line with a quantity of 12 of Item A and a container-load relationship set up so that 6 of Item A will fit into Container A and 2 of Container A will fit into Container B (and Percent Fill Basis is set to Quantity). If you run Auto-Pack Master, the line will be split into 2 lines of 6, the first line will be packed into the first LPN/container, the second line will be packed into the second LPN/container, and the two Detail Containers (2 Container As) will be packed into Container B.

Auto-Packing Customer Items

There are two different ways to specify the type of LPN/container to be used when using Auto-Pack or Auto-Pack Master: specify a Master and/or Detail LPN/container for a customer item, or set up a Container-Load Relationship between the item(s) and LPN(s)/container(s).

If you are Auto-Packing a customer item with a pre-defined Master and/or Detail association (set up in the Customer Item Summary window), then Auto-Pack will use those container types to create the LPNs/containers required and pack the customer item. To determine how many LPNs/containers are needed, Auto-Pack will use the Percent Fill Basis Shipping Parameter. If Percent Fill Basis is set to Quantity, Auto-Pack will look for Container-Load Relationships set up for the item and the Detail Container, as well as for the Detail Container and the Master Container. If these Container-Load Relationships are not set up, then Auto-Pack will use the weights and volumes for the item and the available capacities defined for the LPNs/containers.

For example, your customer preferred that you pack the monitors that you make into a cardboard box (one in each box) and that you pack twelve cardboard boxes (containing the monitors) on a pallet for shipment. You can assign the specific cardboard box (type of container) as the detail LPN/container for the customer item and the pallet as the Master Container for the customer item in the Customer Item Summary window. When the order is booked and the line is pulled into (imported into) Shipping Execution and viewed in the Lines and LPNs tab in the Shipping Transactions form, the cardboard box and the pallet container types will default into the Master and Detail fields for the line. When you run Auto-Pack for this line and Percent Fill Basis set to Quantity, Auto-Pack uses the Container-Load Relationship set up for the item and the LPN/container. If no Container-Load Relationship is set up, Auto-Pack uses the weight and volume and LPN/container capacity for the item and LPN/container to calculate the required number of LPNs/containers. Once the number of LPNs/containers is calculated, the LPNs/containers are created and the items are packed into the LPNs/containers. Then, the total number of Master LPNs/containers are calculated based on the number of Detail containers created, and the appropriate number of Detail LPNs/containers are systematically placed into the appropriate Master LPN/container. So, if you set up a Container-Load Relationship where a maximum of 1 monitor fit in 1 cardboard box and 12 cardboard boxes fit on one pallet and your customer ordered 24 monitors, the 24 monitors would be placed in 24 cardboard boxes (1 in each box) and then 12 cardboard boxes would be placed on each of the 2 pallets that were created.

Packing Workbench

The Packing Workbench allows for two different methods of packing:

  1. Equal Packing

  2. Full Packing

Equal Packing involves packing equal amounts of items from one or many lines into one or many LPNs/containers. Full Packing involves packing the entire quantity of one delivery line into one or many LPNs/containers, and then packing the entire quantity of the next delivery line into one or many LPNs/containers. If the entire quantity of the first line does not fill a LPN/container, items from the next delivery line will be added to the LPN/container with available space until it is filled.

To use the Packing Workbench, you must select the delivery lines and the LPNs/containers in the Lines and LPNs tab in the Shipping Transactions form that you want to pack and then select Packing Workbench from the Actions list. You must have queried up lines and previously created LPNs/containers or you must have queried up lines and then created new LPNs/containers. When selecting lines in the Shipping Transactions form to use in the Packing Workbench, you can use the Packing Calculator (accessed by clicking on the bar on the far right hand side of the Shipping Transactions Form or by selecting Packing Calculator from the Tools menu) to determine whether or not the lines might be able to fit in the LPNs/containers that you have selected. The Available Capacity region shows how much weight and volume the LPNs/containers that you have selected can hold and the Item Total region shows the total weight and volume for all of the lines you have selected.

Once you have selected your lines and LPNs/containers and have selected Packing Workbench from the Actions list, the Packing Workbench displays containing your selected LPNs/containers on one tab and your selected lines on the other tab. The total Available Capacity for the LPNs/containers and the weights and volumes for the items are displayed on the left side of the Packing Workbench. By default, the Pack toggle is next to your lines and LPNs/containers that are selected. If you turn the Pack toggle off for a LPN/container or line, then that line or LPN/container will not be used for packing and, hence, the Available Capacity and Item Total regions will be updated accordingly.

Equal Packing

The first method of packing within the Packing Workbench is Equal Packing. Equal Packing is explained using the following example: Your customer ordered 10 computer monitors and 10 keyboards. The order consists of two lines, one for 10 monitors and one for 10 keyboards. Once the order is booked, you can query your lines in the Shipping Transactions form. If you wanted to pack one of each item into a LPN/container, you would create 10 LPNs/containers (using a container type that was large enough to hold one of each item.) You would then select your two lines and your ten LPNs/containers and pull them into the Packing Workbench. Once in the Packing Workbench, select the Equal Packing Method and choose the Pack button. The Packing Workbench will split the two lines into ten lines for each item and pack 1 monitor and 1 keyboard into each LPN/container. So you will end up with 10 LPNs/containers that have 1 monitor and 1 keyboard in each.

There is a potential drawback to using Equal Packing. When you use Equal Packing, lines are split evenly so that equal quantities will be packed into the selected LPNs/containers. Container-Load Relationships and weight and volume limitations within containers are not used when packing the items equally into LPNs/containers. In other words, the lines are split and packed into the LPNs/containers prior to performing weight and volume validations. Validations based on weight and volume do take place to determine whether or not the LPNs/containers are over-packed (weight or volume exceeds maximum weight or volume for a LPN/container), resulting in the display of Warning messages, but not until after the lines are split. Once the lines are split, you cannot return the lines to their original status (if one line for quantity of 6 was split into two lines for quantity of 3, you cannot return the two lines into one line for quantity of 6). So, if you split the lines and find out that you really want to pack them differently, you will have to pack the resulting split lines rather than the initial pre-split lines.

Full Packing

Full Packing involves taking items in a delivery line and packing them completely into one LPN/container, then taking the next line and packing its entire quantity. If the items in the first delivery line do not completely fill the first LPN/container, the items in the second delivery line will be added to the first LPN/container until it is filled. If all of the items in the second delivery line were not used to fill the first LPN/container, then the remaining items are packed into the second LPN/container.

For example, you have two delivery lines, one consisting of 10 of Item A and one consisting of 10 of Item B, and you wanted to pack them into three LPNs/containers. If the Percent Fill Basis Shipping Parameter was set to Quantity, the Packing Workbench would use the Container-Load Relationship set up to determine the maximum number of items that could fit in the first LPN/container. If Percent Fill Basis was set to Weight or Volume, the Packing Workbench would use the weight and volume defined for the item and the maximum load weight or volume defined for the LPN/container to calculate the total number of items that could fit in the first LPN/container. Let's say Percent Fill Basis is set to Quantity and a Container-Load Relationship is established that says that 5 of Item A will fit in the first LPN/container. Five of Item A will be placed in the first LPN/container, then the Packing Workbench calculates the total number of Item As that will fit into the second LPN/container. If a Container-Load Relationship is set up so that 10 of Item A will fit in the second LPN/container, the Packing Workbench will place the remaining 5 of Item A in the second LPN/container. The Packing Workbench then calculates that the LPN/container is only fifty percent filled, so the Packing Workbench will look at a Container-Load Relationship set up for Item B and the second LPN/container. If the Container-Load Relationship for Item B and the second LPN/container was defined so that 4 of Item B will fit, the Packing Workbench takes fifty percent of the total defined Container-Load Relationship (2 of Item B) and packs that quantity into the second LPN/container. This leaves us with 8 of Item B. The Packing Workbench then looks at the Container-Load Relationship between Item B and the third LPN/container. If 10 of Item B fits into the third LPN/container, the Packing Workbench will pack the remaining 8 in the third LPN/container.

Additional LPN/Container Functionality

Assigning Serial Numbers to LPNs/Containers

You can assign serial numbers to your LPNs/containers. When you create your LPNs/containers in the Master Items window, you can define your LPNs/containers as requiring serial numbers by navigating to the Inventory tab and choosing At Sales Order Issue in the Generation field in the Serial region. Once you create your LPNs/containers in the Shipping Transactions form, you can assign serial numbers to your LPNs/containers. Since LPNs/containers are not transacted items (LPNs/containers are not stored in inventory), you are not required to enter a serial number even though the LPN/container is serialized.

If you assign a LPN/container (Detail Container) to another LPN/container (Master Container), the serial number of the Master Container will automatically default into the Master Serial Number field for the Detail Container. If you change the serial number for the Master Container, which will automatically change the Master Serial Number for the Master Container, Shipping Execution will automatically update the Master Serial Numbers for all Detail Containers assigned to that Master Container.

Generating a Loading Sequence for Deliveries/Containers

You must have imported order lines with a defined Production Sequence Number or you must have entered a Customer Production Sequence Number in Others tab in the Lines region of the Sales Orders window. Generating a loading sequence is optional. You would only generate a loading sequence when you wanted to place items in a LPN/container or on a delivery in a certain order. For example, if an automotive manufacturer's assembly line needed specific items in a certain order, they might want to have items shipped to them placed in a certain order in the LPN/container or delivery so that they could remove the items in the most efficient order for their assembly line. The loading sequence is printed on the Vehicle Load Sheet Detail report.

To generate a loading sequence for deliveries/containers:

  1. Navigate to the Shipping Transactions form.

  2. Select the Delivery tab (a delivery must exist).

  3. Click Details.

  4. In the Lines Loading field, select a loading pattern.

    You can select from Forward (1, 2, 3, 4), Reverse (4, 3, 2, 1), Forward Inverted (2, 1, 4, 3), and Reverse Inverted (3, 4, 1, 2).

    Loading sequence determines the order in which the delivery lines are placed in the LPN/container or the delivery, depending on whether or not you have defined a Detail Container for the delivery line. If you have specified a Detail Container, the loading sequence determines the order in which the delivery line is placed into the LPN/container. If you have specified a Master Container or if you have not specified any LPN/container for the delivery line, the loading sequence will determine the order in which the delivery line will be placed in the vehicle.

  5. Select the action Generate Loading Seq.

    If you have ITEM A with a Production Sequence Number of 1 and ITEM B with a Production Sequence Number of 2 and you select Reverse as your Lines Loading order, ITEM B would have a Loading Order Number of 1 and ITEM A would have a Loading Order Number of 2 (ITEM B would be loaded first and ITEM A would be loaded second).

    If a Customer Production Sequence Number is not assigned to the delivery line, you can enter a Loading Sequence to determine the order in which the delivery line will be loaded into the LPN/container or delivery.

International Trade Management Partner Integration

You use the International Trade Management (ITM) application if you conduct business across international borders and need to ensure that your cross-border trade complies with the export and import rules, regulations, and duties of all countries involved in the transaction (trade compliance).

To provide export compliance and resolve regulatory screening issues, Oracle Applications enables you to use International Trade Management Adapter to communicate with ITM applications that are skilled in the laws of import/export and in acquiring and maintaining this information. With the ITM integration, there is global trade functionality in the standard business transactions.

Oracle Order Management provides a workflow subprocess called Export Compliance Screening - Line that you can insert into your workflows to execute the ITM functions. This workflow subprocess is part of the seeded Line Flow - Generic, With Export Compliance workflow process.

ITM Partner Integration Enhancements Oracle Order Management introduces Generic Export Compliance Request via XML for all the export related compliance checks. These include Restricted Party Screening, Embargo Country Screening, License Determination, Document Generation as well as other partner supported screening such as EPCI.

The partner ITM application evaluates the transaction for export compliance and responds to Oracle Applications with the overall compliance pass or fail status for each of the order lines. The audit trail of the compliance checks is maintained in the partner ITM application.

An eBusiness Suite installation can integrate with a 3rd party vendor's ITM application or 3rd party vendor's / Oracle's Global Trade Management (GTM) application. You cannot integrate with both of these applications (ITM and GTM) at the same time.

Setting Up Constraints

There is a constraint that does not allow user-splits if the line is interfaced to the ITM adapter (Export Compliance Screening activity notified) and is waiting for response. This constraint is seeded by default and cannot be removed in order to prevent the second line split from hanging in Workflow.

Additional constraints at the line level do not allow changes to ship-from, ship-to and all other parties such as Sold to, Bill to, or Deliver to. These constraints are non-system constraints that can be disabled.

Setting Up Workflows

If you plan to use the Generic Export Screening feature, then complete one of the following:

To set up workflows:

  1. For the Order Types and Line Types that you want to perform export screening, assign the line level export screening workflow process Line Flow-Generic, With Export Compliance.

  2. Enable the Export Compliance Screening – Line sub-process into existing line level workflows.

    See: Oracle Shipping Execution Implementation Manual for information on setting up the ITM Adapter.

    Export Compliance Screening Line

    the picture is described in the document text

Export Compliance Screening—Line subprocess can be used in the line level workflow process to perform Export Screening. The subprocess should be placed after scheduling so that the Ship from Organization (warehouse) is already determined. You can plug-in the subprocess based on your business needs.

Line Flow: Generic, With Export Compliance

the picture is described in the document text

Line Flow-Generic, With Export Compliance" is a seeded line flow with the "Export Compliance Screening - Line" activity placed after Scheduling. You can plug in the Export Compliance Screening —Line subprocess into existing line workflows.

Services

Note: The XML tag Order Number is included in the Request XML generated when deliveries are screened for delivery export compliance in ITM.

Concurrent Processing

The concurrent processes submit transactions to the Oracle ITM Adapter. The Oracle ITM Adapter then communicates the transactions to the partner ITM application.

Processing

Oracle's ITM adapter provides a common infrastructure between Oracle e-Business Suite Applications and International Trade Management partner applications.

To use the ITM adapter, populate the adapter interface tables through an API that submits a service request to the adapter. The adapter generates XML transactions for submission to a partner at the appropriate time in your business process.

The adapter can also use your custom processing logic after it performs its usual transaction processing. You can group requests by assigning them to the same request set; the Adapter performs your custom process after it processes all transactions in each request set.

The partner:

The adapter receives the statuses and responses and places them in the response interface tables.

The response processor API interprets the messages and takes actions. It sets the request status based on the highest level message that it finds. The hierarchy of message levels, from highest to lowest, is SYSTEM, DATA, ON_HOLD, and SUCCESS. The error type is always ITM Adapter.

After analyzing the error responses in a report, you can:

Setup Process

Prior to performing international trade management setup, decide:

To set up for international trade management functions, you must:

ITM Lookup Codes

You define lookups, in addition to the seeded ITM lookups, that provide custom values for lists of values within the Oracle ITM Adapter setup windows. ITM lookup codes provide a way to include additional attributes on the outbound compliance request XML messages. For example, if your partner ITM application requires a certain element on the message, you can define a value in lookup code at the appropriate level. The seeded lookups for the Oracle ITM Adapter include the following:

To add additional ITM lookups

  1. Navigate to the Oracle Shipping Lookups window.

  2. Enter a lookup Type and Meaning.

  3. Use the list of values to select the Application Oracle Shipping.

  4. Optionally, enter a Description.

  5. Enter a unique Code for your lookup.

  6. Enter a Meaning and Description for your lookup code.

  7. Optionally, enter a Tag number.

  8. The From Effective Date will default to the current date.

    You can modify this field to another future date if needed.

  9. Optionally, enter a To Effective Date that will disable your lookup.

  10. Verify that the Enabled check box is selected.

  11. Save your work.

International Trade Management Partners

Use this form to master information about international trade management partners. You enter three types of information about a partner:

To set up international trade management partners

  1. Navigate to the ITM Partners window.

    ITM Partners Window

    the picture is described in the document text

  2. Enter your ITM Partner.

  3. In the Website field, enter the uniform resource locator of the partner's web site.

  4. Enter the name of your Contact Person.

  5. Enter the Email address of your contact person.

  6. Save your work.

  7. Within the Services tab, select a service that the partner provides in the Service Type column.

  8. In URL, enter the uniform resource locator (web site address) of the site to which you post the request.

  9. In Port, enter the web server listener port number of the uniform resource locator to which you post the request.

  10. Select the Protocol.

  11. If the protocol is HTTPS:

  12. Save your work

  13. For each service, click Service Parameters.

    ITM Service Parameters Window

    the picture is described in the document text

  14. Enter the Name of the service parameters.

  15. Enter the Value for each service parameter.

    International Trade Management partner may specify the additional service parameters that they need in the compliance request XML that you submit to them.

  16. Click Done and navigate to the Partner Parameters tabbed region.

    ITM Partners Window

    the picture is described in the document text

  17. Enter the Name of the partner parameters.

  18. Enter the Value for each partner parameter.

    Each International Trade Management partner specifies the additional partner parameters that they need in the requests that you submit to them.

  19. Save your work.

International Trade Management Users

Use this window to set up the login information for the partners. You can set up a user for an Application User ID, for a master organization, for an individual organization. A more specific setup overrides a more general setup. For example, a request from an organization with a specific setup uses that specific setup while a request from an organization without a specific setup uses the setup of the master organization to which it belongs.

To set up international trade management users:

  1. Navigate to the ITM Application Users window.

    ITM Application Users Window

    the picture is described in the document text

  2. Select the ITM Partner.

  3. Select the Application that sends requests to this partner (the calling application), for example, Oracle Order Management.

  4. Enter the Master Organization whose organizations send requests to this partner. For Oracle Exchange, enter Operator ID.

  5. Enter an Organization that sends requests to this partner. For Oracle Exchange, enter Party ID.

  6. In Application User, enter an existing Oracle Applications user name that sends requests to this partner.

  7. In ITM User Name, enter the user name that the partner provides for your access to the partner system. The user name can be up to 35 characters and numbers.

  8. In Password, enter, twice, the password that the partner provides for your access to the partner system. The password should be at least five characters.

  9. Save your work.

International Trade Management Partner Service Types

Use this window to specify your preference of partners who provide international trade management services to you.

To set up international trade management partner service types:

  1. Navigate to the ITM Partner Service Types window.

    ITM Partner Service Types Window

    the picture is described in the document text

  2. Select an Application from which you make service requests.

  3. Select a Master Organization from which you make service requests. For Oracle Exchange, enter Operator ID.

  4. In ITM Partner, select a partner that provides a service.

  5. In Service Type, select a service that the partner provides.

    Enter one line of information for each service and partner that you use. If you use more than one partner for a service, enter each partner-service combination on a separate line.

  6. Select Active to indicate that you can submit this type of service request to this partner.

    Note: Clear Active to indicate that you do not want to submit this type of service request to this partner. You can have only one Active partner for each service at one time.

  7. In Priority, indicate the processing priority of this service type with this partner in relation to other partners and services. Select a number from one (highest priority) through five.

International Trade Management Adapter Parameters

Use this window to set up adapter parameters. After you set up or change parameters, stop and start the Adapter (ShutDown ITM Adapter concurrent process and StartUp ITM Adapter concurrent process).

To set up international trade management adapter parameters

  1. Navigate to the ITM Parameter Setup window.

    ITM Parameter Setup Window

    the picture is described in the document text

  2. The valid values are seeded, you cannot create new parameters. You can change the parameters whose Override Allowed checkbox is selected.

  3. Highlight the parameter that you want to change.

  4. In Description, read instructions for the parameter.

  5. In User Defined, enter your changed information.

  6. Save your work.

Adapter Parameters

The Oracle ITM Adapter functions based on parameters. The parameters include the following:

International Trade Management Response Rules

The partner ITM application evaluates the delivery for export compliance and responds to Oracle Applications with the overall compliance Pass or Fail status for the delivery. The export compliance is evaluated for delivery as a whole. If a delivery is found to be compliant by the partner application, it responds back to Oracle Application with compliant (Pass) status. The asynchronous response is received by the Oracle XML Gateway and a synchronous acknowledgement is provided to the partner application.

If a delivery is determined to be non-compliant (Fail), then the ITM adapter logs the exception Not Compliant for Export against the delivery. You need to manually cancel these deliveries depending upon your business processes. In case, the ITM application is unable to evaluate the compliance of a delivery programmatically, the ITM application notifies the compliance users for a manual compliance review. No response is communicated back to Oracle Application until a final compliance determination is made by the compliance user.

Use response rules to translate error types and error codes from the partner responses.

To set up international trade management response rules

  1. Navigate to the ITM Response Errors Classification window.

    ITM Error Classification Window

    the picture is described in the document text

  2. In ITM Partner, enter a partner.

  3. Enter an Error Type and Error Code.

  4. In Interpreted Value, select the interpreted value for the combination of the error code and error type:

  5. Save your work.

Regions and Zones

If you have the Oracle Advanced Planning and Scheduling Suite installed, use regions and zones to group by geographical areas and save the effort of setting up point-to-point transit times.

You can perform the following:

The Oracle Advanced Planning and Scheduling Suite uses this origin-destination information to plan and schedule shipment departure dates, arrival dates, and sourcing.

Region and zone terms are:

When the Oracle Advanced Planning and Scheduling Suite plans shipments, it assumes that the transit time from your facility to all locations within the zone is the same. For example:

The advantages of planning shipments in terms of regions and zones are:

Order Processing

When calculating available-to-promise, the Oracle Advanced Planning and Scheduling Suite uses regional transit times.

When scheduling shipments using zones and regions, the Oracle Advanced Planning and Scheduling Suite:

Setting Up Regions and Zones

If you ship to multiple locations that are near to each other and you want to plan shipments by regions and zones:

Use two concurrent processes to map and load bulk geographical information. Use the forms for individual data entry and data correction.

Setting Up Region and Zone Information

Use the following procedures to set up region and zone information through forms and through concurrent processes.

To set up region and zone information

  1. Navigate to the Regions and Zones window, Regions tabbed region.

    Regions and Zones Window

    the picture is described in the document text

  2. Enter the following information as available.

    Note: The Sub-Regions button is active only after you have saved a new region or when you are querying an existing region.

  3. When you enter a region, you can specify only one new component.

    For example, if you enter country China, province/state Guangdong, and city Guangzhou, you must already have entered the region country China, province/state Guangdong. Use the list of values if you are unsure about existing information for each field.

    Note: After you query previously created regions, you can use the Locations button to view all locations for a selected region. With the cursor on the selected region, click the Locations button to display locations for that region.

  4. Save your work.

To update regions

  1. Navigate to the Regions and Zones window, Regions tabbed region.

  2. From the menu bar, select Query > Enter.

  3. Enter search criteria.

  4. From the menu bar, select Query > Run and view regions that match your search criteria.

  5. Select one of the regions that displays and update the information.

  6. Save your work. If you have changed a parent region, the region becomes assigned to a new parent.

To add and update sub-regions

  1. Navigate to the Regions and Zones window, Regions tabbed region.

  2. From the menu bar, select Query > Enter.

  3. Enter your search criteria.

  4. From the menu bar, select Query > Run and view regions that match your search criteria.

  5. Select one of the regions that displays and click Sub-regions.

    Sub-Regions Window

    the picture is described in the document text

  6. View existing sub-region information and add or change information

    When you enter a sub-region, you can enter only one component and the region must exist. For example, you cannot change the region country United States and province/state California and the sub-region city San Diego in one entry. Instead:

To add zones

  1. Navigate to the Regions and Zones window, Zones tabbed region.

    Regions and Zones Window - Zones Tab

    the picture is described in the document text

  2. Enter a Zone name.

  3. In the Zone Components region, enter information about the regions that you are assigning to the zone. You cannot assign a region and its parent regions to the same zone.

  4. Save your work.

  5. Select the Locations tab.

    The Regions and Zones - Locations Tab window is a view only window used to find previously entered information for locations and the locations, regions, and zones to which they are mapped.

    To query existing information, in the Locations area, use the View pull down menu and select Query by Example, and Enter. Input your query criteria and select the View pull down menu and Query by Example and Run.

    You can also query for a particular location, region, and zone. Place the cursor in the lower area of the window, select the View pull down menu and Query by Example and Enter. Input your query criteria, such as, a city and select the View pull down menu and Query by Example and Run.

To update zones

  1. Navigate to the Regions and Zones window, Zones tabbed region.

  2. From the menu bar, select Query > Enter

  3. Enter search criteria.

  4. From the menu bar, select Query > Run and view zones that match your search criteria.

  5. Update the zone name and components information.

  6. Save your work.

To search for regions and zones

  1. Navigate to the Regions and Zones window, and select a tabbed region.

  2. From the menu bar, select Query > Enter.

  3. Enter values or partial values for the elements that you want to search.

  4. From the menu bar, select Query > Execute.

  5. View information about the regions or zones that match the search criteria.

  6. Navigate to the Regions Interface window and query the region information that you have mapped and verify it; remove any that you do not want to load.

To load regions from locations

  1. Execute the Location to Region Mapping concurrent process. After it completes, check the log to verify the number of regions loaded and that there are no errors. For additional information, see Oracle Shipping Execution User's Guide, Reports, Documents, and Processes chapter.

  2. Navigate to the Regions Interface window.

  3. Query the region information that you have mapped and verify it; remove any that you do not want to load.

    Regions Interface Window

    the picture is described in the document text

  4. Execute the Region Interface concurrent process by clicking Load All Regions and clicking OK. For additional information, see Oracle Shipping Execution User's Guide, Reports, Documents, and Processes chapter.

Oracle Shipping Debugger

The Oracle Shipping Debugger is a package (WSH_DEBUG_SV) and set of profiles that enable you to debug the Oracle Shipping Execution application with the help of Oracle Support.

Calls are made to these APIs from various places in the code:

The Oracle Shipping Debugger enables you to do the following:

The Oracle Shipping Debugger enables you to debug certain areas of Code Flow.

Logging is enabled or disabled in two dimensions:

The level and module of any given log message are defined by the programmer who makes the logging API call to log the message.

Shipping Debugger Profile Options

There are six profile options specific to the Oracle Shipping Debugger:

  1. WSH: Debug File Prefix: Naming Convention for Debug File is <Debug File Prefix Profile>_sessionid.dbg If value of profile is null, naming convention is wsh_<username>_<sessionid>.dbg Where: <username> is Application user name. If application context is not established, it will be defaulted to dbuser: <dbusername>. <sessionid> is Database session id.

  2. WSH: Debug Enabled: Select from the Debug Enabled LOV either YES or NO to activate the debug feature. The default is NO.

  3. WSH: Debug Module: The Module describes where to find the log message within the code. This profile indicates that debug messages from only those modules with names beginning with the profile value will be logged. The naming convention for Module is: <application short name>.<directory>.<package>.<routine>. <label> e.g. wsh.plsql.WSH_WV_UTILS.convert_uom.

  4. WSH: Debug Log Directory: The value entered for this profile option must be specified as a UTL_FILE parameter value.

  5. WSH: Debug Level: The level is a scale specifying the priority of a log message. The level is the lowest level for which the user wants to see messages. Select from the Debug Level LOV one of the following.

    Valid Values are (in increasing order of priority):

  6. WSH: Run PL/SQL Profiler: If this profile option is turned on and you are using PL/SQL, then it collects the performance statistics for the PL/SQL code.