Search Results add_layout




Overview

FND_MLS_SUBMIT is a server-side PL/SQL package owned by the APPS schema in Oracle E-Business Suite. The package name references "MLS," Oracle's Multi-Lingual Support / Multi-Language Submission subsystem, and its documented role is to submit concurrent requests that must be processed by a concurrent manager on behalf of the MLS infrastructure. In the Oracle EBS 12.1.1 and 12.2.2 code lines, concurrent program submission is normally mediated through FND_REQUEST.SUBMIT_REQUEST; FND_MLS_SUBMIT provides an MLS-aware wrapper that assembles the submission context — including printer assignment, print options, layout, language, notification, and organizational context — before the request is handed to the concurrent manager. The package is classified in ETRM as OTHER rather than as a public API, which reflects its role as an internal utility layer rather than a supported integration interface.

Key Procedures and Functions

ETRM documents eleven entry points. Their names indicate the responsibilities of the package:

  • SUBMIT_MLS_REQUEST — the primary function. It submits an MLS concurrent request for processing by a concurrent manager, accepting the application short name, concurrent program name, an optional description, an optional start time, a sub-request flag, and up to one hundred optional request arguments (the declaration begins with default CHR(0) values).
  • INTERNAL — a private helper declared with critical and type parameters, providing internal control flow for the package.
  • ADD_PRINTER — registers the target printer for the request being assembled, resolving the destination against the printer definitions known to the concurrent manager.
  • SET_PRINT_OPTIONS — establishes the print/style options applied when the request output is rendered.
  • SET_OPTIONS — sets general submission options for the request.
  • ADD_LAYOUT — associates a report layout with the submission, relevant to multi-language and formatted output.
  • ADD_NOTIFICATION — attaches notification behavior so that completion or exception conditions can be communicated.
  • ADD_LANGUAGE — specifies the language context in which the MLS request is executed and its output produced.
  • SET_DEST_OPS — sets destination options controlling where and how output is delivered.
  • SET_ORG_ID — establishes the operating unit (ORG_ID) under which the request is submitted, ensuring Multi-Org security context is correct.

Together these procedures implement a builder pattern: caller code sets printer, options, layout, language, destination, notification, and organization, then invokes SUBMIT_MLS_REQUEST to create the request record.

Tables Accessed

The ETRM extract provided for FND_MLS_SUBMIT does not enumerate referenced tables. Because the package's documented purpose is concurrent request submission, it necessarily interacts with the concurrent manager data model — principally FND_CONCURRENT_REQUESTS, FND_CONCURRENT_PROGRAMS, and FND_PRINTER (or the equivalent printer definition view) — through APPS synonyms. These objects record the submitted request, validate the program registration and application, and resolve the printer named through ADD_PRINTER. No table list is asserted here beyond what is implied by that documented behavior.

Usage Notes

FND_MLS_SUBMIT is not a public API and is not referenced by any other documented package (ETRM records zero dependent packages). It is accordingly invoked from within Oracle's own MLS processing paths — for example when a request must be re-submitted under a different language or printer context — rather than from customer integration code. Developers inspecting a search for "add_printer" will find this package relevant because ADD_PRINTER is the documented mechanism by which the MLS submission routine binds printer destination information to a request. Custom code should generally use FND_REQUEST.SUBMIT_REQUEST instead; where FND_MLS_SUBMIT is used directly, the call must run in the APPS schema with an initialized FND_GLOBAL session context, and SET_ORG_ID should be called before submission to guarantee correct Multi-Org partitioning. Because the package is flagged as an internal utility, its signature may change between 12.1.1 and 12.2.2 and any direct dependency should be re-validated during upgrades.