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

EGO_ENGINEERING_CHANGES_B

SharedUsed in 10 subject areas20 reporting columns

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

Primary key: not yet catalogued for EGO_ENGINEERING_CHANGES_B, reference Oracle Tables & Views guide.
Joins (inferred from key columns): ORGANIZATION_ID → INV_ORGANIZATION_DEFINITIONS_V

Columns

ColumnKeyIn reportsDescription (inferred)
APPROVAL_DATE●Approval date.
APPROVAL_REQUEST_DATE●Approval request date.
APPROVAL_STATUS_TYPE●Type of approval status.
ASSIGNEE_ROLE_ID●Identifier for the assignee role.
BASE_CHANGE_MGMT_TYPE_CODE●Code identifying the base change mgmt type.
CANCELLATION_DATE●Cancellation date.
CHANGE_ID●Identifier for the change.
CHANGE_NOTICE●Change notice.
CHANGE_TYPE_ID●Identifier for the change type.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
IMPLEMENTATION_DATE●Implementation date.
INITIATION_DATE●Initiation date.
NEED_BY_DATE●Need by date.
ORGANIZATION_ID●Identifier for the organization.
PRIORITY_CODE●Code identifying the priority.
REASON_CODE●Code identifying the reason.
SOURCE_CODE●Code identifying the source.
STATUS_CODE●Code identifying the status.
STATUS_TYPE●Type of status.

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_ENGINEERING_CHANGES_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