Results for “oie_pdm_destinations”

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

Overview

OIE_PDM_DESTINATIONS is an Oracle E-Business Suite table owned by the AP (Payables) schema that stores per diem destination information. It resides within the Payables product family and supports per diem expense processing, a feature used to reimburse employees for meals and incidental expenses incurred during business travel. Each row associates a per diem destination — a travel location — with an expense report line and a geographic location, along with an effective date range during which that destination assignment applies.

Within the Oracle EBS 12.1.1 and 12.2.2 data model, this table acts as an intersection between an expense report line and a defined location, carrying the validity period of that association. In a heuristic Data Vault classification, OIE_PDM_DESTINATIONS models as a link: it connects two business entities (the expense report line and the location) via foreign keys and carries descriptive context (start and end dates). This classification is a modeling suggestion derived from the foreign-key structure, not a documented Oracle designation. The table is registered as VALID and contains 10 documented columns in the ETRM 12.2.2 physical schema.

Key Information Stored

The table's surrogate primary key is PDM_DESTINATION_ID, enforced by the primary key constraint OIE_PDM_DESTINATIONS_PK1 and mirrored by the unique index OIE_PDM_DESTINATIONS_U1. This column is the value users typically search for as "pdm_destination_id," and it is the identifier propagated to dependent child tables.

Business-relevant columns include:

• REPORT_LINE_ID — foreign key to AP_EXPENSE_REPORT_LINES_ALL, identifying the expense report line to which this per diem destination applies.
• LOCATION_ID — foreign key to AP_POL_LOCATIONS_B, identifying the destination location record.
• START_DATE — the date from which the per diem destination assignment becomes effective.
• END_DATE — the date on which the assignment ceases to be effective.

The remaining documented columns are standard Oracle EBS audit and ownership attributes: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE. These support WHO-column auditing and change tracking consistent with AP schema conventions. The business-key candidate is the surrogate identifier PDM_DESTINATION_ID; the effective-dated pairing of REPORT_LINE_ID, LOCATION_ID, START_DATE, and END_DATE functions as the natural business relationship.

Common Use Cases and Queries

Typical scenarios include retrieving all per diem destinations for a given expense report line, resolving the location details behind a per diem assignment, and auditing effective-dated destination changes. A common query joins to the expense report lines and the location table:

• Retrieve destinations by expense report line: SELECT * FROM AP.OIE_PDM_DESTINATIONS WHERE REPORT_LINE_ID = :report_line_id;
• Resolve location detail: SELECT d.PDM_DESTINATION_ID, d.START_DATE, d.END_DATE, l.LOCATION_NAME FROM AP.OIE_PDM_DESTINATIONS d, AP.AP_POL_LOCATIONS_B l WHERE d.LOCATION_ID = l.LOCATION_ID AND d.PDM_DESTINATION_ID = :id;
• Effective-date filtering: restrict results where SYSDATE BETWEEN START_DATE AND END_DATE to find currently active per diem destinations.
• Find child daily breakup records: join to OIE_PDM_DAILY_BREAKUPS on PDM_DESTINATION_ID to report the daily per diem breakdown for each destination.

Reporting uses include per diem reimbursement analysis, travel destination auditing, and reconciliation of expense report lines against configured per diem locations.

Related Objects

The most significant related objects, based on documented foreign-key relationships, are:

• AP_EXPENSE_REPORT_LINES_ALL — parent of REPORT_LINE_ID; the expense report line driving the per diem destination.
• AP_POL_LOCATIONS_B — parent of LOCATION_ID; the defined destination location.
• OIE_PDM_DAILY_BREAKUPS — child table referencing OIE_PDM_DESTINATIONS.PDM_DESTINATION_ID; stores the daily per diem breakdowns for each destination.
• OIE_PDM_DESTINATIONS_PK1 and OIE_PDM_DESTINATIONS_U1 — the primary key constraint and unique index enforcing uniqueness of PDM_DESTINATION_ID.

Together these objects form the per diem destination sub-model within Oracle Payables expense reporting.