Search Results create_user_parm_value




Overview

SYS.DBMS_REPCAT_RGT is the Oracle-supplied PL/SQL package that provides the runtime administration interface for Refresh Group Templates within Oracle's Advanced Replication infrastructure, which underpins the Oracle E-Business Suite 12.1.1 and 12.2.2 multi-tier deployment model. Refresh group templates allow administrators to define a reusable, parameterized set of objects (tables, views, and supporting structures) that can be instantiated consistently across multiple replication sites. In the EBS context, this is central to deploying and maintaining read-only snapshots and materialized views used by reporting, self-service, and distributed transaction environments.

The package operates against the replication catalog (the SYS-owned REPCAT* repository tables) and exposes a stable programmatic surface for creating, altering, copying, and dropping templates and their component objects. Because it is owned by SYS and granted to PUBLIC, it is callable from any schema with the appropriate privileges, making it the standard entry point for DBAs automating multi-site replication deployments.

Key Procedures and Functions

The package exposes a documented set of procedures for managing templates, their contained objects, template parameters, user parameter values, and user authorizations. The principal groups are:

Tables Accessed

The package reads and writes the System Replication catalog tables, including REPCAT_REFRESH_TEMPLATES, REPCAT_TEMPLATE_OBJECTS, REPCAT_TEMPLATE_PARMS, REPCAT_USER_PARM_VALUES, and REPCAT_USER_AUTHORIZATIONS. These store template metadata, object membership, parameter definitions, user-specific parameter values, and access authorizations, respectively. Persistent changes here directly drive the behavior of downstream instantiation APIs.

Usage Notes

DBMS_REPCAT_RGT is generally invoked by DBAs and automated deployment scripts rather than directly from EBS forms or concurrent programs. It is the foundation on which DBMS_REPCAT_INSTANTIATE and its sibling packages (DBMS_REPCAT_RGT_ALT, DBMS_REPCAT_RGT_CUST, and the utility/checker packages) depend. Custom code should treat these as SYS-owned internals, invoke them only against a healthy replication catalog, and back up the repcat schema before bulk DROP_ALL_* operations.