Search Results customer_group_code

Overview

The APPS.AS_IMP_SL_V view resides in the Sales Foundation (AS) product family of Oracle E-Business Suite and is classified in the ETRM repository as Obsolete. It is a database view owned by the APPS schema with a VALID status in both 12.1.1 and 12.2.2 environments where the object has not been removed by patching. The name follows the AS_IMP_* convention used for Sales Foundation import interface constructs, where "IMP" denotes import and "SL" refers to the sales lead domain. The view therefore exposes a flattened, query-friendly projection of columns relevant to the import and update of sales lead, customer, contact, and address information staged through the AS_IMPORT_INTERFACE table.

Because the description is documented simply as Obsolete, the view should be treated as a legacy artifact. It is retained for backward compatibility and is not recommended as a foundation for new development in 12.1.1 or 12.2.2. Understanding its column inventory remains useful for maintenance, impact analysis during upgrades, and for diagnosing customizations that still reference it.

Underlying Base Objects

ETRM documents a single referenced base object for AS_IMP_SL_V: the synonym AS_IMPORT_INTERFACE, which resolves to the APPS.AS_IMPORT_INTERFACE table. The view text is a straight column projection over that interface table, with ROWID included as the leading expression and no joins, unions, or aggregations visible in the documented excerpt. This structure indicates the view acts as a column-filtered window onto the import interface rather than a denormalized reporting construct. All DML that flows into the interface table through the import process is immediately visible through the view, and inserts performed directly against the view propagate to the base table.

Key Columns

The column list is extensive and spans several functional groupings:

• Import control columns — BATCH_ID, IMPORT_INTERFACE_ID, IMP_LIST_HEADER_NUMBER, LOAD_DATE, LOAD_STATUS, LOAD_TYPE, LOAD_ERROR_MESSAGE. These track the state of each staged record through the import lifecycle.
• Entity resolution flags — NEW_CON_FLAG, NEW_LOC_FLAG, NEW_PARTY_FLAG, NEW_PS_FLAG, NEW_REL_FLAG. The searched term new_loc_flag is exposed here as NEW_LOC_FLAG, indicating whether the address or location referenced by the record represents a new location that must be created during import.
• Customer and party identifiers — CUSTOMER_ID, CUSTOMER_KEY, CUSTOMER_NUMBER, PARTY_ID, PARTY_SITE_ID, PARTY_TYPE, CONTACT_PARTY_ID, ORIG_SYSTEM_CODE, ORIG_SYSTEM_REFERENCE.
• Address attributes — ADDRESS1 through ADDRESS4, ADDRESS_ID, ADDRESS_KEY, ADDRESS_STATUS, CITY, STATE-like locality columns, COUNTRY, COUNTY.
• Contact and communication attributes — FIRST_NAME, LAST_NAME, MIDDLE_INITIAL, JOB_TITLE, EMAIL_ADDRESS, FAX_NUMBER, AREA_CODE, EXTENSION, and the DO_NOT_* preference flags.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on inspecting staged import rows and validating the new-location decision prior to submission of the import concurrent program.

• Identifying records flagged as new locations: SELECT import_interface_id, batch_id, new_loc_flag, address_id, address1 FROM apps.as_imp_sl_v WHERE new_loc_flag = 'Y';
• Reviewing failed or pending rows: SELECT batch_id, load_status, load_error_message FROM apps.as_imp_sl_v WHERE load_status <> 'COMPLETE';
• Auditing party and customer resolution: SELECT customer_number, party_id, party_site_id, new_party_flag FROM apps.as_imp_sl_v WHERE batch_id = :batch_id;

Because the object is documented as Obsolete, any new integration should reference the AS_IMPORT_INTERFACE table directly or use supported TCA and Sales Foundation APIs instead.