Search Results create_attribute_type
Overview
IBC_CTYPE_PVT is the private implementation package that underpins the ETRM (Electronic Technical Reference Manual) content-type and attribute-type registration model in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose, reflected in the source header of ibcvctyb.pls (version 120.2, dated 2005/06/01), is to provide an API to populate and maintain content types and their associated attribute types. The package supplies the procedural foundation on which the public-facing content-type API layer relies, handling record validation, surrogate key management, multi-language translation rows, and flexfield-backed value derivation for attribute definitions.
The package is classified as a PVT (private) API, confirming that it is not intended for direct invocation by external integrators; it is called by sibling or higher-level packages within the same product family. The ETRM metadata records a single dependent package referencing IBC_CTYPE_PVT, which reinforces its role as an internal service layer.
Key Procedures and Functions
The documented API surface comprises nine procedures and functions:
- CREATE_CONTENT_TYPE — Inserts a new content type definition, including its base row and any required translated description rows.
- UPDATE_CONTENT_TYPE — Modifies an existing content type record, applying validation according to the requested validation level.
- DELETE_CONTENT_TYPE — Removes a content type and its dependent translation and attribute relationships.
- GET_CTYPE_REC — Returns a single content type record structure for a given content type identifier, used primarily for read-back and edit flows.
- CREATE_ATTRIBUTE_TYPE — Creates an attribute type associated with a content type code; this is the operation most directly related to the searched term "create_attribute_type".
- GET_ATTRIBUTE_TYPE_LOV — Populates a list-of-values result set of valid attribute types, typically for use by an Oracle Forms LOV.
- GET_CONTENT_TYPE — Retrieves content type data, either as a record or a derived result, for downstream processing.
- IS_VALID_FLEX_VALUE — Validates a supplied value against a flexfield value set, ensuring attribute values conform to registered validation rules.
- GET_SQL_FROM_FLEX — Added in the 01/06/2004 revision; derives a SQL fragment from a flexfield definition so that attribute values can be resolved dynamically.
The package also defines supporting private helpers, including Update_Attribute_Type, Delete_Attribute_Type, Query_attribute_type_row, and IsATypeRecordEmpty, which perform record-level existence and emptiness checks against the Attribute_Type_Rec_Type structure before DML is attempted.
Tables Accessed
The package reads and writes a defined set of APPS-synonymed tables:
- IBC_CONTENT_TYPES_B and IBC_CONTENT_TYPES_TL — base and translated content type definitions, written on create/update/delete.
- IBC_ATTRIBUTE_TYPES_B and IBC_ATTRIBUTE_TYPES_TL — base and translated attribute type definitions, written by CREATE_ATTRIBUTE_TYPE and read by the LOV function.
- FND_FLEX_VALUE_SETS, FND_FLEX_VALIDATION_TABLES, and FND_LANGUAGES — read for flexfield validation and language resolution.
- DBMS_TRANSACTION and PLITBLM — system facilities used for transaction control and PL/SQL table handling.
Usage Notes
Because IBC_CTYPE_PVT is a PVT-classified package, it is invoked through the public ETRM content-type API rather than called directly. Typical invocation paths include Oracle Forms-based maintenance screens that create and edit content types and their attributes, concurrent programs that populate ETRM metadata, and custom extensions that must conform to the same validation and translation model. Callers should expect standard ETRM API semantics: initialization of the message list, a commit indicator, a validation level, and OUT parameters carrying return status, message count, and message data. Direct DML against the underlying tables should be avoided so that translation rows, flexfield validation, and record-level consistency checks performed by the package are preserved.
-
PACKAGE BODY: APPS.IBC_CTYPE_PVT
12.1.1
-
PACKAGE BODY: APPS.IBC_CTYPE_PVT
12.2.2
-
PACKAGE: APPS.IBC_CTYPE_PVT
12.2.2
-
PACKAGE: APPS.IBC_CTYPE_PVT
12.1.1
-
APPS.IBC_CTYPE_PVT dependencies on FND_API
12.2.2
-
APPS.IBC_CTYPE_PVT dependencies on FND_API
12.1.1
-
APPS.IBC_CTYPE_PVT dependencies on FND_API
12.2.2
-
APPS.IBC_CTYPE_PVT dependencies on FND_API
12.1.1
-
APPS.IBC_CTYPE_PVT dependencies on IBC_CTYPE_PVT
12.1.1
-
APPS.IBC_CTYPE_PVT dependencies on IBC_CTYPE_PVT
12.2.2