Oracle Warehouse Management Advanced Lot and Serial Control

An Oracle Topical Essay December 2000

and character fields to simplify extensions you may wish to build on these attributes. customized for specific defaulting and validation requirements. In addition. or WIP Completion. Date Attributes The following date attributes have been added as named lot attributes: • • • • • best by date change date maturity date origination date (manufacturing date) retest date Maturity date is the date the lot matures and is ready for use (e.Oracle Warehouse Management Advanced Lot and Serial Control ADVANCED LOT AND SERIAL CONTROL Advanced Lot and Serial control provides two new areas of functionality for tracking lots and serials. forty unnamed lot and forty unnamed serial attributes have been added such that you may track important information for your industries (e. c_attribute1). Sublot functionality will allow customers to split and merge lots to differentiate between quantities of material that are no longer similar enough to be considered a single lot. Lot Genealogy stores the parent/child relationship between lots and sublots and provides lot traceability resulting from inventory transactions. Miscellaneous Receipt. Types of Attributes Oracle Warehouse Management System will natively store attributes in date.g.g.g. including all lot splits and merges. ATTRIBUTES Lot and serial attributes that are used widely across several industries have been added as named columns (e. The analogous functionality for Serial Genealogy has been available with Discrete Manufacturing since 11i. The opportunity exists for you to write extensions to update the material status of the lot once the maturity date or best by date is reached. Different attributes may be tracked for each item. while best by date is the date at which the quality of the lot may degrade. number. The attributes information can be populated any time new lots or serials are created. Best By Date). shipping to customers). Lot and Serial Attributes allow you to store a range of information for material based upon the lot and/or serial number. Origination date may be defaulted to the 1 . such as at Purchase Order receipt.

