Search Results get_run_function_url

Overview

APPS.CSP_PLANNING_UTILS_PKG is a utility package within the Oracle E-Business Suite packaged applications schema. Its header comment identifies it as a general-purpose helper for Oracle Supply Chain Planning (CSP) functionality, and its $Header revision string (120.0.12020000.4, dated 21-Mar-2013) confirms it is maintained at the 12.1.1/12.2.2 application release level. The package is declared AUTHID CURRENT_USER, meaning its unqualified database references resolve under the privileges of the invoking session rather than the package owner; callers must therefore already hold or inherit the necessary privileges on the underlying objects. As a planning utility rather than a business entity API, the package encapsulates cross-cutting services that other planning components rely on: concurrent request submission, dynamic discovery of a function's run URL, message token substitution, and application session context initialization. It is classified as OTHER in the ETRM metadata, indicating it is a supporting internal utility and not a published integration API. The package does not define or persist planning data of its own; it orchestrates operations against framework and planning configuration objects on behalf of its callers.

Key Procedures and Functions

• SUBMIT_CONC_REQUEST — Accepts a request name and a parameters identifier and returns a concurrent reference cursor. It provides the package's mechanism for launching an Oracle Concurrent Manager request and handing back a result set for the caller to consume, allowing planning logic to trigger long-running background processing rather than executing inline.
• GET_RUN_FUNCTION_URL — Accepts a function name and returns a function URL cursor. This is the routine associated with the search term get_run_function_url. It resolves the run URL for a given FND function, enabling callers to derive the navigable target for a form function dynamically instead of hard-coding a URL.
• GET_MESSAGE — Accepts an application name, a message name, and up to five token/value pairs, and returns a resolved message string. It wraps Oracle's message dictionary lookup so that planning code can emit translatable, token-substituted messages consistent with the FND message framework.
• SET_CONTEXT — Accepts user, responsibility, responsibility application, and security group identifiers and returns a status string. It establishes the Oracle Applications session context (user, responsibility, application, and security group) required before context-sensitive lookups or submissions can proceed correctly.

Tables Accessed

The package accesses the following objects through APPS synonyms:

• CSP_PLANNING_PARAMETERS — the planning parameter store, read to resolve the parameters identifier supplied to concurrent request submission.
• FND_FORM_FUNCTIONS — the function registry, queried by GET_RUN_FUNCTION_URL to resolve a function's run URL.
• FND_LANGUAGES, FND_RESPONSIBILITY_TL — language and translated responsibility metadata supporting message resolution and context setup.
• FND_USER — user validation and context resolution for SET_CONTEXT.
• DUAL — used for single-row expression evaluation and function-call selection.

No direct insert, update, or delete behavior against business tables is documented in the package metadata; the package functions principally as a reader of framework and planning configuration data.

Usage Notes

CSP_PLANNING_UTILS_PKG is intended for internal consumption by Oracle Supply Chain Planning components and by custom code that must operate within the same session context. Typical invocation follows a fixed sequence: SET_CONTEXT is called first to establish the user, responsibility, and security group; GET_MESSAGE supplies localized feedback or error text; GET_RUN_FUNCTION_URL resolves the navigation target for a function; and SUBMIT_CONC_REQUEST dispatches the resulting planning request to the Concurrent Manager, returning a cursor for result retrieval. Because the package is AUTHID CURRENT_USER, callers must ensure their session owns the required object privileges, and because the returned cursors are strongly typed REF CURSORs, consuming code must declare matching cursor variables. The package is not referenced by any other documented package, so its callers are forms, concurrent programs, or bespoke PL/SQL rather than dependent APIs. There is no documented initialization or cleanup routine, and the package holds no package-level state, so it may be invoked repeatedly within a session without ordering side effects beyond the context set by SET_CONTEXT.