VCS_PLANNING_SCH_DETAILS_HIST
Identifies historical data for each collaboration entry per bucket
Details
-
Schema: FUSION
-
Object owner: VCS
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
VCS_PLAN_SCH_DTLS_HST_PK |
ENTRY_DETAIL_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments | Status |
|---|---|---|---|---|---|---|
| ENTRY_DETAIL_ID | NUMBER | 18 | Yes | Primary key indentifying a collaboration entry detail | Active | |
| COLLAB_ENTRY_ID | NUMBER | 18 | Yes | Identifies which collaboration entry the detail belong to | Active | |
| BUCKET_ID | NUMBER | 18 | Yes | ID of the bucket that short circuits period bucket | Active | |
| PUBLISHER_ORDER_TYPE | VARCHAR2 | 32 | Yes | A code representing the type of an order | Active | |
| IS_CURRENT_FLAG | VARCHAR2 | 1 | Yes | A flag that identifies the latest version of a schedule detail for a collaboration entry. | ||
| RECEIVED_DATE | TIMESTAMP | Date received from VCP or uploaded from spreadsheet. | ||||
| PUBLISHED_BY | VARCHAR2 | 64 | The user who published the forecast for this bucket. | |||
| PUBLISHED_DATE | TIMESTAMP | Date available to Supplier in Supplier Portal. | ||||
| COMMIT_DUE_DATE | TIMESTAMP | Date to capture the SLA due date. This will be collab ent SLA days added to the date it was published | ||||
| QUANTITY | NUMBER | Identifies the requested quantity of a bucket | Active | |||
| QUANTITY_UOM | VARCHAR2 | 32 | Identifies the requested quantity UOM of a bucket | Active | ||
| CUMULATIVE_QUANTITY | NUMBER | The total quantity for the current item and all previous quantities within the item forecast. | ||||
| FORECAST_DETAIL_VERSION | NUMBER | 9 | Will track updates to current cycle versions | |||
| COMMIT_DATE | TIMESTAMP | Date the Supplier provided the commit information. This would be updated when we press Push Commits in SP or pass new commit to ABM. | ||||
| COMMITTED_BY | NUMBER | 18 | The party identifier for the user who performed the commit for this bucket. | |||
| COMMITTED_BY_PARTY | VARCHAR2 | 30 | The type of user that performed the commitment. The allowed values in this column are 'ENTERPRISE' or 'SUPPLIER'. | |||
| RESPONSE_QUANTITY | NUMBER | Identifies the response quantity of a bucket | Active | |||
| RESPONSE_QUANTITY_UOM | VARCHAR2 | 32 | Identifies the response quantity UOM of a bucket | Active | ||
| RESPONSE_BUCKET_ID | NUMBER | 18 | The bucket the commit was made against. Could be made against a day, a week or a period. | |||
| CUMULATIVE_RESPONSE_QUANTITY | NUMBER | The total response quantity for the current item and all previous response quantities within the item forecast. | ||||
| DRAFT_SUPPLIER_QUANTITY | NUMBER | Identifies the requested quantity of a bucket entered by the supplier user but not actually commited to. | ||||
| DRAFT_SUPPLIER_QUANTITY_UOM | VARCHAR2 | 32 | Identifies the requested quantity UOM of a bucket | |||
| SUP_DRAFT_QTY_FLAG | VARCHAR2 | 1 | Yes | A flag to identify if the supplier entered a draft commit qty. Valid values are 'Y' or 'N'. The default value should be 'N' | ||
| DRAFT_ENTERPRISE_QUANTITY | NUMBER | Identifies the requested quantity of a bucket entered by the enterprise user but not actually commited to. | ||||
| DRAFT_ENTERPRISE_QUANTITY_UOM | VARCHAR2 | 32 | Identifies the requested quantity UOM of a bucket | |||
| ENT_DRAFT_QTY_FLAG | VARCHAR2 | 1 | Yes | A flag to identify if the enterprise entered a draft commit qty. Valid values are 'Y' or 'N'. The default value should be 'N' | ||
| COMMIT_DETAIL_VERSION | NUMBER | 9 | Will track updates to current cycle versions | |||
| COMMIT_CORRELATION_CODE | VARCHAR2 | 64 | Correlation code that was provided during commit processing that defines what orchestration process the commit was received against. | |||
| COLLAB_SOURCE_ID | NUMBER | 18 | Yes | Identifies which collaboration source the details belong to | Active | |
| BUCKET_INDEX | NUMBER | 8 | Identifies the order of the bucket within the set | |||
| ENT_DRAFT_BUCKET_ID | NUMBER | 18 | The bucket the draft commit was made against. Could be made against a day, a week or a period. | |||
| SUP_DRAFT_BUCKET_ID | NUMBER | 18 | The bucket the draft commit was made against. Could be made against a day, a week or a period. | |||
| PUBLISHED_BY_PARTY | VARCHAR2 | 32 | The type of user that performed forecast publishing. The allowed values in this column are 'ORA_VCS_PLAN_APP_VAL', 'ORA_VCS_ENTERPRISE_VAL', and 'ORA_VCS_SUPPLIER_VAL'. | |||
| DRAFT_SUP_FORECAST_QUANTITY | NUMBER | Identifies the requested forecast quantity of a bucket entered by the supplier user that has not been published yet. | ||||
| DRAFT_SUP_FORECAST_UOM | VARCHAR2 | 32 | Identifies the requested forecast quantity UOM of a bucket entered by the supplier user that has not been published yet. | |||
| DRAFT_ENT_FORECAST_QUANTITY | NUMBER | Identifies the requested forecast quantity of a bucket entered by the enterprise user that has not been published yet. | ||||
| DRAFT_ENT_FORECAST_UOM | VARCHAR2 | 32 | Identifies the requested forecast quantity UOM of a bucket entered by the enterprise user that has not been published yet. | |||
| DRAFT_SUP_FORECAST_BUCKET_ID | NUMBER | 18 | The draft forecast bucket made by supplier user. Could be made against a day, a week or a period. | |||
| DRAFT_ENT_FORECAST_BUCKET_ID | NUMBER | 18 | The draft forecast bucket made by the enterprise user. Could be made against a day, a week or a period. | |||
| STATUS_CODE | VARCHAR2 | 32 | Identifies the current state of the planning schedule time bucket. | |||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | Active | |
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | Active | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | Active | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | Active | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | Active | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | Active | ||
| COLLAB_IDENTITY_ID | NUMBER | 18 | Yes | Provides collab entry identification across multiple publish cycles. | ||
| COMMIT_REASON_CODE | VARCHAR2 | 30 | Abbreviation that identifies the reason the supplier couldn't fulfill their commitment. |
Indexes
| Index | Uniqueness | Tablespace | Columns | Status |
|---|---|---|---|---|
| VCS_PLAN_ENT_DTLS_HST_U1 | Unique | FUSION_TS_TX_IDX | ENTRY_DETAIL_ID | Active |
| VCS_PLAN_SCH_DETAIL_HIST_N1 | Non Unique | Default | COLLAB_ENTRY_ID, BUCKET_ID | |
| VCS_PLAN_SCH_DETAIL_HIST_N2 | Non Unique | Default | COLLAB_SOURCE_ID, BUCKET_ID, IS_CURRENT_FLAG |