Ebs 122 Cum RCD Log

ORACLE E-BUSINESS SUITE
RELEASE CONTENT DOCUMENT
Logistics
Releases 12.1 and 12.2
Prepared by Oracle E-Business Suite Product Development
Last Updated: April 9, 2015
Copyright 2011, 2015 Oracle Corporation

All Rights Reserved
Table of Contents
1. Disclaimer 1
2. Introduction 2
2.1. Purpose of Document 2
3. New and Changed Features in Logistics 3
3.1. Oracle Inventory Management 3
3.1.1. Overview 3
3.1.2. Release 12.1.1 3
3.1.2.1. On Hand Material Status 3
3.1.2.2. Extensibility Enhancements 3
3.1.2.3. Lot Genealogy Enhancements 3
3.1.2.4. Purchasing by Revision Enhancements 4
3.1.3. Release 12.1.2 4
3.1.3.1. Supply Chain Web Services for Items and Inventory 4
3.1.4. Release 12.2 4
3.1.4.1. Optional Lot Allocation 4
3.1.4.2. Serial Number Assignment Enhancements 4
3.1.4.3. Return to Vendor Enhancements 5
3.1.4.4. Global Lot Attributes 5
3.1.4.5. Cycle Counting Enhancements 5
3.1.4.6. Distributed Warehouse Management Integration 5
3.1.4.7. Deferred Electronic Record & Electronic Signature Capture 6
3.1.4.8. Public APIs for Unit of Measure 6
3.1.4.9. Receiving Open Interface Enhancement 6
3.1.4.10. Pay on Receipt for LCM Organizations 6
3.1.5. Release 12.2.3 6
3.1.5.1. Physical Inventory Integration Enhancements 6
3.1.6. Release 12.2.4 6
3.1.6.1. Automated Return to Consignment for WIP Component Returns 6
3.1.7. Release 12.2.5 7
3.1.7.1. Serial Tagging at Sales Order Pick 7
3.1.7.2. Consignment Returns after Consumption 7
3.1.7.3. Tablet Optimized Receiving Screens: Inbound Receipts & Exceptions 7
3.2. Oracle Inventory Management Extensions for Oracle Endeca 8
3.2.1. Overview 8
3.2.2. Release 12.1.3.4 8
3.2.3. Release V5 8
3.2.3.1. Plan Fulfillment 8
3.2.3.2. Track Fulfillment 8
3.2.3.3. Space Utilization 9
3.2.3.4. Enhancements to Item Information Discovery 9
3.2.3.5. General Features 9
3.3. Oracle Landed Cost Management 10
3.3.1. Overview 10
3.3.2. Release 12.1.1 10
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
3.3.2.1. Charge Management 10
3.3.2.2. Advanced Pricing for Charge Templates 11
3.3.2.3. Landed Cost Calculation 11
3.3.2.4. Product Cost Dashboard 11
3.3.2.5. Tax Recovery 11
3.3.2.6. Integration to EBS Supply Chain and Back office 12
3.3.2.7. Procurement Integration 12
3.3.2.8. Receiving Integration 12
3.3.2.9. Cost Management Integration 12
3.3.2.10. Accounts Payable Integration 13
3.3.3. Release 12.1.2 13
3.3.3.1. Oracle Landed Cost Management Support for Process Cost Management 13
3.3.3.2. Visibility into Matched Invoice Amounts 13
3.3.3.3. Landed Cost Calculation History 13
3.3.3.4. Landed Cost Visualization by PO 14
3.3.4. Release 12.1.3 14
3.3.4.1. Landed Cost Simulation for Purchase Orders 14
3.3.5. Release 12.1.3.4 15
3.3.5.1. Landed Cost Management Extensions for Oracle Endeca 15
3.3.6. Release 12.2 15
3.3.6.1. Update estimated landed cost (ELC) of Completed Shipments 15
3.3.6.2. Landed cost calculation for Selected Items 16
3.3.6.3. Manage Charges for LCM as a Service Flow 16
3.3.7. Release 12.2.4 16
3.3.7.1. Update Completed Shipments API 16
3.3.7.2. Update Simulations for Approved POs 16
3.3.7.3. Invoice Matching to Receipts in LCM Enabled Organizations 17
3.3.8. Release 12.2.5 17
3.3.8.1. Calculate Landed Costs for Returns and Corrections 17
3.3.8.2. Close Landed Cost Shipments 17
3.3.8.3. Flexibility on Actual Landed Cost Calculation for Charges 17
3.4. Oracle Mobile Supply Chain Applications 18
3.4.1. Overview 18
3.4.2. Release 12.1.1 18
3.4.2.1. Mobile User Interface Personalization 18
3.4.3. Release 12.2 18
3.4.3.1. Mobile User Interface Personalization Enhancements 18
3.4.3.2. Cycle Counting Enhancements for Lot Controlled Items 19
3.4.4. Release 12.2.3 19
3.4.5. Release 12.2.4 19
3.4.5.2. Mobile User Interface Enhancements 20
3.4.5.3. New mobile user interface for Oracle Yard Management 20
3.4.6. Release 12.2.5 20
3.4.6.1. Single Sign-On 20
3.5. Oracle Warehouse Management 21
3.5.1. Overview 21
3.5.2. Release 12.1.1 21
3.5.2.1. Forward Pick Replenishment 21
3.5.2.2. Mobile User Interface Personalization 21
3.5.2.4. Dock Scheduling and Load Sequencing 22
3.5.2.5. LPN Status 23
3.5.2.6. UCC-128 and Case Picking Enhancements 23
3.5.2.7. Over-Allocation Using WMS Rules 23
3.5.2.8. LPN Over Allocation during Pick Release 23
3.5.2.9. Directed Putaway of Reserved LPNs 24
3.5.2.10. Reusing LPNs 24
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
3.5.2.11. Cluster Pick by Label 24
3.5.2.12. Distributed WMS Deployment 24
3.5.2.13. Advanced Wave Planning 24
3.5.3. Release 12.1.2 25
3.5.3.1. Advanced Wave Planning Enhancements 25
3.5.3.2. Task Cancellation 26
3.5.3.3. High Volume Case Picking Support 26
3.5.4. Release 12.1.3 26
3.5.4.1. Opportunistic Cycle Count 26
3.5.4.2. Lot Substitution 27
3.5.4.3. Distributed WMS Integration with Oracle EBS 27
3.5.4.4. LSP Management and Activity Based Billing 27
3.5.5. Release 12.2 27
3.5.5.1. Advanced Catch-Weight 27
3.5.5.2. Additional Mobile User Interface Personalization Pages 28
3.5.5.3. Return to Vendor enhancements 29
3.5.5.4. Contingent Worker Support 29
3.5.5.5. Mobile Logout Warning 29
3.5.5.6. Distributed Warehouse Management Integration to EBS R12 29
3.5.5.7. Task Management Usability Enhancements 29
3.5.5.8. LPN Visibility in Receiving 30
3.5.5.9. LPN Split Transaction Enhancements 30
3.5.5.11. Warehouse Control Board and Material Workbench Enhancements 30
3.5.5.12. Packing Workbench Enhancements 31
3.5.6. Release 12.2.4 31
3.5.6.1. Multiple Cycle Count Task Types 31
3.5.6.2. Cycle Count Skip Task 31
3.5.6.3. Drop by Location 31
3.5.6.4. Configurable Picking Exception 31
3.5.6.5. Cycle Count Workflow for Change Locator/LPN Exception 31
3.5.7. Release 12.2.5 32
3.5.7.1. Mobile Task Dashboard 32
3.5.7.2. Nested LPN Pick 32
3.5.7.3. Picking by Zone 32
3.6. Oracle Warehouse Management Extensions for Oracle Endeca 33
3.6.1. Overview 33
3.6.2. Release 12.1.3.4 33
3.6.2.1. Plan Fulfillment 33
3.6.2.2. Track Fulfillment 33
3.6.2.3. Space Utilization 33
3.6.2.4. Labor Utilization 34
3.6.3. Release V5 34
3.6.3.1. Plan Fulfillment Enhancements 34
3.6.3.2. Space Utilization Enhancements 34
3.6.3.3. General Features 34
3.6.4. Release V6 34
3.6.4.1. Capacity Analysis 34
3.7. Oracle Yard Management 35
3.7.1. Overview 35
3.7.2. Release 12.2.4 35
3.7.2.1. Yard Definition 35
3.7.2.2. Equipment Definition 35
3.7.2.3. Dock Scheduling Workbench 35
3.7.2.4. Yard Transactions 35
3.7.2.5. Material Workbench 36
3.7.2.6. Yard Workbench 36
3.7.2.7. Integrations 36
3.8. Oracle Mobile Inventory for Oracle E-Business Suite 37
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
3.8.1. Overview 37
3.8.2. V 1.1.0 37
3.8.2.1. Mobile Foundation Updates 37
3.8.2.2. Accessibility Improvements 37
3.8.3. V 1.2.0 37
3.8.3.1. Android Support 37
3.8.3.2. Mobile Foundation Release 3.0 Updates 38
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
1. Disclaimer
This Release Content Document (RCD) describes product features that are proposed for
the specified releases of the Oracle E-Business Suite. This document describes new or
changed functionality only. Existing functionality from prior releases is not described. It
is intended solely to help you assess the business benefits of upgrading to the specified
release of the Oracle E-Business Suite.
This document in any form, software or printed matter, contains proprietary information
that is the exclusive property of Oracle. Your access to and use of this confidential
material is subject to the terms and conditions of your Oracle Software License and
Service Agreement, which has been executed and with which you agree to comply. This
document and information contained herein may not be disclosed, copied, reproduced or
distributed to anyone outside Oracle without prior written consent of Oracle. This
document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all
features described in this document without risking significant destabilization of the code.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 1
2. Introduction
2.1. Purpose of Document

This Release Content Document (RCD) communicates information about new or changed
functionality introduced in Oracle E-Business Suite Releases 12.1 and 12.2, and in
subsequent Release Update Packs (RUPs) and off-cycle patches. For your convenience,
it also includes new or changed functionality introduced in the RUPs for Release 12,
including 12.0.2 through 12.0.7.
The features and enhancements described in this document are grouped by product, and
then by the release in which they first became available, for example, Release 12.1.1.
Features released in an off-cycle patch have a special designation for example, a feature
released after 12.1.1, but before 12.1.2, is designated as Release 12.1.1+.
3. New and Changed Features in Logistics
3.1. Oracle Inventory Management
3.1.1. Overview
With Oracle Inventory Management you can improve inventory visibility, reduce
inventory levels and control inventory operations. All of your material in each line of
business and stage of the inventory lifecycle can be tracked in a single system. Increased
transparency will reduce the need for local buffer stocks, and inventory will be located
where it previously wasn't known to exist.
Oracle Inventory Management is part of the Oracle Logistics solution and integrates
seamlessly with other Supply Chain Management applications, including Oracle
Warehouse Management, Oracle Order Management, Procurement, Discrete and Process
Manufacturing, and Oracle Financials.
3.1.2. Release 12.1.1
3.1.2.1. On Hand Material Status

