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

TABLE: MRP.MRP_GROSS_REQUIREMENTS

Object Details
Object Name: MRP_GROSS_REQUIREMENTS
Object Type: TABLE
Owner: MRP
FND Design Data: TableMRP.MRP_GROSS_REQUIREMENTS
Subobject Name:
Status: VALID


MRP_GROSS_REQUIREMENTS stores the projected gross requirements for a
given item in an MPS, MRP or DRP plan.
.
USING_ASSEMBLY_ITEM_ID stores the item that generated the gross
requirement. For work orders, planned orders and repetitive
schedules, that item will often be a using assembly. For independent
demand, that item will be the same as the INVENTORY_ITEM_ID. For
items with scrap, that item will also be the same as the
INVENTORY_ITEM_ID.
.
USING_ASSEMBLY_DEMAND_DATE stores the date of the demand, or in the
case of rate-based demand, the start date of the demand and
ASSEMBLY_DEMAND_COMP_DATE stores the end date.
.
USING_REQUIREMENTS_QUANTITY stores the quantity of the demand for
discrete demand. USING_REQUIREMENTS_QUANTITY also stores the scrap
quantity of a work order, planned order, purchase order, repetitive
schedule, or purchase requisition. For rate-based demand,
DAILY_DEMAND_RATE stores the daily rate of demand and
USING_REQUIREMENTS_QUANTITY stores the total demand. For rate-based
demand, USING_REQUIREMENTS_QUANTITY will be equal to the number of
work days between ASSEMBLY_DEMAND_COMP_DATE and
USING_ASSEMBLY_DEMAND_DATE (inclusive) multiplied by
DAILY_DEMAND_RATE.
.
ORIGINATION_TYPE identifies the type of demand, and DISPOSITION_ID
identifies the specific entity that generated the demand. For
discrete jobs, DISPOSITION_ID will be a foreign key to
MRP_ITEM_WIP_ENTITIES. For nonstandard jobs, DISPOSITION_ID will be a
foreign key to MRP_WIP_COMPONENTS. For planned orders and recommended
repetitive schedules, DISPOSITION_ID will be a foreign key to
MRP_RECOMMENDATIONS. For independent demand (sales orders, forecasts,
etc), DISPOSITION_ID will be a foreign key to MRP_SCHEDULE_DATES.
DISPOSITION_ID will be a foreign key to MRP_RECOMMENDATIONS for scrap
on a planned orders, repetitive_schedules, discrete jobs, purchase
requisitions, or purchase orders.
.
This table is populated by the Planner.


Storage Details
Tablespace: TablespaceAPPS_TS_TX_DATA
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
MRP_GROSS_REQUIREMENTS_U1 NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnDEMAND_ID
MRP_GROSS_REQUIREMENTS_N1 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnORGANIZATION_ID
ColumnCOMPILE_DESIGNATOR
ColumnINVENTORY_ITEM_ID
ColumnUSING_ASSEMBLY_ITEM_ID
ColumnUSING_ASSEMBLY_DEMAND_DATE
MRP_GROSS_REQUIREMENTS_N2 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnAPPLIED
ColumnCOMPILE_DESIGNATOR
ColumnORGANIZATION_ID
Columns
Name Datatype Length Mandatory Comments
DEMAND_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
USING_ASSEMBLY_ITEM_ID NUMBER
Yes Using assembly item identifier
USING_ASSEMBLY_DEMAND_DATE DATE
Yes Using assembly demand date
USING_REQUIREMENTS_QUANTITY NUMBER
Yes Assembly requirements quantity
ASSEMBLY_DEMAND_COMP_DATE DATE

Using assembly completion date
DEMAND_TYPE NUMBER
Yes Repetitive demand type
ORIGINATION_TYPE NUMBER
Yes Origination type (to add domain)
DISPOSITION_ID NUMBER

Disposition id
DAILY_DEMAND_RATE NUMBER

Daily rate of demand for rate-based
REQUEST_ID NUMBER

Concurrent Who column
RESERVE_QUANTITY NUMBER

Reserved Quantity
PROGRAM_APPLICATION_ID NUMBER

Concurrent Who column
PROGRAM_ID NUMBER

Concurrent Who column
PROGRAM_UPDATE_DATE DATE

Concurrent Who column
SOURCE_ORGANIZATION_ID NUMBER

Not currently used
RESERVATION_ID NUMBER

Not currently used
UPDATED NUMBER

Flag to determine whether add workday modification was applied
STATUS NUMBER

Attribute used for online replanning
APPLIED NUMBER

Attribute used for online replanning
DEMAND_CLASS VARCHAR2 (30)
Not currently used
FIRM_QUANTITY NUMBER

Not currently used
FIRM_DATE DATE

Not currently used
OLD_DEMAND_QUANTITY NUMBER

Not currently used
DEMAND_SCHEDULE_NAME VARCHAR2 (10)
Not currently used
OLD_DEMAND_DATE DATE

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
LENDING_PROJECT_ID NUMBER

lending project id for Payback Demand
LENDING_TASK_ID NUMBER

lending task id for Payback Demand
Query Text

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


SELECT DEMAND_ID
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      INVENTORY_ITEM_ID
,      ORGANIZATION_ID
,      COMPILE_DESIGNATOR
,      USING_ASSEMBLY_ITEM_ID
,      USING_ASSEMBLY_DEMAND_DATE
,      USING_REQUIREMENTS_QUANTITY
,      ASSEMBLY_DEMAND_COMP_DATE
,      DEMAND_TYPE
,      ORIGINATION_TYPE
,      DISPOSITION_ID
,      DAILY_DEMAND_RATE
,      REQUEST_ID
,      RESERVE_QUANTITY
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      SOURCE_ORGANIZATION_ID
,      RESERVATION_ID
,      UPDATED
,      STATUS
,      APPLIED
,      DEMAND_CLASS
,      FIRM_QUANTITY
,      FIRM_DATE
,      OLD_DEMAND_QUANTITY
,      DEMAND_SCHEDULE_NAME
,      OLD_DEMAND_DATE
,      PROJECT_ID
,      TASK_ID
,      PLANNING_GROUP
,      END_ITEM_UNIT_NUMBER
,      LENDING_PROJECT_ID
,      LENDING_TASK_ID
FROM MRP.MRP_GROSS_REQUIREMENTS;

Dependencies

[top of page]

MRP.MRP_GROSS_REQUIREMENTS does not reference any database object

MRP.MRP_GROSS_REQUIREMENTS is referenced by following:

SchemaAPPS
SynonymMRP_GROSS_REQUIREMENTS