Search Results bom_enabled_flag

Overview

AMS_PRODUCT_MAPPING_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS (Marketing) product family. Its documented purpose is to serve as a "Product view for import," exposing marketing product records that have been staged for import processing through the AMS import framework. In both EBS 12.1.1 and 12.2.2 the object carries a VALID status and is defined entirely as a view — no physical storage of its own — so it functions as a read-only projection over the underlying import staging and header tables. Because the view normalizes the generic, positionally named columns of the import staging table (COL1, COL2, COL3, and so on) into meaningful business attribute names, it is the preferred access point for reporting on stage-to-production product imports, validating load outcomes, and diagnosing import failures. The view is particularly relevant to implementers who need to confirm how marketing product attributes map into inventory item attributes during an AMS product load.

Underlying Base Objects

The documented base objects referenced by the view are AMS_IMP_LIST_HEADERS_ALL (exposed through a synonym) and AMS_IMP_SOURCE_LINES (exposed through a synonym). AMS_IMP_LIST_HEADERS_ALL holds the import list header that groups a set of staged source lines, while AMS_IMP_SOURCE_LINES stores the individual import records, including the generic COL1..COLn attribute buckets produced by the import column mapping setup. The view joins the line rows to the list header and aliases the significant COL columns into descriptive names, so that a single row represents one staged marketing product together with its import-processing metadata.

Key Columns

The view exposes two categories of columns: import-control attributes and mapped product attributes.

• Import-control columns — IMPORT_SOURCE_LINE_ID, IMPORT_LIST_HEADER_ID, IMPORT_SUCCESSFUL_FLAG, LOAD_STATUS, OBJECT_VERSION_NUMBER, plus the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). These describe which list and line the record belongs to and whether the load succeeded.
• Mapped product columns — the COLn buckets are aliased to business names, including ORGANIZATION_NAME, ITEM_NUMBER, DESCRIPTION, LONG_DESCRIPTION, ITEM_TYPE, PRIMARY_UOM_CODE, INVENTORY_ITEM_STATUS_CODE, INVENTORY_ITEM_FLAG, STOCK_ENABLED_FLAG, and MTL_TRANSACTIONS_ENABLED_FLAG.
• Order and service flags — CUSTOMER_ORDER_FLAG (COL15) is the flag indicating whether the staged product is intended to be customer-orderable; it is paired with CUSTOMER_ORDER_ENABLED_FLAG (COL16). Related columns include INTERNAL_ORDER_FLAG, INTERNAL_ORDER_ENABLED_FLAG, SHIPPABLE_ITEM_FLAG, RETURNABLE_FLAG, INVOICEABLE_ITEM_FLAG, SERVICE_ITEM_FLAG, SERVICEABLE_PRODUCT_FLAG, and ORDERABLE_ON_WEB_FLAG.
• Pricing and media columns — PRICE_LIST_NAME, LIST_PRICE, PRODUCT_UOM_CODE, CATEGORY_CODE, MEDIA_OBJECT, and related template/access columns.

Common Use Cases and Queries

Typical usage centers on validating import results and auditing the customer-orderable attribute requested by the user's search term.

• Review successful versus failed product imports for a given list header.
• Report which staged products carry CUSTOMER_ORDER_FLAG set, to confirm orderability intent before the record is promoted to an inventory item.
• Reconcile source line generic columns against the mapped attribute names to verify column mapping configuration.

Representative query:

SELECT import_list_header_id,
       item_number,
       organization_name,
       customer_order_flag,
       customer_order_enabled_flag,
       inventory_item_flag,
       load_status,
       import_successful_flag
FROM   apps.ams_product_mapping_v
WHERE  import_list_header_id = :p_list_header_id
AND    customer_order_flag = 'Y'
ORDER BY import_source_line_id;

A second pattern filters only unsuccessful rows to troubleshoot rejected imports:

SELECT import_source_line_id, item_number, load_status
FROM   apps.ams_product_mapping_v
WHERE  import_successful_flag = 'N';

Because the view is read-only and derives from staging data, it should not be used as a DML target; inserts and updates must be performed against the underlying AMS_IMP_SOURCE_LINES and AMS_IMP_LIST_HEADERS_ALL structures through the supported AMS import APIs.