Search Results ibc_attribute_types_pkg




Overview
Explore in AI Chat

Overview

IBC_ATTRIBUTE_TYPES_PKG is the table handler package for the IBC_ATTRIBUTE_TYPES entity within the Oracle E-Business Suite. The IBC schema supports the configuration and definition of attribute types used by content types in the Oracle iProcurement and related self-service procurement modules. Attribute types define the metadata characteristics of attributes that can be associated with content—such as their data type, length, default values, validation rules, minimum and maximum instance counts, and display ordering. This package encapsulates the standard insert, update, delete, lock, and load operations required to maintain rows in the underlying IBC_ATTRIBUTE_TYPES_B and IBC_ATTRIBUTE_TYPES_TL tables.

The package header declares AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is consistent with standard EBS table handler conventions. The header revision history indicates the package was created in January 2002 and has been maintained through multiple updates, including adaptations for the FND_API.G_MISS_XXX constants, OA Framework UI overloads, NOCOPY hint optimization for OUT and IN OUT parameters, and the R12 Load/Translation standards for the LCT (Load, Configuration, Translation) framework.

Key Procedures and Functions

The documented package exposes thirteen procedures that provide the complete lifecycle management for attribute type records:

  • INSERT_ROW — Creates a new attribute type record, accepting values for attribute type code, content type code, data type code, data length, minimum and maximum instance counts, reference code, default value, updateable flag, object version number, name, description, audit columns, display order, and flex value set identifier.
  • LOCK_ROW — Obtains a pessimistic lock on an existing attribute type row to prevent concurrent modification, validating the current object version number before allowing update or delete operations.
  • UPDATE_ROW — Modifies the mutable columns of an existing attribute type record, enforcing optimistic concurrency control.
  • DELETE_ROW — Removes a single attribute type record identified by its primary key.
  • DELETE_ROWS — Removes multiple attribute type records, typically used for bulk cleanup operations.
  • LOAD_ROW — Loads a single attribute type definition from seed data using the R12 standard loading mechanism.
  • LOAD_SEED_ROW — A variant created specifically for R12 LCT standards, used for loading seed data rows during patching and installation.
  • TRANSLATE_ROW — Provides translation support for the translatable columns of the attribute type, writing to the _TL table.
  • ADD_LANGUAGE — Inserts language-specific rows into the translated table for newly installed or enabled languages.

Tables Accessed

The package maintains data across three documented tables accessed through APPS synonyms:

  • IBC_ATTRIBUTE_TYPES_B — The base table storing the primary, language-independent attributes of each attribute type, including data type, length, instance constraints, default values, and validation references.
  • IBC_ATTRIBUTE_TYPES_TL — The translation table storing language-specific values such as attribute type name and description, keyed by language and source language.
  • FND_LANGUAGES — Referenced during ADD_LANGUAGE operations to determine the set of installed and active languages for which translation rows must be created.

Usage Notes

IBC_ATTRIBUTE_TYPES_PKG is typically invoked indirectly rather than called directly by end users. It serves as the programmatic interface behind the Oracle iProcurement attribute type setup forms, where administrators define and maintain attribute types associated with content types. It is also called by concurrent programs and seed data loaders during implementation and patching, particularly through the LOAD_ROW, LOAD_SEED_ROW, and TRANSLATE_ROW procedures that conform to the R12 Load and Translation standards.

The package is referenced by two other packages, indicating that it provides downstream services to additional IBC configuration components. Custom code and extensions that must insert or maintain attribute type definitions should use these procedures rather than performing direct DML against the base and translation tables, ensuring that object version numbers, audit columns, and concurrent locking semantics are handled consistently. The NOCOPY hint on OUT and IN OUT parameters improves performance for large or complex invocations, though callers should be aware that this permits the parameter values to be modified mid-execution in the event of an unhandled exception.