8Shipping

This chapter contains the following:

Introduction

The shipping functionality lets you manage outbound logistics so that you can process shipments, satisfy customer demand, and at the same time manage the pick, pack, and ship cycle. You can set up shipping so that your users can manage and release pick waves, capture freight costs, pack material in containers or onto trucks, and create shipping documents. You can define and maintain shipping setup, including release sequence rules, ship confirmation rules, shipping cost types, shipping exceptions, shipping zones, and so on.

Set up shipping so that your users can use the Inventory Management work area in the Manufacturing and Supply Chain Materials Management offering to streamline picking and shipping:

  • Monitor pick and ship activities to manage outbound shipments.

  • Use a guided process that helps your users pick, pack, and ship tasks so that Inventory Management can fulfill orders quickly and accurately.

  • Set up shipping so that your users can use the Manage Shipping Exceptions task in the Setup and Maintenance work area to identify and resolve exceptions and backlogs to efficiently move materials through the warehouse.

Use roles and tasks to optimize the user experience:

  • Click links to tasks or search directly from work areas so that your users can access important pick and ship activities.

  • Drill into line details so that your users can perform the next logical action in a guided way.

  • Access important information about items during pick and ship transactions. Use visual images, detailed item specifications, and links to online collaboration tools.

User Roles That You Perform During Shipping

The shipping flow includes multiple roles that your organization must perform, from receiving the sales order, processing the shipment, and recording the financials.

The following figure illustrates the user roles that are involved during the shipping flow.

Shipping user roles and the work each role performs

Explanation of Callouts

  1. The warehouse manager does the following work:

    • Receives a sales order from Order Management Cloud.

    • Does order fulfillment work, including processing the sales order.

    • Creates a reservation that reserves material for the sales order. This reservation prevents some other demand source from using this material.

    • Monitors and releases sales orders that this process can use to pick product in the warehouse.

    • Creates pick slips that this process can use to pick material for the outbound material movement.

    • Uses a variety of criteria to create, manage, and release pick waves that results in efficient warehouse operation.

  2. The warehouse operator does the following work:

    • Pick loads, including monitoring and performing the picking activity, and create pick slips for outbound shipments, replenishment, and requisition.

    • Search for a pick slip and confirm the pick slip in a single action. The warehouse manager can also create and distribute pick slip reports and provide instructions to the warehouse operator regarding material movement.

  3. The shipping agent does the following work:

    • Process outbound shipments, including packing, creating shipments, and resolving exceptions, confirming receipt, and doing end-of-day activities.

    • Create outbound shipping documentation, such as the carrier bill of lading when the agent confirms the shipment.

    • Send shipping messages and updates to trading partners, including the contents or a shipment, shipment status, shipment arrival details, and shipment requests. This capability lets you integrate shipping with an external system.

    • Capture the shipping costs that are associated with the shipment and assign them to a shipment, shipment line, or packing unit.

    • Do order fulfillment work, including processing bills and receivables.

    • Do financial control, including financial reporting and cost accounting.

  4. Inventory Management sends shipping information to Order Fulfillment and Cost Management for downstream processing.

How the Reserve, Pick, and Confirm Shipments Process Works

The process that you use to reserve, pick, and confirm shipments begins when Inventory Management receives a sales order from Order Management Cloud or a source order from a source system, and ends when Inventory Management sends a confirmation to Order Management that it completed the movement of this material to the customer ship-to location. You can specify how Inventory Management does this movement.

The following figure illustrates the reserve, pick, and confirm process.

Reserve, pick, and confirm process flow

Explanation of Callouts

  1. A user uses an order entry system, such as Order Management Cloud, to enter a sales order.

  2. A Warehouse Manager uses Inventory Management to create a movement transaction.

  3. Inventory Management creates an approved movement request for the sales order, which is now awaiting shipping. A movement request is a request to transfer material from the subinventory that stocks the material to the subinventory that stages this material. You can specify the staging subinventory in Order Management or on the Manage Shipping Parameters page. Inventory Management allows only one staging subinventory for each pick wave.

  4. Allocate inventory for the movement request. If the Autoconfirm Pick option on the Create Pick Wave page:

    • Contains a check mark. Inventory Management allocates inventory for the movement request.

    • Doesn't contain a check mark. You must manually allocate inventory from the Confirm Pick Slip page.

    Note the following:

    • You must allocate inventory before you print pick slips.

    • A movement request uses inventory picking rules to determine how to allocate the material.

    • Shipping uses the Release Sequence Rule that you enter on the Pick Wave page or that Inventory Management defaults from the Shipping Parameters page to determine the sequence that fulfills the movement request.

    • Shipping sets the default sourcing values for subinventory, locator, revision, lot, and serial number on the movement request. You can use the Confirm Pick Slip page to modify these default values.

  5. Shipping uses the Pick Slip Grouping Rule that you specify on the pick wave or that Inventory Management defaults on the Shipping Parameters page to determine how to print the pick slips.

  6. Confirm the movement request for the pick slips. Note the following:

    • If the Autoconfirm Picks option on the Create Pick Waves page contains a check mark, or if the Pick Confirmation Required option on the Inventory Organization Parameters page doesn't contain a check mark, then Inventory Management confirms the pick during the picking process.

    • If Inventory Management doesn't confirm the pick during Pick Release, then you can use the Confirm Pick Slip page to confirm the pick.

  7. The Pick Confirm transaction moves the material from the stock subinventory to the staging subinventory.

  8. Confirm that the shipment is complete. Shipment is complete when Inventory Management loads all lines in the shipment to the customer ship-to location. A shipment includes a set of shipment lines, grouped according to common shipping attributes that Inventory Management schedules to ship to the ship-to location on a date and time. To confirm a shipment, a user in the warehouse selects the shipment on the Manage Shipments page or the Edit Shipment page, and then selects the Ship Confirm option. Note the following:

    • You must select a ship confirm rule or specify ship confirm options before you can confirm the shipment.

    • You must resolve shipping exceptions before you can confirm the shipment.

    • You must record the lot number and serial number for each item that requires these numbers.

    • You can confirm a shipment only after you confirm that you picked all the shipment lines that the shipment references.

    • Confirming a shipment might result in shipment lines that are in a variety of statuses, such as Shipped, Backordered, Staged, or Cycle Counted. Confirming a shipment is complete only when you record the quantity picked as Shipped.

  9. Inventory Management sends a shipment advice that includes shipment details to Order Management.

Set Up Shipping

To set up shipping, use the following:

  • Offering: Manufacturing and Supply Chain Materials Management

  • Functional Area: Shipping

  • Show: All Tasks

Perform the tasks in the Preparation column in the following table in the order presented.

Note: Oracle recommends that you finish the work described in the Preparation column before you start your implementation. You must perform each task.
Task Preparation

Manage Release Sequence Rules

Determined how we will release shipment lines.

Determined the level of priority that we will assign to the order that contains the lines that we will release.

Manage Ship Confirm Rules

Identified the tasks that we will specify with shipment confirmation.

Identified the options that we will provide for shipped quantities that users don't manually enter.

Manage Shipping Cost Types

Determined the date range that we will use for the cost type.

Determined the cost type that we will use for each currency.

Manage Transportation Schedules

Determined the schedule that we will use to ship and receive shipments.

Manage Shipping Exceptions

Determined the types of shipping exceptions that we will define and how we will define them.

Determined whether we must modify exception severity levels.

Manage Default Packing Configurations

Identified the mode of transport that we most commonly use to deliver shipments.

Determined the storage requirement for the items that we ship.

Manage Shipping Zones

Determined the configurations that we require for zones and zone types.

Manage Shipping Parameters

Determined how we will create, process, and confirm shipments.

Manage Pick Wave Release Rules

Determined how we will select lines for picking.

Determined how we will process and fulfill the selected lines.

Common Tasks That You Perform for Shipping

Shipping requires that you perform the following common tasks:

  • Manage Shipping Value Sets

  • Manage Shipping Descriptive Flexfields

  • Manage Shipping Lookups

  • Manage Shipping Document Sequences

These tasks are common to any Oracle application. Shipping doesn't require specific setup for these tasks, so you can follow the instructions that you use to perform them for any Oracle application. For details about how to perform these common tasks, see the guide titled Oracle SCM Cloud, Implementing Common Features for Oracle SCM Cloud.

How You Set Up Shipping for Drop Ship Transactions

Oracle Fusion Applications support drop shipments. Drop ship is an order fulfillment strategy where the seller doesn't keep products in inventory, but relies on suppliers to build, store, and ship orders to customers. Material flows directly from the supplier to the customer.

You can select whether or not you want to print shipping documents for drop ship orders. To print shipping documents for these transactions, do the following:

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Functional Area: Receiving

    • Task: Manage Receiving Parameters

  2. Select your organization.

  3. On the Manage Receiving Parameters page, select the Print shipping documents for drop ship orders option.

This option is a one-time setup step for your organization. You don't need to set this up per transaction.

Manage Release Sequence Rules

Release sequence rule enables you to specify the order in which the picking lines are pick released to inventory. You must assign a release priority in ascending or descending order to the selected release sequence.

These aspects of defining a release sequence rule will assist you in releasing picking lines according to your preference:

  • Criteria for releasing picking lines

  • Release priority

Criteria for release

You can release picking lines by:

  • Sales order

  • Initial ship date

  • Scheduled ship date

  • Outstanding invoice value

  • Shipping priority

Release priority

You must assign at least one of the criterion specified above to a release priority in the range of 1 to 5 with 1 being the highest priority and 5 being the lowest. You must select the order, ascending or descending, in which the specified criterion will be made effective. For example, if you select the ascending order for the Scheduled date criterion, then the picking lines with the earliest scheduled date are released first.

