Results for “rep_context_entity_name”

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

Overview

ZX_REP_CONTEXT_T is a table in the ZX (E-Business Tax) schema that stores context information for tax reports in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row in the table represents the reporting context for a tax report execution. The context captures operating unit address information for reports run at the ledger or operating unit level, and legal entity information for reports run at the legal entity level. This table functions as a foundational reference that downstream tax reporting detail records rely upon, ensuring that report output can be consistently tied back to the correct reporting entity, address, and party information.

From a heuristic Data Vault modeling perspective, ZX_REP_CONTEXT_T is classified as standalone. It does not exhibit foreign key dependencies on other parent tables within the documented FK structure, though it is referenced by downstream detail tables. The single unique index, ZX_REP_CONTEXT_T_U1 on REP_CONTEXT_ID, reinforces that the primary key is the sole documented business-key candidate. Modelers may treat this object as a hub-like reference dimension given its role as the anchor for reporting context, with the descriptive address and party columns behaving as satellite attributes.

Key Information Stored

The table contains 40 documented columns. The most significant are summarized below, distinguishing the surrogate primary key from business-key and descriptive attributes.

• REP_CONTEXT_ID — Primary key (ZX_REP_CONTEXT_T_PK), the surrogate identifier for each reporting context row. Also forms the unique business-key candidate via index ZX_REP_CONTEXT_T_U1.
• REP_ENTITY_ID — Identifier of the reporting entity associated with the context.
• REP_CONTEXT_ENTITY_LOCATION_ID — Location identifier for the reporting entity.
• REP_CONTEXT_ENTITY_NAME, REP_CONTEXT_ENTITY_CITY, REP_CONTEXT_ENTITY_STATE, REP_CONTEXT_ENTITY_PROVINCE, REP_CONTEXT_ENTITY_COUNTY, REP_CONTEXT_ENTITY_COUNTRY, REP_CONTEXT_ENTITY_POSTAL_CODE — Denormalized address components of the reporting entity, populated for ledger and operating unit level reports.
• REP_CONTEXT_ENTITY_ADDRESS1, ADDRESS2, ADDRESS3 — Street-level address lines for the reporting entity.
• REP_CONTEXT_ENTITY_TEL_NUMBER — Telephone number of the reporting entity.
• REP_CONTEXT_LVL_MNG, REP_CONTEXT_LVL_CODE — Reporting level management and code indicators that describe the granularity at which the tax report was executed (for example, ledger, operating unit, or legal entity).
• LEGAL_CONTACT_PARTY_NAME, LEGAL_CONTACT_TITLE, TAXPAYER_ID, LEGAL_AUTHORITY_NAME — Legal entity and contact attributes used for legal entity level reporting.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns for audit tracking.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID — Concurrent program execution context identifying the report run that generated or consumed the row.

Common Use Cases and Queries

The primary use case is resolving report output to its reporting context. Because detail tables such as ZX_REP_TRX_DETAIL_T store REP_CONTEXT_ID, joining to ZX_REP_CONTEXT_T resolves entity names, addresses, and legal party information required for filing or reconciliation.

• Reconstructing a tax report header: join ZX_REP_TRX_DETAIL_T to ZX_REP_CONTEXT_T on REP_CONTEXT_ID to retrieve entity name, address, and level codes for each detail line.
• Auditing report runs: query by REQUEST_ID or PROGRAM_ID to identify which concurrent request produced a given context, using CREATION_DATE and CREATED_BY for traceability.
• Reporting at the legal entity level: filter on REP_CONTEXT_LVL_CODE and use LEGAL_CONTACT_PARTY_NAME and TAXPAYER_ID for statutory filings.
• Reporting at the operating unit or ledger level: select the REP_CONTEXT_ENTITY_* address columns to populate report headers.

A representative query pattern is: SELECT c.rep_context_id, c.rep_context_entity_name, c.rep_context_entity_city, c.rep_context_entity_country FROM zx.zx_rep_context_t c WHERE c.rep_context_lvl_code = :level; and joining detail rows via ZX_REP_TRX_DETAIL_T d ON d.rep_context_id = c.rep_context_id WHERE d.request_id = :request_id.

Related Objects

The documented foreign key relationships and schema context identify the following significant related objects.

• ZX_REP_TRX_DETAIL_T — The principal child table. It references ZX_REP_CONTEXT_T via REP_CONTEXT_ID, linking individual tax transaction detail lines to their reporting context.
• ZX_REP_CONTEXT_T_PK — The primary key constraint enforcing uniqueness of REP_CONTEXT_ID.
• ZX_REP_CONTEXT_T_U1 — The unique index on REP_CONTEXT_ID, serving as the documented business-key candidate.
• ZX schema reporting tables — Other ZX tax reporting and extract objects that consume reporting context data for report generation.
• FND concurrent program tables — Referenced through REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID to associate contexts with their originating concurrent requests.

Because the object is classified as standalone, no parent-table foreign keys are documented; dependencies flow outward to detail and reporting tables within the E-Business Tax module.