Search Results per_bf_payment_details




Overview
Explore in AI Chat

Overview

The PER_BF_PAYMENT_DETAILS table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically designed to support integrations with third-party payroll providers. Its primary function is to serve as a detailed audit and reconciliation log for payments that have been processed externally. When an organization uses a third-party payroll service, the processed payment information is stored in this table, linked to the specific employee assignment. This enables Oracle HRMS to maintain a complete record of compensation history while delegating the actual payroll calculation and disbursement to an external system. The table's existence is critical for ensuring data integrity and providing a unified view of an employee's earnings within the EBS framework, regardless of the processing origin.

Key Information Stored

The table stores granular details for each payment processed by an external payroll provider. Its structure is anchored by a system-generated primary key, PAYMENT_DETAIL_ID. The most significant foreign key column is PROCESSED_ASSIGNMENT_ID, which links the payment detail to its source record in the PER_BF_PROCESSED_ASSIGNMENTS table, thereby connecting the payment to a specific employee assignment for a given payroll run. Another crucial column is PERSONAL_PAYMENT_METHOD_ID, which identifies the method (e.g., direct deposit, check) used for the disbursement. The table also includes a BUSINESS_GROUP_ID column, enforcing data security by partitioning the data within the correct business group context as defined in HR_ALL_ORGANIZATION_UNITS. Additional columns, inferred from standard patterns, would typically hold payment amounts, dates, earnings classifications, and references to the external payroll run.

Common Use Cases and Queries

The primary use case is reporting and auditing payments made via a third-party provider. HR and payroll administrators query this table to verify processed payments, reconcile totals, and investigate discrepancies. A common reporting pattern involves joining to employee and assignment tables to produce detailed payment registers.

  • Sample Query for Payment Details by Employee:
    SELECT ppf.full_name,
    pbd.*
    FROM per_bf_payment_details pbd,
    per_bf_processed_assignments bpa,
    per_all_assignments_f asg,
    per_all_people_f ppf
    WHERE pbd.processed_assignment_id = bpa.processed_assignment_id
    AND bpa.assignment_id = asg.assignment_id
    AND asg.person_id = ppf.person_id
    AND SYSDATE BETWEEN asg.effective_start_date AND asg.effective_end_date
    AND SYSDATE BETWEEN ppf.effective_start_date AND ppf.effective_end_date;
  • Audit & Reconciliation: Summarizing total payments by business group or payroll run for comparison with external provider reports.
  • Data Integration: Serving as the target table for data loads from the third-party payroll system's output files.

Related Objects

PER_BF_PAYMENT_DETAILS is centrally linked to several key HR tables, primarily through foreign key relationships documented in the ETRM.

  • PER_BF_PROCESSED_ASSIGNMENTS: This is the most direct parent table. The foreign key on PROCESSED_ASSIGNMENT_ID links each payment detail line to the broader processed assignment record, which contains information about the payroll period and assignment context for the external run.
  • HR_ALL_ORGANIZATION_UNITS: The foreign key on BUSINESS_GROUP_ID ensures that every payment detail record is associated with a valid business group, maintaining the HR Security profile's data isolation.
  • PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F: While not direct foreign keys, these are essential related objects. Payment details are logically associated with a person and assignment via the join through PER_BF_PROCESSED_ASSIGNMENTS.ASSIGNMENT_ID.
  • PER_PERSONAL_PAYMENT_METHODS_F: The PERSONAL_PAYMENT_METHOD_ID column would typically reference this table to determine the disbursement method details for the payment.