Release priority impacts the way a picking line is released when a release sequence rule is applied. Before assigning release priority to a release criteria, consider these questions:

  • How you release shipment lines in your organization?

  • What is the level of priority your organization assigns to the order in which lines are released?

Considerations for releasing shipment lines

Before selecting the release criteria, you must plan how your organization will release shipment lines. Consider the following:

  • What is the most commonly used criteria based on which shipment lines are released?

    Consider your organization's preferred criteria for releasing shipment lines. It can be based on sales order number, outstanding invoice value, scheduled date, initial ship date, and shipping priority. This directly impacts how and when the shipment line is released.

Considerations for assigning release priority

Consider these dependencies before assigning attributes to the release priority:

  • You can assign a priority level to one attribute with 1 being the highest and 5 being the lowest.

    Consider your organization's usage of a specific attribute.

    Note: You can select an attribute only once while deciding the relative priorities.
  • You can assign the order, ascending or descending, in which the specified attribute will be made effective.

    For example, if you select the ascending order for attribute Sales Order number, the shipment lines are released by ascending sales order number. Sales Order 1 is released first, then Sales Order 2, Sales Order 3, and so on.

  • You can't assign both the Outstanding invoice value attribute or the Sales Order number attribute to a release priority in the same release sequence rule.

Manage Ship Confirm Rules

Ship confirm rule enables you to determine how shipments are ship confirmed.

The following aspects of defining a ship confirm rule provide you the flexibility to:

  • Specify tasks along with shipment confirmation

  • Specify options if shipped quantities aren't manually entered

  • Specify the document job set

Specify tasks along with shipment confirmation

You can specify your organization's preference of tasks to be completed along with shipment confirmation, by selecting one or more of the following check boxes:

  • Create shipment for remaining staged quantities

    A new shipment will be created for lines with remaining staged quantities. Remaining staged quantity is applicable when shipped quantity is different from picked quantity on the line.

  • Create bill of lading and packing slip

    A bill of lading and packing slip is created.

    Note: You must define sequences of type "Automatic" for the application and module "Shipping." The sequences must be assigned to document sequence categories "BOL" or "PKSLP."
  • Close shipment

    The shipment status is set to closed and as a result all the shipment lines status is set to shipped.

  • Defer sending inventory updates to integrated applications

Specify options if shipped quantities aren't manually entered

You must specify an option that will be applied during ship confirm if the shipped quantity isn't manually entered for a staged line or lines. For example, consider a scenario where a shipment has 10 staged lines, and the shipped quantity is manually entered for eight of the lines. The ship confirm rule must indicate what to do with the two lines for which the shipped quantity isn't manually entered. The options are:

  • Backorder

    The two staged lines are set to Backorder status and are unassigned from the shipment.

  • Cycle count

    The two staged lines are marked for cycle count, set to Backorder status, and unassigned from the shipment.

    Note: The quantities transferred for cycle counting aren't considered for selection during the next pick release.
  • Ship requested quantities

    The requested quantity on the two staged lines is shipped.

  • Stage

    The two staged lines remain staged, but are unassigned from the shipment.

Specify the document job set

When a ship confirm rule is used, you can associate the document job set to use during shipment confirmation.

Considerations for Ship Confirm Rules

You must set up all the ship confirm rules in a manner that they're reusable and service varied needs of different organizations. You can have only one default ship confirm rule per organization and the this rule is associated by the shipping parameters for the organization.

Before setting up default shipping rules consider:

  • Understand shipping processes and anticipate current and future needs of the organization

  • Follow naming conventions

  • Associate the most commonly used rules while defining shipping parameters

Understand shipping processes

You must understand the shipping processes to be able to evaluate and anticipate current and future needs of your organization before defining shipping rules. Consider the most commonly used scenario for the business so that the scenario will be served well with the default rule. This will enable you to create effective rules that optimize performance and reduce the need for granularity, which in turn reduces maintenance.

Follow naming conventions

You must follow naming conventions so as to minimize chances of confusion resulting out of cryptic naming.

Associate most commonly used rules

You must associate the most commonly used rules while defining shipping parameters. For example, you must associate a rule that's used most frequently in your organization. This enables you to minimize the need for overriding the default ship confirm rule.

Manage Shipping Cost Types

Shipping cost types are shipment-related costs such as administration fee, duty fee, insurance, handling cost, export fee, or transportation charge. You can define a cost type within a category with a suggested amount. Shipping costs can be recorded at any point in time for a shipment, shipment line, or packing unit.

Shipping cost types provide you the flexibility to:

  • Defining a uniform shipping cost under a specific category for future reference

  • Specifying an effective date range for the validity of the cost type

  • Defining a cost type in preferred currency

Define shipping cost

You can define a shipping cost type under a specific category. This ensures uniformity of service charges under the selected category across the organization for the same service.

Note: You can override the cost type and suggested amount during or after the recording of shipping cost.

Specify effective date range

You can specify a date range for the validity of the cost type.

Define cost type in preferred currency

You can define a cost type in your functional currency. You can modify the currency at any point in time.

Manage Transportation Schedules

Transportation schedules enable you to define valid shipping and receiving days and hours for trading partners such as organizations, suppliers, customers, and carriers.

Transportation schedules enable you to:

  • Determine when shipments can be shipped and received.

  • Assist Oracle Fusion Global Order Promising in planning valid shipping and receiving days.

Determine shipping and receiving schedule

The shipping and receiving schedules are used to determine when your customers, customer sites, suppliers, supplier sites, and internal organizations can ship and receive. The ship confirm process uses the defined transportation schedules to warn you of invalid shipping days and hours. The initial ship date on the shipment is validated according to shipping schedule for the warehouse and the planned delivery date is validated according to the receiving schedule for the customer or customer site.

For example, you're shipping a shipment from your warehouse in Florida on Monday, September 12, to arrive at your customer's site in New York on Wednesday, September 14. In this case, ship confirm checks the warehouse's shipping schedule and the customer's receiving schedule for the initial ship date and planned delivery date respectively to confirm the following:

  • Monday, September 12, is a valid initial ship date for your warehouse in Florida to ship goods.

  • Wednesday, September 14, is a valid delivery date for your customer's site in New York to receive goods.

If the initial ship date or planned delivery date is invalid, then ship confirm displays a message requesting a review of the dates entered.

Transportation schedules are also used when a pick release process is submitted.

The pick release process also consults your defined transportation schedules and adjusts ship dates as necessary. When you create a pick wave using the pick release process, you can specify a pick wave release rule that defines the scheduled ship dates and requested ship dates on the pick wave. If a shipping transportation schedule is defined for your organization, then the scheduled and requested ship dates on the pick wave are compared against the valid shipping days on the transportation schedule. If either the scheduled or requested ship date falls on an invalid shipping day for your organization, then the dates are automatically adjusted to the next valid shipping day specified in the transportation schedule. For example, if your shipping transportation schedule allows shipments Monday through Friday, and the pick wave release rule calculates a ship date that occurs on a Saturday, then the ship date is automatically moved to the following Monday.

Note: If the transportation schedules aren't defined, then every day and time is assumed to be valid for shipping and receiving.

Assist Oracle Fusion Global Order Promising in planning valid shipping and receiving days

Oracle Fusion Global Order Promising uses the transportation schedule assignments when determining supply availability dates for customer orders.

  • Shipping schedule: The shipping schedule indicates the valid working dates for shipping originating from suppliers and organizations. Oracle Fusion Global Order Promising uses the shipping schedule to determine when material can be shipped from warehouses to customers.

  • Receiving schedule: The receiving schedule indicates the valid working dates for receiving goods at the organizations or customer sites. Oracle Fusion Global Order Promising uses the receiving schedule to determine when material can arrive at the customer site.

  • Carrier schedule: The carrier schedule indicates the working and nonworking days and times for material that's in transit using different means of transport. Oracle Fusion Global Order Promising uses the carrier schedule to determine the transit time from a warehouse to the customer site. For example, a carrier has a transit time of three days but doesn't work on weekends. This implies that the carrier can deliver a shipment that was shipped on Monday afternoon on Thursday afternoon. However, the carrier can deliver a shipment that was shipped on Friday only on Wednesday since Saturday and Sunday are nonworking days.

  • Oracle Fusion Global Order Promising uses shipping, carrier, and receiving schedules to determine when internal transfers between internal manufacturing sites and warehouses can be scheduled to meet customer demands at a warehouse.

    For example, shipping, receiving, and carrier schedules are used for shipping from an internal organization such as a plant to another internal organization such as a warehouse. The plant's shipping schedule is open from Tuesday to Friday. The warehouse's receiving schedule and the carrier schedule are open from Monday to Friday. The transit time is two days. In this case, the warehouse will receive shipments from the plant on Thursday, Friday, and Monday. The warehouse will not have shipments arriving on Wednesday since the plant cannot ship on Monday. If supplies are needed on Wednesday, then Global Order Promising will try to ship from the plant on the previous Friday to arrive on Tuesday.

You can use several combinations of trading partner, schedule name, and schedule usage to create the transportation schedules suitable for your business requirements.

Examples of creating transportation schedules are discussed for the following scenarios:

  • Shipping schedule for a warehouse

  • Receiving schedule for a customer

Shipping schedule for a warehouse

You want to set up a shipping schedule for your warehouse so that you can schedule shipments from your warehouse and calculate shipping and planned delivery dates for your customers. In order to ensure that your warehouse has accurate shipping days and times, you can create a transportation schedule for an organization from where your goods will be shipped, and select shipping as your schedule usage for that organization. You can activate the schedule assignment at the organization trading partner level by selecting the schedule and marking it as active.

Receiving schedule for a customer

