CST_VARIANCE_COSTS_I_GT
This table is used to temporarily store a subset of the data from cst_variance_costs table for internal processing within the cost processor.
Details
-
Schema: FUSION
-
Object owner: CST
-
Object type: TABLE
-
Tablespace: Default
Primary Key
| Name | Columns |
|---|---|
|
CST_VARIANCE_COSTS_I_GT_PK |
VARIANCE_COST_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| VARIANCE_COST_ID | NUMBER | 18 | Yes | Single column surrogate key: Identifies the variance cost for a transaction | |
| TRANSACTION_ID | NUMBER | 18 | Yes | Single column FK: Identifies the costing transaction. | |
| REC_TRXN_ID | NUMBER | 18 | Yes | Single column FK: Identifies the Receipt Transaction for this transfer transaction | |
| DEP_TRXN_ID | NUMBER | 18 | Yes | Single column FK: Identifies the Deplete Transaction for this transfer transaction | |
| COST_ELEMENT_ID | NUMBER | 18 | Yes | Cost element corresponding to the cost of the transaction. | |
| EXPENSE_POOL_ID | NUMBER | 18 | Yes | Identifies the expense pool for which this cost is created. Indicates the following when negative value: -1: Freight Cost -2: Gain/loss on transfer price -3: Transfer Price -4: Expensed LCM cost element (capitalization flag deselected on mapping setup) -22: Used by internal logic to ignore cost for this node but transfer it to the next node for costing as gain/loss -5: Additional taxes for Brazil. Come on tops of TP. | |
| EFF_DATE | TIMESTAMP | Yes | The effective date of the cost record. It is the date when the cost became in effect for the transaction. For new costs, the effective date is the date stamped on the transaction. For user adjustments, the effective date is the user entry date. For acquisition cost adjustments, the effective date is the system date at time of cost processing. | ||
| TRANSACTION_COST_ID | NUMBER | 18 | Yes | Single key FK: Identifies the transactions cost | |
| COST_ORG_ID | NUMBER | 18 | Yes | Single column FK: Identifies the Cost Organization associated with the inventory organization. | |
| COST_BOOK_ID | NUMBER | 18 | Yes | Single column FK: Identifies the Cost Book assigned to the Cost Organization. | |
| INVENTORY_ITEM_ID | NUMBER | 18 | Yes | Identifies the transactions Inventory Item | |
| VAL_UNIT_ID | NUMBER | 18 | Yes | Single column FK: Identifies the Valuation unit for the transfer transaction. | |
| COST_DATE | TIMESTAMP | Date used for transaction sequencing | |||
| BASE_TXN_TYPE_ID | NUMBER | 18 | Inventory transaction type identifier. For origin as INV the value comes from INV_TRANSACTION_TYPES_TL table. | ||
| COST_SOURCE | VARCHAR2 | 30 | Identifies the source of the cost, such as Purchase Order (PO) or Accounts Payable (AP). The LOOKUP_TYPE for these values is CST_COST_SOURCES. | ||
| COST_REFERENCE | VARCHAR2 | 100 | Identifies a specific business object or value that further refines the cost source information, such as the source cost organization identifier or an effective date. | ||
| COST_TRANSACTION_TYPE | VARCHAR2 | 10 | Cost Transaction Type is used by the costing engine to categorize group processing. Set to 'ADJUST' for adjustments, null otherwise. | ||
| ADDITIONAL_PROCESSING_CODE | VARCHAR2 | 240 | Additional Processing Code is an optional further definition of the Cost Transaction Type. It is used on adjustment transactions (Cost Transaction Type is set to 'ADJUST') and is set to 'USER' when the adjustment was done by the user; otherwise, it is set to null. | ||
| ABSORPTION_TYPE | VARCHAR2 | 30 | Absorption type: 1=Include in Inventory, 2=Expense | ||
| QUANTITY | NUMBER | The transactions quantity in costing unit of measure | |||
| UOM_CODE | VARCHAR2 | 25 | Costing Unit of Measure for the transaction quantity | ||
| UNIT_COST | NUMBER | Current Transaction Cost for a unit quantity | |||
| CURRENCY_CODE | VARCHAR2 | 30 | Yes | Identifies the currency of the transaction / cost. | |
| WO_COST_POSTED_FLAG | VARCHAR2 | 1 | Yes | Indicates if costs related to WIP have been transferred to CST_WORK_ORDER_COSTS. Possible values N - No, Y - Yes, X- Not required. | |
| POSTED_FLAG | VARCHAR2 | 5 | Posted Flag indicating if the distributions are created for this layer. | ||
| DISTRIBUTION_ID | NUMBER | 18 | Single column FK: Identifies the cost distribution header record. | ||
| DISTRIBUTION_TYPE | VARCHAR2 | 30 | Indicates the distribution type. Useful if the same event type may go into different accounting line types; depending on some attribute on the cost. | ||
| 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. | ||
| REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or 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. | ||
| PERIOD_NAME | VARCHAR2 | 15 | Period for which the inventory valuation will be calculated. | ||
| START_DATE | DATE | Start Date of the period for which the inventory valuation will be calculated. | |||
| END_DATE | DATE | End date of the period for which the inventory valuation will be calculated. |
Indexes
| Index | Uniqueness | Columns |
|---|---|---|
| CST_VARIANCE_COSTS_I_GT_U1 | Unique | VARIANCE_COST_ID |