[Home] [Help]
[Dependency Information]
| Object Name: | MTL_RTG_ITEM_REVISIONS |
|---|---|
| Object Type: | TABLE |
| Owner: | INV |
| FND Design Data: | INV.MTL_RTG_ITEM_REVISIONS
|
| Subobject Name: | |
| Status: | VALID |
MTL_RTG_ITEM_REVISIONS stores revision levels for routings. When a
routing is defined a revision must be inserted into this table, so
that every routing has at least one valid revision.
.
This table is analagous to MTL_ITEM_REVISIONS, but for routings
instead of items. However, since engineering changes don't yet act on
routings, routing revisions will never come directly from an ECO as
they do for items.
| Tablespace: | APPS_TS_TX_DATA |
|---|---|
| PCT Free: | 10 |
| PCT Used: |
| Index | Type | Uniqueness | Tablespace | Column |
|---|---|---|---|---|
| MTL_RTG_ITEM_REVISIONS_U1 | NORMAL | UNIQUE |
APPS_TS_TX_IDX
|
INVENTORY_ITEM_ID
PROCESS_REVISION
ORGANIZATION_ID
|
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INVENTORY_ITEM_ID | NUMBER | Yes | Inventory item identifier | |
| ORGANIZATION_ID | NUMBER | Yes | Organization identifier | |
| PROCESS_REVISION | VARCHAR2 | (3) | Yes | Routing revision code |
| 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 | ||
| CHANGE_NOTICE | VARCHAR2 | (10) | Engineering change order number | |
| ECN_INITIATION_DATE | DATE | ECO initiation date | ||
| IMPLEMENTATION_DATE | DATE | ECO implementation date | ||
| IMPLEMENTED_SERIAL_NUMBER | VARCHAR2 | (30) | (no longer used) | |
| EFFECTIVITY_DATE | DATE | Yes | Revision effectivity date | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (30) | Descriptive flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive flexfield segment | |
| 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 | ||
| REVISED_ITEM_SEQUENCE_ID | NUMBER | Revised Item Sequence Id |
Cut, paste (and edit) the following text to query this object:
SELECT INVENTORY_ITEM_ID
, ORGANIZATION_ID
, PROCESS_REVISION
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, CREATION_DATE
, CREATED_BY
, LAST_UPDATE_LOGIN
, CHANGE_NOTICE
, ECN_INITIATION_DATE
, IMPLEMENTATION_DATE
, IMPLEMENTED_SERIAL_NUMBER
, EFFECTIVITY_DATE
, ATTRIBUTE_CATEGORY
, ATTRIBUTE1
, ATTRIBUTE2
, ATTRIBUTE3
, ATTRIBUTE4
, ATTRIBUTE5
, ATTRIBUTE6
, ATTRIBUTE7
, ATTRIBUTE8
, ATTRIBUTE9
, ATTRIBUTE10
, ATTRIBUTE11
, ATTRIBUTE12
, ATTRIBUTE13
, ATTRIBUTE14
, ATTRIBUTE15
, REQUEST_ID
, PROGRAM_APPLICATION_ID
, PROGRAM_ID
, PROGRAM_UPDATE_DATE
, REVISED_ITEM_SEQUENCE_ID
FROM INV.MTL_RTG_ITEM_REVISIONS;
INV.MTL_RTG_ITEM_REVISIONS does not reference any database object
INV.MTL_RTG_ITEM_REVISIONS is referenced by following:
APPS
MTL_RTG_ITEM_REVISIONS
|
|
|
|