Even in the most efficient manufacturing and distribution networks, quality issues may
arise. Packages may arrive damaged from transportation; defects may be detected in
manufacturing long after the product has left the production center; or quality issues may
affect only a portion of a manufacturing batch. With this feature, the material status
model leveraged in Oracle Warehouse Management has been extended to provide
material status at the on hand balance level.
This On Hand Material Status will enable warehouse users to:
Separate the physical movement of material and changes to the material status
into different responsibilities, which will prevent the accidental change of
material status when material is moved.
Put part of a lot that exists in a certain location on hold without having to place
the entire lot on hold.
This also enables holds to be placed on non lot or serial controlled items without
moving that material to a quarantine location.
3.1.2.2. Extensibility Enhancements

Users often require the ability to programmatically alter the details of an allocation record
in Oracle Inventory. This may include manipulating the transaction based on logic
derived from a third party materials management application or a custom user interface
used to drive picking. To better support these requirements, Oracle Inventory now offers
a public API to manipulate records allocations prior to committing a pick confirm
transaction.
3.1.2.3. Lot Genealogy Enhancements

Enhancements have been incorporated into the Lot Genealogy form to allow the user to:
Highlight a particular item lot on the genealogy tree and toggle between the
Where Used and Source tabs using the highlighted item lot as the top level node
in the tree structure. This allows the user to refresh the tree with a different top
level node without being forced to go back to the query window.
View more levels of detail in the left-side navigator window where lot branches
are expanded before they are forced to scroll horizontally.
3.1.2.4. Purchasing by Revision Enhancements

The profile option INV: Purchasing by Revision controls whether an item revision will
be specified on purchase requisitions generated by Min-Max Planning. Purchasing by
Revision has been enhanced to be used for non-revision controlled items, as well as
revision controlled items. Item revisions may be defined and used when purchasing
material, although the item may not be revision-controlled in inventory. The latest
revision will be defaulted onto the purchase requisition.
3.1.3. Release 12.1.2
3.1.3.1. Supply Chain Web Services for Items and Inventory

As part of this enhancement, web services are provided by exposing business logic
contained within Oracle forms through Java APIs. These web services are cataloged in
the Oracle Integration Repository and can be browsed though Oracle Integration
Repository Browser Interface under respective product family node. By Clicking on the
Business Entity in Integration repository, you can view full description, list of web
services for that business entity along with the description of the web service, whereas
description of parameters can be seen from the xsd definition of the service available via
the generated wsdl.
Following web service is provided for Item:

1) Item: Create Item, Query Item Details, Update Item Details
Following web services are provided for Inventory:

1) Lot Number: Create Lot Number, Query Lot Number, Update Lot Number
2) Reservation: Create Reservation, Delete Reservation, Query Reservation, Update
Reservation
3) Serial Number: Create Serial Number, Query Serial Number, Update Serial Number
3.1.4. Release 12.2
3.1.4.1. Optional Lot Allocation

In warehouses where lot-controlled material is stacked in picking locations, the actual lot
number picked may depend on how accessible it is in the picking area. If the system
were to automatically allocate a specific lot, it may not be the lot which the picker can
retrieve. In such cases, it is optimal for the system to allocate quantities based on
availability as opposed to allocating specific lots. Then the user will confirm the lot at
pick confirmation or while picking the task in case of WMS organization.
Users can turn this feature on and off at the Inventory Organization level. An API is
provided to enable/disable this feature at the item, subinventory and locator levels.
Optional Lot Allocation is also available for Warehouse Management organizations.
Optional Lot Allocation is not supported for OPM Inventory Organizations.
3.1.4.2. Serial Number Assignment Enhancements

In addition to the ability to defer serial number instantiation until ship confirmation (sales
order issue), Release 12.2 of Oracle Inventory now provides the ability to receive and
transfer inventory without assigning a serial number and defer the serial number
assignment to later in the materials management process at the following issue
transactions:
WIP Component Issue and WIP Component Receipt
Field Service Issue and Field Service Recovery
Return To Vendor
These serial numbers are tracked in the serial genealogy.
The above functionality works in conjunction with Serial Number Control At Sales
Order Issue and No (serial) Control. However, if the user chooses Serial Number
Control At Receipt for an item, serial numbers must be tracked for all material receipts
for that item.
3.1.4.3. Return to Vendor Enhancements

In this release, the Return to Vendor process has been enhanced to manage the fulfillment
process of any outbound shipments associated with the return and to offer greater
flexibility in the determination of which facility can ship the returned goods. In the latest
release of Oracle Receiving, users can now track the entire shipment cycle of returns.
The major features include:
1. Create Return Request in Oracle Receiving and track the corresponding
shipment in Oracle Shipping Execution.
2. Print documents and perform export compliance check for the material being
returned to vendor.
3. Return material using return request without requiring a purchase order.
4. Return material from any warehouse independent of the Inventory Organization
in which it was initially received.
3.1.4.4. Global Lot Attributes

In the course of regular manufacturing and distribution processes, a single lot sourced
from one production batch might find itself located in multiple facilities. To better
maintain attributes of lots as material travels across organizations, a new profile has been
introduced that will allow the lot to retain its attributes as it traverses through the supply
chain. This feature also provides a new concurrent request which will sync up global lot
attributes across organizations.
3.1.4.5. Cycle Counting Enhancements

Warehouses conduct cycle counts to reconcile the system on-hand quantity with the
actual on-hand quantity. Items are prioritized using ABC Classification to count more
important (A) items more frequently than less important (C) items. The following
enhancements have been made to the cycle counting process:
Unit Cost in ABC Compile criteria In addition to existing criteria, ABC
Compile can now be created using a new compile criterion of Item Unit Cost.
Using this criterion ranks the items based on the item unit cost.
Public API for ABC Assignment A new public API supports creating and
updating ABC assignments. This will be useful during initial implementation
when converting from another system. It will also be useful for automating the
process when new items are defined which also need to be added to the ABC
Assignment to be included in future cycle counts.
3.1.4.6. Distributed Warehouse Management Integration

As the number of customers on E-Business Suite Release 12 grows, so too has the
demand to provide integrations between EBS Release 12 and Oracle Warehouse
Management (WMS) for those customers who choose to implement their WMS on a
separate instance. To better support this deployment methodology, the distributed WMS
Integration with Oracle EBS provides a starter kit for integration between a distributed
WMS instance and an EBS 11.5.10, 12.1 or 12.2 instance.
3.1.4.7. Deferred Electronic Record & Electronic Signature Capture

In order to better support businesses with tight procedural controls around product
quality, Oracle Inventory Management now supports the ability to defer a material status
change until the electronic record and signature which approves the status change has
been recorded. Based on a profile option, the system can now either allow the new status
to go into effect immediately or it can be deferred until all signatures and approvals have
been captured in the Oracle Electronic Records and Electronic Signatures (ERES)
system. If the deferral option is chosen, the restrictions (the disallowed transactions) of
both the current and the pending status will be honored.
3.1.4.8. Public APIs for Unit of Measure

Public APIs are now available to create and update data related to Unit of Measure
(UOM). This includes the following:
Create/update UOM Class
Create/update Unit of Measure
Create/update UOM Conversions such as Inter Class, Intra Class, Lot Specific
Conversions
This will be useful for importing data from legacy systems during implementations and
for mass updates of UOM Conversions.
3.1.4.9. Receiving Open Interface Enhancement

The Transaction Status Summary form now allows the user to query, resubmit/delete
Receiving Open Interface transactions without using a script to update underlying tables.
A form function has been introduced to control access to delete Pending or Running
ROI transactions.
3.1.4.10. Pay on Receipt for LCM Organizations

Self-billing suppliers upon receipt is not supported in LCM Inventory Organizations.
The Pay on Receipt program has been enhanced to populate the AP interface tables and
generate the invoices or debit memos (for return transactions) for the interfaced data.
3.1.5. Release 12.2.3
3.1.5.1. Physical Inventory Integration Enhancements

Some businesses with a high volume of physical inventory transactions need the ability to
update physical inventory records from an external system. For this requirement, Oracle
Inventory Management provides a public Physical Inventory API for updating existing
physical tag records and their corresponding adjustment records.
3.1.6. Release 12.2.4
3.1.6.1. Automated Return to Consignment for WIP Component Returns

Many companies inspect only a portion of the material that their suppliers ship them. For
this reason, defective components which have been consigned from suppliers may not be
identified until that material has been issued into production. With this enhancement,
using WIP component return to move material back into inventory will automatically
return it to a consigned status and automatically perform the required financial
accounting.
An API is also available to allow users to add custom logic to control the auto consigned
return process.
3.1.7. Release 12.2.5
3.1.7.1. Serial Tagging at Sales Order Pick
The ability to defer serial number assignments to specific transactions in the materials
management process has been enhanced. You can now assign serial numbers during pick
confirmation for sales orders and internal orders.
This feature works in conjunction with Serial Number Control At Sales Order Issue and
No (serial) Control. With this feature, users can enable serial tagging for sales order
pick, internal order pick or both. This allows for serial capture at picking and expedites the
downstream shipment process by reducing the burden on the shipping operator. Serial
tagging at sales order picking is supported in WMS as well as OPM enabled organizations.
3.1.7.2. Consignment Returns after Consumption
Sometimes there can be a need to return the material back to consigned inventory even
after it has been consumed and a consumption advice or an invoice is generated for it.
This enhancement provides the user the flexibility to return the consumed material to
consigned inventory at any point and automatically performs the required financial
accounting. A new form function parameter CONS_INV_RTN_DAYS determines how
far in the past consumed material may be returned. A corresponding debit memo can be
generated automatically if the Auto Create Debit Memo for RTS parameter is enabled in
the Supplier Site set up.
3.1.7.3. Tablet Optimized Receiving Screens: Inbound Receipts & Exceptions

