Results for “psa_mf_account_mapping_all”

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

Overview

The PSA_MF_ACCOUNT_MAPPING_ALL table resides in the PSA schema and belongs to the Public Sector Financials (PSA) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store Multi-Funds Account Mapping Details, which support the translation or redirection of accounting combinations used in multi-fund (grant, fund, and appropriation) accounting environments. The table is registered as VALID in the ETRM repository and is a standalone object under the heuristic Data Vault classification mined from its foreign key structure. In Data Vault modeling terms, this suggests treating the object as an independent hub or reference table rather than a dependent satellite or link, because it carries its own surrogate identity and does not participate in a documented foreign key relationship to another entity.

Key Information Stored

The documented physical schema contains thirty columns. Among these, the following are the most significant for functional and technical analysis:

• PSA_MF_ACCT_MAP_ID — the surrogate primary key column. This is the unique identifier enforced by the PK_MF_ACCT_MAP_ID constraint.
• PSA_ACCT_MAPPING_ID — documented as the primary key attribute of the PK_MF_ACCT_MAP_ID constraint, making it the primary business identifier used to reference an account mapping definition.
• LOOKUP_TYPE and LOOKUP_CODE — classify the mapping entry, allowing the same structure to serve multiple mapping categories or fund scenarios.
• SOURCE_ACCOUNT and TARGET_ACCOUNT — the core mapping pair; represent the originating account combination and the account combination to which it is redirected.
• ORG_ID — the operating unit identifier, supporting multi-organization (multi-org) security and partitioning of mapping definitions.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the effective date range during which the mapping is valid, enabling historical and future-dated mappings.
• PSA_MF_ACCOUNT_MAPPING_ALL standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide WHO columns for change tracking and auditing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (Descriptive Flexfield) columns, exposed for customer-specific extensions and reporting attributes.

Common Use Cases and Queries

The primary use case is resolving a source account to its target account within a multi-fund environment, typically during Public Sector accounting events, grant accounting, or budgetary fund reallocation. Common reporting patterns include listing active mappings for a specific operating unit and date, and identifying mappings with overlapping or expired effective dates.

Example query to retrieve current mappings for an operating unit:

• SELECT PSA_ACCT_MAPPING_ID, LOOKUP_TYPE, LOOKUP_CODE, SOURCE_ACCOUNT, TARGET_ACCOUNT FROM PSA_MF_ACCOUNT_MAPPING_ALL WHERE ORG_ID = :org_id AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE + 1);

A second pattern joins on the DFF attributes for customer-specific reporting, for example filtering by ATTRIBUTE_CATEGORY to isolate mappings maintained by a particular department. A third pattern audits stale entries where END_DATE_ACTIVE is in the past but the mapping remains referenced by transaction checks.

Related Objects

Because the metadata classifies this table as standalone in the Data Vault sense, no foreign key dependencies are documented on the object itself. Related PSA Multi-Funds objects that typically reference or operate against this mapping include:

• PSA_MF_ACCOUNT_MAPPING_ALL is self-referenced via the PSA_ACCT_MAPPING_ID business key whenever groupings of mapping lines are assembled.
• PSA_MF_ACCOUNT_MAPPING style base views and lookup views that project the active-dated mapping rows for form and concurrent program consumption.
• Public Sector multi-fund accounting validation and substitution logic that consumes SOURCE_ACCOUNT and TARGET_ACCOUNT during journal or budget entry.
• Standard EBS lookup objects keyed by LOOKUP_TYPE and LOOKUP_CODE, which provide the meaning behind the mapping classification codes.
• Organization definition tables referenced by ORG_ID to enforce operating unit security on the mapping definitions.

Any extension or report that relies on Multi-Funds Account Mapping should treat this table as the authoritative persistence source and always apply the effective-date and operating unit filters described above.