Analytics Catalog/Data dictionary/PJO_PLAN_LINES
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

PJO_PLAN_LINES

ProjectsUsed in 2 subject areas11 reporting columns

Projects Planning (PJO), line table, one row per line item under the header.

Likely primary key: PLAN_HEADER_ID, LINE_NUMBER (inferred from Oracle naming conventions, verify against Tables & Views)

Columns

ColumnKeyIn reportsDescription (inferred)
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEDate and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGINSession login of the user who last updated the row.
LINE_NUMBERPK?Line number.
PLAN_HEADER_IDPK?Identifier for the plan header.
TC_AVG_STD_BILL_RATETc avg std bill rate.
TC_AVG_STD_BRDND_COST_RATETc avg std brdnd cost rate.
TC_AVG_STD_RAW_COST_RATETc avg std raw cost rate.
TC_BILL_RATE_OVERRIDETc bill rate override.
TC_BRDND_COST_RATE_OVERRIDETc brdnd cost rate override.
TC_RAW_COST_RATE_OVERRIDETc raw cost rate override.

Used by reports

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

Where this surfaces in OTBI

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 PJO_PLAN_LINES?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern