Results for “hr_s_payment_types”
40 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
HR_S_PAYMENT_TYPES is a Human Resources (PER) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. The designation "_S_" indicates that this is a translated (multi-language) seed or setup table within the HR schema. Its primary function is to define and store the configuration of payment types used in payroll-style disbursements, such as direct deposit, check, or other payment mechanisms. Each row represents a distinct payment type that can be assigned to employees, applicants, or third parties for compensation purposes. The table carries validation rules, currency and territory restrictions, and default-assignment flags that control how a payment type behaves during payroll or payment processing.
Based on the heuristic Data Vault classification provided in the ETRM metadata, this object is treated as a standalone entity, meaning it does not have parent-child relationships apart from referencing PAY_PAYMENT_TYPES via a foreign key. In Data Vault modeling terms, it is best described as a hub with descriptive attributes, or more precisely as a reference table / lookup hub that holds the business key PAYMENT_TYPE_ID and associated descriptive columns. The standalone classification indicates no downstream FK dependencies, simplifying its role as a configuration reference source.
Key Information Stored
The table contains 17 documented columns. The most important are:
- PAYMENT_TYPE_ID — Surrogate primary key and the business key candidate. Also a foreign key to PAY_PAYMENT_TYPES, establishing the master list of payment types.
- PAYMENT_TYPE_NAME — The display name of the payment type (e.g., "Direct Deposit", "Check").
- TERRITORY_CODE — Restricts the payment type to a specific legislative or geographic territory.
- CURRENCY_CODE — The currency in which the payment type is valid.
- CATEGORY — A classification grouping (e.g., bank transfer, manual check) used for filtering and reporting.
- ALLOW_AS_DEFAULT — Indicates whether this payment type can be set as the default for an assignment.
- PRE_VALIDATION_REQUIRED — Flag determining whether pre-validation logic must run before the payment type can be used.
- PROCEDURE_NAME — The name of the PL/SQL procedure invoked for validation or processing.
- VALIDATION_DAYS — Number of days within which validation must occur.
- VALIDATION_VALUE — A threshold or reference value used by the validation routine.
- RECONCILIATION_FUNCTION — The function used to reconcile payments of this type.
- DESCRIPTION — Free-text explanation of the payment type.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard audit columns tracking who created or modified the record and when.
The surrogate primary key is PAYMENT_TYPE_ID. No separate unique index is documented beyond this key, though PAYMENT_TYPE_ID combined with TERRITORY_CODE and CURRENCY_CODE may serve as a composite business-key candidate in practice.
Common Use Cases and Queries
Typical uses include configuring payment methods during payroll setup, validating employee payment assignments, and reporting on payment type distribution by territory or currency. A common query retrieves all allowed default payment types for a given territory:
SELECT payment_type_id, payment_type_name, currency_code FROM hr_s_payment_types WHERE territory_code = :p_territory AND allow_as_default = 'Y';- Joining to PAY_PAYMENT_TYPES to reconcile the master and HR-specific configurations:
SELECT p.payment_type_name, s.territory_code FROM pay_payment_types p, hr_s_payment_types s WHERE p.payment_type_id = s.payment_type_id; - Reporting on validation rules:
SELECT payment_type_name, pre_validation_required, procedure_name FROM hr_s_payment_types WHERE pre_validation_required = 'Y';
These queries support payroll administrators in auditing payment type eligibility and troubleshooting failed validations during payroll runs.
Related Objects
The most significant related objects include:
- PAY_PAYMENT_TYPES — The parent master table referenced via HR_S_PAYMENT_TYPES.PAYMENT_TYPE_ID → PAY_PAYMENT_TYPES.PAYMENT_TYPE_ID. This is the primary FK relationship.
- PAY_PAYMENT_TYPES_TL — Translation table for payment type names.
- HR_S_PAYMENT_TYPES_TL — Translated version of this table for multi-language support.
- PAY_PERSONAL_PAYMENT_METHODS — Stores employee-level payment method assignments that reference payment types defined here.
- PAY_EXTERNAL_ACCOUNTS — Bank account details associated with specific payment types.
- PER_ALL_PEOPLE_F — Indirectly related through payment method assignments to people records.
These relationships confirm the table's role as a configuration reference supporting payroll and payment processing within Oracle EBS Human Resources.
-
- Retrofitted
-
- Retrofitted
-
TABLE: HR.HR_S_PAYMENT_TYPES 12.1.1
-
TABLE: HR.HR_S_PAYMENT_TYPES 12.2.2
-
VIEW: HR.HR_S_PAYMENT_TYPES# 12.2.2
-
VIEW: HR.HR_S_PAYMENT_TYPES# 12.2.2
-
PACKAGE: APPS.HR_LEGISLATION 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
PACKAGE: APPS.HR_LEGISLATION 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person