Search Results bne_mapping_lines_pk

Overview

BNE_MAPPING_LINES is a core configuration table within the BNE (Web Applications Desktop Integrator) product of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. The table stores the definition of individual column mappings that connect abstract interface definitions to concrete content columns. In the Desktop Integrator architecture, mapping headers (held in BNE_MAPPINGS_B) declare the relationship between an interface and a content source, while BNE_MAPPING_LINES carries the row-per-column detail that resolves how each interface column is populated from, or written back to, a corresponding content column.

From a heuristic Data Vault modeling perspective, the foreign key structure indicates that BNE_MAPPING_LINES is best classified as a link entity. It sits between three parent reference tables — BNE_MAPPINGS_B, BNE_INTERFACE_COLS_B, and BNE_CONTENT_COLS_B — and its three-part foreign key pattern (application/code/sequence triplets) is characteristic of an associative table that records the intersection of interface and content metadata.

Key Information Stored

The table is owned by the BNE schema and comprises 17 documented columns in the 12.2.2 physical schema. The most operationally significant columns are:

• APPLICATION_ID, MAPPING_CODE, SEQUENCE_NUM — the composite primary key (BNE_MAPPING_LINES_PK), uniquely identifying each mapping line and anchoring it to its parent mapping definition in BNE_MAPPINGS_B.
• INTERFACE_APP_ID, INTERFACE_CODE, INTERFACE_SEQ_NUM — the triplet that identifies the specific interface column being mapped, referencing BNE_INTERFACE_COLS_B.
• CONTENT_APP_ID, CONTENT_CODE, CONTENT_SEQ_NUM — the triplet that identifies the corresponding content column, referencing BNE_CONTENT_COLS_B.
• DECODE_FLAG — governs whether the mapping value is subject to decode translation when applied.
• OBJECT_VERSION_NUMBER — supports optimistic locking under the Oracle Applications Framework (OAF) row-level concurrency model.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — the standard EBS WHO columns capturing audit and user context.
• ZD_EDITION_NAME — the editioning column introduced in 12.2 for Online Patching, forming part of the unique index BNE_MAPPING_LINES_UK2.

The unique index BNE_MAPPING_LINES_UK2 (APPLICATION_ID, MAPPING_CODE, SEQUENCE_NUM, ZD_EDITION_NAME) is the documented business-key candidate, extending the primary key with the editioning column to support the AD Online Patching architecture.

Common Use Cases and Queries

Administrators and integrators query this table to diagnose why a Web ADI spreadsheet or Desktop Integrator upload fails to populate the correct columns. A typical diagnostic joins the mapping line to its interface and content column definitions:

• Auditing a specific mapping: SELECT INTERFACE_CODE, CONTENT_CODE, DECODE_FLAG FROM BNE_MAPPING_LINES WHERE APPLICATION_ID = :app AND MAPPING_CODE = :code ORDER BY SEQUENCE_NUM;
• Reconciling orphaned mappings by confirming every INTERFACE_SEQ_NUM and CONTENT_SEQ_NUM resolves to a valid parent row.
• Reporting the full mapping configuration to compare interface-to-content alignment across environments after a clone or upgrade.
• Investigating decode behavior by filtering on DECODE_FLAG when values are not translating as expected.

Related Objects

The FK metadata defines the principal dependencies of BNE_MAPPING_LINES:

• BNE_MAPPINGS_B — joined on APPLICATION_ID and MAPPING_CODE; the mapping header that owns each line.
• BNE_INTERFACE_COLS_B — joined on INTERFACE_APP_ID, INTERFACE_CODE, INTERFACE_SEQ_NUM; defines the interface-side column.
• BNE_CONTENT_COLS_B — joined on CONTENT_APP_ID, CONTENT_CODE, CONTENT_SEQ_NUM; defines the content-side column.
• BNE_MAPPINGS_TL — the translated mapping descriptions associated with BNE_MAPPINGS_B.
• BNE_INTERFACE_COLS_TL / BNE_CONTENT_COLS_TL — translated column labels for the respective parents.