Search Results dbms_repcat_rgt_cust




Overview
Explore in AI Chat

Overview

DBMS_REPCAT_RGT_CUST is a member of the Oracle Advanced Replication management infrastructure that is shipped in the SYS schema and exposed in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The package name decomposes into "REPCAT" (Replication Catalog), "RGT" (Refresh Group Template), and "CUST" (Customization), indicating that it belongs to the subset of replication management APIs that administer refresh group templates rather than the refresh groups themselves.

In the EBS context, refresh group templates are the metadata definitions used by the Multi-Organization and multi-site deployment topologies to describe, in advance, how snapshot refresh groups should be constructed for downstream or "child" database sites. Administrators define a template once and the replication machinery instantiates concrete refresh groups from it as new sites are registered. DBMS_REPCAT_RGT_CUST provides the customization layer of that template facility — the packaged entry points that let a template be tailored (for example, to adjust the membership or propagation behaviour of groups generated from it) without altering the master template definition.

The object is reported as VALID in the ETRM repository, confirming that it is compiled and available in a standard EBS 12.2.2 installation. It is classified as an "OTHER" API, i.e. it is not a documented public EBS business API such as those in the AP, GL or OE schemas, but rather an Oracle Server-supplied PL/SQL package that EBS relies upon indirectly.

Key Procedures and Functions

The ETRM metadata records no documented procedures or functions for this package. This is expected: DBMS_REPCAT_RGT_CUST is an internal Oracle Server package whose callable interface is not published as part of the EBS API catalogue. Consequently, no parameter lists, return types or overload signatures are asserted here.

Functionally, the package belongs to the DBMS_REPCAT_RGT family, whose members divide responsibility as follows:

  • DBMS_REPCAT_RGT — the primary template administration interface (creating, dropping and generating from templates).
  • DBMS_REPCAT_RGT_CUST — the customization routines applied to templates and to the refresh groups generated from them.
  • DBMS_REPCAT_RGT_CUST2 — a companion customization package, referenced alongside this one in the dependency map.
  • DBMS_REPCAT_RGT_ALT and DBMS_REPCAT_RGT_UTL — alternate and utility layers respectively.

The dependency metadata states that DBMS_REPCAT_RGT_CUST is referenced by four packages: DBMS_REPCAT_RGT, DBMS_REPCAT_RGT_ALT, DBMS_REPCAT_RGT_CUST2 and DBMS_REPCAT_RGT_UTL. This bidirectional coupling within the RGT family is the strongest documented fact about the package: it is a supporting component invoked by the higher-level template APIs, not an entry point that end users or EBS application code call directly.

Tables Accessed

The ETRM extract lists no tables referenced through APPS synonyms, and no SQL statements are enumerated beyond the dependency block. This is consistent with the package's placement in SYS: the RGT packages operate almost exclusively against the replication dictionary — the SYSTEM-owned catalog views and base tables such as those underlying DBA_REPCAT, DBA_REPCAT_REFRESH_TEMPLATES, DBA_REPCAT_TEMPLATE_OBJECTS and their parameter and site-association companions.

Because those objects are owned by SYS/SYSTEM and are not exposed through APPS synonyms, they do not appear in the EBS table-reference inventory. The absence of documented table access therefore reflects namespace ownership rather than a package that performs no DML; the RGT family plainly maintains template and refresh-group metadata in the replication catalog.

Usage Notes

DBMS_REPCAT_RGT_CUST should not be invoked from EBS forms, concurrent programs or custom PL/SQL. It is an internal implementation dependency of the replication template layer, and Oracle has never published its specification as a supported programmatic interface. Customizations that call it directly risk breaking on patch application, since the package body may change between 12.1.1 and 12.2.2 and between Oracle Server patch sets.

Its practical relevance in an EBS 12.1.1 or 12.2.2 environment is diagnostic. When validating a database with utlrp.sql, investigating invalidation storms in the SYS schema, or assessing the impact of an Advanced Replication patch, this object appears in dependency chains reachable from DBMS_REPCAT_RGT. A status of VALID confirms a correctly compiled replication catalog. Any change to INVALID should be resolved by recompiling the DBMS_REPCAT_RGT family as SYS, rather than by attempting to recompile this customization package in isolation.