Search Results update_content_type

Overview

IBC_CTYPE_PVT is a private PL/SQL package in the APPS schema that implements the business logic layer for iProcurement content type and attribute type administration. It supports the definition and maintenance of content types, which classify catalog content and control how items, attributes, and flexfield-based validation are presented to users within Oracle iProcurement. The package encapsulates create, update, and delete operations against the IBC_CONTENT_TYPES and IBC_ATTRIBUTE_TYPES entities, and provides helper routines for retrieving content type records and for resolving flexfield value sets into usable SQL for validation. Its classification as a PVT (private) package indicates that it is not part of the published, externally supported API surface; it is intended for internal consumption by other iProcurement packages rather than by customer extensions. In Oracle EBS 12.1.1 and 12.2.2, the package status is VALID and it is documented in the ETRM repository as a dependency-bearing unit that relies on the FND_API framework and JTF collection types.

Key Procedures and Functions

The package exposes nine documented procedures and functions, summarized below. Parameter signatures are intentionally not reproduced here.

• CREATE_CONTENT_TYPE — Creates a new content type definition, including its base and translated rows.
• UPDATE_CONTENT_TYPE — Modifies an existing content type definition.
• DELETE_CONTENT_TYPE — Removes a content type and its dependent attribute type associations.
• GET_CTYPE_REC — Retrieves the full record for a content type, typically returning entity attributes used by callers.
• CREATE_ATTRIBUTE_TYPE — Creates an attribute type associated with a content type.
• GET_ATTRIBUTE_TYPE_LOV — Returns a list of values for attribute types, suitable for use in forms and selection dialogs.
• GET_CONTENT_TYPE — Returns content type information, likely in a lightweight form for lookups.
• IS_VALID_FLEX_VALUE — Validates a given value against a flexfield value set.
• GET_SQL_FROM_FLEX — Derives a SQL predicate from a flexfield definition, enabling dynamic validation at runtime.

Tables Accessed

The package reads and writes several iProcurement and Application Object Library tables via APPS synonyms. Content type definitions are stored in IBC_CONTENT_TYPES_B (base) and IBC_CONTENT_TYPES_TL (translated), while attribute type definitions reside in IBC_ATTRIBUTE_TYPES_B and IBC_ATTRIBUTE_TYPES_TL. Flexfield validation logic draws on FND_FLEX_VALIDATION_TABLES and FND_FLEX_VALUE_SETS, and language-specific handling uses FND_LANGUAGES. Infrastructure references include DBMS_TRANSACTION for transactional control and PLITBLM for internal PL/SQL table support. The JTF_* collection types (JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100/300/2000) are used for bulk parameter passing, and FND_API provides the standard EBS API error-handling framework.

Usage Notes

IBC_CTYPE_PVT is invoked internally by IBC_CITEM_ADMIN_GRP and is referenced by one other package within iProcurement. It is not intended for direct calls from customizations; customers requiring content type administration should use the supported iProcurement administration forms, which ultimately route through this logic. Because it depends on FND_API for error handling and on flexfield views and value sets, any call context must initialize the FND global variables and, where relevant, set the org context. The package's self-referential dependency suggests internal helper routines are shared across its procedures. In 12.1.1 and 12.2.2 the package remains valid and unchanged in its documented interface.