Results for “ap_expense_report_params_all”

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

Overview

AP_EXPENSE_REPORT_PARAMS_ALL is a Payables (AP) module table that stores expense type information for expense report templates in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a configurable line parameter — an expense type entry — that defines how a particular expense line behaves on an expense report, including prompting, receipt requirements, tax handling, itemization rules, and policy association. It is a core configuration table for the Oracle Internet Expenses (OIE) / Payables expense reporting feature set.

The table is owned by the AP schema and is classified as VALID in ETRM. Based on the foreign key structure, the heuristic Data Vault classification is hub-leaning. In Data Vault modeling terms, this suggests treating PARAMETER_ID as a hub business key, with the descriptive attributes (prompts, flags, policy references) modeled as a satellite, while the associations to expense reports, expenditure types, and policies function as links.

Key Information Stored

The primary key is AP_EXPENSE_REPORT_PARAMS_PK, defined on the surrogate column PARAMETER_ID. Two unique indexes define business-key candidates:

• AP_EXPENSE_REPORT_PARAMS_U1 — (PARAMETER_ID, ZD_EDITION_NAME)
• AP_EXPENSE_REPORT_PARAMS_U2 — (EXPENSE_REPORT_ID, PROMPT, ORG_ID, ZD_EDITION_NAME)

The table contains 37 documented columns. The most significant include:

• PARAMETER_ID — surrogate primary key identifying each expense type parameter.
• EXPENSE_REPORT_ID — FK to AP_EXPENSE_REPORTS_ALL, identifying the owning expense report template.
• PROMPT / WEB_FRIENDLY_PROMPT — the display label shown to users for this expense type.
• LINE_TYPE_LOOKUP_CODE — classifies the line type for the expense entry.
• EXPENSE_TYPE_CODE / CATEGORY_CODE — classification of the expense type.
• PA_EXPENDITURE_TYPE — FK to PA_EXPENDITURE_TYPES, mapping the line to a Projects expenditure type.
• COMPANY_POLICY_ID — FK to AP_POL_HEADERS, linking the parameter to an expense policy.
• RECEIPT_REQUIRED_FLAG / REQUIRE_RECEIPT_AMOUNT — receipt enforcement rules.
• JUSTIFICATION_REQUIRED_FLAG — whether a justification is mandatory.
• AMOUNT_INCLUDES_TAX_FLAG / VAT_CODE — tax handling attributes.
• ITEMIZATION_REQUIRED_FLAG / ITEMIZATION_ALL_FLAG — itemization control flags.
• ORG_ID — multi-org operating unit context.
• ZD_EDITION_NAME — editioning column used in Online Patching (12.2.2) to partition the table by edition.

Common Use Cases and Queries

This table is primarily queried to audit and report on expense report template configuration.

• Listing expense types for a template: join to AP_EXPENSE_REPORTS_ALL to retrieve all parameters for a given report.
• Receipt and policy auditing: identify which expense types require receipts or are bound to a company policy.
• Projects integration checks: confirm mapping of expense lines to PA_EXPENDITURE_TYPES.
• Web enablement reporting: filter on WEB_ENABLED_FLAG and WEB_SEQUENCE to review the user-facing layout.

A representative query:

• SELECT p.PARAMETER_ID, p.PROMPT, p.EXPENSE_TYPE_CODE, p.RECEIPT_REQUIRED_FLAG FROM AP.AP_EXPENSE_REPORT_PARAMS_ALL p WHERE p.EXPENSE_REPORT_ID = :report_id AND p.ORG_ID = :org_id;

Related Objects

The table participates in several documented foreign key relationships:

• AP_EXPENSE_REPORTS_ALL — parent template; joined via EXPENSE_REPORT_ID. Also references this table through DEFAULT_PARAMETER_ID.
• PA_EXPENDITURE_TYPES — referenced via PA_EXPENDITURE_TYPE.
• AP_POL_HEADERS — referenced via COMPANY_POLICY_ID.
• AP_CARD_PARAMETERS — references PARAMETER_ID to link corporate card configuration.
• AP_POL_ITEMIZATIONS — references PARAMETER_ID and ITEMIZATION_PARAMETER_ID for itemization rules.

These relationships make AP_EXPENSE_REPORT_PARAMS_ALL a central configuration hub for expense reporting, corporate card integration, and policy enforcement within Oracle Payables and Internet Expenses.