Search Results default_payment_method_id




Overview

APPS.HRFV_PAYROLLS is a read-only Oracle EBS view that presents payroll definitions in a denormalized, user-friendly form suitable for reporting, integration, and lookups. It belongs to the HR/Payroll "FV" (flexfield view) family of seeded APPS views and is owned by the APPS schema. The view joins the payroll definition entity (PAY_PAYROLLS_X) to the organization payment method definition (PAY_ORG_PAYMENT_METHODS_X) and to the translated organization name table (HR_ALL_ORGANIZATION_UNITS_TL), resolving the payroll's business group name, its payroll name and period type, its default payment method name, and the surrogate identifiers for both the payroll and the default payment method. Because it is defined WITH READ ONLY, it exposes a stable, query-only surface over the underlying transactional views. In the Oracle EBS 12.1.1 and 12.2.2 environments, HRFV_PAYROLLS is used wherever a descriptive payroll list is required without embedding the underlying joins directly into the calling SQL. The column default_payment_method_id is central to the view's purpose: it is the surrogate key that links each payroll to its configured payment method and is also the key exposed for downstream lookups.

Underlying Base Objects

The documented base objects referenced by HRFV_PAYROLLS are PAY_PAYROLLS_X (view), PAY_ORG_PAYMENT_METHODS_X (view), HR_ALL_ORGANIZATION_UNITS_TL (synonym), and the packages HR_BIS, HR_GENERAL, and HR_SECURITY. The primary driving object is PAY_PAYROLLS_X, aliased as PAY. The join to PAY_ORG_PAYMENT_METHODS_X (aliased OPM) is an outer join on pay.default_payment_method_id = opm.org_payment_method_id(+), meaning a payroll appears even when no matching payment method row exists; in that case the default_payment_method name is null. The business group is resolved through an equi-join to HR_ALL_ORGANIZATION_UNITS_TL (aliased BGRT) on pay.business_group_id = bgrT.organization_id. Two further predicates apply: the translation language is restricted with bgrT.language = userenv('LANG'), so the business group name is returned in the session language, and pay.business_group_id = NVL(hr_bis.get_sec_profile_bg_id, pay.business_group_id), which enforces the HR security profile business group where one is defined.

Key Columns

  • business_group_name — the translated name of the business group owning the payroll.
  • payroll_name — the payroll name from PAY_PAYROLLS_X.
  • payroll_period_type — the period type (for example, monthly, semi-monthly) associated with the payroll.
  • default_payment_method — the organization payment method name sourced from PAY_ORG_PAYMENT_METHODS_X; null when no matching payment method exists because of the outer join.
  • default_payment_method_id — the surrogate identifier of the payroll's default payment method. This is the column most commonly searched and is used to join back to payment method definitions and to filter payrolls by the method they use for payment.
  • business_group_id — the business group identifier, also used by the security predicate.
  • payroll_id — the primary surrogate key of the payroll record, used for joins to assignments, elements, and other payroll-related entities.

The view also exposes a literal column, '_DF:PAY:PAY_PAYROLLS:pay', which identifies the descriptive flexfield context associated with the underlying payroll entity.

Common Use Cases and Queries

Typical uses include payroll listings for a business group or legal entity, resolving the default payment method name for a given payroll, and joining payrolls to payment method configuration for reconciliation. A basic listing filters on security-visible rows and orders by payroll name:

  • SELECT payroll_id, payroll_name, payroll_period_type, default_payment_method FROM apps.hrfv_payrolls ORDER BY payroll_name;
  • SELECT payroll_name, default_payment_method FROM apps.hrfv_payrolls WHERE default_payment_method_id = :p_payment_method_id;
  • SELECT p.payroll_name, p.default_payment_method FROM apps.hrfv_payrolls p WHERE p.business_group_id = :p_bg_id ORDER BY p.payroll_name;

Because the view already applies the HR security profile business group and the session-language restriction, these queries require no additional business group predicate. Note that default_payment_method may be null when the outer join finds no payment method row, so applications should test default_payment_method_id rather than the descriptive name when validating configuration completeness.