You want to set up a receiving schedule so that you can schedule shipping and receiving days and calculate shipping and planned delivery dates for your customers. In order to ensure that the customer has accurate receiving days and times, you can create a transportation schedule for the customer to whom your goods will be shipped, and select receiving as your schedule usage for that customer. You can activate the schedule assignment at the customer trading partner level by selecting the schedule and marking it as active.

Trading partner type can be customer, supplier, carrier, and organization. The schedule usage you define for every trading partner type determines what the schedule assigned to the trading partner is used for. For example, if shipping is defined as schedule usage for a trading partner organization, then that schedule is used for shipping. You can define and activate one or more sites for a trading partner. You can assign a different schedule for each trading partner site. Note that setting up schedules at the site level is optional. If a schedule isn't defined at the site level, then the schedule defined at the trading partner level is used. For example, a trading partner has 20 ship-from sites and 18 of those sites have the same schedule for shipping days. In this case, one shipping schedule can be defined for the trading partner and two other shipping schedules for the sites.

Site level schedules enable you to:

  • Determine when shipments can be shipped and received at the site

  • Validate shipping and receiving days

Determine site level shipping and receiving schedule

Enables you to define a shipping and receiving schedule for a trading partner site.

For example, a trading partner site (referred to in the following list as customer site) is receiving a shipment on Thursday. In this case, ship confirm checks the trading partner site schedules to confirm the following::

  • The customer site is activated to receive shipments.

  • The customer site can receive goods on Thursday.

Validate shipping and receiving days

The ship confirm process consults your defined site level schedules and warns you about invalid shipping days and hours as necessary.

When you ship confirm a shipment using the ship confirm process, the initial ship date and planned delivery date is checked in the trading partner site schedule. If a trading partner site schedule is defined for your trading partner site, then the initial ship date and planned delivery date are compared against the valid shipping and receiving days on the site schedule. If either the initial ship date or the delivery date falls on an invalid shipping or receiving day for your warehouse and customer site respectively, then alternative valid dates are suggested. For example, if your shipping site schedule allows shipments Monday through Friday, and the ship confirm process calculates an initial ship date that occurs on a Saturday, then Monday is suggested as the alternative initial ship date.

FAQs for Manage Transportation Schedules

If a transportation schedule isn't defined, then every day and time is assumed to be valid for shipping and receiving.

Manage Shipping Exceptions

Shipping exception is an unexpected event resulting out of a conflict between the requirements of the shipper, customer, or transportation carrier.

Shipping exception enables you to:

  • Define and maintain the three types of shipping exceptions

  • View and modify predefined exceptions

  • Modify severity levels of exceptions

Define and Maintain New Shipping Exceptions

You can define and maintain new exceptions. The exceptions can be of three types:

  • Shipment: exceptions that are logged against shipments.

  • Picking: exceptions that are logged during the picking process.

  • Batch: exceptions logged to store the messages generated during the automated shipping processes such as automatically pack and ship confirm.

View and Modify Predefined Exceptions

You can view and use predefined exceptions. You can choose to activate or inactivate predefined exceptions based on their validity for your organization. You can only modify the severity level for predefined exceptions.

Modify Severity Levels of Exceptions

You can define and maintain the following severity levels of shipping exceptions:

  • Error: Requires resolution before the transaction can be closed.

  • Warning: Can be superseded and doesn't require resolution to close the transaction.

  • Information: Provides information on a particular transaction. The user isn't required to act on the information exception to close the transaction.

Predefined exceptions are already defined in Oracle Fusion Shipping. They are defined for the most common scenarios that may lead to the creation of an exception.

Predefined exceptions provide the flexibility to:

  • Activate valid exceptions

  • Inactivate exceptions

  • Modify severity level

Activate Valid Exceptions

You can activate exceptions that are valid for exception scenarios for your organization from a list of predefined exceptions.

This table lists the predefined exceptions available for your organization.

Exception Name Description Severity Level

Requested Quantity Changed

Requested quantity changed due to change in order line quantity.

Error

Shipment Grouping Changed

One or more shipment grouping attributes were changed.

Error

Scheduled Date Postponed

The scheduled date was postponed.

Error

Scheduling Attributes Changed

One or more scheduling attributes were changed.

Error

Pick Release Error

Pick release detailing completed with an expected error.

Error

Shipment Request Error

Line has shipment request errors in shipment message interface.

Error

Shipment Line on Hold

The shipment line was placed on hold by a shipment request.

Error

Manifest Request Cancellation Accepted

Manifest request cancellation accepted by carrier manifesting.

Information

Manifest Request Cancellation Rejected

Manifest request cancellation rejected by carrier manifesting.

Information

Backordered at Picking

The shipment line was backordered at picking.

Information

On Hold at Picking

The line had a hold at picking.

Information

Shipment Line Unassigned by Shipment Request

Line unassigned from shipment after processing shipment request.

Information

Invalid Packing

Items should be unpacked from the packing unit.

Information

Change Due to Party Merge

Party merge has changed the shipment line or packing unit.

Information

Pick Release Detailing Warning

Pick release detailing completed with warnings.

Information

Batch Message

This message was logged by a batch program.

Information

Pick Release Warning

Pick release completed with warnings.

Information

Added by Append Shipments

Line added to a shipment through the append shipments process.

Warning

Appended Shipment Could Not Be Marked as Planned

The shipment couldn't be updated to planned at the end of the append shipment process.

Warning

Inactivate Exceptions

You can inactivate an exception that's no longer in use by your organization.

Modify Severity Level

You can modify the severity level of a predefined exception by selecting one of the following severity levels: Error, Information, Warning. For example, the predefined severity level for exception "Added by Append Shipments" is Warning but if your shipping processes require such an exception to be resolved prior to ship confirm, you can set the severity of this exception to Error.

Note: You can modify the severity level of an exception only if it's not currently in use by a shipment, shipment line, or packing unit. You can't modify the severity level for an Error exception.

FAQs for Manage Shipping Exceptions

Shipping exceptions occur when predefined criteria for shipment creation, processing, and delivery aren't met or fail.

Predefined exceptions are logged automatically against shipments, shipment lines, and packing units when specific events occur.

You can also log shipping exceptions manually for a specific shipment, shipment lines, and packing units.

Yes. Remove the Active check box selection in the Edit Shipping Exception page. You can inactivate a manually defined exception only if the exception isn't currently in use by a shipment, shipment line, or packing unit.

Note: You can't inactivate a predefined exception.

Manage Default Packing Configurations

Packing shipments is the process of packing items into packing units for shipping to the customer.

Packing shipments provides the flexibility to:

  • Manually pack

  • Automatically pack

Pack Shipments Manually

You can pack shipment lines manually by creating packing units and specifying the lines that are packed in each of the packing units. Packing can be done for items as well as packing units. You can pack items into a packing unit and also pack those packing units into another packing unit. For example, you can pack items into a box and many boxes onto a pallet.

Pack Shipments Automatically

You can choose to automatically pack shipment lines into packing units by selecting the Automatically Pack option for the specific lines. The selected shipment lines are grouped by shared attributes, such as the ship-to location, and are then packed based on the preferred default packing configuration.

Note: You can automatically pack a shipment that's open and has at least one shipment line assigned to it.

You can automatically pack if packing configurations have been defined.

Default packing configuration enables you to assign a packing unit type to an item.

Default packing configuration provides you the flexibility to:

  • Specify maximum quantity of an item that can be packed into the chosen packing unit type

  • Automatically pack shipments

Specify Maximum Item Quantity

You can specify maximum quantity of an item that can be packed into the chosen packing unit. This assists in calculating the number of packing units required for a shipment line while packing automatically.

Automatically Pack Shipments

You can automatically pack items into packing units, which in turn can be further packed into larger packing units. Examples of larger packing units are pallet or boxcar.

Packing units are defined in Oracle Fusion Inventory Management. Every packing unit can be classified into a broader packing unit type meant for a specific kind of packaging and shipping. For example, the airline container packing unit is used to pack shipments that are delivered by air. Before assigning a packing unit to an item, consider:

  • What is the most commonly used mode of transport used to deliver shipments by your organization?

  • What is the storage requirement for the items shipped from your organization?

Mode of Transport to Deliver Shipments

Consider which modes of transport are most commonly used by you organization to deliver shipments. Your organization's preferred modes of transport indicate the packing units most likely to be used during shipping.

Storage Requirement

Consider the weight and volume of the items being shipped from your organization to determine the packing unit to be used.

Manage Shipping Zones

You can create zone types and zones for the use of defining boundaries to be used in, for example, tax or shipping zones.

In order to create a zone boundary you need to define the following:

  • Zone types

  • Zones

Zone Types

Zone types categorize and group zones together, for example, the zone types of Income Tax and Shipping Regions.

Zone types need to be created before you define a zone for the geographical boundary. You can create a zone type which will contain geographical boundaries from anywhere in the world, or you can create a zone type that will only contain geographies from within a specified country. When you create a zone type that's bounded by a country you can define which geography types or geographies you will be able to choose when you create a zone.

Zones

Zones are geographical boundaries for a zone type, for example, the San Jose Tax zone. Zones are based on the master reference geography hierarchy data.

Zones are created within a zone type, and you can associate geographies to define the zone. For example, for the Shipping Regions zone type you can create a West Coast zone which has the state of California as one of its geographies. Within a geography you can specify a postal range. So for the state of California, for example, you can specify that the zone spans from postal code 90001 to 90011.

This example shows how to create a zone type and zone for shipping and tax.

Create a new zone type which is limited to one country, specify which geography types you want to select for a zone, and create a zone.

Creating a Zone Type

When you're creating a zone you will need to either create the zone under an existing zone type, or you will need to create a new zone type and then create the zone. In this example, a suitable zone type doesn't exist in the application, and so you create a new zone type.

