Search Results pdm_destination_id
Overview
The OIE_PDM_DESTINATIONS table is a core data structure within the Oracle E-Business Suite (EBS) Payables module, specifically supporting the functionality for per diem expense management. Its primary role is to store destination-specific information linked to per diem expense lines. This table acts as a junction, connecting individual expense report lines to their associated geographical locations, thereby enabling the system to calculate and apply the correct per diem rates based on company travel policy for each destination. Its existence is critical for the accurate processing and auditing of travel-related reimbursements in Oracle Internet Expenses (OIE).
Key Information Stored
The table's structure is defined by its primary and foreign key relationships. The central column is PDM_DESTINATION_ID, which serves as the unique primary key for each record. Two other columns are of paramount importance as they establish the table's functional links to other core entities. The REPORT_LINE_ID column foreign keys to the AP_EXPENSE_REPORT_LINES_ALL table, tethering the destination data to a specific line item on an employee's expense report. The LOCATION_ID column foreign keys to the AP_POL_LOCATIONS_B table, which is the master table for policy locations. This link associates the expense line with the precise destination (e.g., city, region) as defined in the system's travel policy setup, which is used for per diem rate derivation.
Common Use Cases and Queries
This table is primarily accessed for reporting and data validation related to per diem expenses. A common operational use case is verifying the destination applied to a submitted expense line for audit purposes. For reporting, it enables analyses such as summarizing per diem costs by destination or identifying frequently traveled locations. A typical query would join OIE_PDM_DESTINATIONS to the expense report lines and policy locations to create a detailed dataset.
Sample Query Pattern:
SELECT erl.report_header_id, erl.line_number,
pdm.pdm_destination_id, loc.location_name
FROM ap_expense_report_lines_all erl,
oie_pdm_destinations pdm,
ap_pol_locations_b loc
WHERE erl.report_line_id = pdm.report_line_id
AND pdm.location_id = loc.location_id
AND erl.itemization_parent_id IS NULL; -- To get parent lines
Related Objects
- AP_EXPENSE_REPORT_LINES_ALL: This is the master table for expense report line items. The OIE_PDM_DESTINATIONS table references it via the foreign key on the column OIE_PDM_DESTINATIONS.REPORT_LINE_ID. Each record in OIE_PDM_DESTINATIONS is a child of a single expense line.
- AP_POL_LOCATIONS_B: This table stores the master list of locations defined for travel policy. The OIE_PDM_DESTINATIONS table references it via the foreign key on the column OIE_PDM_DESTINATIONS.LOCATION_ID. This relationship ties the per diem destination to the official policy location used for rate lookups.
-
Table: OIE_PDM_DESTINATIONS
12.1.1
owner:AP, object_type:TABLE, fnd_design_data:SQLAP.OIE_PDM_DESTINATIONS, object_name:OIE_PDM_DESTINATIONS, status:VALID, product: AP - Payables , description: This table holds per diem destination information. , implementation_dba_data: AP.OIE_PDM_DESTINATIONS ,
-
Table: OIE_PDM_DESTINATIONS
12.2.2
owner:AP, object_type:TABLE, fnd_design_data:SQLAP.OIE_PDM_DESTINATIONS, object_name:OIE_PDM_DESTINATIONS, status:VALID, product: AP - Payables , description: This table holds per diem destination information. , implementation_dba_data: AP.OIE_PDM_DESTINATIONS ,