ProductCatalogOutputConfig Component Does Not Send All SKUs to the Indexer On SKU-Based Indexing When Using CustomCatalogVariantProducer

(Doc ID 1580245.1)

Last updated on DECEMBER 22, 2016

Applies to:

Oracle ATG Web Commerce - Version 9.4 and later
Information in this document applies to any platform.


The ProductCatalogOutputConfig sends an unexpected number of records for indexing.
When you add different variants you see more SKUs but different total numbers indexed each time.
You are doing SKU-based indexing.
The defect is in the variant producer logic so it is common to both ATG Search and Endeca Search implementations.



You started using multiple Variant Producers, one of which is (the default) /atg/commerce/search/CustomCatalogVariantProducer.

For more details on CustomCatalogVariantProducer component see the following documents depending on what products you use.

ATG-Endeca Integration Guide > Customizing the Output Records > Using Variant Producers > CustomCatalogVariantProducer.

ATG Search Administration Guide > Indexing Commerce Catalog Data > Indexing the Product Catalog Repository > Indexing a Catalog Repository with Multiple Catalog Items.

All the versions of ATG documents are found here.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms