Warehouse Management

The Oracle Warehouse Management system (WMS) is a component of Oracle’s Supply Chain Management and Manufacturing solution. It spans the areas of warehouse resource management, warehouse configuration, task management, advanced pick methodologies, and value added services.

Inbound Logistics

Oracle WMS inbound logistics refers to receiving, inspection, and put away processes within the warehouse. The major inbound features of Oracle WMS include the following:

• Support for handling Advanced Shipment Notices (ASNs).

The WMS system supports suppliers sending ASNs that might include item, quantity, lot, and serial information, project number and task (with Oracle Project Manufacturing,) as well as the LPNs into which the material is packed. You can receive ASNs through a standard ASN receipt, where LPN contents are verified by the receiver, or through an Express ASN receipt, where the LPN contents do not need to be verified.

• Functionality to receive material directly into unique license plate numbers (LPNs).

All material received through Oracle WMS is associated with a unique LPN. This enables material to be easily tracked and transacted throughout the warehouse, without scanning the item, quantities, lots, or serials.

• Features that enable you to specify and capture lot and serial information at receipt.

With standard Oracle Purchasing, at the time of receipt, you are not allowed to enter lot and serial numbers. With Oracle WMS, however, you can enter lot and serial numbers immediately, at the time of receipt. You can also enter related material statues or attributes that might apply to the lot or to the serial just received.

• Functionality to automate the matching of material received to expected material.

Automatically Matching Material Received to Expected Material Oracle WMS matches the item and quantity received to the document that the material was received against. This means that the receiver does not need to manually select lines or shipments individually. However, Oracle WMS does not show the expected quantity to be received, rather, the system requires the receiver to enter the actual quantity received, and then through a background process, the system matches the actual quantity against the expected quantity.
Instead of having to spend time reviewing the related purchasing documentation, a the time of receipt, automatically matching the received material also enables operators to efficiently process inbound material.

• Support for Oracle Quality.
• System suggested put away locations.
• Opportunistic Cross Docking for backordered sales order lines.
• Support for N step material movement path.

Inbound Setup

1. Receiving area layout
1.1 Segregate inventory and receiving in warehouse
http://www.oracleug.com/user-guide/oracle-inventory/receiving-sub-inventory
1.2 Subdivide receiving area into functional zone
http://www.oracleug.com/user-guide/warehouse-management/locator-zones
1.3 Subdivide zones into locators and assign locator types
http://www.oracleug.com/user-guide/oracle-inventory/5-define-locators

2. Inbound material flow
2.1 Route the material in the physical warehouse lay out
http://www.oracleug.com/user-guide/warehouse-management/set-operation-plans
2.2 Define the rules & strategies

Organization Parameter

• Direct operators to put an item away in the same locator where the item is already stored
• Prohibit commingling of different items or different lots of the same item in a single locator
• Avoid lot commingling in a locator
• Base the put away location on inspection results, the type of purchase order, or item category
• Direct operators to put away items based on refrigeration restrictions.

1. In the Quantity Function field, use the list of values to select the equation that you want the system to use to determine the capacity of the potential locators for this put away rule.
2. In the Object field, use the list of values to select the first business object for the rule.
3. In the parameter field, enter the value associated with the business object.
4. In the Operator field, select the mathematical operator that supports the rule conditions, for example equals or greater than.
5. If you want the system to sort the locator’s that will be returned by the rule, enter the sort criteria on the Sort Criteria tab, by selecting the object, parameter, and ascending/descending specification.

After you finish defining all of your rule restrictions and have specified the appropriate sort criteria, return to the Restrictions tab and select the Enabled check box if you want to enable the rule. Select the Common to All Orgs check box if you want the rule to be available for all organizations.

WMS Strategies
A strategy is a list of rules to apply, in sequence, until the put away is complete.

Assign strategy to item

Receiving Parameters

Receiving options are set up at the Organization-level. However, most of the options that you set in the Receiving Options window can be overridden for specific suppliers, items, and purchase orders fore details check

http://www.oracleug.com/user-guide/purchasing-overview/defining-receiving-options

WMS Inbound Features

The WMS system also supports the following:

Optional inbound material inspections: The system supports an inbound inspection flow that includes a receipt step, an inspection step, and a put-away step. The system does not increment on-hand balances until the inspection and put away are complete. Inspections can be performed using standard Oracle Purchasing Inspection or using the optional module of Oracle Quality. Commingling of accepted and rejected material into the same LPN is not prevented by the system. It should be done operationally. If WMS is enabled in a Project Manufacturing organization, Oracle Quality can be set up to trigger collection plans based on project and task numbers.

System assigned cost groups: At the time of receipt, the system will assign a cost group–providing that you have set them up–to the inbound material. WMS separates physical inventory accounting from standard cost group accounting. This enables you to assign split portions of an LPN different cost groups.

System suggested put-away locations: Using the WMS Rules Engine, the system will suggest an optimal put away location for inbound material. Put away suggestions are not enforced by the system and therefore, you can override them at the time of put away.

Workflow enabled discrepancy actions: If you override a put away suggestion at the time of put away, then you must provide a reason for the change. You can optionally build workflow notifications and corrective actions that are triggered on put away override reasons.

System suggested opportunistic cross-docking: If you enable cross docking for your warehouse, then before suggesting a put away location, the WMS will attempt to cross-dock inbound material directly to an outbound staging area to fulfill backordered sales order lines.

Monitor and track inbound material using receiving locators: The inbound area can be defined as a receiving subinventory and segmented into locators. The inbound material can be received in receiving locators in order to monitor and  track movement within the inbound area.

Describing Receiving Documents
The WMS supports the following receiving documents:

• Purchase orders, with or without ASNs
• Return material authorizations (RMAs)
• Inter-org intransit shipment documents
• Internal requisitions
• Blanket purchase orders

Performing Receipts

To start the standard receipt process an operator scans the incoming document, or enters the document number. Next the operator scans the LPN if it exists. If an LPN does not exist, the operator can create a new LPN. The operator then scans or enters the item numbers, quantity, lot number and serial numbers if applicable. The system then matches the material to the document shipping lines according to the matching algorithm. The operator then enters the receipt header information and finally puts away the material. The system does not increment the on hand balance for the material until the operator transfers the material from a receiving subinventory in to a storage subinventory.

Standard Receipt Flow

The direct receiving flow is very similar to the standard receipt flow. An operator scans the incoming document or enters the document number to start the receiving process. Next, the operator scans the LPN if it exists. If an LPN does not exist, the operator can create a new LPN. Next the operator can scan or enter the item numbers, quantity, lot number and serial number if applicable. Finally the operator scans or enters an inbound staging lane or stock
locator for the material. The system then matches the material entered to the document shipment lines according to the matching algorithm. The system increments the on hand  balance for this material as soon as the operator completes the receipt.
 
An operator can optionally choose to perform a put away to enable the rules engine to suggest a storage location, but if the operator received the material directly in an appropriate storage location no further transactions are necessary.

Receipts Using the Receiving Common Interface
Businesses need to be able to perform receipts without knowing the document types they are receiving against. The single receiving common user interface allows receipts against all inbound document types. Document types include Purchase Orders, Return Material Authorizations, Intransit Shipments, ASN, and Internal Requisitions. If your business does not need to use one common user interface to perform all the receipts, it is advisable to use the different menu entries for each of the types of receipts. This will increase the performance while validating the list of values.

1. Navigate to the Receipts screen by selecting All from the Receiving menu. The Receipts screen displays the document field where you can enter the document number without knowing the document type you are receiving against.

2. The Document field is an LOV that includes all the open purchase orders, return material authorizations, intransit shipments, and internal requisitions against which the material can be received. Warehouse Management will determine the document type, displaying a list of values if there are multiple matches.

3. Based on the document type, once you exit the Document field, the user interface changes to look exactly as if you would have performed the receipt for that document type after initiating it directly from the menu. For example, if the scanned document is a purchase order, the Supplier and Line Num fields would display on the user interface. Also based on the document type selected, the prompt for the Document field changes. In this example it changes to PO Num so you understand you are performing a PO receipt.

WMS Rules Engine

The Oracle Warehouse Management (WMS) rules engine provides a repository for restrictions and business policies related to your warehouse. You define and implement rules, directly from standard Oracle Applications forms, without having to write custom code. Instead, you can compose rules, by selecting various elements from lists of values. Special security features have been included in the rules engine to prevent modification of rules that are currently in use.

Rules Engine Capabilities and Rule Types

• Enables directed picking - Directed picking
• Enables directed put away - Directed put away
• Assigns cost groups to received material - Cost group assignment
• Assigns tasks to a resource with the appropriate training and equipment - Task type assignment
• Determines which operation plan will be used for consolidation - Operation plan selection
• Ensures customer compliant labeling - Label format assignment

Rules & Strategies

You use a series of Oracle Warehouse Management rule types to set up various rules for your warehouse. Although you use the same windows to set up all rules, the setup that is required for Cost Group, Picking, and Put Away rules differ from the setup that is required for Task Type, Label Format, and Operation Plan Selection rules. You do not
assign task type, label format, and operation plan selection rules to strategies. Rather, the rules engine automatically links these types of rules directly to the organization when you enable the rule . The search order is determined by a weight applied. The larger the number, the higher the weight. You can assign weights only to task type assignment, label rormat, and operation plan selection rules.

Use the following windows to set up rules:

1. Rules window
2. Strategies window
3. Rules Workbench

Storage and Facility Management

Material Management

Storage and Facility Management

Material Management

License Plate Numbers (LPNs)

In Oracle Warehouse Management, a license plate number (LPN) is any object that holds items. Although LPNs are associated with containers, they do not need to represent a physical entity, such as a box. Thus, you can define an LPN as a collection of items.

