Search Results new_party_flag
Overview
APPS.AS_IMP_SL_V is a reporting and integration view in Oracle E-Business Suite (documented for 12.2.2, applicable to 12.1.1) used by the Sales Lead / Sales List import process within the Oracle Sales (AS) module. It exposes the staging contents of the sales lead import interface, presenting a flattened, query-ready projection of imported lead and contact data. The view is typically consumed to inspect, validate, or report on records that are pending or have completed import into the sales lead tables. Because the view exposes the NEW_PARTY_FLAG column — the term the user searched on — it is the recommended object for identifying whether an imported sales lead record references a newly created party versus an existing party already registered in the Trading Community Architecture (TCA) model. It is an APPS-owned view, meaning it is referenced through the standard APPS schema synonym layer used across EBS reporting, Discoverer workbooks, and custom concurrent programs.
Underlying Base Objects
Per the documented view metadata, AS_IMP_SL_V is defined over a single referenced base object: AS_IMPORT_INTERFACE (referenced through a synonym). AS_IMPORT_INTERFACE is the interface (staging) table populated by the sales lead import program before validation and transfer into the production lead, contact, and party tables. The view does not introduce additional joins documented in the metadata; it presents a selecting projection over that interface table, alongside ROWID for record identification. Consequently, the view is a filtered/projected representation of the staging rows rather than a consolidated multi-table join. This makes it a low-overhead access path for reviewing interface data before or after the import concurrent program executes.
Key Columns
The view exposes a broad set of columns spanning lead, contact, party, address, phone, and import-control attributes. Notable columns include:
- NEW_PARTY_FLAG — Indicates that the imported record will create (or has created) a new party in TCA; central to the user's search and to determining import behavior.
- NEW_CON_FLAG, NEW_LOC_FLAG, NEW_PS_FLAG, NEW_REL_FLAG — Companion flags indicating, respectively, new contact, new location, new party site, and new relationship creation during import.
- PARTY_ID, PARTY_SITE_ID, CONTACT_PARTY_ID, CUSTOMER_ID, LOCATION_ID — Surrogate keys to the TCA and customer entities the lead is associated with.
- IMPORT_INTERFACE_ID, BATCH_ID, IMP_LIST_HEADER_NUMBER, LOAD_DATE, LOAD_STATUS, LOAD_TYPE, LOAD_ERROR_MESSAGE — Import-control columns tracking the batch, load state, and validation outcome.
- ADDRESS_KEY, CONTACT_KEY, CUSTOMER_KEY, ORIG_SYSTEM_CODE, ORIG_SYSTEM_REFERENCE — Source-system and deduplication identifiers.
- Customer/lead category columns such as CUSTOMER_CATEGORY_CODE, CUSTOMER_CLASS_CODE, CUSTOMER_TYPE, LEAD_RANK_CODE, LEAD_NUMBER, CHANNEL_CODE, and the INTEREST_TYPE_ID_n / INVENTORY_ITEM_ID_n / ORGANIZATION_ID_n flex column sets.
- Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
Common Use Cases and Queries
Typical uses include verifying which staged leads will create new parties, diagnosing import errors, and reconciling batch loads. The NEW_PARTY_FLAG is frequently used to segment records for follow-up processing.
- Identify records flagged for new party creation:
SELECT IMPORT_INTERFACE_ID, LEAD_NUMBER, NEW_PARTY_FLAG, LOAD_STATUS
FROM APPS.AS_IMP_SL_V
WHERE NEW_PARTY_FLAG = 'Y'; - Review failed or unprocessed interface rows within a batch:
SELECT BATCH_ID, LEAD_NUMBER, LOAD_STATUS, LOAD_ERROR_MESSAGE
FROM APPS.AS_IMP_SL_V
WHERE LOAD_STATUS = 'ERROR'; - Summarize new-entity creation across a load:
SELECT NEW_PARTY_FLAG, NEW_CON_FLAG, COUNT(*)
FROM APPS.AS_IMP_SL_V
GROUP BY NEW_PARTY_FLAG, NEW_CON_FLAG;
Because the view is a projection over AS_IMPORT_INTERFACE, queries return staging data and reflect the current state of the interface table at query time, making it suitable for both pre-import validation and post-import auditing in 12.1.1 and 12.2.2 environments.
-
VIEW: APPS.AS_IMP_SL_V
12.2.2
-
View: AS_IMP_SL_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AS.AS_IMP_SL_V, object_name:AS_IMP_SL_V, status:VALID, product: AS - Sales Foundation , description: Obsolete , implementation_dba_data: APPS.AS_IMP_SL_V ,
-
View: AS_IMP_SL_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AS.AS_IMP_SL_V, object_name:AS_IMP_SL_V, status:VALID, product: AS - Sales Foundation , description: Obsolete , implementation_dba_data: APPS.AS_IMP_SL_V ,
-
VIEW: APPS.AS_IMP_SL_V
12.1.1
-
VIEW: AR.HZ_SRCH_PSITES#
12.2.2
-
VIEW: AR.HZ_SRCH_CONTACTS#
12.2.2
-
VIEW: AR.HZ_SRCH_CPTS#
12.2.2
-
VIEW: OSM.AS_IMPORT_INTERFACE#
12.2.2
-
VIEW: APPS.AS_IMP_SL_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AS.AS_IMP_SL_V, object_name:AS_IMP_SL_V, status:VALID,
-
VIEW: APPS.AS_IMP_SL_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AS.AS_IMP_SL_V, object_name:AS_IMP_SL_V, status:VALID,
-
VIEW: AR.HZ_SRCH_CONTACTS#
12.2.2
owner:AR, object_type:VIEW, object_name:HZ_SRCH_CONTACTS#, status:VALID,
-
APPS.AS_IMPORT_SL_PVT SQL Statements
12.2.2
-
VIEW: AR.HZ_SRCH_CPTS#
12.2.2
owner:AR, object_type:VIEW, object_name:HZ_SRCH_CPTS#, status:VALID,
-
VIEW: AR.HZ_SRCH_PSITES#
12.2.2
owner:AR, object_type:VIEW, object_name:HZ_SRCH_PSITES#, status:VALID,
-
APPS.HZ_IMP_MATCH_RULE_50 SQL Statements
12.2.2
-
APPS.HZ_IMP_MATCH_RULE_50 SQL Statements
12.1.1
-
APPS.AS_IMPORT_SL_PVT SQL Statements
12.1.1
-
VIEW: OSM.AS_IMPORT_INTERFACE#
12.2.2
owner:OSM, object_type:VIEW, object_name:AS_IMPORT_INTERFACE#, status:VALID,
-
APPS.HZ_IMP_MATCH_RULE_52 SQL Statements
12.2.2
-
APPS.HZ_IMP_MATCH_RULE_51 SQL Statements
12.1.1
-
APPS.HZ_IMP_MATCH_RULE_51 SQL Statements
12.2.2
-
APPS.HZ_IMP_MATCH_RULE_52 SQL Statements
12.1.1
-
View: AMS_LEAD_MAPPING_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AMS.AMS_LEAD_MAPPING_V, object_name:AMS_LEAD_MAPPING_V, status:VALID, product: AMS - Marketing , description: This view stores the mapping of ams_imp_source_lines table. This is used to populate the data from the data file. , implementation_dba_data: APPS.AMS_LEAD_MAPPING_V ,
-
View: AMS_LEAD_MAPPING_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AMS.AMS_LEAD_MAPPING_V, object_name:AMS_LEAD_MAPPING_V, status:VALID, product: AMS - Marketing , description: This view stores the mapping of ams_imp_source_lines table. This is used to populate the data from the data file. , implementation_dba_data: APPS.AMS_LEAD_MAPPING_V ,
-
VIEW: APPS.AMS_LEAD_MAPPING_V
12.2.2
-
VIEW: APPS.AMS_LEAD_MAPPING_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AMS.AMS_LEAD_MAPPING_V, object_name:AMS_LEAD_MAPPING_V, status:VALID,
-
VIEW: APPS.AMS_LEAD_MAPPING_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AMS.AMS_LEAD_MAPPING_V, object_name:AMS_LEAD_MAPPING_V, status:VALID,
-
VIEW: APPS.AMS_LEAD_MAPPING_V
12.1.1
-
PACKAGE BODY: APPS.HZ_IMP_MATCH_RULE_52
12.1.1
-
PACKAGE BODY: APPS.HZ_IMP_MATCH_RULE_50
12.1.1
-
TABLE: OSM.AS_IMPORT_INTERFACE
12.2.2
owner:OSM, object_type:TABLE, fnd_design_data:AS.AS_IMPORT_INTERFACE, object_name:AS_IMPORT_INTERFACE, status:VALID,
-
TABLE: OSM.AS_IMPORT_INTERFACE
12.1.1
owner:OSM, object_type:TABLE, fnd_design_data:AS.AS_IMPORT_INTERFACE, object_name:AS_IMPORT_INTERFACE, status:VALID,
-
APPS.AMS_IMPORTCLIENT_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.HZ_IMP_MATCH_RULE_52
12.2.2
-
PACKAGE BODY: APPS.HZ_IMP_MATCH_RULE_50
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.HZ_IMP_MATCH_RULE_51
12.1.1
-
PACKAGE BODY: APPS.HZ_IMP_MATCH_RULE_51
12.2.2
-
APPS.HZ_MATCH_RULE_50 SQL Statements
12.2.2
-
APPS.HZ_MATCH_RULE_50 SQL Statements
12.1.1
-
APPS.HZ_MATCH_RULE_52 SQL Statements
12.1.1
-
APPS.HZ_MATCH_RULE_52 SQL Statements
12.2.2
-
TABLE: AR.HZ_SRCH_PSITES
12.1.1
owner:AR, object_type:TABLE, fnd_design_data:AR.HZ_SRCH_PSITES, object_name:HZ_SRCH_PSITES, status:VALID,
-
TABLE: AR.HZ_SRCH_CPTS
12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.HZ_SRCH_CPTS, object_name:HZ_SRCH_CPTS, status:VALID,
-
APPS.HZ_MATCH_RULE_51 SQL Statements
12.2.2
-
TABLE: AR.HZ_SRCH_CPTS
12.1.1
owner:AR, object_type:TABLE, fnd_design_data:AR.HZ_SRCH_CPTS, object_name:HZ_SRCH_CPTS, status:VALID,
-
APPS.HZ_MATCH_RULE_51 SQL Statements
12.1.1
-
TABLE: AR.HZ_SRCH_CONTACTS
12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.HZ_SRCH_CONTACTS, object_name:HZ_SRCH_CONTACTS, status:VALID,
-
TABLE: AR.HZ_SRCH_CONTACTS
12.1.1
owner:AR, object_type:TABLE, fnd_design_data:AR.HZ_SRCH_CONTACTS, object_name:HZ_SRCH_CONTACTS, status:VALID,
-
TABLE: AR.HZ_SRCH_PSITES
12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.HZ_SRCH_PSITES, object_name:HZ_SRCH_PSITES, status:VALID,