Results for “je_es_modelo_347_all”

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

Overview

The JE_ES_MODELO_347_ALL table is a Spanish localization data object owned by the JE schema within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides in the JE – European Localizations product family and stores the information required to produce the Spanish Modelo 347 declaration, the annual informative return that Spanish legal entities must file with the Agencia Tributaria to report third-party operations (operations with third parties) whose cumulative value exceeded the statutory threshold during the fiscal year. In practice, the table holds the declarant and counterparty identification data, fiscal addresses, and aggregated amounts that feed the Modelo 347 report generated from Payables and Receivables activity.

The object is classified as standalone under the heuristic Data Vault classification mined from its foreign-key structure. This classification indicates that the table has no documented parent or child relationships in the ETRM reference model, and should therefore be treated as an independent data set rather than as a hub, link, or satellite within a Data Vault implementation. Where integration with a wider warehouse model is required, the table is best modeled as an isolated reference/summary entity keyed by its own business identifiers.

Key Information Stored

The table contains 18 documented columns. The most significant are summarized below.

• SET_OF_BOOKS_ID — Identifies the ledger (set of books) for which the Modelo 347 data is maintained. This is part of the primary key and scopes all records to a specific accounting configuration.
• TIPO — The operation or record type, distinguishing the nature of the reported third-party operation. Part of the primary key.
• FIN_IND — The final indicator flag, part of the primary key, used to flag the terminal or closing record for a given grouping.
• NIF — The counterparty's Spanish tax identification number (Número de Identificación Fiscal), the key fiscal identifier used in the return.
• NOMBRE — The legal name of the third party (counterparty) associated with the reported operations.
• IMPORTE — The aggregated monetary amount reported for the counterparty, normally the annual sum of operations subject to the declaration.
• SIGLA — The abbreviated name or acronym used to identify the counterparty.
• MUNICIPIO — The municipality of the counterparty's fiscal address.
• CODIGO_POSTAL — The postal code of the counterparty's fiscal address.
• VIA_PUBLICA — The street or public way component of the fiscal address.
• NUMERO, ESCALERA, PISO, PUERTA — The street number, stairway, floor, and door components that complete the structured Spanish address.
• REF_CATASTRAL — The Spanish cadastral reference of the property, an additional address verification attribute.
• FLAG_ARRENDA — A flag indicating whether the operation relates to a lease (arrendamiento) subject to special reporting treatment.
• ORG_ID — The operating unit identifier, supporting multi-organization reporting within the EBS instance.

The surrogate primary key is defined by JE_ES_MODELO_347_ALL_PK on the composite of TIPO, FIN_IND, and SET_OF_BOOKS_ID. Of these, SET_OF_BOOKS_ID and TIPO function as the principal business-key candidates; FIN_IND completes the uniqueness constraint and differentiates the closing/final indicator record within a ledger and type combination.

Common Use Cases and Queries

The primary use case is generation of the Modelo 347 annual informative return. Reporting logic typically selects all records for a given ledger and fiscal year, aggregates amounts by NIF, and formats the output according to the AEAT record layout. The counterparty identification and address columns supply the declarant and third-party blocks of the return.

A representative query pattern retrieves declared amounts per counterparty for a ledger:

• SELECT NIF, NOMBRE, SIGLA, IMPORTE FROM JE.JE_ES_MODELO_347_ALL WHERE SET_OF_BOOKS_ID = :ledger_id AND TIPO = :operation_type;

Address validation and cleanup of historical Modelo 347 data commonly filters on the structured address columns (MUNICIPIO, CODIGO_POSTAL, VIA_PUBLICA, NUMERO) to identify incomplete counterparty records. A second pattern isolates lease-related operations using the FLAG_ARRENDA column, since lease reporting carries distinct treatment. Multi-organization environments additionally constrain results by ORG_ID to reconcile operating-unit-level totals against ledger-level balances.

Related Objects

Because the ETRM model classifies this object as standalone, it exposes no documented foreign-key parent or child relationships. The applicable related objects are therefore best derived from the localization architecture and the Modelo 347 reporting flow rather than from FK metadata.

• GL_SETS_OF_BOOKS — Joined on SET_OF_BOOKS_ID to resolve ledger name, currency, and accounting period context for the reported operations.
• HR_OPERATING_UNITS — Joined on ORG_ID to determine the operating unit responsible for the counterparty operations.
• AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL — Source of the third-party name, NIF, and fiscal address data that populate NOMBRE, NIF, and the address columns for Payables-sourced operations.
• AP_INVOICES_ALL and AP_PAYMENT_SCHEDULES_ALL — Provide the transaction-level amounts subsequently aggregated into IMPORTE for suppliers.
• RA_CUSTOMERS and AR_PAYMENT_SCHEDULES_ALL — The Receivables-side counterparts supplying customer identification and transaction amounts for the declaration.
• JE_ES_REPORTING_PARAMETERS (localization parameter objects) — Configuration data controlling thresholds and filing parameters used when this table is populated.

No PL/SQL package or concurrent program is documented as a direct dependency in the ETRM metadata; report generation logic is delivered through the Spanish localization report set that consumes this table.