Search Results web_html_call




Overview
Explore in AI Chat

Overview

The APPS.BIS_RG_FIX_AKFLEX_DATA package body is a private, one-time remediation utility delivered with the Oracle E-Business Suite Business Intelligence System (BIS) product family. Its documented purpose is to migrate Oracle Application Framework (OAF) / AK region flex field data associated with Report Regions from the global data elements context into the BIS PM Viewer context. The header comment block, dated 02-25-00 with an initial creation by user "amkulkar," identifies the package as a corrective data-fix script rather than a general-purpose API. The most recent source revision recorded is 115.4 2002/11/19, indicating the package has been stable for many release cycles and remains shipped with EBS 12.1.1 and 12.2.2 as legacy content.

The package operates on the AK (Application Kit) region metadata that drives Oracle EBS self-service and HTML-based report rendering, specifically the entries created by the BIS viewer functions registered as BISVIEWER.SHOWREPORT%. Because these functions historically wrote flex field attribute context as global data elements, downstream rendering of BIS PM Viewer report pages could resolve the wrong attribute category. This package corrects that condition by re-tagging the affected AK metadata records.

Key Procedures and Functions

Two procedures are documented for this package:

  • FIX_AK_REGIONITEMS — Repairs individual AK region item records. The body opens a cursor over FND_FORM_FUNCTIONS to derive the report region code embedded in the WEB_HTML_CALL column, then updates the ATTRIBUTE_CATEGORY value on matching rows in AK_REGION_ITEMS to BIS PM Viewer. It returns a numeric status code and a status message describing the outcome, and traps WHEN OTHERS to surface the SQL error code and message rather than aborting.
  • FIX_AK_REGIONS — Performs the equivalent corrective update against the parent AK_REGIONS table, using the same cursor logic to identify BIS viewer report regions and re-assign the attribute category to the BIS PM Viewer context. Like the companion procedure, it exposes a return code and status message for caller inspection.

Both procedures are remediation-only: they contain no parameterized business logic, no commit management, and no re-entrancy safeguards beyond the standard exception handler.

Tables Accessed

  • FND_FORM_FUNCTIONS — Read only. The WEB_HTML_CALL column is parsed with INSTR/SUBSTR to extract the region code from the quoted argument of BISVIEWER.SHOWREPORT calls. Rows are filtered with an uppercase LIKE 'BISVIEWER.SHOWREPORT%' predicate.
  • AK_REGION_ITEMS — Updated. The ATTRIBUTE_CATEGORY column is set to the BIS PM Viewer context for every region item whose REGION_CODE matches a BIS viewer region.
  • AK_REGIONS — Updated in the same manner, correcting the region-level attribute category that governs flex field context resolution.

All three objects are resolved through APPS synonyms, confirming the package executes under the APPS schema against the shared AK and FND application foundation tables.

Usage Notes

This package is classified as OTHER and is referenced by no other packages, so it is not part of any standard runtime call chain. It is invoked manually — typically during patch application or post-upgrade remediation — by a DBA or technical consultant through SQL*Plus or a similar tool, executing the two procedures in sequence and inspecting the returned code and message for errors. The procedures do not commit; the caller is responsible for validating the row counts and committing the transaction. Because the package mutates AK metadata shared across the application, it should be run only under an approved change control window after a metadata backup. No form, concurrent program, or public API wrapper is documented for this object in ETRM.