1. Store information about an LPN such as item, revision, lot, serial, organization, subinventory, or locator
2. Track contents of any container in receiving, inventory, or in-transit
3. Receive, store, and pick material by LPN
4. View on hand balances by LPN
5. Move multiple items in a transaction by LPN
6. Transfer LPN contents
7. Pack, unpack, consolidate, split, and update LPNs
8. Print labels and reports for referencing container contents
9. Track nested LPNs Oracle Internal & OAI Use OnlyOracle Only
10. Reuse empty LPNs
11. Receive and send LPN information on an ASN

Nesting License Plate Numbers

Generating License Plate Numbers

You can generate LPNs using one of the following methods:

1. Automatically by submitting a concurrent request
   
2. Manually by generating LPNs using a mobile device

Viewing LPNs

You can use the Material Workbench or the mobile user interface to view the contents of an LPN.



In the Material Workbench, you can view the attributes of a particular LPN. Use the following instructions to view the contents of an LPN.
1. Navigate to the Material Workbench window
2. In the View By field, select LPN from the list of values.
3. Expand the Organizations folder to display a list of LPNs for the organization.
4. Select the LPN that you want to view.
The system displays the contents of the LPN in the right panel of the window. You can also expand an LPN in the left column to view its specific contents. Continue expanding the LPN to see increasing levels of detail.
5. When you are finished, close the Material Workbench to return to the navigator.

LPN Context

Warehouse Management defines a context for each LPN to denote the current state. You can use these contexts to define specialized picking and put away rules. You can also query by context in the material workbench.


1.1 Pre-generated
Pre-generated LPNs exist in the system, but, are not associated with any physical material.

1.2 Defined but not Used
This context refers to a defined LPN that does not contain material. An example is a reusable tote an operator can use to pick orders.

2.1 Resides at Vendor Site
When a vendor sends an Advanced Shipment Notice (ASN) ASN, Warehouse Management generates an LPN and associates it with the material information on the ASN. Warehouse Management does not recognize material associated with LPNs of this context as on hand or costed.

2.2 Resides in Receiving
An LPN with this context indicates material associated with this LPN was received using a standard routing or inspection routing receipt, but still resides at the receiving dock. The material does not reside in inventory and is not costed.

2.3 Resides in Inventory
An LPN with this context indicates material associated with this LPN is costed and accounted for in inventory. an operator cannot this context when receiving material against a standard or inspection routed receipt, but can use it for a direct delivery routed receipt. operators can perform outbound transactions on LPNs with this context.

3.1 Pre-Pack for WIP
LPNs that reside in WIP, and are associated with material pre-packed in WIP, receive this context. This context is used after Warehouse Management associates the LPN with the material, but the material is not physically packed in the LPN.

3.2 Resides in WIP
An LPN with this context indicates material associated with this LPN is currently part of a WIP operation. The material does not reside in inventory, and is not costed.

4.1 Picked
Picked LPNs receive this context. They are in-transit within the warehouse.

4.2 Packing
The system uses this context internally as an intermediary during picking, put away or packing. Do not use it anywhere, including the setup of picking or put away rules.

4.3 Loaded for Shipment
This context refers to material loaded for shipment onto a carrier that is ready to leave the warehouse. Once the carrier leaves the dock, the LPN context changes to resides in in-transit, or issued out of stores.

4.4 Issued out of Stores
LPNs with this context do not reside in the warehouse. However, the system retains the LPN transaction history. LPNs shipped out of inventory receive this context and cannot be received again.

5. Resides in In-transit
An LPN with this context indicates material is moving from one location to another. For example, when an LPN moves from one organization to another. LPNs in this context are in an intermediary state, but are accounted for in the system. This context is used only for inter-org transit or internal sales orders where an indirect shipping network is defined between the organizations.

Maintaining LPNs

Updating LPNs


You can update the attributes of a LPN including:

1. Weight UOM
2. Volume UOM
3. Volume content
4. Container item

Lot Transactions

Lot and Serial Attributes

Warehouse Management Setup

This section provides an overview of the setup requirements for Oracle Warehouse Management system (WMS).Setting up Oracle WMS includes setting up related Oracle applications, such as Oracle Inventory and Oracle Bills of Material. Therefore, you might only need to make WMS modifications specific to existing data, like existing items. Check with your
implementation team to determine which setup requirements have already been fulfilled.

Oracle Warehouse Management system requires that Oracle Inventory, Oracle Purchasing (Receiving), and Oracle Order Management (Shipping) are installed and set up.

This chapter covers the following topics:

1. Overview of Oracle Warehouse Management Setup
2. Warehouse Organization Setup
3. Set Up Subinventory Parameters
4. Set Up Locator Parameters
5. Setting Up Locator Zones
6. Material Setup
7. Defining Shipping Parameters
8. Implementing Profile Options

Locator Zones

A zone is a logical grouping of locators. A zone may represent a specific work area(s) such as a Packing station(s) or it may just indicate an area where material movement occurs. The locators for a zone may span one or more subinventories You can specify a zone for an operation when you define the operation plan. This association determines the candidate set of locators where the particular operation is performed. You can use zones to define the path that material takes in the course of completing an activity. Defining zones is not mandatory especially if the warehouse is small and the operations are not complex where subinventories and / or locators could suffice.

You can also use zones for workload balancing and optimization. Users can optionally sign-on to zones and consequently can only perform tasks that originate within the zone.


1. Navigate to the Zone Summary window.
2. Enter the name of the zone in the Name field.
3. Optionally, enter a description of the zone in the Description field.
4. Optionally, select a Disable Date from the list of values. If you enter a date in this field, the zone is disabled on this date.
5. Choose the Enabled Flag to enable the zone.
6. Save your work.
7. Choose View/Modify to open the View Modify Locators window

Task Management

Task planning is the release of work to the warehouse floor in order to optimally run the day-to-day warehousing operations. Once multiple tasks are created from the various task creation sources, they are placed in one single pool and released appropriately to the warehouse floor for optimal operation of the warehouse. Optimization is performed by task interleaving and resource-workload balancing.
Tasks are comprised of

1. Demand pick tasks for sales orders, work orders, and replenishment.
2. Inbound receiving and put away tasks
3. Inbound-outbound hybrid cross-docking tasks.
4. Inventory transfer tasks
5. Inventory control related cycle counting tasks

1. Pick
2. Put away
3. Move order issue
4. Move order transfer
5. Replenishment
6. Cycle count

Task Setup Steps

Task planning is the release of work to the warehouse floor in order to optimally run the day-to-day warehousing operations. Tasks are comprised of demand pick tasks for sales orders, work orders, and replenishment. Tasks are also comprised of inbound receiving and put away tasks, slotting inventory transfer tasks, inventory control related cycle counting tasks, and inbound-outbound hybrid crossdocking tasks. Once multiple tasks are created from the various task creation sources, they are placed in one single pool and released appropriately to the warehouse floor for optimal operation of the warehouse. Optimization is performed by task interleaving and resource-workload balancing.

Wave planning in warehousing plans the allocation and release of material to the warehouse floor in the form of work/tasks in order to fulfill the various kinds of material demand. It plans the release of material to fulfill sales orders, work orders, and replenishments.

You need to be able to plan the release of tasks in the warehouse on a day-to-day basis so that you can run operations optimally to minimize cost and maximize productivity. To do this, you need a single workbench that enables you to view the entire workload for one or more days. Using the Warehouse Control Board, you can query tasks based on multiple criteria, re-prioritize and interleave them, and release them to the warehouse floor in the form of task waves.

Equipment & Employee

WMS -> Set up -> Resources -> Equipment

Rules Window

Use the Oracle Warehouse Management Rules window to set up any of the six rules types: Picking, Put away, Cost group, Task type, Labeling, Operation plan selection

1. Setup for picking and put away rules differs from the setup for cost group, task type, label assignment, and operation plan selection rules. Picking and put away rules require a quantity function and use an optional sort criteria, while the assignment-type rules require a return value. Picking rules also have optional consistency requirements as well as the choice of allocation modes.

2. In the header section of the Oracle Warehouse Management Rules window, you select the type of rule to define. You also specify a name and description for the rule, and the quantity function or return value. If you are creating a picking rule, you also specify the allocation mode for the rule.

3. You must also enable the rule, if you want the system to consider it for use in a strategy. After you enable it, the system also checks the rule for proper syntax.
Note: After you enable a rule, you cannot change it. Furthermore, rules that you assign to a strategy cannot be disabled. To modify a rule already assigned to a strategy, you must disable the strategy and then disable the related rule. If an enabled rule has not been assigned to a strategy and you need to modify it, clear the Enabled check box.

4. You can optionally make the rule available to all of the organizations in your company. If you enable a picking or put away rule in all organizations, then other organizations can include it in strategies. If you make a task type, label format, and operation plan selection rules available to all organizations, then all organizations will use the rule, because there are no strategy assignments for these types of rules.

5. The rules engine comes seeded with several basic rules. For seeded rules, the User Defined check box is clear. You cannot edit seeded rules, but you can use the rule copy function on the Tools menu to copy a rule.

Restrictions Tab
You specify the business objects, their related parameters, and the restrictions of the rule. Each line in corresponds to a restriction on the Restrictions tab. You use the AND and OR operators to join multiple lines of restrictions. You use the open and close parenthesis to create complex compound statements. The Sequence Number field in this window, enables you to specify the sequence in which the restrictions are linked together.
Note: When you set up restriction sequence numbers, consider a numbering scheme, such as 10, 20, 30. This enables you to easily add more restriction lines, if necessary.

Strategies Window

After you define your rules, you must set up a strategy and then associate the applicable rules. After you assign rules to a strategy, the rules engine can execute the strategies on any objects to which the strategy applies. The rules engine executes each subsequent rule in your strategy until an allocation is completely filled.

After the rules engine finds a strategy, it will not continue to another strategy if the task cannot be fulfilled based on the first strategy. Therefore, unless you want the strategy to fail if specific restrictions are not met, the last rule in your rule strategies should be a default rule that includes no restrictions. You set up strategies in the Oracle Warehouse Management Strategies Window.

When you define strategies, verify that the User Defined check box is selected; for seeded strategies, the User Defined check box is clear. You cannot modify system defined strategies, however you can copy them using the strategy copy function located in the window's tool bar.

Make sure you enable the strategies so that the strategies can later be assigned in the Rules Workbench. To add rules strategy, you specify a sequence number in which you want the rule to be considered (within the strategy) and then use the list of values in the Rule Name field to select the rule that you want to add.

The Partial Success Allowed check box enables the system to only partially fulfill the requirements of a rule's allocation, and then move onto the next rule in the strategy.
Note: Enabled strategies cannot be modified. To modify a strategy, you must disable the strategy by clearing the Strategy Enabled check box

Rules Workbench

The Rules Workbench enables you to assign strategies, rules, and cost group values directly to any number of objects in an assignment matrix.
The Rules Workbench provides you with the following functionality:
• Add, update, or delete strategies, rules, and cost group values in the selection criteria
• Enable and disable selection criteria in the assignment matrix
• Hide and show columns of the strategy selection matrix based on user preferences
• Query where a rule, strategy, or cost group value is assigned
• Assign crossdock criteria to business objects for planned and opportunistic

The Rules Workbench is comprised of two regions:


Rules Workbench Tree
Rules Workbench tree displays a view of all the rules and strategies that are available in the organization.
In the Rules Workbench, a rule type to view to assign The Rules Workbench contains the following rule types:

• Picking
• Putaway
• Cost group
• Planned crossdock
• Opportunistic crossdock

• Rules Workbench Matrix

Inventory Transactions with LPNs

You can use Oracle Warehouse Management to pack LPNs with any grouping of material into a locator. You can then enter the LPN to transact the material. The system transacts all contents of the LPN, including the contents of any LPN nested within the LPN. You can associate LPNs with the following inventory transactions:

• Miscellaneous issues
• Subinventory transfers
• Direct inter-organization transfers
• Move order transactions

Locator Alias

A locator alias is an alternative identifier that corresponds to a physical locator. It can be a check digit, a unique identifier, or a non-unique identifier. For example, you can use the check digit 13 as the locator alias for the locator 06-06-01. The system does not suggest a locator alias to you during a transaction, it suggests the actual locator.

Locator aliases ensure the presence of a user at the physical location. You can use a barcode to represent the locator alias. This ensures that when the alias is scanned, a user must be present at the physical location.

Locator Alias Setup
You enable locator aliases when you setup your organization. You must also enable locator aliases for individual subinventories. When you create you locators, you also create locator aliases.
If you enable locator aliases for a subinventory, then you must enter a locator alias for all transactions in and out of the subinventory. If the subinventory is under dynamic locator control you cannot create a locator during a mobile transaction. The only way you can generate a locator for this type of subinventory is during a desktop transaction.

Locator Alias Uniqueness
There are three uniqueness options for locator alias: no uniqueness constraints, unique within a subinventory, and unique within an organization. For example, if you set the Enforce Locator Alias Uniqueness parameter at the organization level, and you create the locator alias 12 for locator C1.1.1 in organization W1, then you cannot use that locator alias anywhere else in the organization; however, you can use locator alias organization W2. If you set the Enforce Locator Alias Uniqueness Parameter at the organization level, then the subinventory level parameter is disabled.

You can also use the same locator aliases for more than one subinventory or within the same subinventory if you set no uniqueness constraints. For example, you can use check digit 13 as the locator alias for locators 06-06-01 and 06-06-02 in subinventory FGI.

You define locator alias uniqueness in the Locators Maintenance window. You define the organization-level uniqueness in the Organization Parameters window.You define the subinventory-level uniqueness in the Subinventories window.

Locator Alias Behavior
For user and system directed pages, the locator alias behavior depends upon locator uniqueness. During a transaction, the system prompts you to enter the locator alias when you navigate to the locator field on that page. If the locator alias is unique, then the locator segments appear, and you can navigate to the next field. If you enter an incorrect alias, then the system displays an error message, and prompts you to enter the correct alias. If the locator alias is not unique, then after you enter the locator alias you must also enter the locator segments that correspond to the locator alias.

Set up Operation Plans

Operation plans define the material movement path and the sequence of operations to perform to complete an activity. You can use both inbound and outbound operation plans. You can create inbound Operation plans using the following inbound operation plan types:

• Standard: Standard operation plans apply to any move order lines that does not require inspection, or was not crossdocked. A standard operation plan can end in a receiving or inventory locator. It can also traverse multiple receiving and inventory locators. You cannot follow a drop to an inventory locator by a drop to a receiving locator, because once you drop material to an inventory locator, it is delivered to inventory.
• Inspect: Inspect operations plans apply to move order lines that have the Inspect Required flag set. The inspect step is the last step in the operation plan. Inspect operation plans do not allow drops to inventory locators.
• Crossdock: Crossdock operation plans apply to crossdocked move order lines. The crossdock step is the last step in the operation plan. The crossdock step implies a load and a drop to a staging locator. The drop operation before a crossdock operation does not happen in inventory.
  

1. Set up Zones: If you choose to segregate your material by zones, you must create zones.
2. Set up Operation Plan Assignment Rules: You must set up operation rules in the Rules window to tie your operation plans to your system rules.

1.  Direct consolidation in staging lane across deliveries
2.  Direct consolidation in staging lane within delivery
3.  LPN based consolidation in staging lane within delivery
4.  LPN based consolidation in staging lane across deliveries
5.  LPN based consolidation in consolidation locator, across deliveries in staging lane
6.  LPN based consolidation in consolidation locator within delivery in staging lane
7.  Locator based consolidation in consolidation locator, across deliveries in staging lane
8.  Locator based consolidation in consolidation locator within delivery in staging lane.

Setup Task Filters

The task filter window enables you to determine which tasks the picking page can perform. If you include a task type, then the picking page can perform the task type. You can use task filters to control the types of tasks the system dispatches to operators.
For example, you can create task filters so an operator receives internal order pick tasks, but not replenishment tasks.



1.Navigate to the Task Filters window.

2.Enter the filter name in the Name field.

3.Enter a brief description of the filter in the User Name field.

4.Enter a long description in the Description field.

5.In the Task Source alternative region, select the Include check box to include the associated task source. That task sources are as follows:
• Internal Orders
• Move Order Issues
• Move Order Transfers
• Replenishments
• Sales Orders
• Work Orders
• Cycle Counting

6.Save your work.

Task Dispatch and Assignment

The above figure shows the picking task processes.

First, the system evaluates the picking rules to come up with a material allocation.

Next, the system evaluates the task type assignment rules in the sequence indicated by the rule weight, and then assigns the task type of the first rule where the restrictions are met. In this example, the rules have been set up based solely on the subinventory of the task, resulting in the task type assignments indicated above.

Now the task will be split based on equipment capacity.

Finally, after performing the material allocation, task type assignment, and task splitting, the Task Dispatch engine dispatches the tasks to each operator's mobile device, based on their equipment and task type assignment. When the operator completes the task and requests the next task, the system dispatches the next closest task that the operator is qualified to perform with the equipment that is currently available.

Note: The previous example provides a detailed view of picking tasks. However, the Oracle Warehouse Management performs replenishment tasks using an identical process.

Task Management Setup
Setting up task type assignment and dispatch includes setting up the following:
Resources
Equipment items
Equipment resources
Departments
Setting up task type assignment rules

Task Type assignment Rules
The Oracle Warehouse Management Rules Engine enables the system to assign task types to tasks. Like the picking and put away rules, task type assignment rules can be based on a variety of data, including the following:

Unit of measure (UOM) defined for the pick line: for example, if the pallets need to be picked, the Task Type Assignment engine can dispatch tasks to the pallet pickers

Ownership of the material: for example, if the item belongs to XYZ company, and XYZ requires that their hazardous material be handled by a resource that has hazardous material handling skills, then the Task Type Assignment engine will dispatch tasks associated with XYZ's hazardous material handling requirements

Task Type Assignment and Dispatch
Assume that your warehouse has the following human resources, each assigned to the roles and equipment shown in the following table.

Performing Task

Explaining Task Unloading
A task that has been loaded can be unloaded at any point prior to the task drop.
Unloading a task enables you to reverse the task load, returning the material, or full LPN, to the same locator from which it was picked. If the material requirement that has created that task has been cancelled, then the task will be cancelled when it is unloaded.

This is particularly for change management of sales orders and work orders.

You can use the Manual Unload page to unload tasks loaded using advanced pick load.

To unload a task:
1. Navigate to the Manual Unload page.
2. Enter the task to unload in the Current Task field.
3. Choose <Unload> to unload the task, or <Cancel> to cancel the task unload.
4. If you choose <Unload>the Unload page appears. The unload page displays the From LPN, From Subinventory, From Locator, Item, UOM and Qty, or displays the Subinventory and Locator information if you are unloading the entire LPN.
5. Choose <Unload> to unload the task, or choose <Cancel> to cancel the unload.

Explaining Task Skipping
An operator may be unable to perform a task that has been dispatched to them due to conditions outside their control, and do not warrant another type of task exception. For example, the aisle to which he or she was directed may be temporarily blocked. The operator may skip the task it is returned to the pool of pending tasks and dispatched again.

Task Exceptions
If at any point during the pick process the user reports a discrepancy, warehouse manage can initiate a corrective action workflow. Discrepancies might include any of the following:

• Picking a different quantity than the quantity suggested by the system
• Dropping material into a different staging lane than the staging lane suggested by the system. If a discrepancy is reported, the system immediately directs the user to an audit screen, where he or she is prompted to indicate a reason for the mismatch.

Warehouse Control Board

Oracle Warehouse Management creates tasks such as picks, put away, moves, and replenishments and dispatches pending tasks on demand to mobile radio frequency devices.

The Warehouse Control Board is a tool that Oracle Warehouse Management and supervisors use to monitor, plan, control, and execute various warehouse operations, including the following:
• Effectively use resources
• Query tasks

• Plan tasks
• Release tasks to the warehouse floor
• Assign, reassign, and prioritize the progress of tasks
• Perform manual scheduling
• Cancel crossdock tasks
The Warehouse Control Board enables you to view workloads across the entire warehouse, manage exceptions, and review, release, reassign, and re-prioritize tasks.

Specifically, the Control Board enables you to do the following:
• View tasks: including unreleased, pending, queued, dispatched, active, loaded, completed, and exception tasks
Note: At the time of pick release (Sales Order or WIP), you can specify whether or not to plan the release of tasks. If planning is opted, pick tasks are created with a status of Unreleased so that you cannot perform or execute them immediately. If you do not want to plan the tasks, pick tasks are created with a status of Pending.

• Manage task assignments: including mass selection/refinement through add, remove and filtering features, the mass change/update of task status, priority, resource assignments and sorting on various fields, for the resultant task record set view

• View task exceptions: including a description of the cause for failure You can also view the status of each task, including the time in which it was dispatched, the time it was picked up, and the time it was dropped into a staging lane. If any errors occurred in processing the task, you have full view of the error reported, and the task in question's current status.

Task Status
The task status is the current task state. Task statuses are as follows:
Unreleased: The task was created, but is not eligible for dispatch. Managers use this status to control when the task is released. Managers can update tasks in this status to Pending, (eligible for dispatching), or Queued.

Pending: The task was created and can be sent to any available operator. Pending tasks are dispatched to operators in sequence of priority, subinventory picking order, and locator picking order in relation to the operator’s last known position. Warehouse Management filters tasks by task type, current operator equipment, and subinventory. It dispatches a task in Pending status only when there are no more Queued and Dispatched
tasks assigned to the operator.

Queued: Managers use this task type to manually assign a task to a particular operator in the warehouse control board.

Dispatched: The task is dispatched to an operator, but the operator has not started the task. Note: Dispatched behaves like queued except the system assigns the operator to the task based on pick methodology instead of by a manager in the control board.

Active: The task the operator is performing. The system dispatched the task to the mobile device, but the user has not loaded or dropped the task. The status of the task changes, as soon as either the task is loaded or dropped. The operator assigned to the task also displays in the WMS Control Board.

Loaded: The task is loaded; however, no material transaction has posted. To complete the task, the operator must drop the task.

Completed: The task has been completely transacted.

Outbound Logistics

Pick release is the process of selecting orders for release to the warehouse for picking and shipping. After the orders are released, Oracle Warehouse Management uses the Rules Engine to determine the appropriate material allocations. After the system completes the allocations, the Task Type Assignment engine assigns the appropriate
task types, and the system can then suggest packing configurations.

At this point, the task is now ready for dispatching to an operator. The operator can then log onto the system, optionally sign onto a material handling device, and accept pick tasks. Optionally, the operator can accept all pick tasks for a specific task grouping as a bundled set of tasks. Oracle Warehouse Management enables the operator to pick multiple partial LPNs, full LPNs, and loose picks for a single task. Loose material and material packed in an LPN can be picked in any sequence for a given task. Operators can continue to load material as long as there is capacity on the equipment. After the material is loaded, it can be dropped into staging lanes for further packing and labeling before shipment. This completes the material picking process. At this time, order lines are also split or merged based on equipment capacity defined for the equipment and pick methodology defined by pick slip grouping rules.

Outbound logistics enables operators to pick, pack, and ship orders to customers. Outbound logistics contains the following components:
1.1 Pick Release
1.2 Rules (Release rule, release seq rule and picking rule)
1.3 Tasks/Task Type Assignment

2.1 WMS Control Board
2.2 Load
2.3 Drop

3.1 Consolidation/Packing
3.2 Dock Door Appointments
3.3 Shipping

1.1 Pick Release
The picking process enables operators to pick material to fulfill orders. Warehouse Management supports three types of picking: order picking, replenishment picking, and WIP picking. The system distributes picks to operators as tasks.

1.2 Rules
During implementation, you can create rules to fulfill orders in the most efficient manner. The following rules support the picking process:
• Release Rules: The picking criteria of order lines for pick release.
• Release Sequence Rules: The order the system releases delivery lines for picking.
• Pick Slip Group Rules: How the system groups tasks on a move order pick slip report for picking.

1.3 Tasks
Warehouse Management creates and dispatches tasks to qualified operators based on rules you configure.

2.1 WMS Control Board
The WMS Control Board provides managers with a real-time snap shot of the warehouse, and enables them to redistribute tasks as needed. They can monitor the progress of tasks as well as manually dispatch tasks to operators.

3.1 Consolidation
Warehouse Management enables operators to consolidate partially filled containers in to fewer and better-optimized containers.

Packing
Warehouse Management enables operators to pack containers with multiple levels of nesting, and sends notifications if an order contains special packing instructions. Operators can perform packing during picking or as an independent process.

3.2 Dock Appointments for Trips
Managers can use Warehouse Management to schedule outbound carrier appointments, dock door availability, and staging lane usage within the warehouse.

3.3 Shipment Verification and Close
Once an operator picks and loads an order, Warehouse Management automatically determines the items and quantities to deduct from inventory.

Overview of Picking

Picking enables operators to pick material to fulfill orders. Warehouse Management supports three types of picking: order picking, replenishment picking, and WIP picking. Warehouse Management dispatches picks to operators as tasks. Managers can perform manual pick release, or you can create a series of rules to automate the process during implementation.

Please read the pick release basics @
http://www.oracleug.com/user-guide/order-management/pick-release

Warehouse Management uses the following rules to release orders: pick release rules, release sequence rules, picking rule and pick slip grouping rules.

Pick release rules determine how the system to selects sales orders for release. If trips are not scheduled for dock doors, then pick release rules also determine the appropriate staging lane for sales orders. After the system determines the sales orders to release, it can use release sequence rules to determine the sequence delivery lines are released for picking, based on sales order number, outstanding invoice value, scheduled date, departure date, and shipment priority. Pick slip grouping rules establish how tasks are grouped on a move order pick slip.

picking rule in inventory determine the order in which revisions, lots, subinventories, and locators are picked for sales orders. Picking rule in WMS is used for directed picking creates material allocations and directs operators to pick material from specific locations.



They workin conjunction with the different pick methodologies. Pick methodologies refer to the different method an operator performs picking tasks. For example, an operator may select to pick an order by itself, or to pick multiple orders at the same time.

The system generates picking tasks and dispatches them to qualified operators based on rules. After picking is complete, the system provides operators with the appropriate number and size of containers the order requires for shipping.

Explaining Pick Release
The pick release process selects sales order lines to release to the floor for picking and shipping. A pick release rule stores the criteria that will be used to select sales orders for release. If trips are not scheduled for dock doors, then the release rule also determines the staging lane to which the material should be delivered.

Replenishment Picking

• Pick loose items into an LPN
• Pick whole LPNs
• Pick multiple LPNs, for example, pick 5 boxes of 10 each to fulfill a task to pick 50
• Pick from LPNs, for example, pick 5 items out of a box of 10
• Pick multiple partial LPNs, full LPNs, and loose picks for a single task
• Build larger LPNs
• View cartonization suggestion

Pick Methodologies

Pick methodologies refer to the different ways in which you might select to perform picking tasks. For example, you might select to pick an order by itself, or to pick multiple orders at the same time. The type of picking methodology that a warehouse uses depends on the kinds of operations that they run. For example may opt to use
cluster picking in order to pick multiple orders in one pass.

Oracle Warehouse Management supports the following pick methodologies:

Discrete picking: The system dispatches discrete groups of tasks, grouped by pick slip grouping rules.

Order picking: The system assigns picks for one order or job/schedule at a time to a user. Thus, when a user accepts a task for the first line of a job/schedule or sales order, all other picking tasks associated with that job/schedule or order are automatically assigned to the user as well, regardless of the task type or subinventory.

Wave picking: The system dispatches tasks line by line, regardless of the subinventories where those tasks are picked from, or to whom other lines on the order have been dispatched.

Bulk picking: The system groups tasks to pick the same items that are sourced from the same locator so you only see one task that might represent picks for several order lines. Deconsolidation of order lines occur at pick drop. Oracle Warehouse Management automatically splits bulk tasks based on equipment constraints during the pick release process. You can choose to bulk pick items at pick release via the pick slip grouping rules, or choose to use the concurrent program to bulk pick across pick waves after pick release. You can also bulk pick within a delivery or
across deliveries.
The following bulk pick exceptions apply:
• The system does not allow bulk picking for cartonized items
• The bulk picked item must be the same revision.

Zone Picking: Zone picking enables you to utilize all of the picking methodologies but restricts to a specific subinventory. You designate the subinventory before you begin your picking tasks.

Cluster picking: A specified number of clusters is dispatched to a single user at once. A cluster is defined as all the tasks related to a sales order delivery, or a manufacturing job or schedule. The number of clusters can be set for the organization, or controlled by each user individually. Cluster picking offers significant levels of optimization by enabling a user to pick multiple orders at a time by interleaving the pick tasks for various orders and sequencing them in ascending locator/optimal travel sequence. This enables the user to pick orders in its entirety before proceeding to pick more orders.

Pick and pass/label picking: LPNs are generated by the system during cartonization and the labels are printed prior to picking. To pick, the user scans the LPN and is dispatched the picking task associated with that LPN. The user can then "pass" the LPN to the next user or continue picking all material for the LPN and will not be
prompted to drop the LPN in the staging lane, until all the lines have been picked.
Note: If you select order picking as the pick release methodology, and specify an order picking rule type at pick release, the system bypasses all bulk picking checks at the subinventory and the item and does not bulk pick any material as part of that pick release.