When you're creating a new zone type you can allow zone types to span across countries, however the zone type you're creating in this example will be limited to geographies within the United States.

  1. On the Manage Zone Types page, click Actions and then click New.

  2. On the Create Zone Type page, enter a name for the zone type in the Zone Type field.

  3. Click the Bounded by country option.

  4. In the Boundary section, click the Country list.

  5. Click Search.

  6. Enter United states in the Name field.

  7. Click Search.

  8. Select the United States row.

  9. Click OK.

  10. In the Boundary section, click Zone Created Allowed for the State, County, City, and Postal Code geography types.

  11. Click Save and Close to go back to the Manage Zone Types page.

Creating a Zone

Now that you have created a zone type, you want to create a zone for the zone type. In this example, the zone will contain State geographies.

  1. On the Manage Zone Types page, click Next.

  2. Click Actions and then click New.

  3. On the Create Zone page, enter a name for the zone in the Zone field.

  4. Enter a unique name for the zone in the Code field.

  5. Enter the date you want the zone to be effective from in the Start Date field.

  6. Enter the date you want the zone to be inactive from in the End Date field.

  7. Now you need to enter the geographical boundaries of the zone by adding geographies. In the Associated Geographies section, click Actions and then click New.

  8. Enter State in the Geography Type field.

  9. Enter CA in the Geography Name field.

  10. Click Search.

  11. Highlight the California geography, and click Save and Close.

  12. Repeat steps 7 to 11 for every geography you want to enter for the zone.

  13. Click Save and Close.

  14. Create as many zones as you require for your zone type.

  15. Click Save and Close on the Manage Zones for Zone Type page.

Manage Shipping Parameters

Shipping parameters affect how Oracle Fusion Shipping creates and confirms a shipment, and how it interacts with Oracle Fusion Inventory Management. Consider the following questions when you set shipping parameters:

  • How will your organization create, process, and confirm shipments?

  • How will Oracle Fusion Shipping update Oracle Fusion Inventory Management?

Create and Confirm Shipments

Before selecting the shipping parameters, you must plan how your organization will create, process, and confirm shipments. Consider the following before configuring the shipping parameters for each of your ship-from organizations.

  • Which shipment creation criteria to use?

    Consider your organization's criteria for creating shipments; if a shipment can be created across sales orders or must be created from within a sales order.

  • Which confirm rule to use?

    Consider your organization's usage of a specific confirm rule and decide which can be used as the default rule during confirmation. Select the commonly used rule in your organization to save time and quickly confirm shipments.

  • What weight UOM class and volume UOM class to use?

  • What currency to specify?

    Consider your organization's range of transactions in a particular currency.

  • Whether to enable automatic packing?

    Consider your organization's usage of packing shipment lines into packing units. Note that the shipment lines to be automatically packed are grouped together by shared attributes such as ship-to location and the shipment line information can't be changed until the shipment is unpacked.

  • Whether to consolidate backordered lines?

    Consider your organization's policy on consolidating a line that was split and backordered with other backordered lines.

  • Whether to enforce packing?

    Consider your organization's practice of requiring every shipping line in a shipment to be packed.

  • Whether to enforce shipping method?

    Consider your organization's practice of requiring a record of shipping method for each shipment.

  • Whether to enable future ship date?

    Consider your organization's policy on recording an actual ship date in the future.

  • Whether to enable carrier manifesting?

    Consider if you want to enable carrier manifesting for the shipments in the warehouse.

Update Oracle Fusion Inventory Management

Consider the following dependencies before configuring your organization's shipping parameters on updating Oracle Fusion Inventory Management tables.

  • Whether to defer sending inventory updates to integrated applications?

    Consider your organization's preference on delaying updates to Oracle Fusion Inventory Management tables once the shipment is confirmed. If you choose to defer sending inventory updates to integrated applications, then the Shipping interface does not initiate updates to Oracle Fusion Inventory Management interface tables and in turn, the inventory processor does not pick up or update the inventory tables.

  • Whether to defer online processing of inventory updates?

    Consider your organization's preference on delaying processing of records in Oracle Fusion Inventory Management.

  • How much inventory interface batch size to specify?

    Specify the number of records that are selected for processing in a batch in Oracle Fusion Inventory Management. Consider the maximum number of records your organization would prefer to be processed in a batch. Note that an optimum batch size reflects inventory updates faster in the application.

Set Shipping Parameters

Consider the following items when you set a shipping parameter on the Manage Shipping Parameters page in the Setup and Maintenance work area.

Parameter Description

Appending Limit

Select one of the following values:

  • Do Not Append. Do not enable Oracle Fusion Shipping to append a shipment.

  • Start of Staging. Enable Oracle Fusion Shipping to append a shipment after it stages at least one of the fulfillment lines that the shipment references.

  • End of Staging. Enable Oracle Fusion Shipping to append a shipment after it stages all fulfillment lines that the shipment references.

Packing Slip Document Sequence Category

Select a value that specifies the document sequence category to use for the packing slip. You can use this parameter to specify the starting packing slip number, or to specify whether or not the sequence contains gaps or is continuous without gaps.

Consolidate Backordered Lines

If this parameter is selected, Oracle Fusion Shipping consolidates any line that was split and then subsequently backordered. It consolidates this line with the backordered lines that existed before the split. Oracle Fusion Shipping searches for existing backorders for the shipment line when a backorder occurs. If it finds an existing backorder, then it consolidates the current backordered shipment line with the existing backordered shipment line.

Oracle Fusion Shipping only consolidates backordered lines that aren't assigned and not packed.

Required on Packing Slip

Select the options to print on the packing slip:

  • Packing Slip Status. Print Draft or Final on the packing slip.

  • Shipment Description. Print the description that the user enters for the shipment.

  • Transportation Reason. Print the reason for sending the goods that the user enters for the shipment.

The options selected for this parameter print on the packing slip. By default, no options are selected.

Enable Carrier Manifesting

If this parameter is selected, Oracle Fusion Shipping sends shipments to the carrier manifesting system so that this system can confirm the shipment. Only shipments that are open and that include lines that are assigned, staged, and packed are sent. Packing is performed prior to manifesting because Oracle Fusion Shipping can only manifest packed lines.

A shipper can use carrier manifesting to process shipments that use carriers that are integrated with Oracle Fusion Shipping. The carrier manifesting process does the following work:

  • Weigh parcels.

  • Calculate freight cost.

  • Create shipping documents.

  • Send manifest data to systems that third party carriers use.

Publish Transactional Events

If this parameter is selected, the shipping transaction event for backordered quantities is always published.

Trade Compliance Screening Method

Select one of the following values to set the default screening method for all shipment lines:

  • None. Shipment lines aren't screened for trade compliance.

  • Pick confirm. You must submit shipment lines for trade compliance screening as soon as the lines are picked and staged. However, for outside processing and return to supplier order types, you must submit shipment lines for trade compliance screening as soon as the lines are created.

  • User initiated. You must manually submit shipment lines for trade compliance screening after the lines have been picked and staged.

Shipment grouping attributes are defined for Ship-from Organization and determine how shipment lines are grouped on a shipment. Ship-to Location and Ship-from Organization are always applied during grouping of shipment lines into shipments. Before selecting shipment grouping attributes, consider:

  • How would you like to group your shipment line into shipments?

  • Do you need to further refine your grouping criteria?

Group Shipment Lines

You must consider your organization's business preference for grouping shipment lines into shipments. For example, there are two types of freight terms; Prepaid and Collect. If you enable the grouping attribute Freight Terms, then the shipment lines that share the same freight term, Prepaid, will be grouped into one shipment. And the shipment lines that share the freight term, Collect, will be grouped into another shipment. The following tables illustrate the example and the consequent grouping of shipment lines into shipments based on selection of the grouping attribute, Freight Terms.

This table shows an example of shipment lines and their attributes.

Shipment Lines Ship-from Organization Ship-to Location Freight Terms

1234A

Organization 1

San Jose

Prepaid

1234B

Organization 1

San Jose

Collect

1234C

Organization 1

San Jose

Collect

1234D

Organization 1

San Jose

Prepaid

This table shows an example of how the shipment lines were grouped into a shipment when the grouping attributes were applied.

Shipment Lines Ship-from Organization Ship-to Location Freight Terms Shipment

1234A

Organization 1

San Jose

Prepaid

Shipment 1

1234B

Organization 1

San Jose

Collect

Shipment 2

1234C

Organization 1

San Jose

Collect

Shipment 2

1234D

Organization 1

San Jose

Prepaid

Shipment 1

When a shipment is created, it inherits the enabled grouping attributes from the lines. For example, Freight Terms is enabled as a grouping attribute and a shipment is created for the lines with the term Prepaid. In this case, the shipment will automatically have the freight term, Prepaid upon creation.

When an optional attribute is enabled as a grouping criteria and there are shipment lines that don't have a value specified for the enabled attribute, then all those shipment lines are grouped together on a separate shipment. You can also choose to not select any of the optional grouping attributes.

Refine Grouping Attributes

You must consider your organization's preference for assigning Customer, Shipping Method, FOB, and Freight Terms as grouping criteria for creating shipments.

You can select more than one grouping attribute to further refine your grouping criteria. For example, if you select Customer and Shipping Method, then shipment lines with the same customer and shipping method will be grouped into one shipment.

You can print the details of the model and options selected for configured items on fulfillment documents. This is known as the sales order view. The application calls a service at the time of shipment confirmation that provides this information. You can view the details of the configured product on the packing slip and commercial invoice throughout the receiving, inventory, and shipping processes. This helps avoid confusion when shipping configured products because the contents of the shipment are indicated on the documents.

Note: The quantities of the components contained in the configured item display on the documents in terms of a single unit quantity. This means that the documents show the number of required components when the configured item quantity equals one.

