Search Results program_has_args




Overview
Explore in AI Chat

Overview

FND_CONC_SSWA is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Oracle Application Framework (OAF) based "Requests" and "Schedule Requests" Self-Service Web Applications (SSWA). Its name derives from Concurrent processing and SSWA (Self-Service Web Applications), reflecting its role as a server-side helper layer that translates the rich client behavior of the Oracle Forms Concurrent Manager interface into functionality callable from web-based (OA Framework) pages. In EBS 12.1.1 and 12.2.2, users no longer submit concurrent requests exclusively through the Forms-based "Submit Requests" window; the SSWA pages expose the same capabilities over HTTP, and FND_CONC_SSWA supplies the presentation-support logic those pages require.

The package is classified as OTHER in the ETRM documentation, indicating it is an internal, Oracle-supplied utility package rather than a published public API. It is validated and valid in the APPS schema, and it is referenced by several other packages including FND_CP_OPP_REQ, FND_OAM, and FND_WEBFILE, confirming its role as a shared foundation component for concurrent processing and output management features surfaced through the web UI.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions, whose names reflect their intended purposes:

  • GET_PHASE — Retrieves the current phase of a concurrent request (for example, Pending, Running, Completed) for display or logic purposes.
  • GET_STATUS — Returns the status of a concurrent request, complementing phase information for status display and decision logic.
  • GET_SSWA_STATUS — Provides status information specific to the SSWA presentation layer, distinguishing the web-facing status view from the internal request status.
  • GET_OFILE_STATUS — Determines the status of the output file associated with a concurrent request, supporting display and download of request output.
  • GET_SCH_DESC — Returns the description of a schedule, used to render schedule details on the request submission pages.
  • PROGRAM_HAS_ARGS — Indicates whether a concurrent program defines arguments, allowing the UI to render or suppress the arguments region.
  • MAP_ATTR_TO_ARG — Maps an OA Framework page attribute to a concurrent program argument, bridging the web page model to the concurrent program argument model.
  • ELAPSED_TIME — Computes and formats the elapsed time of a request for display to the user.
  • GET_NOTIFICATIONS — Retrieves worklist or request notifications relevant to the requesting user or request.
  • DIAGNOSTICS — Provides diagnostic information useful for troubleshooting concurrent request and SSWA behavior.
  • LAYOUT_ENABLED and LAYOUT_ENABLED_YN — Determine whether the layout/layout-based output feature is enabled, returning either a boolean-style or Y/N value as required by the calling context.
  • PUBLISHER_INSTALLED — Checks whether Oracle XML Publisher (BI Publisher) is installed, enabling conditional display of publisher-related features.

Tables Accessed

FND_CONC_SSWA reads from several core concurrent processing and descriptive flexfield tables through APPS synonyms. FND_CONCURRENT_PROGRAMS supplies program definitions; FND_CONCURRENT_REQUESTS supplies request header data; FND_CONC_REQUEST_ARGUMENTS and FND_CONC_REQ_OUTPUTS provide argument and output file details; FND_CONC_PP_ACTIONS and FND_CONC_RELEASE_CLASSES support request lifecycle and release class information; FND_DESCR_FLEX_COLUMN_USAGES supports descriptive flexfield rendering; FND_LOOKUP_VALUES provides lookup-based labels and values; and PLITBLM is the standard Oracle Forms/PLSQL table-to-memory utility used for array handling.

Usage Notes

FND_CONC_SSWA is invoked indirectly by the OA Framework pages and controllers that implement the EBS "Submit Requests," "Find Requests," and related self-service concurrent processing screens. It is referenced by FND_CP_OPP_REQ, FND_OAM, and FND_WEBFILE, indicating its integration with output management and web file delivery. Because it is an internal package and not a public API, customizations should avoid direct invocation; Oracle does not guarantee its interface across releases. Customers typically interact with its functionality through the standard EBS web interface rather than through custom PL/SQL calls.