Paper-based picking: Users pick according to a paper pick slip that is printed at pick release. This enables a user to dispatch tasks to themselves when working in a paper-assisted environment.

User-defined pick grouping

Performing Picks

1. Bulk picking reduces the number of times goods are processed and returned to a user. After pick release occurs for both outbound sales orders and internal orders, or for manufacturing component picks, Oracle Warehouse Management consolidates tasks of similar characteristics into a single bulk task. This process can be initiated either at the time of pick release, or through a concurrent program separate from the pick release process.

An advantage to bulk picking is that a typical warehouse operation will benefit from a reduced replenishment effort once bulk picking is employed. Replenishment is the process by which material from a packed or overstock bulk location refills the forward or fast picking area for high velocity items.

2. Paper based pick

Task Loading and Dropping

Task loading and dropping includes the following and completes the Oracle Warehouse Management picking task process.

• Loading material onto equipment
• Dropping material directly into a staging lane or consolidation locator

SO to Pick Confirm - Complete Process

1. Create a sales order


2.  Lunch the pick release with below parameters
Auto Pick Confirm = NO (Ensure that require pick confirm is enabled in organization parameter if you want to pick loose material instead of LPN)
Auto Allocate =YES
Plan task =YES
Use an LPN controlled sub inventory as pick from sub inventory.


3.  Navigate to Ware House Manager - > Inquiry -> Warehouse Control Borad  and query with the sales order number.
Verify the task created in unreleased status and note down the pick id.


4. Navigate to  asks->Manual Tasks->Paper Based Pick->Enter Pick ID of Unreleased Task and complete the picking task.



Verify the task status

5.  Navigate to  asks->Directed Tasks->Directed Move->Drop Loaded LPNs -> Enter the LPN
Complete the picking task by droping the item.

Receiving Options (Mobile & Desktop)

Mobile Receiving Options
Receiving Substitutes
Operators can use the mobile device to receive substitutes if Allow Substitutes is enabled on the shipment line, and substitutes are defined for the item.

Receive Expense Items
Operators can use the mobile device to receive expense items, but the expense items cannot be traced in the warehouse after receipt.

Receive Vendor Item
Operators can use the mobile device to receive vendor items by the vendor item number. However, vendor items are traced through the original item number in the warehouse.

Receive by GTIN Number
Operators can use the mobile device to receive numbers by GTIN number instead of the internal item number.

Enable Shortage Notification Messages
The system can generate shortage notifications after receipt when material shortage is enabled
for items and a backordered sales order or WIP job exists.

Unavailable Mobile Receiving Options
Warehouse Management does not support the following receiving options:
Blind receipts- Warehouse management does not support blind receipts.

Receipts without a document or item- Operators cannot use the mobile device to receiving material if they do not have the document information or the item information.

Unordered receipts- Operators cannot use the mobile device to receive unordered material in to the warehouse.

Receipt Corrections- Operators cannot use the mobile device to make receipt corrections.

LPN Receipts

Receiving LPNs Using a Mobile Device
Using the mobile device for receipts helps operators to track material in the warehouse.
Operators can reuse defined but not in use LPNs, and nest an LPN for a normal receipt.
The system requires LPNs for receipts except in the following cases:

• Expense items
• Direct receipts

Cross Docking

Crossdocking is the use of inbound receipts to satisfy outbound demands. You can use crossdocking to match outbound shipments to scheduled receipts in advance. This enables you to achieve faster flow-through times and optimize warehouse resources.

Before system uses the rules engine to determine a put away suggestion, Warehouse Management checks for backordered sales order lines or WIP jobs that incoming material can fulfill if you enable cross docking for the organization. If Warehouse Management finds an eligible line, it prompts operator to put away the incoming material directly to an outbound staging lane or issue it to the WIP job. This flow avoids the unnecessary material handling and material processing.

If only a portion of the incoming material is needed to fulfill the requirement, the system directs the operator to cross dock the material needed to fulfill requirement. The system then uses the rules engine to find an optimal storage location for the remaining quantity. The system checks for cross docking opportunities before it suggests storage put away locations, if you enable cross docking for the organization.

Cross docking is available only for standard and inspection routing receipts. Depending on the parameter setting for the organization, the system may prioritize WIP demand before or after sales order demand.

Crossdock planning horizon/window
Crossdocking occurs during a period of time known as the crossdock planning horizon. The crossdock planning horizon is the time period within which the system considers demands with a schedule shipment date for  crossdocking.

The earliest crossdock time is the beginning of the crossdock planning horizon. This is the maximum time difference that a scheduled receipt can lag with respect to the scheduled shipment time. For example, if the earliest crossdock time is four hours, and a demand exists with a scheduled shipment time of 6:00 p.m., then the system does not consider material with a scheduled receipt time that is earlier than 2:00 p.m.

The latest crossdock time is the end of the crossdock planning horizon. This is the minimum time difference that a scheduled receipt can lag with respect to the scheduled shipment time. For example, if the latest crossdock time is one hour, and a demand exists with a scheduled shipment time of 6:00 p.m., then the system does not consider material with a scheduled receipt time that is later than 5:00 p.m.

The crossdock window is the difference between the earliest and latest crossdock time. For example, if the earliest crossdock time is four hours, and the latest crossdock time is one hour, then the crossdock window is three hours.

Example :
Let, Earliest cross dock time = 7 hours
Latest cross dock time = 2 hours
A SO is scheduled to be shipped @ 10PM
Then cross dock window is (7 – 2) = 5 hours
And cross dock horizon starts @ (10 – 7) 3 PM and ends (10 -2) 8 PM

Cross Docking Types
Oracle Warehouse Management supports two types of crossdocking, planned crossdocking and opportunistic crossdocking. Planned crossdocking matches expected receipts to a demand source, and opportunistic crossdocking matches demands to received supply.

In case of Planned crossdocking the pre-allocation is done during Pick Release. In opportunistic crossdocking dynamic allocation is done during material putaway.

You use planned crossdocking and opportunistic crossdocking for different scenarios. Planned crossdocking works best when you know your supply in advance. It enables you to control the throughput of your warehouse and matches known demand with expected supplies. Opportunistic crossdocking helps with uncertainties. It uses the rules
engine to match newly arriving supply to existing demands. This helps in cases in which a supply or demand source is changed, modified, or cancelled.

Crossdocking Setup

You use the Cross dock Criteria window to determine the eligible supply and demand sources for crossdocking. After you create a crossdock criterion, you enable it in the rules workbench /or else can default it from organization parameter for opportunistic cross docking.

To Create a Crossdock Criterion, navigate to the Crossdock Criteria window.

1.1 Enter a name and a description for the crossdock criteria.
1.2 Select the Criterion Type. Planned crossdocking attempts to select a supply from among eligible supply sources and matches it to a given demand source.
Opportunistic crossdocking selects from eligible demand sources, and matches it to a given supply source.

2.1 Enter the time bucket for which the system considers documents for crossdocking. You can enter a crossdock window in days, hours, or minutes.
2.2 Enter the Order Processing Time. This is the time required to process the order. If you do not enter a value in this field, then the system automatically assumes the value is zero. You can enter an order processing time in hours, days, or minutes.
2.3 Enter a Buffer Time. This is the time required to safely fulfill an order. The system uses the order processing time and the buffer time to trigger exceptions. The system does not consider supply and demand that occur within the buffer zone for crossdocking. If you do not enter a value in this field, then the system automatically assumes the value is zero. You can enter a buffer time in hours, days or minutes.
2.4 Enter a Past Due Supply Cut-Off. This is the offset time the system uses to determine the past due supply cut off time fence. This parameter is used for planned crossdocking. The system does not consider any supply that occurs beyond this time fence for crossdocking.

Example
The following demand exists for which crossdocking needs to be planned at 8:00 a.m. The order processing time is two hours, the buffer time is one hour, and the crossdock window is four hours. Shipment 1 has a shipment time of 3:00 p.m. and Shipment 2 has a scheduled ship time of 4:00 p.m. The time fences for the demand sources are:

1. Approved PO
2. ASN
3. Internal Requisition
4. Intransit Shipments
5. Material in Receiving

• Sales Order (Scheduled)
• Sales Order (Backordered)
• Internal Order (Scheduled)
• Internal Order (Backordered)
• WIP Component Demand (Backordered )

Planned Crossdocking

Planned crossdocking occurs during pick release. Oracle Warehouse Management uses release sequence rules to sequence demand sources, and fulfills the demand based on the allocation method that you specify during pick release. When you run pick release, the system uses the allocation method to determine whether crossdock should be planned. If crossdock should be planned, then the system uses the crossdock criteria that you specified to determine the eligible supply. If you did not define the crossdock criteria during pick release, then the system uses the rules workbench to determine the appropriate planned crossdock criteria to use for the demand.

If the system identifies a supply source other than inventory for fulfillment, then it determines the scheduled ship time for the delivery lines, and assigns the scheduled ship date and times to delivery lines as follows:
• If an outbound trip exists, then the system bases the departure time on the dock schedule.
• If the sales order is associated with a delivery, then the system checks to see whether a carrier exists. If a carrier exists, then the system bases the departure dated on the carrier time and dock door appointment.

If multiple dock door appointments for the carrier exist, then the system selects the dock door and appointment that is closest to the scheduled ship date and time.
• If the sales order has a specified ship method, then the system determines the carrier and the exact time for the carrier if the carrier has a dock door appointment for the same day. If multiple appointments exist, then the system selects the appointment that is closest to the scheduled ship time and date.
• If none of these conditions apply, then the system uses the departure time as the scheduled ship time for the order; however, if the crossdock criteria allow scheduling flexibility, then the system assumes the order can ship anytime during the day.

