Results for “oa_flex_application_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BNE.BNE_FLEX_OVERRIDES is a configuration table owned by the BNE schema (Web Applications Desktop Integrator) in Oracle EBS 12.1.1 and 12.2.2. It stores per-flexfield override settings that control how key flexfield segment values are formatted during desktop integration processes — specifically right-justify and zero-pad behaviors. These overrides ensure that values exported to or imported from ADI/Web ADI spreadsheet interfaces retain consistent display and padding characteristics, which is critical when key flexfield combinations are matched textually.

The table is documented as standalone under heuristic Data Vault classification, meaning it has no foreign key dependencies into other documented tables. In a Data Vault model this would be modeled as a satellite keyed to the flexfield definition it describes, rather than as a hub or link. The absence of FK relationships supports treating each row as an independent attribute set describing formatting behavior for a specific flexfield.

Key Information Stored

The table contains 9 documented columns. The most significant are:

• OA_FLEX_APPLICATION_ID — Identifies the Oracle application (e.g., GL, AP) owning the flexfield. Part of the composite primary key.
• OA_FLEX_CODE — The flexfield code (for example GL# or a descriptive flexfield code) whose formatting is overridden. This is the column most frequently referenced when searching on "oa_flex_code". Part of the composite primary key and the unique key.
• OA_FLEX_NUM — The flexfield structure number, distinguishing multiple structures within the same application and code. Completes the composite primary key.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OA framework to prevent lost updates during concurrent edits.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent modification and session.

The surrogate/business key here is composite: BNE_FLEX_OVERRIDES_PK on (OA_FLEX_APPLICATION_ID, OA_FLEX_CODE, OA_FLEX_NUM). A unique index, BNE_FLEX_OVERRIDES_UK1, covers the same three columns, reinforcing that this triplet is the natural business key. The remaining columns carry audit and concurrency metadata.

Common Use Cases and Queries

Typical scenarios include diagnosing why a key flexfield value appears unpadded in a Web ADI upload, or auditing which flexfields have override formatting enabled before a system copy.

To list overrides for a specific flexfield code:

• SELECT * FROM bne.bne_flex_overrides WHERE oa_flex_code = 'GL#';

To find overrides for an application across all flexfields:

• SELECT oa_flex_code, oa_flex_num, last_updated_by, last_update_date FROM bne.bne_flex_overrides WHERE oa_flex_application_id = :app_id ORDER BY oa_flex_code;

Reporting use cases include generating a configuration inventory of formatting rules as part of upgrade validation, and correlating override rows with ADI layout definitions to explain value truncation or padding discrepancies.

Related Objects

Because the table is classified standalone, it has no documented foreign keys. The following objects are conceptually or functionally related, primarily through the flexfield identity columns shared with the broader flexfield metadata model:

• FND_APPLICATION — joined on OA_FLEX_APPLICATION_ID = APPLICATION_ID to resolve application names.
• FND_ID_FLEXS — key flexfield definitions referenced by OA_FLEX_CODE.
• FND_ID_FLEX_STRUCTURES — structures referenced by OA_FLEX_APPLICATION_ID, OA_FLEX_CODE, OA_FLEX_NUM.
• FND_FLEX_VALUES / FND_FLEX_VALUES_VL — segment values affected by right-justify and zero-pad overrides.
• BNE_LAYOUTS / BNE_INTERFACE_LAYOUTS — Web ADI layout definitions consuming these overrides.
• BNE_GRANTS / BNE_CONTENT_ITEMS — related BNE configuration objects sharing the same schema and WHO audit pattern.