Results for “allow_as_default”

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

Overview

PAYBV_PAYMENT_TYPE_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PAY (Payroll) product family. It exposes payment type definitions used by Oracle Payroll and related Oracle Payments functionality, presenting a denormalized, translation-aware join between the payment type definition table and its multilingual (TL) translation table. The view is defined WITH READ ONLY, meaning it supports query and reporting access only; no DML is permitted against it.

Its principal reporting value lies in the CATEGORY_M column, which the user searched as "category_m". This column is not stored physically on the base tables. It is derived at runtime by a call to HR_BIS.BIS_DECODE_LOOKUP('PAYMENT_CATEGORY', PT.CATEGORY), which decodes the internal numeric or coded payment category into its business-facing lookup meaning. Consumers who query this view therefore obtain a human-readable category label alongside the raw category code, without having to join to the lookup tables themselves.

Underlying Base Objects

ETRM documents three referenced base objects: the package HR_BIS, and the synonyms PAY_PAYMENT_TYPES and PAY_PAYMENT_TYPES_TL, which resolve to the underlying APPS base tables.

• PAY_PAYMENT_TYPES (PT) — the primary definition table holding payment type identity and configuration attributes such as category, validation rules, reconciliation function, territory, and currency.
• PAY_PAYMENT_TYPES_TL (TL) — the translation table supplying the language-dependent PAYMENT_TYPE_NAME and DESCRIPTION, joined on PAYMENT_TYPE_ID with the predicate TL.LANGUAGE = USERENV('LANG').
• HR_BIS — the HR business intelligence/utility package whose BIS_DECODE_LOOKUP function resolves the PAYMENT_CATEGORY lookup to produce CATEGORY_M.

The join is an equi-join on PAYMENT_TYPE_ID, so each row represents one payment type in the session's current language, with translated descriptive attributes and untranslated configuration attributes drawn from the base table.

Key Columns

• CATEGORY_M — decoded, user-readable payment category derived from the PAYMENT_CATEGORY lookup; the most frequently reported column.
• PAYMENT_TYPE_NAME / DESCRIPTION — translated name and description from the TL table, presented in USERENV('LANG').
• CATEGORY — the underlying category code before decoding; useful for comparison or filtering against seeded lookup values.
• PAYMENT_TYPE_ID — primary key of the payment type, used to join to related payment and payroll objects.
• ALLOW_AS_DEFAULT — indicates whether the payment type may be used as a default.
• PRE_VALIDATION_REQUIRED, PROCEDURE_NAME, VALIDATION_DAYS, VALIDATION_VALUE — validation rule configuration controlling pre-payment validation behavior.
• RECONCILIATION_FUNCTION — the function used for reconciliation processing.
• TERRITORY_CODE, CURRENCY_CODE — geographic and currency applicability of the payment type.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used in reporting and integration queries that need a readable list of configured payment types, their categories, and validation settings. A common pattern filters by decoded category:

• Listing all payment types with their readable category labels for configuration review.
• Identifying payment types marked ALLOW_AS_DEFAULT for a given territory and currency.
• Auditing which payment types require pre-validation and what procedure or validation period applies.
• Extracting payment type IDs to join against payroll payment or reconciliation data.

Sample SQL:

SELECT category_m,
       payment_type_name,
       description,
       category,
       allow_as_default,
       territory_code,
       currency_code
FROM   apps.paybv_payment_type_v
WHERE  category_m = :p_category
ORDER  BY payment_type_name;

SELECT payment_type_id,
       payment_type_name,
       pre_validation_required,
       procedure_name,
       validation_days,
       validation_value
FROM   apps.paybv_payment_type_v
WHERE  allow_as_default = 'Y'
AND    territory_code = :p_territory;

Because CATEGORY_M is computed through BIS_DECODE_LOOKUP, queries filtering on the decoded value may incur the overhead of the lookup call; filtering on the underlying CATEGORY code where known can be more efficient. As the view is read-only and language-sensitive, results depend on the language environment of the querying session.