Search Results check_status




Overview
Explore in AI Chat

Overview

WSH_FTE_ENABLED is a small utility package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its sole documented purpose is to report whether the Force Trace Execution (FTE) capability is currently enabled in the environment. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references resolve under the privileges of the invoking session rather than the definer, which is consistent with a lightweight runtime status check that carries no privileged logic of its own.

The package header script is identified by the revision marker WSHENBLS.pls 115.1, dated 12 November 2002. This places the object among the older, stable components of the WSH (Shipping) product family, and its AUTHID CURRENT_USER declaration and mandatory package naming convention confirm compliance with Oracle's PL/SQL API standards. The ETRM classification for this object is OTHER, indicating that it is not a public business API for data manipulation but an internal utility used to gate or branch behavior at runtime.

Key Procedures and Functions

The package exposes a single documented function:

  • CHECK_STATUS — The function determines whether Force Trace Execution is enabled. According to the embedded header comment, it accepts no input parameters and produces no output parameter other than its return value. It returns the character 'Y' when FTE is enabled and 'N' otherwise. Because it takes no arguments, it is a pure environment probe that can be called repeatedly without side effects on the data model.

No other procedures or functions are documented for this package in the ETRM metadata. The function body itself is not reproduced in the source excerpt, and its internal logic is therefore not documented; only the contract described above is guaranteed.

Tables Accessed

The documented metadata lists no tables referenced by WSH_FTE_ENABLED via APPS synonyms. This is consistent with the function's stated behavior: CHECK_STATUS reports a configuration or profile-based setting rather than querying a transactional table. Any value it reads is obtained indirectly, such as through a profile option lookup or an internal package state, and no direct SQL against an application table is documented. The absence of table references means the function cannot introduce locking, read-consistency, or row-level dependency concerns for the calling program.

Usage Notes

The package is referenced by one other package in the application, indicating that it is consumed programmatically rather than exposed directly through a form or concurrent program. Typical invocation patterns include:

  • Conditional branching in shipping logic — Calling packages evaluate CHECK_STATUS and enable trace-generation or diagnostic paths only when the return value is 'Y'.
  • Debug and support scenarios — Support personnel may enable FTE to capture diagnostic output during shipping transactions; the calling code queries CHECK_STATUS to decide whether to emit that output.
  • Custom extensions — Developers writing custom code alongside the WSH modules can call APPS.WSH_FTE_ENABLED.CHECK_STATUS to align their own diagnostic behavior with standard functionality.

Because CHECK_STATUS returns a single-character flag and requires no parameters, it is inexpensive to call. The package carries the Oracle Proprietary, Confidential Information designation, so its use should be limited to supported extension points. In both 12.1.1 and 12.2.2 the object is unchanged in documented structure, and no differences between the two releases are recorded in the ETRM metadata.