Results for “payment_type_id”

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

Overview

PAY_ORG_PAYMENT_METHODS_F_EFC is a date-tracked (F) copy of the PAY_ORG_PAYMENT_METHODS_F table in the Oracle Payroll (PAY) module, residing in the HR schema. It is populated exclusively by the EFC (Euro as a Functional Currency) process, an upgrade and migration utility used to stage and validate organization payment method definitions during a Euro functional currency conversion. Because its contents are generated by a background process rather than maintained directly by users, this table functions as a migration-specific shadow copy of the production payment method configuration and is not intended for direct transactional use.

From a Data Vault modeling perspective, the metadata classifies this table as standalone. Applying that heuristic, the object most closely resembles a satellite: it carries the descriptive attributes (PAYMENT_TYPE_ID, CURRENCY_CODE) as a dated, EFC_ACTION_ID-scoped snapshot of a business key entity, without asserting independent hub or link responsibilities on its own.

Key Information Stored

The table is documented with six columns in the 12.2.2 ETRM. Two categories of identifiers are relevant:

• ORG_PAYMENT_METHOD_ID — the surrogate identifier inherited from the source payment method definition; the anchor for joins back to the operational table.
• EFC_ACTION_ID — the migration run identifier associating the row with a specific EFC execution.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the date-tracked validity window for the record, mirroring the source table's effective dating.
• PAYMENT_TYPE_ID — the associated payment type (for example, check, direct deposit, or EFT), foreign-keyed to PAY_PAYMENT_TYPES.
• CURRENCY_CODE — the currency in which the payment method is denominated; central to EFC processing since the process re-evaluates currency assignments.

The primary key PAY_ORG_PAYMENT_METH_F_EFC_PK is a composite over ORG_PAYMENT_METHOD_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and EFC_ACTION_ID. This composite structure means the same payment method identifier may appear under multiple EFC_ACTION_ID values or effective-date spans, uniquely distinguishing each migrated version. ORG_PAYMENT_METHOD_ID combined with the effective dates forms the natural business-key candidate, while EFC_ACTION_ID acts as the migration-scoping discriminator.

Common Use Cases and Queries

Typical uses center on validating, auditing, and reconciling the results of an EFC conversion before the records are trusted or compared against the live configuration.

• Counting payment methods captured per EFC run: SELECT efc_action_id, COUNT(*) FROM hr.pay_org_payment_methods_f_efc GROUP BY efc_action_id;
• Detecting currency changes introduced by the migration:
  SELECT f.org_payment_method_id, f.currency_code, f.effective_start_date
FROM hr.pay_org_payment_methods_f_efc f
WHERE f.efc_action_id = :action_id;
• Reconciling the EFC copy against the live table to confirm parity or intentional deltas, joining on ORG_PAYMENT_METHOD_ID and the effective-date range.
• Reporting on payment types and currencies affected by the Euro conversion for audit deliverables.

Related Objects

• PAY_ORG_PAYMENT_METHODS_F — the source table this copy mirrors; joined on ORG_PAYMENT_METHOD_ID and effective dates.
• PAY_PAYMENT_TYPES — referenced via the PAYMENT_TYPE_ID foreign key, supplying payment type codes and names.
• PAY_ORG_PAYMENT_METHODS_F_EFC_PK — the primary key constraint enforcing uniqueness across the four key columns.
• Related organization and currency setup tables (such as currency definitions) that supply CURRENCY_CODE values.
• The EFC migration process and its run log/action identifier, which defines EFC_ACTION_ID scope.

Because the table is process-generated, any queries should be scoped by EFC_ACTION_ID to avoid mixing results from separate migration executions.