Search Results put_missing_period




Overview
Explore in AI Chat

Overview

BIS_VALIDATION_UTILITIES is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Business Intelligence System (BIS) product family, which supplies the application-side infrastructure for the Oracle EBS Intelligence/Discoverer reporting stack and the underlying ETL and staging logic. The package is declared AUTHID CURRENT_USER, meaning its unqualified object references resolve against the privileges and schema of the calling session rather than the package owner. Its header carries the revision marker 115.0, dated 2003/06/26, indicating the file has been stable across many release cycles.

The business purpose of the package is to record data-quality and validation exceptions that arise when BI content is refreshed or reconciled. Rather than raising hard errors, the procedures publish structured exception rows describing a defect — a missing currency, missing unit of measure, missing accounting period, or missing contract — together with an optional exception message and a corrective-action flexfield token that points the user at the resolution step. In ETRM terms the package is classified as OTHER rather than as a public or private API, reflecting its role as an internal utility invoked by other BIS code rather than by external integrations.

Key Procedures and Functions

The package exposes six documented procedures, all of which follow a consistent "PUT_*" naming convention for writing a validation finding into the BI exception store.

  • PUT_MISSING_PERIOD — Records a validation failure caused by an absent or unresolvable accounting period, and accepts parameters identifying the exception message, the corrective action, and the period and calendar context. This is the procedure associated with the search term "put_missing_period".
  • PUT_MISSING_CURRENCY — Records an exception where a required currency, currency pair, or exchange-rate type is missing or unavailable for the relevant effective date.
  • PUT_MISSING_UOM — Records an exception where a unit-of-measure conversion is missing, including the inventory item context where the conversion applies.
  • PUT_MISSING_CONTRACT — Records an exception involving a missing or invalid contract, carrying rate type, currency, date, and contract number/identifier/status context.
  • PUT_OTHER_VALIDATION — A generic catch-all entry point for validation findings that do not fit the specialised procedures, distinguished by an error-type parameter.
  • PUT_MISSING_GLOBAL_SETUP — Records missing global setup data; unlike the other procedures it takes a single parameter list rather than discrete named parameters.

Tables Accessed

The documented object dependencies are DBMS_SQL, BIS_REFRESH_LOG, and PLITBLM. BIS_REFRESH_LOG is the principal persistent target: the PUT_* procedures write their exception rows into this BI refresh log so that failures are visible during and after a collection run. PLITBLM is the standard Oracle EBS PL/SQL table/array helper package used internally for bulk collection handling. DBMS_SQL appears in the dependency list because PUT_MISSING_GLOBAL_SETUP accepts a DBMS_SQL.VARCHAR2_TABLE parameter for its parameter list. No other application tables are documented as being read or written.

Usage Notes

The procedures are designed to be called programmatically by other BIS validation and collection logic rather than directly by end users. In a typical refresh, a validation routine detects a condition such as a fact row referencing a period that does not exist in the assigned calendar and then calls PUT_MISSING_PERIOD to log it with a corrective-action flexfield entry; that entry surfaces through the BI exception reporting UI so an administrator can correct the source data and re-run the collection. Because the package is AUTHID CURRENT_USER, custom diagnostics run under a different schema will resolve synonyms against that schema's privileges. The package is not referenced by any other documented package, so it should be treated as a leaf utility. Customisations should call the procedures as documented and should not modify the package body, since it is a shipped Oracle object whose behaviour is preserved across 12.1.1 and 12.2.2.