Results for “cost_cleared_payment”

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

Overview

PAY_ORG_PAYMENT_METHODS_F is a datetracked (effective-dated) payroll configuration table in the Oracle E-Business Suite HR schema, owned by the Payroll (PAY) product. It defines the payment methods available to a specific Business Group, controlling how employees, assignments, and third parties are paid within that enterprise structure. Each row represents a single payment method available for use in a Business Group during a defined effective date range, such as direct deposit to a bank account, check issuance, or a cash transfer.

Because the table is suffixed with _F and carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, it participates in Oracle's date-tracked (datetrack) framework. Changes to a payment method's configuration are versioned rather than overwritten, preserving historical accuracy. From a Data Vault modeling perspective, the mined relationship structure suggests a link classification: the table associates independent entities — Business Group (organization), external account, payment type, defined balance, and time definition — through foreign keys housed on a surrogate-keyed record.

Key Information Stored

The primary key PAY_ORG_PAYMENT_METHODS_F_PK is the composite (ORG_PAYMENT_METHOD_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE); in the documented 12.2.2 schema this business-key candidate is further augmented with ZD_EDITION_NAME for the edition-based redefinition model. ORG_PAYMENT_METHOD_ID is the surrogate identifier for the payment method, while the date pair establishes its datetrack validity window.

• ORG_PAYMENT_METHOD_NAME — the user-facing name of the payment method shown in payroll setup and screens.
• BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS identifying the owning Business Group.
• EXTERNAL_ACCOUNT_ID — foreign key to PAY_EXTERNAL_ACCOUNTS, tying the method to a bank or clearing account.
• PAYMENT_TYPE_ID — foreign key to PAY_PAYMENT_TYPES, classifying the mechanism (e.g., direct deposit, check).
• DEFINED_BALANCE_ID — foreign key to PAY_DEFINED_BALANCES, used when payments are driven by a balance source.
• TIME_DEFINITION_ID — foreign key to PAY_TIME_DEFINITIONS, controlling timing rules.
• CURRENCY_CODE — the currency in which the payment method operates.
• COST_PAYMENT, COST_CLEARED_PAYMENT, COST_CLEARED_VOID_PAYMENT — flags governing costing of issued, cleared, and cleared-void payments.
• TRANSFER_TO_GL_FLAG — indicates whether associated entries transfer to the General Ledger.
• EXCLUDE_MANUAL_PAYMENT — restricts the method from manual (non-process) payment entry.
• PARENT_ORG_PAYMENT_METHOD_ID — self-referencing hierarchy pointer for derived methods.
• PMETH_INFORMATION_CATEGORY and PMETH_INFORMATION1–20 — the standard Oracle descriptive flexfield segment set for extensible attributes.

Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support concurrency control.

Common Use Cases and Queries

Typical usage involves resolving the effective payment method for a Business Group as of a given date, driving payment setup validation, and reporting on costing/GL behavior. Queries must respect the datetrack window to avoid returning future-dated or expired rows.

• Listing active methods for a Business Group: filter BUSINESS_GROUP_ID = :bg and constrain SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE.
• Joining to PAY_PAYMENT_TYPES to translate PAYMENT_TYPE_ID into a readable payment mechanism for reporting.
• Auditing costing configuration by selecting COST_* flags alongside EXTERNAL_ACCOUNT_ID for reconciliation against GL transfers.
• Identifying methods excluded from manual entry via EXCLUDE_MANUAL_PAYMENT for compliance checks.
• Extracting flexfield values (PMETH_INFORMATION1–20) for integration into downstream banking or treasury files.

Related Objects

The following objects are directly referenced through documented foreign keys and are the most significant for joins and dependency analysis:

• HR_ALL_ORGANIZATION_UNITS — joined on BUSINESS_GROUP_ID.
• PAY_EXTERNAL_ACCOUNTS — joined on EXTERNAL_ACCOUNT_ID.
• PAY_PAYMENT_TYPES — joined on PAYMENT_TYPE_ID.
• PAY_DEFINED_BALANCES — joined on DEFINED_BALANCE_ID.
• PAY_TIME_DEFINITIONS — joined on TIME_DEFINITION_ID.
• PAY_ORG_PAYMENT_METHODS_F (self-reference) — joined on PARENT_ORG_PAYMENT_METHOD_ID for hierarchical methods.