Results for “argument_method_code”

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

Overview

FND_CONCURRENT_PROGRAMS is the registration repository for concurrent programs in Oracle E-Business Suite, owned by the APPLSYS schema and part of the FND – Application Object Library product. A concurrent program is any executable unit of work that can be submitted to the Concurrent Manager — an Oracle Reports report, a PL/SQL stored procedure, a host script, a Java or spawned process. Each row in this table defines one such program: its name, the executable it invokes, its argument and execution methods, its request class, its default print and style attributes, and the many behavioral flags that govern queuing, restarts, and security. The table is central to the Concurrent Manager architecture, because requests submitted through the Submit Requests form, the SRS APIs, or Request Sets all resolve their program definition from this object.

Applying Data Vault modeling heuristics to its foreign-key topology suggests classifying FND_CONCURRENT_PROGRAMS as a hub: it is referenced by a large number of dependent tables and itself references a modest number of code and lookup tables. Under that suggestion, APPLICATION_ID and CONCURRENT_PROGRAM_ID form the natural hub key, with descriptive and flag attributes optionally modelled as a satellite.

Key Information Stored

The documented physical schema exposes 72 columns. The primary key is the composite FND_CONCURRENT_PROGRAMS_PK, comprising APPLICATION_ID and CONCURRENT_PROGRAM_ID. Because the key is composite and application-scoped, there is no single surrogate column; the pair acts as the durable identifier. Two unique indexes serve as business-key candidates. FND_CONCURRENT_PROGRAMS_UK1 / _U2 enforces uniqueness on APPLICATION_ID, CONCURRENT_PROGRAM_NAME (plus ZD_EDITION_NAME in 12.2.2), and FND_CONCURRENT_PROGRAMS_U1 restates the primary-key columns.

• APPLICATION_ID, CONCURRENT_PROGRAM_ID — composite primary key identifying the owning application and the program.
• CONCURRENT_PROGRAM_NAME — the internal, untranslated program name; the business key used when submitting by name.
• EXECUTABLE_APPLICATION_ID, EXECUTABLE_ID — foreign key to FND_EXECUTABLES, tying the program to its executable definition.
• EXECUTION_METHOD_CODE, ARGUMENT_METHOD_CODE — how the program runs (e.g., IMMEDIATE, PL/SQL, Oracle Reports) and how its parameters are passed.
• CLASS_APPLICATION_ID, CONCURRENT_CLASS_ID — the request class assigned to the program, referencing FND_CONCURRENT_REQUEST_CLASS.
• ENABLED_FLAG, REQUEST_SET_FLAG, RUN_ALONE_FLAG, SRS_FLAG, SAVE_OUTPUT_FLAG — enablement and behavioral controls.
• QUEUE_CONTROL_FLAG, QUEUE_METHOD_CODE, REQUEST_PRIORITY — concurrency and scheduling behavior.
• PRINTER_NAME, OUTPUT_PRINT_STYLE, REQUIRED_STYLE, OUTPUT_FILE_TYPE, MINIMUM_WIDTH, MINIMUM_LENGTH — output and printing defaults, with PRINTER_NAME and OUTPUT_PRINT_STYLE referencing FND_PRINTER and FND_PRINTER_STYLES.
• EXECUTION_OPTIONS, CD_PARAMETER, INCREMENT_PROC, RESTART, ENABLE_TRACE, ENABLE_TIME_STATISTICS, STAT_COLLECT — runtime and Oracle Reports-specific options.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS in Multi-Org contexts.
• NLS_COMPLIANT, MLS_EXECUTABLE_APP_ID, MLS_EXECUTABLE_ID — multilingual and translated-executable handling.

Common Use Cases and Queries

Typical scenarios include identifying which program definition a submitted request used, auditing program registrations across applications, and reporting on enabled versus disabled programs. A common join pairs the program with its executable and translation:

• Join to FND_EXECUTABLES on EXECUTABLE_APPLICATION_ID and EXECUTABLE_ID to report the executable and execution method.
• Join to FND_CONCURRENT_PROGRAMS_TL on APPLICATION_ID and CONCURRENT_PROGRAM_ID for the user-facing translated name.
• Join to FND_CONCURRENT_REQUESTS on PROGRAM_APPLICATION_ID and CONCURRENT_PROGRAM_ID to list requests and their outcomes.
• Join to FND_REQUEST_SET_PROGRAMS / FND_REQUEST_GROUP_UNITS to trace which request sets include a program.

A representative query filters by business key: select CONCURRENT_PROGRAM_ID, EXECUTION_METHOD_CODE, ENABLED_FLAG from FND_CONCURRENT_PROGRAMS where APPLICATION_ID = :app and CONCURRENT_PROGRAM_NAME = :name. Reporting queries often combine ENABLED_FLAG with REQUEST_SET_FLAG to distinguish standalone programs from set-only members.

Related Objects

• FND_EXECUTABLES — referenced via EXECUTABLE_APPLICATION_ID, EXECUTABLE_ID.
• FND_CONCURRENT_REQUESTS — references this table via PROGRAM_APPLICATION_ID, CONCURRENT_PROGRAM_ID.
• FND_CONCURRENT_PROGRAMS_TL — translated names, joined on APPLICATION_ID, CONCURRENT_PROGRAM_ID.
• FND_CONCURRENT_REQUEST_CLASS — referenced via CLASS_APPLICATION_ID, CONCURRENT_CLASS_ID.
• FND_REQUEST_SET_PROGRAMS / FND_REQUEST_GROUP_UNITS — request-set membership.
• FND_CONCURRENT_COMPLEX_LINES / FND_CONCURRENT_QUEUE_CONTENT — queue and complex-program membership.
• FND_ATTACHED_DOCUMENTS / FND_DOCUMENTS — attachments keyed to program application and ID.
• FND_APPLICATION, FND_PRINTER, FND_PRINTER_STYLES, FND_SECURITY_GROUPS — lookup and code references.