bomtrm

MTL_SUPPLY
MTL_SUPPLY stores incoming supply information for an organization.
This table forms one of the sources in Inventory’s Demand–Supply
form. There are four different types of supply captured in this table:
1) Approved Requisitions
2) Approved Purchase orders
3) Shipments from suppliers
4) Intransit shipments from another organization
Types 3 and 4 could be distinguished by the presence of data in the
INTRANSIT_OWNING_ORGANIZATION_ID column, which identifies
the ownership of the items in intransit. If this column is null then it
means that the shipment supply is from a Vendor.
This information is used by the available to promise routine to derive
the ATP information as appropiate. Quantities of items in intransit are
also kept track of in the table.
Records in MTL_SUPPLY are created every time you approve a
requisition or a PO or create an intransit shipment. One record of REQ
type will be created for one requisition line when the requisition is
approved. One record of PO type will be created per PO distribution
when a PO is approved and one record per shipment line will be created
when a shipment is created.
Records in MTL_SUPPLY will be recreated whenever there are
transactions such as return to receiving, return to vendor or cancellation
of purchase orders.
Records in MTL_SUPPLY are deleted every time you change the
document status to not approved. For example, a PO would require
approval if you change the line and shipment quantity. If such a PO is
re–approved then the PO supply will be recreated for the new quantity.
The supply type code of a REQ supply record is changed to PO every
time a requisition is autocreated. Similarly the supply type code is
changed from PO to RECEIVING when a PO is fully received. If a PO is
partially received then a supply with the supply type code of
RECEIVING will be created for the quantity received. When the receipt
is delivered the RECEIVING supply is deleted. SHIPMENT supply
works in the same way as PO supply.
There is a database trigger on MTL_SUPPLY with the name
MTL_SUPPLY_T. This trigger fires on insert, update or deletion of
Oracle Proprietary, Confidential Information––Use Restricted by Contract
Detailed Design
3 – 571