Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
TABLE OF CONTENTS
Introduction ................................................................................................................................ 3
Scope ............................................................................................................................................ 3
Serial Number Uniqueness........................................................................................................ 4
Defining Serial Number Control for Items ............................................................................ 5
Serial Number Generation ........................................................................................................ 7
Serial Number Assignments...................................................................................................... 8
Technical Details......................................................................................................................... 9
Serial Number State or Status .............................................................................................. 9
Accepted and Assigned Statuses ........................................................................................ 10
Explanation of MARK_Ids ................................................................................................ 13
Profile option - 'INV: Restrict Receipt of Serials' ........................................................... 13
RMA Receipts for Serial Controlled Items ........................................................................... 14
Inter-org Shipment Creation for Serial Controlled Items .................................................. 15
Technical Details .................................................................................................................. 15
Dropship Receipts for Serial Controlled Items.................................................................... 19
Technical Details .................................................................................................................. 20
Receiving Open Interface support for Serial Controlled Items......................................... 22
Appendix A - List of Tables Used in Serial Numbers Storage And Processing ............. 23
Appendix B - Troubleshooting Some Common Issues...................................................... 25
Appendix C - Shortnames of the Forms Related to Serial Number setup and Entry.... 26
Appendix D - At a glance…. .................................................................................................. 27
INTRODUCTION
A Serial Number is a unique number assigned to each discrete unit of an item that is
stored in inventory. A serial number can also be defined as a set of characters that
uniquely identifies a single unit and can be used for traceability and warranty purposes.
Serial numbers are valuable in quality control, as once a defect is found in the
production of a particular batch of product, the serial number will quickly identify which
units are affected. Serial numbers are also used as a deterrent against theft and
counterfeit products in that serial numbers can be recorded, and stolen or otherwise
irregular goods can be identified.
Oracle Inventory provides complete serial number support for inventory transactions.
Serial number control can be enabled for specific items in inventory. For items under
serial number control, a unique serial numbers is assigned to each individual unit and
thereafter the same serial numbers is referenced each time a material transaction is
performed.
SCOPE
This white paper details the receiving processes for serial controlled items performed via
desktop application. It explains the basic setup involved in using serial numbers and
provides technical details about the serial numbers and serial controlled items and related
receiving processes. It does not discuss Mobile Applications or WMS specific details for
receiving. It also does not discuss the serial number attributes as they are specific to
WMS.
At Receipt: Serial numbers are created and assigned when the item is received into
The serial number control inventory. Thereafter, for any material transaction, serial number for each unit must be
attribute is controlled at provided.
Organization Level, which
means that same item in At sales order issue: Serial numbers are created and assigned when the item is issued
different inventory
(shipped) against a sales order. Serial numbers are then required at ship confirm. If the
organizations can have
item is received back on a Return Material Authorization (RMA), serial numbers are
different serial number
control defined.
required. All other material transactions for this item bypass serial number information.
No control: Serial number control is not established for the item. All material
transactions involving this item bypass serial number information.
The serial number control attribute is controlled at Organization Level, which means
that same item in different inventory organizations can have different serial number
control defined.
The following table presents conditions where certain options can be changed back and
forth:
Dynamic entry at sales order Predefined serial numbers Item has no on–hand
issue quantity
Predefined serial numbers No serial number control Item has no on–hand
quantity
Dynamic entry at inventory Dynamic entry at sales order Item has no on–hand
receipt issue quantity
If Serial Generation is controlled at the Item level, the check for on–hand quantity is
against the sum of on–hand quantities in all child organizations.
Oracle Inventory uses the starting serial number prefix and the starting serial number
specified in the Item window to load the number of predefined serial numbers
requested. Any number of serial numbers can be generated for any item under serial
number control using the Generate Serial Numbers Window.
Receipt or Ship Date - The date on which a material transaction for the serialized unit
was performed. This information is updated when serialzed unit is moved using material
transactions.
Serial State - Oracle Inventory assigns one of the following states to the serialized unit:
Defined but not used, Resides in inventory, Issued out of inventory, or Resides in
intransit.
Location - The organization, subinventory, and locator in which the serialized unit
currently resides. Material transactions update this information when the serialized unit
is transferred.
Revision level - The revision of the item when the serial number was assigned to the
unit.
Lot number - During material transactions, the lot number is specified first and then
the serial number. Oracle Inventory tracks the lot from which a specific serialized unit
originates.
Explanation of MARK_Ids
When a serial number is used
in a transaction, the mark_id MTL_SERIAL_NUMBER table has 3 mark_id fields: GROUP_MARK_ID,
fields get populated as soon
as the user identifies the LINE_MARK_ID, LOT_LINE_MARK_ID. These fields are used to ensure that that
serial number they want to
use.
serial numbers used by one user's session do not become available incorrectly to another
user. Oracle Inventory uses serial number marking and un-marking routines to update
these fields. When these fields are populated, the serial number is ‘locked’ and is not
available for any transactions.
When a serial number is used in a transaction, the mark_id fields get populated as soon
as the user identifies the serial number they want to use. These fields are made NULL or
un-marked, once the transaction is complete, thus ‘locking’ the serial number during its
processing.
There are known issues when some transactions fail to un-mark these fields due to
unexpected termination of the transaction. If the transaction is stuck and can be found
in Pending Transactions or Transaction Summary forms, then deleting the transactions
from the form should un-mark the serial numbers too. But if the related transaction
cannot be found in these forms, then the only way to un-mark these fields then is to
apply a datafix.
When set to Yes, Oracle Inventory does NOT allow receipt of serial numbers that have
a status of 4 – Issued out of Stores.
When this option is checked, the Serial List of Values (LOV), at the time of receipt, will
contain only the valid Serial Numbers that were entered on the RMA Line (Return Lot
and Serial detail form for RMA Line in Order Management). Manual entries are also
validated against the Serial Numbers that were entered on the RMA Line.
For example, if SN100 - SN109 is entered on the RMA Line, the Receiver cannot enter
any Serial Numbers other than SN100 - SN109 (SN100 - SN109 should be valid); if
Serial Number SN200 is entered manually, an error will be displayed.
But if no Serial Numbers are entered on RMA line or Validate Serial Numbers On RMA
Receipts is NOT checked, all the valid serial numbers for the item in that inventory
organization are displayed.
Note: The validation is based on the Serial Numbers entered on the RMA Line, not the
Serial Numbers referenced and Shipped on the corresponding Sales Order Line. There is
no validation for revision, lot, or serial numbers against inventory tables in Order
Management at the time of RMA creation.
In addition to above validation, system also checks the value of profile INV: Restrict
Receipt of Serials and will allow receipt of a serial number in status 4 – Issued out of
Stores only if the value of profile is No.
Technical Details
See Figure 5 for a process flow diagram of the intransit shipment creation.
NOTE: There are other tables used in the process that are not listed here like MMTT,
MTLI etc. Figure 5 shows only those tables that are most relevant to the process being
described.
If the serial numbers do not already exist in the organization, then they are first created
and records inserted in MTL_SERIAL_NUMBERS (MSN) table. The transaction lines
are recorded in MTL_MATERIAL_TRANSACTIONS (MMT) and related serial
numbers transactions are recorded in MTL_UNIT_TRANSACTIONS (MUT). The
status of the serial numbers is updated to “Resides in In-transit” (Status = 5) in MSN.
Please refer to Accepted and Assigned Statuses section for more details about the
serial number status for specific transactions.
Data in RSS is used by Serial Entry form at the time of deliver into inventory to ensure
that same serial numbers are delivered to stores as the ones shipped. If a serial number is
not present in this table for a shipment, it will not show on the Serial Entry form when
delivering the shipment. Once the serial number is delivered into inventory, a serial
transaction is recorded in RCV_SERIAL_TRANSACTIONS (RST) and the serial
number is removed from RSS.
NOTE: To see the serial control setup of the item and intransit shipment receipt
transactions accepted and assigned serial number statuses, please refer to Table 5.
For Direct:
RTI.TRANSACTION_TYPE = ‘SHIP’
RTI.AUTO_TRANSACT_CODE = ‘DELIVER’
The shipment is received and delivered at the same time that it is created in the
destination organization. The header and lines are created in RSH and RSL respectively.
At the same time, receive and deliver transactions are recorded in
RCV_TRANSACTIONS (RT) and RCV_SERIAL_TRANSACTIONS (RST). No
records are populated in RSS, since the serial numbers are delivered directly into the
receiving inventory.
MSNI
MTI
Create inter-org Populate
transfer Interface
tables and
Inventory
call Inv
Transaction
Ship confirm an Transaction
Manager
internal sales order Processor
Populate RCV
Interface and call Create Issue
RCV Txn Transaction
Manager
Receiving
Transaction RTI
Processor
MSNI
MMT
RSH
MUT
RSL
MSN
RSS
RST
Ships To
Supplier Customer
Invoice PO
PO Invoice
Seller
Shipment (Sales Order)
Notification
Drop shipments are created as sales orders in Order Management (indicated as drop
shipments when their source type is entered as ‘External’). The Purchase Release
Concurrent program inserts records in Requisition Interface. Requisition Import
program in Purchasing creates requisition. After requisition is approved, a Purchase
Order is created from it and approved and communicated to the supplier. Supplier
then ships the items to the customer and notifies the seller that goods have been
shipped (via Advanced Shipment Notification) or sends an invoice to seller. Seller
then creates a receipt for the PO, which creates inbound and outbound material
transactions for accounting purposes. Then an invoice is generated to send to the
customer.
In case of drop shipments where item is serial controlled, the serial control level of the
item determines how the serial numbers are processed at the time of inbound (receipt)
and outbound (issue) transactions of the drop shipment.
If the item serial number control is set to ‘Dynamic Entry At Receipt’ or ‘Predefined’,
then when doing an issue transaction, the serial numbers are retrieved from prior receipt
transactions for the same item, warehouse and locator combination. Since no inventory
is maintained for items used for drop shipments, the serial numbers are shipped as soon
as they are received.
If the item serial number control is set to ‘Dynamic Entry At Sales Order Issue’, no
serial numbers are required at the time of receipt entry. At the time of issue transaction,
one serial number per quantity is generated with appropriate prefix defined in the item
setup.
See Figure 6 for a process flow diagram of the Dropship process for serial
controlled items.
NOTE: There are other tables used in the process that are not listed here like
MLN, MTLI etc. Figure 6 shows only those tables that are most relevant to
the process being described.
RTI
MMTT
MSN
Save Dropship PO
Receipt
Receiving MSN
Populate Receiving Transaction
Interface tables and Processor
call Receiving
Populate Populate INV
Transaction Inventory
Receiving Interface and
call INV Txn Transaction
Tables
Manager Processor
Create Receipt
RSH RSL Transaction
(increment inventory)
MMT MUT
RT RST
Is
interface Is this Call OM
No DropshipReceive
populated Return receipt for
for issue a dropship API
PO?
Yes Yes
MMT
Call OM
MUT process_order API to
update the sales
MSNI.PRODUCT_TRANSACTION_ID links to
RTI.INTERFACE_TRANSACTION_ID.
MSNI.PRODUCT_CODE should be ‘RCV’.
See metalink note 301281.1 for sample scripts for inserts into ROI tables for
lot/serial controlled items. Also see metalink note 309896.1 for a list of ROI
sample scripts for various document types and transactions.
MTL_SERIAL_NUMBERS – This table stores the definition and current status of all
serial numbers in Oracle Inventory. These serial numbers are also used in other areas of
Oracle Manufacturing.
The serial generation program populates this table, given the number of serial numbers
to create and the starting number and prefix.
It is possible to have child records in this table without a parent record due to the
autocommit feature of the Serial Number Entry form. Periodic deletion of irrelevant
data from this table is desired.
If a record is present in RSS, but the error still occurs, then check the current
status of the serial number. The serial number must have status of ‘Resides in In-
transit’. See Table 5
If the status is also correct, then verify that the Mark_Id fields are NULL (or –1).
INVTTESR.fmb – Enter Serial Numbers form. This form is called from all transaction
forms that require serial number entry.
INVSLENT.pll – Form Library for serial number entry form INVTTESR.fmb
INVITSNU.fmb – View Serial Numbers form. This form can be used to view the status
of the serial number and its related transactions, if any.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com