Results for “ap_pol_locations_b”

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

Overview

AP_POL_LOCATIONS_B is a Payables (AP) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores policy schedule location information. It serves as the master reference for physical or logical locations used by Oracle Payables policy schedules, which govern reimbursement and expense rules applied to specific places of business. The table is owned by the AP schema and carries a VALID status in the data dictionary. From a data modeling perspective, the ETRM metadata classifies this object as hub-leaning, meaning it behaves primarily as a foundational reference entity that other transactional and setup tables point to through foreign keys rather than as a transactional or link table. Its relatively small, slowly changing footprint and its central role as a target of multiple foreign keys reinforce that classification.

Key Information Stored

The table contains 15 documented columns. The surrogate primary key is LOCATION_ID, which is also the sole business-key candidate as documented through the unique index AP_POL_LOCATIONS_B_U1 (LOCATION_ID). TERRITORY_CODE identifies the territory or country associated with the location and references FND_TERRITORIES. UNDEFINED_LOCATION_FLAG indicates whether the location is a placeholder rather than a fully defined address. LOCATION_TYPE and COUNTRY further describe the nature and geographic placement of the location. STATE_PROVINCE_ID, COUNTY_ID, and CITY_LOCALITY_ID provide hierarchical geographic detail; each is a self-referencing foreign key pointing back into AP_POL_LOCATIONS_B, supporting a structured nested-address model. END_DATE and STATUS control the effective lifecycle and activation state of the location record. The audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — follow standard EBS WHO-column conventions and record who created and last modified each row.

Common Use Cases and Queries

Typical uses include validating expense report destinations, resolving policy schedule applicability by location, and joining locations to expense lines and policy lines for reporting. A representative query retrieving active locations with their territory and status:

• SELECT location_id, territory_code, location_type, status, end_date FROM ap.ap_pol_locations_b WHERE status = 'A' AND (end_date IS NULL OR end_date > SYSDATE);
• Join expense lines to their location: SELECT l.location_id, e.expense_report_line_id FROM ap.ap_pol_locations_b l, ap.ap_expense_report_lines_all e WHERE l.location_id = e.location_id;
• Resolve policy line locations: SELECT p.pol_line_id, l.location_id FROM ap.ap_pol_lines p, ap.ap_pol_locations_b l WHERE p.location_id = l.location_id;
• Identify a user's default expense location: SELECT w.user_id, l.location_id FROM ap.ap_web_preferences w, ap.ap_pol_locations_b l WHERE w.default_location_id = l.location_id;
• Traverse the geographic hierarchy: self-joins on STATE_PROVINCE_ID, COUNTY_ID, and CITY_LOCALITY_ID.

These patterns support audit, reimbursement reconciliation, and location-based spend analysis.

Related Objects

AP_POL_LOCATIONS_B participates in a well-documented relationship graph. It references FND_TERRITORIES through TERRITORY_CODE. It self-references on STATE_PROVINCE_ID, COUNTY_ID, and CITY_LOCALITY_ID, forming an internal geographic hierarchy. Several objects depend on it: AP_EXPENSE_REPORT_LINES_ALL references it via LOCATION_ID and LOCATION_TO_ID; AP_POL_LINES references LOCATION_ID; AP_POL_SCHEDULE_OPTIONS references LOCATION_ID; AP_WEB_PREFERENCES references DEFAULT_LOCATION_ID; and OIE_PDM_DESTINATIONS references LOCATION_ID. Together these dependencies establish AP_POL_LOCATIONS_B as a shared hub for expense reporting, policy scheduling, user preferences, and destination data across the Payables and related modules.