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).

Primary key: not declared here, see Oracle's Tables and Views page for EGO_CHANGE_LINES_B

Columns

ColumnKeyIn reportsDescription (inferred)
ASSIGNED_DATE●Assigned date.
CHANGE_ID●Identifier for the change.
CHANGE_LINE_ID●Identifier for the change line.
COMPLETE_BEFORE_STATUS_CODE●Code identifying the complete before status.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
EFFECTIVITY_ON_APPROVAL_FLAG●Indicator (Y/N) for the effectivity on approval.
IMPLEMENTATION_DATE●Implementation date.
NEED_BY_DATE●Need by date.
NEW_ITEM_REVISION●New item revision.
NEW_REVISION_REASON●New revision reason.
PK1_VALUE●Pk1 value.
PK2_VALUE●Pk2 value.
REQUIRED_FLAG●Indicator (Y/N) for the required.
SCHEDULED_DATE●Scheduled date.
SEQUENCE_NUMBER●Sequence number.
START_AFTER_STATUS_CODE●Code identifying the start after status.
STATUS_CODE●Code identifying the status.
SUBJECT_INTERNAL_NAME●Name 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. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed 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