Search Results calculate_amount_flag

Overview

The APBV_EXPENSE_REPORT_PARAMS view is a secured, read-only Oracle E-Business Suite database object owned by the APPS schema and defined within the Oracle Payables (AP) product family. In EBS 12.1.1 and 12.2.2, this view exposes the configuration parameters that govern how individual expense report templates (expense report definitions) behave in the Oracle Internet Expenses (OIE) and Payables Expense reporting flows. Each row represents a single configurable parameter attached to a specific expense report definition, identified by EXPENSE_REPORT_ID, and controls attributes such as prompting, receipt and justification requirements, tax handling, and data capture rules.

The view is important for reporting and integration because it provides a stabilized, business-facing interface over the underlying parameter storage. Downstream reports, personalizations, and interfaces frequently need to know which prompts, flags, and validation rules apply to a given expense template — for example, whether a receipt is mandatory, whether amounts include tax, or which expense type code drives categorization. Because the view is defined WITH READ ONLY and enforces a _SEC organization security predicate on ORG_ID, it also supports multi-org security consistent with Oracle EBS access control conventions.

Underlying Base Objects

Per the documented ETRM metadata, APBV_EXPENSE_REPORT_PARAMS is defined over a single referenced base object: the synonym AP_EXPENSE_REPORT_PARAMS_ALL. The view text aliases this base as AERPA and selects its columns without joins or aggregation, functioning essentially as a secured projection of the _ALL table. The _ALL suffix indicates the base table holds organization-stripped data across operating units, with the ORG_ID column distinguishing records by organization. The view applies a mandatory security predicate:

• WHERE '_SEC:AERPA.ORG_ID' IS NOT NULL — the EBS row-level security (RLS / VPD) policy is injected here, restricting rows to those organizations the querying user is authorized to see.
• WITH READ ONLY — prevents DML through the view, ensuring expense parameter configuration is only modifiable through the supported Payables/OIE setup forms.

Because the definition references a synonym rather than the physical table directly, the view depends on the APPS.AP_EXPENSE_REPORT_PARAMS_ALL synonym resolving to the actual Payables base table. The view name prefix APBV follows Oracle's convention for Payables business views.

Key Columns

The view exposes thirty-one columns. The most functionally significant include:

• PARAMETER_ID — primary identifier for the parameter row.
• EXPENSE_REPORT_ID — the expense report definition/template to which the parameter belongs.
• EXPENSE_TYPE_CODE — the expense type classification associated with the parameter; this is the column most directly relevant to the user's search term and links parameter configuration to an expense type used in expense entry.
• PROMPT and WEB_FRIENDLY_PROMPT — the display labels shown to users when capturing the parameter, including the web (OIE) variant.
• LINE_TYPE_LOOKUP_CODE — indicates the line type context for the parameter.
• VAT_CODE — tax code applied to the parameter line.
• FLEX_CCID, FLEX_DESCRIPTION, FLEX_CONCACTENATED — accounting flexfield reference, description, and concatenated display used for default accounting.
• SUMMARY_FLAG, WEB_ENABLED_FLAG, WEB_SEQUENCE, WEB_IMAGE_FILENAME — control whether and how the parameter appears in the web expense UI.
• JUSTIFICATION_REQUIRED_FLAG, RECEIPT_REQUIRED_FLAG, REQUIRE_RECEIPT_AMOUNT, ITEMIZATION_REQUIRED_FLAG, ITEMIZATION_ALL_FLAG — validation and receipt itemization rules.
• AMOUNT_INCLUDES_TAX_FLAG, CALCULATE_AMOUNT_FLAG — tax and amount calculation behavior.
• PA_EXPENDITURE_TYPE, CARD_EXP_TYPE_LOOKUP_CODE — integration mappings for Projects expenditure types and corporate card expense types.
• COMPANY_POLICY_ID, CATEGORY_CODE, DATA_CAPTURE_RULE_ID — policy, category, and data capture rule references.
• ORG_ID plus audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and END_DATE — multi-org key, audit trail, and effective end dating.

Common Use Cases and Queries

This view is typically queried to audit or report expense template configuration, to drive personalizations, or to troubleshoot expense entry behavior.

Retrieve all parameters for a specific expense report definition:

SELECT parameter_id, prompt, expense_type_code,
       receipt_required_flag, web_enabled_flag
FROM   apps.apbv_expense_report_params
WHERE  expense_report_id = :p_expense_report_id
ORDER  BY web_sequence;

List parameters tied to a particular expense type code — the searched term:

SELECT expense_report_id, parameter_id, prompt,
       justification_required_flag, amount_includes_tax_flag
FROM   apps.apbv_expense_report_params
WHERE  expense_type_code = :p_expense_type_code;

Identify parameters requiring receipts for a given org:

SELECT erp.expense_report_id, erp.prompt, erp.require_receipt_amount
FROM   apps.apbv_expense_report_params erp
WHERE  erp.receipt_required_flag = 'Y'
AND    erp.org_id = :p_org_id;

Because the view enforces organization security and is read-only, it is safe for reporting and query-only integrations, while configuration changes must be made through the native Payables/OIE setup screens rather than through this view.