Search Results cost_processor

Overview

APPS.CST_JOB_SM_PROCESSOR is a PL/SQL package body residing in the APPS schema that belongs to the Oracle Cost Management (CST) module family in Oracle E-Business Suite 12.1.1 and 12.2.2. The "SM" component of the package name indicates its association with the Standard Costing and job costing processor flow, and its naming convention ties it to the CST_JOB_SM family of modules used to drive cost processing for discrete manufacturing jobs. The package exposes entry points that conform to the standard Oracle cost processor interface signature, accepting an error code and an error message as OUT NOCOPY parameters so that calling programs can interrogate the outcome of processing.

In the shipped file (CSTPSMOB.pls, version 115.3 dated 2002/11/11), the package body is intentionally minimal. Each documented program simply initializes err_code to zero and clears err_mesg to an empty string, and COST_UPDATE additionally assigns its input identifier to a local dummy variable. This structure indicates the object is a stub or placeholder shell that defines the calling contract for the Standard Costing job processor without embedding substantive costing logic in this repository version.

Key Procedures and Functions

ETRM documents two procedures within the package body:

• COST_PROCESSOR — The primary entry point for the costing processor interface. Per the standard Oracle cost processor convention, it returns an error code and an error message to the caller. In the shipped source it performs only initialization, setting the error code to success and the message to null.
• COST_UPDATE — Accepts a cost update identifier (x_cost_update_id) plus the standard error code and error message OUT parameters. It is intended to drive or validate an update against a specific cost update request. As shipped, it discards the identifier into a dummy variable and returns success with an empty message.

The consistent presence of err_code and err_mesg across both procedures confirms that the package is designed to be driven by the Oracle Cost Management processor framework, where the err_mesg parameter carries diagnostic text back to the calling manager.

Tables Accessed

The documented ETRM metadata lists no tables referenced via APPS synonyms for this package body. This is consistent with the stub implementation, which performs no SQL against any base or interface table. Any deployment in which the package body is replaced or extended would presumably reference the standard job costing tables such as CST_COST_UPDATES and related cost processor staging tables, but such references are not part of the documented shipped code.

Usage Notes

Because the package is referenced by zero other documented packages, it is not invoked through an internal dependency chain recorded in ETRM. Its outward-facing contract suggests invocation from custom code, from the Work in Process job costing flow, or from concurrent programs that call a cost processing API with the err_code/err_mesg signature. Developers searching for err_mesg in this context should note that, as shipped, both procedures always return a null message and zero error code, so error handling logic depending on err_mesg will not be exercised by this body. When standard costing is implemented, this stub is typically superseded by the active CST_JOB_SM_PROCESSOR implementation that performs the real validation and update work.