Results for “pa_functions”

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

Overview

PA_FUNCTIONS is a reference table in the Oracle Projects (PA) schema that stores system-defined groupings of related AutoAccounting transactions. Each row defines a distinct "function" — for example, cost distribution, revenue distribution, or invoice generation — for which Oracle Projects derives accounting flexfield combinations automatically. The table therefore acts as the master registry that maps each accounting function to the application and key flexfield context against which AutoAccounting rules are evaluated.

The table carries a documented primary key, PA_FUNCTIONS_PK, defined as (FUNCTION_CODE, APPLICATION_ID). Two unique indexes, PA_FUNCTIONS_U1 (FUNCTION_CODE, APPLICATION_ID, ZD_EDITION_NAME) and PA_FUNCTIONS_U2 (FUNCTION_NAME, APPLICATION_ID, ZD_EDITION_NAME), represent business-key candidates and confirm that function code and function name are each unique within an application. The ETRM metadata classifies this object heuristically as satellite-leaning within a Data Vault model. In practice, PA_FUNCTIONS behaves largely as a reference/lookup table that is the parent of dependent transactional and parameter tables, rather than as a true hub or link; the satellite classification is best treated as a modeling suggestion reflecting its role as descriptive master data rather than a fact or junction entity.

Key Information Stored

The documented column set contains twelve columns. The most operationally significant are:

• FUNCTION_CODE — the business identifier for the AutoAccounting function; part of the primary key and the principal join column to dependent tables.
• APPLICATION_ID — the owning Oracle application; part of the primary key and a foreign key to FND_APPLICATION and to FND_ID_FLEXS.
• FUNCTION_NAME — the user-facing name of the function; a business-key candidate via PA_FUNCTIONS_U2.
• ID_FLEX_CODE — the key flexfield code used for AutoAccounting against this function; combined with APPLICATION_ID this is the join into FND_ID_FLEXS.
• DESCRIPTION — textual explanation of the function's purpose.
• INTERNAL_PRODUCT_CODE — an internal product classification associated with the function.
• ZD_EDITION_NAME — edition discriminator used in the unique indexes, supporting editioned/multi-version data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns tracking who created and last modified each row.

Note that APPLICATION_ID and ID_FLEX_CODE together address FND_ID_FLEXS, which is directly relevant to the user's search term "fnd_id_flexs": PA_FUNCTIONS is one of the tables that resolves a flexfield definition by application and flexfield code.

Common Use Cases and Queries

Typical reporting and diagnostic queries resolve function names for transactions, or trace a function back to its flexfield definition:

• List functions and their flexfield context:

SELECT pf.function_code, pf.function_name, pf.application_id,
       pf.id_flex_code, pf.internal_product_code
FROM   pa_functions pf
WHERE  pf.application_id = :app_id
ORDER  BY pf.function_name;

• Join to FND_ID_FLEXS to retrieve the flexfield definition for each function:

SELECT pf.function_code, pf.function_name, ifx.id_flex_name
FROM   pa_functions pf, fnd_id_flexs ifx
WHERE  pf.application_id  = ifx.application_id
AND    pf.id_flex_code    = ifx.id_flex_code;

• Attribute function-level transactions through PA_FUNCTION_TRANSACTIONS_ALL for AutoAccounting analysis and reconciliation.
• Drive parameter-driven validation by joining PA_FUNCTION_PARAMETERS on FUNCTION_CODE and APPLICATION_ID.

Related Objects

The most significant related objects, per documented foreign keys and dependent relationships, are:

• FND_APPLICATION — joined via PA_FUNCTIONS.APPLICATION_ID; supplies the owning application name.
• FND_ID_FLEXS — joined via APPLICATION_ID and ID_FLEX_CODE; the flexfield definition source relevant to the "fnd_id_flexs" search.
• PA_FUNCTION_PARAMETERS — child table joined on FUNCTION_CODE and APPLICATION_ID; stores function-level parameters.
• PA_FUNCTION_TRANSACTIONS_ALL — child table joined on FUNCTION_CODE and APPLICATION_ID; records transactions processed under each function.
• AutoAccounting rule tables (via the function code) — where derivation rules are configured for each function.

Because PA_FUNCTIONS is referenced by these dependent tables, it must not be modified outside supported Oracle Projects configuration; the FUNCTION_CODE and APPLICATION_ID pair forms the durable business key for all downstream joins.