Search Results c_param_type_batch




Overview
Explore in AI Chat

Overview

EGO_PUB_FWK_PK is the publication framework package within the Oracle E-Business Suite Product Information Management (PIM) / Oracle Product Hub module, owned by the APPS schema and classified as an OTHER API in ETRM. Its business purpose is to manage the lifecycle of publication batches — the mechanism by which master item and catalog data is published from a source system to one or more destination systems. The package header declares AUTHID CURRENT_USER, meaning that all SQL inside the package executes with the privileges of the invoking user rather than the definer, so callers must hold the necessary object grants for the underlying EGO tables. The package provides procedures to create a batch, copy a batch, publish batches, and delete batches, together with supporting status-update and derived-entity utilities. It relies on a set of package-level PL/SQL types, notably BAT_PARAM_REC_TYPE and TBL_OF_BAT_PARAM_TYPE, which carry batch parameter data such as workspace name and auto-release indicators. In the context of a user searching for "publish_batch", this package is the definitive entry point: PUBLISH_BATCH is the documented procedure that performs the actual publication of a batch.

Key Procedures and Functions

Eight procedures and functions are documented for this package:

  • PUBLISH_BATCH — Publishes an existing publication batch, driving the transfer of batch content to the designated destination systems. This is the procedure most often referenced by name in custom integrations.
  • CREATE_BATCH — Creates a new publication batch, establishing the batch header and associated parameter and entity records.
  • COPY_BATCH — Copies an existing batch so that its definition can be reused or modified without recreating it from scratch.
  • DELETE_BATCH — Deletes a batch and its associated framework records.
  • UPDATE_PUB_STATUS — Updates publication status information, keeping batch status consistent with processing outcomes.
  • UPDATE_PUB_STATUS_THRU_AIA — A variant of status updating invoked through the Application Integration Architecture (AIA) flow, used where publication is orchestrated by AIA rather than by direct call.
  • ADD_DERIVED_ENTITIES — Adds derived entities to a batch, expanding the set of objects to be published beyond those explicitly selected.
  • DELETEGTTABLEDATA — Clears data from the global temporary table used by the framework, supporting cleanup of working data between processing cycles.

Parameter handling is mediated by TBL_OF_BAT_PARAM_TYPE, whose entries carry param_name, char_value, number_value, date_value, data_type and param_type. Valid data types are C_NUMBER_TYPE, C_STRING_TYPE and C_DATE_TYPE; valid parameter types are C_PARAM_TYPE_BATCH and C_PARAM_TYPE_DEST. Documented parameters include C_PARAM_WKSPNAME (Workspace Name) and C_PARAM_AUTOREL (Auto-Release). The API validates the parameter name and value and then resets data_type and param_type to their correct values.

Tables Accessed

The package reads and writes the core publication batch tables through APPS synonyms: EGO_PUB_BAT_HDR_B and its sequence EGO_PUB_BAT_HDR_S1 (batch header), EGO_PUB_BAT_PARAMS_B and EGO_PUB_BAT_PARAMS_S1 (batch parameters), EGO_PUB_BAT_ENT_OBJS_B and EGO_PUB_BAT_ENT_OBJS_S1 (batch entity objects), EGO_PUB_BAT_STATUS_B (batch status), EGO_PUB_BAT_SYSTEMS_B (destination systems) and EGO_PUBLICATION_BATCH_GT (the global temporary working table cleared by DELETEGTTABLEDATA). It also consults FND_USER and FND_RESPONSIBILITY for user and responsibility context, MTL_BUSINESS_EVENTS_S and MTL_ITEM_CATALOG_GROUPS_B for business event and catalog group information, EGO_MTL_CATALOG_GRP_VERS_B for catalog group versions, and DBMS_SQL for dynamic SQL execution.

Usage Notes

EGO_PUB_FWK_PK is typically invoked from the Oracle Product Hub publication UI, from concurrent programs that process publication batches, and through AIA-mediated integration flows for enterprise-wide publication. Seven other packages reference it, confirming it as a shared framework dependency rather than a standalone module API. Custom code calling PUBLISH_BATCH, CREATE_BATCH, COPY_BATCH or DELETE_BATCH should supply batch parameters through TBL_OF_BAT_PARAM_TYPE, observe the documented data_type and param_type conventions, and accept that the API will normalize those attributes internally. Because the package is AUTHID CURRENT_USER, custom callers should verify grants on the underlying EGO tables and avoid assuming APPS-level privileges are inherited. Status synchronization should generally be performed through UPDATE_PUB_STATUS or UPDATE_PUB_STATUS_THRU_AIA rather than by direct DML against EGO_PUB_BAT_STATUS_B.