Results for “bpa_attribute1”

36 results




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

Overview

PER_BF_PROCESSED_ASSIGNMENTS is a Human Resources (PER) module table in the HR schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as an intersection table that records which employee assignments have been processed by a third-party (non-Oracle) payroll provider during a given payroll run. The "BF" prefix refers to the payroll interface architecture used to exchange data between Oracle EBS and an external payroll engine; rows in this table represent the successful linkage of an assignment to a specific payroll run processed through that external provider.

From a data-modeling perspective, the table is heuristic-classified as hub-leaning. It carries its own surrogate primary key and resolves into child tables (balance amounts and payment details), which is characteristic of a hub or reference entity that anchors downstream transactional detail. This classification is a modeling suggestion only, derived from the foreign-key topology, and should not be treated as a formal Data Vault design.

Key Information Stored

The table is documented with 40 columns. The most significant structural and descriptive columns are:

The BPA attribute columns are the dominant volume of the 40 documented columns and are the extension point for third-party provider integration data, whereas the identity and relationship columns above are the ones routinely joined and filtered in reporting.

Common Use Cases and Queries

Typical scenarios include reconciling third-party payroll output back to Oracle, identifying which assignments were accepted or rejected in a run, and drilling from a run into per-assignment balance or payment detail.

  • List all assignments processed in a specific run:
    • SELECT processed_assignment_id, assignment_id FROM per_bf_processed_assignments WHERE payroll_run_id = :run_id;
  • Confirm the assignment was processed exactly once per run (business-key validation): GROUP BY payroll_run_id, assignment_id HAVING COUNT(*) > 1.
  • Join to run header for context:
    • SELECT pba.assignment_id, pr.run_name FROM per_bf_processed_assignments pba JOIN per_bf_payroll_runs pr ON pr.payroll_run_id = pba.payroll_run_id;
  • Aggregate balance or payment detail per processed assignment through the child tables PER_BF_BALANCE_AMOUNTS and PER_BF_PAYMENT_DETAILS using PROCESSED_ASSIGNMENT_ID.
  • Report on flexfield values by querying BPA_ATTRIBUTE_CATEGORY and the relevant BPA_ATTRIBUTE column.

Related Objects

  • PER_BF_PAYROLL_RUNS — Parent table; joined on PAYROLL_RUN_ID.
  • PER_BF_BALANCE_AMOUNTS — Child table; references this table via PROCESSED_ASSIGNMENT_ID, holding balance detail per processed assignment.
  • PER_BF_PAYMENT_DETAILS — Child table; references this table via PROCESSED_ASSIGNMENT_ID, holding payment-level detail per processed assignment.
  • PER_ASSIGNMENTS_F / PER_ALL_ASSIGNMENTS_F — Source of assignment context referenced by ASSIGNMENT_ID.
  • PER_BF_PROCESSED_ASSIGNS_PK / PER_BF_PROCESSED_ASSIGNS_UK1 — Primary and unique indexes enforcing the identity and business-key constraints.