Search Results sort_code

Overview

The HRFV_GB_DIRECT_DEPOSITS view is an Oracle E-Business Suite business view template residing in the APPS schema under the PER (Human Resources) product. Its designation "HRFV" identifies it as an HR Flexfield View—a generated database object instantiated from a business view template that exposes descriptive flexfield segments as discrete, queryable columns. Specifically, this template maps the United Kingdom (GB) bank direct deposit flexfield structure maintained on personal payment methods, converting the otherwise opaque SEGMENT1 through SEGMENT8 columns of PAY_EXTERNAL_ACCOUNTS into meaningful business attributes such as sort code, bank name, bank branch, and account number.

Because it is a template-driven flexfield view, its runtime definition can be regenerated whenever the underlying descriptive flexfield configuration changes. It serves as the reporting and integration surface for HR and Payroll users who require a flattened, denormalized representation of employee direct deposit instructions together with the organizational and assignment context needed for reconciliation, audit, and third-party bank file generation. In both 12.1.1 and 12.2.2, the object is delivered as a VALID view, though the 12.2.2 ETRM metadata records a slightly different base object set than the illustrative view text, reflecting the ongoing consolidation of HR views onto the PER_PEOPLE_X, PER_ASSIGNMENTS_X, and HR_ALL_POSITIONS_F_TL layer.

Underlying Base Objects

The view joins a broad set of HR and Payroll synonyms and views. Documented referenced objects include HR_ALL_ORGANIZATION_UNITS_TL, HR_ALL_POSITIONS_F_TL, HR_LOCATIONS_ALL_TL, PER_ASSIGNMENTS_X, PER_PEOPLE_X, PER_GRADES_TL, PER_JOBS, PAY_EXTERNAL_ACCOUNTS, PAY_ORG_PAYMENT_METHODS_F, PAY_PERSONAL_PAYMENT_METHODS_F, PAY_PAYMENT_TYPES, and PAY_PAYMENT_TYPES_TL. Supporting PL/SQL packages invoked during view execution include HR_DISCOVERER (used in the view text via CHECK_END_DATE to apply effective-date logic), and the security and utility packages HR_SECURITY, HR_GENERAL, HR_PERSON_NAME, and HR_BIS.

The flexfield segments themselves are sourced from PAY_EXTERNAL_ACCOUNTS (PEA), whose SEGMENT1..SEGMENT8 columns hold the GB bank details. The join to PAY_PAYMENT_TYPES and its translation table supplies the payment type, while the territory code check (PT.TERRITORY_CODE = 'GB') ensures segments are only surfaced for United Kingdom legislative contexts, returning NULL otherwise.

Key Columns

The GB-specific bank columns are the central output, each guarded by a DECODE on territory code:

• SORT_CODE — SEGMENT1; the UK bank sort code.
• BANK_NAME — SEGMENT2; the financial institution name.
• BANK_BRANCH — SEGMENT3; the branch designation.
• ACCOUNT_NUMBER — SEGMENT4; the employee's bank account number.
• ACCOUNT_NAME — SEGMENT5; the account holder name.
• ACCOUNT_TYPE — SEGMENT6; savings, current, or similar.
• BLD_SOCIETY_ACCOUNT_NUMBER — SEGMENT7; building society reference.
• BANK_BRANCH_LOCATION — SEGMENT8; branch location detail.

Contextual columns include PERSON_NAME, EMPLOYEE_NUMBER, ASSIGNMENT_NUMBER, BUSINESS_GROUP_NAME, ORGANIZATION_NAME, JOB_NAME, POSITION_NAME, GRADE_NAME, LOCATION_NAME, PAYMENT_METHOD, PAYMENT_TYPE, CURRENCY_CODE, AMOUNT, PERCENTAGE, PRIORITY, and the effective start/end dates. Surrogate identifiers such as PERSON_ID, ASSIGNMENT_ID, EXTERNAL_ACCOUNT_ID, and PERSONAL_PAYMENT_METHOD_ID enable downstream joins.

Common Use Cases and Queries

Typical uses include validating employee bank details ahead of a UK BACS payment run, reconciling direct deposit splits across multiple accounts, and feeding third-party payroll or treasury systems. Because the user search term was "bank_branch," the most direct query filters on the BANK_BRANCH column:

SELECT person_name, employee_number, sort_code, bank_name, bank_branch, account_number, payment_method, percentage FROM apps.hrfv_gb_direct_deposits WHERE bank_branch IS NOT NULL ORDER BY person_name;

For enforcement of HR security, callers should invoke the standard HR_SECURITY predicates or query through the secured business group layer rather than selecting directly, since the base view does not by itself filter rows by the session's security profile. A second common pattern groups deposits by payment method to reconcile the percentage split:

SELECT person_name, payment_method, payment_type, SUM(percentage) total_pct FROM apps.hrfv_gb_direct_deposits GROUP BY person_name, payment_method, payment_type;

Overall, HRFV_GB_DIRECT_DEPOSITS provides a stable, template-generated interface to UK bank direct deposit data, insulating report builders from the underlying flexfield segment numbering while remaining consistent across EBS 12.1.1 and 12.2.2.