Search Results ego_com_attr_validation




Overview
Explore in AI Chat

Overview

EGO_COM_ATTR_VALIDATION is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in ETRM as an "OTHER" API. It belongs to the EGO (E-Business Suite eCommerce and Product Information Management) module family and provides the server-side validation engine for user-defined attribute groups. In Oracle EBS 12.1.1 and 12.2.2, extensible attributes are attached to business entities such as items, item categories, and trading partners through attribute groups defined in the EGO schema. Before any attribute value set is committed, the values must be validated against the metadata (data type, value set, required flags, and defaulting rules) that governs each attribute in the group.

This package centralizes that validation logic. It accepts a set of attribute name/value pairs, resolves effective values — including values sourced from the database when not supplied by the caller — and returns a status code together with a structured array of error messages. It also supports validation of default component attributes, allowing the caller to pre-validate a primary key context rather than a full attribute payload. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, a deliberate choice that preserves EBS security semantics for the calling session.

Key Procedures and Functions

Four documented entry points are exposed by the package specification:

  • VALIDATE_ATTRIBUTES — The primary validation procedure. It accepts an attribute group identifier (type, name, and ID), a collection of user attribute name/value pairs, and an optional collection of primary key column name/value pairs. It returns an overall return status and an error message collection, enabling the caller to surface validation failures to the user.
  • GET_ATTR_VALUE_FROM_DB — A function that resolves the stored value of a named attribute for a given attribute group. Because attribute values are keyed by primary key context, the function consults the database when the caller's in-memory value collection does not contain the attribute, returning the value as a VARCHAR2.
  • IS_ATTRIBUTE_GROUP_TELCO — A boolean function that determines whether the named attribute group is of Telco (telecommunications industry) type. This is the function directly relevant to the search term "is_attribute_group_telco." It allows generic validation and rendering logic to branch for Telco-specific attribute behavior without hard-coding group names.
  • VALIDATE_DEFAULT_COMPATTR — A procedure that validates default component attributes against an optional primary key column name/value collection, returning status and error messages. It is used when the system must confirm that defaulting rules can be satisfied before attribute data is persisted.

Tables Accessed

Two database objects are documented as referenced through APPS synonyms:

  • EGO_FND_DSC_FLX_CTX_EXT — The extension table that stores attribute metadata and contextual attribute definitions for flexfield-based descriptive attribute groups. The package reads this table to resolve attribute definitions, Telco classification, and stored values.
  • PLITBLM — The standard EBS PL/SQL table used for message handling and error text resolution, referenced when populating the error message collection returned to callers.

Usage Notes

EGO_COM_ATTR_VALIDATION is not documented as being referenced by any other package, indicating that it is invoked directly by forms, OAF pages, or custom integration code rather than being part of a nested internal call chain. In typical EBS usage, it is called whenever attribute data must be validated before insert or update — for example, when an item attribute form saves user-entered extensible attribute values, or when a concurrent program validates a batch of attribute records. Custom code using the package should declare variables of the documented collection types (ego_user_attr_data_table and ego_col_name_value_pair_array) and should check x_return_status before proceeding. Because the specification header dates to 2009 and the compilation stamp is 120.0.12010000.3, the interface is stable across 12.1.1 and 12.2.2; direct calls to IS_ATTRIBUTE_GROUP_TELCO should account for its boolean return type, which is not directly bindable in SQL.