FAQs for Manage Shipping Parameters

What happens if I select different appending limit options during shipment creation?

Select Do Not Append to prohibit automatic appending to an existing shipment. Select Start of Staging to allow automatic appending to a shipment till one of the lines is staged. Select End of Staging to allow automatic appending to a shipment till all the lines are staged.

Carrier manifesting is a method used by shippers to process shipments that use carriers that are integrated into Oracle Fusion Shipping. The carrier manifesting process includes weighing parcels, calculating freight cost, generating shipping documents, and submitting manifest data to third party carrier systems. When you enable carrier manifesting, open shipments with assigned lines that are staged and packed are sent to be ship confirmed in the carrier manifesting system. Packing is performed prior to manifesting since only packed lines can be manifested.

Manage Pick Wave Release Rules

A pick wave is a batch of shipment lines that are pick released together based on certain business-related criteria.

Examples of when you might want to use pick waves include:

  • Fulfilling a particular customer demand

  • Optimizing transportation

  • Fulfilling backorders to reduce delay in shipment

Fulfill a Particular Customer Demand

If your organization has customers who have specific quality demands, then you can create a pick wave to perform extra quality checks or follow special procedures during shipping.

Optimize Transportation

You can process a batch of shipment lines that are bound by common ship-to location, shipping method, and shipping priority in order to optimize transportation. If your organization has several customers in one location, then your organization can choose to collect all the shipment lines for those customers and ship them together through a common carrier. For example, if an organization has 10 customers in location B, then it can collect all shipment lines for location B and create a pick wave to ship them together using a common carrier, such as UPS truck service.

Fulfill Backorders to Reduce Delay in Shipment

If your organization chooses to fulfill backorders by putting them on a faster shipping schedule, then you can create a pick wave for all the backordered lines and ship them using a faster shipping method, such as Air.

Pick wave release rule defines the criteria to determine the order lines to select for pick release and how they need to be processed. The optional processing includes:

  • Creating shipments

  • Picking and staging the material

  • Packing the material

  • Ship confirming the lines

The following criterion based on which you can define a pick wave release rule will assist you in planning and meeting your organization's needs:

  • Effective Start and End Date range

  • Demand Selection criteria

  • Process criteria

  • Fulfillment criteria

Date range

Effective start and end date range for the rule.

Demand Selection Criteria

Enables you to specify criteria pertaining to shipping organization, order, order date, item, and shipping details.

Process Criteria

Enables you to specify the release sequence rule, pick slip grouping rule, ship confirm rule, document job set, and also if the shipment should be automatically packed among others.

Fulfillment criteria

Enables you to specify the pick-from subinventory and staging subinventory of the shipping organization.

Pick wave release rule defines the criteria to determine the order lines to select for pick release and how they must be processed.

Before creating a pick wave release rule consider:

  • How you select lines for picking in your organization?

  • How do you process and fulfill the selected lines?

Select shipment lines

You must consider your organization's preference before selecting lines for picking. Before selecting the order, date, and item details you must plan how your organization creates a pick wave. Consider the following:

  • Which subinventory to use?

    Your choice of subinventory results in the selection of those order lines that are planned to be sourced from the specified subinventory. The source subinventory is specified for the order lines in the sales order creation stage.

  • Which sales order to select?

    Determine if the shipment lines to be pick released for a specific sales order.

  • Which customer to select?

    Determine if the shipment lines to be pick released are for a specific customer.

  • Which shipment set to select?

    If your organization groups order lines within a sales order based on customer specification to ship together, then those set of lines are shipped together in the same shipment. You can select the appropriate shipment set number from where the order lines will be selected.

  • Which destination type to select?

    Determine if the shipment lines to be pick released for specific geography, zone, or ship-to location.

  • What are specified date ranges?

    Determine the from and to scheduled ship dates and from and to requested ship dates.

  • What item details to specify?

    Consider if you're creating a pick wave for a specific item. If yes, then specify the catalog and category name along with the item name and description.

  • What shipping details to specify?

    Determine the preferred shipping method. The selected shipping method enables selection of those order lines that are planned for shipping using the specified shipping method.

Process shipment lines

You must consider your organization's preference for the way lines are fulfilled and processed. Consider the following:

  • What pick-from subinventory and pick-from locator to specify?

    Consider your organization's usage of a specific subinventory and locator to pick material from.

    Note: This is an optional criterion.
  • What staging subinventory and locator to specify?

    Consider your organization's usage of a specific subinventory and locator to finally deposit picked material.

  • What release sequence rule to specify?

    Consider your organization's preference regarding the order in which lines are allocated during pick release.

  • What pick slip grouping rule to specify?

    Consider your organization's preference regarding how lines grouped onto pick slips.

  • What ship confirm rule to specify?

    Consider if your organization prefers shipments to be ship confirmed as part of pick release.

  • Whether to automatically confirm pick slips?

  • Whether to create shipments?

  • Which shipment creation criteria to use?

    Consider your organization's criteria for creating shipments; if a shipment can be created across orders or must be created from within an order.

  • Whether to automatically pack shipments?

  • Whether to append existing shipments?

Set Pick Wave Release Rules

Consider the following items when you set pick wave release rule criteria on the Manage Pick Wave Rules page in the Setup and Maintenance work area.

Criteria Description

Initial Destination

Select the initial destination for the shipment and shipment lines for the pick wave. The transportation shipment must have been planned in a transportation management system.

Trade Compliance Screening Method

Select one of the following values to set the default screening method for all pick wave releases:

  • None. Shipment lines aren't screened for trade compliance.

  • Pick confirm. You must submit shipment lines for trade compliance screening as soon as the lines are picked and staged. However, for outside processing and return to supplier order types, you must submit the shipment lines for trade compliance screening as soon as the lines are created.

  • User initiated. You must manually submit shipment lines for trade compliance screening after the lines have been picked and staged.

Transportation Shipment

Select the transportation shipment that represents the shipment and corresponding shipment lines that are planned to ship together.

Options criteria impact the way lines are fulfilled and processed. Before selecting the options criteria, consider:

  • Fulfillment criteria

  • Processing criteria

Fulfillment Criteria

Before you select the fulfillment criteria, you must plan how your organization prefers lines to be fulfilled.

  • What pick-from subinventory and pick-from locator will you specify?

    Consider your organization's usage of a specific subinventory and locator to pick material from.

    Note: This is an optional criteria.
  • What staging subinventory and locator will you specify?

    Consider your organization's usage of a specific subinventory and locator to deposit the picked material for staging.

Processing Criteria

Before you select the processing criteria, you must consider your organization's preference for processing lines.

  • What release sequence rule will you specify?

    Consider your organization's preference regarding the order in which lines are allocated during pick release.

  • What pick slip grouping rule will you specify?

    Consider your organization's preference regarding grouping of lines onto pick slips.

  • What ship confirm rule will you specify?

    Consider if your organization prefers shipments to be ship confirmed as part of pick release.

  • Will you automatically confirm pick slips?

    Consider if your organization prefers pick slips to be automatically confirmed during pick release.

  • Will you create shipments?

    Consider if your organization prefers shipments to be created during the pick release process.

  • Which shipment creation criteria will you use?

    Consider your organization's criteria for creating shipments--whether a shipment can be created across orders or must be created from within an order.

  • Will you automatically pack shipments?

    Consider if your organization prefers shipments to be automatically packed.

  • Will you append existing shipments?

    Consider if your organization prefers to append shipment lines to the existing shipments.

    Note: Here are the prerequisites for appending shipment lines:
    • The appending limit must be defined as a value other than Do not append on the Manage Shipping Parameters page.

    • An organization must be specified.

    • Create shipments functionality must be enabled.

    • Shipment creation criteria must be defined as across orders.

    • Autoconfirm pick slips functionality must be disabled.

Integrate Shipping with Transportation and Trade Management Systems

Overview of Integrating Shipping with Transportation and Trade Management Systems

Oracle Fusion Shipping provides seamless integration with any transportation management or trade management solution.

Using Shipping with transportation and trade management solutions, you can:

  • Avoid fines by complying with the crucial regulatory compliance requirements

  • Reduce the risk associated with global shipments

  • Reduce costs by shipment optimization and carrier outsourcing

  • Improve process flows by managing holistically across businesses and geographies

  • Improve customer satisfaction by reducing order cycle time

Note: Although these integrations are available to any third-party solutions, Oracle Fusion Shipping is designed to work directly with Oracle Transportation Management Cloud and Oracle Global Trade Management Cloud. For more information about these products, see the Oracle Logistics Cloud documentation available on the Oracle Help Center.

The integration features for Shipping are predefined, and you can access them through the following existing job roles:

  • Warehouse manager

  • Shipping manager

  • Warehouse operator

  • Shipping agent

How Shipping Integrates with Transportation and Trade Management Systems

Oracle Fusion Shipping provides seamless integration with any transportation management or trade management solution.

When you integrate Shipping with a:

  • Transportation management system, you can schedule and optimize shipments, and tender shipments to carriers.

  • Trade management system, you can ensure compliance by properly screening transactions and managing legal, regulatory, and corporate requirements for cross-border transactions.

The graphic shows a high-level overview of this cross-product business process flow.

Shipping integration with transportation and trade
management process flow

Explanation of callouts:

1. Order managers can send order lines to a transportation management system for planning. After the order lines are planned, the transportation details are sent back to Shipping for further processing.

2. Order managers can perform compliance screening directly from both Oracle Fusion Order Management and Shipping. Order managers can request compliance screening for order lines, and shipping users can check trade compliance for shipment lines.

The following subsections provide more detailed information about how Shipping integrates with Order Management, transportation management, and trade management systems.

Shipping Integration with Order Management