With Tablet Optimized Receiving screens, warehouse supervisors can manage inbound
receipts against purchase orders, requisitions, advanced shipment notices (ASNs) etc.
Warehouse supervisors can identify exceptions and take quick receiving actions on the go.
Quickly receive materials while verifying quantities
View the buyer/initiator to confirm who ordered the material
Putaway and deliver receipts to appropriate subinventories/locators
View all overdue expected receipts and manage receipt exceptions
3.2. Oracle Inventory Management Extensions for Oracle Endeca
3.2.1. Overview
Imagine always being able to focus on the right priorities at the right time. Oracle
Inventory Management Extensions for Oracle Endeca brings order to the chaotic flow of
data we deal with on a daily basis. Endeca turns raw data into accessible, usable
information for discovery; information that is the basis for action. Oracle Inventory
Management Extensions for Oracle Endeca enable users to navigate directly to actionable
user interfaces, providing a fast, easy means for taking action. Whether sitting at a desk
or on-the-go, native application support for mobile tablets means that access to Oracle
Inventory Management is only a touch away.
3.2.2. Release 12.1.3.4
Oracle Inventory Management Extensions for Oracle Endeca empowers manufacturing
and logistics managers, supply chain analysts and business users with the ability to find
parts suppliers and alternates for effective sourcing decisions, compare product
specifications, and instantly detect duplicate parts and product catalog discrepancies
Key features include:
Search Assistance: As End Users type in Search Box, the list of matching
values in key attributes like Item Number, Catalog Group, Item Description and
Long Description are displayed
Complete view of Item and related business entity: Access to 360o view of
Item and related business entities without the need to navigate to multiple screens
and manually stitch/correlate related information. Oracle Cost Management
Extensions for Oracle Endeca allows users to discover transactions and related
accounting information in real time thereby providing opportunity to effectively
manage the period close process, reconcile accounting as well as ensure accuracy
of accounting across sub ledgers.
Product Comparisons: End User can quickly add Item records across different
organizations for side by side attribute comparison, eliminating the need to
export data to excel to perform such analysis
Integration: Fully integrated with Oracle E-Business Suite
3.2.3. Release V5
3.2.3.1. Plan Fulfillment

With Plan Fulfillment, an inventory manager can plan daily outbound work. Visibility to
daily work as well as overdue work provides a full picture of demand. All in one place,
demand can be compared to current inventory information. Overall scarce inventory or
stock outs are highlighted. Additional attention can be made to high value orders with
stock issues.
3.2.3.2. Track Fulfillment

The Track Fulfillment work area allows an inventory manager to quickly identify
customer orders that are being fulfilled. Full visibility to fulfillment status (picked, picked
with exception, staged) helps track the fulfillment of customer orders in the warehouse.
Users have the ability to manage delivery exceptions, holds and interface activity which
could delay the fulfillment and revenue recognition process.
3.2.3.3. Space Utilization
The Space Utilization work area visually identifies problem areas in the warehouse in
terms of material storage. Poorly slotted material, fragmented items, and fragmented
locators are highlighted. A new feature to highlight fragmentation based on velocity has
been introduced as a part of this release. The user can initiate a movement request to
consolidate fragmented material, improve the slotting of material or update item/locator
status to manage quarantine/recalls, all from this work area.
3.2.3.4. Enhancements to Item Information Discovery

Range filters have been enabled for all numeric attributes in guided navigation.
Carousel viewing option is available for Items result list region.
Item Cost is now available for incremental refresh but only for Discrete inventory
organizations and not Process organizations.
Navigate from Endeca Discrete Work Order Search to Item Information
Discovery page via deep linking.
Access Item Master form via Update Item link.
3.2.3.5. General Features

All tabs can be configured to upload data for specific organizations and/or subinventories
by setting the following lookups:
Organization Control for INV Endeca Extensions
Subinventory Control for INV Endeca Extensions
The default value for the lookups is ALL, which implies all Inventory organizations
and/or subinventories are uploaded by default. Users may choose to restrict the upload to
specific organizations and/or subinventories, in order to limit the amount of data in each
periodic refresh.
Users can invoke the shipping transaction form directly from delivery link with delivery
information defaulted.
Users can reference flexfields to filter data based on specific attributes.
3.3. Oracle Landed Cost Management
In an effort to meet revenue targets and profitability expectations, companies often look
to international trade to maximize their customer reach, gain competitive advantage, and
reduce costs. However, international trade introduces new coordination and management
complexities as well as costs. Understanding and attributing how much money an
enterprise is currently earning by product becomes very difficult. This is due in large part
to the fact that financial processes do not often mirror complicated physical supply flows.
Companies are looking for ways to bridge these two realities and accurately map product
movement and costs to financial accounting. They need the confidence to know that cost
and inventory valuations are correct. This is important not just for regulatory compliance
but also for strategic decision making. Knowledge and visibility into these trade costs
would help organizations better evaluate new product plans, price their products, and
negotiate contracts with both suppliers and customers.
Additionally, some industries and regions require that product specific landed costs be
tracked and included on documentation even for domestic trade. These are often driven
by a federal wide mandate in the case of countries like Brazil and India. However, they
can also be driven by industries like process manufacturing where it is difficult to track
the individual acquisition components against the resulting products that get stored and
sold further downstream.
A landed cost management solution itemizes all the merchandise and non-merchandise
related costs associated with an organizations supply chain. It apportions these costs
back to the individual merchandise item providing traceability throughout the items
lifecycle. The result is overall visibility that drives strategic decisions around sourcing,
product pricing, contract negotiation, and product planning initiatives. It also provides
the evidence and data to support accurate fiscal reporting and compliant trade
documentation.
3.3.1. Overview
Oracle Landed Cost Management is a new product that was introduced in EBS R12.1.1.
It captures extended supply chain costs (freight, insurance, duties, taxes, etc.) and
attributes them back to product(s), which incurred them. As a result, costs tracked in
Oracle Cost Management are no longer based on purchase order item costs but are
instead based on total landed cost. This means that decisions made from system cost
valuations and the related financial reports and statements are more effective and based
on real product costs. This can equate to increased product profitability through better
pricing models, sourcing decisions, and contract negotiations.
3.3.2. Release 12.1.1
3.3.2.1. Charge Management

Many of the charges that apply to landed costs can be complicated in their application,
maintenance, and ongoing tracking. These charges are received in a variety of formats at
different points during a fulfillment process. These points include product creation,
sourcing, order creation, shipping, receiving, and invoicing. Organizing and tracking
these charges as soon as they are incurred is key to a company fully understanding their
outstanding liabilities.
Oracle Landed Cost Management collects an unlimited number of estimated charges and
allows users to configure how charges should be applied to a shipment line, a group of
lines within a shipment, or an entire shipment. It applies these charges based on weight,
volume, quantity, or the value of the items being traded. These charges can be
categorized by different cost factors which will ultimately govern the behavior in how
they are included in a total landed cost calculation. Once actual amounts are received,
Charge Management records the new value for comparison with the earlier estimates and
sends adjustments to back office applications.
3.3.2.2. Advanced Pricing for Charge Templates

When organizations try to obtain estimates for a particular charge, they can typically
identify standard business rules for when these charges should apply. Oracles Landed
Cost Management application allows users to enter lists of estimated charges and
conditions as to when these charges should apply by using Advanced Pricing. This
enables a template of charges to automatically be applied to a receipt. It removes the
need for a charge reference spreadsheet or document often found in organizations dealing
with complex supply chains and minimizes error prone steps of manually entering
charges during a transaction. Once these estimated costs are applied by Advanced
Pricing, users have the ability to verify and update them via Oracle Landed Cost
Managements Charge Management functionality. Ultimately, Oracle Landed Cost
Management uses these components to calculate the estimated landed cost.
3.3.2.3. Landed Cost Calculation

Most organizations struggle to find the real costs required to take a product to market,
to source a product overseas, or to do business with a particular vendor or customer.
Knowing the total actual landed cost of goods provides powerful insight in todays
competitive global markets. When companies use this landed cost information
strategically, they can control overall product margin and optimize profitability. Some
companies can only estimate this landed cost at best, while others can calculate estimated
or actual costs. Often times, this is done in a semi-automated fashion in different places,
making it difficult to compare estimates with actuals.
The Oracle Landed Cost Management engine provides the ability to calculate the
estimated landed cost based on charges manually assigned and automatically allocated
based on the configuration in the charge management repository. It recalculates
applicable taxes and can be configured to exclude recoverable tax amounts. It also
calculates the actual landed costs by prorating the actual invoices and proportional taxes
to obtain the variances between what was estimated and what was charged. Cost
components summed in the calculation remain stored at the most granular level for
detailed tracking of charge amounts while variances are updated to the appropriate
accounts.
3.3.2.4. Product Cost Dashboard

Financial flows do not mirror physical supply chain transactional flows. Landed cost
management helps to link these two flows together and provides visibility and traceability
from one to the other. With Landed Cost Managements dashboard pages, companies
can see the real time accrual updates for a particular receipt or shipment. They can
validate the accuracy of a suppliers estimate by comparing estimated and actual costs
and can see the percentage of a particular cost component for a particular item.
Additionally, users can make use of all the flexible Oracle and E-Business Suite tools in
order to meet their own customized reporting requirements.
3.3.2.5. Tax Recovery

Many countries impose high tariffs on items as they pass through the supply chain. This
can sometimes reach into the double digits. As a result, tax recoverability becomes
extremely important when organizations are making sourcing decisions and automating
inbound flows. Oracle Landed Cost Management factors in tax recoverable amounts in
the landed cost calculation, so that estimated and actual landed cost calculations do not
overstate the true tax costs.
3.3.2.6. Integration to EBS Supply Chain and Back office

Almost all organizations struggle to provide their back office systems visibility into
estimates of accrued liabilities that are then updated with actual amounts when they
become known. This is particularly the case when organizations have a large portion of
their trade done across borders or have a complex supply chain. Oracles Landed Cost
Management is integrated with Oracle E-Business Suites financial and supply chain
applications to provide this visibility and make implementation straightforward. Oracle
Landed Cost Management provides the estimated landed cost to E-Business Suite
Inventory Receiving which then automatically forwards it on to E-Business Suite Cost
Management module. Once actual costs are obtained and shared with Accounts Payable,
variances are effectively communicated to E-Business Suite Cost Management module.
3.3.2.7. Procurement Integration

Procurement Information is often the baseline information used to itemize expected
shipment or receiving lines on which extended supply chain charges will be applied.
Landed Cost Management provides visibility into E-Business Suite Procurement data in
order to build expected shipments for charge application and subsequent landed cost
estimation calculations. When manually entering expected shipments the reference
information provided by Procurement saves time and decreases errors that might occur
without automated access to this information. Once available in Landed Cost
Management, expected values received from procurement such as quantity and price can
be edited for estimated cost calculation purposes. Furthermore, all the necessary data is
provided to help arrive at an accurate three way match once an invoice for a PO line or
charge is entered into Accounts Payable.
3.3.2.8. Receiving Integration

It is difficult to gain insight into charges associated with the acquisition of items through
an extended supply chain. Often, organizations are not aware of them until an invoice is
received. Companies need better visibility into these charges. Additionally, many regions
require that all expenses be accounted for at an item/product level upon receipt. In order
to comply with these requirements and provide an accurate calculation of product related
expenses, these extended costs need to be estimated and applied to an item at the time of
receipt.
Oracles Landed Cost Managements integration with EBS Inventorys Receiving
module enables Receiving to view LCMs estimated shipments and receive against them.
It further calls LCM for a total cost estimation calculation for all receipts whether they
originate in LCM or in Receiving itself. These estimations are then forwarded to E-
Business Suite Cost Management module in order to update inventory valuations and
accounting.
3.3.2.9. Cost Management Integration

