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

EGO_CHANGE_LINES_B

SharedUsed in 7 subject areas19 reporting columns

base table, language-neutral data (paired with _TL labels and the _VL view).

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

Columns

ColumnKeyIn reportsDescription (inferred)
ASSIGNED_DATEAssigned date.
CHANGE_HEADER_IDPK?Identifier for the change header.
CHANGE_IDIdentifier for the change.
CHANGE_LINE_IDPK?Identifier for the change line.
COMPLETE_BEFORE_STATUS_CODECode identifying the complete before status.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
EFFECTIVITY_ON_APPROVAL_FLAGIndicator (Y/N) for the effectivity on approval.
IMPLEMENTATION_DATEImplementation date.
NEED_BY_DATENeed by date.
NEW_ITEM_REVISIONNew item revision.
NEW_REVISION_REASONNew revision reason.
PK1_VALUEPk1 value.
PK2_VALUEPk2 value.
REQUIRED_FLAGIndicator (Y/N) for the required.
SCHEDULED_DATEScheduled date.
SEQUENCE_NUMBERSequence number.
START_AFTER_STATUS_CODECode identifying the start after status.
STATUS_CODECode identifying the status.
SUBJECT_INTERNAL_NAMEName of the subject internal.

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