Order Management and the Oracle Fusion Inventory Management suite of products (shipping, receiving, and inventory management) work together to fulfill orders that your users enter directly in Order Management or that you import from some other source.

You can integrate Order Management with a transportation management system so that it sends sales orders to that system for transportation planning, and to receive updates at fulfillment milestones, such as plan completion or proof of delivery. For more information about Order Management integration with a transportation management system, see the Oracle SCM Cloud Implementing Order Management guide.

Shipping Integration with Transportation Management Systems

Integrating Shipping with a transportation management system enables your order managers to send order lines to that system for planning. After your order lines are planned, the transportation details are sent back to Shipping for further processing.

Some of the advantages of this integration include:

  • Shipping automatically receives transportation planning details, such as transportation shipment information, shipping method details, and shipping dates.

  • Warehouse personnel can perform actions on shipment lines collectively based on the associated transportation shipment.

  • The transportation management system is automatically notified of backordered quantities.

  • Shipping communicates the final shipment information to the transportation management system, which helps in the generation of more accurate shipping documents.

  • Third-party logistics (3PL) applications and warehouse management systems (WMS) can integrate directly with transportation management systems, and Shipping communicates directly with the 3PL application and WMS.

For more information about transportation management, see the Oracle Logistics Cloud documentation available on the Oracle Help Center.

Shipping Integration with Trade Management Systems

Integrating Shipping with a trade management system enables order managers to perform compliance screening directly from Order Management and Shipping. Order managers can request compliance screening for order lines, and shipping users can check trade compliance for shipment lines.

Some of the advantages of this integration include:

  • Shipping users can request shipment lines to be screened at a stage that's appropriate to your business. For example, shipping users can request compliance screening when the lines are staged automatically, or manually before the material is shipped.

  • Warehouse personnel can perform actions on shipment lines collectively based on your compliance screening needs.

  • The trade management system is automatically notified of backordered quantities.

  • You can communicate the final shipment information to the trade management system, which helps in releasing any licenses withheld and generating export documentation.

  • Third-party logistics (3PL) applications and warehouse management systems (WMS) can integrate directly with a trade management system, and Shipping communicates directly with the 3PL application and WMS.

Considerations for Integrating Shipping with Transportation and Trade Management Systems

The following are points to consider when integrating Oracle Fusion Shipping with transportation management or trade management systems.

  • Integrations are available for any third-party solutions, however, Shipping is designed to work together with Oracle Transportation Management Cloud and Oracle Global Trade Management Cloud.

  • Visibility is not available within Shipping to determine if shipment lines were previously screened in Oracle Fusion Order Management.

  • Shipment lines can't be shipped using Oracle Fusion Inventory Management for organizations controlled by external systems, such as third-party logistics (3PL) applications or warehouse management systems (WMS). Contract manufacturing is the exception.

  • Printing of shipping documents is performed using the transportation management system.

  • Printing of commercial invoices is performed using the trade management system.

How You Set Up Shipping for Backordered Shipment Line Notifications

With Oracle Fusion Shipping, backordered line notifications are available for the shipment lines you have enabled for transportation planning and compliance screening. However, if you need these notifications for integrations or implementations, then you must enable the Publish Transactional Events shipping parameter.

To enable the Publish Transactional Events shipping parameter, do following.

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Functional Area: Shipping

    • Task: Manage Shipping Parameters

  2. On the Manage Shipping Parameters page, select a value for Appending Limit as required.

When this parameter is selected, the shipping transaction event for backordered quantities is always published.

Notifications for Backordered Shipment Lines

Oracle Fusion Shipping provides new events that enable you to work with backordered shipment lines and pull shipment information.

For these events to be available, do the following:

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Functional Area: Shipping

    • Task: Manage Shipping Parameters

  2. On the Manage Shipping Parameters page, enable the Publish Transactional Events parameter.

These events are available by way of Integrated Cloud Service (ICS) and include transportation shipment and trade compliance screening attributes to assist with such integrations. ICS is an end-to-end integration orchestration platform that simplifies how to use and apply product integrations offered within the cloud. Shipping creates a shipment advice event that is published after confirming a shipment.

When integrating Shipping with a transportation management system, you can keep the transportation shipment up to date for the backorder quantities. The shipment advice event enables you to also update the transportation shipment incrementally and complete it in an orderly fashion. After completion, the transportation shipment information is final and accurate so that you can generate applicable shipping documents.

Transportation Planning Details for Shipment Lines

Integrating Oracle Fusion Shipping with a transportation management system, you can:

  • Receive planning details for shipment lines from transportation applications

  • Automatically split shipment lines for partial shipments

  • Allow users to review, delete, and resubmit a shipment request if there are issues

Receive Transportation Details for Shipment Lines

You can receive the transportation planning details using the batch method of the Shipment Request public web service.

These details include transportation shipment, transportation shipment line, initial destination, shipping method, and scheduled ship date. You manage transportation planning details for shipment lines using the Manage Shipment Lines page in the Inventory Management work area in the Manufacturing and Supply Chain Materials Management offering.

Shipping can receive one transportation shipment at a time. You must split shipment lines if you plan to ship partially on a transportation shipment. You can review any errors and resubmit the shipment request using the Manage Shipment Message Interface task in the Inventory Management work area in the Manufacturing and Supply Chain Materials Management offering.

Shipping Support for Transportation Systems

With Shipping support for transportation shipments, you can:

  • Group one or more shipments into a single transportation shipment.

When you combine one or more shipments into a single transportation shipment, you can progress the shipment lines for customers independent of each other, even though the lines belong to the same transportation shipment. Shipping communicates the shipment information to the transportation management system in an incremental fashion, that is, one shipment at a time.

  • Enable pick release of all shipment lines for a transportation shipment or initial leg destination location.

  • Support planned and unplanned lines within a single organization, however, Oracle Fusion Order Management decides which lines require planning.

  • Enable manual updates to transportation attributes on the lines by way of the Manage Shipment Lines page in the Inventory Management work area.

You manage shipping details for transportation shipments using the Create Pick Wave page in the Inventory Management work area.

How You Screen Shipment Lines for Trade Compliance

Oracle Fusion Shipping integration with a trade management system enables you to screen shipment lines for trade compliance.

You can:

  • Publish trade screening request events that are visible in Integration Cloud Service (ICS)

  • Enable users to determine which lines to screen

  • Enable the trade management system to receive shipment lines and send back screening results

How Compliance Screening Works for Shipment Lines

You can publish a new trade compliance screening event as soon as it's staged or anytime thereafter. This event includes a list of shipment line identifiers and is available by way of ICS. ICS is an end-to-end integration orchestration platform that simplifies how to use and apply product integrations offered within the cloud.

The determination of when an event is published for a shipment line is based on the trade compliance screening method selected for the line. The choices are:

  • None. Shipment lines are not screened for trade compliance.

  • Pick confirm. You must submit shipment lines for trade compliance screening as soon as the lines are picked and staged. However, for outside processing and return to supplier order types, you must submit shipment lines for trade compliance screening as soon as the lines are created

  • User initiated. You must manually submit shipment lines for trade compliance screening after the lines have been pick and staged. You do so by initiating the Check for Trade Compliance action from the Manage Shipments page or the Manage Shipment Lines page in the Inventory Management work area in the Manufacturing and Supply Chain Materials Management offering.

Using this screening event, the trade management system pulls the list of shipment lines that are ready for compliance screening. After screening is complete, the trade management system sends back shipping line updates to Shipping with the screening results.

Shipping Support for Trade Compliance

Shipping enables the trade management system to receive shipment lines and send back the screening results.

The decision to screen shipment lines for trade compliance is transacted independently within the Shipping application. Any setup or decisions made about screening in the order management functions does not have an impact in Shipping. You select the screening method for a shipment line based on the selection made when releasing the line for picking. The trade compliance screening details are available to be included in the shipping documents.

Impact on 3PL and WMS Integration with Shipping

Third-party logistics (3PL) applications and warehouse management systems (WMS) enable integration to transportation and trade management systems directly.

When integrating Oracle Fusion Shipping with a 3PL application or WMS, Shipping does not communicate with transportation and trade management systems directly. Shipping facilitates the external applications to perform the necessary integrations by:

  • Communicating fulfillment, transportation planning, and compliance requirement-related attributes to the external system

  • Using the shipment information regardless of the planning and compliance statuses

Integrate with 3PL and Warehouse Management Systems

Third-Party Logistics and Warehouse Management Systems

A third-party logistics (3PL) provider typically specializes in integrated operation, warehousing, and transportation services that can be scaled and configured to customer need based on market conditions. A warehouse management system (WMS) is a software application designed to support warehouse or distribution center management and staff. This application facilitates management of available resources to move and store materials into, within, and out of a warehouse, while supporting staff in material movement and storage.

Oracle Fusion Applications provide a central integration framework that coordinates communication with a 3PL system or WMS to support purchase order receipts, returns to suppliers, internal material transfers, inventory transactions, and sales order shipments. Using Simple Object Access Protocol (SOAP)-based web services, Oracle Fusion Inventory Management communicates receiving advice and shipment requests to a 3PL provider or external WMS for processing. After completion of processing in the 3PL system or WMS, Inventory Management accepts receipt confirmations, shipment confirmations, and inventory transactions from the 3PL system or WMS.

Overview of Inventory Management Integration with 3PL and Warehouse Management Systems

Oracle Fusion Inventory Management supports a central integration framework for working with third-party logistics (3PL) providers and warehouse management systems (WMS). The inventory management suite of products include Oracle Fusion Receiving, Oracle Fusion Inventory Management, and Oracle Fusion Shipping.

The following figure illustrates how Inventory Management integrates with 3PL and WMS systems. The subsections following the figure provide more detail for this integration.

