Search Results cst_lc_adj_interface_trx_s

Overview

APPS.CST_LCMADJUSTMENTS_PUB is a public PL/SQL package body in the Oracle E-Business Suite Cost Management (CST) module. Its purpose is to manage the processing of Landed Cost adjustments (LCM) by orchestrating the threaded, parallel execution of worker processes that apply landed cost charges to material transactions. Landed cost management allows organizations to allocate freight, duty, insurance, and other charges to received goods so that accurate inventory valuations are reflected in the general ledger.

The package acts as a controller or launcher rather than performing the detailed allocation logic itself. It coordinates concurrency, records processing state, and dispatches worker jobs that read pending landed cost adjustment records, apply them to the appropriate transaction or receipt, and update the related accounting entries. The object is classified as a public API (PUB) and resides in the APPS schema. The ETRM metadata shows it is a VALID package body in both Oracle EBS 12.1.1 and 12.2.2, and it is not referenced by any other database object, indicating it is invoked directly by users or concurrent programs rather than called from within other packages.

Key Procedures and Functions

The documented API surface for this package consists of a single procedure:

• LAUNCH_WORKERS — The primary entry point of the package. It is responsible for initiating the worker processes that perform landed cost adjustment processing. Based on the dependencies it references, this procedure validates and initializes the operating context, submits or launches concurrent worker requests, tracks them through the concurrent manager, and writes status/logging information. It is the mechanism by which a set of landed cost adjustment interface records are handed off to parallel processors for completion.

No function signatures or parameter lists are documented in the ETRM extract, and none are fabricated here. The procedure name and surrounding dependencies indicate its orchestration role rather than a data-transformation role.

Tables Accessed

The package references the following tables and views through APPS synonyms, each serving a distinct role:

• CST_LC_ADJ_INTERFACE — The landed cost adjustment interface staging table holding pending adjustments to be processed.
• CST_LC_ADJ_INTERFACE_TRX_S — A sequence associated with the adjustment interface records, used to generate or track identifiers during processing.
• CST_LC_PROCESSOR_GRP_S — A sequence used to generate processor group identifiers that group worker processes for a given run.
• MTL_INTERFACE_PROC_CONTROLS — Interface processing control records that govern how many and which interface rows a worker handles.
• MTL_MATERIAL_TRANSACTIONS — The material transaction records against which landed cost adjustments are ultimately applied or created.
• MTL_PARAMETERS — Organization-level inventory parameters used to establish the operating organization context.
• RCV_TRANSACTIONS — Receiving transactions linked to the receipts that generate landed cost adjustments.
• FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS — Concurrent manager definitions and submitted request records used for launching and monitoring worker jobs.
• DUAL — Used for simple scalar evaluations.

Additionally, the package depends on standard APIs and utilities including FND_API, FND_CONCURRENT, FND_FILE, FND_GLOBAL, FND_LOG, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, and FND_REQUEST, reflecting its use of message handling, logging, profile options, and concurrent request submission.

Usage Notes

CST_LCMADJUSTMENTS_PUB.LAUNCH_WORKERS is typically invoked by a concurrent program or a scheduled request in the Cost Management responsibility when landed cost adjustments require processing. Because it submits child worker requests through FND_REQUEST, the calling concurrent manager environment and any user-defined processor counts or group size profile options influence the degree of parallelism applied. The package is not referenced by other database objects, so it should be called directly rather than relied upon as a subordinate API.

Administrators and developers should execute it in a controlled concurrent environment, monitor the resulting child requests, and review the request log output written through FND_FILE for error diagnostics. When troubleshooting, the primary diagnostic tables are the concurrent requests created for the workers and the records in the landed cost adjustment interface tables that were selected for processing.