Results for “paybv_balance_type”
17 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAYBV_BALANCE_TYPE is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) module. It exposes the definition of payroll balance types as stored in the underlying base tables, presenting them in a decoded, user-facing form suitable for reporting, integration, and diagnostics. The view is defined with the WITH READ ONLY clause, ensuring that consumers cannot issue DML statements against it; it is intended purely as a query surface.
The view resolves core reference values into descriptive text through calls to the HR_BIS.BIS_DECODE_LOOKUP function. The units of measure associated with a balance (BALANCE_UOM) are decoded via the lookups for the UNITS lookup type, the assignment remuneration flag is decoded via the YES_NO lookup, and the tax type is decoded through the US_TAX_TYPE lookup. This decoding is one of the principal reasons the view exists: it delivers balance-type metadata in a form that can be embedded directly into reports and interfaces without requiring consumers to join to lookup tables themselves.
By exposing both the raw code columns (BALANCE_UOM_CODE, ASG_REMUNERATION_FLAG_CODE, TAX_TYPE_CODE) and their decoded counterparts, the view supports both presentation-oriented queries and code-driven logic within a single object.
Underlying Base Objects
The documented base objects referenced by this view are PAY_BALANCE_TYPES (a synonym), PAY_BALANCE_TYPES_TL (a synonym), and the HR_BIS package. The view joins the base balance-type definition table PBT to its translation table PBTT on BALANCE_TYPE_ID, restricting the translation row to the language of the current session via PBTT.LANGUAGE = USERENV('LANG'). This is a standard EBS translated-entity pattern: the untranslated rows carry the structural and coding attributes, while the _TL table supplies the BALANCE_NAME and REPORTING_NAME in the user's language.
The HR_BIS package is invoked for all lookup decoding, and the view also uses HR_BIS.GET_LEGISLATION_CODE and HR_BIS.GET_SEC_PROFILE_BG_ID to evaluate row-level security. The final CASE expression computes BG_SECURITY_FLAG_CODE as 'Y' or 'N', marking whether the balance type is visible to the current user based on legislation and business group security profile.
Key Columns
- BALANCE_NAME / REPORTING_NAME — the translated name of the balance type and its reporting label, both sourced from PAY_BALANCE_TYPES_TL.
- BALANCE_UOM — the decoded unit of measure (for example monetary, hours, or days) obtained via BIS_DECODE_LOOKUP on the UNITS lookup, with the underlying BALANCE_UOM_CODE also exposed.
- CURRENCY_CODE — the currency in which the balance is held, where applicable.
- LEGISLATION_CODE / LEGISLATION_SUBGROUP — the legislation to which the balance type belongs and any subgrouping.
- ASSIGNMENT_REMUNERATION_FLAG — decoded YES_NO indicator (ASG_REMUNERATION_FLAG_CODE) denoting whether the balance feeds remuneration for the assignment.
- TAX_TYPE — decoded US_TAX_TYPE value (TAX_TYPE_CODE) for tax reporting.
- BALANCE_TYPE_ID, BUSINESS_GROUP_ID, BALANCE_CATEGORY_ID, BASE_BALANCE_TYPE_ID, INPUT_VALUE_ID — principal keys and relationships to categories, base balances, and input values.
- BG_SECURITY_FLAG_CODE — row-level security indicator evaluated against the user's security profile and legislation context.
- Attribute columns and the '_DF:PAY:PAY_BALANCE_TYPES:PBT' descriptor — descriptive flexfield support and the DFF reference used by the form definition.
Common Use Cases and Queries
A frequent requirement is to determine the unit of measure and reporting context for a given balance type — precisely the "balance_uom" lookup that motivates searches on this object. A representative query follows:
SELECT balance_name,
reporting_name,
balance_uom,
currency_code,
legislation_code
FROM apps.paybv_balance_type
WHERE bg_security_flag_code = 'Y'
ORDER BY balance_name;
To inspect the decoded versus raw units values and confirm how lookups resolve:
SELECT balance_name,
balance_uom,
balance_uom_code
FROM apps.paybv_balance_type
WHERE balance_type_id = :p_balance_type_id;
For remuneration reporting, filtering on the decoded flag is common:
SELECT balance_name, reporting_name, tax_type
FROM apps.paybv_balance_type
WHERE assignment_remuneration_flag = 'Yes';
Because the view already applies language translation and security filtering, it is well suited to operational reports, concurrent program queries, and integration extracts that need human-readable balance metadata without additional joins to lookup or translation tables.
-
View: PAYBV_BALANCE_TYPE 12.2.2
APPS.PAYBV_BALANCE_TYPE·↳ HR_BIS·↳ PAY_BALANCE_TYPES·↳ PAY_BALANCE_TYPES_TL·Explore PAY module →
-
View: PAYBV_BALANCE_TYPE 12.1.1
APPS.PAYBV_BALANCE_TYPE·↳ HR_BIS·↳ PAY_BALANCE_TYPES·↳ PAY_BALANCE_TYPES_TL·Explore PAY module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.