Search Results ap_reporting_entity_lines_u1

Overview

AP.AP_REPORTING_ENTITY_LINES_ALL is the transactional detail table that stores the balancing segment lines belonging to each tax reporting entity defined in Oracle Payables. Reporting entities are the mechanism by which an organization groups one or more balancing segment values (typically the company or organization segment of the Accounting Flexfield) so that 1099 reporting can be performed for the correct legal or business unit. Every tax reporting entity must have at least one line that carries the balancing segment value for the organization being reported on, and a single entity may hold multiple lines when 1099 processing is consolidated across several organizations. A given balancing segment value may appear in only one reporting entity, which the application enforces as a business rule.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10 and is registered in FND Design Data under SQLAP.AP_REPORTING_ENTITY_LINES_ALL. In the Reporting Entity window, the rows of this table correspond directly to the Balancing Segment Values region.

From a Data Vault modeling perspective, the ETRM dependency metadata classifies this object as satellite-leaning. This suggests treating it as a satellite attached to AP_REPORTING_ENTITIES_ALL as its parent hub, at the granularity of balancing segment value per operating unit.

Key Information Stored

The table comprises nine documented columns. The most significant are:

• BALANCING_SEGMENT_VALUE — VARCHAR2(25). The Accounting Flexfield balancing segment value for the reporting entity. It forms part of the unique business key and, per the documented primary key (AP_REPORTING_ENTITY_LINES_PK), is the primary key column.
• ORG_ID — the operating unit identifier, and the second column of the unique index AP_REPORTING_ENTITY_LINES_U1 (BALANCING_SEGMENT_VALUE, ORG_ID). Together with the balancing segment value it defines the business-key candidate for the row.
• TAX_ENTITY_ID — NUMBER(15). The reporting entity identifier; a foreign key to AP.AP_REPORTING_ENTITIES_ALL. This is the column that links each balancing segment line back to its parent reporting entity.
• DESCRIPTION — VARCHAR2(80). Free-text description of the balancing segment value, useful for reporting and user-facing listings.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY. These capture audit information and are populated automatically by the application.

Note the distinction between the surrogate/technical key (BALANCING_SEGMENT_VALUE, as documented in the primary key) and the business-key candidate represented by the unique index AP_REPORTING_ENTITY_LINES_U1, which pairs the balancing segment value with ORG_ID. Reference to "AP_REPORTING_ENTITY_LINES_U1" in a search therefore refers to this uniqueness constraint rather than a column name.

Common Use Cases and Queries

Typical usage centers on resolving which balancing segment values roll up into a given 1099 reporting entity, and on validating that a balancing segment value is not assigned to more than one entity.

Retrieving all balancing segment lines for a reporting entity:

SELECT l.balancing_segment_value, l.description, l.org_id
FROM   ap.ap_reporting_entity_lines_all l
WHERE  l.tax_entity_id = :p_tax_entity_id;

Joining to the parent entity to obtain the entity name and Tax ID:

SELECT e.entity_name, l.balancing_segment_value, l.description
FROM   ap.ap_reporting_entity_lines_all  l,
       ap.ap_reporting_entities_all       e
WHERE  l.tax_entity_id = e.tax_entity_id;

Detecting a balancing segment value assigned to more than one entity (this should return no rows under normal operating conditions):

SELECT balancing_segment_value, COUNT(*)
FROM   ap.ap_reporting_entity_lines_all
GROUP  BY balancing_segment_value
HAVING COUNT(*) > 1;

Reporting and reconciliation use cases include building 1099 extract queries that map supplier payments to the correct reporting entity by balancing segment value, and auditing changes to reporting entity configuration via the WHO columns. Because the table is transactional, queries should generally filter by ORG_ID in a multi-organization environment to respect operating unit security.

Related Objects

• AP.AP_REPORTING_ENTITIES_ALL — the parent table; joined on TAX_ENTITY_ID. Defines the reporting entity itself, including its Tax ID and name.
• AP.AP_REPORTING_ENTITY_LINES_ALL is the source for the Reporting Entity window's Balancing Segment Values region, so the Reporting Entity setup forms and the Tax Reporting Entity concurrent programs depend on it.
• FND_USER — referenced implicitly by LAST_UPDATED_BY and CREATED_BY, enabling audit trails of who configured each line.
• GL Code Combination / Accounting Flexfield objects — the BALANCING_SEGMENT_VALUE corresponds to the balancing segment of the Accounting Flexfield, so reporting queries commonly join to GL_CODE_COMBINATIONS to resolve segment descriptions.
• AP.AP_REPORTING_ENTITY_LINES_U1 — the unique index (BALANCING_SEGMENT_VALUE, ORG_ID) enforcing the "one entity per balancing segment value" rule; the subject of the original search term.