Results for “populate_summary_table”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OE_BIS_CUST_SAT_SUMMARY is an Oracle E-Business Suite PL/SQL package that belongs to the Order Management (OE) module's Business Intelligence System (BIS) component. Its purpose is to support customer satisfaction analysis by consolidating and summarizing order-related data into a structure suitable for reporting and analytical review. The package forms part of the Order Management intelligence layer, which aggregates transactional activity into summary-level information used by Oracle BIS reporting and customer satisfaction tracking.

The package is defined with the AUTHID CURRENT_USER clause, meaning its stored procedures execute with the privileges of the invoking user rather than the package owner. This has practical implications for schema access and synonym resolution at runtime, particularly in environments where custom reporting or interval processing runs under a non-APPS account. The source header (OEXBCSSS.pls 115.3, dated 1999) indicates the package originates from an early release lineage and has been carried forward through subsequent EBS versions, including 12.1.1 and 12.2.2, where it is classified under the ETRM "OTHER" API category.

Key Procedures and Functions

The package exposes four documented public procedures. Consistent with the published metadata, parameter lists are not restated here; the descriptions below reflect purpose only.

• LOAD_SUMMARY_INFO — The primary loader procedure responsible for populating the customer satisfaction summary structures from the underlying order data. It performs the initial aggregation pass that drives the summary tables used by BIS reporting.
• LOAD_SUMMARY_INFO2 — A parallel or secondary loader variant. Its numbering suggests it handles an alternate data set, an additional summary dimension, or a subsequent processing phase distinct from the first loader.
• POPULATE_SUMMARY_TABLE — Populates the summary table, accepting an error number and error message as output parameters. This standard EBS error-handling convention allows the calling program to detect and report failures during population.
• POPULATE_SUMMARY_TABLE2 — The companion population routine to the first, likewise returning an error number and error message. It supports a second summary target or an extended population path.

Tables Accessed

The ETRM metadata for this object does not enumerate the specific tables referenced through APPS synonyms. Based on the package's name, module affiliation, and procedure naming, the package is intended to read from Order Management transactional tables and write to customer satisfaction summary tables within the BIS reporting schema. Because table-level mappings are not documented in the provided metadata, administrators should verify actual object dependencies in their instance using ALL_DEPENDENCIES or USER_DEPENDENCIES before relying on assumptions about the underlying data model. No other packages are documented as referencing this package, indicating it is typically a top-level invoker rather than a shared utility.

Usage Notes

OE_BIS_CUST_SAT_SUMMARY is generally invoked through Oracle Order Management BIS concurrent programs or scheduled batch processes that refresh customer satisfaction summary data. Typical invocation patterns include:

• Concurrent Program Execution — Run through the standard concurrent manager when refreshing BIS summary content.
• Scheduled Batch Jobs — Called on a periodic cycle to regenerate summary data for analytical reporting.
• Custom Code and Extensions — Because the procedures return error number and message outputs, they can be wrapped in custom PL/SQL that handles error capture and logging.

The user search term "Summet enterprises" (likely "Summit Enterprises") does not correspond to an EBS schema object but may reflect a customer or organization name queried in the context of customer satisfaction reporting. As with any BIS summary package, invocation should be sequenced after the underlying Order Management data is complete for the reporting period to avoid partial aggregates.