High-level overview of Inventory Management integration
with 3PL and WMS systems

Receiving Integration

Receiving integration addresses the following points:

  • Sends a receipt advice to the WMS for the various documents, such as purchase order (POs), advanced shipment notices (ASNs), and return material authorizations (RMAs).

  • Receives and processes receipt confirmations to acknowledge the receipt of material, updates the source documents and on-hand details for quantities and other related information, such as lots, serials, and external packing units, and the return of rejected material.

Shipping Integration

Shipping integration addresses the following points:

  • Sends the shipment requests to the WMS for the various documents, such as sales orders and transfer orders.

  • Receives and processes shipment confirmations to acknowledge the shipment of material and updates the source documents.

  • Updates the on-hand details for quantities and other related information, such as lots and serials and splitting of the unfulfilled portions.

Inventory Management Integration

Inventory Management integration addresses the following points:

  • Receives and processes various inventory transactions that can happen within a WMS that might affect the material location and on-hand details. Such inventory transactions include adjustments, miscellaneous receipts and issues, and transfers.

  • Receives and processes inventory balance updates for solving inventory reconciliation challenges.

Inventory Management Integration with 3PL and Warehouse Management Systems Process Flow

Oracle Fusion Inventory Management integration with third-party logistics (3PL) and warehouse management systems (WMS) provides you the ability to outsource part or all of your supply chain management functions.

Using this integration, you can:

  • Improve customer service by minimizing total delivery time and costs using a 3PL provider

  • Improve visibility to expected shipment and receipt detail to better plan import and customs clearance by way of web service payloads

  • Accept returns from your customers with authorization from the manufacturer by way of receipt advices

  • Maintain tighter controls between Inventory Management and the execution system for greater transparency for 3PL or WMS activities

  • Monitor inventory accuracy

The following figure shows a high-level overview of this integration process flow. Details of this flow are provided following the figure.

Inventory Management integration with 3PL and WMS
systems process flow, diagram of

The web service Send Receipt Advice, available by way of Oracle Fusion Receiving, enables Inventory Management to communicate expected shipment lines sent to and received by a 3PL system or WMS. Then, the 3PL system or WMS, by way of the Receive Receipt Confirmation web service in Receiving, communicates confirmation and receipt details of the expected shipment lines.

The web service Material Shipment Line, available by way of the GenerateShipmentRequest operation in Oracle Fusion Shipping, enables inventory management users to send shipment requests to a 3PL system or WMS. The 3PL system or WMS can accept and confirm the shipment requests by way of the CreateandConfirm operation on the Material Shipment web service in Shipping.

Also, within Shipping, you can use the tasks in the Inventory Management work area in the Manufacturing and Supply Chain Materials Management offering so that you can send a shipment request directly from the Inventory Management work area. Additionally, when shipment confirmation errors occur from the 3PL system or WMS, you can select a task in the Inventory Management work area to view the error in a spreadsheet, correct the error, and reprocess the shipment. This action brings the confirmation details into the shipping tables.

The web service Inventory Transaction Manager enables you to receive material transaction updates made by the 3PL system or WMS to keep on-hand balances synchronized with Inventory Management.

Supported Roles for Inventory Management Integration with 3PL and WMS Systems

The features for Inventory Management integration with 3PL and WMS systems are predefined, and you can access them through the following existing job roles:

  • Warehouse manager

  • Receiving and inspection manager

  • Shipping manager

The users roles associated with this feature are:

  • Warehouse operator

  • Receiving agent

  • Shipping agent

Implementation Decision Points and Setup Best Practices for 3PL and Warehouse Management Systems Integration

Oracle provides services required to integrate Oracle Fusion Inventory Management, Oracle Fusion Receiving, and Oracle Fusion Shipping to a third-party logistics (3PL) provider or external warehouse management system (WMS). These product areas work together cohesively to support transfer orders, inventory transactions, reconciliation of inventory balances, and so forth.

Decision Points

Before implementing your external systems integration, consider the following points.

  • If you plan to receive material using a 3PL provider or WMS, then use the predefined scheduled processes to generate a receipt advice.

  • If you plan to ship material using a 3PL provider or WMS, then use the predefined scheduled processes to generate shipment requests.

Setup Best Practices

The following setup best practices are recommended before integrating with external systems.

  • Use a 3PL provider or WMS at the inventory organization level. By representing the 3PL provider or WMS as an inventory organization, virtual tracking and visibility of inventory at the 3PL or WMS location is available to users in real time.

  • For simplicity, set up a receiving subinventory and one subinventory for each material status used in the implementation of Oracle Fusion Inventory Management. For example, you might set up subinventories for receiving, quality assurance, rejected, and available inventory.

  • Use security rules to control access to transactions performed in the 3PL or WMS organization.

Additional Considerations

Keep in mind the following additional considerations when planning your 3PL or WMS implementation.

  • Don't track locator and packing unit information because this data isn't tracked in Inventory Management.

  • Process inventory transactions only when the item status has changed or the item is received into or issued out of Inventory Management. For example, when a third party performs material transactions within locations or packing units at their facility, these transactions aren't tracked in Inventory Management.

  • Track inventory transactions for lot and serialized items in Inventory Management. This tracking is a requirement when lot and serialized items are issued out of inventory to support install base and product genealogy.

Receipt Advice and Receipt Confirmation Processes for External Systems Integration

This topic describes the receipt advice and receipt confirmation integration flow between Oracle Fusion Inventory Management and external systems, such as third-party logistics (3PL) and warehouse management systems (WMS).

Inventory Management communicates receipt advices to the 3PL system or WMS for processing. After completion of the processing in the 3PL system or WMS, Inventory Management accepts the receipt confirmations from the 3PL system or WMS.

For receiving, the web service Send Receipt Advice enables Inventory Management to communicate expected shipment lines to be received by a 3PL system or WMS. Then the Receive Receipt Confirmation service enables the 3PL system or WMS to communicate confirmation and receipt details of the expected shipment lines that were communicated with the Send Receipt Advice web service.

The following figure shows this flow.

Receipt advice and receipt confirmation process
flow for 3PL and WMS integration

Explanation of callouts:

  1. The scheduled process Generate Receipt Advice publishes an event to notify the 3PL system or WMS that receipt advices are ready to be interfaced. The web service Send Receipt Advice provides the ability for the 3PL system or WMS to receive the actual receipt advices with the expected shipment lines for purchase orders (POs), transfer orders, and return material authorizations (RMAs).

  2. After the 3PL system or WMS receives the receipt advices, the 3PL system or WMS performs receiving-related processes including receiving, inspection, and put away.

  3. The web service Receive Receipt Confirmation is initiated, and receipt confirmation is sent to Inventory Management. This web service provides the ability for the 3PL system or WMS to send the material and receiving details for the expected shipment lines received. This service also interprets and transforms the message, and creates the necessary records in Inventory Management. These records carry all the reference information from the external system to easily identify them for performing any future returns or corrections.

  4. Inventory Management validates and processes the receiving transactions by processing the receipt confirmation messages and by updating the release status and integration status.

You can use the scheduled process Manage Receiving Transactions to automatically validate and process the transactions received. If an error occurs while processing the transactions, you can review and correct pending and error transactions using the Review Receipts Interface task in the Inventory Management work area, and resubmit the transactions for processing. When the transactions have successfully processed, the associated document is updated accordingly. For example, the status on an associated purchase order document is updated to Closed for Receiving.

You can use the scheduled process Generate Changed Receipt Advice to manage changes. For example, if there was a change to a purchase order line that was already interfaced but not confirmed, the service sends a changed receipt advice to communicate the associated change to the 3PL system or WMS.

You can use the Receive Expected Shipments page in the Inventory Management work area in the Manufacturing and Supply Chain Materials Management offering to perform receiving of expected shipment lines to record various details, such as integration status. Integration status values include Ready to Interface, Interfaced, and Confirmed.

.

Shipment Request and Shipment Confirmation Processes for External Systems Integration

This topic describes the shipment request and shipment confirmation flows between Oracle Fusion Inventory Management and external systems, such as third-party logistics (3PL) and warehouse management systems (WMS).

The following figure shows this flow.

Shipment request and shipment confirmation processes
for external systems integration

Explanation of callouts:

  1. The outbound shipment request integration process between Oracle Fusion Inventory Management and a 3PL system or WMS starts with a shipment request. The scheduled process Generate Shipment Request enables inventory management users to manually send shipment lines to the 3PL system or WMS using the task Create Outbound Shipment request in the Shipping UI, or they can automate the process using a scheduled process. The shipment request service Material Shipment Line uses the existing pick wave release rules to provide the criteria for selecting the shipment lines.

    Alternatively, the 3PL system or WMS can initiate the shipment request service voluntarily at specified intervals to retrieve shipment requests from Inventory Management.

  2. After the 3PL system or WMS receives the shipment request, the pick, pack, and ship processes are performed.

  3. The web service Material Shipment, when initiated with the required input, receives and processes the shipment confirmation messages. This service interprets and transforms the message, and creates the necessary records in the shipping open interface tables. This transformation provides the mechanism for the 3PL system or WMS to send the material and shipping details for the shipment lines fulfilled.

The scheduled process Perform Shipping Transactions processes the pending transaction records received into the open interface tables. The process validates the data on the transaction records received from the 3PL system or WMS before processing them. Any errors from the validation step are recorded, and the transaction records remain in the open interface tables. The interface records with errors are available for users to view, edit, or resolve the errors, or reprocess.

In the event an error occurs while processing the shipment confirmation messages, users can access the Manage Shipping Transaction Corrections in Spreadsheet task to manage pending transactions by way of a spreadsheet interface using Application Development Framework Desktop Integration (ADFdi) technology. This interface supports management of interface transactions and corresponding errors related to shipment confirmations received from 3PL system and WMS. You can access this task in the Inventory Management work area of the Manufacturing and Supply Chain Materials Management offering.