When organizations are able to estimate landed costs, they often do not communicate
those estimates to their back office system. This is because they lack an automated
method to update these estimates with actual values once they are received. This
prevents them from fully utilizing the estimated information in their reporting and
decision making processes.
After actual values are received and the true landed cost is calculated in Landed Cost
Management, any variances between the actual and the estimate are determined. Those
variances are updated to E-Business Suite Cost Management module which in turn
updates the proper accounts and valuation.
3.3.2.10. Accounts Payable Integration

Few Accounts Payable applications provide a mechanism to apply and match an
unlimited number of charges to a particular procured item line or group of lines. This
means that accurate actual landed cost calculations might be difficult to automatically
calculate. Additionally, this prevents tying an actual charge back to any record of an
earlier estimated landed cost calculation.
Oracle Accounts Payable allows for unlimited numbers of charges to be entered and
applied to procured line items and allows line items to be applied and associate to
recovered line items. This information is forwarded to Landed Cost Management which
in turn calculates the Actual Landed Cost. These values are compared with earlier
estimates to determine if a variance should be communicated to Costing and ultimately to
the General Ledger.
3.3.3. Release 12.1.2
3.3.3.1. Oracle Landed Cost Management Support for Process Cost Management
In a global environment, extended supply chain and logistical costs can account for as
much as 30, 40 or 50% of the overall cost to obtain an item. Process industries are
particularly sensitive to these additional costs especially when the goods being acquired
are commodities with narrower margins. Oracle Landed Cost Management is being
enhanced to support Oracle Process Manufacturing. Most of the enhancements are
designed to allow Oracle Process Manufacturing Cost Management to consume the
landed cost calculations and adjustments. Please see the 12.1.2 Release Content
Document for Manufacturing for more information on the bulk of the enhancements
made to Oracle Process Manufacturing Cost Management to support this flow.
3.3.3.2. Visibility into Matched Invoice Amounts

Comparing a total landed cost calculation against the portion of the cost that has been
invoiced gives companies visibility into the finality of the actual landed cost calculation.
It also helps them understand how complete the billing is for a particular receipt
including all of the applicable charges.
The Shipment Hierarchy screens Allocations view has been enhanced with a third
calculation column, Matched in addition to the estimated and actual amounts. This
column includes the portion of the actual landed cost that has been billed or invoiced.
Users can drill down to review the itemized matched or billed transactions to help resolve
issues, tracing back a landed cost calculation to the related invoices.
3.3.3.3.Landed Cost Calculation History

Organizations that make decisions from landed cost data often monitor landed cost
calculations for any unexpected inconsistencies between estimated and actual
calculations. If an inconsistency exists, they require the ability to drill into the root cause
of the calculation and related transactions. Insight into this is useful in many regards but
is particularly helpful in refining estimated charge calculations or troubleshooting errors.
The Landed Cost Details page has been enhanced with a calculation history diagram.
Peaks in actual calculations not in line with estimates identify areas of interest that might
warrant further investigation. Users can then choose to review the details for that
particular landed cost calculation for more information
3.3.3.4. Landed Cost Visualization by PO
In purchasing organizations where material is coming from overseas or cross borders,
extended costs are a big portion of the overall acquisition cost. In these instances, it is
often helpful for procurement professionals to see the estimated landed cost of a PO
before submitting it.
With 12.1.2, Oracle Landed Cost Management will update the current Display
Acquisition Cost page in Oracle Purchasing to display landed cost information by
Purchase Order.
3.3.4. Release 12.1.3
3.3.4.1. Landed Cost Simulation for Purchase Orders

Landed cost is the cost to land the good on the ultimate (final) location. It could be also
the cost that a buyer has incurred in purchasing a product (good or service). Landed Cost
is calculated in order to accurately measure the corporations cost calculation and item
profitability. Knowing the real landed cost is important in actual costing, evaluating on-
hand inventory, as well as setting sales prices and revenue forecasting.
This feature allows a buyer to simulate the landed costs at creation time of purchase
orders, allowing better sourcing decisions based on the true landed cost of the items. The
buyer can also review the landed cost information simulations by editing the charges
automatically calculated or create and delete new ones.
3.3.5. Release 12.1.3.4
3.3.5.1. Landed Cost Management Extensions for Oracle Endeca

The Landed Cost Management Extensions for Oracle Endeca are part of the Oracle Cost
Management Extensions for Oracle Endeca product. It allows users to analyze the
landed cost information for enhanced supply and product margin management through
two new pages: Monitor Daily Operations and Landed Cost Analysis.
Monitor Daily Operations provides easy identification of shipments that need
attention from users such as the ones to be corrected or require an additional step
to complete the landed cost shipment lifecycle.
Landed Cost Analysis provides an in-depth understanding of the landed costs to
assist in managing and lowering the total inventory costs and to help take better
sourcing decisions.
3.3.6. Release 12.2
3.3.6.1. Update estimated landed cost (ELC) of Completed Shipments

Landed Cost Management application introduces the capability to update the estimated
landed cost of completed shipments. LCM provides the ability to adjust estimate landed
cost after the shipment is received into Inventory, but the invoice has not been matched to
the receipt.
This functionality provides the required flexibility to update the completed LCM
shipments with the latest pricing information provided by item supplier and charge
providers to reflect the changes to the business scenario such as change of freight
provider, shipping methods, etc. This feature is limited to Discrete Inventory
Organizations only.
3.3.6.2. Landed cost calculation for Selected Items

The landed cost calculation is set at purchase order approval time for the supported
purchase documents. In previous releases, all supported lines shipped to LCM-enabled
organizations were set for landed cost calculation. Now, the users have the ability to
define a set of items to be eligible for landed cost calculation, by setting a category set.
This functionality will allow companies to define the landed cost calculation and tracking
for selected items that have most impact from extended supply chain charges, such as
transportation and duty fees.
3.3.6.3. Manage Charges for LCM as a Service Flow

LCM as a Service flow is an implementation option in which the landed cost shipments
are automatically created when the receipts are entered in the Receiving application.
During the landed cost shipment creation, the charges are automatically defaulted by
Advanced Pricing engine and prorated into the shipment lines landed cost.
Through this new feature, the users will be able to review and update the defaulted
charges lines during the landed cost shipment creation. It will be possible for users to
selectively define rules that govern which shipments can complete automatically and
which shipments require manual intervention (to review and/or update the charges and
complete the shipment manually).
3.3.7. Release 12.2.4
3.3.7.1. Update Completed Shipments API

Users can update the estimated landed cost components (e.g.: item prices and charge
amounts) by using a public API. Update ELC API provides the following functionality:
Allow mass updates to the item prices of shipment lines of completed shipments
Allow mass updates to the charge amounts of existent charge lines from
completed shipments
Allow mass creation of charge lines of completed shipments
The following should be observed when processing item price updates:
Updates are allowed only for lines of completed shipments that have not yet been
matched.
New item price is required and must be compliant with the PO price tolerances.
3.3.7.2. Update Simulations for Approved POs

Oracle Landed Cost Management now enables the users to modify the landed cost
simulations of approved purchase orders. The LC simulation workbench has been
modified to:
Allow users to create new simulations for approved POs
Allow users to copy existent simulation into new ones for approved POs
The ability to update simulations of approved purchase orders allows keeping the
simulation data in sync with the latest pricing information and delivers improved
flexibility required by companies that use the simulations as a defaulting mechanism for
the landed cost charges generation.
The landed costs from firmed simulations are used to derive the charges when the
estimated landed cost is calculated.
3.3.7.3. Invoice Matching to Receipts in LCM Enabled Organizations

The charge invoice matching to LCM-enabled receipts presents new features:
Multi currency support for the charge invoices matched to LCM enabled receipts.
LCM users can match charge invoices such as domestic freight in local
currencies even if the purchase order is in another currency.
Ability to search receipt lines to be matched to an Invoice using additional
attributes such as LCM shipment number, cost factor, and charge party.
View landed cost information in charge invoice matching screen
Easy navigation from invoice matching screen to LC details of the receipt lines
that can be matched to the invoice.
3.3.8. Release 12.2.5
3.3.8.1. Calculate Landed Costs for Returns and Corrections

Oracle Laded Cost Management now recalculates the landed cost of the items whenever
the receipt quantity is changed by either a receiving correction or a return to supplier.
The concepts of refundable and non-refundable cost factors have been introduced when
the landed costs are being recalculated after the returns and corrections and are defined in
the Cost Factors setup page.
The refundable charge amounts are excluded from the unit landed cost proportionally to
the corrected / retuned quantity.
The non-refundable charge amounts keep constant during the landed cost calculation.
When the adjusted receipt quantity is smaller after the correction or return, the result is a
higher unit landed cost, as the same charge amount is prorated into less quantity.
3.3.8.2. Close Landed Cost Shipments

The Landed Cost Management users have now the option to mass-update landed cost
shipments and close the shipment lines for update and matching.
Closed shipment lines, according to an option setup, may not be visibly during the
charges invoice matching in Oracle Payables.
3.3.8.3. Flexibility on Actual Landed Cost Calculation for Charges

It has been provided extended flexibility to control how the actual landed cost calculation
considers the invoice change amounts that have been automatically allocated during the
invoice matching.
3.4. Oracle Mobile Supply Chain Applications
3.4.1. Overview
Oracle Mobile Supply Chain Applications enables users to perform many common
warehouse and shop floor transactions through hand-held radio frequency devices,
personal digital assistants and truck-mounted radio frequency scanners. Transactions can
be carried out on these wireless devices at the point of use, offering real time transaction
processing, improved data accuracy and increased mobility and convenience.
3.4.2. Release 12.1.1
3.4.2.1. Mobile User Interface Personalization

A major benefit of Oracle Mobile Supply Chain Applications (MSCA) mobile data entry
capability is the ability to record a material movement at the point of usage. Data entry at
the point of usage enhances inventory accuracy and records real time information. Mobile
personalization goes one step further by providing the user with the flexibility to record
data that is most relevant for the transaction without compromising the accuracy of
transaction. In addition, mobile personalization can record additional use defined data in
flex fields for specific transactions. Using this feature a warehouse can immediately
realize the following benefits:
Improve transaction execution speed by hiding or defaulting fields on a mobile
transaction form
Improve transaction accuracy by defaulting a value in field using a user defined
logic
Allow recording of additional data on a mobile transaction form using flex fields
All the above changes to a mobile transaction form can be made using a user friendly
configuration screen without resorting to code changes that are expensive to complete
and difficult to maintain. In this release, personalization is available for mobile receipt
transactions in MSCA.
3.4.3. Release 12.2
3.4.3.1. Mobile User Interface Personalization Enhancements

transaction. In addition, mobile personalization can record additional user defined data in
transaction form
logic
and difficult to maintain. In this release, personalization is available for the following
MSCA mobile pages:
Detail Pick
Cycle Count
Physical Count
Item Inquiry
Lot Attributes
Account Alias Receipt
Account Alias Issue
3.4.3.2. Cycle Counting Enhancements for Lot Controlled Items

