Search Results g_order_lead

Overview

IBE_LEAD_IMPORT_PVT is the private implementation package body for the Oracle iStore / Oracle Sales lead import functionality in Oracle E-Business Suite. It serves as the engine behind the Sales Lead Import process, which allows organizations to bring external lead data into the CRM and Order Management data model. The package parses inbound lead records staged in the AS_IMPORT_INTERFACE and AS_IMP_LINES_INTERFACE interface tables, validates them, and creates corresponding sales leads, notes, and sales team assignments through the AS_SALES_LEADS_PUB public API. It also supports the creation of leads directly from Oracle Quoting (ASO_QUOTE_LINES_ALL, ASO_QUOTE_HEADERS_ALL) and Order Management (OE_ORDER_HEADERS) records, extending the import process to source leads from existing quote and order activity.

Because the object is classified as a PVT (private) package, it is not intended for direct customer invocation. Instead, it is called by other packages and concurrent program drivers that orchestrate the overall lead import run.

Key Procedures and Functions

The 22 documented procedures and functions fall into several functional groups:

• Logging and diagnostics: WRITE_LOG, UPDATE_LOG, and INSERT_LOG_DETAILS write processing diagnostics to the IBE_LEAD_IMPORT_LOG table, enabling traceability of import runs.
• Parsing and selection: PARSEINPUT interprets import parameters; GET_QUOTES_RECORDS, GET_QUOTE_LINE_RECORDS, GET_ORDER_RECORDS, and GET_ORDER_LINE_RECORDS retrieve source quote and order data; GET_DATE_PERIOD handles date range derivation.
• Lead creation: CREATE_ORDER_LEADS and CREATE_QUOTE_LEADS build leads from order and quote sources respectively; CREATE_SALES_LEAD and CREATE_LEADANDNOTES insert the lead header and associated notes.
• Team and ranking: RANK_SALES_LEAD, CREATE_SALES_TEAM, and BUILD_SALES_TEAM handle lead ranking and sales team population.
• Orchestration: IMPORT_QUOTE_LEAD, IMPORT_ORDER_LEAD, and PROCESS_SALES_LEAD_IMPORT drive the overall import workflow. PRINT_PARAMETER renders parameter output.

Tables Accessed

The package reads and writes several interface and application tables through APPS synonyms:

• Interface tables: AS_IMPORT_INTERFACE and AS_IMP_LINES_INTERFACE (with their _S sequence views) hold staged inbound lead data that the package consumes and validates.
• Staging and log tables: IBE_LEAD_IMPORT_DETAILS, IBE_LEAD_IMPORT_DETAILS_S1, and IBE_LEAD_IMPORT_LOG persist processed records and diagnostics.
• Source data: ASO_QUOTE_HEADERS_ALL, ASO_QUOTE_LINES_ALL, and OE_ORDER_HEADERS supply quote and order records from which leads are generated.
• Reference and party data: AMS_SOURCE_CODES, HZ_PARTIES, HZ_PARTY_SITES, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, and MTL_SYSTEM_ITEMS_KFV supply lookup, party, and item information.

Usage Notes

IBE_LEAD_IMPORT_PVT is invoked indirectly, primarily by the Sales Lead Import concurrent program and by related iStore / Quoting processes. It is referenced by two other database objects, confirming its role as a supporting implementation layer rather than an entry point. The package depends heavily on FND_API, FND_MSG_PUB, FND_PROFILE, FND_FILE, and FND_GLOBAL for the standard Oracle EBS API framework, concurrency, and value-set/profile services. Because it is a validated private package in the APPS schema and is not referenced by any application-tier form or public API directly, customizations should call the public wrapper AS_SALES_LEADS_PUB rather than this body. Its behavior is consistent across Oracle EBS 12.1.1 and 12.2.2.