Search Results cz_pb_client_apps




Overview
Explore in AI Chat

Overview

The CZ_PB_CLIENT_APPS table is a core data object within the Oracle Configurator (CZ) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. Its primary function is to manage the association between a Configurator publication and the Oracle EBS applications that are authorized to access and utilize that published configuration model. A publication is a runtime version of a configuration model, deployed for use in transactional environments like Oracle Order Management or Oracle iStore. This table acts as a critical security and access control mechanism, ensuring that only designated applications can invoke specific configurator publications, thereby enforcing modular and secure integration within the EBS architecture.

Key Information Stored

The table stores a straightforward mapping between two key identifiers. The PUBLICATION_ID column holds a foreign key reference to a specific, deployed configuration model as defined in the CZ_MODEL_PUBLICATIONS table. The FND_APPLICATION_ID column stores the unique identifier (APPLICATION_ID) from the FND_APPLICATION table, which defines all registered applications within the Oracle EBS instance. Together, these two columns form the table's primary key (CZ_PB_CLIENT_APPS_PK), enforcing a unique relationship where a given publication can be linked to a specific application only once. This structure explicitly defines which EBS applications are valid "clients" for each configurator publication.

Common Use Cases and Queries

A primary use case is validating application access during a configuration session. When a user initiates a configuration from within an EBS application like Order Management, the system queries this table to verify the application's right to launch the associated publication. Administrators use this table for audits and maintenance, such as identifying all applications enabled for a publication before decommissioning it, or adding a new application as a client after an upgrade. Common reporting queries include listing all publications accessible to a particular application or finding all client applications for a given model. A sample query to retrieve this information is:

  • SELECT mp.PUBLICATION_NAME, fa.APPLICATION_NAME
  • FROM CZ.CZ_PB_CLIENT_APPS ca,
  • CZ.CZ_MODEL_PUBLICATIONS mp,
  • APPLSYS.FND_APPLICATION fa
  • WHERE ca.PUBLICATION_ID = mp.PUBLICATION_ID
  • AND ca.FND_APPLICATION_ID = fa.APPLICATION_ID
  • AND mp.PUBLICATION_NAME = '<Publication_Name>';

Related Objects

The CZ_PB_CLIENT_APPS table maintains a direct and essential foreign key relationship with the core publications table. As documented in the ETRM metadata, the table references the CZ_MODEL_PUBLICATIONS table via the column CZ_PB_CLIENT_APPS.PUBLICATION_ID. This ensures referential integrity, meaning every record in CZ_PB_CLIENT_APPS must correspond to a valid, existing publication ID. The table also has an implicit logical dependency on the FND_APPLICATION table (owned by the APPLSYS schema), as the FND_APPLICATION_ID column stores keys from that table, although this is not enforced as a formal database foreign key in the provided metadata.