CST_CP_PARAMS
Contains the request level parameters for the Cost Process and is the parent table to CST_CP_PARAM_DTLS.
Details
-
Schema: FUSION
-
Object owner: CST
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
Name | Columns |
---|---|
CST_CP_PARAMS_PK |
PARAMS_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
PARAMS_ID | NUMBER | 18 | Yes | The surrogate key that uniquely identifies the row. | |
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. | |
RUN_CONTROL | VARCHAR2 | 30 | Yes | Identifies the Run Control used for cost processing. | |
PREPROCESS_FLAG | VARCHAR2 | 1 | Yes | Indicates if the Pre-processors should be executed as part of the cost process run. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. | |
COST_ADJUSTMENTS_FLAG | VARCHAR2 | 1 | Yes | Indicates if AP Cost Adjustments should be processed. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. | |
PERPETUAL_AVERAGE_COST_FLAG | VARCHAR2 | 1 | Indicates if the Perpetual Average Cost Processor should be executed as part of the cost process run. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. | ||
COST_PROCESSOR_FLAG | VARCHAR2 | 1 | Yes | Indicates if the Cost Processor should be executed as part of the cost process run. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. | |
COGS_RECOGNITION_FLAG | VARCHAR2 | 1 | Yes | Indicates if the COGS Recognition Processor should be executed as part of the cost process run. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. | |
COST_DISTRIBUTION_FLAG | VARCHAR2 | 1 | Yes | Indicates if the Cost Distribution Processor should be executed as part of the cost process run. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. | |
CST_REPORTS_FLAG | VARCHAR2 | 1 | Indicates if the Reporting Logic should be executed as part of the cost process run. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. This option does an incremental build of the daily summarization data. | ||
CST_REBUILD_REPORTS_FLAG | VARCHAR2 | 1 | Indicates if the Reporting Logic should be executed as part of the cost process run. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. This option does a clean and build (rebuild) of the daily summarization data. | ||
COMMIT_LIMIT | NUMBER | 18 | Yes | Identifies the Commit Limit for the cost processing. It is the unit of work to perform before committing the work to the database. | |
MAX_PARALLEL_WORKERS | NUMBER | 9 | The maximum number of parallel workers that the cost processor will submit while processing the transactions. | ||
COLLECT_STATS_FLAG | VARCHAR2 | 1 | Indicates if table statistics should be collected as part of the cost process run. N - No, Y - Yes. There is no LOOKUP_TYPE for these codes. | ||
LAST_RUN_DATE | TIMESTAMP | Identifies the Last Run Date for the Run Control and is the start time of the run. | |||
LAST_REQUEST_ID | NUMBER | 18 | Identifies the Last Request/Process ID for the Run Control that was started. | ||
USER_COMMENT | VARCHAR2 | 240 | Optional user comment or description. | ||
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. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
CST_CP_PARAMS_U1 | Unique | FUSION_TS_TX_DATA | RUN_CONTROL |
CST_CP_PARAMS_U2 | Unique | FUSION_TS_TX_DATA | PARAMS_ID |