Results for “dpp_executionprocess_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

DPP_EXECUTIONPROCESS_PUB is a public PL/SQL package in the APPS schema that belongs to the Oracle E-Business Suite Execution Process framework, part of the Distribution and supply chain processing modules. The package is declared with AUTHID CURRENT_USER, meaning that its unqualified database object references resolve under the privileges and schema of the calling user rather than the APPS owner. This design pattern is standard for ETRM public APIs, which are intended to be invoked from multiple calling contexts, including concurrent programs, Oracle Forms, and external integration code.

The package exposes a single documented entry point, Initiate_ExecutionProcess, whose stated purpose is to initiate an execution process. In the EBS architecture, such "public" wrapper packages typically validate inputs, perform any required setup or logging, and then delegate to internal private packages that carry out the core business logic. The naming convention DPP_EXECUTIONPROCESS_PUB identifies the package as the published interface of an execution-process feature, distinguishable from private companion packages that should not be called directly.

Users searching for "delya executer" (a likely misspelling of phrases such as "delay executor" or "execution process") commonly encounter this object when troubleshooting delayed or queued execution of distribution transactions, which may lead them to inspect or invoke this API.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure in this package:

• Initiate_ExecutionProcess — The sole documented procedure. Its purpose is to initiate an execution process within the DPP execution framework. The versioned source header identifies dpppexcs.pls at version 120.1.12010000.4, last modified in June 2009, which indicates the package has been stable across the 12.1.1 and 12.2.2 releases and is a long-standing component of the EBS 12.x code line.

The documentation excerpt does not enumerate the full parameter list in prose, and the metadata confirms only one procedure exists. No additional functions or overloads are documented for this package in ETRM 12.2.2.

Tables Accessed

The ETRM metadata for DPP_EXECUTIONPROCESS_PUB lists no tables referenced through APPS synonyms. This is consistent with the package acting as a thin public wrapper: direct DML and queries against execution, transaction, and staging tables are typically performed by subordinate private packages that this public API invokes. Because the package is declared AUTHID CURRENT_USER and no synonym-level table references are recorded, any table access occurs either indirectly through delegated packages or through objects resolved at runtime in the caller's schema.

Usage Notes

As a public API classification package with a single initiation procedure, DPP_EXECUTIONPROCESS_PUB is intended to be called programmatically rather than queried. Typical invocation scenarios include:

• Concurrent programs that require an execution process to be started as part of a batch or scheduled run.
• Oracle Forms or OAF pages that trigger execution processing in response to user action.
• Custom or integration code that needs to hand off work to the DPP execution framework using the supported public interface rather than private internals.

The metadata records zero packages referencing this object, indicating it is not a dependency of other shipped EBS code and is therefore called primarily from external or custom entry points. Because the package runs with AUTHID CURRENT_USER, callers must ensure that the invoking schema has the necessary privileges on any underlying objects resolved at runtime.

Given the absence of documented parameter details in the ETRM record, implementers should inspect the package specification and body in the target environment (for example, via ALL_SOURCE) before writing calls against it, and should confirm behavior against Oracle Support documentation or patches applicable to their exact release and patch level.