Search Results launch_workers

Overview

The APPS.CST_LCMADJUSTMENTS_PUB package is a public PL/SQL API within Oracle E-Business Suite's Cost Management (CST) module. It supports Landed Cost Management (LCM) adjustments, a specialized costing feature that allows organizations to apply, recalculate, or reverse landed cost charges against received goods. Landed costs represent additional expenses — freight, duty, insurance, handling — layered onto the base cost of purchased items. The package provides the programmatic entry point for submitting the concurrent processing that performs these landed cost adjustment transactions.

As a PUB (public) classified API, it is intended for external invocation by other Oracle applications, forms, or custom code, rather than being restricted to internal ETRM use. The $Header comment (revision 120.0.12010000.2, dated November 2008) indicates the specification has remained stable across the 12.1.1 and 12.2.2 release lines, with no procedural signature changes between them.

Key Procedures and Functions

The package exposes a single documented procedure:

• LAUNCH_WORKERS — This is the primary and only public procedure in the specification. It serves as the concurrent-style launcher that orchestrates the background processing of landed cost adjustment records. Consistent with standard Oracle concurrent program conventions, it uses the errbuf OUT NOCOPY VARCHAR2 and retcode OUT NOCOPY NUMBER parameters, which are the conventional return values expected when a package procedure is registered as a concurrent program executable. The procedure name indicates it dispatches (or "launches") worker processes to handle the adjustment workload rather than performing the recalculation inline.

The specification also declares a private collection type, rowid_tbl_typ, defined as a table of ROWID indexed by BINARY_INTEGER. This type is used internally to track the specific rows in the landed cost adjustment interface that require processing, enabling efficient bulk handling of interface records.

Tables Accessed

The documented table references, resolved through APPS synonyms, reflect the end-to-end landed cost adjustment data flow:

• CST_LC_ADJ_INTERFACE and CST_LC_ADJ_INTERFACE_TRX_S — the landed cost adjustment interface tables, holding the adjustment records and their associated transaction detail awaiting processing by the workers.
• CST_LC_PROCESSOR_GRP_S — stores the processor grouping that determines how adjustment records are batched and assigned to worker processes.
• MTL_MATERIAL_TRANSACTIONS and RCV_TRANSACTIONS — the core inventory transaction and receiving tables, which are read/updated to apply the cost adjustments to the underlying receipts.
• MTL_PARAMETERS — organization parameters supplying costing and processing defaults.
• MTL_INTERFACE_PROC_CONTROLS — interface processor control settings governing concurrency and processing behavior.
• FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS — used to identify and submit the concurrent program requests that perform the worker execution.
• DUAL — used for lightweight scalar queries and control checks.

Usage Notes

LAUNCH_WORKERS is typically invoked as a concurrent program from the Landed Cost Management responsibility, or called from custom code using the standard concurrent request submission pattern (FND_REQUEST.SUBMIT_REQUEST) with the two standard OUT parameters. It is not documented as being referenced by any other package, though it may itself be wrapped by LCM submission routines. Because the interface tables and processor group structures are central to its operation, organizations should ensure adjustment interface records are staged and validated before launching workers, and should monitor FND_CONCURRENT_REQUESTS to confirm completion and diagnose failures.