eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: INV.MTL_SUPPLY

Object Details

Object Name:	MTL_SUPPLY
Object Type:	TABLE
Owner:	INV
FND Design Data:	INV.MTL_SUPPLY
Subobject Name:
Status:	VALID

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 records in
MTL_SUPPLY. It inserts records into MRP_RELIEF_INTERFACE table.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
MTL_SUPPLY_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	SUPPLY_SOURCE_ID SUPPLY_TYPE_CODE
MTL_SUPPLY_N10	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	CHANGE_FLAG
MTL_SUPPLY_N11	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	ITEM_ID TO_ORGANIZATION_ID SUPPLY_TYPE_CODE DESTINATION_TYPE_CODE
MTL_SUPPLY_N12	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	MRP_TO_ORGANIZATION_ID ITEM_ID SUPPLY_TYPE_CODE DESTINATION_TYPE_CODE
MTL_SUPPLY_N13	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	FROM_ORGANIZATION_ID
MTL_SUPPLY_N14	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	RCV_TRANSACTION_ID
MTL_SUPPLY_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PO_DISTRIBUTION_ID
MTL_SUPPLY_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PO_LINE_LOCATION_ID
MTL_SUPPLY_N4	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PO_LINE_ID
MTL_SUPPLY_N5	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PO_HEADER_ID
MTL_SUPPLY_N6	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PO_RELEASE_ID
MTL_SUPPLY_N7	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	REQ_HEADER_ID
MTL_SUPPLY_N8	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	REQ_LINE_ID
MTL_SUPPLY_N9	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	SHIPMENT_HEADER_ID

Columns

