Search Results ego_item_user_attrs




Overview
Explore in AI Chat

Overview

EGO_PUB_FWK_PK, whose body is delivered by script EGOPFWKB.pls, is the publication framework engine within the Oracle E-Business Suite Product Information Management (PIM) product data hub. It coordinates the batch-oriented publication of item, catalog group, and catalog attribute changes from the working repository to downstream consuming systems. Publication batches are the transactional unit through which approved item master and item catalog data is staged, validated, and released; this package owns the lifecycle of those batches, including their creation, validation, persistence, status transition, copying, and deletion. Because the user-searched term ego_item_user_attrs relates to published item-level user attribute values, EGO_PUB_FWK_PK is the component that determines whether such attribute changes flow to the publication target or are rejected during batch validation. The package is classified as OTHER in the ETRM registry and is invoked primarily from the publication framework's concurrent programs and from the PIM HTML user interface, while seven other packages reference it, confirming its role as a shared framework service rather than an application-layer utility.

Key Procedures and Functions

The package exposes a compact public surface, with the remaining logic encapsulated in private validation and processing routines. The documented entry points are:

  • CREATE_BATCH — Establishes a new publication batch header and its associated entities and parameters, providing the batch identifier returned to the caller for subsequent processing.
  • PUBLISH_BATCH — Drives the actual publication of a batch to the configured target system, invoking the internal entity processing and status-update routines.
  • COPY_BATCH — Duplicates an existing batch, including its associated batch entities and parameters, so that a prior publication can be reused or reissued.
  • DELETE_BATCH — Removes a batch and its dependent rows from the publication framework tables, subject to status and validation constraints.
  • UPDATE_PUB_STATUS — Sets the publication status of a batch or of individual batch entities following validation, processing, or error handling.
  • UPDATE_PUB_STATUS_THRU_AIA — Propagates publication status changes received through Oracle Application Integration Architecture, allowing externally initiated status transitions to be reflected in the batch records.
  • ADD_DERIVED_ENTITIES — Adds derived batch entities to a batch using the internal derived entity object collection type, expanding a batch beyond the entities entered by the user.
  • DELETEGTTABLEDATA — Clears rows from the global temporary table used to stage publication data during a processing session, preventing stale state from carrying across requests.

Private routines referenced in the body include process_entities, Basic_Validation, validate_batch_id, validateStatus, valdiateBatSystem, validateBatSysEnt, Process_Pub_Status, and the function calc_return_status, which together implement batch validation and status resolution.

Tables Accessed

The package works almost exclusively against the EGO publication framework tables. EGO_PUB_BAT_HDR_B, EGO_PUB_BAT_HDR_S1, EGO_PUB_BAT_ENT_OBJS_B, and EGO_PUB_BAT_ENT_OBJS_S1 hold batch headers and batch entity objects; EGO_PUB_BAT_PARAMS_B and EGO_PUB_BAT_PARAMS_S1 hold batch parameters; EGO_PUB_BAT_STATUS_B holds status definitions. EGO_PUB_BAT_SYSTEMS_B records the target publication systems, while EGO_PUBLICATION_BATCH_GT is the global temporary table staged and cleared by DELETEGTTABLEDATA. External master data is resolved through EGO_MTL_CATALOG_GRP_VERS_B and MTL_ITEM_CATALOG_GROUPS_B for catalog group versions and assignments, MTL_BUSINESS_EVENTS_S for business event subscription metadata, and FND_USER and FND_RESPONSIBILITY for the submitting user and responsibility. DBMS_SQL is used for dynamic SQL construction during publication processing.

Usage Notes

EGO_PUB_FWK_PK is typically invoked from the PIM publication concurrent programs and the publish/copy/delete actions exposed in the item and catalog management HTML pages, where the caller supplies a batch identifier and receives the standard x_return_status, x_msg_count, and x_msg_data error-handling triple. Custom integrations that need to create or republish batches should call CREATE_BATCH or PUBLISH_BATCH and then inspect the returned status messages before committing. The ADD_DERIVED_ENTITIES routine is relevant when a batch must include entities implied by the primary selection rather than explicitly entered items. Because the package depends on FND_USER, FND_RESPONSIBILITY, and globally temporary staging data, it should be executed in a session with the correct responsibility context and should always be followed by DELETEGTTABLEDATA cleanup in long-running or looped batch processing.