CST_CP_ERRORS
This table holds all the errors for the cost process and is viewed through the cost process review UI. The errors are aggregated by appropriate values, such as currency code, UOM or item, depending on the info required by the user. The Period End Validation flow requires errors captured and persisted at the transaction details level.
Details
-
Schema: FUSION
-
Object owner: CST
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
CST_CP_ERRORS_PK |
CP_ERROR_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| CP_ERROR_ID | NUMBER | 18 | Yes | Unique key identifying a cost process error. | |
| REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row. | ||
| PROCESSOR_NAME | VARCHAR2 | 30 | Yes | Identifies the processor that created the message. This is typically the alternate short name of the LBA (Logical Business Area). RUNC - Cost Process, PREP - Preprocessor, PERP - Perpetual Average Cost Processor, COGS - COGS Recognition Processor, DPROC - Cost Distribution Processor, PE - Period End Validation Process. The LOOKUP_TYPE for these values is CST_PROCESSOR_NAME. | |
| ERROR_CODE | VARCHAR2 | 30 | Yes | Identifies the event that occurred. This value maps to the MESSAGE_NAME column of the FND_MESSAGES table. | |
| COST_ORG_ID | NUMBER | 18 | Single column FK: Identifies the Cost Organization associated with the inventory organization. | ||
| COST_BOOK_ID | NUMBER | 18 | Single column FK: Identifies the Cost Book assigned to the Cost Organization. | ||
| TOKEN1_NAME | VARCHAR2 | 30 | Token name as required by error code message. | ||
| TOKEN1_VALUE | VARCHAR2 | 240 | Token value as required by error code message. For the DATE token data type, the format to use is 'yyyy-mm-dd hh24:mi:ss'. | ||
| TOKEN2_NAME | VARCHAR2 | 30 | Token name as required by error code message. | ||
| TOKEN2_VALUE | VARCHAR2 | 240 | Token value as required by error code message. For the DATE token data type, the format to use is 'yyyy-mm-dd hh24:mi:ss'. | ||
| TOKEN3_NAME | VARCHAR2 | 30 | Token name as required by error code message. | ||
| TOKEN3_VALUE | VARCHAR2 | 240 | Token value as required by error code message. For the DATE token data type, the format to use is 'yyyy-mm-dd hh24:mi:ss'. | ||
| TOKEN4_NAME | VARCHAR2 | 30 | Token name as required by error code message. | ||
| TOKEN4_VALUE | VARCHAR2 | 240 | Token value as required by error code message. For the DATE token data type, the format to use is 'yyyy-mm-dd hh24:mi:ss'. | ||
| TOKEN5_NAME | VARCHAR2 | 30 | Token name as required by error code message. | ||
| TOKEN5_VALUE | VARCHAR2 | 240 | Token value as required by error code message. For the DATE token data type, the format to use is 'yyyy-mm-dd hh24:mi:ss'. | ||
| TOKEN6_NAME | VARCHAR2 | 30 | Token name as required by error code message. | ||
| TOKEN6_VALUE | VARCHAR2 | 240 | Token value as required by error code message. For the DATE token data type, the format to use is 'yyyy-mm-dd hh24:mi:ss'. | ||
| ROW_COUNT | NUMBER | 18 | Yes | Row count, normally 1 but can be summed for large counts or global errors. | |
| RUN_CONTROL | VARCHAR2 | 30 | Yes | Identifies the Run Control used for cost processing. The Run Control is a pointer to the Cost Process parameters table. | |
| MESSAGE_TYPE | VARCHAR2 | 30 | Message type. When used as part of the Cost Process this can be left as null because the Cost Process will automatically derive message types at the end of every run. Other processes using this table but are not part of the Cost Process will need to derive the message type manually. The Message type value is derived from FND_MESSAGES.TYPE based on the error code. | ||
| MESSAGE | VARCHAR2 | 240 | Resolved message text. When used as part of the Cost Process this can be left as null because the Cost Process will automatically resolve messages at the end of every run. Other processes using this table but are not part of the Cost Process will need to resolve the message manually. | ||
| TABLE_NAME | VARCHAR2 | 30 | Identifies the source table from which the error or event was generated. | ||
| SUBPROCESSOR_NAME | VARCHAR2 | 900 | Subprocessor Name. This value is the direct name and not a look up. Used internally and not displayed on a UI. | ||
| ACCOUNTED_DATE | TIMESTAMP | Accounted Date is used by the Period End validation process. | |||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| JOB_DEFINITION_NAME | VARCHAR2 | 100 | Enterprise Service Scheduler: indicates the name of the job that created or last updated the row. | ||
| JOB_DEFINITION_PACKAGE | VARCHAR2 | 900 | Enterprise Service Scheduler: indicates the package name of the job that created or last updated the row. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| CST_CP_ERRORS_N1 | Non Unique | FUSION_TS_TX_DATA | RUN_CONTROL, REQUEST_ID, PROCESSOR_NAME, ERROR_CODE, MESSAGE |
| CST_CP_ERRORS_N2 | Non Unique | FUSION_TS_TX_DATA | COST_ORG_ID, COST_BOOK_ID |
| CST_CP_ERRORS_N3 | Non Unique | FUSION_TS_TX_DATA | REQUEST_ID, MESSAGE |
| CST_CP_ERRORS_N4 | Non Unique | FUSION_TS_TX_DATA | MESSAGE_TYPE |
| CST_CP_ERRORS_N5 | Non Unique | Default | UPPER("RUN_CONTROL") |
| CST_CP_ERRORS_N6 | Non Unique | Default | CREATION_DATE |
| CST_CP_ERRORS_U1 | Unique | FUSION_TS_TX_DATA | CP_ERROR_ID |