Cycle count of lot controlled items on the mobile user interface enforces the user to enter
the total quantity first before the individual lot and their quantities can be entered into the
system. Flexibility is now provided to allow the warehouse operator to directly enter the
lot numbers and their quantities without having to enter the total item quantity first if
multiple lots are cycle counted in a location. This can be enabled using a new form
function parameter.
3.4.4. Release 12.2.3

transaction. In addition, mobile personalization can record additional user defined data in
transaction form
logic
and difficult to maintain. In this release, personalization is available for the following
MSCA mobile pages:
Subinventory Transfer
Inventory Organization Transfer
Move Order Replenishment
Kanban Replenishment
3.4.5. Release 12.2.4

In this release, personalization has been updated or made available for the following
MSCA mobile pages:
Ship Confirm
Quick Ship
Load Truck
3.4.5.2. Mobile User Interface Enhancements
With the release of a new product - Oracle Yard Management, the following existing
MSCA mobile pages have been enhanced:
Receipt
Quick Ship
LPN Ship
Load/Unload Truck
Inventory Ship Confirm
3.4.5.3. New mobile user interface for Oracle Yard Management

With the release of a new product - Oracle Yard Management, the following new MSCA
mobile pages have been introduced:
Seal Equipment
Unseal Equipment
Equipment Update
Yard Move
3.4.6. Release 12.2.5
3.4.6.1. Single Sign-On
Users can now login MWA (Mobile Supply Chain Applications Server) using Single Sign
On (SSO) credentials that are authenticated by OID (Oracle Internet Directory).
3.5. Oracle Warehouse Management
3.5.1. Overview
Oracle Warehouse Management (WMS) automates and optimizes material handling
processes to reduce labor costs, improve facility utilization, increase order accuracy and
provide innovative services to customers. Oracle Warehouse Management supports
inbound, outbound, and reverse logistics, finished, raw and work in process materials,
manufacturing and distribution environments and advanced value-added services such as
kitting and cross docking.
Oracle Warehouse Management is part of the Oracle Value Chain Execution solution and
integrates seamlessly with other Value Chain Execution products, including Oracle Order
Management, and Oracle Transportation Management.
3.5.2. Release 12.1.1
3.5.2.1. Forward Pick Replenishment

Forward pick area replenishment is an important activity in a warehouse. By replenishing
a forward pick area, a distribution center disaggregates material stored in reserve or bulk
area and moves it into a pick area that is optimized for unit picking. In this release the
following replenishment features are available for use:
Pull Replenishment: This type of replenishment is useful for items with high
uniform demand in forward pick area. A replenishment suggestion will be auto-
created as soon as a shortfall is detected during order release process.
Push Replenishment: This type of replenishment is useful for items with irregular
demand in forward pick area. Using push replenishment, the aggregated future
demand for an item is replenished to a forward pick area for future order picking
activity.
Dynamic Execution: The dynamic replenishment execution feature orchestrates
the warehouse tasks in such a way that a pick task to a forward pick area will be
dispatched only when replenishment has been completed. Similarly a
replenishment task will be dispatched only when a forward pick area has enough
capacity to receive the replenished material.
These features provide tremendous productivity benefits to a warehouse engaged in
distribution activity. Replenishment to forward pick area will allow distribution center to
reap the benefits of bulk procurement and optimized storage in a reserve area as well as
optimized picking for order profiles with smaller quantities.
3.5.2.2. Mobile User Interface Personalization

A major benefit of Warehouse Managements mobile data entry capability is the ability
to record a material movement at the point of usage. Data entry at the point of usage
enhances inventory accuracy and records real time information. Mobile personalization
goes one step further by providing the user with the flexibility to record data that is most
relevant for the transaction without compromising the accuracy of transaction. In
addition, mobile personalization can record additional user defined data in flex fields for
specific transactions. Using this feature a warehouse can immediately realize the
following benefits:
transaction form
logic
and difficult to maintain.
WMS mobile pages which support Mobile User Interface Personalization include:
Pick Load
Pick Drop
Manual Load
Item Load
Move Any LPN
Putaway Drop
Update LPN
PO Receipt
PO Receipt Information
LPN Ship
Mobile Ship Confirm

Task Extensibility features provide tremendous implementation flexibility in the
execution of WMS tasks. This feature will deliver a public API to modify, update, split
and cancel a WMS task. Using these features, WMS task functionality can be extended
for customer or industry specific needs. The following list of business scenarios
illustrates the applicability of this API:
A user defined application that dispatches tasks to warehouse workers. Task API
will be used to modify task status from unreleased to pending
An extension that assigns a task to a warehouse operator based on a customer
specific logic
An extension to the cartonization algorithm that can split a task and assign a
cartonized LPN to tasks
An extension that supplements the warehouse control system layer to allow the
warehouse automation system (for example and automated storage and retrieval
system) to enable the automation system to drive updates to the lots, serials or
quantities picked
3.5.2.4. Dock Scheduling and Load Sequencing

Organizations leveraging both Oracle Transportation Management (OTM) and Oracle
Warehouse Management (WMS) can now make use of additional integrations between
the two products to drive distribution efficiencies. OTM can schedule shipments to dock
doors and sequence the loading of trailers at the doors based on time required, door
availability and stop sequence for drop offs. With this feature, the dock doors, the dock
door appointments and sequence of loads into a trailer can be synchronized with WMS.
WMS will use this additional information to plan outbound activities such as:
Release of shipments for pick execution based on dock door schedule
Sequencing of drops in the staging area for a multi-stop shipping itinerary
Sequencing of tasks for picking when a multi-stop shipping itinerary is being
used
3.5.2.5. LPN Status
Even in the most efficient manufacturing and distribution networks, quality issues may
arise. Packages may arrive damaged from transportation; defects may be detected in
manufacturing long after the product has left the production center; or quality issues may
affect only some of the LPNs produced in a manufacturing batch. With this feature, the
material status model has been extended to provide License Plate (LPN) level holds.
This will enable warehouse users to:
Put individual pallets, cases or totes on hold without impacting the rest of the lot
or the batch.
Place holds on material that is neither lot nor serial controlled without moving
that material to a quarantine location for speedier intervention when issues are
discovered.
Separate the physical movement of material and changes to the material status
into different responsibilities, which will prevent the accidental change of
material status when material is moved.
3.5.2.6. UCC-128 and Case Picking Enhancements

In consumer packaged goods industry, its common requirement to have the goods packed
into containers with UCC-128 labeling. While the ability to print UCC-128 label already
exists in WMS R12, this feature makes it easy to manage varied compliance needs of
customers in consumer packaged goods industry based on customers ASN preference
e.g. pallet level ASN or case level ASN, order type e.g. bulk order, store order, etc. This
feature will also allow printing of sequential carton count on label e.g. 1 of 3, 2 of 3,
etc. and also allow generation of ITF-compliant (I 2 of 5 labeling standard) labels with
shipping information.
This feature also introduces support for efficient Case Picking. The case labels printed
at order release can be assigned to pick operators. The operator can now perform case
picks and either perform Pick to Belt or Pick to Pallet by scanning multiple case
labels.
3.5.2.7. Over-Allocation Using WMS Rules

This feature is useful to pick items that are difficult to fulfill in exact order quantity.
Examples of such items are: Metal strips, Gas cylinders, fluid containers, paper rolls,
wire bobbins, etc. Such items are typically stored or packed in non-standard quantities in
the warehouse. Over shipment is a very common business practice for such items since
its not cost effective to cut, split or unpack the items in order to ship the exact ordered
quantity.
In this feature WMS rules can be configured to over allocate containers that are within
over shipping tolerance and at the same time closest to the requested quantity on the
order. In this way WMS operators are directed to pick containers that require minimal
material handling without entering any pick exception codes even though the pick
quantity may be greater than requested quantity.
3.5.2.8. LPN Over Allocation during Pick Release

Certain industries and business situation require that an Order cannot be fulfilled in the
exact quantity. A good example is primary metal where an order for an item such as steel
sheets cannot be exactly fulfilled because its expensive to cut a steel sheet to match the
exact order quantity. In such situations, over allocation or under allocation is a normal
business practice. This feature in Oracle WMS facilitates over allocation of an entire LPN
provided its within over shipment tolerance defined on the Order Line.
3.5.2.9. Directed Putaway of Reserved LPNs
In a made to order manufacturing environment, the finished material is often packed into
LPNs at manufacturing completion. In order to ensure that the manufactured material is
fulfilled correctly, the entire LPN is reserved to the sales order. However its a common
business scenario to putaway the LPN within the warehouse prior to its eventual
shipment to the customer. This feature allows a reserved LPN to be transferred or
putaway within the warehouse while retaining the reservation for the customer. The
reservation guarantees the supply for the order line while the system enables you to move
reserved lots within an LPN throughout the warehouse.
3.5.2.10. Reusing LPNs

The REUSE_LPNS API enables you to reuse LPNs and to review an LPN history. This
API enables you to physically re-use returned containers after their contents have been
issued out of stores, or returned using an RMA (return materials authorization).
3.5.2.11. Cluster Pick by Label

One Step Pick and Pack Process i.e. picking of products directly into a shipping carton
offers huge productivity gains as no downstream packaging is required. Oracle
Warehouse Management currently supports One Step Pick and Pack Process using
cartonization and pick by label picking. This feature makes it possible to pick one or
more orders (the cluster) directly into their respective shipping cartons (pick by label).
With this feature it is now possible to get further productivity using one step pick and
pack for several orders at once.
With cluster pick by label, labels are printed at pick release and manually distributed to
operators based on criteria such as cart capacity. An operator scans multiple labels, and
WMS facilitates interleaving of picks from several orders in one pass of the warehouse.
3.5.2.12. Distributed WMS Deployment

Distributed WMS deployment is a new feature delivered as a patch on Release 12.1.1.
Until now Oracle E-Business Suite (EBS) Warehouse Management System (WMS)
required the transaction source systems of Purchasing and Order Management and
execution systems like WMS to reside and operate within the same instance. With a
Distributed WMS deployment, its possible for WMS to be installed on a separate
physical instance that is independent from the remaining applications of E-Business Suite
such as Order Management, Purchasing and Financials. This feature gives powerful
choices to customers to deploy WMS either "integrated" as a module within EBS or as a
"distributed" and independent solution installed on a separate instance. Customers who
want the latest WMS features in R12.1 can have WMS deployed on a separate instance
without upgrading the entire application suite. This feature also makes it possible to use
Oracle WMS for warehousing operations along with an EBS or a non-EBS host system.
In addition, warehouse with network connectivity issues can also consider a distributed
WMS installation for an "always on" WMS solution.
To better support this deployment methodology, the distributed WMS Integration with
Oracle EBS provides a starter kit for integration between a distributed WMS instance and
an EBS 11.5.10, 12.1 or 12.2 instance.
3.5.2.13. Advanced Wave Planning

