Results for “as_lookups4”

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

Overview

APPS.AST_SALES_LEADS_REL_BALI_V is a reporting and integration view in the Oracle EBS Applications Technology and Customer Relationship Management schema. It consolidates sales lead records from the Oracle Trade Management / Sales Leads module (formerly iStore and Sales Offline, referenced by the AST prefix) and decorates them with the lookup meanings required to render human-readable values in user interfaces, concurrent program outputs, and outbound integrations. The view is defined over AS_SALES_LEADS as its driving table, joined to status, rank, contact, and lookup entities, so that coded columns such as STATUS_CODE, CHANNEL_CODE, and BUDGET_STATUS_CODE are exposed alongside their translated meanings.

The name suffix REL_BALI_V indicates a relationship-style view used for lead-to-contact association reporting. It is not a base data-entry view; it is intended for read-only query, extraction, and downstream integration, particularly where lead scoring, qualification, and contact linkage must be reported together.

Underlying Base Objects

The view draws on eight referenced objects:

• AS_SALES_LEADS (SYNONYM) — the driving table, aliased LEAD, supplying lead identity, status, owner assignment, budget, score, and descriptive-flex columns.
• AS_SALES_LEAD_CONTACTS (SYNONYM) — aliased ASLC, providing the associated CONTACT_PARTY_ID for each lead.
• AS_STATUSES_VL (VIEW) — aliased STATUS, supplying MEANING for STATUS_CODE.
• AS_SALES_LEAD_RANKS_TL (SYNONYM) — aliased RANK, an outer-joined, language-aware translation table returning RANK.MEANING filtered by USERENV('LANG').
• AS_LOOKUPS (VIEW) — referenced four times as AS_LOOKUPS2 through AS_LOOKUPS5, resolving budget status, decision timeframe, close reason, and vehicle response code respectively.
• OE_LOOKUPS (VIEW) — aliased OELKP, resolving CHANNEL_CODE into OELKP.MEANING.

Lookup joins use the (+) outer-join operator, so leads with unmapped codes are still returned. Only STATUS_CODE is enforced as an inner join through AS_STATUSES_VL.

Key Columns

• Identity and audit: ROWID, SALES_LEAD_ID, LEAD_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and the REQUEST_ID/PROGRAM_ID concurrent-request columns.
• Status and qualification: STATUS_CODE with MEANING, STATUS_OPEN_FLAG, QUALIFIED_FLAG, ACCEPT_FLAG, KEEP_FLAG, URGENT_FLAG, DELETED_FLAG.
• Assignment: ASSIGN_TO_PERSON_ID, ASSIGN_TO_SALESFORCE_ID, ASSIGN_SALES_GROUP_ID, ASSIGN_DATE, AUTO_ASSIGNMENT_TYPE.
• Scoring: TOTAL_SCORE and SCORECARD_ID, with LEAD_RANK_ID and LEAD_RANK_CODE resolved to RANK.MEANING.
• Descriptive flexfields: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.
• The AS_LOOKUPS5 mapping: the user search term as_lookups5 corresponds to the alias resolving VEHICLE_RESPONSE_CODE into its meaning, returned as an unnamed lookup column. The companion aliases resolve BUDGET_STATUS_CODE (as BUDGET_STATUS), DECISION_TIMEFRAME_CODE, and CLOSE_REASON.

Common Use Cases and Queries

Typical scenarios include lead pipeline reporting by status and rank, contact-level lead association extracts, and integration feeds requiring decoded lookup values rather than raw codes. A representative query returning scored leads with decoded status, channel, and vehicle response:

• SELECT lead_number, sales_lead_id, contact_party_id, meaning, channel_meaning, total_score
• FROM apps.ast_sales_leads_rel_bali_v
• WHERE status_open_flag = 'Y' AND total_score IS NOT NULL
• ORDER BY total_score DESC;

For auditing assignment activity, filter on ASSIGN_DATE and ASSIGN_TO_PERSON_ID. Because the view contains a ROWID column and outer joins, it is suitable for read-oriented ETL; direct DML against it is not supported.