Results for “hrfv_backfeed_payment_details”
33 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.HRFV_BACKFEED_PAYMENT_DETAILS is a business view template in the PER (Human Resources) product family, used as the source from which a flexfield view is generated. In Oracle EBS 12.1.1 and 12.2.2, this object exposes backfeed payment details — the payment records produced after payroll processing and backfed into the HRMS payment tables. The view assembles organization, payroll, assignment, person, and payment data into a single denormalized projection suitable for reporting and integration. It is not a transactional table; it joins current effective-dated rows from several PER and PAY tables and applies HR security and decode packages at runtime. The presence of descriptive flexfield (DFF) pseudo-columns such as '_DF:PER:PER_BF_PAYMENT_DETAILS:BPD' indicates that the view is a flexfield-enabled template consumed by the Flexfield View Generator, enabling DFF attributes to be surfaced as queryable columns.
Underlying Base Objects
The view is defined over the following documented objects:
- PER_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_BUSINESS_GROUPS — person, assignment, and business group context.
- PER_BF_PAYMENT_DETAILS, PER_BF_PROCESSED_ASSIGNMENTS, PER_BF_PAYROLL_RUNS — the core backfeed tables holding processed assignment and payment detail rows.
- PAY_ALL_PAYROLLS_F, PAY_PAYMENT_TYPES, PAY_ORG_PAYMENT_METHODS_F, PAY_PERSONAL_PAYMENT_METHODS_F — payroll definition and payment method configuration.
- HR_GENERAL, HR_PERSON_NAME, HR_SECURITY — PL/SQL packages invoked for lookup decoding, name formatting, and security filtering.
The joins follow the payroll run hierarchy: PAYROLL_RUN_ID links BPR to BPA; PROCESSED_ASSIGNMENT_ID links BPA to BPD; ASSIGNMENT_ID and PERSON_ID link back to the assignment and person rows. Effective-dated tables are constrained with TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE, so the view returns only currently effective rows.
Key Columns
- Check Type — the searched term
CHECK_TYPEoriginates from PER_BF_PAYMENT_DETAILS and is presented asHR_GENERAL.DECODE_LOOKUP('BACKFEED_PD_CHECK_TYPE', BPD.CHECK_TYPE). This resolves the stored code into a meaningful lookup value for reporting. - Payment identifiers — PAYROLL_IDENTIFIER (PAY_PAYROLL_IDENTIFIER), CHECK_NUMBER, PAYMENT_DATE, AMOUNT.
- Organization and payroll — ORG.NAME (business group), PAYROLL_NAME, PERIOD_START_DATE, PERIOD_END_DATE, PROCESSING_DATE.
- Assignment and person — ASSIGNMENT_NUMBER, ASSIGNMENT_ID, PERSON_ID, EMPLOYEE_NUMBER, FULL_NAME.
- Payment method and currency — ORG_PAYMENT_METHOD_NAME, PAYMENT_TYPE_NAME, CURRENCY_CODE, PERSONAL_PAYMENT_METHOD_ID.
- Descriptive flexfield columns — the _DF token columns for BPD, BPA, and BPR contexts, exposed through the flexfield view generation process.
Common Use Cases and Queries
This view is typically consumed by payroll reconciliation reports, backfeed audit extracts, and interfaces that must validate payment details against payroll runs. Because CHECK_TYPE is stored as a lookup code, any query intending to filter or display it should apply the same decode logic used in the view.
SELECT business_group_name
, payroll_name
, assignment_number
, full_name
, check_number
, check_type
, payment_date
, amount
, currency_code
FROM apps.hrfv_backfeed_payment_details
WHERE payroll_identifier = 'SEMI-MONTHLY'
ORDER BY payment_date DESC;
To isolate a specific payment instrument, filter on the decoded check type:
SELECT check_number, amount, payment_date FROM apps.hrfv_backfeed_payment_details WHERE check_type = 'Electronic' AND payment_date BETWEEN :start_date AND :end_date;
Security is enforced through HR_SECURITY, so results are automatically restricted to the operating user's accessible business groups and organizations. When performance is a concern, restrict the query by PAYROLL_RUN_ID or PROCESSING_DATE, since the effective-date predicates and lookup decode are evaluated per row.
-
Business view template from which the flexfield view is generated.
APPS.HRFV_BACKFEED_PAYMENT_DETAILS·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore PER module →
-
Business view template from which the flexfield view is generated.
APPS.HRFV_BACKFEED_PAYMENT_DETAILS·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore PER module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
VIEW: APPS.PER_PEOPLE_F 12.1.1
-
VIEW: APPS.PER_PEOPLE_F 12.2.2
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person