Results for “backfeed_pd_check_type”

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

Overview

APPS.HRFV_BACKFEED_PAYMENT_DETAILS is an Oracle E-Business Suite (EBS) reporting view that consolidates payroll backfeed payment information associated with processed assignments in Oracle Payroll. In the context of EBS 12.1.1 and 12.2.2, "backfeed" refers to the process by which third-party payment data — most commonly disbursements generated by a payroll provider or external payment system — is loaded back into Oracle Payroll so that the corresponding assignment, payroll run, and payment records are reconciled and reflected in the application.

The view joins the backfeed header tables (PER_BF_PAYROLL_RUNS, PER_BF_PROCESSED_ASSIGNMENTS, PER_BF_PAYMENT_DETAILS) with core HR and Payroll master data, including person, assignment, business group, payroll, and payment method information. It is defined WITH READ ONLY, so it is strictly a query surface and cannot be used to insert, update, or delete data. Because the view is exposed under the APPS schema, it acts as a secure, date-effective reporting layer for developers and analysts who need visibility into backfeed payment transactions without navigating the underlying normalized tables directly.

The user's search term backfeed_pd_check_type corresponds directly to a decoded column in this view. The view text references HR_GENERAL.DECODE_LOOKUP('BACKFEED_PD_CHECK_TYPE', bpd.check_type), meaning the raw check-type code stored on PER_BF_PAYMENT_DETAILS is translated through the BACKFEED_PD_CHECK_TYPE lookup into its user-facing meaning (for example, identifying the form or instrument of payment).

Underlying Base Objects

The view is built over several categories of objects. The transactional core consists of PER_BF_PAYMENT_DETAILS, PER_BF_PROCESSED_ASSIGNMENTS, and PER_BF_PAYROLL_RUNS, which store the backfeed payment detail line, the processed assignment link, and the backfeed payroll run header respectively. These are joined to HR master data through PER_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_BUSINESS_GROUPS.

Payment method information is sourced from PAY_PERSONAL_PAYMENT_METHODS_F, PAY_ORG_PAYMENT_METHODS_F, and PAY_PAYMENT_TYPES, while the payroll definition is obtained from PAY_ALL_PAYROLLS_F. Supporting packages include HR_GENERAL (used for the lookup decode), HR_PERSON_NAME (for name formatting), and HR_SECURITY (for row-level security filtering by business group and security profile). All date-effective entities are constrained in the WHERE clause by TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date, ensuring that only currently effective person, assignment, payment method, and payroll records are returned.

Key Columns

• ORG.NAME — Business group name owning the payroll run.
• PAYROLL_NAME / PAYROLL_IDENTIFIER — Payroll and its short identifier.
• ASSIGNMENT_NUMBER, EMPLOYEE_NUMBER, FULL_NAME — Assignment and person identifying information.
• PERIOD_START_DATE, PERIOD_END_DATE, PROCESSING_DATE — Payroll run period and processing dates.
• CHECK_NUMBER, PAYMENT_DATE, AMOUNT — Payment detail values from PER_BF_PAYMENT_DETAILS.
• DECODE_LOOKUP('BACKFEED_PD_CHECK_TYPE', bpd.check_type) — Decoded check type; the column addressed by the search term.
• ORG_PAYMENT_METHOD_NAME, PAYMENT_TYPE_NAME, CURRENCY_CODE — Payment method and currency context.
• Descriptor columns (_DF:PER:PER_BF_PAYMENT_DETAILS:bpd, etc.) and hidden keys (PERSON_ID, ASSIGNMENT_ID, PAYROLL_ID, PAYROLL_RUN_ID, PAYMENT_DETAIL_ID, PERSONAL_PAYMENT_METHOD_ID).

Common Use Cases and Queries

Typical uses include reconciliation of third-party payments, audit of backfeed loads, and validation that check types, amounts, and dates match the source payment file. A representative query filtering on check type follows:

SELECT payroll_name,
       full_name,
       assignment_number,
       check_number,
       payment_date,
       amount,
       HR_GENERAL.DECODE_LOOKUP('BACKFEED_PD_CHECK_TYPE', check_type) check_type
FROM   apps.hrfv_backfeed_payment_details
WHERE  TRUNC(payment_date) BETWEEN :p_start AND :p_end
ORDER  BY payment_date, full_name;

Because the view already resolves lookup meanings and enforces date-effectiveness and HR security, it is well suited for concurrent-program extracts, OBIEE/BIP reports, and integration queries that export backfeed payment results to downstream financial or treasury systems. Any custom code referencing the column should use the decoded form rather than reading check_type directly from PER_BF_PAYMENT_DETAILS, to remain consistent with the view's presentation of the BACKFEED_PD_CHECK_TYPE lookup.