Name	Datatype	Length	Mandatory	Comments
SUPPLY_TYPE_CODE	VARCHAR2	(25)	Yes	Supply type code
SUPPLY_SOURCE_ID	NUMBER		Yes	REQ_HEADER_ID, PO_DISTRIBUTION_ID, SHIPMENT_LINE_ID or RCV_TRANSACTION_ID depending on SUPPLY_TYPE_CODE
LAST_UPDATED_BY	NUMBER		Yes	Standard Who column
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
LAST_UPDATE_LOGIN	NUMBER			Standard Who column
CREATED_BY	NUMBER			Standard Who column
CREATION_DATE	DATE			Standard Who column
REQUEST_ID	NUMBER			Standard Who column
PROGRAM_APPLICATION_ID	NUMBER			Standard Who column
PROGRAM_ID	NUMBER			Standard Who column
PROGRAM_UPDATE_DATE	DATE			Standard Who column
REQ_HEADER_ID	NUMBER			Requistion header identifier
REQ_LINE_ID	NUMBER			Requistion line identifier
PO_HEADER_ID	NUMBER			Purchase order header identifier
PO_RELEASE_ID	NUMBER			Purchase order release identifier
PO_LINE_ID	NUMBER			Purchase order line identifier
PO_LINE_LOCATION_ID	NUMBER			Purchase order line location identifier
PO_DISTRIBUTION_ID	NUMBER			Purchase order distribution Identifier
SHIPMENT_HEADER_ID	NUMBER			Shipment header identifier
SHIPMENT_LINE_ID	NUMBER			Shipment line identifier
RCV_TRANSACTION_ID	NUMBER			Receiving transaction identifier
ITEM_ID	NUMBER			Item identifier
ITEM_REVISION	VARCHAR2	(3)		Inventory item revision
CATEGORY_ID	NUMBER			Item category identifier
QUANTITY	NUMBER		Yes	Actual supply quantity
UNIT_OF_MEASURE	VARCHAR2	(25)	Yes	Unit of measure for actual supply quantity
TO_ORG_PRIMARY_QUANTITY	NUMBER			Supply quantity in terms of primary unit of measure of item in destination organization
TO_ORG_PRIMARY_UOM	VARCHAR2	(25)		Primary unit of measure of item in destination organization
RECEIPT_DATE	DATE			Expected or actual receipt date depending on supply type
NEED_BY_DATE	DATE			Original need by date
EXPECTED_DELIVERY_DATE	DATE			Expected delivery date (receipt Date + post-processing lead time for MFG)
DESTINATION_TYPE_CODE	VARCHAR2	(25)	Yes	Destination type (expense location, WIP jobs or inventory)
LOCATION_ID	NUMBER			Location identifier within receiving/inspection
FROM_ORGANIZATION_ID	NUMBER			Sending organization identifier for interorg shipment
FROM_SUBINVENTORY	VARCHAR2	(10)		Sending subinventory for interorg shipment
TO_ORGANIZATION_ID	NUMBER			Destination organization identifier
TO_SUBINVENTORY	VARCHAR2	(10)		Destination subinventory
INTRANSIT_OWNING_ORG_ID	NUMBER			Owner organization identifier for interorg shipment
MRP_PRIMARY_QUANTITY	NUMBER			MRP processed quantity in term of primary UOM of item in destination organization
MRP_PRIMARY_UOM	VARCHAR2	(25)		MRP processed primary UOM of item in destination organization
MRP_EXPECTED_DELIVERY_DATE	DATE			MRP's current expected delivery date
MRP_DESTINATION_TYPE_CODE	VARCHAR2	(25)		MRP's current destination type (Destination Type change between REQs and POs)
MRP_TO_ORGANIZATION_ID	NUMBER			MRP's current destination organization (destination org can be changed prior to receipt)
MRP_TO_SUBINVENTORY	VARCHAR2	(10)		MRP's current destination subinventory (destination sub can be changed until a delivery is made)
CHANGE_FLAG	VARCHAR2	(1)		Flag for marking records to be processed by Supply Update function
CHANGE_TYPE	VARCHAR2	(25)		Change type to indicate changes to ignore for MRP
COST_GROUP_ID	NUMBER			Cost group id to which inventory belongs
EXCLUDE_FROM_PLANNING	VARCHAR2	(1)		Exclude from planning for CLM POs

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT SUPPLY_TYPE_CODE
,      SUPPLY_SOURCE_ID
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      CREATED_BY
,      CREATION_DATE
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      REQ_HEADER_ID
,      REQ_LINE_ID
,      PO_HEADER_ID
,      PO_RELEASE_ID
,      PO_LINE_ID
,      PO_LINE_LOCATION_ID
,      PO_DISTRIBUTION_ID
,      SHIPMENT_HEADER_ID
,      SHIPMENT_LINE_ID
,      RCV_TRANSACTION_ID
,      ITEM_ID
,      ITEM_REVISION
,      CATEGORY_ID
,      QUANTITY
,      UNIT_OF_MEASURE
,      TO_ORG_PRIMARY_QUANTITY
,      TO_ORG_PRIMARY_UOM
,      RECEIPT_DATE
,      NEED_BY_DATE
,      EXPECTED_DELIVERY_DATE
,      DESTINATION_TYPE_CODE
,      LOCATION_ID
,      FROM_ORGANIZATION_ID
,      FROM_SUBINVENTORY
,      TO_ORGANIZATION_ID
,      TO_SUBINVENTORY
,      INTRANSIT_OWNING_ORG_ID
,      MRP_PRIMARY_QUANTITY
,      MRP_PRIMARY_UOM
,      MRP_EXPECTED_DELIVERY_DATE
,      MRP_DESTINATION_TYPE_CODE
,      MRP_TO_ORGANIZATION_ID
,      MRP_TO_SUBINVENTORY
,      CHANGE_FLAG
,      CHANGE_TYPE
,      COST_GROUP_ID
,      EXCLUDE_FROM_PLANNING
FROM INV.MTL_SUPPLY;

Dependencies

[top of page]

INV.MTL_SUPPLY does not reference any database object

INV.MTL_SUPPLY is referenced by following:

INV: MTL_SUPPLY#