Search Results rep_entity_id

Overview

ZX_REP_EXTRACT_V is an APPS-owned reporting view in Oracle E-Business Suite, listed under the FND – Application Object Library product. It is part of the ETRM (E-Business Tax Reporting and Management) extract infrastructure, which supports the generation of tax reporting extracts for regulatory and statutory reporting. The view consolidates information drawn from tax repository context, transaction detail, accounting extension, and journal extension tables into a single, flattened reporting structure. Its primary role is to present the fully resolved reporting context for each tax repository line — legal entity, tax registration, taxpayer identity, address, and transaction attributes — so that downstream extract programs and ad hoc reports can retrieve tax reporting data without navigating multiple underlying tables.

The view is central to the tax reporting extract flow initiated by a concurrent request. The request identifier drives the association between the reporting context (ZX_REP_CONTEXT_T) and the transaction detail (ZX_REP_TRX_DETAIL_T), ensuring that each row is scoped to the correct extract run.

Underlying Base Objects

The view is defined over four documented base objects, all exposed to APPS through synonyms:

• ZX_REP_CONTEXT_T — supplies reporting context information such as the reporting entity, context level code and manager, taxpayer identifier, entity name, location, city, county, state, province, addresses, country, postal code, and telephone number.
• ZX_REP_TRX_DETAIL_T — supplies transaction-level detail, including ledger, chart of accounts, detail tax line, extract source ledger, report line number, document sequence attributes, and transaction date.
• ZX_REP_ACTG_EXT_T — an accounting extension table used within the tax reporting extract model.
• ZX_REP_TRX_JX_EXT_T — a journal extension table supporting the reporting extract model.

The view joins ZX_REP_CONTEXT_T (aliased ZXREPCON) to ZX_REP_TRX_DETAIL_T (aliased ZXREPDET), with the request identifier and reporting entity linking the two. The accounting and journal extension tables participate in the broader extract model from which these primary objects are populated.

Key Columns

The columns most relevant to the user's search term, "doc_seq_value", are the document sequence attributes: DOC_SEQ_ID, DOC_SEQ_NAME, and DOC_SEQ_VALUE. These carry the identifier, name, and the resolved sequence value of the document sequence assigned to the transaction, supporting sequential numbering required for tax reporting.

Other significant columns include:

• REQUEST_ID — the concurrent request that generated the extract row.
• REP_ENTITY_ID and REP_CONTEXT_LVL_CODE / REP_CONTEXT_LVL_MNG — the reporting entity and its context level.
• LEDGER_ID, LEDGER_NAME, CHART_OF_ACCOUNTS_ID, FUNCTIONAL_CURRENCY_CODE — accounting and ledger identity.
• TAXPAYER_ID and LEGAL_ENTITY_TAX_REG_NUMBER — taxpayer and registration identity.
• REP_CONTEXT_ENTITY_NAME and the address columns (ADDRESS1–3, CITY, COUNTY, STATE, PROVINCE, COUNTRY, POSTAL_CODE, TEL_NUMBER) — the reporting party's location data.
• TRX_ID, TRX_NUMBER, TRX_DESCRIPTION, TRX_DATE, DETAIL_TAX_LINE_ID — transaction identification and detail linkage.

Common Use Cases and Queries

The view is typically queried to audit or reconcile a tax reporting extract run. A frequent scenario is validating document sequence values for reported transactions:

• Retrieve all rows for a specific request: SELECT * FROM apps.zx_rep_extract_v WHERE request_id = :p_request_id;
• Inspect document sequence attributes: SELECT trx_number, doc_seq_name, doc_seq_value FROM apps.zx_rep_extract_v WHERE request_id = :p_request_id;
• Reconcile reporting entity and taxpayer data: SELECT rep_context_entity_name, taxpayer_id, legal_entity_tax_reg_number FROM apps.zx_rep_extract_v WHERE rep_entity_id = :p_entity_id;

These queries support extract validation, troubleshooting of missing or misnumbered document sequences, and reconciliation against the underlying tax repository tables.