Search Results create_relationships

Overview

CSI_ML_CREATE_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Create Instances processing engine of Oracle's Installed Base / Asset Tracking functionality. The package belongs to the CSI (Customer Service Intelligence / Installed Base) module family and is closely associated with the CSI mass-load and mass-create processing components that transform transactional and interface data into installed base instances and the relationships between them. In Oracle EBS 12.1.1 and 12.2.2, the package is used to drive batch creation of installed base records from staging/interface data, particularly where source system information and transaction date ranges define the scope of processing.

The "_ML_" component of the package name denotes the multi-lingual or multi-load processing context, and the "_PUB" suffix confirms it is a public API classified for external invocation. The package exposes procedures invoked by concurrent programs or other orchestration code rather than by end users directly through a form.

Key Procedures and Functions

The documented package exposes three public procedures. Actual parameter lists are defined in the package specification and should be validated against the target environment; the descriptions below describe purpose only.

• create_instances — The primary driver procedure that creates installed base instances for a given transaction date range, batch name, and source system. It accepts transaction-from and transaction-to dates, a batch name, a source system name, and a resolve-IDs indicator, and returns a return status plus message data to the caller. This procedure is the main entry point for a mass instance creation run.
• create_parallel_instances — A worker-oriented variant of instance creation intended for parallel processing. It accepts transaction date bounds, a source system name, and a worker ID (alongside the standard return status and message data outputs), allowing the parent process to partition the workload across multiple concurrent workers. It omits the batch name and accepts a worker identifier instead.
• create_relationships — Creates the relationship records that link newly created (or existing) installed base instances according to the source transaction data. It accepts transaction-from and transaction-to dates and a source system name, and returns a return status and message data. This procedure is the direct resolution target for the search term "create_relationships," and is the mechanism by which instance hierarchies and associations are built after instance creation.

Tables Accessed

The documented package references the following tables through APPS synonyms:

• CSI_INSTANCE_INTERFACE — The interface/staging table holding source instance data. The package reads from this table to determine which instances and relationships must be created, and may write back status or processed markers.
• DUAL — The standard Oracle single-row utility table, used for expression evaluation and control-flow logic within PL/SQL.
• PLITBLM — The PL/SQL internal table (index-by table) utility structure used to manage collections of identifiers and message data within the package logic.

Usage Notes

CSI_ML_CREATE_PUB is typically invoked by concurrent programs or orchestration logic that govern mass loading of installed base data, and by custom code that needs programmatic creation of instances and relationships from interface content. The presence of both a single-threaded procedure and a parallel worker procedure indicates the package is designed to be scheduled across multiple workers, with the parent process calling create_instances or orchestrating create_parallel_instances for each worker. Relationship creation is invoked after instances exist, using the same transaction date and source system filters. The metadata indicates the package is referenced by zero other packages, so callers are generally concurrent programs or custom extensions rather than dependent APIs. Developers should confirm current signatures and any parameter changes in their specific 12.1.1 or 12.2.2 patch level, as the documented specification reflects a 2006 revision.