Search Results ap_reporting_entities_u3




Overview

AP.AP_REPORTING_ENTITIES_ALL is a transaction data table in the Oracle Payables (AP) schema that stores the tax reporting entities defined by an organization for 1099 and related statutory reporting. The table backs the Reporting Entity window and is a prerequisite for 1099 processing: at least one reporting entity must exist before 1099 reports can be generated, and each submitted report is produced once per defined entity. This design supports multi-organization reporting where a single operating unit may report under more than one Tax Identification Number.

In Oracle E-Business Suite 12.1.1 and 12.2.2, the table is registered under FND Design Data as SQLAP.AP_REPORTING_ENTITIES_ALL and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The documented physical schema spans 37 columns and includes a unique primary key, AP_REPORTING_ENTITIES_PK, on TAX_ENTITY_ID. From a Data Vault modeling perspective, the table is heuristic-classified as hub-leaning: its stable business key and long-lived entity identity suggest a hub pattern, with descriptive attributes such as address and reference numbers behaving as satellite content. This classification is a modeling suggestion only; the table is a native EBS object, not a Data Vault artifact.

Key Information Stored

Each row describes one reporting entity. The most significant columns are:

Three unique indexes enforce business keys: AP_REPORTING_ENTITIES_U1 on (ENTITY_NAME, ORG_ID), AP_REPORTING_ENTITIES_U2 on (TAX_IDENTIFICATION_NUM, ORG_ID) — the index most commonly referenced in lookup troubleshooting — and AP_REPORTING_ENTITIES_U3 on TAX_ENTITY_ID. All three reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

Reporting-entity data supports 1099 report generation, 1096 transmittal creation, and tax filing reconciliation. A typical lookup resolves an entity name from its TIN within an operating unit:

  • SELECT tax_entity_id, entity_name, tax_identification_num FROM ap.ap_reporting_entities_all WHERE tax_identification_num = :tin AND org_id = :org;
  • Listing all entities for an operating unit: SELECT entity_name, tax_identification_num, primary_entity_flag FROM ap.ap_reporting_entities_all WHERE org_id = :org ORDER BY entity_name;
  • Joining to locations for filing addresses: SELECT e.entity_name, l.address_line_1, l.city FROM ap.ap_reporting_entities_all e, hr_locations_all l WHERE e.location_id = l.location_id;

Because AP_REPORTING_ENTITIES_U2 is unique, duplicate TIN attempts raise a unique constraint error — a frequent point of diagnostic value when 1099 report submission fails. Queries should always filter by ORG_ID, since the uniqueness of both name and TIN is scoped to the operating unit.

Related Objects

The table participates in a small but tightly coupled reporting cluster:

  • AP.AP_1096_DATA_ALL — references TAX_ENTITY_ID; stores 1096 transmittal data per entity.
  • AP.AP_REPORTING_ENTITY_LINES_ALL — references TAX_ENTITY_ID; holds 1099 report lines attributed to each entity.
  • AP.FV_1096_DATA_ALL — the federal 1096 counterpart referencing TAX_ENTITY_ID.
  • HR.HR_LOCATIONS_ALL — referenced by LOCATION_ID; provides the reporting entity address.
  • FND_USER and FND_LOGINS — implicitly referenced by the who columns for audit attribution.

Together these objects form the entity-reporting lineage used by the Payables 1099 submission and filing programs.