Search Results margin_percentage




Overview

APPS.PA_FCST_PROJ_SHOW_AMT_V is a lightweight security and presentation view in Oracle EBS Project Accounting (Oracle Projects) that governs which forecast amount types a user is permitted to see for the project currently held in context. Rather than storing any forecast figures itself, the view filters rows from the PA_LOOKUPS repository for the lookup type PA_FORECAST_AMOUNT_TYPE and returns only those amount-type lookup codes that pass a set of authorization rules. The rules are evaluated dynamically by two package calls: PA_FCST_GLOBAL, which supplies the project's type class and project identifier, and PA_SECURITY.VIEW_LABOR_COSTS, which determines whether the current user may view labor cost information for that project.

The view is significant because the string 'MARGIN_PERCENTAGE' appears explicitly within its decode logic. This makes the view the mechanism by which margin percentage amounts are exposed or suppressed in forecast entry and inquiry windows. It is therefore central to any requirement involving forecast profitability display, and it is frequently referenced when users search for "margin_percentage" in the context of Oracle Projects forecasting.

Underlying Base Objects

The documented base objects referenced by the view are PA_LOOKUPS (a view over the lookup repository), PA_FCST_GLOBAL (a package), and PA_SECURITY (a package).

  • PA_LOOKUPS — Supplies the LOOKUP_CODE and MEANING pairs restricted to LOOKUP_TYPE = 'PA_FORECAST_AMOUNT_TYPE'. Typical codes in this lookup type include COST, REVENUE, MARGIN, and MARGIN_PERCENTAGE.
  • PA_FCST_GLOBAL — Provides session-level context through GetProjectTypeClass and GetProjectId. GetProjectTypeClass returns values such as 'CONTRACT', which selects the branch of the decode logic applied.
  • PA_SECURITY — Provides VIEW_LABOR_COSTS(project_id), returning 'Y' or 'N' to indicate whether the current user is privileged to see labor cost amounts on the project in context.

No project transaction tables are joined; the view is purely a filtered lookup list, which is why it is inexpensive to query and safe to embed in list-of-values and form-level validations.

Key Columns

  • LOOKUP_CODE — The forecast amount type identifier (for example COST, REVENUE, MARGIN, MARGIN_PERCENTAGE). This is the value consumed by forecasting screens and concurrent processes.
  • MEANING — The user-facing description of the amount type, used for display in lists of values and report parameters.

The view exposes only these two columns. The filtering predicate is applied in the WHERE clause by comparing the decode result to LOOKUP_CODE, so a row is returned only when the computed value equals its own lookup code. Effectively, the decode acts as a per-row visibility switch.

Common Use Cases and Queries

The principal uses are restricting forecast amount type lists of values, controlling whether margin and margin percentage rows appear in forecast inquiry, and diagnosing why a user cannot see margin-related forecast amounts. Because the view depends on PA_FCST_GLOBAL session state, it must be queried after the project context has been initialized; calling it without context typically yields the non-contract, no-labor-cost behavior.

  • List all visible amount types for the project in context: SELECT lookup_code, meaning FROM apps.pa_fcst_proj_show_amt_v ORDER BY lookup_code;
  • Check specifically whether margin percentage is exposed: SELECT lookup_code, meaning FROM apps.pa_fcst_proj_show_amt_v WHERE lookup_code = 'MARGIN_PERCENTAGE';
  • Join the view to reporting logic to display only authorized amount types: SELECT t.amount_type, v.meaning FROM pa_forecast_totals t, apps.pa_fcst_proj_show_amt_v v WHERE t.amount_type = v.lookup_code;

Note the security consequence embedded in the decode: for contract projects where labor costs are not viewable, COST is suppressed; for projects where labor costs are viewable, REVENUE, MARGIN, and MARGIN_PERCENTAGE are suppressed, leaving cost amounts visible. Any customization or report that expects margin percentage rows must account for this project-class and security-dependent filtering.