After the shipment lines are successfully confirmed, the integration status and shipment status are updated accordingly.

Inventory Transaction Processes for External System Integration

All internal material transactions that occur within a third-party logistics (3PL) or warehouse management system (WMS) must be integrated appropriately to keep the inventory picture accurate in Oracle Fusion Inventory Management.

You can use the web service Transaction Manager to maintain inventory accuracy in Inventory Management with the 3PL system or WMS for the following:

  • Miscellaneous account alias issues and receipts

  • Subinventory transfers

  • Interorganization transfers

  • Cycle count adjustments

  • Physical inventory adjustments

  • Material status updates

This service inserts data into the applicable transaction interface tables and calls the transaction manager to process the rows that are ready for processing. If the transaction manager completes successfully, you can view the completed transaction on the Review Completed Transactions page. If the transaction processing fails, you can view the error details as well as transaction data on the Manage Pending Transaction page. From this page, you can correct the data and resubmit to the manager for reprocessing. You can access these pages in the Inventory Management work area in the Manufacturing and Supply Chain Materials Management offering.

Inventory Balances Integration with External Systems

Using Oracle Fusion Inventory Management's inventory balances integration capabilities, you can outsource warehousing and manufacturing processes to efficiently lower costs, service local markets, reduce cycle times, and so on.

A central integration framework across Oracle Purchasing Cloud, Oracle Fusion Order Management, and Inventory Management tracks interactions between the various external systems. You can receive inventory balance details from external systems, such as third-party logistics providers, warehouse management systems, or contract manufacturers and use this information to reconcile inventory balances. Inventory on-hand details can include subinventory, locator, lot, serial number, and external packing unit.

The inventory balances integration feature enables you to:

  • Use the Inventory Balance Transactions service to post inventory balance messages from an external system

  • Import inventory balance messages in bulk using a SaaS spreadsheet

  • Enable users to resolve any processing exceptions

  • Purge inventory balance messages periodically

Note: This feature is automatically available and is included with the shipped job roles (warehouse manager and inventory manager).

Use the following processes and task to interface with external systems to improve tracking and visibility across your supply chain, including partners:

  • Manage Inventory Balances Processes

  • Manage Inventory Balance Messages in Spreadsheet (ADFdi)

  • Manage Inventory Transaction Process

  • Purge Inventory Balance Messages Process

Manage Inventory Balances Process

This scheduled process processes the imported inventory balance messages in the interface tables.

Manage Inventory Balance Messages in Spreadsheet (ADFdi)

Use this task, in the Inventory Management work area in the Manufacturing and Supply Chain Materials Management offering, to review and resolve any exceptions while processing the inventory balance messages.

Manage Inventory Transaction Process

This scheduled process processes the necessary adjustment transactions to reconcile the inventory balances.

Purge Inventory Balance Messages Process

Use this scheduled process to purge the historical balance inventory messages collected over time in the interface tables. Using the processing status parameter, you can purge error, successful, or all messages between a date range.

FAQs for Integrating with 3PL and Warehouse Mangement Systems

Can I synchronize master data with third-party logistics or warehouse management systems?

Yes. Oracle Fusion Product Hub, Oracle Fusion Purchasing, and the Oracle Sales Cloud integration solutions work together to provide integration capabilities to support automated integration for items, suppliers, and customers.

Shipping Documents

Overview of Shipping Documents

Complex processes involving multiple applications and multiple fulfillment scenarios result in the generation of a series of shipping documents. These include the distribution of the documents by multiple mechanisms to a variety of trading partners, the documents required to accompany a shipment, and the documents to be filed with various fiscal agencies.

As a Warehouse Manager or Shipping Manager, you can define sets of shipping documents, called shipping document job sets, and use them to generate shipping documents at pick release or shipment confirmation.

How You Set up Shipping Document Job Sets

A shipping document job set is grouping of reports generated at the time of pick release or shipment confirmation. For example, a shipping document job set could include required shipping paperwork such as the bill of lading, packing slip, and commercial invoice. Use the Enterprise Scheduler Jobs for Financial and Supply Chain Management and Related Applications task to create and manage your shipping document job sets. You can define a group of standard or user-defined shipping reports as document sets or job sets for any business scenario.

Manage Job Sets

A job set is a collection of several jobs in a single process set that you can submit instead of running individual jobs separately.

To create the job sets, do the following.

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Functional Area: Manufacturing Master Data

    • Task: Manage Enterprise Scheduler Job Definitions and Job Sets for Financial, Supply Chain Management, and Related Applications

  2. On the Manage Enterprise Scheduler Job Definitions and Job Sets for Financial, Supply Chain Management, and Related Applications page, open the Manage Job Sets tab, click Actions > Create.

  3. On the Create Job Sets, page, enter the required details and then click Save and Close.

How You Manage Shipping Document Job Set Rules

You can set up the business rules for selection of the document job set. To determine which shipping documents are generated use the Manage Shipping Document Job Set Rules task.

Define Shipping Document Job Set Rules

To define shipping documents job set rules:

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Functional Area: Shipping

    • Task: Manage Shipping Document Job Set Rules

  2. On the Manage Shipping Document Job Set Rules page, click Create New Rule. The page displays the Attributes and Actions tabs, which display a tree-view of the available values.

  3. In the Attributes tab, search for or select the attribute from the tree view, and move it to the IF node to create an IF rule condition. You can use the following attributes to define a shipping document job set rule:

    • Ship-from Organization

    • Ship-to Organization

    • Customer

    • Customer Ship-to

    • Supplier

    • Supplier Order Type

    • Customer Country

    • Carrier

    • Shipping Method

    The Create Condition dialog box appears, which is used to define the rule.

    Note: Alternatively, you can click the New Condition icon in the IF node. The Create Condition dialog box appears, where you can enter the attribute and the rule condition.
  4. Enter the IF rule condition by selecting the operator from the list of operators and entering the value in the text box. Click OK.

  5. Click THEN, select DO, and select Perform an Action.

  6. Enter the DO rule action.

    The following figure illustrates the document job set rule for organization V1 in the following use case:

    IF Ship-from Organization = V1

    THEN DO

    Document Job Set = Ship Confirm Documents

    Shipping document job set rule
  7. Click Save and Close.

Publish a Shipping Document Job Set Rule

To publish a shipping documents job set rule:

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Functional Area: Shipping

    • Task: Manage Shipping Document Job Set Rules

  2. On the Manage Shipping Document Job Set Rules page, select the rule and click Publish.

  3. In the rule dialog box, select Activate Rule and click Save and Close.

    The rule is activated.

Overview of Managing Shipping Document Output Preferences

You can automate the delivery of the shipping documents by setting output preferences and the delivery mechanism for the documents. Use the Manage Shipping Document Output Preferences page to:

  • Define shipping document output preference such as email, fax, and printer

  • Define output preferences based on user, job role, organization, and subinventory

  • Attach shipping documents to a shipment as attachments

You can define output preferences either at the job set level or at the job level. Some job level preferences like format and layout will default from the Oracle Business Intelligence Publisher server.

Define Document Job Set Output Preferences

To define document job set output preferences:

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Manufacturing and Supply Chain Materials Management

    • Functional Area: Manufacturing Master Data

    • Task: Manage Shipping Document Output Preferences

  2. On the Manage Shipping Document Output Preferences page, click Actions > Create.

  3. In the Create Shipping Document dialog box, select the Job Set Name created using the Manage Enterprise Scheduler Job Definitions and Job Sets for Financial, Supply Chain Management, and Related Applications task.

  4. Select the values for the following fields:

    • Job Name

    • Layout

    • Format

    • Start Date

    • End Date

    To enable this document to be automatically attached to the shipment, select Attach Document.

  5. Do one of the following:

    • Click Save and Close to save the new document and close the Create Shipping Document dialog box.

    • Click Save and Create Another to save the new document and create another document.

  6. Search for the shipping documents.

  7. Select the shipping document you created in Search Results and in the Output Preferences section, click Actions > Create.

  8. In the Create Output Preferences dialog box, select values for User, Job role, Organization, and Subinventory and set the following:

    • To configure the shipping document output as a physical copy, set the values in the Printer section.

    • To configure the shipping document output as an email, set the values in the Email section.

    • To configure the shipping document output as a fax, set the values in the Fax section.

  9. Click Save and Close.

For more information on setting up delivery destinations, see the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher.

Manage Quick Shipment

Quick Shipments

For quicker shipment, you can skip pick release and pick confirmation and ship goods on transfer orders and sales orders.

Perform a Quick Shipment

To perform a quick shipment:

  1. In the Inventory Management work area, click Manage Shipment Lines from the Shipments Tasks panel.

  2. On the Manage Shipment Lines page, search for a shipment line that is in the Ready to release, Backordered, Not applicable, or Planned status.

  3. For the shipment line, enter values for inventory details such as Subinventory, Lot, and Serial. Use Record Serial Numbers from the Actions menu to enter the serial number.

  4. Save the shipment line. The Quick ship status appears as a check box in the shipment line details. The shipment line is no longer available for pick release or to be sent to your warehouse management system, third-party logistics provider, or contract manufacturer.

    Note: If you enter values incorrectly, select Reset Quick Ship Status from the Actions menu to reenter the values.
  5. Select one of the following from the Actions menu:

    Stage Lines

    Stage lines in a staging subinventory for packing, compliance screening, or carrier manifesting before you ship confirm.

    Ship Confirm

    Shipment lines are automatically created, packed, and the shipment is closed.

  6. Close the shipments manually or use the Enterprise Scheduled Process.