Search Results pon_auction_attr_mapping_b

Overview

PON_AUCTION_ATTR_MAPPING_B is a Sourcing (PON) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the mapping between auction attributes and user-defined attributes. It belongs to the Supplier Management project area and supports the configuration layer of Oracle Sourcing auctions, where sourcing administrators define which negotiation attributes are exposed, captured, or transformed during an auction event. Each row represents a single attribute mapping rule tied to a specific auction header and attribute list.

The table is owned by the PON schema and holds 18 documented columns. Its primary unique index, PON_AUCTION_ATTR_MAPPING_U1, is defined on MAPPING_ID, confirming that column as the surrogate primary key. Based on the heuristic Data Vault classification mined from the foreign key structure, this table is modeled as a standalone object rather than a hub, link, or satellite. In practice, its role is closest to a satellite or configuration-driven link, since it carries descriptive mapping attributes that depend on parent auction and attribute list records.

Key Information Stored

The most significant columns capture the mapping definition, its parent auction context, and the attribute being mapped:

• MAPPING_ID — Surrogate primary key enforced by the unique index PON_AUCTION_ATTR_MAPPING_U1.
• AUCTION_HEADER_ID — Foreign key to PON_AUCTION_HEADERS_ALL, identifying the parent auction.
• ATTRIBUTE_LIST_ID — Foreign key to PON_ATTRIBUTE_LISTS, identifying the attribute list being mapped.
• LINE_NUMBER — Ordering reference within the auction or attribute list.
• SECTION_ID — Identifies the auction section to which the mapping applies.
• SEQUENCE_NUMBER — Controls display or processing order.
• MAPPING_TYPE — Classifies the nature of the mapping (for example, response capture or display).
• RESPONSE — Stores response-related mapping behavior.
• CLASS_SCHEME — Classification scheme governing the attribute mapping.
• ATTR_GROUP_ID — Groups related attributes for presentation.
• ATTR_INT_NAME — Internal attribute name used for programmatic resolution.
• DATA_LEVEL_ID — Identifies the data level at which the mapping operates.
• MULTI_ROW_CODE — Indicates whether the attribute supports multiple rows.

Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE — track record provenance and are standard across EBS PON tables.

Common Use Cases and Queries

Typical scenarios include auditing auction attribute configuration, troubleshooting why a user-defined attribute does not appear on a negotiation, and reporting on mapping consistency across auctions. A common query retrieves all mappings for a given auction:

• SELECT m.mapping_id, m.line_number, m.attr_int_name, m.mapping_type, m.multi_row_code FROM pon_auction_attr_mapping_b m WHERE m.auction_header_id = :auction_header_id ORDER BY m.sequence_number;
• Joining to the attribute list to validate configuration: SELECT m.mapping_id, al.attribute_list_id, m.attr_int_name FROM pon_auction_attr_mapping_b m, pon_attribute_lists al WHERE m.attribute_list_id = al.attribute_list_id AND m.auction_header_id = :auction_header_id;
• Detecting duplicate or conflicting mappings by grouping on AUCTION_HEADER_ID, ATTRIBUTE_LIST_ID, and ATTR_INT_NAME.

Related Objects

The table participates in a small but well-defined set of relationships. The most significant related objects are:

• PON_AUCTION_HEADERS_ALL — Parent auction header, joined on AUCTION_HEADER_ID.
• PON_ATTRIBUTE_LISTS — Attribute list definition, joined on ATTRIBUTE_LIST_ID.
• PON_AUCTION_ATTR_MAPPING_TL — Likely translation counterpart for display text.
• PON_AUCTION_ATTRIBUTES — Auction-level attribute definitions interacting with mapping rules.
• PON_ATTRIBUTE_GROUPS — Grouping referenced through ATTR_GROUP_ID.
• PON_AUCTIONS_ALL — Auction master data related through the header.

Because functional APIs in Oracle Sourcing typically operate through the auction header and attribute list entities, direct DML against this table should be avoided; configuration changes should flow through supported Sourcing setup and auction creation flows.