CST_TRANSACTION_COSTS

CostingUsed in 1 subject areas24 reporting columns

Cost Management (CST).

Likely primary key: TRANSACTION_COST_ID (inferred from Oracle naming conventions — verify against Tables & Views)

Columns

Column	Key	In reports	Description (inferred)
ABSORPTION_TYPE		●	Type of absorption.
ACCOUNTING_STATUS		●	Status of the accounting.
ADJUSTMENT_DATE		●	Adjustment date.
ADJUSTMENT_TRANSACTION_ID		●	Identifier for the adjustment transaction.
COSTING_STATUS		●	Status of the costing.
COST_DATE		●	Cost date.
COST_REFERENCE		●	Cost reference.
COST_SOURCE		●	Cost source.
CREATED_BY		●	User who created the row.
CREATION_DATE		●	Date and time the row was created.
CURRENCY_CODE		●	Code identifying the currency.
EFF_DATE		●	Effective date.
LAST_UPDATED_BY		●	User who last updated the row.
LAST_UPDATE_DATE		●	Date and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGIN		●	Session login of the user who last updated the row.
OVERHEAD_ID		●	Identifier for the overhead.
PAC_PROCESSED_FLAG		●	Indicator (Y/N) for the pac processed.
PERIODIC_COST_ID		●	Identifier for the periodic cost.
PERIOD_NAME		●	Name of the period.
POSTED_FLAG		●	Indicator (Y/N) for the posted.
TRANSACTION_COST_ID	PK?	●	Identifier for the transaction cost.
TRANSACTION_ID		●	Identifier for the transaction.
UNIT_COST		●	Unit cost.
USER_ADJUSTMENT_ID		●	Identifier for the user adjustment.

No cataloged report reads from this table yet — it's part of the broader Fusion dictionary.

The OTBI subject areas that expose this table. You can't join across them in OTBI — the owned conformed model joins them on shared keys.

Need the extract + dbt staging for CST_TRANSACTION_COSTS?

We ship parameterized SQL, BICC config, and dbt models you own.