To perform planned crossdocking Oracle Warehouse Management:

1. Determines supply eligibility
2. Performs pegging
3. Creates delivery
4. Links reservation to supply and demand
5. Assigns crossdock operation plan
6. Changes delivery line status to Planned for Crossdock

Plan CrossDocking Example

• Crossdock Window : Wait Time, Time during which cross docking takes place
• Order Processing Time (OPT) : The time required to complete the shipping process;Load/unload/move Time
• Buffer Time (BT) : Extra time provided for Safety margin
• Past Due Supply Cut-off (PDS) : To exclude uncertain supplies; Any supply before this time is ignored by the system.Suppose current time is 10AM and PDS is 30 mins then system would ignore any supply before 9.30 AM

• Maximize Crossdock (FIFO)
• Minimize Wait (LIFO)
• Custom

2. Crossdock criteria assignment

• Locator based consolidation in consolidation locator, within delivery in staging lane
• LPN based consolidation in consolidation locator, within delivery in staging lane
• Direct consolidation in staging lane within delivery
• LPN based consolidation in staging lane across deliveries
• Direct consolidation in staging lane across deliveries
• LPN based consolidation in consolidation locator, across deliveries in staging lane
• Locator based consolidation in consolidation locator, across deliveries in staging lane

Planned Crossdocking Setup

• Crossdock Window : Wait Time, Time during which cross docking takes place
• Order Processing Time (OPT) : The time required to complete the shipping process;Load/unload/move Time
• Buffer Time (BT) : Extra time provided for Safety margin
• Past Due Supply Cut-off (PDS) : To exclude uncertain supplies; Any supply before this time is ignored by the system.Suppose current time is 10AM and PDS is 30 mins then system would ignore any supply before 9.30 AM

• Maximize Crossdock (FIFO)
• Minimize Wait (LIFO)
• Custom

2. Crossdock criteria assignment

• Locator based consolidation in consolidation locator, within delivery in staging lane
• LPN based consolidation in consolidation locator, within delivery in staging lane
• Direct consolidation in staging lane within delivery
• LPN based consolidation in staging lane across deliveries
• Direct consolidation in staging lane across deliveries
• LPN based consolidation in consolidation locator, across deliveries in staging lane
• Locator based consolidation in consolidation locator, across deliveries in staging lane

Opportunistic Crossdock

Opportunistic cross docking is supply initiated. When you receive materials against a PO, Warehouse Management System can use those newly receiving material to fulfill an existing demand like a SO (scheduled or backordered), an Internal order (scheduled or backordered),  a WIP Component demand(backordered),  if you enable Opportunistic Cross docking on the Organization Parameters window.

Warehouse Management uses the rules workbench to determine the appropriate crossdock criterion to use for supply. Depending on the eligible demand sources, crossdocking goal, and time fences that you specify in the opportunistic crossdock criteria, the system determines to which demand to crossdock the supply. It then stamps and operation plan on the material. To perform opportunistic crossdocking, the system:

1. Validates supply source
2. Determines eligibility pool
3. Performs pegging
4. Creates reservations
5. Creates delivery

Cartonization, Consolidation and Packing

Warehouse Management uses cartonization to suggest the best packaging configuration for a group of items. The system presents packaging suggestions to operators in the following ways: automatically generating LPNs, printing container and shipping labels, and during tasks.

Cartonization can segregate items by categories you identify during implementation based on different packaging requirements. For instance, refrigerated goods may require a particular type of insulated cooler, while miscellaneous goods can be packed into any standard corrugated cardboard box. In addition, the warehouse may use several sizes of each type of container. You can also set minimum fill percentages for containers, below which, the system suggests a smaller container.

You can create multiple levels of packaging, along with the requisite labels, so operators can generate labels in a single operation, for inner cartons, outer cartons, and pallets. Operators can halt packing with a hierarchy of containers midway, and then continue again at a later point. Operators can pack material in a storage container during receipt, and pack it again during sales order picking into a final shipping container.

All these considerations, in addition to the item dimensions, weight, and volume in comparison to the physical attributes of the container, are made when the system selects the container type and quantity to use.

How it works
Suppose there are 2 products – Mobile and Digital Camera which needs different kind of packaging. For mobile create an item category MOBILE with the ‘Cartonization groups’ as the item category structure.Next attach the item category MOBILE to both the container item and contained item category sets.
Create a mobile item MOB01 and attached it with the category set contained item & category MOBILE.
Similarly create a mobile container item CONTAINER_MOB01 and attached it with the category set container item & category MOBILE.

Now when system does the Cartonization for the item MOB01, it ‘ll consider CONTAINER_MOB01 as the packaging material.

You can do the similar kind setups for Digital camera products.

Consolidation enables multiple operators to drop material assigned to a delivery in to the same locator or LPN prior to placing the consolidated load in a staging lane.
Note: If necessary, operators can ship material directly from the consolidation location.

Packing Material
Packing involves transferring of loose items or LPNS into an LPN. Operators can pack items either on receipt, while they reside in inventory, or during outbound shipment to customers. Operators can use both the desktop and the mobile device to pack material. While desktop packing allows packing for inbound and outbound material, mobile packing allows packing for outbound material only. The benefits of packing include:
• Consolidation of items into suitable containers based on criteria such as item, delivery, sales order, or warehouse location
• Confirmation and record the contents of containers while packing
• Transaction by container
• Protection of packed items from damage

LPN Put Away Process

In addition to supporting LPN put away from a Standard Routing, Oracle Warehouse Management enables you to initiate a put away by scanning an LPN anywhere in the warehouse.

After you scan an LPN, you have the option of loading that LPN onto your current equipment, or dropping the LPN immediately. If you load the LPN, you can scan additional LPNs onto their equipment then begin dropping LPNs whenever they are at the appropriate locations to be dropped.

Note: Putaway transactions must be carried out using the manual load, directed drop, drop an LPN, or manual drop pages.

Manual Loads
A manual load is a put away task that you create.
You can use the Manual Load page to fully load the contents of one LPN into another LPN to put away the outer LPN.
You can also transfer the contents of one LPN into another LPN in order to put away the second LPN. Finally, you can use the Manual Load page to select items from an LPN and put away only those items. For efficient warehouse operations, you sometimes need to put away individual contents of an LPN and then consolidate the content at various warehouse storage locations. To accomplish this, you load an entire LPN and then specify which items of the LPN to put away at the various storage locations.

To perform a manual load, complete the following steps:

Label Printing

WMS labeling features helps you to move inventory more efficiently through the warehouse. Supplier labeling speeds-up the receiving process by enabling bar code scanning of inbound purchase orders, that results in less receipt processing time, immediate recognition of available materials, and higher receiving accuracy.

Labeling also enables you to comply with customer requirements for barcoding. You can produce customer-specific labels on demand for each shipment and for advanced shipment notices (ASNs).

You can also use labeling in flow manufacturing. Each step in the manufacturing flow can use labeling.
Customer Labeling Requirements Customer labels are typically centered on the following major requirements:

1. Label format
2. Label data
3. Bar code specifications
4. Symbol content

• Materials label: Provides information about an item, including the item's lot information, if applicable.
• Serial label: Provides information that is specific to a serial of an item.
• LPN label: Provides information about the License Plate Number (LPN). This label does not contain content information. You typically use the LPN label to identify LPNs as they travel throughout the warehouse.
• LPN Contents label: Provides information about the LPN contents. You typically use this label to identify LPNs as they travel throughout the warehouse.
• LPN Summary label: Provides information about the LPN and a summary view of the LPN contents. If an LPN contains multiple LPNs, then all of the contents of all the nested LPNs are summed by item, revision, and lot.
• Location label: Provides information about specific warehouse locators.
• Shipping label: Provides information for an outbound shipment. It does not include information about the contents of the shipment. It includes only addresses and  information that is pertinent to the shipment itself.
• Shipping Contents label: Provides information about outbound shipment. It includes information about all of the contents that are part of the shipment.
• WIP Content label: Provides information about the WIP components that are picked for a WIP job. It includes component number, serial, lot, job number, assembly number, and start date.

Defining Custom Label Fields

You can create custom label fields and associate them with label formats. This enables you to have additional control over the values that are listed on a label. You can write a custom SQL statement to create the custom label field.

For example, if you have a requirement to show the carrier PRO number, and the system does not seed this field,  then you can write a custom SQL statement that creates this field.

The custom label field that you create appears in the Define Label Fields window along with the seeded values. You should restrict this window from certain responsibilities; only users with knowledge of SQL should have access to this window. You can use any field that you create on this window in a label. To define custom label fields:

1. Navigate to the Define Custom Labels window.
2. Select the label type. This associates the fields with the appropriate label type.
3. Enter the field name, description, and SQL query statement.
4. Save your work.

Associating Label Types to Business Flows

After you set up label formats, you must associate them with the specific warehouse business flow where you want to use them. This association enables the label type to be printed automatically as part of that business flow.

You can also print the same label type from different business flows with a different format used at each flow. For example, many times a package is labeled with a carton label when it is picked (Shipping Contents label type at Pick Load business flow), but is then labeled with a shipping label when it is shipped (Shipping Contents label type at
Ship Confirm Business flow.) This enables you to set up a label format selection rule that is based on the business flow that the label print request was generated from.

The following table provides a list of the various business flows and the types of labels that you can associate with each flow. The horizontal header row of the table lists the various label types that are available. The far left vertical column lists the warehouse-related business flow. The number in parentheses ( ) indicates the business flow code number that is needed when you are defining Rules Engine format based rules. Yes indicates that the system can generate the label type for that business flow.
No means that the system does not generate that label type for the business flow.

Label Format Assignment Rules

Printing Modes

Oracle WMS provides 3 different ways to integrate third party printing software with WMS.
1.    Asynchronous mode
2.    Synchronous Mode - Generic
3.    Synchronous Mode – TCP/IP
The profile option WMS: Label Print Mode determines the printing mode.
Asynchronous Mode

