To define revision, lot, serial, and LPN parameters:

1. Click the Revision, Lot, Serial And LPN tab on the Organization Parameters window.

2. Enter the following data:

   Field Name	Value
   Starting Revision	Enter a starting revision to be the default for each new item.
   Uniqueness	Select an option for lot number uniqueness. Across items: Enforce unique lot numbers for items across all organizations. None: Unique lot numbers are not required.
   Generation	At organization level: The system uses values you enter in the Zero Pad Suffix, Prefix, and Total Length fields to automatically generate a lot number for an item when you receive it. At item level: The system uses the starting lot number prefix and the starting lot number you define in the item master to automatically generate a lot number for an item when you receive it. User Defined: You can define a lot number for an item when you receive it.

3. Enter the following data for lot name generation:

   Field Name	Value
   Zero Pad Suffix	Indicate whether to add zeroes to right-justify the numeric portion of lot numbers.
   Prefix	If At organization level is selected, optionally, enter an alphanumeric lot number prefix for lot numbers generated by the system at the organization level.
   Total Length	Optionally, define the maximum length for lot numbers. Additional Information: When using Oracle Work in Process (WIP): if the WIP parameter is set to default the lot number based on inventory rules, then WIP validates the length of the lot number against the length that you enter in this field.
   Allocate Lot	The Allocate Lot feature enables you to bypass the system allocation to manually allocate lots. For example, with the Allocate Lot feature enabled, an operator has the flexibility to allocate lots that are easier or more convenient to retrieve than those allocated by the system. Attention: For additional flexibility, Oracle Inventory provides an API stub INV_FLEX_LOT_ALLOCATION_PUB that overrides the parameter setting of Yes or No so you can enable or disable the allocate lot feature for a particular source. Select one of the following values: Yes (default value): The system allocates lots during the allocation process. No: Lots will not be allocated even though material will be allocated. If Allocate Lot is set to No, then the Item Details page on the mobile application will simply display the lot field with a LOV where the operator can pick the desired lot and continue the picking process. Also, from the Transact Move Order window, when allocations are created for a move order line, you can review or modify the allocations in the Select Available Inventory window. For more information, see Allocating and Transacting Move Orders. Note: When No is selected, if you try to pick release with auto allocate as Yes, allocations will not be detailed up to the lot level. Restrictions Oracle recommends not enabling the Allocate Lot feature if your system requires lot-level controls that are dependent on specific lots. Otherwise, unwanted issues may arise with lot indivisibility, lot-specific UOM conversions, lot consistency, lot specific rules, and so on. The optional lot allocation feature is not applicable to OPM organizations. The Allocate Lot value of No is not applicable for the process manufacturing (OPM) batch move order auto-detailing process. The system will override this value as Yes and will always allocate the lot for OPM batch auto-detail processing.

4. Enter the following data to generate child lots for lot control at the organization level:

   Field Name	Value
   Child Generation	Select the value for generating child lots: Parent: The system bases the child lot numbers on the same sequence as the lot number. For example, if a parent lot is P1, then the child lot is P2. Parent + Child: The parent lot acts as a prefix, and the system adds the next available number to form the child lot. For example if the parent lot is P1, then the child lot is P1-1.
   Zero Pad	Indicate whether to add zeroes to right-justify the numeric portion of lot numbers.
   Prefix	Enter an alphanumeric prefix if the child lot generation is set to Parent + Child.
   Total Length	Enter the total amount of characters for the child lot. This includes the prefix if applicable.
   Format Validation	Select Format Validation to ensure that manually-entered lots conform to the predetermined naming convention.
   Copy Lot Attributes	Select Copy Lot Attributes to ensure the child lots inherit the parent lot information.

5. Select the desired value for Auto Create Lot UOM Conversion:

   • Yes

   • No

   • User Confirmation

   • Null

   If Yes or User Confirmation is selected, then the system automatically creates lot-specific unit of measure conversions. The system bases the conversion on lot quantities that you receive in the transactional UOM, and creates a conversion between the transactional UOM and the secondary UOM. The system creates a lot conversion only if the item is under dual unit of measure control and the lot conversion is different from the item conversion. For example, a conversion would be created only if the user changes the secondary quantity (or the primary quantity without changing the secondary quantity) so that the conversion between primary and secondary is different from the item level conversion.

   Note: If you enable this parameter, then the system automatically creates lot level UOM conversions for lots that are created in Inventory and Process Manufacturing. It does not automatically create lot-level UOM conversions for lots that are created in Work in Process.

6. Select the value for Allow Different Material Status to control the action that occurs when material statuses differ when you perform transactions (differences in material status of non-lot controlled items are included as well):

   • Yes: You can transfer out of, receive into, or produce material into an existing status and the new quantity inherits the status of the existing material.

   • No: You cannot transfer out of, receive into, or produce material into an existing status.

   • With exception: You can transfer out of, receive into, or produce material into an existing status only if the on-hand balance of the destination organization is zero.

   Default Lot On-hand Status During Organization Transfer Receiving

   When a lot is transferred from one organization to another, if the lot exists in the destination organization, then the onhand/lot status of the lot in destination organization is retained. If the lot does not exist in the destination organization, and the Allow Different Material Status is set to:

   • No or With exception: On-hand/lot status will be transferred from the source organization.

   • Yes: On-hand status defaults from the on-hand status defaulting logic in the destination organization.

   Note: This feature is extended to Intra-Org Transactions like subinventory transfer, and staging transfer.

7. Enter the following data to define serial control parameters:

   Field Name	Value
   Uniqueness	Select the level at which you want to enforce serial number uniqueness for your organization (the levels for serial uniqueness are cumulative): Across organizations: Enforces unique serial numbers throughout all organizations. In addition to the Within organization restrictions, you cannot assign the same serial number to any other item regardless of the organization. For example if you assign SN100 to item A you cannot receive item B with the serial number SN100 in any organization. If you assign Across organizations uniqueness to any organization it restricts the serial generation in all other organizations. If one organization dictates Across organizations, all other organizations must do so. Within inventory model and items: Enables configurations of the same model to be assigned the same serial number as the base model item. For example, this is useful in ATO (assemble-to-order) configurations where you generate a serial number for the base configuration, and need to generate the same serial number for the next configuration of the same model. Within organization: Enforces unique serial numbers within the current organization. In addition to the Within inventory items restrictions, the same serial number cannot exist twice within the same organization. For example, if you assign SN100 to item A, you cannot receive item B with the serial number SN100 in the same organization. You can, however, receive item B with the serial number SN100 in any other organization. Within inventory items: Enforce unique serial numbers for inventory items. After a serial number is assigned to a particular item, you cannot assign the same serial number to the same item regardless of the organization. For example, if you assign serial number SN100 to item A, you cannot assign serial number SN100 to any other instance of item A in any organization. This also includes CTO items derived from base model A. However you could receive item B with serial number SN100 in any organization.
   Generation	Defines the level at which serial control is generated: At item level: Define the starting serial number prefix and the starting serial number when you define the item. At organization level: Define the starting prefix and serial number information for items using the information you enter in the following fields of this window.
   Prefix	Optionally, select an alphanumeric serial number prefix to use for system-generated serial numbers when generation is at the organization level.
   Starting Serial Number	Optionally, enter a starting serial number to use for system-generated serial numbers. If serial number generation is at the organization level, you must enter a starting serial number.
   Allocate Serial Numbers	Select whether the system suggests serial numbers as part of the move order line allocating process. If you select No, then you must manually enter the serial numbers to transact the move order.

   Additional Information: Serial number control for an inventory item is defined on the Item Master window. You can select from No control, Predefined, At inventory receipt, or At sales order issue. For more information, see Setting Up Serial Number Control.

   To define LPN generating options:

If your organization has installed Oracle Warehouse Management, and you are working with a Warehouse Management enabled organization, you can define LPN Generating Options. LPNs must be unique across organizations. Setting the parameters on this tab enables the system to generate LPNs on demand, or through a concurrent request. As long as the number is unique, Oracle Warehouse Management also enables you to generate your own LPNs.

1. Enter the prefix to append to every LPN generated in this organization.

2. Enter the suffix to append to every LPN generated in this organization.

3. Enter the starting number from which LPNs the system generates LPNs.

4. Indicate if a UCC-128 suffix is appended to the LPN.

   To generate LPNs using the Serial Shipping Container Code (SSCC-18) standard:

You can generate LPNs using the 18-digit serial shipping container code (SSCC-18) standard. The SSCC-18 number ensures a unique LPN number for shipping containers across the supply chain. This number is required to generate a UCC-128 shipping label. SSCC-18 or the license plate number appearing on UCC-128 label is also required on outbound ASNs that the system transmits customers. Consequently, it is important that LPNs are generated using SSCC-18 standard within Oracle Warehouse Management. Oracle Shipping Execution refers to this LPN in the outbound ASN. The data structure for the 18-digit number consists of the following:

SSCC-18 Standards

In Oracle Warehouse Management, you can also set up LPN generation parameters to auto-generate LPNs conforming to SSCC-18 standards. To do this, use the LPN Prefix to define the UCC Company Prefix and Extension Digit and enter the value of 18 for the Total Length of the LPN. The serial number is the starting serial number for LPN generation. This system increments this number when it generates LPNs. This number will be padded by leading '0' to generate LPN with the desired length.

LPN generation setup in Oracle Warehouse Management to auto-create LPNs using SSCC-18 standard

The previous table auto-generates LPNs confirming to SSCC-18 standards as follows:

• 012355600000030474

• 012355600000030481

• 012355600000030498

• 012355600000030504

Sometimes, the UCC Application Identifier (AI) for LPN 00 is also added in the LPN prefix and the LPN number with AI is transmitted in EDI messages. In such a case, the LPN length is entered as 20 and the Application Identifier 00 is added to the LPN Prefix. The following example illustrates this type of scenario:

LPN generation setup in WMS to auto-create LPNs using SSCC-18 standard

In the previous table, the system auto-generates LPNs that confirm to SSCC-18 standards as follows:

• 00012355600000030474

• 00012355600000030481

• 00012355600000030498

• 00012355600000030504