Академический Документы
Профессиональный Документы
Культура Документы
ATTRIBUTES
Lot and serial attributes that are used widely across several industries have been added as named columns (e.g. Best
By Date). In addition, forty unnamed lot and forty unnamed serial attributes have been added such that you may
track important information for your industries (e.g. c_attribute1). Different attributes may be tracked for each item,
customized for specific defaulting and validation requirements. The attributes information can be populated any time
new lots or serials are created, such as at Purchase Order receipt, Miscellaneous Receipt, or WIP Completion.
Types of Attributes
Oracle Warehouse Management System will natively store attributes in date, number, and character fields to simplify
extensions you may wish to build on these attributes.
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.g. shipping to customers), while best by date is the
date at which the quality of the lot may degrade. 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. Origination date may be defaulted to the
1
current date upon receipt and overridden to the date of manufacture at the supplier, if applicable. When completing
finished product, this date is the date of manufacturing completion. The re-test date is the date the material needs to
be re-tested to re-verify its quality. You may define an item descriptive flexfield to track how frequently an item
should be re-tested. This item attribute can be used to default the re-test date.
Note that expiration date, the date after which lot should not be used in production or shipped to customers, is
controlled as it has been in past releases by the item attribute. Therefore, expiration date does not behave exactly as
other lot attributes.
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. This information is stored in the D_ATTRIBUTE1 through
D_ATTRIBUTE10 columns on the MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS tables respectively.
Character Attributes
One category of additional lot and serial information to track are characteristics of the lot. Some of these
characteristics may include lot grade, color, country of origin, place of origin, and recycled content.
The following character attributes have been added as named lot attributes:
• color
• country of origin
• date code
• grade
• place of origin (e.g. 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. This information is stored in the C_ATTRIBUTE1 through
C_ATTRIBUTE20 columns on the MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS tables respectively.
Note that the material status may be controlled at the subinventory, locator, lot, or serial level. Therefore, the material
status on the lot or serial number does not behave exactly as other lot or serial attributes. If the material status of the
subinventory or locator is more restrictive than the material status of the lot or serial number, then the material status
of the subinventory or locator will override the material status of the lot or serial number.
Numeric Attributes
Some industries track numerous dimensions and weights of each lot. Up to thirty distinct numeric attributes can be
used for any given lot.
2
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. If the origination date is not specified, the creation date of the lot will be used. The creation date
of the lot is the same as the date the first quantity for the lot is received. Calculating the age in days and storing
enhances the performance when allocation of lots based on their age is performed.
It is recommended for ease of use that the unit of measure attributes (length UOM, thickness UOM, volume UOM,
width UOM) for each of the dimension attributes (length, thickness, volume, width) be implemented together.
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. This information is stored in the N_ATTRIBUTE1 through
N_ATTRIBUTE10 columns on the MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS tables respectively.
Attribute Functionality
Lot and serial attributes is supported when you license the Oracle Warehouse Management product. However, 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.
3
Oracle WMS supports forms and APIs to populate, maintain, and use the lot and serial attributes.
Populate Attributes
Desktop functionality
Lot and serial attributes need to be populated when new lots and serials are created. If desired, the attributes may be
defaulted and/or overridden by the receiver. When you receive against an existing lot, you may view but not update
the attributes of the existing lot. The attributes of the material received will be inherited from the attributes of the pre-
existing lot.
Populating lot and serial attributes are supporting for the following transactions for non-WMS inventory organizations:
purchase order delivery, miscellaneous receipt, WIP completion, work-orderless completion, flow schedule
completion.
Note: Populating lot attributes is only supported in the Lot Entry window of the Miscellaneous Transactions form.
You may find it easier for if you remove the lot field from the Miscellaneous Transaction Lines window using the
folder form functionality.
Mobile functionality
Lot and serial attributes need to be populated when new lots and serials are created. If desired, the attributes may be
defaulted and/or overridden. When you receive against an existing lot, the attributes of the material received will be
inherited from the attributes of the pre-existing lot.
Populating lot and serial attributes are supporting for the following transactions for non-WMS inventory organizations:
receiving delivery transactions and miscellaneous receipt.
Populating lot and serial attributes are supporting for the following transactions for WMS enabled inventory
organizations: inbound receipt (including ASN receipt) and miscellaneous receipt. Note: it is not yet supported that
suppliers may send lot and/or serial attributes on the ASN. The functionality will be enhanced in a future release to
support this.
Note: There are distinct differences between the receiving process for WMS-enabled inventory organizations and
regular inventory organizations. For inventory organizations, lots and serials may not be specified until the delivery
transaction. Therefore, the lot and serial attributes may not be populated until after this time. For WMS-enabled
organizations, this limitation has been lifted. However, the introduction of the LPN functionality changes the business
4
flow substantially. Incoming material is packed into an LPN at receipt. In order to specify the material being packed
into the LPN, the lot and serial numbers are specified at this time. Consequently the lot and serial attributes are
specified at this time. For more information, please refer to the Inbound Topical Essay.
Desktop functionality
The Maintain Lots and Maintain Serial Numbers forms will allow authorized personnel to update lot and serial
attributes. The View Lot Numbers and View Serial Numbers forms will give non-authorized personnel view-only
access to lot and serial attributes. Limiting access is achieved by calling the Lots and Serials forms in query only
mode (using the QUERY_ONLY form function parameter). An audit log of changes to lot and serial attributes is not
stored. However, 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.
Mobile functionality
You may view lot and serial attributes through the mobile Item Inquiry form. If you wish to update a lot or serial
attribute, this maintenance should be performed through the desktop form.
Use Attributes
5
When a lot is split into multiple new lots, the lot attributes of the new lots are defaulted from the starting lot. You
may override the defaulted attributes. When lots are merged into a new lot, the lot attributes of the new lot are
defaulted from the lot attributes of the largest lot merged into the new lot. If two lots of the same quantity are
merged, the lot attributes of the new lot are defaulted from the first starting lot.
Setup
There are two steps to setting up lot and serial attributes. First, the lot and serial contexts must be defined. Contexts
are supported by descriptive flexfields, so the setup is identical to the setup for descriptive flexfields. Next, the
default context must be assigned to item categories and, if appropriate, items. The reason for this step is that
standard descriptive flexfield functionality requires the reference field for the context be on the transaction form. The
item category field is not on the transactions forms. Therefore, this additional piece of functionality was built to drive
the context off of the item category.
Define Context
A context should be defined using the Segments form for descriptive flexfields, where the descriptive flexfield title is
Lot Attribute or Serial Attribute. Different contexts should be defined for each type of item that tracks different
groups of attributes. In addition, since default values are defined at the context level, different defaulting behavior will
require different contexts.
Each context can have up to forty attributes (ten numeric attributes, twenty character attributes, and ten date
attributes). Each attribute must specify which database column the attribute will be stored in; database types of
varchar, number, and date are supported. Each attribute may be required or optional, and can have a default value set
based on any of the defaulting types mentioned earlier. Finally, a value set must be specified for each attribute. The
value set determines the length of the attribute, as well as the type of validation of the date (no validation, independent
validation against a manually defined list of values, or table validation).
6
Note that in 11i, category sets may be enabled to allow items to be assigned to multiple categories within a category
set. You will only be able to select category sets that do not have this feature selected. This is required so that a
unique context when receiving an item may be derived.
Implementation Considerations
Sublot Control
Sublot functionality fundamentally consists of the ability to split and merge lots and to track a lot’s genealogy.
Sublots are created by splitting a single starting lot into multiple resulting lots. Multiple lots can be merged into a
single resulting lot. 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. Production problems or tampering are examples of when a
product recall is required. In a recall situation, 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.
Sublot control can be broken into three primary components: lot splitting, lot merging, and lot genealogy.
Lot Splitting
Lot splitting allows you to split a quantity of material that has been produced together as a single lot. In this case a
sublot might be material produced in same shift, a pallet of material, an ingot of metal, or a roll of paper.
Splitting may also be performed when a portion of a lot now has different characteristics. An example of this might
be that a lot is stored in multiple locations. Something happens to one of the lots in a location which lowers the
quality of the material. That quantity of the lot would be split into a different lot which is assigned the new quality
characteristics.
7
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.g. 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, including all lot splits and merges.
Sublot Features
In some systems, sublots are modeled differently from sublots. In Oracle WMS 1.0, a sublot is a lot that has a
parent/child relationship to another lot. When a lot is split or merged, a parent/child relationship between the two lots
is stored. Modeling sublots as lots enables sublots to have the same depth of functionality that exists for lots. The
parent/child sublot architecture supports an unlimited number of levels. Therefore, a lot may be split numerous times.
Note that a reserved lot cannot be merged.
LPN Support
Both loose and packed material may be split or merged.
8
Lots within an LPN can be either be split within that LPN, or can be packed in a new LPN when they are split. That
new LPN can be either a pre-existing LPN, or an LPN generated dynamically. A move transaction can also be
performed at the same time as lot split or lot merge, moving the destination lots (and LPNs, if applicable) to a new
subinventory and locator.
When lots are merged within an LPN, the resulting LPN is the same as the starting LPN. When lots in different LPNs
are merged, the LPNs will be consolidated when the lot is merged.
Lot Attributes
The lot attributes of the split lot will be defaulted from the starting lot. You may update the defaulted split lot
attributes before saving the new lot.
Lot attributes of a merged lot will be defaulted from the starting lot with the largest quantity, as resulting lots have
more of that lot than any other lot. If two lots of equal quantity are merged, the lot attributes will be defaulted from
the first lot.
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, lot attributes, transaction history of a lot, and the current on-hand quantities of a lot.
9
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.
10
Oracle Warehouse Management Advanced Lot and Serial Control
December 2000
Author: Susan Ellsworth, David Wertheimer
Contributing Author: Susan Ellsworth
Copyright © Oracle Corporation 2000
All Rights Reserved Printed in the U.S.A.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
415.506.7000
Fax 415.506.7200
11