Search Results cst_costprocvalidation_pvt




Overview
Explore in AI Chat

Overview

APPS.CST_COSTPROCVALIDATION_PVT is a private PL/SQL package in the Oracle E-Business Suite Cost Management (CST) module. Its stated purpose, taken directly from the package header comments, is to check for data corruption in MTL_MATERIAL_TRANSACTIONS (MMT). The package forms part of the Cost Processor validation layer, providing the internal diagnostics used to confirm that material transaction data is internally consistent before costing processes rely on it.

The package is classified as Private (PVT) in the ETRM metadata, meaning it is not a public API and is not intended for direct invocation by external or customer code. It was introduced in the 11i era (the header identifies version 1.0, dated 2005) and continues to be shipped and documented in EBS 12.1.1 and 12.2.2. The single documented procedure is targeted by the search term "validate_transactions".

Key Procedures and Functions

The package exposes exactly one documented procedure:

  • VALIDATE_TRANSACTIONS — Declared with a single OUT NOCOPY parameter, x_return_status, which returns the outcome of the validation to the caller. The procedure checks material transaction records for data corruption. Because the return mechanism is limited to a status indicator, the procedure acts as a pass/fail gate rather than a reporting routine: the caller learns whether the MMT data set is trustworthy, not a detailed list of every inconsistency found. No public function, cursor, or additional overload is documented.

No further procedures or functions are present in the documented metadata, and the package does not expose public APIs for transaction creation or cost calculation — those responsibilities belong to the Cost Management public APIs and the cost processor itself.

Tables Accessed

The documented table references reveal the scope of the corruption check across the cost and manufacturing data model. All tables are accessed through APPS synonyms:

Usage Notes

Because ETRM records zero referencing packages and the procedure is private, VALIDATE_TRANSACTIONS is not designed for standalone customer invocation. In practice it is called from within the Cost Management concurrent processing flow — most plausibly from a diagnostic or pre-processing concurrent program that the Cost Processor launches against a set of material transactions — and the inclusion of FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS in the table list supports this pattern.

On EBS 12.1.1 the package is compiled into the APPS schema alongside other CST private packages, and it remains documented unchanged in 12.2.2. Customers encountering cost processor errors should treat a non-success x_return_status as an indicator that MMT data requires investigation through standard inventory transaction inquiry and the material transaction data-fix diagnostics, rather than attempting to call the package directly. Direct invocation is unsupported, and any wrapper built on it would depend on a private, version-sensitive interface.