In Asynchronous Mode, Warehouse Management creates an Extensible Markup Language (XML) file and transfers it to a directory the third party software monitors. You cannot use Warehouse Management to monitor the status of the print request after creation of the XML file.
Note: The profile option WMS: Label output directory determines the output directory.

Asynchronous mode of architecture is simplest to set up and debug, as there is a
clear external record of the label request. Disadvantages of asynchronous printing include latency, possible security issues to FTP files across servers if print server running on different platform, and no possibility for response.

1. Oracle WMS places the XML file in a specified Directory.
2. Print Server / Other tool monitors the specified directory and picks up the XML.
3. Print server / Other tool modifies the XML.
4. Print server maps the XML to the label format and generates print stream in printers proprietary language.
5. Printer prints the label

Synchronous Mode – Generic

In Synchronous mode of integration, Oracle WMS generates a label XML and sends it directly to the partner via one of two synchronous methods. In the first method, the integration is via an API implemented by the third party application that replaces an empty stub provided by Oracle. Third party software processes this XML and prints the XML. You need to set the profiles - ‘WMS Label Print Mode’ to ‘Synchronous – Generic’.

1. Oracle WMS calls Synchronous API and pushes the XML to print server / other tool.
2. Print server / Other tool modifies the XML.
3. Print server maps the XML to the label format and generates print stream in printers proprietary
language.
4. Print Server prints the label at the specified printer.

Synchronous Mode TCP/IP

Synchronous Mode TCP/IP is a real-time integration mode between Warehouse Management and third party software that is handled through a standard ethernet TCP/IP connection. Warehouse Management ensures the printer or print server is listening to the IP and port and successfully receives the XML string, but does not receive the status the detailed status of the print request.

Label Printing Strategies

Oracle WMS and MSCA have robust label printing capabilities built into the product to easily produce compliance labels at any point in the business process and with any data. Oracle works with two types of label printing partners – direct to- printer, and print server – to provide the full end-to-end solution, and each of these partners have different strengths.

Oracle WMS produces label XML files as part of a transaction or event, such as a purchase order receipt, pick confirmation, work order completion, or license plate generation.

To print the Oracle generated label XML, you will always need the actual label printers, as well as a label design application (LDA) to define the graphical layout of the variable and boilerplate data. These strategies differ, however, on the basis of the integration of the XML to that format occurs within the printer firmware with no other middleware, or in a separate print server application.

Direct-to-print label printers that natively understand Oracle’s XML allow you to directly print the Oracle generated label XML without any middleware or print server. 
The print servers, on other hand, add an intermediary layer between Oracle Applications and actual label printer. Although the print servers introduce an additional partner and added implementation cost, they also provides significant value in the areas of print management, label configuration and manipulation, error management and Internet printing.

Oracle supports two types of label printing configurations:
1. Printing using a third party label software and a print server
2. Printing using XML enabled Direct Label Printers.

The printing strategy selection depends on several factors – ROI, real time latency, need for compliance labeling, printer models in current use, volume of labels to be printed, network infrastructure et al. To reiterate, each additional layer between Oracle WMS and the printer gives you additional flexibility, while also generally  also meaning additional complexity and cost.

PRINT SERVER SOLUTIONS
This strategy require s you to have a configuration of Oracle WMS, third party label printing software, print server and a network of printers. The LDA allows you to define the different label formats that need to be printed, as well as manage the library of formats for an enterprise printing solution. The print server manages the print queue, comes with necessary printer drivers and the printer parameters associated with them. Finally, the label printer actually prints the label. The label printer can be from any vendor supported by the print server. Typically, the LDA and print server come same the vendor.

This strategy is recommended when you have a high volume of labels to print from each printer, and also is often simpler to maintain when the label formats change frequently. The LDA or related application sometimes enables you to configure the label with the content being derived from many sources, where the Oracle XML forms just one such source. A print server partner is usually recommended when the Oracle XML needs to be manipulated beyond the capabilities of standard Oracle functionality prior to printing, such as to pull in additional data elements, split an individual label request into multiple labels, or control the destination printer beyond Oracle’s basic rules. Many of the third party label software will allow you to custom program a label in these – and other – ways. Third party label print software will use Oracle XML as the primary data sources for the label fields, executing additional logic or ODBC calls as required.

Another use of these extended capabilities from the print server partners is to compensate for the fact that Oracle MSCA lacks an inbuilt rules engine like Oracle WMS to determine the label to be printed. However, some label printing software help you to configure rules to determine the label to be printed and manipulation of the label.

This strategy is also recommended when you have printers from multiple manufacturers in a single site that all need to print a single format, as only some of the printers in your facility may be able to support XML directly, and furthermore, each of the Direct-to-Printer partners uses different LDAs that produce different pre-compiled output that may need to be loaded to the printers in different ways and using different tools. Additionally, the advanced queuing / print job management capabilities make this a preferred option when more than two or three  users need to concurrently print large batches of labels from a single printer. While the print server partners may require an additional investment in software licenses and implementation costs, when you have characteristics such as those above that require the features of these partners, your total cost of ownership will actually be lower than trying to use the simpler architecture of the Direct-to-XML printers

Print server sloution works with all the three printing modes :  Synchronous TCP/IP,  Synchronous Generic & Asynchronous.

XML DIRECT PRINTER
In this strategy Oracle WMS sends the XML directly to the printer. The label printer is capable of receiving XML that meets Oracle’s label specification and merges with pre-defined label formats to print a label.

This strategy can be easily deployed when the Oracle XML does not need any manipulation to produce the label desired. The volume of printing and the number of users that would need to print concurrently to a single printer is also a factor.  For instance, when more than three or four users may trigger simultaneous requests to print to a single printer, the number of available connections on some of the printers may be exceeded, or for large jobs, the buffers may overflow. While Oracle provides multiple mechanisms for reprinting so that the jobs are not lost, these volume and concurrency considerations should be included in evaluating the XML Direct printers against each other, and against a print server partner.

With some XML Direct partners, XML-enabled printers are only supported on their flagship printer models, so that you may pay a premium for this capability.  On the other hand, all XML Direct printers to date are capable of running both modes, whereby they can parse both XML from Oracle and the print stream in their proprietary language, typically without any change in configuration, and typically, also simultaneously, so the same printer can be used in multiple ways, and you can easily change to a print server as your requirements grow.

The XML Direct strategy calls for pre-loading the printers with label formats. Since there is no centralized print server, every time you add a printer to the network, you need to load the required label formats, and every time you add a format, you need to add it to all the printers. Some  partners have printer management software to aid in this decentralized approach.

XML direct printers work with both Synchronous TCP/IP and Synchronous Generic mode of printing. To enable to print in TCP/IP mode, you need to set ‘WMS Label Print Mode’ to ‘Synchronous – TCP/IP’ and define the TCP/IP IP
address and port number for each printer in the network.

Cartonization

Cartonization is the process that suggests a container to pack items based on constraints such as cubic volume of items and container volume. Oracle Warehouse Management uses cartonization to suggest the best packaging configuration for a group of items. The system can present the packaging suggestion to you in one of many ways, including automatically generating license plates, printing container and shipping labels, and presenting the suggestion to you as part of a task.

You can create multiple levels of packaging, along with the requisite labels, so you can generate in a single operation, labels for inner cartons, packed inside outer cartons, and placed on a pallet. You can halt packing with a hierarchy of containers midway, and  then continue again at a later point, so you can pack material in a storage container when it is first received or completed, and then pack it again during sales order picking into a final shipping container.

All these considerations, in addition to the item dimensions, weight, and volume in comparison to the physical attributes of the container, are made when the system selects the container type and quantity to use.

Cartonization Uses
Oracle Warehouse Management uses cartonization in three places:

1. Sales order and manufacturing picking
2. Prepack for manufacturing completion
3. Inventory bulk pack

1. Single Item – An item is always matched to the same container based on the static relationship you setup in the item/container relationship window.
2. Mixed Item – Uses the contained-container item capacity and dimension restrictions defined on the master item window and checks it against the category and category set setup as well.
3. Pick Slip Grouping – Generate an LPN for all items that belong to the same pick slip.
4. Customer Algorithm – Uses a stub API to interface with customer-defined cartonization rules.

Cartonization Process

The cartonization algorithm Oracle Warehouse Management uses minimizes the number of containers used at each level in the packaging hierarchy, subject to volume, weight, and minimum percent fill settings of the containers. The algorithm also verifies the dimensions of the packed material can fit inside the dimensions of the container.

If you defined multi-level hierarchy after all the material is packed at the first level, the  algorithm repeats itself with the new containers. The process continues until the top of the packaging hierarchy has been reached, the packaging process has completed the indicated number of levels, or no additional containers are available due to minimum
percent fill, dimensions, or other physical attributes.

The following two examples illustrate how cartonization works on a single and a multiple level cartonization hierarchy. Although labels are generated at all levels in the cartonization process, LPNs are only created for the outermost level for each request.

Single Level Cartonization


Single level packaging hierarchies are most commonly used during sales order pick release for Pick by Label functionality, or to select the right packing container. You may also use it for packing material in inventory and generating labels prior to manufacturing completion if the labeling requirements are simple.

Steps
1. Define an item and assigned contained category group. Define a container and assign the container category.
2. Create a SO and Run pick release with Auto Confirm – No, Create Delivery – Yes, Auto Allocation – Yes, Plan task – Yes.
3. Navigate to Load
Enter the pick id (transaction number on warehouse control board)
4. System‘ll show the container number as per the setup.

Multi Level Cartonization


Use multi level packaging hierarchies when you require labeling for more complex packaging configurations, such as when you need to pack inner boxes into outer boxes, that are placed on a pallet. The multiple levels can be packed all at once, or when using the mobile Bulk Pack page, can be broken up into several intermediate steps. Labels can be generated for each of the many levels of the hierarchy.

