PJC_PRJ_ASSETS_ALL

ProjectsUsed in 1 subject areas25 reporting columns

Projects Costing (PJC) — transaction table (rows scoped across all operating units).

Primary key: PROJECT_ASSET_ID

Columns

Column	Key	In reports	Description (inferred)
AMORTIZE_FLAG		●	Indicator (Y/N) for the amortize.
ASSET_DESCRIPTION		●	Description of the asset.
ASSET_NAME		●	Name of the asset.
ASSET_NUMBER		●	Asset number.
ASSET_UNITS		●	Asset units.
BOOK_TYPE_CODE		●	Code identifying the book type.
CAPITAL_HOLD_FLAG		●	Indicator (Y/N) for the capital hold.
CREATED_BY		●	User who created the row.
CREATION_DATE		●	Date and time the row was created.
DATE_PLACED_IN_SERVICE		●	Date placed in service.
DEPRECIATE_FLAG		●	Indicator (Y/N) for the depreciate.
ESTIMATED_ASSET_UNITS		●	Estimated asset units.
ESTIMATED_COST		●	Estimated cost.
ESTIMATED_IN_SERVICE_DATE		●	Estimated in service 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).
MANUFACTURER_NAME		●	Name of the manufacturer.
MODEL_NUMBER		●	Model number.
PM_ASSET_REFERENCE		●	Pm asset reference.
PM_PRODUCT_CODE		●	Code identifying the pm product.
PROJECT_ASSET_ID	PK	●	Identifier for the project asset.
PROJECT_ASSET_TYPE		●	Type of project asset.
REVERSE_FLAG		●	Indicator (Y/N) for the reverse.
SERIAL_NUMBER		●	Serial number.
TAG_NUMBER		●	Tag number.

Change a column here and these are the reports that move with it — the blast radius for any change to PJC_PRJ_ASSETS_ALL.

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 PJC_PRJ_ASSETS_ALL?

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