Advanced Wave Planning is a new feature being released as a patch on Release 12.1.1.
Advanced wave planning provides advanced Pick Wave management functionality over
and above what currently exists in pick release. Wave Planning is particularly useful for
warehouses that fulfill a high volume of small order lines. Wave planning makes it easier
to manage large order volume by grouping orders into waves and subsequently releasing
them for execution and monitoring.
With Advanced Wave Planning warehouse managers can select orders using simple
criteria and group them into pick waves. In addition, advanced filters similar to the WMS
rules engine can be used to select orders for waves as well and create waves by
constraining them to be within certain line count, weight, cube or value. Wave planning
provides a preview of lines and tasks, expected completion, fill rate and labor needs prior
to release of the wave. Advanced wave planning also comes with a Wave Dashboard that
can be used to view wave progress and drill down to detailed line or task status. The
exception engine in wave planning can be configured for specific business cases to
proactively look for exceptions so that corrective action can be taken. For example, a
severe exception can be triggered if 80% of the lines in a wave are not loaded to the
trailer 30 minutes prior to dock appointment end time.
The other advanced wave planning feature is task planning. The task planning criteria can
be used to configure the conditions under which tasks will be released automatically for
execution.
3.5.3. Release 12.1.2
3.5.3.1. Advanced Wave Planning Enhancements

In a distribution center, a wave is a grouping of orders governed by user defined criteria
for release to the warehouse floor. Wave Planning is particularly useful for warehouses
that fulfill a high volume of small order lines. It makes managing large order volume
easier by grouping orders into waves and subsequently releasing them for execution and
monitoring.
Advanced Labor Planning

With further enhancement as part of release 12.1.2, Advanced Wave Planning now
provides detailed labor requirements planning for the wave. Advanced wave planning
also offers additional travel time modeling criteria to provide more precise labor
requirement for pick execution based on item category, operation plan and pick zones.
Pick Rules and Crossdocking

Wave planning now considers the impact of crossdocking criteria on fill rate estimation.
The scope and visibility provided in Wave Management user interfaces has also been
enhanced to provide visibility to inventory in receiving area and in-transit material for
high speed warehousing and visibility to cross docking tasks. In addition wave planning
also offers the ability to compute fill rate based on pick rules constraints a. The fill rate
computation based on pick rules and crossdocking allows warehouse managers increased
visibility to material and labor availability and ensure that only waves feasible for
execution are released to the warehouse.
Enhanced Exception Handling

Advanced Wave Planning in release 12.1 offered flexible order grouping, wave creation
and release using advanced filters and dashboards to monitor wave progress along with
configurable proactive exception handling.
Advanced Wave Planning now has the ability to add and respond to exceptions such as
managing emergency orders in an active wave and canceling tasks.
3.5.3.2. Task Cancellation

Cancellation of tasks is often required in a warehouse environment. Cancellation of tasks
may be needed when material allocation or warehouse task planning needs to be revoked.
Cancelling tasks feature gives warehouse managers the flexibility to stop execution of
certain tasks without the need to backorder sales order lines and gives them the
opportunity to release lines with new allocated material and task assignment at a later
time.
3.5.3.3. High Volume Case Picking Support

Case pick efficiency is critical in high volume distribution centers where more picks are
in cases than individual units or whole pallets. Release 12.1 introduced case picking
methodologies that allowed an operator to bypass labeling and scanning processes while
loading cases at the picking line. Case picking could optionally become a label initiated
process where labels are generated prior to wave release. The operator can then use these
labels to conduct the picking operation.
In Release 12.1.2, the case picking is further streamlined by allowing labels to be

grouped and sequenced prior to wave release. This allows operators to selectively choose
the labels that will send them to a specific zone or aisle, thus limiting travel time across
the warehouse. Picks within that label set can be automatically grouped and sequenced by
pick slip grouping or order.
Release 12.1.2 now also offers the capability to load and drop the tasks only after the last
task for an order is dispatched to the user. This provides further visual cues to the user
that their current set of work has ended and allows them to prepare for a run to a staging
area. This capability is enabled for discrete picking, order picking and manifest picking
to streamline the traveling path when orders are grouped for dispatch to a single user.
3.5.4. Release 12.1.3
3.5.4.1. Opportunistic Cycle Count

Cycle count is a powerful tool to ensure inventory accuracy in the warehouse. Regular
cycle count is a recommended best practice for warehouses. The most efficient way to
count a locator is when the operator is already present at the locator for a pick activity
and the on-hand stock at the bin is either zero or close to zero. This way cycle count of
the location can be optimally executed when the operator is already physically present at
the location. Moreover the task of counting is also further simplified because the locator
is either empty or close to being empty.
Opportunistic cycle count achieves this goal by interleaving a cycle count task with
picking. In addition, the count threshold can be configured in WMS to trigger a cycle
count task when its most convenient to do so. The threshold can be set to 0 i.e. the
operator will be asked to count after a pick activity only if the pick results in driving the
locator empty.
3.5.4.2. Lot Substitution

Warehouses stocking lot controlled material often commingle lots in the same locator e.g.
pallets with different lots in a 2-deep pallet location. In such a scenario physically
performing the move to reach the right pallet is counterproductive. This is especially true
if the warehouse does not follow a strict lot allocation or FIFO policy. Lot substitution
feature in WMS provides the flexibility to the pick operator to override the system
suggested lot. WMS will continue to direct the picker to a location and a lot; however the
picker can pick a different lot by entering an exception. Lot substitution provides
tremendous amount of flexibility and convenience to warehouses that stock lot controlled
products and often commingle them in the same locator.
3.5.4.3. Distributed WMS Integration with Oracle EBS

The distributed WMS deployment option provides enormous flexibility in deploying
WMS. By enabling the distributed WMS option, customers can deploy WMS on a
separate instance that is physically distinct from an Oracle EBS instance. In this
implementation model, the distributed instance of WMS will be focused exclusively on
warehouse execution with minimal configuration required outside of WMS.
The distributed WMS Integration with Oracle EBS provides a starter kit for integration
between a distributed WMS instance and an EBS 11.5.10, 12.1 or 12.2 instance. Using
this integration, the Order to Cash and Procure to Pay processes can be executed
seamlessly within the two systems. The order capture and receivables management takes
place in EBS and warehouse wave planning and subsequent pick, pack and ship
execution is managed in WMS. Similarly procurement and payables management takes
place in EBS and receiving, inspection and putaway is managed in WMS.
3.5.4.4. LSP Management and Activity Based Billing

LSP Management addresses a critical requirement of Logistics Service Providers (LSP)
to manage their warehouse in multi-tenant mode. LSP management feature allows quick
on boarding of client in the warehouse, allows automatic segregation of activities for
every client and also enables process level differentiation for each client using client level
rules.
Activity based billing is a critical requirement for The LSPs perform material handling on
behalf of their clients. These warehouses managed by LSPs receive, store and ship
product on behalf of their clients. Activity based billing provides a complete solution that
refers a service level contract, pricing of logistics services and relies on activity data in
WMS to produce an itemized bill based on the actual services performed by the
warehouse on behalf of the clients. Using activity based billing LSPs can invoice their
clients accurately with minimal overheads.
3.5.5. Release 12.2
3.5.5.1. Advanced Catch-Weight

Catch Weight management applies primarily to the manufacturing, distribution and
consumer product industries where weights can vary from piece to piece, either due to
biological variations, or because of weight loss that occurs during storage. This
variability affects the procurement pricing and sales invoicing processes. A distinction
must be made between the fulfillment unit of measure and a valuation unit of measure.
While the fulfillment unit is the leading unit for all processes in operative logistics, the
valuation and payment flows take place on the basis of the valuation unit. The logistic
units often used are pieces, cases or each; the valuation units often used are
Kilogram/Pound. Although the term catch weight is most commonly used in the food
industry, this feature could be leveraged by a range of industries including those that
manage products with variable lengths.
As the raw material flows through the manufacturing process, the likelihood of finished
product not adhering to standard conversions is high. Even after storage, the finished
product can lose or gain weight due to heat or humidity in the facility. One storage
locator can have products from multiple process batches or lots in multiple license plates
(LPNs) which each have a different weight.
Most consumer packaged goods companies cost and invoice by weight and fulfill by
units. As a result of this, items are mostly defined with a Primary UOM of weight and a
Secondary UOM of units. For a warehouse resource involved in the fulfillment process,
a pallet of boxes of beef looks the same irrespective of the batch or lot or LPN. For this
reason, flexibility is needed regarding which UOM to use for fulfillment.
The Advanced Catch-Weight solution addresses this problem by introducing the concept
of a Fulfillment Base at the sales order line level. The Fulfillment Base is driven from
the Ordered UOM class and can either be the Primary UOM or the Secondary UOM.
Fulfillment Base is honored in warehouse management while fulfilling the order line.
Enhancements have also been made to Order Management, Advanced Pricing, Shipping,
and Mobile Supply Chain Applications to support this solution. Please refer to the
Advanced Catch-Weight Solution in Oracle E-Business Suite Applications white paper
for additional details [ID 1551171.1].
3.5.5.2. Additional Mobile User Interface Personalization Pages

A major benefit of Warehouse Managements mobile data entry capability is the ability
to record a material movement at the point of usage. Data entry at the point of usage
enhances inventory accuracy and records real time information. Mobile personalization
goes one step further by providing the user with the flexibility to record data that is most
relevant for the transaction without compromising the accuracy of transaction. In
addition, mobile personalization can record additional use defined data in flex fields for
specific transactions. Using this feature a warehouse can immediately realize the
following benefits:
transaction form
logic
and difficult to maintain.
In this release, Mobile User Interface Personalization has been has been extended to
support the following WMS mobile pages:
Detail pick
LPN Inquiry
ASN Receipt
Cycle Counting
Lot Attributes
LPN Pack
LPN Split
LPN Unpack
Mobile LPN Inspection
Account Alias Receipt
Account Alias Issue
Physical Count
Item Inquiry
3.5.5.3. Return to Vendor enhancements
In this release, the Return to Vendor process has been enhanced to manage the fulfillment
process of any outbound shipments associated with the return and to offer greater
flexibility in the determination of which facility can ship the returned goods.
The major features include:

1. Create Return Request in Oracle Receiving and track the corresponding
shipment in Oracle Shipping Execution.
2. Print documents and perform export compliance check for the material being
returned to vendor.
3. Execute ship confirm for Return Order from the mobile Quick Ship form.
4. Return material using return request without requiring a purchase order.
5. Return material from any warehouse independent of the Warehouse
Organization in which it was initially received.
3.5.5.4. Contingent Worker Support

Temporary workers are a standard business practice in warehousing. Oracle Warehouse
Management now supports defining contingent workers as warehouse labor resources, in
addition to permanent employees.
3.5.5.5. Mobile Logout Warning

