Prepare and sync product sales text

  • 2 minute(s) read
Prev Next

Zilliant CPQ can retrieve product sales text, known as material sales text in SAP ERP, as part of the product synchronization process. In SAP, sales text is maintained per sales organization and distribution channel and can have translations in several languages. However, during synchronization, only the languages maintained in Zilliant CPQ are retrieved.

This topic explains:

Synchronize product sales text

To automatically synchronize products with sales text:

  1. In Zilliant CPQ, enable the SettingProductSyncDownloadProductSalesText setting:

    1. Sign in to Zilliant CPQ with your administrator credentials.

    2. From the left navigation area, select Administration.

    3. From the top navigation bar, select Master Data Management.

    4. Move through or search to locate Setting Boolean and select it from the list.

    5. Select SettingProductSyncDownloadProductSalesText.

    6. Set the Setting Value Boolean switch to YES.

    7. Select Save.

  2. In SAP ERP, enable the RFC_READ_TEXT BAPI. This BAPI is used to read the text content directly from SAP ERP during synchronization. For details, read Enable BAPIs.

Lookup tables for sales text synchronization

Two Zilliant CPQ lookup tables support the sales text synchronization:

MVKE table

This table links a product (known as material in SAP ERP) with the relevant sales organization and distribution channel. It ensures that CPQ can locate the correct sales text entry in SAP.

The MVKE table contains the following columns:

  • MATNR—Product ERP ID (material number in SAP ERP).

  • VKORG—Sales organization ERP ID.

  • VTWEG—Distribution channel ERP ID.

You can populate this table in either of the following ways:

  • Direct sync from SAP’s MVKE table. To limit the number of records, create a filtered database view in SAP ERP and sync that view instead.

  • Manual data entry in CPQ.

LANGUAGEKEYS table

This table maps SAP language keys to the 2-character ISO language codes used in CPQ. The data source for this table is SAP’s T002 table.

The LANGUAGEKEYS table contains the following columns:

  • SPRAS—Language key.

  • LAISO—2-character SAP language code.

Groovy script for language mapping

By default, Zilliant CPQ uses the current user’s locale language to determine which sales text to display for a product. However, you can override this behavior by uploading a Groovy script for the predefined extension point. This helps support cases where the sales text is used for a different purpose. In a Groovy script, define custom mapping logic between the user’s language and the desired SAP sales text language.

To use a Groovy script for language mapping:

  1. Write a script.

  2. Upload the script to CPQ.

Write a script

The following binding variables are available for the script:

Variable name

Description

userLanguage

The 2-character ISO code of the current user’s language, for example, en or de.

textType

Type of text being requested, for example, SALES_TEXT.

Sample script:

/* This script determines the sales text language to use
* when retrieving product sales text from SAP ERP.
*/

if (textType.equals("SALES_TEXT")) {
    return "en_sg";
}

return userLanguage;

Upload the script to CPQ

Upload the script for UserLangToTextLangMappingScript. For details about uploading and configuring Groovy scripts, read Upload a Groovy script.

This script runs automatically when Zilliant CPQ retrieves sales text from SAP ERP.