Search Results ap_flex_segment_mappings_pk

Overview

The table AP_FLEX_SEGMENT_MAPPINGS_ALL is a configuration table within the Oracle E-Business Suite Payables module (AP). Its primary function is to store user-defined mappings that control the display order of Accounting Flexfield (AFF) segments for a specific operational report. As indicated by the official documentation, this table directly supports the Expense Distribution Detail Report. It enables organizations to customize the sequence in which key accounting segments, such as Company, Cost Center, or Account, appear on this critical financial report, aligning the output with internal review and analysis requirements. The presence of the '_ALL' suffix denotes that it is a multi-organization support table, capable of storing data for multiple operating units within a single installation.

Key Information Stored

The table's structure is designed to link a specific ledger (Set of Books) with a defined segment display sequence. The primary columns include SEGMENT_MAPPING_ID, which uniquely identifies a mapping set, and SET_OF_BOOKS_ID, which links to the GL_SETS_OF_BOOKS table to associate the mapping with a specific ledger. The SEQUENCE column stores the numeric order for a segment mapping entry. While the provided metadata does not list all columns, typical tables of this nature would also include columns to identify the specific flexfield segment (e.g., SEGMENT_NUMBER) and its assigned display position. The primary key constraint, AP_FLEX_SEGMENT_MAPPINGS_PK, is on the SEGMENT_MAPPING_ID column, ensuring the uniqueness of each mapping definition.

Common Use Cases and Queries

The principal use case is the generation of the Expense Distribution Detail Report with a customized segment order. An administrator configures these mappings via the Payables application interface, with the settings persisted in this table. From a reporting and support perspective, common queries involve verifying existing configurations or troubleshooting report output. A typical diagnostic SQL pattern would join to the ledger table to verify mappings for a specific ledger name:

• SELECT sob.name ledgername, afsm.* FROM ap_flex_segment_mappings_all afsm, gl_sets_of_books sob WHERE afsm.set_of_books_id = sob.set_of_books_id AND sob.name = 'US Primary Ledger' ORDER BY afsm.sequence;

Data in this table is typically static, referenced at runtime by the report engine, and is not the target for frequent direct DML operations outside of the standard application setup path.

Related Objects

This table maintains a direct foreign key relationship with a core Financials table, as documented in the provided metadata.

• GL_SETS_OF_BOOKS: The foreign key from AP_FLEX_SEGMENT_MAPPINGS_ALL.SET_OF_BOOKS_ID references GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID. This relationship ties each segment mapping rule to a specific accounting ledger, enforcing data integrity and enabling ledger-specific reporting formats.

While not listed in the excerpt, this table is logically related to the underlying key flexfield structures (FND_FLEX_VALIDATION_TABLES, etc.) and is the definitive source for the segment ordering used by the Expense Distribution Detail Report's concurrent program and its underlying views or packages.