Search Results end_of_time

Overview

APPS.PAY_DK_BAL_UPLOAD is a Danish localization package in Oracle E-Business Suite Payroll that supports the balance upload process used to load and validate third-party or externally calculated payroll balances into Oracle Payroll. Its primary business role is to determine the correct expiry date for uploaded balance entries, so that the Payroll application knows how long a given balance value remains valid for processing. The package belongs to the API classification OTHER and is documented in both ETRM 12.1.1 and 12.2.2, with source header information indicating a ship version of pydkbalupl.pkb (120.1, dated 2007). The package is closely associated with the write-back and balance adjustment logic used by pay_balance_upload, specifically the dim_expiry_date mechanism. References to fixed calendar boundaries (START_OF_TIME and END_OF_TIME) show that the package treats dates as either valid within the supported payroll range or as sentinel values indicating failure or an indefinite boundary.

Key Procedures and Functions

The package exposes four documented procedures and functions. Their names and purposes are as follows:

• EXPIRY_DATE — Returns the expiry date of a given balance dimension relative to an upload date. It evaluates the assignment and time period information to establish when an uploaded balance ceases to be effective. This is the core function supporting the balance upload expiry rule, and it is used by pay_balance_upload.dim_expiry_date.
• IS_SUPPORTED — Determines whether the balance upload scenario or dimension is supported by this Danish localization package, allowing callers to gate processing on localization-specific support.
• INCLUDE_ADJUSTMENT — Controls whether an adjustment entry should be included in the upload processing, generally used to decide if a balancing or corrective adjustment is required for the supplied upload context.
• VALIDATE_BATCH_LINES — Validates the individual lines of an upload batch before the balance data is applied, ensuring that assignments, dates, and related attributes are consistent enough to proceed.

The visible body code includes the internal routine get_expiry_date_info, which derives the inception-to-date (ITD) start date from PER_ALL_ASSIGNMENTS_F and PER_TIME_PERIODS. It computes the greatest of the minimum assignment effective start date and the minimum time period start date, then compares that value to the upload date. If the derived start date is on or before the upload date, it is returned; otherwise the code assigns END_OF_TIME ('31/12/4712'), signalling that the expiry cannot be derived and that a failure has occurred.

Tables Accessed

The package accesses three documented tables through APPS synonyms:

• PER_ALL_ASSIGNMENTS_F — Supplies assignment-level information, including effective start and end dates and the payroll to which the assignment belongs. It is central to determining the assignment's valid date range for balance upload purposes.
• PER_TIME_PERIODS — Provides payroll time period start dates, used to align the derived ITD start date with the payroll calendar for the assignment's payroll.
• DUAL — Used for simple date or constant evaluations, consistent with PL/SQL packages that need to return or compare sentinel date values.

Usage Notes

PAY_DK_BAL_UPLOAD is typically invoked indirectly by the Oracle Payroll balance upload framework rather than called from a user-facing form. The documented linkage to pay_balance_upload.dim_expiry_date indicates it is called during the balance upload process when the expiry date for a dimension must be determined. Because the expiry date function returns END_OF_TIME to indicate failure, callers must interpret that sentinel value according to the documented rule: an end-of-time expiry means the expiry date could not be derived and the consuming process should act accordingly, for example by rejecting or flagging the upload line. Custom code extending the Danish balance upload should therefore use IS_SUPPORTED and INCLUDE_ADJUSTMENT as gating checks, and validate batch lines via VALIDATE_BATCH_LINES before applying the upload. The package is not referenced by other packages, so it acts as a localized service used by the balance upload flow rather than as a shared utility. Because the code was shipped under an older file version, implementers should confirm behavior against the target 12.1.1 or 12.2.2 installation and avoid modifying the shipped package body directly; any localization or extension should be handled at the calling layer.