Results for “psb_flex_mapping_sets”

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

Overview

PSB_FLEX_MAPPING_SETS is a table in the PSB (Public Sector Budgeting) product schema of Oracle E-Business Suite, documented as VALID in ETRM for releases 12.1.1 and 12.2.2. The table stores flexfield mapping sets — named configurations that define how source Key Flexfield segment values are translated or aligned to target segment values during budgeting and worksheet processing. Mapping sets give implementers a reusable, named container for segment-level translation rules, allowing a single definition to be applied consistently across worksheets and budgeting cycles rather than redefined per transaction.

The physical schema documents nine columns and a single-column primary key, PSB_FLEX_MAPPING_SETS_PK, defined on FLEX_MAPPING_SET_ID. A unique index, PSB_FLEX_MAPPING_SETS_U1, is also documented on FLEX_MAPPING_SET_ID, indicating the surrogate identifier doubles as the documented business-key candidate. Under the heuristic Data Vault classification mined from the foreign-key structure, this object is hub-leaning: it holds the identity and descriptive attributes of a mapping set, while its detail rows and consuming transactions are modeled separately. In Data Vault terms, PSB_FLEX_MAPPING_SETS is best treated as a hub of mapping-set identities, with PSB_FLEX_MAPPING_SET_VALUES supplying the link or satellite detail that enumerates individual value mappings.

Key Information Stored

The table's most significant columns are:

• FLEX_MAPPING_SET_ID — surrogate primary key and unique business-key candidate; the identifier referenced by dependent tables.
• NAME — the user-facing name of the mapping set, used to select a definition in budgeting setup and worksheet configuration.
• DESCRIPTION — free-text explanation of the mapping set's purpose or scope.
• SET_OF_BOOKS_ID — the ledger context to which the mapping set belongs, scoping the definition to a specific set of books.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing audit and concurrency information.

The table does not store the individual value translations themselves; those reside in the child table. Consequently, PSB_FLEX_MAPPING_SETS functions primarily as a header or definition record, and any query reporting on mapped values must join to PSB_FLEX_MAPPING_SET_VALUES.

Common Use Cases and Queries

Typical scenarios include identifying which mapping sets exist for a ledger, determining which worksheets consume a given mapping set, and auditing who created or last changed a definition. The following patterns illustrate standard access:

• List all mapping sets for a ledger:
  SELECT flex_mapping_set_id, name, description, set_of_books_id FROM psb_flex_mapping_sets WHERE set_of_books_id = :p_sob_id ORDER BY name;
• Retrieve the definition with its detail values:
  SELECT h.flex_mapping_set_id, h.name, d.* FROM psb_flex_mapping_sets h, psb_flex_mapping_set_values d WHERE h.flex_mapping_set_id = d.flex_mapping_set_id AND h.flex_mapping_set_id = :p_id;
• Identify worksheets bound to a mapping set:
  SELECT w.* FROM psb_worksheets w WHERE w.flex_mapping_set_id = :p_id;
• Audit recent changes:
  SELECT flex_mapping_set_id, name, last_updated_by, last_update_date FROM psb_flex_mapping_sets WHERE last_update_date >= :p_from_date;

Reporting is usually driven from the child values table outward, using the header for naming and ledger filtering. Because the primary key is a surrogate, joins should always use FLEX_MAPPING_SET_ID rather than NAME, which is not documented as unique.

Related Objects

The documented foreign-key relationships identify the following significant dependents and references:

• PSB_FLEX_MAPPING_SET_VALUES — child table holding individual mapped segment values; joined on FLEX_MAPPING_SET_ID (PSB_FLEX_MAPPING_SET_VALUES.FLEX_MAPPING_SET_ID references PSB_FLEX_MAPPING_SETS).
• PSB_WORKSHEETS — budgeting worksheets that reference a mapping set via FLEX_MAPPING_SET_ID, establishing which translation rules apply during worksheet activity.

In practice, PSB_FLEX_MAPPING_SETS is also referenced indirectly by budgeting setup and worksheet generation logic within the PSB module, since any process that applies segment translation must first resolve a mapping set identifier. The dependency chain is therefore header to values for definitional detail, and header to worksheets for operational consumption.