Search Results register_maint_server_process

Overview

APPS.CZ_ORAAPPS_INTEGRATE is a standalone PL/SQL package that belongs to the Oracle EBS Applications Technology layer and is registered with the API classification OTHER. Its principal role is to manage the integration plumbing between an Oracle E-Business Suite instance and one or more remote Oracle Applications databases through Oracle database links. The package generates the "surrogate keys" that uniquely identify master and transactional entities—items, components, projects and end users—so that records can be matched reliably across distributed systems where local identifiers may differ. It also creates, drops and recompiles the extraction views (EXV) that expose remote source data to the local instance, administers the CZ_SERVERS registry that describes each participating database, and drives several concurrent programs that register and maintain the transfer processes used by the integration.

Key Procedures and Functions

The package is declared AUTHID CURRENT_USER; the user who searches for component_surrogate_key is most likely tracing how a bill-of-material component is identified across instances. That function, COMPONENT_SURROGATE_KEY, accepts a component sequence identifier together with the explosion type, operating unit and top-level item, and returns a VARCHAR2 surrogate key that is stable regardless of which database resolved the query. The same pattern is applied by ITEM_SURROGATE_KEY, PROJECT_SURROGATE_KEY and ENDUSER_SURROGATE_KEY, each of which derives its key from the corresponding entity and organization context. ITEM_EXTERNAL_PK provides a related external primary key for items. ISLINKALIVE tests whether a named database link is reachable, returning a status used throughout the package to select a valid connection or to fail over.

View administration is handled by CREATE_EXV_VIEWS, DROP_EXV_VIEWS and RECREATE_EXV_VIEWS, with RECREATE_EXV_VIEWS_CP providing a concurrent-program wrapper that reports link status, the database link used and whether recompilation was requested. CREATE_REMOTE_HGRID_VIEW and CREATE_LINK_CP build the remote views and the link itself. The server registry is maintained through POPULATE_CZ_SERVER_CP, ALTER_CZ_SERVER_CP and SHOW_CZ_SERVERS_CP. Process registration is handled by REGISTER_SPX_PROCESS, DELETE_SPX_PROCESS, REGISTER_EXPORT_PROCESS, REGISTER_IMPORT_PROCESS and REGISTER_MAINT_SERVER_PROCESS. Many of these functions carry PRAGMA RESTRICT_REFERENCES(WNDS), confirming they perform no writes and read no package state.

Tables Accessed

The package reads and writes CZ_SERVERS and its CZ_SERVERS_S sequence-backed table to maintain the directory of integration nodes, and CZ_DB_SETTINGS and CZ_DB_LOGS for configuration values and executed transfer history. CZ_DEVL_PROJECTS and CZ_XFR_PROJECT_BILLS supply project and bill data used when surrogate keys are derived. CZ_XFR_TABLES identifies which tables are eligible for extraction. It queries USER_DB_LINKS and USER_OBJECTS to confirm the existence of links and views, and DUAL and DBMS_SQL are used for dynamic SQL and static value retrieval.

Usage Notes

CZ_ORAAPPS_INTEGRATE is invoked primarily from the concurrent programs that populate the server registry, recreate extraction views and register transfer processes, and secondarily from custom integration code that calls the surrogate key functions directly. The four packages that reference it depend on the key-generation routines. Because it relies on database links, it requires the integration administrator to have created the relevant links and CZ_SERVERS rows before the extraction views can be created or recompiled. In 12.1.1 and 12.2.2 the package name and AUTHID clause are unchanged, so callers referencing APPS.CZ_ORAAPPS_INTEGRATE.COMPONENT_SURROGATE_KEY remain portable across both releases.