Results for “je_it_report_parameters”

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

Overview

JE_IT_REPORT_PARAMETERS is a table owned by the GL schema within the JE — European Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description identifies it as a repository of Italian report parameters, meaning it stores the runtime selection criteria and execution state associated with the Italian VAT and fiscal reporting programs delivered under the European localizations layer of Oracle General Ledger.

The table is keyed by REQUEST_ID, which serves as the primary key column of the JE_IT_REPORT_PARAMETERS_PK constraint. This design ties each parameter row to a concurrent program submission, so the row acts as the persisted run-time context for a single execution of an Italian report. A unique index, JE_IT_REPORT_PARAMETERS_U1, also exists on REQUEST_ID, confirming that one parameter row is permitted per concurrent request.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is hub-leaning. In a Data Vault model, REQUEST_ID would function as the natural business key of a hub, and the descriptive attributes would be distributed into one or more satellites. This classification is a modeling suggestion rather than a physical design statement, as the table itself is a conventional relational construct.

Key Information Stored

The table is documented with 15 columns, of which the following are the most significant for understanding its purpose.

• REQUEST_ID — The primary key and the sole business-key candidate, as confirmed by JE_IT_REPORT_PARAMETERS_PK and the unique index JE_IT_REPORT_PARAMETERS_U1. It links the parameter set to the underlying concurrent request.
• REPORT_STATUS — Captures the status of the Italian report run associated with the request.
• RUN_DATE — The date on which the report was executed, used for point-in-time reporting and audit.
• SET_OF_BOOKS_ID — Identifies the ledger (set of books) against which the report was executed, determining the accounting context.
• CONCURRENT_PROGRAM_ID — Identifies the concurrent program definition that generated the run, distinguishing among the various Italian localizations reports.
• PARAMETER_1 through PARAMETER_5 — Five generic parameter columns that hold the actual user-entered report selection values, such as reporting periods, registration ranges, or tax reporting options.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard Oracle Applications WHO columns providing auditability of row creation and modification, including the login context via LAST_UPDATE_LOGIN.

The distinction between the surrogate primary key and the business-key candidate is minimal here, since REQUEST_ID functions simultaneously as the database key and the natural identifier of the business event.

Common Use Cases and Queries

The primary use case is retrieving and re-running Italian localization reports with the exact parameters previously used. Querying by request identifier is the most common access path.

• Retrieving parameters for a specific concurrent request: SELECT * FROM gl.je_it_report_parameters WHERE request_id = :request_id;
• Listing recent runs ordered by execution time: SELECT request_id, report_status, run_date FROM gl.je_it_report_parameters ORDER BY run_date DESC;
• Auditing activity per ledger: SELECT set_of_books_id, COUNT(*) FROM gl.je_it_report_parameters GROUP BY set_of_books_id;
• Identifying the concurrent program and status distribution: SELECT concurrent_program_id, report_status, COUNT(*) FROM gl.je_it_report_parameters GROUP BY concurrent_program_id, report_status;

Reporting use cases include reconciliation of report executions against the concurrent manager request history, tracking completion status over a period, and reconstructing the parameter values that produced a given VAT or fiscal output.

Related Objects

The documented foreign key relationships connect this table to the following objects.

• JE_IT_VAT_REPORT_INV — References JE_IT_REPORT_PARAMETERS through the column REQUEST_ID, making the Italian VAT report inventory dependent on the parameter row identified by the same request.
• FND_CONCURRENT_REQUESTS — The standard concurrent requests table, which shares the REQUEST_ID business key and provides execution metadata such as phase and completion status.
• FND_CONCURRENT_PROGRAMS — Referenced conceptually through CONCURRENT_PROGRAM_ID to resolve the program name and application of the Italian report.
• FND_SET_OF_BOOKS / GL_LEDGERS — Resolves SET_OF_BOOKS_ID to the ledger definition used during the run.

Because REQUEST_ID is the shared identifier, joins between JE_IT_REPORT_PARAMETERS and JE_IT_VAT_REPORT_INV, or between the parameter table and FND_CONCURRENT_REQUESTS, are performed directly on REQUEST_ID without additional filtering columns.