Search Results clob_to_varchar2

Overview

APPS.BIS_IMPL_DEV_PKG is a VALID PL/SQL package in the APPS schema that forms part of the Oracle E-Business Suite application implementation and setup infrastructure within the BIS (Business Intelligence System / EBS setup) module family. Its primary role is to manage implementation-time metadata that links application objects, pages, concurrent programs, and dependencies to one another. In practice, the package provides the programmatic backbone used by the migration and customization tooling that tracks how application content objects depend on each other, how page functions are registered, and which implementation pages have been migrated between environments. It is registered with an API classification of OTHER, indicating it is a supporting utility package rather than a public business API exposed for external integration. The package depends on the standard FND_API error-handling framework and the SYS.STANDARD package, and it is itself referenced by three other packages, including BIS_COLL_RS_HISTORY, BIS_CREATE_REQUESTSET, and its own package body, as well as the view BIS_OBJ_DEPENDENCY_V.

Key Procedures and Functions

The documented package exposes approximately thirty procedures and functions, which fall into three functional clusters.

• Linkage management: CREATE_LINKAGE, UPDATE_LINKAGE, and DELETE_LINKAGE create, maintain, and remove relationships between implementation objects (for example, between a page and its associated program).
• Validation helpers: DEP_LOOP_VALIDATION, PAGE_NAME_VALIDATION, OBJECT_NAME_VALIDATION, OBJECT_OWNER_VALIDATION, CONC_PROGRAM_VALIDATION, and REFRESH_PROGRAM_EXISTS enforce integrity rules before persistence — checking that dependency chains do not form loops, that page and object names are unique and valid, that owners exist, and that referenced concurrent programs are present.
• Dependency management: CREATE_DEPENDENCY, UPDATE_DEPENDENCY, and DELETE_DEPENDENCY maintain entries in the object dependency registry. Query helpers GET_USER_OBJECT_NAME, IS_PAGE_MIGRATED, and GET_FUNCTION_BY_PAGE retrieve object names, migration status, and the form function tied to a given page.
• Property management: CREATE_PROPERTIES, UPDATE_PROPERTIES, DELETE_PROPERTIES, and UPDATE_OBJ_LAST_REFRESH_DATE manage object property records and stamp the last refresh timestamp used by the migration process.
• Utility: CLOB_TO_VARCHAR2 converts large character objects to standard VARCHAR2 values for comparison, storage, or display purposes.

Tables Accessed

The package reads and writes several core BIS and FND tables through APPS synonyms:

• BIS_OBJ_DEPENDENCY — the master registry of object-to-object dependencies; central to the CREATE/UPDATE/DELETE_DEPENDENCY and validation routines.
• BIS_OBJ_PROG_LINKAGES — stores the linkage between implementation objects and the concurrent programs that implement them; used by the linkage procedures.
• BIS_OBJ_PROPERTIES — holds attribute-value properties for implementation objects, managed by the property procedures.
• FND_APPLICATION — provides application identifiers and short names used during owner and object validation.
• FND_FORM_FUNCTIONS — supplies the function definitions referenced by pages, supporting GET_FUNCTION_BY_PAGE and CONC_PROGRAM_VALIDATION.
• DBMS_LOB — the Oracle-supplied LOB package used by CLOB_TO_VARCHAR2.

Usage Notes

BIS_IMPL_DEV_PKG is invoked during implementation, migration, and setup activities rather than at runtime transaction processing. It is referenced by BIS_COLL_RS_HISTORY and BIS_CREATE_REQUESTSET, indicating that request-set generation and collection history processes call into it to resolve and validate implementation dependencies. The BIS_OBJ_DEPENDENCY_V view exposes its dependency data for reporting. Because the package is not classified as a public API, direct calls from custom code should be undertaken with caution and only after validating against the target release (12.1.1 or 12.2.2), since procedure signatures are not documented in the ETRM extract and may vary between releases. The presence of validation procedures implies the package is intended to be called behind UI or concurrent-program front ends, which supply the parameters and handle the YES/NO outcomes returned by the validation and existence checks.