Packaging vs. LPN
Only the outermost level created at each level of cartonization is defined as a license plate. License plates are not generated for intermediate levels. You can only calculate material availability at the innermost license plate level, and the rules engine cannot allocate nested LPNs and you cannot pick them in a single transaction. The way you
create license plates and packaging entities impacts how labels print and on-hand balance maintenance.

Content and Summary Labels
Labels generate for each level in the packaging hierarchy regardless of whether you create a license plate or record the level as packaging.

LPN Summary labels are printed at every level during the cartonization process. These multi-record labels include all the items contained at or below the current cartonization.

LPN Content labels print at every level that contains loose material. For levels that license plates are not generated, the innermost packaging level contains loose material and a LPN Content label may be printed. Because material availability calculations do not have visibility to packaging levels that do not have license plates, the system also
prints an LPN Content label for the innermost license plate even if there are other levels of packaging inside the license plate.

You can identify all levels created by cartonization with a unique number. If a license plate exists, the number is the license plate number. If a license plate does not exist, the number is a packaging identifier that can be included on the label. You can print the identifier (packaging or LPN), as well as the immediate parent of the level on every
content and summary label. Thus an LPN Summary label may be identified by a package ID and a parent license plate number, or by a license plate number and a parent package identifier. These relationships help you pack the material as determined by the defined packaging hierarchies.

Setting up Cartonization

You must perform several setups steps before you can use cartonization. For items that always require a specific container, use the container load relationship. For other items packed into containers in a container group, you must create categories to group the container types and the items. You must then assign the corresponding items to the
categories, and assign the physical characteristics such as volume and weight. Finally, you must define the containers the, designate physical characteristics, and assign them to the corresponding categories. You must enable sales order cartonization at the subinventory and organization levels if necessary.

1.1 Subinventory and Organization Setup

1. You can turn on cartonization, in which case pick released lines are cartonized regardless of the allocation subinventory.
2. You can turn off cartonization in which case no pick released lines are cartonized.
3. You can configure cartonization at the subinventory level. The system first checks the cartonization flag on the subinventory definition before cartonization.

Define Cartonization Groups

A flexfield structure, called Cartonization Groups, is seeded with the system. Therefore, to define cartonization groups, you need only to select the Cartonization Groups flexfield structure and then set up a category code and description for each group.

1.3 Assign Cartonization Groups to Cartonization Category Sets
After you set up the appropriate cartonization groups (also known as category codes), you assign the groups to category sets. You must assign cartonization groups to the following two category sets:

1. Contained item, which represents items that are packed
2. Container item, which represents the actual container, such as a box, or pallet into which items are packed.

Containers and Contained Items

After you set up the appropriate category codes and category sets, you must define the containers and cartons into which you will later pack items. Because containers represent another type of item, you use the Master Items form to set them up.

Note: You must define container items and contained item with the same unit of measure class. For example, if you have an item defined in inches, and a container defined in centimeters, the system will make the conversion from inches to centimeters (or centimeters to inches), because both units of measure are of the UOM class, Length

Defining Contained Item


After you set up appropriate category codes and category sets, you must modify or update the attributes of the items for which you want the system to suggest containers.
For cartonization to work properly, you must update the following item attributes:

• Item's category set from the Contained Item category set
• Physical dimensions of the item: weight, volume, and dimension

Container Load Relationships

Some items require specific containers. These items have container load relationships, which are direct relationships between a container item and a contained item. The relationship specifies how many of the contained item can fit into one container. You set up container load relationships in the Container Item Relationship window.

Although you can establish multiple relationships for a single contained item, the cartonization process uses only the preferred relationship. There can be only one preferred relationship for each content item.

Prior to setting up these relationships, the container items must be properly setup. Any container item setup using the steps above will is a valid container item for a direct relationship. Alternatively, to setup items just for direct container load relationships, the only required step is to check the container flag in the container object group. No other
physical attributes of the contained item or container item need to be entered.

more details @
http://www.oracleug.com/user-guide/order-management/managing-packingcontainerslpns

Consolidation

Consolidation is the process of bringing material from various parts of the warehouse together for the purpose of packing and shipping. Consolidation can occur at one or more points during the outbound flow of material. Most warehouses perform consolidation of picked material so it can be packed prior to shipment. Some warehouses perform subsequent consolidations such as building pallets of packed items and then shipping the pallets.

Oracle Warehouse Management allows eight types of system-directed consolidation based on the following key factors:
• Should material be consolidated in a consolidation locator or directly in a staging lane?
• Should consolidation occur at the LPN level?
• Can material from different deliveries be consolidated based on the operation plan while upholding the consolidation rules such as no loose material is allowed in the outermost LPN?

1. LPN Based Consolidation in Staging Lane Within Delivery
This is the default consolidation method. This consolidation method enables you to consolidate material for a single delivery directly to an LPN in a staging lane. The system suggests the last LPN that is dropped off for delivery in the staging lane.

2. Direct Consolidation in Staging Lane Across Deliveries
This consolidation method enables you to consolidate material across deliveries in a staging lane. In this consolidation method, you do not consolidate material in a consolidation LPN within the staging lane. The system does not suggest a drop into LPN for the material.

3. Direct Consolidation in Staging Lane Within Deliveries
This consolidation method enables you to consolidate material for a single delivery directly in a staging lane. The system does not suggest a drop into LPN for the material.

4. LPN Based Consolidation in Consolidation Locator Across Deliveries in Staging Lane
This consolidation method enables you to consolidate material across deliveries into a consolidation LPN in a consolidation locator. After you consolidate the material, you can use the mass move functionality to move all the material to the staging lane.

5. LPN Based Consolidation in Consolidation Locator Within Deliveries in Staging Lane
This consolidation method enables you to consolidate material within a delivery into a consolidation LPN in a consolidation locator. After you consolidate the material, you can use the mass move functionality to move all the material to a staging lane.

6. LPN Based Consolidation in Staging Lane Across Deliveries
This consolidation method enables you to consolidate material across multiple deliveries into a consolidation LPN directly in the staging lane.

7. Locator Based Consolidation in Consolidation Locator Across Deliveries in Staging Lane
This consolidation method enables you to consolidate material for each delivery in a separate consolidation locator and then consolidate material for multiple deliveries in the same staging lane.

8. Locator Based Consolidation in Consolidation Locator Within Delivery in Staging Lane
This consolidation method enables you to consolidate material for a delivery in a consolidation locator and then move the material to a staging lane.

Consolidation Setup

When you perform a Pick Drop, Staging Move, or LPN Mass Consolidate for material consolidated across deliveries, the following conditions apply:
• All lines in the From and To LPN, if the material resides in an existing LPN, must be assigned to a delivery.
• The destination LPN must be in a locator of type Staging.
• The destination LPN must not have any loose material. If LPNs are nested, the nested LPNs can contain loose material.
• All tasks loaded into the From LPN and To LPN must have an operation plan with the consolidation method set to Across Deliveries.

Shipping Validation
Transportation Execution validates material consolidated across deliveries and determines if a valid deconsolidation point exists, and if the ship-from location are the same. After consolidation, and at ship confirm, Shipping Execution automatically
creates a trip for the second leg, from the deconsolidation point to the final ship-to destination as follows:

• If no trips associated to the deliveries exist for the second leg, Shipping Execution creates a trip for each delivery from the deconsolidation point to the final ship-to destination.
• If deliveries for the second leg exist, Shipping Execution deletes the delivery from the associated trip, and creates a new trip from the deconsolidation point to the final ship-to destination.

Consolidation Inquiry

Once material is consolidated, it is ready for further processing such as packing, shipping, or loading. It is essential that you know the status of consolidated material so you can make a decision on what material is eligible for further processing.

Consolidation Locators Inquiry
The Consolidation Locators Inquiry page serves as the gateway to view consolidation locators with material in various states so that you can make a determination on what material is ready for further processing.

Complete Locators
The Complete Locators mobile page enables you to view consolidation locators that have completely consolidated material.

Empty Locators
The Empty Locators mobile page enables you to view empty consolidation locators. It displays subinventory and locators that are empty, one locator at a time. The total number of empty locators displays at the bottom of the page.

Non-Empty Locators
The Non-Empty Locators mobile page enables you to view consolidation locators that have at least one staged LPN in it. It includes locators with either completely or partially consolidated material or both.
It displays subinventory and locators that have at least one LPN with a status of Staged. It shows all locators that have material in them regardless of whether material has been completely consolidated or not.

It also has a <Find LPNs> button that invokes the Consolidated LPNs page and displays LPNs that exist in the displayed locator.

Consolidated LPNs Inquiry
The Consolidated LPN Inquiry page serves as the gateway to view consolidated LPNs with deliveries in various states so that you can make a determination on what material is ready for further processing. The Consolidated LPN Inquiry can be performed against any staged LPN, delivery, or order number or any combination of the three.

Material Status Control

Material status control, which is one of the best feature of oracle WMS is now also available in Oracle inventory after release 12. It allows to control what type of transactions can be & cannot be done on onhand quantities. This feature provides similar controls to materials as item status provides to items.

Material Status control restricts the movement and usage of portions of on-hand inventory. Using material status control enables you to control whether you can pick or ship an internal order or sales order, or issue material for a work order. You can also specify whether material needs to be quarantined until you inspect it. In addition, you can determine whether products with a particular status can be reserved, included in available to promise calculations, or netted in production planning. You assign material statuses at four levels: subinventory, locator, lot, and serial.

You assign subinventory and locator statuses in the subinventory and locator windows. The location status applies to the material in the location and not the location itself.

you can choose which transaction types are available for material status control by enabling the check box in transaction type definition form



Material status control @ subinventory & locator



Material status control @ Lot & Serail
Material work bench window