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: MRP.MRP_ITEM_PURCHASE_ORDERS

Object Details

Object Name:	MRP_ITEM_PURCHASE_ORDERS
Object Type:	TABLE
Owner:	MRP
FND Design Data:	MRP.MRP_ITEM_PURCHASE_ORDERS
Subobject Name:
Status:	VALID

MRP_ITEM_PURCHASE_ORDERS stores a copy of all active purchase orders,
purchase requisitions, purchase orders in receiving, intransit
shipments, or intransit receipts. Each entry in the table represents
exactly one of these five entities.
.
PURCHASE_ORDER_ID is a foreign key to the PO_HEADER_ID in
PO_PO_SUPPLY_VIEW for purchase orders. PURCHASE_ORDER_ID is a foreign
key to REQUISITION_HEADER_ID in PO_REQ_SUPPLY_VIEW for purchase
requisitions. PURCHASE_ORDER_ID is a foreign key to PO_HEADER_ID in
PO_RCV_SUPPLY_VIEW for purchase orders in receiving.
PURCHASE_ORDER_ID is a foreign key to SHIPMENT_HEADER_ID in
PO_SHIP_SUPPLY_VIEW for intransit shipments. PURCHASE_ORDER_ID is a
foreign key to SHIPMENT_HEADER_ID in PO_SHIP_RCV_SUPPLY_VIEW for
intransit receipts. UOM_CODE is the unit of measure for the purchase
order line, as defined in purchasing. PO_UOM_DELIVERY_BALANCE is the
outstanding balance of the purchase order, expressed in the unit of
measure of the line on the purchase order.
.
DELIVERY_NEED_DATE is the date the shipment is expected on the dock,
while DELIVERY_SCHEDULE_DATE is the date the order is due to be
available in stores. The difference between DELIVERY_SCHEDULE_DATE
and DELIVERY_NEED_DATE is the item's postprocessing lead time. These
dates must be valid workdates. If the purchase order, purchase
requisition or purchase order in receiving actually has non-valid
workdates for these values, the Snapshot will adjust these to the next
valid workdate.
.
This table is populated by the Snapshot, and is used by the Planner.
This table is derived mainly from PO_PO_SUPPLY_VIEW for purchase
orders, PO_REQ_SUPPLY_VIEW for purchase requisitions,
PO_RCV_SUPPLY_VIEW for purchase orders in receiving,
PO_SHIP_SUPPLY_VIEW for intransit shipments, and
PO_SHIP_RCV_SUPPLY_VIEW for intransit receipts.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
MRP_ITEM_PURCHASE_ORDERS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	TRANSACTION_ID
MRP_ITEM_PURCHASE_ORDERS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	INVENTORY_ITEM_ID COMPILE_DESIGNATOR ORGANIZATION_ID
MRP_ITEM_PURCHASE_ORDERS_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PURCHASE_ORDER_ID COMPILE_DESIGNATOR INVENTORY_ITEM_ID ORDER_TYPE ORGANIZATION_ID PURCH_LINE_NUM
MRP_ITEM_PURCHASE_ORDERS_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	VENDOR_ID

Columns

Name	Datatype	Length	Mandatory	Comments
TRANSACTION_ID	NUMBER		Yes	Unique identifier
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
LAST_UPDATED_BY	NUMBER		Yes	Standard Who column
CREATION_DATE	DATE		Yes	Standard Who column
CREATED_BY	NUMBER		Yes	Standard Who column
LAST_UPDATE_LOGIN	NUMBER			Standard Who column
INVENTORY_ITEM_ID	NUMBER		Yes	Inventory item identifier
ORGANIZATION_ID	NUMBER		Yes	Organization identifier
COMPILE_DESIGNATOR	VARCHAR2	(10)	Yes	MPS, MRP or DRP plan identifier
PURCHASE_ORDER_ID	NUMBER		Yes	Purchase order identifier
SOURCE_ORGANIZATION_ID	NUMBER			The source organization for transfers.
VENDOR_ID	NUMBER			Purchase order supplier identifier
VENDOR_SITE_ID	NUMBER			Purchase order supplier site identifier
ORDER_TYPE	NUMBER		Yes	Purchase order type code
DELIVERY_SCHEDULE_DATE	DATE		Yes	Date order is available in stores
PO_NUMBER	VARCHAR2	(60)		Purchase order number
DELIVERY_BALANCE	NUMBER		Yes	Purchase order schedule quantity
EXPECTED_SCRAP_QUANTITY	NUMBER		Yes	Expected scrap quantity
UOM_CODE	VARCHAR2	(3)	Yes	Unit of measure code
PO_UOM_DELIVERY_BALANCE	NUMBER		Yes	Outstanding quantity with the UOM of the purchase order
DELIVERY_PRICE	NUMBER			Purchase order price
DELIVERY_STATUS_TYPE	NUMBER			Purchase order status code
PURCH_LINE_NUM	NUMBER		Yes	Purchase order line number
LINE_ID	NUMBER		Yes	Line identifier
FIRM_PLANNED_STATUS_TYPE	NUMBER			Flag to indicate if the purchase order is firmed
DELIVERY_NEED_DATE	DATE			Order dock date
REVISION	VARCHAR2	(3)		UOM of the purchase order line
PRINT_DATE	DATE			Date the order was printed
RECEIVING_DOCUMENT_DESIGNATOR	VARCHAR2	(10)		Receipt document
REQUEST_ID	NUMBER			Concurrent Who column
PROGRAM_APPLICATION_ID	NUMBER			Concurrent Who column
PROGRAM_ID	NUMBER			Concurrent Who column
PROGRAM_UPDATE_DATE	DATE			Concurrent Who column
DEMAND_CLASS	VARCHAR2	(30)		Not currently used
PROJECT_ID	NUMBER	(15)		Project identifier
TASK_ID	NUMBER	(15)		Task identifier
PLANNING_GROUP	VARCHAR2	(30)		Planning group
END_ITEM_UNIT_NUMBER	VARCHAR2	(30)		Unit number

Query Text

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


SELECT TRANSACTION_ID
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      INVENTORY_ITEM_ID
,      ORGANIZATION_ID
,      COMPILE_DESIGNATOR
,      PURCHASE_ORDER_ID
,      SOURCE_ORGANIZATION_ID
,      VENDOR_ID
,      VENDOR_SITE_ID
,      ORDER_TYPE
,      DELIVERY_SCHEDULE_DATE
,      PO_NUMBER
,      DELIVERY_BALANCE
,      EXPECTED_SCRAP_QUANTITY
,      UOM_CODE
,      PO_UOM_DELIVERY_BALANCE
,      DELIVERY_PRICE
,      DELIVERY_STATUS_TYPE
,      PURCH_LINE_NUM
,      LINE_ID
,      FIRM_PLANNED_STATUS_TYPE
,      DELIVERY_NEED_DATE
,      REVISION
,      PRINT_DATE
,      RECEIVING_DOCUMENT_DESIGNATOR
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      DEMAND_CLASS
,      PROJECT_ID
,      TASK_ID
,      PLANNING_GROUP
,      END_ITEM_UNIT_NUMBER
FROM MRP.MRP_ITEM_PURCHASE_ORDERS;

Dependencies

[top of page]

MRP.MRP_ITEM_PURCHASE_ORDERS does not reference any database object

MRP.MRP_ITEM_PURCHASE_ORDERS is referenced by following:

MRP: MRP_ITEM_PURCHASE_ORDERS#