Results for “delete_column”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CN_SYS_TABLES_PVT is a private PL/SQL package in the Oracle EBS APPS schema that belongs to the Oracle Engineering / Product Lifecycle Management data model (the CN_* table family, historically associated with the "CN" application used by Oracle's Product Development Exchange and related configuration products). The package encapsulates the low-level create, read, update, and delete logic for user-defined table metadata — that is, for the "system tables" that describe how object structures are physically represented and related within a configured repository.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer. This design is deliberate: the routines inspect data dictionary views such as ALL_OBJECTS, ALL_TAB_COLUMNS, and ALL_USERS, which return results scoped to the invoking user. It is classified as a "PVT" (private) API, indicating that it is intended for internal consumption by a companion public API package — specifically, it is referenced by one other package documented in the ETRM repository. It is not a public, supported integration surface for customer code.

Key Procedures and Functions

The package exposes six documented procedures, organized around two record structures: a table-level record derived from CN_OBJECTS, and a column-level record also anchored to CN_OBJECTS. Together they provide symmetrical maintenance of table and column metadata.

• CREATE_TABLE — Creates the metadata record for a table in CN_OBJECTS and simultaneously creates the associated column definitions. This is the primary entry point of the package, and the header comments document the standard EBS API parameter convention (p_api_version, p_init_msg_list, p_commit, p_validation_level) together with the table record.
• UPDATE_TABLE — Modifies an existing table's metadata attributes (name, description, status, alias, schema, and related flags) within the CN_OBJECTS repository.
• DELETE_TABLE — Removes a previously defined table and its dependent metadata from the repository.
• INSERT_COLUMN — Adds a single column definition to an existing table's structure, capturing datatype, position, value set, key and foreign-key flags, and dimension linkage.
• UPDATE_COLUMN — Changes the attributes of an existing column definition without recreating it.
• DELETE_COLUMN — Removes a column definition from a table's structure.

Tables Accessed

The package reads and writes the core CN metadata repository. CN_OBJECTS and its sequence-backed surrogate CN_OBJECTS_S / CN_OBJECTS_S1 store the master object definitions used by both the table and column record types. CN_ATTRIBUTE_RULES supplies attribute-level rules associated with object columns, while CN_DIMENSIONS and CN_REPOSITORIES provide the dimensional context and repository ownership for each object. CN_TABLE_MAPS_ALL holds the table-to-object mapping used when resolving physical tables against logical definitions.

Data dictionary views — ALL_OBJECTS, ALL_TAB_COLUMNS, ALL_USERS — are consulted to validate that referenced physical tables, columns, and schemas actually exist and are visible to the current user. DUAL and USER_SYNONYMS are used for lightweight lookups and synonym resolution. Because these dictionary views are user-scoped, the AUTHID CURRENT_USER declaration is essential to correct behaviour.

Usage Notes

As a private package, CN_SYS_TABLES_PVT is not intended for direct invocation from forms, concurrent programs, or customer extensions. It is called by its single documented referrer package, which presents the supported public interface. In EBS 12.1.1 and 12.2.2 the CN data model is largely dormant for most installations, and the package executes only when tables and columns are being defined or maintained within a configured repository.

The search term "package com.intellect.interfaces.fileprocessor.encryption" is a Java namespace and has no relationship to this PL/SQL package; it reflects a custom Java integration layer (the "intellect" vendor namespace) rather than any Oracle EBS API. Custom code requiring the same functionality should use the public wrapper, not this private package, since Oracle does not guarantee the private interface across patches.