Results for “cc_function_transaction_code”

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

Overview

PA_SYSTEM_LINKAGES is a reference and control table in the Oracle Projects (PA) module of Oracle E-Business Suite. It stores system-defined categories — referred to as system linkages or expenditure type classes — that classify expenditure types and determine how expenditure items assigned to each type are processed by the Projects costing, accounting, and interface engines. Rather than acting as a simple lookup list, the table functions as a central definition point: every expenditure type, transaction source, resource map, and resource transaction attribute references a system linkage function to determine its costing behavior.

Because the table is the authoritative parent for a large number of dependent objects, the heuristic Data Vault classification derived from its foreign-key structure is hub. This is a modeling suggestion: PA_SYSTEM_LINKAGES behaves as a business-key hub whose FUNCTION value is referenced by many downstream satellites and links, including expenditure attributes, allocation rules, and encumbrance group definitions. Note that the table is self-referencing through COST_CREDIT_FUNCTION_CODE, meaning certain rows point back to other rows in the same hub to establish debit/credit pairings.

Key Information Stored

The documented schema contains sixteen columns, of which the following are most significant:

• FUNCTION — The primary business identifier for each system linkage. It forms the single-column primary key constraint PA_SYSTEM_LINKAGES_PK and is the column most commonly used in joins across the Projects schema.
• APPLICATION_ID — Foreign key to FND_APPLICATION, identifying the owning Oracle application context for the linkage.
• MEANING — The user-facing name of the system linkage as displayed in Projects setup windows.
• DESCRIPTION — Free-text explanation of the linkage purpose.
• PROJECT_MANUFACTURING_FLAG — Indicates whether the linkage is valid for project manufacturing flows.
• LABOR_NON_LABOR_FLAG — Distinguishes labor-oriented linkages from non-labor cost categories.
• COST_DEBIT_FUNCTION_CODE and COST_CREDIT_FUNCTION_CODE — Define the debit and credit side functions used during cost accounting. COST_CREDIT_FUNCTION_CODE is also a foreign key back to FUNCTION within this same table.
• COST_JE_CATEGORY_NAME — The journal entry category applied when the linkage is used in accounting.
• CC_FUNCTION_TRANSACTION_CODE — Transaction code associated with cost credit processing.
• ZD_EDITION_NAME — Edition column supporting the editioning model used in the 12.2.x database architecture.

Two unique indexes act as business-key candidates: PA_SYSTEM_LINKAGES_U1 on (FUNCTION, APPLICATION_ID, ZD_EDITION_NAME) and PA_SYSTEM_LINKAGES_U2 on (APPLICATION_ID, MEANING, ZD_EDITION_NAME). The surrogate primary key remains FUNCTION.

Common Use Cases and Queries

Typical uses include validating expenditure type setup, diagnosing costing or accounting errors caused by misconfigured linkages, and building reference reports for Projects configuration reviews.

Resolving an expenditure type to its system linkage:

• SELECT et.expenditure_type, et.system_linkage_function, sl.meaning, sl.cost_je_category_name FROM pa_expenditure_types et, pa_system_linkages sl WHERE et.system_linkage_function = sl.function;

Identifying debit/credit pairings defined within the hub:

• SELECT function, cost_debit_function_code, cost_credit_function_code FROM pa_system_linkages WHERE cost_credit_function_code IS NOT NULL;

Auditing which transaction sources map to which linkage:

• SELECT ts.transaction_source, ts.system_linkage_function, sl.meaning FROM pa_transaction_sources ts, pa_system_linkages sl WHERE ts.system_linkage_function = sl.function;

Related Objects

The following dependent objects are the most operationally significant, based on the documented foreign-key relationships:

• PA_EXPENDITURE_TYPES — joins on SYSTEM_LINKAGE_FUNCTION; the primary consumer of linkage definitions.
• PA_EXPENDITURE_ITEMS_ALL — joins on SYSTEM_LINKAGE_FUNCTION; drives how individual cost transactions are processed.
• PA_EXPENDITURE_GROUPS_ALL — joins on SYSTEM_LINKAGE_FUNCTION; controls which linkages are valid in a given expenditure group.
• PA_EXPEND_TYP_SYS_LINKS — intersects expenditure types and system linkages.
• PA_ALLOC_RULES_ALL — references linkages through TARGET_EXP_TYPE_CLASS and OFFSET_EXP_TYPE_CLASS.
• PA_TRANSACTION_SOURCES — joins on SYSTEM_LINKAGE_FUNCTION to classify incoming transaction streams.
• PA_RESOURCE_MAPS and PA_RESOURCE_TXN_ATTRIBUTES — join on SYSTEM_LINKAGE_FUNCTION to govern resource-level processing.
• PA_PROJECT_ASSIGNMENTS — references EXPENDITURE_TYPE_CLASS.
• GMS_ENCUMBRANCE_GROUPS_ALL — joins on SYSTEM_LINKAGE_FUNCTION in Grants-related encumbrance processing.
• FND_APPLICATION — parent of APPLICATION_ID, defining application ownership.

Together these relationships establish PA_SYSTEM_LINKAGES as a foundational hub whose accurate configuration is prerequisite to correct expenditure processing and cost accounting in Oracle Projects.