Search Results eni_items_star_pkg




Overview
Explore in AI Chat

Overview

The concurrent program ENI_ITEMS_STAR_PKG is delivered as part of the ENI – Product Intelligence product family within Oracle E-Business Suite. It is exposed to end users under the user-facing name “Load Item Dimension Hierarchy”. Functionally, the program updates existing items into a dimensional structure — specifically, it populates or refreshes the item star schema (dimension) used by Product Intelligence analytics and reporting. The metadata description recorded in ETRM 12.2.2 describes the program as “Update existing items into dimension,” confirming its role as a data-load utility rather than a transactional or inquiry program.

In ETRM 12.2.2 the ENI Product Intelligence module is flagged as Obsolete, Enabled: Yes. This designation indicates that while the program remains active and submittable, Oracle has superseded the broader Product Intelligence functionality in later releases. Customers on 12.1.1 and 12.2.2 should treat ENI_ITEMS_STAR_PKG as a legacy integration object and verify its continued applicability before relying on it in new implementations.

Execution Details

The documented execution attributes are consistent across the ENI documentation set:

  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: ENI_ITEMS_STAR_PKG
  • Execution Filename: ENI_ITEMS_STAR_PKG.CREATE_STAR_TABLE
  • Subroutine Name: (not populated)
  • Enabled: Yes

The execution filename reveals the internal entry point invoked by the concurrent manager: the packaged procedure ENI_ITEMS_STAR_PKG.CREATE_STAR_TABLE. Because the execution method is PL/SQL Stored Procedure with a Standard argument method, the program accepts runtime parameters passed as a standard concurrent program argument list, which are bound into the called package procedure at submission time.

How to Run

Users submit ENI_ITEMS_STAR_PKG through the standard Submit Request (SRS) window, filtering on the request name Load Item Dimension Hierarchy under the ENI – Product Intelligence application. Because the execution method is a stored procedure, no report layout or output file template is associated; output is limited to the concurrent manager log and, potentially, PL/SQL output written by the package.

The Standard argument method implies that parameters are defined at the concurrent program level rather than resolved dynamically from a report definition. Administrators should inspect the Parameters zone of the concurrent program definition in the Applications Developer responsibility to enumerate the exact arguments required (for example, organization or item range selectors, or a mode-of-operation flag). General guidance:

  • Run during off-peak windows; a dimension load can be resource-intensive on large item masters.
  • Confirm that the ENI Product Intelligence schema and any related interface staging tables are accessible and populated before submission.
  • Review the request log for errors, since a stored-procedure program will not produce a formatted report to diagnose failures.
  • Because the module is marked Obsolete, validate the necessity of the load against current reporting requirements.

Related Objects

The program executes the ENI_ITEMS_STAR_PKG package, and its entry point is CREATE_STAR_TABLE. Related artifacts typically include:

  • ENI_ITEMS_STAR_PKG — the PL/SQL package itself, containing the dimensional load logic.
  • Item dimension / star schema tables owned by the ENI schema, which receive the refreshed item records.
  • Item master interface and staging structures used to feed the dimension load.
  • Sibling ENI concurrent programs that build or refresh other Product Intelligence dimensions and hierarchies, which should be sequenced appropriately when run as a set.

Given the limited published metadata, implementers should confirm exact table and package dependencies directly in the database using the data dictionary before scheduling the program.