Main

Release 12 Archives

February 5, 2007

Oracle E-Business Suite Release 12

Oracle E-Business Suite R12 release has been anounced. Look here for more details on the release announcement. If you are a new or an existing customer, you can obtain R12 from Oracle Store or download it from  Oracle Electronic Product Delivery site.

Many of you are curious to know more about R12. The Oracle
E-Business Suite Online Documentation Library Release 12
can be downloaded from here. Please look at Metalink note 394692.1 for helpful links to plan your R12 installation or upgrade.

For Logistics, R12 is a major milestone with hundreds of new features spanning Inventory, Shipping, WMS, MSCA and transportation. Check out the R12 RCD for a complete list of new features in Logistics area.

Some of the main features in this release for those interested in Logistics are as follows. Those who attended Oracle Open World in San Francisco, may recall demo of some of these features.

Inventory:

  • Convergence with OPM
  • Dual Unit of Measure Control
  • Material status control
  • Advanced Lot Control
Shipping
  • Flexible Document Support
  • Workflow enabled shipping transactions
WMS
  • Oracle Process Manufacturing Support (With R12 WMS can be used by OPM customers as well)
  • Control Board Enhancements
  • Planned Crossdocking
  • Labor Management
MSCA
  • Oracle Process Manufacturing Support
  • Oracle EAM support
Transportation Execution
  • Multi-Delivery Consolidation
  • Third-Party Warehousing Enhancements

March 13, 2007

Locator Check Digits

In my previous posting on inventory accuracy in the warehouse, I referred to locator check digit feature in R12. In this blog entry I want to provide more details about this small but powerful feature to improve inventory accuracy in the warehouse. The biggest benefit of locator check digit is that it ensures that warehouse operator physically travels to the locator and performs transaction. Consider this example:

Suppose you have a "Pick to Clean" picking strategy and WMS directs the warehouse operator to pick the material from a far out locator say X9-2-4. What if the warehouse operator notices the very same product at locator Y4-5-2? What if the operator physically picks the material from Y4-5-2 but confirms the pick transaction at X9-2-4? No exception is logged and now you have two locators X9-2-4 and Y4-5-2 with incorrect inventory. What happens when WMS suggests X9-2-4 for putaway since it shows up as an empty locator? What does the putaway operator do when he travels to X9-2-4 and finds it occupied? Does he find another empty locator and confirms put away at X9-2-4?

Sounds familiar? How does check digits help? The way check digits work is that each locator is associated with a check digit and transactions can be confirmed only using check digit. This check digit is printed on the locator label physically but it is not suggested to the operator on the mobile device. Meaning that operator can use the locator suggested on the mobile device to travel to the locator but must go to the locator to record its check digit. Besides check digits also helps in faster data entry especially if you have to enter long locator values manually.

Here is a small utility that I have developed in Excel that could be useful for initial locator or warehouse bin definition in your warehouse. To summarize the Excel file does the following:

  1. Auto generates locators using range for 3 segments such as Row, Rack and Bin or X, Y and Z coordinates.

  2. Generate check digits for each locator using algorithms such as Modulo-10, Alphanumeric, or Unique 4 digit check digit

  3. Create locator labels with check digit. You need to have an XML enabled printer such as Zebra 110XiIII, Intermec PM4i, Sato CL412e, Toshiba B-SX6T, Cognitive Advantage LX, Datamax I-4308 or Printronix T5206. Alternatively you need an XML enabled print server such as Loftware, Niceware, Optio or Unibar.

The excel sheet can run a macro to generate the label XML. If you wish to randomize the check digits, there is a macro for it as well.


loc:


The locator generation parameters includes a range for each segment. Each segment in turn is split into two sections and you could provide a range for each section using the "From" and "To" parameter. You could for example create locators from EA1-A1-A11 to EA2-D3-Z14 by entering the "From" and "To" parameters as follows:


loc2:


The Excel sheet will create locators for all permutations of "from" and "to" segment  range values e.g. A1, A2, A3, B1, B2, B3, ...etc. Once again the excel sheet can be downloaded here:

http://blogs.oracle.com/adityaAgarkar/gems/locator.zip


Please note that this is freeware and you are free to modify or update it as you please.

April 25, 2007

Crossdocking from Manufacturing

In one of my previous posts, I blogged about facilitating "Just in Time" crossdocking from your assembly line directly to a shipping dock. The objective is to finish assembly completion into an LPN, move it directly to a staging area and then ship it. This process has obvious benefits such as:

  • Reduction in inventory, storage and thereby carrying costs

  • Minimal material handling and therefore reduction in labor and equipment costs

  • Reduction in lead time and therefore faster shipment

In order to make this process work, you need to tie the WIP job to a sales order using either the new planned crossdocking functionality in R12 or using ATO feature. Either way your WIP job will be reserved to the sales order. To further optimize the process, you need to minimize "contacts" for the shipping container and you might want to consider the following ideas:

  • Shipping Label at Manufacturing: To minimize material handling, you would want to create a shipping label directly at WIP completion for the license plates. The labels can be customer specific that include the customer name, address and purchase order number. By labeling the license plates at WIP completion, the shipping process can be simplified because no additional labeling steps may be required as part of the outbound flows. However the customer data is not available on any labels at WIP completion. You will need to use the "Custom Label Field" feature in R12 to fetch the shipping information e.g. a custom label field can be defined for  order number as follows. In this example the return value of the following SQL is mapped to custom label field defined for order number:

Select A.ORDER_NUMBER FROM OE_ORDER_HEADERS_ALL A, MTL_RESERVATIONS B, WMS_LABEL_REQUESTS WLR, OE_ORDER_LINES_ALL D
where WLR.ORGANIZATION_ID = B.ORGANIZATION_ID
and B.ORGANIZATION_ID = D.SHIP_FROM_ORG_ID
and D.HEADER_ID = A.HEADER_ID
and D.INVENTORY_ITEM_ID = B.INVENTORY_ITEM_ID
and B.DEMAND_SOURCE_LINE_ID = D.LINE_ID
and WLR.LPN_ID = B.LPN_ID
  • Conveyor for Staging Move: After assembly completion and labeling, you can have the operator drop the LPN on a conveyor with a fixed mount barcode reader and divertor that directs the LPN to the correct outbound dock based on the reservation and the dock schedule for the order. If you wish, you can also have an in-line weighing scale that verifies the actual weight of the container to its standard weight and diverts it to a manual inspection area based on a tolerance.

  • Automate Ship Confirm: If you wish you could also install a fixed mount bar code scanner to read the LPN barcode or have the LPN pass through an RFID portal to initiate ship confirm transaction for the LPN.

Update: The query mentioned above has been corrected. Thanks to Pawan Dwivedi for pointing out the error.

About Release 12

This page contains an archive of all entries posted to Warehouse Management in the Release 12 category. They are listed from oldest to newest.

RFID is the previous category.

WMS Implementation is the next category.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type and Oracle