In order to avoid productivity losses due to unintentional logouts by mobile users,
WMS mobile user interfaces now show a warning and request a re-confirmation before
logging out a mobile user.
3.5.5.6. Distributed Warehouse Management Integration to EBS R12

As the number of customers live on E-Business Suite Release 12 grows, so too has the
demand to provide integrations between Release 12 and Oracle Warehouse Management
(WMS) for those customers who choose to implement their WMS on a separate instance.
To better support this deployment methodology, the distributed WMS Integration with
Oracle EBS provides a starter kit for integration between a distributed WMS instance and
an EBS 11.5.10, 12.1 or 12.2 instance.
3.5.5.7. Task Management Usability Enhancements

Several usability enhancements have been made to the task dispatching user interfaces in
Oracle WMS in order to better support high volume operations with greater efficiency
and ease.
First, Oracle WMS now enables a user to confirm a pick for a Move Order Issue
transaction without reconfirming the account to which the material is being charged.
This will save extraneous keystrokes in environments where users are shown a non
editable account field that does not influence the picking activity.
Next, when a user overrides a suggested destination locator in which they are dropping
material for a given task, Oracle WMS provides an audit page for the operator to indicate
the reason for the discrepancy. The reason selected can initiate a corrective action and
will also be recorded for audit purposes. In this release of Oracle WMS, the list of
exception reasons will be pre-populated in the audit page to reduce the number of
keystrokes an operator has to perform in order to complete the task at hand.
Further, if a user substitutes a lot (picks a lot that was not the system suggestion for the
pick task) and picks the entire quantity in the LPN, that LPN will be defaulted as the
Transfer LPN, thus allowing the user to pick an entire case without repacking it, even
when lot substitution is performed. This defaulting is also supported when the user picks
the entire quantity in an LPN as part of an over pick against the allocated lot. Substitution
is now allowed for items that are both lot and serial controlled, provided serial allocation
is turned off.
Finally, when cycle count tasks are being performed, the system will now take the user
into the next appropriate cycle count task rather than returning them to the menu to select
the next unit of work to be performed. This ensures greater system control over operator
work and will also save operator keystrokes as they perform counting through the
warehouse.
3.5.5.8. LPN Visibility in Receiving

When a serial number is inspected in WMS, the Receiving Transactions user interface in
the desktop can now show the inspection transaction and its results at the shipment line or
LPN level instead of serial by serial. This enables better auditing capabilities in high
volume serialized environments. Further, the Receiving Transaction form and Manage
Shipment form now allows users to view and query by LPN on the desktop so that
desktop users have greater visibility and traceability to receipts performed as well as
expected shipments in Oracle WMS.
3.5.5.9. LPN Split Transaction Enhancements

In order to better support high volume distribution environments with greater efficiency,
the following changes have been made to the way in which LPNs are managed in Oracle
Warehouse Management:
If an LPN split is performed for a source LPN that had only one item in it, the system will
now present a <Next> page that is blank, allowing the user to select a new destination
LPN for the subsequent split transactions.

Organizations with the need for additional validation for data entered on the mobile
interface can now leverage a new stub in the Warehouse Management mobile user
interface to validate the user input. This stub allows the system to ensure that any entity
conforms to your naming conventions, desired formats and can be validated against any
logic specific to your business in addition to the existing Oracle WMS validations.
Organizations with the need for additional control over when labels are printed can now
leverage a new stub to specify which labels to print. For example, when splitting a parent
LPN completely into children LPNs it may not be desired to print all of the labels
generated for the parent LPN since this LPN will finally be empty at the end of the
transaction.
3.5.5.11. Warehouse Control Board and Material Workbench Enhancements

The Material Workbench has been enhanced to accommodate for material that has been
picked from LPNs and loaded for tasks, but has not yet been dropped to the destination
location. This provides a real time on-hand and availability picture to the user.
The Warehouse Control Board has been enhanced to show additional details for the
exceptions related to the tasks that are queried up by the user. This facilitates any
corrective actions to reduce or eliminate such exceptions to improve productivity. In
addition, aborted outbound picking tasks Pick None or Zero Pick Exceptions are now
visible as exceptions on the Warehouse Control Board.
3.5.5.12. Packing Workbench Enhancements

The Packing Workbench has been enhanced to support Lot Attributes entry for lot
controlled items. This allows users extended functionality to provide Lot Attributes
values during the packing operation using the workbench. Lot attributes are stored in a lot
level descriptive flexfield.
3.5.6. Release 12.2.4
3.5.6.1. Multiple Cycle Count Task Types

WMS supports multiple task types for cycle counts which enables users to leverage task
type assignment rules to assign cycle count tasks. This provides the flexibility to dispatch
counting tasks based on customer specific business logic and setup. This feature could be
used to assign cycle count tasks for different subinventories to different operators that
may be using different equipment.
3.5.6.2. Cycle Count Skip Task

The cycle count task mobile page allows the user to skip the current cycle count task and
get the next eligible cycle count task. This provides consistency between cycle counts and
picking tasks around the skipping operation and improves efficiency by eliminating extra
keystrokes.
3.5.6.3. Drop by Location

Drop by Location allows users to drop all outbound loaded LPNs destined to the same
locator in a single step. This eliminates the need to perform separate drop for each LPN
loaded and increases the efficiency of the overall picking process.
3.5.6.4. Configurable Picking Exception

When a Curtail Pick or Pick None exception is raised during picking, user have the
option to configure the exception handling in one of the following two ways:
1) Backorder only the current tasks on which the exception was raised
2) Backorder the current task and all other tasks for the same SKU
Raising an exception associated with 'Cycle count' workflow generates an alternate
suggestion based on the pick rules. Once this suggestion is created, there is a configurable
extension to let the customer determine picker of this picking suggestion.
3.5.6.5. Cycle Count Workflow for Change Locator/LPN Exception

The picking exception Change Locator/LPN, can now be associated with the cycle
count' workflow. This provides the functionality to create new cycle count entries/
reservations when the user raised a Change Locator/LPN exception. This ensures the on
hand inaccuracy does not translate to incorrect tasks downstream and improves overall
picking efficiency.
3.5.7. Release 12.2.5
3.5.7.1. Mobile Task Dashboard
Currently, the WMS Task Dispatching engine dispatches tasks to the warehouse operator
based on their eligibility to perform the task and task priority. Skipping such a task
automatically brings the next best eligible tasks. However at times, the user may not be
able to perform certain set of tasks due to reasons like damaged locator, blocked material
etc. This would require the user to skip multiple tasks before they can get the desired task
thereby reducing productivity and efficiency. This enhancement allows the warehouse
operator to view all the eligible tasks for the current task group and select the desired task.
The user also has an option to configure and view the shipping and packing instructions
associated with the sales order line of the task.
3.5.7.2. Nested LPN Pick
Current picking functionality allows a warehouse operator to pick only the immediate
contents of an LPN. As a result, for a nested LPN, the operator is forced to break the LPN
and pick the material from the inner LPNs thereby reducing the overall picking efficiency.
This feature will enable picking of nested LPN provided:
All the child LPNs within the nested LPN only have the item associated to the
current task
Contents are contained within the same level of the nested LPN structure
Sum total of quantity within the inner LPNs is less than the task quantity or
within the over shipment tolerance of the sales order line
Nested LPN is picked in its entirety
3.5.7.3. Picking by Zone

Customers with large warehouse and subinventories often divide it into zones for
efficient picking. The current task dispatching logic dispatches the task only
at the subinventory level. This new feature allows the operator to sign into a zone and
filter the tasks dispatched to the specific zone. The WMS Rules engine framework has
been enhanced to configure picking, put away and task type assignment rules based on
zones while the Warehouse Control Board provides the ability to query and managing the
tasks by zones.
3.6. Oracle Warehouse Management Extensions for Oracle Endeca
3.6.1. Overview
Imagine always being able to focus on the right priorities at the right time. Endeca brings
order to the chaotic flow of data we deal with on a daily basis. Oracle Warehouse
Management Extensions for Oracle Endeca turns raw data into accessible, usable
information for discovery. This provides information that is the basis for action. Oracle
Warehouse Management Extensions for Oracle Endeca have native application support
for mobile tablets.
3.6.2. Release 12.1.3.4
3.6.2.1. Plan Fulfillment

Within Plan Fulfillment, a Warehouse Manager can plan outbound work for the day.
Visibility to daily work as well as overdue work provides a full picture of demand. All in
one place, demand can be compared to the inventory situation. Overall scarce inventory
or stock outs are highlighted. Then additional attention can be paid to high value orders
with stock issues.
Plan Fulfillment can quickly and efficiently simulate pick waves based on available
inventory. Warehouse Managers can filter and visually shop for which orders to
include in a Pick Wave. This is useful when youre manually trying to decide what to
release into a pick wave. From the Plan Fulfillment work area, the Warehouse Manager
can launch a manual pick release or create and launch a pick wave in Oracle Warehouse
Management. The user also has visibility to order and item details and access to manage
reservations.
3.6.2.2. Track Fulfillment

The Track Fulfillment work area allows the Warehouse Manager to quickly identify
customer orders that are being fulfilled. Full visibility to fulfillment status (picked, picked
with exception, staged) helps track the fulfillment of customer orders in the warehouse.
The Warehouse Manager can reprioritize or reassign a warehouse task appropriately. Top
picking exceptions are visually highlighted. Users have the ability to manage delivery
exceptions, holds and interface activity which can delay the fulfillment and revenue
recognition process.
3.6.2.3. Space Utilization

The Space Utilization Work Area visually shows the Warehouse Manager where the
problem areas are in the warehouse in terms of material storage. Poorly slotted material,
fragmented items, and fragmented locators are highlighted. A new feature to highlight
fragmentation based on velocity has been introduced as a part of this release. The
Warehouse Manager can then initiate a movement request to consolidate fragmented
material, improve the slotting of material or update item/locator status to manage
quarantine/recalls, all from this work area.
3.6.2.4. Labor Utilization
The Labor Utilization work area allows you to do Information Discovery on the actual
work transactions performed in the warehouse. For example, the Warehouse Manager can
analyze the details around How much work is left to complete the fulfillment for the
next carriers pickup? or How is that work spread across the different areas of my
facility? Then the actual labor information can be reviewed to perform a root cause
analysis. The Warehouse Manager can identify overload situations and reassign staff to
improve labor utilization. Visual representation of completed tasks by warehouse
operator provides insight into labor trends and helps with forecasting labor requirements
based on historical trends.
3.6.3. Release V5
3.6.3.1. Plan Fulfillment Enhancements

Changes to Plan Fulfillment include:
"Create Wave" is available as a page link in standard Endeca navigation and has been
removed from the actions menu on the results table.
"Create Wave" page now defaults the filters selected by the user.
Reservation page accessed from Endeca now defaults the data for selected
reservation.
3.6.3.2. Space Utilization Enhancements