This information is stored in the D_ATTRIBUTE1 through D_ATTRIBUTE10 columns on the MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS tables respectively. locator. then the material status of the subinventory or locator will override the material status of the lot or serial number. Note that expiration date. Therefore. If the material status of the subinventory or locator is more restrictive than the material status of the lot or serial number. The re-test date is the date the material needs to be re-tested to re-verify its quality. the material status on the lot or serial number does not behave exactly as other lot or serial attributes. this date is the date of manufacturing completion. Numeric Attributes Some industries track numerous dimensions and weights of each lot. Character Attributes One category of additional lot and serial information to track are characteristics of the lot. This information is stored in the C_ATTRIBUTE1 through C_ATTRIBUTE20 columns on the MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS tables respectively. Up to thirty distinct numeric attributes can be used for any given lot. if applicable. country of origin. expiration date does not behave exactly as other lot attributes. Therefore.current date upon receipt and overridden to the date of manufacture at the supplier. and recycled content. the date after which lot should not be used in production or shipped to customers. or serial level. is controlled as it has been in past releases by the item attribute. Some of these characteristics may include lot grade. 2 . place of origin.g. color. You may define an item descriptive flexfield to track how frequently an item should be re-tested. farm. forest) supplier supplier lot number The following character attributes have been added as named serial attributes: • country of origin You may define up to thirty distinct character attributes for any given lot or serial number which reflects information that your organization captures for an item. lot. The following date attributes have been added as named serial attributes: • origination date (manufacturing date) You may define up to twenty distinct date attributes for any given lot or serial number which reflects information that your organization captures for an item. The following character attributes have been added as named lot attributes: • • • • • • • color country of origin date code grade place of origin (e. This item attribute can be used to default the re-test date. Note that the material status may be controlled at the subinventory. When completing finished product.

thickness. Attribute Functionality Lot and serial attributes is supported when you license the Oracle Warehouse Management product. Calculating the age in days and storing enhances the performance when allocation of lots based on their age is performed. width UOM) for each of the dimension attributes (length. 3 . If the origination date is not specified. width) be implemented together. volume. the creation date of the lot will be used. This information is stored in the N_ATTRIBUTE1 through N_ATTRIBUTE10 columns on the MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS tables respectively. The creation date of the lot is the same as the date the first quantity for the lot is received. The following numeric attributes have been added as named serial attributes: • • • • • • • • • • • cycles since new cycles since repair cycles since overhaul cycles since visit cycles since mark number of repairs time since new time since repair time since overhaul time since visit time since mark You may define up to thirty distinct number attributes for any given lot or serial number which reflects information that your organization captures for an item.The following numeric attributes have been added as named lot attributes: • • • • • • age (in days) length recycled content thickness volume width A concurrent program may be run to automatically calculate the age of a lot from the origination (manufacture) date when it is specified. thickness UOM. However. volume UOM. the lot and serial attribute functionality may be implemented for both WMS enabled inventory organizations as well as inventory organizations that are not WMS enabled. It is recommended for ease of use that the unit of measure attributes (length UOM.

For WMS-enabled organizations. previous field. while lot controlled textiles may include attributes such as length. The attributes of the material received will be inherited from the attributes of the preexisting lot. If desired. Populating lot and serial attributes are supporting for the following transactions for non-WMS inventory organizations: purchase order delivery. the attributes may be defaulted and/or overridden. Contexts can be assigned to item categories. and age. For instance. lot controlled food products may include attributes such as best by date. You may find it easier for if you remove the lot field from the Miscellaneous Transaction Lines window using the folder form functionality. so that all lot controlled items in a particular category have the same context. However. If desired. Default values for attributes can be specified when configuring the contexts. flow schedule completion. there may be exceptions to the item category. and use the lot and serial attributes. and SQL statement. maintain. Note: Populating lot attributes is only supported in the Lot Entry window of the Miscellaneous Transactions form. Desktop functionality Lot and serial attributes need to be populated when new lots and serials are created. Mobile functionality Lot and serial attributes need to be populated when new lots and serials are created. The currently supported default methods for attributes are constant. Note: it is not yet supported that suppliers may send lot and/or serial attributes on the ASN. thickness. By specifying a context for the lot and serial attributes. so individual items may be assigned to a context that overrides any item category assignment. Therefore. and style. the attributes may be defaulted and/or overridden by the receiver. The functionality will be enhanced in a future release to support this. However. When you receive against an existing lot. For inventory organizations. Note: There are distinct differences between the receiving process for WMS-enabled inventory organizations and regular inventory organizations. grade. this limitation has been lifted. lots and serials may not be specified until the delivery transaction. work-orderless completion.Oracle WMS supports forms and APIs to populate. Populating lot and serial attributes are supporting for the following transactions for non-WMS inventory organizations: receiving delivery transactions and miscellaneous receipt. the attributes of the material received will be inherited from the attributes of the pre-existing lot. current date. Populating lot and serial attributes are supporting for the following transactions for WMS enabled inventory organizations: inbound receipt (including ASN receipt) and miscellaneous receipt. When you receive against an existing lot. Populate Attributes Default by item number or category which attributes to collect at receipt The lot context or serial context of an item specifies which lot or serial attributes need to be maintained for each item. miscellaneous receipt. the introduction of the LPN functionality changes the business 4 . profile option. only those attributes which are appropriate for each item can be collected. the lot and serial attributes may not be populated until after this time. WIP completion. you may view but not update the attributes of the existing lot.

which will result in the attributes always being transferred with the material. Once the lot with the appropriate characteristics has been located. Therefore. Other material allocation requirements could include picking lots with the best by date at least fourteen days from the current date. If you wish to update a lot or serial attribute. the lot and serial numbers are specified at this time. For more information. However. Mobile functionality You may view lot and serial attributes through the mobile Item Inquiry form. Reservations is not supported for serial numbers. An audit log of changes to lot and serial attributes is not stored. that specific lot may be reserved. the context mapping can be made common to all organizations. Consequently the lot and serial attributes are specified at this time. please refer to the Inbound Topical Essay. Fulfilling sales orders based on lot and serial attributes If material is reserved at sales order entry. Transfer attributes with lot or serial number Lot and serial attributes are transferred to other inventory organizations within the supply chain. Limiting access is achieved by calling the Lots and Serials forms in query only mode (using the QUERY_ONLY form function parameter).flow substantially. Incoming material is packed into an LPN at receipt. The View Lot Numbers and View Serial Numbers forms will give non-authorized personnel view-only access to lot and serial attributes. there is no automatic way to identify that the first segment of one context is the same information as the first segment in a different context. this maintenance should be performed through the desktop form. viewing the attributes populated at receipt of the lot in the Materials Transactions desktop form may indicate whether the attributes have been updated since the original receipt of the lot or serial. To aid the requirement of transferring attributes when performing organization transfers. Complex picking rules may be configured to control the characteristics of the lots and/or serials you use to fulfill each order. Defaulting lot attributes when lots are split and merged 5 . If material is not reserved at sales order entry. the material will be allocated when the sales order pick released. so that the attributes only need to be populated once. it is required that the same context assignments be defined in all the source and destination organization. Otherwise. fulfilling sales orders based on the serial attributes will need to take place at pick release. For instance. Maintain & View Attributes Desktop functionality The Maintain Lots and Maintain Serial Numbers forms will allow authorized personnel to update lot and serial attributes. you may search for lots by their characteristics in the Material Workbench. In order to specify the material being packed into the LPN. However. Use Attributes Put-away based on lot and serial attributes Put-away rules may be based on lot and/or serial characteristics such as the country of origin or the age of the material. you may specify which grade of material each class of customer should received.

You may override the defaulted attributes. the lot attributes of the new lot are defaulted from the first starting lot. Therefore. Contexts are supported by descriptive flexfields. independent validation against a manually defined list of values. database types of varchar. Therefore. The value set determines the length of the attribute. The hierarchy for determining which context will be used is illustrated below: Context Level Global Global Organization Organization Assignment Type Item Category Item Item Category Item For example. if appropriate. the lot attributes of the new lot are defaulted from the lot attributes of the largest lot merged into the new lot. and date are supported. where the descriptive flexfield title is Lot Attribute or Serial Attribute. a value set must be specified for each attribute. If two lots of the same quantity are merged. as well as the type of validation of the date (no validation. Next. items. Define Context A context should be defined using the Segments form for descriptive flexfields. number. and can have a default value set based on any of the defaulting types mentioned earlier. etc… 6 . at the organization level or globally (Common to all Orgs). In addition. Setup There are two steps to setting up lot and serial attributes. Each context can have up to forty attributes (ten numeric attributes. different defaulting behavior will require different contexts. When lots are merged into a new lot. the organization level assignment by item will override the organization level assignment by item category and the organization level assignment by item category will override the global level assignment by item. the lot and serial contexts must be defined. Assign Default Context You will be prompted to enter the correct group of attributes for each type of item based on the assigned default context. so the setup is identical to the setup for descriptive flexfields. Different contexts should be defined for each type of item that tracks different groups of attributes. The reason for this step is that standard descriptive flexfield functionality requires the reference field for the context be on the transaction form. First. and ten date attributes). The item category field is not on the transactions forms. Finally. or table validation). You may assign by categories in any category set. this additional piece of functionality was built to drive the context off of the item category. Each attribute must specify which database column the attribute will be stored in. the lot attributes of the new lots are defaulted from the starting lot. twenty character attributes. the attributes may be driven off of the Inventory category set or a new category set may be created to drive the attributes.When a lot is split into multiple new lots. You may assign default contexts by item category or item number. the default context must be assigned to item categories and. Each attribute may be required or optional. since default values are defined at the context level.

In a recall situation. An example of this might be that a lot is stored in multiple locations. Sublots are created by splitting a single starting lot into multiple resulting lots.Note that in 11i. the priority of these two requirements need to be weighed to determine the optimal setup for your organization’s supply chain. In this case a sublot might be material produced in same shift. Implementation Considerations Should I default the context at the global or organization level? Contexts may be assigned at the organization level when different organizations in the supply chain wish to track different information regarding a lot and/or serial. To aid in this setup. Problems mainly result from the addition of a required lot/serial attribute once lots/serials exist for that item. a manufacturing plant may need to track more information about a lot and or serial than a sales office. For example. category sets may be enabled to allow items to be assigned to multiple categories within a category set. In general. disabling lot/serial attributes and adding non-required lot/serial attributes should not pose problems (other than the issue that all existing lots will not have information populated for the new attributes). inter-organization transfers of items with lot or serial attributes require that the same context assignments be defined in all the source and destination organization. 7 . lot merging. a pallet of material. Splitting may also be performed when a portion of a lot now has different characteristics. the context mapping can be made common to all organizations. You will only be able to select category sets that do not have this feature selected. or a roll of paper. changing that context may result in an error when querying up the lot/serial due to a null value in for a required attribute. For example. Customers usually need to split and merge lots to differentiate between quantities of material that are no longer similar enough to be considered a single lot. Lot genealogy is chiefly used in product recall situations. Once lots and serial numbers for an item have been defined with a given context. a company needs to be able to recall all assembly /final product lots that have had a particular component/raw material lot used in the manufacture. Something happens to one of the lots in a location which lowers the quality of the material. In summary. Production problems or tampering are examples of when a product recall is required. Sublot Control Features Sublot control can be broken into three primary components: lot splitting. and lot genealogy. Lot Splitting Lot splitting allows you to split a quantity of material that has been produced together as a single lot. This is required so that a unique context when receiving an item may be derived. On the other hand. Sublot Control Sublot functionality fundamentally consists of the ability to split and merge lots and to track a lot’s genealogy. How changeable is the Lot/Serial Attribute setup? It is recommended that a detailed analysis be completed of which attributes will be tracked for each item or category before receiving the material. Multiple lots can be merged into a single resulting lot. an ingot of metal. That quantity of the lot would be split into a different lot which is assigned the new quality characteristics. material that is sent back from the sales office might lose the information originally gathered regarding the lot and this information would need to be re-entered.

then a lot split may not be performed for the lot.0. has a material status that disallows lot merge. The same is true for merging lots. or the locator or subinventory in which the lot is located. then a lot merge may not be performed for the lot. or the locator or subinventory in which the lot is located. Lot Level Control Lot split and lot merge are transaction types. Modeling sublots as lots enables sublots to have the same depth of functionality that exists for lots. Full vs. Partial Lot Split/Merge A full lot split consists of splitting the entire quantity of a starting lot into resulting lots. Or even if lot split / merge is allowed for an item in general. a parent/child relationship between the two lots is stored. 8 . Item Level Control ‘Lot split enabled’ is an item attribute that has been added to control whether lot splitting should be allowed for that item. including all lot splits and merges. has a material status that disallows lot split. sublots are modeled differently from sublots. leaving remaining quantity in the starting lot. Similarly. they may be transactions that have been disallowed for certain material statuses. Both types of splits are allowed. Therefore. storing material in a vat or silo together) Lot Genealogy Lot Genealogy store the parent/child relationship between lots and sublots and provides lot traceability resulting from inventory transactions.Lot Merge Supporting lot merging will allow you to track when lots are stored together and the identity of each lot can no longer be maintained (e. “intelligent” lot numbering may be used. a sublot is a lot that has a parent/child relationship to another lot. The Split Lot form will only split lots for items that allow lot splitting. Restricting Lot Split and Merge For some items. The parent/child sublot architecture supports an unlimited number of levels. When a lot is split or merged. ‘Lot merge enabled’ is an item attribute that has been added to control whether lot merging should be allowed for that item. such that the lot genealogy is in effect in the lot number itself.g. For those that want the starting lot to be apparent in the lot number. In Oracle WMS 1. A partial split consists of splitting only a portion of the starting lot into resulting lots. The Merge Lot form will only merge lots for items that allow lot merging. there may be particular lots for which it should be disallowed. Hence. Note that a reserved lot cannot be merged. if the lot. If the lot. LPN Support Both loose and packed material may be split or merged. a lot may be split numerous times. lot split and/or lot merge should not be allowed. Sublot Features In some systems.

and they will be applied to all of the sublots created. the lot attributes will be defaulted from the first lot. In this case the new sublots will be automatically created. Autosplit When a lot is split into a small number of resulting lots. When lots in different LPNs are merged. transaction history of a lot. The lot attributes are also visible by lot in the lot source genealogy form. Where Used Genealogy A tree structure is shown on the where-used tab that shows all subsequent lots that have used a lot as an ingredient or component (often new lots created during lot splits). Manual Split vs. lot attributes. That new LPN can be either a pre-existing LPN. The profile option “INV:Genealogy Delimiter” determines what should be the delimiter between the item number and the lot number. When a lot is split into a large number of resulting lots.Lots within an LPN can be either be split within that LPN. the LPNs will be consolidated when the lot is merged. and the current on-hand quantities of a lot. Lot Attributes The lot attributes of the split lot will be defaulted from the starting lot. if applicable) to a new subinventory and locator. You will specify the lot attributes once. Lot Genealogy Lot genealogy includes an on-line inquiry forms that display parent/child relationships between lots and sublots created during lot splits and lot merges. moving the destination lots (and LPNs. or an LPN generated dynamically. For example. and Suffix (the lot number is displayed after the item number). you can view which supplier and purchase order a component lot came from (transaction type = purchase order receipt) and which 9 . as resulting lots have more of that lot than any other lot. or can be packed in a new LPN when they are split. The transaction region shows where a lot has gone to and/or where a lot come from. Lot Source Genealogy Lot genealogy is displayed in a tree structure that shows all of the ingredients or component lots that have been used in making a particular lot. the resulting LPN is the same as the starting LPN. If two lots of equal quantity are merged. When lots are merged within an LPN. The profile option “INV:Genealogy Prefix or Suffix” determines whether the item number should be displayed along with the lot number in the genealogy tree structure. You may update the defaulted split lot attributes before saving the new lot. you may specify the number of resulting lots or the proper quantity of the resulting lots to automatically create. The three possible settings are None (the item number is not displayed). Lot attributes of a merged lot will be defaulted from the starting lot with the largest quantity. Prefix (the lot number is displayed before the item number). This will allow a batch of 100 pallets to be easily split into 100 sublots of 1 pallet per sublot. A move transaction can also be performed at the same time as lot split or lot merge. you may manually specify the resulting lot numbers and lot quantities.

Oracle WMS 1. lot split. 10 . Splitting lots in third-party systems will be supported through the use of APIs to create the new lots and import the lot splitting transactions.sales orders to which customers (transaction type = sales order issue) or other distribution centers (transaction type = organization transfer) a finished product lot has been shipped to. and populate lot genealogy. System-defined transaction types of Lot Split and Lot Merge have been added to track splitting & merging of lots.0 sublot functionality includes all of the APIs to integrate with 3rd party systems. new lot creation. The following four APIs are provided: completion of assembly/product. Completion of assembly/product and lot split are also supported via a transaction interface. Sublot Third Party Integration Lot split & Lot merge are new Transaction Actions.

7200 Copyright © Oracle Corporation 1995 All Rights Reserved 11 . David Wertheimer Contributing Author: Susan Ellsworth Copyright © Oracle Corporation 2000 All Rights Reserved Printed in the U. Oracle Corporation does not provide any warranties covering and specifically disclaims any liability in connection with this document.S.A. Please report any errors herein to Oracle Corporation.Oracle Warehouse Management Advanced Lot and Serial Control December 2000 Author: Susan Ellsworth.7000 Fax 415. Oracle is a registered trademark.A. Worldwide Inquiries: 415.506. Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores.S.506. CA 94065 U. This document is provided for informational purposes only and the information herein is subject to change without notice.

Sign up to vote on this title
UsefulNot useful