Kontakt

Ansicht
Dokumentation

CND_MAST_GEN_TRANSFER_OBJECTS - Generation of Objects for Transfer of Condition Master Data

CND_MAST_GEN_TRANSFER_OBJECTS - Generation of Objects for Transfer of Condition Master Data

rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Report CND_MAST_GEN_TRANSFER_OBJECTS can be used to generate various objects that are required for the transfer of condition records to the mobile client.

The report must be executed in a client that permits the maintenance of client-independent Customizing. You require authorization /SAPCND/CO, activity 64 (generation) to execute the report.

Integration

Prerequisites

Features

Selection

The condition tables for which the various objects should be generated can be restricted with the following parameters:

  • Application
  • Usage
  • Table Number

The following options are available to you:

  • Generate CDB Condition Tables and Additional Tables
Generally speaking, CDB condition tables and addiitonal tables are generated together with condition tables for CRM Online. It is only necessary to restart generation of the CDB tables if the previous generation failed.
  • Generate CDB Scale Tables
Generally speaking, CDB scale tables are generated together with condition tables for CRM Online. It is only necessary to restart generation of DCB scale tables if the previous generation failed.
  • Generate Synchronization BDocs
If condition records are required on the mobile client, it is necessary to generate corresponding synchronization BDocs for the relevant condition tables.
  • Activate Synchronization BDocs
In addition to being generated, synchronization BDocs also have to be activated. This can take place in one run together with generation. In exceptional cases it may be necessary to restart activation if the previous activation failed.
  • Store Secondary Index for Mobile Clients
This option causes a secondary index to be created on the mobile client. This is required for condition access (pricing), and should, therefore, be created for all condition tables that are transferred to the mobile client.
  • Generate Secondary Index for CDB Condition Table
This option causes a secondary index to be created for the CDB table, which improves the runtime during a Data Integrity Manager (DIMa) comparison with the CRM Online database. However, the runtime behavior deteriorates during the master data transfer to the CDB condition table.
  • Generate DIMa Objects
The Data Integrity Manager (DIMa) makes it possible to compare data in CRM Online tables and CDB tables. To use this tool for particular condition tables, corresponding DIMa objects are required.

Standard Variants

Output

Activities

Example






Addresses (Business Address Services)   General Material Data  
This documentation is copyright by SAP AG.

Length: 3634 Date: 20240531 Time: 080059     sap01-206 ( 59 ms )