Results for “default_location_id”

8 results




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

Overview

AP_WEB_PREFERENCES is an Oracle Payables (AP) transaction and setup table that stores user-level preferences for Oracle Internet Expenses, the web-based expense entry and approval application delivered with the E-Business Suite. Each row represents a single employee's saved defaults and behavioral settings used when that user creates, validates, or submits expense reports through the self-service interface. The table resides in the AP schema and is marked VALID in both Oracle EBS 12.1.1 and 12.2.2. Its documented physical schema in 12.2.2 comprises 20 columns.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table is keyed by EMPLOYEE_ID, which behaves as a business key identifying the owning party, while the remaining attributes are descriptive preferences that change over time. This pattern is consistent with a satellite attached to an employee or party hub rather than an independent hub or a link resolving a many-to-many relationship.

Key Information Stored

The unique index AP_WEB_PREFERENCES_U1 on EMPLOYEE_ID establishes the employee as the business-key candidate; there is no separately documented surrogate primary key column in the ETRM metadata, so EMPLOYEE_ID functions as the effective row identifier.

Common Use Cases and Queries

Typical usage includes diagnosing why an expense report defaulted to an unexpected approver, location, or template; auditing which employees have enabled detail validation or foreign-currency defaults; and confirming that preference rows exist before Go-Live or after a user-data migration.

A representative query returns the core defaults for a given employee:

  • SELECT employee_id, default_approver_id, default_expense_template_id, default_location_id, default_source FROM ap.ap_web_preferences WHERE employee_id = :emp_id;

To join default locations to their descriptive names, use the documented foreign key: AP_WEB_PREFERENCES.DEFAULT_LOCATION_ID = AP_POL_LOCATIONS_B.LOCATION_ID. Reporting queries frequently combine this table with employee data to reconcile setup coverage against the active workforce.

Related Objects

  • AP_POL_LOCATIONS_B — referenced by DEFAULT_LOCATION_ID; supplies the location name and address context for the default expense location.
  • PSB_EMPLOYEES — referenced by EMPLOYEE_ID; the party/employee source that anchors the preference row and its satellite classification.
  • AP_EXPENSE_REPORT_HEADERS_ALL — consumes the approver, template, purpose, and currency defaults when reports are created.
  • AP_WEB_EXPENSE_TEMPLATES — defines the templates referenced by DEFAULT_EXPENSE_TEMPLATE_ID.
  • AP_WEB_DB_AP_EXPENSES_PKG / OIE public APIs — Oracle Internet Expenses program units that read and write these preferences at runtime.