Results for “force_latest_bal_flag_code”

8 results




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

Overview

The PAYBV_DEFINED_BALANCE view is a business (BV) layer object in the Oracle EBS Payroll (PAY) module, owned by the APPS schema. It presents a secured, read-only projection of payroll defined balances together with derived display codes that are required by the Oracle Forms and OAF user interface layer. Its primary role is to expose the configuration attributes of a defined balance — including accumulation rules such as SAVE_RUN_BALANCE and GROSSUP_ALLOWED_FLAG — while applying business group and legislation level data security through a computed security flag. Because the view is defined WITH READ ONLY, all access is query-only, making it suited to reporting, integration, and UI retrieval rather than transactional DML.

Underlying Base Objects

The view is defined over two documented referenced objects. The first is the PAY_DEFINED_BALANCES synonym (aliased as PDB), which is the principal source of balance definition data such as DEFINED_BALANCE_ID, BALANCE_TYPE_ID, and BALANCE_DIMENSION_ID. The second is the HR_BIS package, a business intelligence/security helper package used to decode lookup values and evaluate security context. Specifically, HR_BIS.BIS_DECODE_LOOKUP is invoked to translate the FORCE_LATEST_BALANCE_FLAG into a YES/NO display value, while HR_BIS.GET_LEGISLATION_CODE and HR_BIS.GET_SEC_PROFILE_BG_ID are used to evaluate the user's current legislation and business group security profile. The relationship is therefore a direct one-to-one projection of PAY_DEFINED_BALANCES rows, enriched at query time by package function calls rather than joined to additional tables.

Key Columns

  • DEFINED_BALANCE_ID — Primary identifier of the defined balance record.
  • GROSSUP_ALLOWED_FLAG — Indicates whether the balance permits gross-up processing, a key attribute for tax and deduction configuration.
  • SAVE_RUN_BALANCE — Controls whether the defined balance is retained when a payroll run is saved.
  • FORCE_LATEST_BALANCE_FLAG — Decoded via HR_BIS.BIS_DECODE_LOOKUP to a YES/NO value for display; the raw code is also exposed as FORCE_LATEST_BAL_FLAG_CODE.
  • LEGISLATION_CODE and LEGISLATION_SUBGROUP — Define the legislative scope of the balance definition.
  • BALANCE_TYPE_ID and BALANCE_DIMENSION_ID — Link the definition to its balance type and dimensional context.
  • BUSINESS_GROUP_ID — Identifies the owning business group and participates in the security evaluation.
  • BG_SECURITY_FLAG_CODE — A computed column returning 'Y' or 'N' based on whether the row is visible under the user's business group and legislation security profile.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

The view is commonly used to drive the Defined Balance configuration form and to support extracts of payroll balance setup. Because security is pre-computed via BG_SECURITY_FLAG_CODE, reports may filter directly on that column. A typical query retrieving gross-up-enabled balances for the current security context is:

SELECT DEFINED_BALANCE_ID, GROSSUP_ALLOWED_FLAG, SAVE_RUN_BALANCE,
       FORCE_LATEST_BALANCE_FLAG, LEGISLATION_CODE, BUSINESS_GROUP_ID
  FROM APPS.PAYBV_DEFINED_BALANCE
 WHERE GROSSUP_ALLOWED_FLAG = 'Y'
   AND BG_SECURITY_FLAG_CODE = 'Y';

A second scenario inspects forced-latest-balance behavior across legislative groups, using the decoded display column for readability:

SELECT LEGISLATION_CODE, LEGISLATION_SUBGROUP, FORCE_LATEST_BALANCE_FLAG,
       COUNT(*)
  FROM APPS.PAYBV_DEFINED_BALANCE
 WHERE BG_SECURITY_FLAG_CODE = 'Y'
 GROUP BY LEGISLATION_CODE, LEGISLATION_SUBGROUP, FORCE_LATEST_BALANCE_FLAG;

Because the view is read-only and invokes HR_BIS functions per row, large extracts should be restricted with appropriate filters to control performance. All queries should reference the view through the APPS synonym to respect the supported access path.