Search Results create_params_attribute_group

Overview

EGO_PUB_WS_AG is the attribute group exploder package within the Oracle E-Business Suite Product Information Management (PIM) and Oracle Data Librarian (ODI) integration stack. Its business purpose is to take an incoming XML payload describing one or more attribute groups — the logical containers that organize item attributes, value sets, and descriptive flexfield context information — and expand, or "explode," those groupings into the individual end-value-set rows that downstream synchronization processes require. This explosion step is essential because attribute groups are hierarchical definitions, whereas the target EGO and ODI staging tables operate at a granular, per-entity, per-value-set level.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the APPS owning schema. This design is consistent with its role as a utility invoked from Java wrappers, concurrent programs, and other PL/SQL callers that already operate within an authenticated session context. Its header identifies it as file EGOWSAGS.pls, shipped under the EGOPAGS.pls header line.

Key Procedures and Functions

• CREATE_PARAMS_ATTRIBUTE_GROUP — Accepts a session identifier and establishes the parameter scaffolding required for an attribute group operation. It prepares the working context that the subsequent pre-processing and explosion steps consume.
• PREPROCESS_INPUT_ATTRGROUP — Performs the pre-processing of the input XML for an entity type of Attribute Group. Its documented actions are: (1) reading the input parameters held in the XML payload stored in EGO_PUB_WS_PARAMS by session_id and transferring them into EGO_PUB_WS_CONFIG; (2) populating the ODI input table EGO_ODI_SYNC_ENTITIES for entity AG according to the invocation type, such as batch or list; and (3) exploding the attribute group across all end-value-sets that must be processed. The session identifier originates as a unique database sequence generated by the Java wrapper.
• EXPLODE_ATTRIBUTE_GROUP — Performs the core expansion of a single attribute group into its constituent end-value-set rows, making each generated element individually addressable by the subsequent synchronization logic.

Tables Accessed

The package reads and writes the published web service staging and metadata tables through APPS synonyms:

• EGO_PUB_WS_PARAMS — Holds the raw input parameters extracted from the XML payload, keyed by session_id.
• EGO_PUB_WS_CONFIG — Receives the copied parameter values that drive the current run configuration.
• EGO_PUB_WS_ENTITIES and EGO_PUB_WS_ENTITIES_S — Store the web service entity definitions, including attribute group entities.
• EGO_PUB_WS_INPUT_IDENTIFIERS — Resolves the identifiers supplied in the invocation.
• EGO_PUB_BAT_ENTS_B and EGO_PUB_BAT_PARAMS_B — Batch definition and batch parameter tables used when the invocation type is batch.
• EGO_VALUE_SET_EXT, FND_FLEX_VALUE_SETS, and FND_DESCR_FLEX_COLUMN_USAGES — Supply value set and descriptive flexfield column usage metadata that determine which end-value-sets the explosion must reach.
• EGO_FND_DF_COL_USGS_EXT and EGO_FND_DSC_FLX_CTX_EXT — Extended flexfield column usage and context information.
• DBMS_SQL, DBMS_UTILITY, and DUAL — Oracle-supplied utilities used for dynamic SQL construction and supporting operations.

Usage Notes

EGO_PUB_WS_AG is not exposed as an end-user form function. It is invoked programmatically, most commonly from the Java wrapper service layer that creates the session identifier, and from concurrent programs or custom PL/SQL that publish or synchronize attribute group definitions. The expected calling sequence begins with CREATE_PARAMS_ATTRIBUTE_GROUP, proceeds through PREPROCESS_INPUT_ATTRGROUP, and completes with EXPLODE_ATTRIBUTE_GROUP. The package is referenced by one other package in the ETRM metadata, confirming its role as an internal dependency of the EGO web services layer rather than a standalone API.

In Oracle EBS 12.1.1 and 12.2.2, the version stamp (120.2) and "noship" flag indicate the file is an internal, non-shipped-in-UI component that may change under patch. Custom code should therefore call the package only at the documented entry points and should never rely on internal cursor or global variable behavior.