Velocity fragmentation is restricted to top 1000 items and locators and ignores project
locators for velocity calculation.
3.6.3.3. General Features

All tabs can be configured to upload data for specific organizations and/or subinventories
by setting the following lookups:
Organization Control for INV Endeca Extensions
Subinventory Control for INV Endeca Extensions
The default value for the lookups is ALL, which implies all Inventory organizations
and/or subinventories are uploaded by default. Users may choose to restrict the upload to
specific organizations and/or subinventories, in order to limit the amount of data in each
periodic refresh.
Users can invoke the shipping transaction form directly from delivery link with delivery
information defaulted.
Users can reference flexfields to filter data based on specific attributes.
3.6.4. Release V6
3.6.4.1. Capacity Analysis
Capacity analysis enables the user to track the inventory capacity (available and
occupied) in terms of units, weight and volume. Customers who have locator control
enabled will benefit the most from this information discovery since the capacity attributes
are only available at a locator level. A new tab Capacity has been added to the WMS
Space Utilization Page and provides detailed information on the Locator consumption
and its availability. Users can select data displays related to capacity analysis for locators
with finite capacity or infinite capacity corresponding to the selected filter.
3.7. Oracle Yard Management
3.7.1. Overview
Oracle Yard management improves equipment and material visibility, increases labor
productivity, and reduces detention and demurrage costs. Both private fleet and third-
party tractor and trailer units can be efficiently tracked and managed while they are on
your yard premises. Raw materials, packaging supplies, and/or finished goods can be
moved efficiently within a campus style environment. Increased dock door efficiency is
critical for facilities with automated truck loading systems and just-in-time production
operations.
3.7.2. Release 12.2.4
3.7.2.1. Yard Definition

For each campus, a yard organization manages your operations. Yard areas can be used
to model inbound, outbound, and storage areas within a yard organization. Parking spots
are used within a yard area to track exactly where equipment is located. A yard
organization can service multiple warehouse facilities on a campus which are setup as
separate Inventory Organizations.
3.7.2.2. Equipment Definition

Oracle Yard Management allows you to manage tractors and trailers within your yard
premises from the equipment type (e.g. 48 flat floor trailer, single power unit) down to
the specific unit (aka serial). You can manage both your private fleet as well as 3rd party
owned equipment.
3.7.2.3. Dock Scheduling Workbench

Oracle Yard Management includes a graphical dock appointment scheduling workbench.
Dock appointments created in Oracle Yard Management can be reflected in both Oracle
Warehouse Management and Oracle Transportation Management. Optionally,
collaboration with carriers to tender and schedule carrier appointments in Oracle
Transportation Management can be reflected in the Dock Appointments in both Oracle
Yard Management and Oracle Warehouse Management.
3.7.2.4. Yard Transactions

Oracle Yard Management manages the tractor and trailer activity into, within, and out of
a yard facility. Business events can also be raised during various yard transactions. The
yard transactions are:
- Check-In: When equipment arrives at the yard premises, a check-in transaction will
initiate the tracking of the yard equipment and capture relevant information including
equipment condition, seal code, whether seal is intact, driver name, driver license
number, tare weight, gross weight, shipment document reference, and more. Label
printing is also available at check-in time to capture/post all necessary information.
- Unsealing: Sealed trailers can be unsealed before receiving. Unsealing trailers
provides the opportunity to inspect them and update their status accordingly.
- Unloading: After a loaded trailer has been checked-in, the trailer is ready to be
received.
- Yard Move: Used to move a specific piece of equipment around the yard or between
buildings on a campus, to retrieve equipment from the yard to the required dock door,
or to move equipment from a dock door back to an appropriate parking spot within
the yard. Mobile RF capability is available throughout yard movement.
- Loading: Once material is staged in the warehouse, the trailer is ready to be loaded
and eventually ship confirmed. Dock door and trailer information may be captured
as a part of the loading process.
- Sealing: Loaded trailers can be sealed before they check out of the yard.
- Check-out: When equipment leaves the yard premises, a check-out transaction will
capture relevant information including seal code, driver name, driver license number,
tare weight, gross weight, shipment document reference, etc
3.7.2.5. Material Workbench

The Material Workbench provides real-time visibility of yard equipment and the
Standard Carrier Alpha Code (SCAC) for inbound material in the yard from the facility
being serviced by the yard.
3.7.2.6. Yard Workbench

The Yard Workbench provides real-time visibility of yard equipment and the contents of
the yard with capabilities to assign tractors and trailers from one parking spot to another.
This information is based on the referenced shipment documents (such as Purchase
Orders, ASNs, RMAs, Sales Orders, Deliveries, Shipment Numbers, etc).
3.7.2.7. Integrations
Oracle Yard Management is a natural expansion of the Oracle Value Chain Execution
solution and has been designed with end-to-end process integration in mind.
3.7.2.7.1. E-Business Suite Integration
Oracle Yard Management has integration with EBS products, including Inventory,
Costing, Purchasing, Receiving, Order Management, Shipping and MSCA. Yard
Management has the flexibility to track costs (hence liability) in the yard, using
average costing and cost groups.
3.7.2.7.2. Warehouse Management Integration

Oracle Yard Management seamlessly integrates to Oracle Warehouse Management
when deployed either in integrated or distributed mode. A single yard and its
tractors and trailers can be shared across multiple Warehouse Management
organizations on a campus.
Dock Scheduling in Oracle Yard Management is integrated with Dock
Appointments and Dock Door Assignments in Oracle Warehouse
Management for both inbound as well as outbound Dock Appointments.
3.7.2.7.3. Transportation Management Integration
Companies can collaborate with carriers to schedule and book
appointments. These Carrier Appointments can be integrated with Oracle
Warehouse Management and Oracle Yard Management to optimize
inbound & outbound logistics.
3.7.2.7.4. RFID and Event Management Integration
Oracle Yard Management can be integrated into RFID technology to track
the physical flow of tractors and trailers within the yard and related value
added information services such as condition monitoring or security
related services. See the MSCA section of this document for more
information on new mobile transactions for Yard Management.
3.8. Oracle Mobile Inventory for Oracle E-Business Suite

3.8.1. Overview
With Oracle Mobile Inventory for Oracle E-Business Suite, inventory managers can
quickly look up on-hand and in-transit inventory across facilities.
View in-stock material across facilities

Identify existing material reservations
View loose vs. packed material
Identify pending material movements
View in-transit and received material
Query LPNs to view contents
Oracle Mobile Inventory for Oracle E-Business Suite is compatible with Oracle E-
Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must be a licensed user
of Oracle Inventory Management, with mobile services configured on the server side by
your administrator. Users of Oracle Warehouse Management get additional capability for
LPN Inquiry.
3.8.2. V 1.1.0
3.8.2.1. Mobile Foundation Updates

Improvements in login and configuration flow
Ability to change server URL without reinstalling app
Diagnostics improvements
3.8.2.2. Accessibility Improvements

There are accessibility improvements in the mobile inventory smartphone application.
Improvements in contextual tab bar , springboard, error/warning messages
Voice over improvements.
3.8.3. V 1.2.0
3.8.3.1. Android Support

In previous versions, Oracle Mobile Inventory for Oracle E-Business Suite was available
only for iOS devices. Starting with version 1.2.0, the app is now available for Android
devices as well.
3.8.3.2. Mobile Foundation Release 3.0 Updates
Changes to support both iOS and Android with the same client code
Ability to update server URL from Connection Details page

Ebs 122 Cum RCD Log

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ebs 122 Cum RCD Log

Hochgeladen von

Copyright:

Verfügbare Formate

ORACLE E-BUSINESS SUITE

RELEASE CONTENT DOCUMENT

Prepared by Oracle E-Business Suite Product Development

Last Updated: April 9, 2015

Copyright 2011, 2015 Oracle Corporation

2.1. Purpose of Document

3.1. Oracle Inventory Management

3.1.2.1. On Hand Material Status

3.1.2.2. Extensibility Enhancements

3.1.2.3. Lot Genealogy Enhancements

3.1.2.4. Purchasing by Revision Enhancements

3.1.3.1. Supply Chain Web Services for Items and Inventory

Following web service is provided for Item:

Following web services are provided for Inventory:

3.1.4.1. Optional Lot Allocation

3.1.4.2. Serial Number Assignment Enhancements

3.1.4.3. Return to Vendor Enhancements

3.1.4.4. Global Lot Attributes

3.1.4.5. Cycle Counting Enhancements

3.1.4.6. Distributed Warehouse Management Integration

3.1.4.7. Deferred Electronic Record & Electronic Signature Capture

3.1.4.8. Public APIs for Unit of Measure

3.1.4.9. Receiving Open Interface Enhancement

3.1.4.10. Pay on Receipt for LCM Organizations

3.1.5.1. Physical Inventory Integration Enhancements

3.1.6.1. Automated Return to Consignment for WIP Component Returns

3.1.7.1. Serial Tagging at Sales Order Pick

3.1.7.2. Consignment Returns after Consumption

3.1.7.3. Tablet Optimized Receiving Screens: Inbound Receipts & Exceptions

3.2.3.1. Plan Fulfillment

3.2.3.2. Track Fulfillment

3.2.3.4. Enhancements to Item Information Discovery

3.2.3.5. General Features

3.3.2.1. Charge Management

3.3.2.2. Advanced Pricing for Charge Templates

3.3.2.3. Landed Cost Calculation

3.3.2.4. Product Cost Dashboard

3.3.2.5. Tax Recovery

3.3.2.6. Integration to EBS Supply Chain and Back office

3.3.2.7. Procurement Integration

3.3.2.8. Receiving Integration

3.3.2.9. Cost Management Integration

3.3.2.10. Accounts Payable Integration

3.3.3.2. Visibility into Matched Invoice Amounts

3.3.3.3.Landed Cost Calculation History

3.3.4. Release 12.1.3

3.3.4.1. Landed Cost Simulation for Purchase Orders

3.3.5.1. Landed Cost Management Extensions for Oracle Endeca

3.3.6. Release 12.2

3.3.6.1. Update estimated landed cost (ELC) of Completed Shipments

3.3.6.2. Landed cost calculation for Selected Items

3.3.6.3. Manage Charges for LCM as a Service Flow

3.3.7.1. Update Completed Shipments API

3.3.7.2. Update Simulations for Approved POs

3.3.7.3. Invoice Matching to Receipts in LCM Enabled Organizations

3.3.8.1. Calculate Landed Costs for Returns and Corrections

3.3.8.2. Close Landed Cost Shipments

3.3.8.3. Flexibility on Actual Landed Cost Calculation for Charges

3.4.2.1. Mobile User Interface Personalization

3.4.3.1. Mobile User Interface Personalization Enhancements

3.4.3.2. Cycle Counting Enhancements for Lot Controlled Items

3.4.4.1. Mobile User Interface Personalization Enhancements

3.4.5.1. Mobile User Interface Personalization Enhancements