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_IDINV_ORGANIZATION_DEFINITIONS_V

Columns

ColumnKeyIn reportsDescription (inferred)
APPROVAL_DATEApproval date.
APPROVAL_REQUEST_DATEApproval request date.
APPROVAL_STATUS_TYPEType of approval status.
ASSIGNEE_ROLE_IDIdentifier for the assignee role.
BASE_CHANGE_MGMT_TYPE_CODECode identifying the base change mgmt type.
CANCELLATION_DATECancellation date.
CHANGE_IDIdentifier for the change.
CHANGE_NOTICEChange notice.
CHANGE_TYPE_IDIdentifier for the change type.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
IMPLEMENTATION_DATEImplementation date.
INITIATION_DATEInitiation date.
NEED_BY_DATENeed by date.
ORGANIZATION_IDIdentifier for the organization.
PRIORITY_CODECode identifying the priority.
REASON_CODECode identifying the reason.
SOURCE_CODECode identifying the source.
STATUS_CODECode identifying the status.
STATUS_TYPEType 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