Ansicht
Dokumentation
DMC_MT_COUNT_TABLES - MWB: Table Count for a Mass Transfer
BAL Application Log Documentation SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Purpose
Counting the tables in a mass transfer
Features
The table counter counts all tables in a mass transfer and stores the result for the given mass transfer together with the related access plan or precalculation ID. If different target tables were defined in a mass transfer, these tables are used for the counting in the receiver sytsem.
Selection
As input, the function needs the ID of the mass processing.
It is necessary to specify an access plan or precalculation ID because the result of the counting is stored together with the access plan or precalculation ID. The related access plans or precalculations do not necessarily have to exist at the time when they are entered here.
You can exclude certain tables from the counting. This makes sense, for example, if very big tables are involved in a mass transfer and counting them would take too much time. As an alternative, you can limit the counting to specific tables.
If a counting is started repeatedly, only the tables that have a number of data records equalling zero in the related field are counted once again. If you want to count all tables once again, set the indicator "Count All Tables Again".
By default, the tables from the table list for the mass transfer are counted. In addition to the options that have already been named (exclude tables, only count specific tables), you can change the worklist using the following settings:
- Determine tables from conversion objects (incl. hierarchical objects): once you have created a conversion object, the relevant tables are determined based on the tables that are defined in the conversion object. In the process, table hierarchies are also expanded, so that all of the tables of a conversion object are counted. Differing target tables are also determined, provided a unique assignment exists (a unique assignment exists when only one receiver table is assigned as a primary relation to a sender table). If, however, a table in the receiver container is not defined in the sender container and is also not uniquely assigned to a sender table, this table cannot be included in the worklist.
- Ignore tables with application insert: if a receiver table is uniquely assigned to a sender table, which in turn is marked as an application insert, you can use this setting to exclude this table from the counting in the sender and the receiver.
- Take additional tables in counting persistence into account: if you activate this function, all
additional entries from the counting persistence (database table DMC_MT_COUNT_RES) with the same mass
transfer and access plan IDs are read and counted, in addition to the determined table quantity. This
function lets you count additional tables that are not present in the worklist for the mass transfer.
You have to manually create the additional tables in database table DMC_MT_COUNT_RES with the corresponding mass transfer and access plan IDs.
Caution: as soon as this function is activated, all tables (for the current ID) in the counting persistence (DMC_MT_COUNT_RES) are counted. If you deleted tables from the worklist for the mass transfer, for which an entry already exists in the counting persistence, this table will still be counted for this function. For this reason, the user has to manually delete obsolete tables from the counting persistence when using this function.
The counting takes place at two points in time during the project:
- Before the migration: At this time, the tables in the sender system and in the receiver system are counted to find out about the number of data records before the migration. Consequently, this step must be completed before the actual data transfer starts.
- After the migration: After the transfer, the tables in the receiver system are counted once again. This data is needed for a comparison between the expected and the actual number of records in the receiver system.
For the counting "before the migration", you can make an additional setting. If you activate the option "Use Merge Scenario" (by choosing the relevant pushbutton), additional fields are displayed at the end of the input screen. To deactivate this function, choose the same pushbutton (which is now labeled "Use Standard Scenario") again.
If you have a merge scenario, you need to additionally specify the mass transfer and access plan that has been used for the transfer to the same target system (and client). Because in a scenario of this type the number of data records in the receiver system before the transfer is the same as the number of records in the receiver system after the transfer, the tables for the values from the previous transfer are not counted again in the receiver system. If the current mass transfer covers additional tables, these are also counted in the receiver.
In section "Relevant Systems", you specify (by selecting the relevant checkbox) the system in which you want to do the counting. Thus, you can, for example, do the counting for the sender and for the reveicer system at different times before the migration. If you want to do the counting for a certain system, you need to maintain the related RFC connection correctly. Also, you can specify the number of jobs you want to use in parallel for the counting in the given system. When specifying this number, consider that the number of batch processes available in the MWB system must be at least as high as the number of jobs to be started in parallel in the sender and receiver system.
If you want to count a large number of tables, start this program in the background. The logging takes place in the usual way (via application log); you can view the log via transaction SLG1.
Standard Variants
Output
Prerequisites
The specified mass transfer was created, and the relevant tables are maintained.
Activities
Example
CL_GUI_FRONTEND_SERVICES - Frontend Services CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 6348 Date: 20240531 Time: 233944 sap01-206 ( 166 ms )
