Search Results execute_openinterface

Overview

CSI_ML_PROGRAM_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PUBLIC API within the ETRM (E-Business Suite Table and API Repository) metadata. The package supports the Oracle Install Base foundation of Oracle Enterprise Asset Management (eAM) and related CSI (Customer Service Intelligence) application modules by providing programmatic entry points for processing Install Base interface data. Specifically, it serves as the wrapper or driver used by the Install Base open interface and parallel asset creation processes, allowing bulk loads of asset, instance, party, and relationship data to be brought into the Install Base repository through the staging and interface tables.

In release 12.1.1 and 12.2.2, the package forms part of the standard Install Base public API set that abstracts the low-level interface table structures from callers, enabling concurrent programs, forms, and custom integrators to submit work without directly manipulating the underlying interface tables.

Key Procedures and Functions

The documented ETRM metadata identifies two public procedures:

• EXECUTE_OPENINTERFACE — Invokes the Install Base open interface process. Its purpose is to trigger the loading and validation of records staged in the CSI interface tables, driving the transfer of external asset and instance data into the Install Base schema.
• EXECUTE_PARALLEL_CREATE — Initiates parallel creation of Install Base entities. This procedure supports high-volume processing by dividing asset creation work across multiple worker processes, improving throughput for large data loads or batch conversions.

Parameter lists are not published in the supplied metadata and are therefore not reproduced here. Callers should derive exact signatures from the package specification in the database (APPS.CSI_ML_PROGRAM_PUB) rather than relying on external references.

Tables Accessed

The package interacts with the following documented tables, accessed through APPS synonyms:

• CSI_I_ASSET_INTERFACE — Staging table for asset records, used as the source of asset data to be validated and created in Install Base.
• CSI_INSTANCE_INTERFACE — Stores instance-level data for asset instances during the open interface cycle.
• CSI_I_PARTY_INTERFACE — Holds party interface records linking assets to the parties that own or are associated with them.
• CSI_II_RELATION_INTERFACE — Captures relationship interface data between Installed Base entities.
• CSI_IEA_VALUE_INTERFACE — Stores attribute value interface rows (e.g., instance attributes) to be applied to created assets.
• PLITBLM — A generic PL/SQL table (index-by table) structure commonly used within EBS APIs for passing arrays or collections internally.

These interface tables collectively feed the Install Base open interface and parallel creation flows, which subsequently populate the production CSI tables. No other packages reference CSI_ML_PROGRAM_PUB, indicating it is a top-level driver intended to be invoked directly by concurrent programs or external callers.

Usage Notes

In typical EBS deployments, CSI_ML_PROGRAM_PUB is invoked indirectly through the Install Base open interface concurrent programs, such as the Asset Open Interface and related parallel creation concurrent requests. Because ETRM classifies it as a PUBLIC (PUB) API, it is also considered safe for custom code and external integrations to call directly, provided that input interface tables are populated correctly and validation errors are captured via the standard open interface error tables.

Users integrating external asset data (for example, loading legacy asset records during an upgrade or interfacing from third-party asset systems) would populate the CSI interface tables, then call EXECUTE_OPENINTERFACE to load the data and EXECUTE_PARALLEL_CREATE to generate Install Base records at scale. Because it is a standalone driver with no dependent packages, it can be scheduled as a concurrent program or invoked from a submission script. As with all Install Base APIs, processing should be performed while users are not actively maintaining the affected records, and results should be reviewed through the standard interface error reports.