Ansicht
Dokumentation

/AFS/NDIF_MASS_UPDATE - Mass Update Report

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Title

Mass Update

Purpose

Before doing an initial download of AFS materials to any external systems, you must execute Mass Update to generate all required information. The user interface is divided into four sections:

• Matrix

• Coverage strategy

• Material

• Runtine version

Selection criteria are available for each section. You can execute the four sections simultaneously or separately.

If you want to execute all four sections simultaneously, choose each of the tabstrips and enter your selection data. Then select the processing mode (foreground/background).

If you want to execute all four sections separately, you should execute them in the sequence above.

1. Select the proper tabstrip (Matrix, Coverage strategy, Material or Runtime version).
2. Select Execute mass update.
3. Fill in your selection data.
4. Choose Execute. If you prefer to execute the update in background, choose Program → Execute in background from the menu.

Matrix mass update

This is the first step in converting existing AFS materials into standard materials.

Customers can select the material master matrix for which they need to create variant tables.

When you execute matrix mass update, the system generates variant tables for the selected matrix. The matrix is flagged as processed and the variant table name is stored in an application table.

Existing master matrices require mass update in order to create the variant tables required by the Knowledge Base dependencies of the materials.

Coverage strategy mass update

Customers can select the material category structure and/or coverage strategy for which they need to create variant tables. Not all the coverage strategies need to have variant tables, only those with category structure relevant for value combinations (type VLC).

You execute mass update of coverage strategies, the system generates variant tables for the valid ones. The coverage strategy is flagged as processed and the variant table name is stored in an application table.

Existing coverage strategies require mass update in order to create the variant tables required by the Knowledge Base dependencies.

Material mass update

Customers can select the materials that they need to convert and send to external systems. An AFS material is eligible for mass update when all these conditions are met:

• Its master matrix and coverage strategy are fixed

• Its master matrix has been updated so that its variant table is created

• If its coverage strategy is defined with combination values, the coverage strategy has been updated so that its variant table is created.

Caution: The mass update of AFS materials should occur before the CRM initial download is performed, so that the full processing will impact the only the AFS system.

Normally in CRM, the initial download is used to download all material information to CRM. This process is initiated from CRM and you can set up filters to restrict the data to be downloaded. After the initial download is finished, the delta download functionality is then triggered, and from now on it is used to transfer each change that occurs for a specific business object (in this case, the business object MATERIAL).

When the mass update of AFS materials occurs, either initial download from CRM has not been done and no data will be automatically transferred to CRM, or else the initial download was already done and each material change will be sent to CRM by means of BTEs (Business Transaction Events).

When CRM delta download is activated, BTE for the material will be raised and AFS variant master data will be sent automatically to CRM. Customizing settings identify whether the AFS variants should be transferred or not and whether they should be saved to database. If transfer is possible, Customizing settings determine whether it should occur right away or be submitted as a job. The AFS master data for the variant can then be generated at a later time. Users need to schedule their own jobs in background. (This generation option is specified in Customizing.)

Runtine version mass update

The runtime version must be generated after an AFS material has been converted and its bill of materials has been created. There is no automatic generation of the runtime version. You trigger the generation of the runtime version either through this mass update or from the standard menu.

Mass update of the runtime version allows you to launch multiple runtime versions for multiple Knowledge Base objects at once. You can choose the materials for which you need the runtime versions or else rely on the entries from the cross-reference table. You can run this mass update online or submit it as a background job.

Mass update of the runtime version should be done before the CRM initial download of the business object SCE (Sales Configuration Engine).

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example

ROGBILLS - Synchronize billing plans   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 6163 Date: 20240419 Time: 192114     sap01-206 ( 97 ms )