Search Results pf_org_id

Overview

PAY_IN_ARCH_PF_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It resides within the Payroll (PAY) product family and exposes archived Provident Fund (PF) contribution and organizational data captured during Indian payroll processing. The view is classified as VALID in the ETRM metadata, indicating that it is compiled and available for querying in a standard EBS installation.

The view serves as a reporting and integration surface for statutory PF information. Because the underlying PF data is stored as generic action information rows rather than dedicated columns, the view performs the necessary pivoting and joining to present a business-friendly, denormalized result set. This makes it suitable for extracts, reconciliation reports, and downstream interfaces that require PF numbers and associated organization details without needing to interpret PAY_ACTION_INFORMATION directly.

Underlying Base Objects

PAY_IN_ARCH_PF_V is defined over three synonyms and one package function, all documented in the ETRM metadata:

• PAY_ACTION_INFORMATION (synonym) — referenced twice in the view text, as aliases PAI_PA and PAI_AAP.
• PAY_PAYROLL_ACTIONS (synonym, alias PPA) — supplies the payroll action context.
• PAY_ASSIGNMENT_ACTIONS (synonym, alias PAA) — supplies the assignment-level action context.
• FND_PROFILE (package) — invoked as FND_PROFILE.VALUE('PER_BUSINESS_GROUP_ID') to restrict results to the current business group.

The view joins the two PAY_ACTION_INFORMATION instances on action context identifiers and on the shared values of ACTION_INFORMATION1 (contribution period) and ACTION_INFORMATION2 (PF organization ID). It filters PAI_PA rows where ACTION_INFORMATION_CATEGORY equals 'IN_PF_PAY' and PAI_AAP rows where ACTION_INFORMATION_CATEGORY equals 'IN_PF_ASG'. Context types are constrained to 'PA' and 'AAP' respectively, and the payroll action is linked to the assignment action through PAYROLL_ACTION_ID. The DISTINCT keyword eliminates duplicate rows produced by the multi-table join.

Key Columns

• CONTRIBUTION_PERIOD — sourced from PAI_PA.ACTION_INFORMATION1; identifies the PF contribution period.
• PF_ORG_ID — sourced from PAI_PA.ACTION_INFORMATION2; the PF organization identifier.
• PF_ORG_CLASS — sourced from PAI_PA.ACTION_INFORMATION7; the classification of the PF organization.
• PENSION_NUMBER — sourced from PAI_AAP.ACTION_INFORMATION15; the pension number for the assignment.
• PF_NUMBER — sourced from PAI_AAP.ACTION_INFORMATION3; the statutory PF number, which is the column most commonly targeted by the search term "pf_number".
• ORG_NAME — sourced from PAI_PA.ACTION_INFORMATION8; the descriptive name of the PF organization.

Common Use Cases and Queries

Typical uses include PF reconciliation, statutory reporting, and data feeds to external PF trust systems. A representative query retrieving PF numbers by contribution period is:

• SELECT pf_number, pension_number, contribution_period, pf_org_id, org_name FROM apps.pay_in_arch_pf_v WHERE contribution_period = :period;
• SELECT pf_number, org_name FROM apps.pay_in_arch_pf_v WHERE pf_org_class = :class ORDER BY pf_number;

Because the view already resolves the business group via FND_PROFILE and applies DISTINCT, report authors can query it directly without replicating the action information category filters or join logic. For high-volume extracts, restricting by CONTRIBUTION_PERIOD or PF_ORG_ID improves performance.