Results for “rtf_file_source”
7 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The JL_BR_SPED_EXTR_PARAM table is a Latin America Localizations (JL) object in the Oracle E-Business Suite database. It functions as a parameter repository for the Brazilian SPED (Sistema Público de Escrituração Digital) Accounting Data extract programs. Every time a SPED data extraction concurrent program is submitted, the run-time parameters supplied by the user — including ledger, legal entity, establishment, reporting period, and reporting mode selections — are persisted in this table against the generating concurrent request. This persistence supports auditability, re-submission, and downstream reporting by allowing extraction runs to be identified and reproduced from stored parameters.
Under the supplied Data Vault classification heuristic, this object is characterized as standalone. In Data Vault modeling terms, this suggests the table behaves primarily as a satellite-like record of extraction events keyed to a request, rather than as a hub or link resolving relationships between business entities. The classification is a modeling suggestion derived from the absence of inbound dependencies in the mined foreign key structure.
Key Information Stored
The documented schema for 12.2.2 contains 37 columns. The most operationally significant are:
- REQUEST_ID — The concurrent request identifier. This is the designated business-key candidate, enforced by unique index
JL_BR_SPED_EXTR_PARAM_U1. It effectively functions as the surrogate key routing each parameter set to its extraction execution. - LEDGER_ID — The ledger against which the SPED extract is executed.
- LEGAL_ENTITY_ID — The legal entity for the extraction; foreign key to
FV_LEGAL_ENTITIES. - ESTABLISHMENT_ID and ESTABLISHMET_NAME — The reporting establishment and its name.
- PERIOD_TYPE, PERIOD_NAME, and ADJUSTMENT_PERIOD — The accounting period selection, including whether an adjustment period is in scope.
- SPEC_SITU_INDIC, SPEC_SITU_START_DATE, SPEC_SITU_END_DATE — The special situation indicator and its effective date range.
- BOOKKEEPING_TYPE and ESTB_ACCT_TYPE — Bookkeeping and establishment accounting type classifications.
- REPORT_MODE and ACCT_STMT_INDF — The reporting mode and accounting statement indicator controlling extract output.
- DATA_EXIST — Flag recording whether qualifying data was found for the submission.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns.
Additional columns such as AGC_SOURCE, RTF_FILE_SOURCE, REGISTRATION_SOURCE, and the XLE_/ZX_ registration and tax identifiers capture source-system and municipal/state registration context used in SPED file generation.
Common Use Cases and Queries
Consultants and support analysts query this table to reconstruct the exact parameters of a previously run SPED extract — particularly when validating why a particular ledger or establishment produced (or failed to produce) output. A typical pattern joins the parameter record to the concurrent request table:
- Retrieve parameters for a specific run:
SELECT * FROM jl.jl_br_sped_extr_param WHERE request_id = :request_id; - List recent extracts for a legal entity:
SELECT request_id, ledger_id, period_name, report_mode, data_exist
FROM jl.jl_br_sped_extr_param
WHERE legal_entity_id = :legal_entity_id
ORDER BY creation_date DESC; - Audit whether any submission returned data:
SELECT request_id, data_exist, creation_date
FROM jl.jl_br_sped_extr_param WHERE data_exist = 'N';
These queries support troubleshooting, audit trails, and reconciliation of SPED submissions across periods.
Related Objects
FV_LEGAL_ENTITIES— Referenced byLEGAL_ENTITY_ID; the primary documented foreign key relationship.FND_CONCURRENT_REQUESTS— Join onREQUEST_IDto obtain request status, phase, and completion details.JL_BR_SPED_EXTR(extract data tables) — Populated by the same concurrent programs that recorded parameters here.GL_LEDGERS/GL_LEDGER_NORM_SEG_VALS— Provide ledger context forLEDGER_ID.BALSHEET_REP_REQUEST_IDandINCMSTMT_REP_REQUEST_ID— Internal references to balance sheet and income statement report requests associated with the extraction.
Together these objects form the operational envelope around Brazilian SPED accounting extraction in Oracle EBS 12.1.1 and 12.2.2.
-
A table to store the parameters of every Accounting SPED Data extract program submitted
-
eTRM - JL Tables and Views 12.2.2
JL_ZZ_INFO_T is temporary table