Results for “pv_process_type”

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

Overview

APPS.AML_LEAD_PROCESS_REPT_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, residing in the APPS schema. It consolidates lead processing information from Oracle's Trade Management and Marketing (ETRM) modules, providing a denormalized, query-friendly presentation of sales lead processing outcomes. The view joins lead master records, rule-evaluation results, lookup meanings, territory and address data, and processing-stage definitions into a single dataset. It is intended primarily for reporting and integration purposes, enabling users to analyze how processing rules were applied to individual sales leads, which rules won, and what the resulting rank, stage, and status were.

Underlying Base Objects

The view is defined over several documented base objects. The central fact source is PV_ENTITY_RULES_APPLIED, joined to AS_SALES_LEADS on ENTITY_ID = SALES_LEAD_ID where ENTITY = 'SALES_LEAD'. Rule definitions are supplied by two aliases of PV_PROCESS_RULES_VL — PARENT (domain/precedence) and CHILD (sub-rule) — outer-joined via PARENT_PROCESS_RULE_ID and PROCESS_RULE_ID. Lookup meanings derive from FND_LOOKUP_VALUES_VL (aliased LK1 and LK2) and AS_STATUSES_VL. Address and territory enrichment comes from an inline subquery over HZ_PARTY_SITES, HZ_LOCATIONS, and FND_TERRITORIES_VL. Stage and rank metadata are drawn from AML_LEAD_PROCESSING_STAGES_V, used twice (STAGES and RANK).

Key Columns

• SALES_LEAD_ID / LEAD_NUMBER / LEAD_NAME — the lead identifier, number, and description.
• ENTITY_RULE_APPLIED_ID — identifier of the specific rule application record.
• PROCESS_RULE_ID / RULE_ID / DOMAIN / SUB_RULE / PRECEDENCE — the applied rule hierarchy.
• EVAL_CODE / PROCESS_STATUS_CODE / PROCESS_STATUS / WINNING_RULE_FLAG / LATEST_FLAG — evaluation outcome and status details.
• STAGE / RULE_CODE / RESULT — lookup-derived meanings for the process stage and result.
• STATUS / STATUS_CODE — lead status from AS_STATUSES_VL.
• COUNTRY / COUNTRY_CODE / TERRITORY_SHORT_NAME — geographic attributes.
• LEAD_RANK / LEAD_RANK_ID / LEAD_RANK_IND / ACCEPT_FLAG — ranking and acceptance indicators.
• EVALUATION_DATE / CREATION_DATE / CURRENCY_CODE / CHANNEL_CODE — auditing and classification attributes.

The user's search term pv_process_type maps directly to the join condition APP.PROCESS_TYPE = LK1.LOOKUP_CODE AND LK1.LOOKUP_TYPE = 'PV_PROCESS_TYPE', which drives the value shown in the view's STAGE and RULE_CODE columns.

Common Use Cases and Queries

Typical use cases include analyzing which rules won for a lead, auditing rule evaluation history, and reporting lead movement across processing stages. A representative query filters winning evaluations by process type:

• Report all leads where a specific PV_PROCESS_TYPE rule was applied.
• List the latest evaluation per lead using LATEST_FLAG = 'Y'.
• Summarize winning rules by territory or country.

Sample SQL:

SELECT lead_number, lead_name, stage, process_status, domain, sub_rule, evaluation_date
FROM apps.aml_lead_process_rept_v
WHERE winning_rule_flag = 'Y'
AND stage = 'LEAD_RANKING'
ORDER BY evaluation_date DESC;

A second query filters by process_status to review rule-application outcomes for a given lead number, joining to AS_SALES_LEADS only through the view itself. Because the view is fully resolved in the APPS schema, report logic should reference it with the APPS prefix and respect standard EBS security and MOAC considerations.