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_PENDING_ENG_CHANGES

Object Details

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

Not Currently Used.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
MRP_PENDING_ENG_CHANGES_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	ECN_ID
MRP_PENDING_ENG_CHANGES_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	ORGANIZATION_ID COMPILE_DESIGNATOR ENG_CHANGE_USING_ASSY_ID INVENTORY_ITEM_ID CHANGE_NOTICE OPERATION_SEQ_NUM

Columns

Name	Datatype	Length	Mandatory	Comments
ECN_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
CHANGE_NOTICE	VARCHAR2	(10)	Yes	Engineering change notice code
ENG_CHANGE_USING_ASSY_ID	NUMBER			Engineering change using assembly
OPERATION_SEQ_NUM	NUMBER			Manufacturing operation sequence number
ENGINEERING_CHANGE_TYPE	NUMBER		Yes	Pending engineering change code
REVISION	VARCHAR2	(3)		Inventory item revision code
OPTIONAL_COMPONENT	NUMBER		Yes	Flag to indicate whether or not this component is an optional component (for ATO purposes)
EFFECTIVITY_DATE	DATE		Yes	Expected implementation date
SUGGESTED_EFFECTIVITY_DATE	DATE			Use up date if USE_UP_CODE is 1
OLD_EFFECTIVITY_DATE	DATE		Yes	Old effectivity date
DRIVING_ITEM_ID	NUMBER			Item whose inventory use up date will drive the suggested effective date of the ECO
USE_UP_CODE	NUMBER		Yes	ECO use up code
REMAINING_IMPL_UNITS	NUMBER			Current remaining implementation units
ABSOLUTE_QUANTITY	NUMBER		Yes	New usage quantity
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
WIP_SUPPLY_TYPE	NUMBER			WIP supply type code
OPERATION_OFFSET_PERCENT	NUMBER			Operation offset percent

Query Text

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


SELECT ECN_ID
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      INVENTORY_ITEM_ID
,      ORGANIZATION_ID
,      COMPILE_DESIGNATOR
,      CHANGE_NOTICE
,      ENG_CHANGE_USING_ASSY_ID
,      OPERATION_SEQ_NUM
,      ENGINEERING_CHANGE_TYPE
,      REVISION
,      OPTIONAL_COMPONENT
,      EFFECTIVITY_DATE
,      SUGGESTED_EFFECTIVITY_DATE
,      OLD_EFFECTIVITY_DATE
,      DRIVING_ITEM_ID
,      USE_UP_CODE
,      REMAINING_IMPL_UNITS
,      ABSOLUTE_QUANTITY
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      WIP_SUPPLY_TYPE
,      OPERATION_OFFSET_PERCENT
FROM MRP.MRP_PENDING_ENG_CHANGES;

Dependencies

[top of page]

MRP.MRP_PENDING_ENG_CHANGES does not reference any database object

MRP.MRP_PENDING_ENG_CHANGES is referenced by following:

APPS: MRP_PENDING_ENG_CHANGES