Search Results in_pf_asg

Overview

APPS.PAY_IN_ARCH_PF_V is an Oracle E-Business Suite (EBS) reporting view that consolidates contribution and provident fund (PF) organization information captured during Indian payroll processing. It is defined in the APPS schema and is delivered as part of the Oracle Payroll localization for India. The view reconciles two distinct streams of payroll action information — one recorded at the payroll action level and one recorded at the assignment action level — to produce a single, denormalized result set that pairs PF contribution periods and organization identifiers with the pension and PF numbers belonging to individual assignments.

Because the view abstracts a four-way join across action information and action header tables, it is typically used as a read-only reporting and integration source. It presents payroll-processed PF data in a form suitable for statutory extracts, third-party payroll interfaces, and reconciliation reporting, without requiring the consuming application to understand the underlying action information model.

Underlying Base Objects

The view's text references the following documented base objects, all resolved through APPS synonyms: PAY_ACTION_INFORMATION, PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, and the FND_PROFILE package.

• PAY_ACTION_INFORMATION (aliased PAI_PA and PAI_AAP) — referenced twice. The PAI_PA instance carries rows in the action information category 'IN_PF_PAY' at context type 'PA'; the PAI_AAP instance carries rows in the action information category 'IN_PF_ASG' at context type 'AAP'.
• PAY_PAYROLL_ACTIONS (PPA) — joined on PAYROLL_ACTION_ID to the payroll-level action information and to the assignment actions, and filtered by BUSINESS_GROUP_ID.
• PAY_ASSIGNMENT_ACTIONS (PAA) — joined on ASSIGNMENT_ACTION_ID to the assignment-level action information, and on PAYROLL_ACTION_ID back to the payroll action.
• FND_PROFILE — invoked as FND_PROFILE.VALUE('PER_BUSINESS_GROUP_ID') to restrict the result set to the current session's business group.

The two action information instances are linked by matching ACTION_INFORMATION1 (contribution period) and ACTION_INFORMATION2 (PF organization identifier), which is what allows payroll-level and assignment-level PF attributes to be reported together.

Key Columns

The view exposes six columns, drawn from the two action information instances:

• CONTRIBUTION_PERIOD — sourced from PAI_PA.ACTION_INFORMATION1; identifies the PF contribution period for which the record applies.
• PF_ORG_ID — sourced from PAI_PA.ACTION_INFORMATION2; the identifier of the PF organization or trust.
• PF_ORG_CLASS — sourced from PAI_PA.ACTION_INFORMATION7; the classification of the PF organization.
• PENSION_NUMBER — sourced from PAI_AAP.ACTION_INFORMATION15; the assignment's pension number for the period.
• PF_NUMBER — sourced from PAI_AAP.ACTION_INFORMATION3; the assignment's PF number.
• ORG_NAME — sourced from PAI_PA.ACTION_INFORMATION8; the descriptive name of the PF organization.

The DISTINCT clause removes duplicate rows that would otherwise arise from the multi-table join, ensuring one row per unique combination of the six attributes.

Common Use Cases and Queries

Typical scenarios include producing PF contribution extracts for a given period, validating that assignment-level PF and pension numbers are consistent with the payroll-level PF organization, and feeding downstream statutory or third-party reporting. A representative query is:

• SELECT contribution_period, pf_org_id, org_name, pf_org_class, pf_number, pension_number FROM apps.pay_in_arch_pf_v WHERE contribution_period = :period ORDER BY pf_org_id, pf_number;
• SELECT pf_org_id, org_name, COUNT(DISTINCT pf_number) FROM apps.pay_in_arch_pf_v GROUP BY pf_org_id, org_name;

Because the view filters on FND_PROFILE.VALUE('PER_BUSINESS_GROUP_ID'), results are automatically scoped to the business group of the responsible user; queries submitted in a different business group context will return no rows.