Results for “p_lang”

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

Overview

FND_MLS_REQUEST is an Oracle E-Business Suite package body owned by APPS that implements the multilingual (MLS) concurrent request submission facility. Its principal role is to accept a single user-submitted concurrent request and fan it out into one request per installed or selected language, so that a report, program, or request set can be executed simultaneously against multiple language environments. This package underpins the "Standard Request Submission" / MLS scheduling behaviour used when an administrator or application wishes to publish output in several languages without manually resubmitting the same program for each language.

The metadata classifies the object as an OTHER API and records two documented entry points: FNDMLSUB and STANDARD_LANGUAGES. The package also depends on a private helper, GEN_ERROR, which builds a standardized SQL/PLSQL error string by calling FND_MESSAGE with the SQL_PLSQL_ERROR message name and the routine, error number, and reason tokens, truncated to 240 characters. The header comment shows a maintenance revision dated 2008, indicating a long-lived, stable foundation component.

Key Procedures and Functions

• FNDMLSUB — The MLS master program. It is a concurrent-program-style procedure taking the conventional errbuf and retcode OUT parameters alongside an application id, a concurrent program id, and an optional use_func flag defaulting to 'N'. It drives the fan-out by opening the run_req_info cursor, which joins request-set program definitions to their submission attributes, then creating one concurrent request per applicable language. It is the entry point a concurrent program manager or request-set definition ultimately calls.
• STANDARD_LANGUAGES — Provides the language set used when a request is submitted for all standard installed languages rather than an explicit list. It supplies the base population of languages against which FND_RUN_REQ_LANGUAGES rows are validated and expanded.
• GEN_ERROR — Internal helper returning a formatted error message; not part of the published interface but documented in the source excerpt.

Tables Accessed

• FND_RUN_REQUESTS — the core header table for an MLS run/request grouping; the package inserts and updates the master run record.
• FND_RUN_REQ_LANGUAGES — stores the per-run language selection that drives fan-out.
• FND_RUN_REQ_PP_ACTIONS — holds post-processing actions associated with the generated requests.
• FND_CONCURRENT_REQUESTS, FND_CONCURRENT_PROGRAMS, FND_EXECUTABLES, and FND_APPLICATION — resolve program and application identifiers and supply submission attributes.
• FND_LANGUAGES and FND_TERRITORIES — provide the valid language and territory definitions.
• DUAL and DBMS_SQL — utility access; DBMS_SQL supports dynamic request submission.

Usage Notes

FND_MLS_REQUEST is invoked indirectly rather than from user code. Standard uses are: submitting an MLS-enabled concurrent program through the Standard Request Submission form, defining or running a request set that spans multiple languages, and internal calls from concurrent manager processing. Because the API is classified OTHER, it should not be treated as a supported public API for custom development. The search term "p_lang" corresponds to the parameter naming convention used for language selection in this family of programs, but no parameter of that exact name appears in the documented FNDMLSUB signature; callers passing a language argument do so through the run request language tables rather than a literal p_lang formal parameter in this package body. Custom code requiring multi-language scheduling should model submissions on the documented tables (FND_RUN_REQUESTS, FND_RUN_REQ_LANGUAGES) and rely on the standard concurrent request submission APIs where possible.