Search Results check_scripts

Overview

INV_DCP_PVT is a private PL/SQL package in the Oracle E-Business Suite Inventory module (APPS schema) that implements the server-side logic of the Data Collection Processor (DCP). DCP is the framework through which Oracle Inventory validates, processes, and posts material transactions that arrive from external or non-Forms sources, such as mobile devices, barcode scanners, interfaces, and the Oracle iSupplier / e-commerce transaction flows. Because the package is a PVT (private) API, it is not intended as a public integration point; it is invoked internally by public Inventory APIs, the transaction-processing forms, and DCP-driven interfaces that must confirm whether a given transaction is eligible for processing, whether it satisfies the DCP validation rules, and what subsequent action to take.

The package header declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user, and defines global records, nested tables, and exceptions used to carry transaction, serial, and debugging context across DCP processing.

Key Procedures and Functions

• SEND_MAIL — Sends an e-mail notification, accepting sender, up to four recipients, and a message body. It is used by DCP error handling to alert administrators or users when a transaction or validation fails.
• VALIDATE_DATA — The principal validation entry point. It evaluates a specified DCP event against a transaction header, temporary transaction identifier, and batch identifier, returning a status to the caller. An optional flag controls whether a data_inconsistency_exception is raised rather than returned. This is the procedure most commonly associated with the check_scripts search.
• CHECK_SCRIPTS — Examines the DCP scripts (validation scripts) configured for a given action code and a specific transaction, temporary transaction, or batch. It is the mechanism by which configurable, script-driven validation is applied to an inbound transaction, returning or signalling whether the scripts pass. The declared global G_CHECK_DCP supports this check path.
• POST_PROCESS — Performs post-transaction activities after a DCP action completes, such as updating derived state or triggering follow-on logic, with an option to raise an exception on failure.
• IS_DCP_ENABLED — Returns whether DCP processing is enabled for the current context, allowing callers to short-circuit DCP logic when the feature is disabled.
• ADD_SERIAL_DATA — Populates the package's serial-status collection, tracking serial number status against the action being performed so that serial-controlled items are validated consistently with inventory rules.
• DUMP_MMTT — Diagnostic utility that dumps content from the material transactions temporary table, used to troubleshoot DCP transaction flow.

Tables Accessed

All access is via APPS synonyms. MTL_MATERIAL_TRANSACTIONS_TEMP stores the pending transactions that are validated and posted; MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV supply item attributes and concatenated descriptions. MTL_TRANSACTION_TYPES and MTL_TXN_SOURCE_TYPES determine valid action codes and source types, while MTL_PARAMETERS provides organization-level defaults. Location and serial data come from MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, MTL_SECONDARY_LOCATORS, MTL_ITEM_REVISIONS, MTL_SERIAL_NUMBERS, and MTL_SERIAL_NUMBERS_TEMP. FND_USER supports e-mail/notification lookups, and DUAL and DBMS_UTILITY are used for utility purposes.

Usage Notes

INV_DCP_PVT is not typically called directly by external systems. It is invoked by public Inventory APIs, the transaction entry forms, delivery-detail and delivery-group APIs, ITS (iSupplier) code, and DCP-enabled interfaces, and is referenced by one other package. Because it is private, customizations should call the supported public Inventory APIs rather than this package. The data_inconsistency_exception is raised at the outer DCP level and must be handled by callers. Debugging is controlled by the G_DEBUG_STARTED global, supporting DCP-level trace output.