Search Results get_current_status

Overview

The APPS.FND_SVC_COMPONENT package body is the core runtime controller for the Oracle E-Business Suite Service Component architecture. Service components are long-running, Java-based or PL/SQL-based processes (such as notification mailers, workflow agents, or inbound/outbound message processors) that execute inside a container managed by the Service Component framework. This package provides the server-side API layer that Oracle EBS and custom code use to start, stop, suspend, resume, refresh, and query the state of those containers and the individual components running inside them.

The package body header ($Header: AFSVCMPB.pls 120.4 2006/05/03) confirms its long-standing role in the technology stack. It maintains private package variables such as pv_system_guid, pv_schema_name, pv_last_agent_name, pv_last_queue_name, and pv_install_mode, which are explicitly marked as private and not for customer use. These variables cache local container identity and install context so that repeated component operations avoid redundant lookups. The package also defines private exceptions (for example, e_ContainerNotRunning) and private helper routines such as Get_Container_Info, Raise_Control_Event, Get_ConcQ_Name, Get_ConcQ_ID, and Refresh_Container.

Key Procedures and Functions

The documented public interface exposes 21 procedures and functions. The GET_CURRENT_STATUS function, which is the target of the user's search, returns the present runtime status of a service component or container, allowing callers to poll the framework for state transitions without inspecting underlying tables directly. Related status-oriented routines include GET_CONTAINER_STATUS, UPDATE_STATUS, VERIFY_CONTAINER, VERIFY_ALL_CONTAINERS, and GET_OAM_ROLLED_STATUS_BY_TYPE.

Lifecycle control is provided by START_COMPONENT, STOP_COMPONENT, SUSPEND_COMPONENT, RESUME_COMPONENT, REFRESH_COMPONENT, and RESET_CONTAINER_COMPONENTS. Request execution and parameter handling are handled by EXECUTE_REQUEST, DELETE_REQUEST, INSERT_PARAM_VALS, RETRIEVE_PARAMETER_VALUE, and VALIDATE_OPERATION. Session and operational context are managed through NAME_CONTAINER_SESSION and GENERIC_OPERATION, while REFRESH_CONTAINER_LOG_LEVEL adjusts logging verbosity for a running container.

Tables Accessed

According to the ETRM metadata, the package reads and writes the following tables via APPS synonyms: FND_SVC_COMPONENTS (component definitions and state), FND_SVC_COMP_PARAMS_B and FND_SVC_COMP_PARAM_VALS / FND_SVC_COMP_PARAM_VALS_S (parameter definitions and values), FND_SVC_COMP_REQUESTS, FND_SVC_COMP_REQUESTS_H, and FND_SVC_COMP_REQUESTS_H_S (component request queues and their history tables), and FND_CONCURRENT_QUEUES (for deriving concurrent queue identifiers). The package also draws on WF_PARAMETER_LIST_T for the Workflow parameter list type, and on Oracle infrastructure views and packages: DBMS_APPLICATION_INFO, DBMS_JOB, DUAL, and GV$SESSION.

Usage Notes

Typical invocation occurs from Oracle Forms-based Service Component administration screens, from concurrent programs that manage container health, and from custom PL/SQL that needs to interrogate or manipulate component state. Because GET_CURRENT_STATUS and its siblings operate on live session and job data (including GV$SESSION and DBMS_JOB), they are generally privileged, APPS-owned APIs and should be called only with the APPS schema or through a wrapper. Developers integrating with the framework should prefer the documented public routines and treat the private variables and helpers as internal implementation details. Two other packages reference FND_SVC_COMPONENT, reinforcing its role as a shared dependency within the Service Component subsystem.