Kontakt

Ansicht
Dokumentation

Product Catalog Staging (New) ( RELNCRM_52_MD_PCT )

Product Catalog Staging (New) ( RELNCRM_52_MD_PCT )

General Material Data   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Product Catalog Staging (New)

Use

This release note is only relevant if upgrading from SAP CRM 5.0.

Catalog staging has been introduced in the product catalog of the B2B and B2C Web shop. Catalog staging means the process of creating, validating, and activating a product catalog for productive use. According to this process, you can verify if a product catalog is correct, before it is released for general access.

Prior to this release, usually one version of a catalog variant was available on the TREX server. In this context, catalog variant version is used as an equivalent for a set of TREX indexes, that means, A-index for Area, P-index for Products, and S-index for additional information. When the indexing of a catalog variant was started, existing indexes were overwritten by delta indexing or deleted by initial indexing.

As of this release, a versioning of catalog variants including indexes is available. That means that indexing no longer touches existing indexes. Instead, a new version of a catalog variant creates a new set of indexes. As a result, there is no longer any downtime of the productive Web shop while the indexing process is running. Versioning allows the use of the master/slave principle on the TREX server, which makes the product catalog permanently up-to-date and available in the Web shop.

For more information about the new programming interface, see release note Programming Interface SAP TREX API (New).

Catalog Variant Versioning

To manage catalog variant versions and make them available in the productive Web shop, the following four version states have been introduced:

  • The active status can be applied to exactly one version of a catalog variant
The active status is to be applied to a catalog variant version to be used by standard users in the productive Web shop.
  • The inactive status can be applied to several versions of a catalog variant
A new catalog variant version is always inactive. It is used by internal users (external users have no access) to check completeness and correctness before the catalog variant is released. Therefore, the inactive variant version already looks the same as it does after it has been activated and made available for customers. This also means that current and future Internet Pricing and Configurator (IPC) information is already available.
After the version has been checked, it can be activated. That means that the status of the existing active version of the same catalog variant automatically changes to obsolete.
For users of the productive Web shop, activation has two effects:
  • Users who start the product catalog after the inactive catalog variant version has been activated directly access the new catalog variant version.

  • Users who have already started the product catalog before the inactive catalog variant version has been activated stay connected to the obsolete version. This guarantees consistent catalog browsing with no Web shop downtime.

  • The obsolete status can be applied to several versions of a catalog variant
Obsolete catalog variant versions are former active catalog variant versions that enable consistent catalog browsing. These catalog variant versions can be removed manually from the TREX server. Removal can also be performed automatically by a batch program after a predefined period of time.
  • The erroneous status is only applied if errors occur during indexing

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

  • You define the product catalog indexing in Customizing at Customer Relationship Management -> Master Data -> Product Catalog -> Define Catalog Variant Indexing.
  • You define the RFC destinations for the initial- or delta indexing of the product catalog in Customizing at Customer Relationship Management -> Master Data -> Product Catalog -> Maintain IMS Server for Catalog Indexing.
  • In Extended Configuration Management (XCM), for productive Web shops, you can specify application configurations that always use active catalog variant versions. Additionally, you can define application configurations that allow selection of active, inactive, or obsolete versions of a catalog variant for a preview in the Web shop.
  • Log on to Extended Configuration Management (XCM) for your Web shop at: http:///or/admin/xcm/init.do.

  • Choose Start -> Components -> Customer -> webcatalog and create your own component configuration for inactive catalog variants.

  • Select Active or Inactive in the dropdown-box of the parameter catalogstatus under Component Configuration Details.

  • Assign the component configuration to the application configuration

Further Information






PERFORM Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 6379 Date: 20240520 Time: 203633     sap01-206 ( 112 ms )