Search Results pay_run_type_org_methods_f




Overview
Explore in AI Chat

Overview

PAY_RUN_TYPE_ORG_METHODS_F is an Oracle E-Business Suite Payroll (PAY) table owned by the HR schema. It stores organisation-level payment methods associated with a particular payroll run type. In effect, it defines which disbursement methods—such as cheque, direct deposit, or bank transfer—are permitted for a given run type within a specific organisation, business group, and legislative context.

The table is date-tracked. Every row carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, enabling Data Electronically Recorded (DateTrack) history so that configuration changes over time can be preserved and audited. The heuristic Data Vault classification mined from the foreign key structure is standalone. This indicates the table is not directly connected through a mined referential path to a parent or child in that heuristic model, and it may reasonably be treated as a reference or lookup-style entity rather than a hub, link, or satellite in a Data Vault design.

Key Information Stored

The table comprises 17 documented columns. The most operationally significant are:

  • RUN_TYPE_ORG_METHOD_ID — Surrogate primary key component, uniquely identifying each row in combination with the effective dates.
  • RUN_TYPE_ID — Foreign key to the payroll run type; identifies which run type the organisation payment method is attached to.
  • ORG_PAYMENT_METHOD_ID — Foreign key to the organisation payment method definition.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — DateTrack effective dating that defines the active period for the row.
  • BUSINESS_GROUP_ID — Business group context, a required component of the alternate unique key.
  • LEGISLATION_CODE — Legislative jurisdiction, also part of the alternate unique key, reflecting jurisdiction-specific payment method rules.
  • PRIORITY — Ordering of the payment method when multiple methods apply.
  • PERCENTAGE and AMOUNT — Split allocation values used when a payment is disbursed across multiple methods.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the application during updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit and WHO columns.
  • ZD_EDITION_NAME — Editioning marker present in the 12.2.x edition-based redefinition model.

The surrogate primary key is PAY_RUN_TYPE_ORG_METHODS_PK on (RUN_TYPE_ORG_METHOD_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE). The business-key candidate is the unique index PAY_RUN_TYPE_ORG_METHODS_UK1 on (RUN_TYPE_ID, ORG_PAYMENT_METHOD_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, BUSINESS_GROUP_ID, LEGISLATION_CODE). In the 12.2.2 physical schema both indexes also include ZD_EDITION_NAME.

Common Use Cases and Queries

Typical uses include validating which payment methods are available for a run type, reporting payment method configuration by legal entity, and diagnosing payment processing errors caused by a missing or inactive method.

A common query resolves active methods for a run type as of a given date:

  • SELECT org_payment_method_id, priority, percentage, amount FROM pay_run_type_org_methods_f WHERE run_type_id = :p_run_type_id AND business_group_id = :p_bg_id AND legislation_code = :p_leg_code AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Reporting queries frequently filter on BUSINESS_GROUP_ID and LEGISLATION_CODE to isolate a jurisdiction, and order by PRIORITY to reproduce the intended disbursement sequence. Because the table is date-tracked, historical point-in-time comparisons are performed by constraining the effective date range rather than relying on the current row only.

Related Objects