Search Results cz_servers_s

Overview

CZ_ORAAPPS_INTEGRATE is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified under the ETRM taxonomy as OTHER. It belongs to the Oracle Applications Rapid Implementation (formerly "Oracle Applications Integrate") family of utilities and provides the runtime integration layer used to register, administer, and reconcile external applications and servers that participate in a distributed Oracle EBS landscape. Its principal responsibilities include deriving surrogate key values for Oracle Applications objects, managing server-to-server database link definitions, orchestrating the creation, refresh, and removal of external views, and enrolling or removing processes (SPX, export, import, maintenance) with the integration framework.

The package is versioned as 120.19.12020000.2 and is applicable to both Release 12.1.1 and 12.2.2 environments. It is a low-level infrastructure package rather than a business-logic API, and it is referenced by four other packages within the Oracle Applications integration stack. The header comment identifies the source file as czcaintb.pls.

Key Procedures and Functions

The package exposes 44 documented program units. The surrogate key functions construct composite identifiers used to uniquely represent transactional entities across servers:

• ITEM_SURROGATE_KEY — returns a delimited composite key from an item and organization identifier.
• COMPONENT_SURROGATE_KEY — returns a delimited key combining component sequence, explosion type, organization, and top item.
• PROJECT_SURROGATE_KEY — returns a key from explosion type, organization, and top item.
• ENDUSER_SURROGATE_KEY — returns a key from organization and salesperson identifier.
• ITEM_EXTERNAL_PK — computes the external primary key representation of an item.

Server and database-link administration includes CREATE_LINK_CP, SHOW_CZ_SERVERS_CP, POPULATE_CZ_SERVER_CP, ALTER_CZ_SERVER_CP, CREATE_REMOTE_HGRID_VIEW, and ISLINKALIVE, which collectively insert, modify, display, and validate the remote connectivity definitions stored in CZ_SERVERS. The external view lifecycle is handled by CREATE_EXV_VIEWS, RECREATE_EXV_VIEWS, RECREATE_EXV_VIEWS_CP, and DROP_EXV_VIEWS.

Process enrollment is covered by REGISTER_SPX_PROCESS, DELETE_SPX_PROCESS, REGISTER_EXPORT_PROCESS, REGISTER_IMPORT_PROCESS, and REGISTER_MAINT_SERVER_PROCESS. The get_App_Info procedure performs dynamic invocation of FND_INSTALLATION.GET_APP_INFO to resolve an Oracle schema name for a given application short name and link name.

Tables Accessed

The package operates against the following documented tables through APPS synonyms:

• CZ_SERVERS and CZ_SERVERS_S — store the server registry and its translated/denormalized companion rows manipulated by the *_SERVER_CP and link procedures.
• CZ_DB_LOGS — records diagnostic and audit messages emitted by the integration routines.
• CZ_DB_SETTINGS — supplies configuration parameters, including database link naming conventions.
• CZ_XFR_TABLES — drives the transfer-table catalogue used when building external views.
• CZ_XFR_PROJECT_BILLS and CZ_DEVL_PROJECTS — support project-related surrogate key derivation and integration metadata.
• DBMS_SQL, DUAL, USER_DB_LINKS, and USER_OBJECTS — provide dynamic SQL execution, single-row expression evaluation, link verification, and object existence checks respectively.

Usage Notes

CZ_ORAAPPS_INTEGRATE is invoked by the Oracle Applications integration framework and by the four dependent packages that call into it; it is not intended as an end-user entry point. The surrogate key functions are typically called from interface and conversion routines that must produce a deterministic, delimiter-based identifier usable in a distributed context. The *_CP procedures carry the concurrent-program naming convention, indicating that they are launched from concurrent program definitions, commonly through Oracle Applications Manager or the System Administrator responsibility for server registration and database link maintenance. View creation and process registration procedures are normally invoked during integration setup and configuration cycles rather than during routine transaction processing.

No call to a procedure named log_report appears in this package body. The diagnostic logging associated with this package is persisted through the CZ_DB_LOGS table; consumers seeking log output should query that table using the request or batch identifier recorded by the calling concurrent program.