Search Results bne_mapping_lines_uk2

Overview

BNE.BNE_MAPPING_LINES is a transactional configuration table within the Oracle E-Business Suite (EBS) Application Technology stack, owned by the BNE schema (the same schema that hosts the application framework's content and interface column definitions). Its purpose is to store the individual content column to interface column mappings — that is, the row-level detail that defines how a given content application column is mapped to a corresponding interface application column for a specific mapping definition. Each row represents a single mapping line identified by a mapping code, an application identifier, and a sequence number.

Where the parent tables (BNE_MAPPINGS_B and the content/interface column tables) hold the header-level and dictionary-level information, BNE_MAPPING_LINES holds the pairing itself. It sits at the intersection of content metadata and interface metadata: the CONTENT_APP_ID/CONTENT_CODE/CONTENT_SEQ_NUM triplet identifies the source content column, and the INTERFACE_APP_ID/INTERFACE_CODE/INTERFACE_SEQ_NUM triplet identifies the target interface column.

From a Data Vault modeling perspective (heuristic classification only), this object is best viewed as a link, connecting content-column and interface-column hubs through the mapping definition. It resolves a many-to-many relationship between content columns and interface columns under a given mapping code.

Key Information Stored

The most important columns, as documented, are:

• APPLICATION_ID — Application identifier (foreign key to FND_APPLICATIONS.APPLICATION_ID), scoping the mapping to an application.
• MAPPING_CODE — Code identifying the entity within the given application; the business grouping key for a mapping.
• SEQUENCE_NUM — Sequence number identifying each line within a mapping.
• CONTENT_APP_ID — Application id of the content column being mapped.
• CONTENT_CODE / CONTENT_SEQ_NUM — Content code and sequence of the content column being mapped.
• INTERFACE_APP_ID — Application id of the interface column being mapped.
• INTERFACE_CODE / INTERFACE_SEQ_NUM — Interface code and sequence of the interface column being mapped.
• DECODE_FLAG — Controls whether the content column is decoded via the interface column's 'TABLE' validation query.
• OBJECT_VERSION_NUMBER — Optimistic-locking / version token for the row.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE for auditability.

The primary key is BNE_MAPPING_LINES_PK (APPLICATION_ID, MAPPING_CODE, SEQUENCE_NUM). The unique index BNE_MAPPING_LINES_UK2 is documented (in the 12.2.2 physical schema) as (APPLICATION_ID, MAPPING_CODE, SEQUENCE_NUM, ZD_EDITION_NAME); the ZD_EDITION_NAME component reflects Edition-Based Redefinition (EBR) support in 12.2.x. The composite PK and unique business-key compositions are effectively equivalent except for the edition discriminator.

Common Use Cases and Queries

Typical use cases involve inspecting or troubleshooting content-to-interface column mappings when configuring integrations, interfaces, or data translations. Administrators may query which interface columns a given content column feeds, or validate mapping completeness before running an interface process.

List mapping lines for a given application and mapping code:

• SELECT * FROM BNE.BNE_MAPPING_LINES WHERE APPLICATION_ID = :app AND MAPPING_CODE = :code ORDER BY SEQUENCE_NUM;

Resolve the content and interface column identifiers into human-readable codes by joining to the content and interface column dictionary tables using the CONTENT_* and INTERFACE_* triplets. A reporting scenario might reconcile every mapping line against its parent mapping header in BNE_MAPPINGS_B to confirm the mapping is active and complete. Because the unique index includes ZD_EDITION_NAME in 12.2.x, queries in an EBR-enabled environment should account for edition context.

Related Objects

• BNE.BNE_MAPPINGS_B — referenced by APPLICATION_ID; the mapping header/definition that each line belongs to.
• BNE.BNE_CONTENT_COLS_B — referenced by CONTENT_APP_ID; the dictionary of content columns available for mapping.
• BNE.BNE_INTERFACE_COLS_B — referenced by INTERFACE_APP_ID; the dictionary of interface columns receiving the mapping.
• FND_APPLICATIONS — source of APPLICATION_ID values.
• FND_USER / FND_LOGINS — audit references for the WHO columns.
• BNE_MAPPING_LINES_PK and BNE_MAPPING_LINES_UK2 — the primary and unique indexes governing row identity.