Search Results l_conc_ret_sts_success
Overview
EGO_ITEM_USER_ATTRS_CP_PUB is a public PL/SQL package body in the APPS schema that supports the Oracle E-Business Suite Product Information Management (PIM) item user-attribute framework. Its principal business function is to process item user-defined attribute data submitted through the item import and item copy pipelines, applying validation, security filtering, and attribute-change logic before records are written to the interface tables that feed the item master. The package carries the source header EGOCIUAB.pls and is versioned as a public API (API classification PUB), meaning it is intended for invocation by other application modules, concurrent programs, and integrators.
The package declares an extensive set of private globals that document its runtime contract. Debug logging constants map to FND_LOG levels, concurrent return status constants (L_CONC_RET_STS_SUCCESS, L_CONC_RET_STS_WARNING, L_CONC_RET_STS_ERROR) define a 0/1/2 return-code convention, and G_ITEM_NAME fixes the item object identifier as EGO_ITEM. The error-handler globals (G_ENTITY_ID, G_ENTITY_CODE, G_HZ_PARTY_ID) indicate integration with the EGO entity/error infrastructure. The exception names G_NO_CURRVAL_YET and G_NO_USER_NAME_TO_VALIDATE reveal that sequence management and user-name validation are internal concerns. The table-name global G_TABLE_NAME defaults to EGO_ITM_USR_ATTR_INTRFC (tagged BUG 5352217), confirming the interface table as the primary staging target.
Key Procedures and Functions
- GET_ITEM_SECURITY_PREDICATE — Constructs a security predicate used to restrict the item user-attribute rows visible to the calling context, applying organization and user-level access rules.
- PROCESS_ITEM_USER_ATTRS_DATA — The central driver that ingests item user-attribute data, performs validation and transformation, and stages the results for downstream processing.
- GET_RELATED_CLASS_CODES — Retrieves related item class codes, supporting class-driven attribute resolution during import or copy operations.
- IMPL_ITEM_ATTR_CHANGE_LINE — Implements the attribute-change line logic applied when user attributes on an existing item are modified, ensuring interface rows reflect the delta.
- COPY_DATA_TO_INTF — Moves processed user-attribute data into the interface table so that the standard item import concurrent program can consume it.
Tables Accessed
The package reads and writes a broad set of EGO and FND synonyms. Interface and association tables — EGO_ITM_USR_ATTR_INTRFC, EGO_ITEM_ASSOCIATIONS, and EGO_ITEM_ASSOCIATIONS_INTF — are the primary staging and relationship targets. Attribute modeling metadata is drawn from EGO_ATTR_GROUP_DL, EGO_VALUE_SET_EXT, EGO_VS_VALUES_DISP_ORDER, and EGO_FND_DF_COL_USGS_EXT, while flexfield context and column usage definitions come from EGO_FND_DSC_FLX_CTX_EXT and FND_DESCR_FLEX_COLUMN_USAGES. Item and style data are resolved through EGO_MTL_SY_ITEMS_EXT_B, EGO_STYLE_VARIANT_ATTR_VS, EGO_DATA_LEVEL_B, and EGO_OBJ_TYPE_LIFECYCLES. Import behavior is controlled via EGO_IMPORT_COPY_OPTIONS and EGO_IMPORT_OPTION_SETS.
Usage Notes
The package is invoked from the item import and item copy flows, typically from concurrent programs or the PIM item maintenance forms, and is referenced by five other packages within the EGO module. Custom code should call only the documented public procedures and treat the private globals and helper routines as internal. The search term g_ps_in_process is a naming convention for a private package global state flag used to guard re-entrant processing; it is not a public API. Integrators should not depend on it, as it may change between 12.1.1 and 12.2.2 patch levels.