Results for “decrease_counter”

16 results




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

Overview

APPS.JTF_TASK_CONFIRMATION_PUB is a public PL/SQL API package in the Oracle E-Business Suite, residing in the APPS schema and carrying a status of VALID in both the 12.1.1 and 12.2.2 releases. It belongs to the Oracle Common Application Components (JTF) module that underpins task management and resource scheduling functionality. The package encapsulates the business logic responsible for managing the confirmation lifecycle of tasks, and for maintaining numeric counters associated with those tasks. In practical terms, it provides a controlled, API-driven mechanism through which task confirmation requirements are set, confirmations are recorded and reset, and various counter values attached to a task record are incremented, decremented, reset, or re-signed.

Because it is classified as a PUB (public) API classification, the package is intended to be called by other application code rather than being restricted to internal use. Its design follows standard EBS API conventions, including a dependency on FND_API, which provides the common error-handling, message-stack, and transaction-control infrastructure used across Oracle Applications public APIs.

Key Procedures and Functions

The documented interface exposes twelve procedures and functions. The counter-management group includes SET_COUNTER_STATUS, which sets the status associated with a task counter; RESET_COUNTER, which returns a counter to its initial value; INCREASE_COUNTER and DECREASE_COUNTER, which adjust a counter upward or downward respectively; and CHANGE_COUNTER_SIGN, which alters the sign (polarity) applied to a counter value.

The confirmation-management group includes RESET_CONFIRMATION_STATUS, which clears the confirmation state of a task; SET_CONFIRMATION_REQUIRED, which flags whether confirmation is mandatory for a given task; and SET_CONFIRMATION_CONFIRMED, which records that a task's confirmation has been completed. These procedures collectively govern the state transitions of the task confirmation workflow. Detailed parameter lists are not reproduced here; callers should consult the package specification and ETRM documentation for exact signatures.

Tables Accessed

The package references the JTF_TASKS_B table, accessed through an APPS synonym. JTF_TASKS_B is the base (non-translated) task table in the JTF task schema, and it stores the core task records. The confirmation and counter procedures in this package read and write task-level attributes on this table to persist status changes, confirmation flags, and counter values. The reliance on a single documented base table indicates a focused write path centered on task state rather than broad multi-table processing.

Usage Notes

This package is not typically invoked directly by end users. It is called by higher-level application code, as evidenced by its dependency relationships: it is referenced by CSF_TASKS_PUB, JTF_TASK_TEMPLATES_UTL, and by the package itself. CSF_TASKS_PUB is the public task API used by Field Service and related modules, while JTF_TASK_TEMPLATES_UTL handles task template processing. These referrers invoke JTF_TASK_CONFIRMATION_PUB to manipulate confirmation status and counters as part of broader task operations initiated from forms, concurrent programs, or custom integrations.

Because it depends on FND_API and on the STANDARD package, callers should follow the standard EBS API pattern: initialize the FND message stack, invoke the procedure with the appropriate initialization and commit flags, inspect the return status, and handle any errors raised through the FND_API message mechanism. When extended custom development is required, this package should be treated as an internal building block invoked through the supported public APIs rather than as a directly scheduled or user-facing entry point.