CST_LAYER_OHCOST_STG_GT
Current transactions and transfers staged for overheads calculations.
Details
-
Schema: FUSION
-
Object owner: CST
-
Object type: TABLE
-
Tablespace: DEFAULT
Primary Key
Name | Columns |
---|---|
CST_LAYER_OHCOST_STG_GT_PK |
TRANSACTION_ID, REC_TRXN_ID, DEP_TRXN_ID, COST_ELEMENT_ID, EXPENSE_POOL_ID, EFF_DATE |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
TRANSACTION_ID | NUMBER | 18 | Yes | Single column FK: Identifies the costing transaction. | |
REC_TRXN_ID | NUMBER | 18 | Yes | Transaction identifier of a receipt transaction. | |
DEP_TRXN_ID | NUMBER | 18 | Yes | Transaction identifier of a depleting 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 column FK: Identifies the transaction cost. | |
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. | ||
INVENTORY_ITEM_ID | NUMBER | 18 | Inventory item identifier associated with cost. | ||
VAL_UNIT_ID | NUMBER | 18 | Valuation unit identifier associated with cost. | ||
COST_DATE | TIMESTAMP | Cost date used for processing transaction. | |||
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. | ||
BASE_TXN_ACTION_ID | NUMBER | 18 | Inventory transaction action identifier. For Origin as INV, the value comes from lookup INV_TRANSACTION_ACTIONS and for Origin as CST the value is from lookup_type CST_BASE_TXN_ACTIONS. | ||
BASE_TXN_SOURCE_TYPE_ID | NUMBER | 18 | Inventory transaction source type identifier. For origin as INV the value comes from INV_TXN_SOURCE_TYPES_TL table, but a custom source type is treated as INVENTORY (value>100 is brought in as 13), and for CST it comes from lookup_type CST_BASE_TXN_SOURCE_TYPES. | ||
COST_TRANSACTION_TYPE | VARCHAR2 | 10 | Cost transaction type is used by the costing engine to categorize group processing. Possible values are ISSUE, RECEIPT or ADJUST. | ||
ADDITIONAL_PROCESSING_CODE | VARCHAR2 | 240 | Code specifying what kind of processing needs to be done. The value is defined in CST_TXN_SOURCE_ACTIONS for the transaction type and is used by cost processors for additional processing. | ||
COST_COMPONENT_CODE | VARCHAR2 | 30 | Identifies the cost component. Values are based on the seeded cost components in the lookup type CST_COMPONENT_CODES. | ||
QUANTITY | NUMBER | Value that identifies the transaction quantity. | |||
UOM_CODE | VARCHAR2 | 25 | Unit of measure for the transaction quantity. | ||
UNIT_COST | NUMBER | Indicates the unit cost of the cost element. | |||
CURRENCY_CODE | VARCHAR2 | 30 | Yes | Identifies the currency of the transaction / cost. | |
ADJUSTMENT_FLAG | VARCHAR2 | 1 | Yes | Identifies if the row represents an adjustment cost being propagated. 'N' - No 'Y' - Yes | |
POSTED_FLAG | VARCHAR2 | 1 | Indicates the processing status of the transaction. Possible values are N-Not processed, Y-Processed, X-Excluded. | ||
REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row. | ||
PERPAVG_COST_ID | NUMBER | 18 | Identifies the perpetual average cost used for this row. | ||
STD_COST_ID | NUMBER | 18 | Identifies the standard cost used for this row. | ||
PERIODIC_COST_ID | NUMBER | 18 | Unique identifier for a periodic average cost row. | ||
COST_METHOD_CODE | VARCHAR2 | 30 | Cost method with which transactions get costed. Value comes from LOOKUP_TYPE CST_COST_METHODS. |
Indexes
Index | Uniqueness | Columns |
---|---|---|
CST_LAYER_OHCOST_STG_GT_U1 | Unique | TRANSACTION_ID, REC_TRXN_ID, DEP_TRXN_ID, COST_ELEMENT_ID, EXPENSE_POOL_ID, EFF_DATE |