Sometimes, it is preferable to change the way the application processes the migration data.
The most important reason is to improve the performance of the data load by avoiding checks in the application that are not necessary, for example, due to the data migration strategy. It might also be that the SAP application must accept the data because the data was already accepted in the legacy system and needs to be transferred as it is.
Verifying the existence of billing documents while you are migrating device installations may not be required if, according to the migration strategy, billing documents are to be migrated after the installation of devices. In bypassing this verification, you can save database accesses. This improves the performance of the device installations. However, if billing documents already exist due to a previous migration step, a verification must be executed.
The requirements are different in each project. Therefore, it is in the responsibility of the project to verify whether it is possible to take advantage of a control parameter.
Switching off standard checks may lead to inconsistencies in the application and the database. Use control parameters carefully. Documentation is available for each control parameter. Check the documentation in the IS Migration Workbench thoroughly before changing the delivered settings.
The application reads the control parameter during data migration, and treats the data according to the setting of the relevant control parameter. Sometimes, the setting of the control parameters supersedes the Customizing in the IMG. The following control parameters are available in the IS Migration Workbench:
3.6.1 General Control Parameters
o FICA_INTEREST_DATE (Definition of a field in the FKKOP_T structure)
The FICA_INTEREST_DATE control parameter decides which field of the FKKOP structure the information of the last interest calculation date in the legacy system is transferred to. This occurs during data migration of financial open items. When open items with the DOCUMENT migration object are migrated, a corresponding interest calculation attachment is written to ensure correct processing of the document in the next interest calculation run.
o EVENT_DISTR_IMPORT (User-specific function module for distributed import)
The EVENT_DISTR_IMPORT control parameter defines a custom-specific function module during the execution of the distributed import. For more information, see chapter 2.7.5 User-Exit in Master Job.
3.6.2 Control Parameters Specific to SAP for Utilities
o BBP_DFKKTHI_OFF (Deactivation of the update of the DFKKTHI database table)
The BBP_DFKKTHI_OFF control parameter controls the update of DFKKTHI database table during the migration of budget-billing plans. The application updates the DFKKTHI database table when deregulated budget-billing plans are migrated even a dispatch or aggregated posting is not required. For more information, see SAP note 794199.
o INST_CERT_CHECK_OFF (Deactivation of a certification check for a device installation) The INST_CERT_CHECK_OFF control parameter controls the certification of devices during the migration of device installation. This parameter prevents checks for the next replacement year during device installation so it is possible to migrate historic processes correctly. For more information, see SAP note 314579.
o INST_CERT_LOSS_OFF (Avoidance of the loss of the device certification)
The INST_CERT_LOSS_OFF control parameter controls the certification of devices during the migration of device removal. This parameter is designed to avoid the loss of certification during the removal of devices (without considering the settings in Customizing), so it is possible to display historic processes correctly. For more information, see SAP note 314579.
o INST_BILLPER_OFF (Deactivate check for billed periods)
The INST_BILLPER_OFF control parameter controls the checks of already billed periods during the migration of device installation, removal, and replacement. This parameter allows changes of the installation structure in periods where billing documents already exist for this installation. For more information, see SAP note 449827.
o INST_CONS_OBJ_OFF (Deactivate period consumption for device installation
The INST_CONS_OBJ_OFF control parameter controls the processing of the period consumption during the migration of device installation, removal, and replacement. This parameter deactivates the processing of the period consumption object. The period consumption must be migrated separately with the CONSUMPT migration object. For more information, see SAP note 314579.
o INST_CONS_BILL_OFF (Deactivate period consumption during bill-related installation) The INST_CONS_OBJ_OFF control parameter controls the processing of the period consumption during the migration of a billing related device installation. This parameter deactivates the processing of the period consumption object. For more information, see SAP note 445399.
o INST_CONS_RATE_OFF (Deactivate period consumption during rate maintenance) The INST_CONS_RATE_OFF control parameter controls the processing of the period consumption during the migration of rate data at device and register level with the DEVICERATE migration object. This parameter suppresses a generation of time slices when migrating rate data if the period consumption values have already been migrated.
o INST_DISMANT_CH_OFF (Deactivate check for disconnection)
The INST_DISMANT_CH_OFF control parameter controls the checks for disconnections during the migration of a device installation, removal, and replacement. This parameter deactivates the checks for device disconnection to be able to work with devices regardless of the assigned disconnection status. For more information, see SAP note 445399.
o INST_PREDEF_EAST_OFF (ignore predefined register relationship)
The INST_PREDEF_EAST_OFF control parameter controls the processing of predefined register relationships during the migration of device installation. This parameter deactivates the consideration of predefined register relationship in Customizing. The register relationship can be migrated separately with the REGRELSHIP migration object.
For more information, see SAP note 445399.
o INST_FACTS_REQ_OFF (Deactivate Check for Required Value for Operand)
The INST_FACTS_REQ_OFF control parameter controls the handling of the Required Value for Operand indicator during the migration of business objects that effect installations. With this control parameter, missing required values for operands are ignored when you create or change installations until the migration of operands with the FACTS migration object.
o INST_POD_OBJ_OFF (Deactivate changes to PoD during changes to installation)
The INST_POD_OBJ_OFF control parameter controls the processing of a point of delivery (PoD) during the migration of changes of an installation. This parameter deactivates the processing of the POD when an installation is changed. For more information, see SAP note 508222.
o INST_POD_PRO_CH_OFF (Deactivate the profile and PoD allocation)
The INST_POD_PRO_CH_OFF control parameter controls the checks of profile and PoD allocations during the migration of device installation. This parameter deactivates the checks for existing profile and POD allocations. For more information, see SAP note 445399.
o MOI_POD_SERV_CH_OFF (Deactivate default values of PoD services during move-in) The MOI_POD_SERV_CH_OFF control parameter controls the processing of non-billable PoD services during the migration of a move-in with the MOVE_IN migration object. By not carrying out a check for existing default values and subsequent allocation of non-billable POD services, the customized proposal logic of POD services is deactivated. In addition, transferred POD data in the automation data is not processed. POD services have to be migrated separately with PODSERVICE migration object. The usage of the MOI_POD_SERV_CH_OFF control parameter improves the performance of the migration of move-ins. For more information, see SAP note 508222.
o MR_VALIDATION_OFF (Deactivate meter reading result validation)
The MR_VALIDATION_OFF control parameter controls the processing of meter reading validation during a device installation with INST_MGMT migration object, and the migration of meter readings with METERREAD migration object. This parameter allows the migration of meter readings, which have been accepted in the legacy system but would be rejected by the defined plausibility rules in the Customizing of the SAP system.
o POD_BILLPER_OFF (Deactivate checks of already billed periods)
The POD_BILLPER_OFF control parameter controls the checks of already billed periods during the migration of meter readings. This parameter allows changes to the PoD for periods that have already been billed. For more information, see SAP note 656893.
o READ_BILLPER_OFF (Deactivate checks of already billed periods (meter reading)) The READ_BILLPER_OFF control parameter controls the checks of already billed periods during the migration of meter readings. This parameter allows the migration of meter readings in periods that have already been billed, for example, the migration of meter readings after the successful migration of billing documents. For more information, see SAP note 449827.
o PERF_EVENT_OFF (Deactivate update of workflow events of SAP for Utilities)
The PERF_EVENT_OFF control parameter controls the handling of workflow events during the data migration for all SAP for Utilities specific migration objects.
o PERF_STATS_OFF (Deactivate update of stock/transaction statistics)
The PERF_STATS_OFF control parameter controls the creation of stock and transaction statistics during the data migration for all relevant SAP for Utilities specific migration objects (material management or plant management).
o CRM_REPL_OFF (Deactivation of CRM replication)
The CRM_REPL_OFF control parameter controls the delta replication of business objects to the SAP CRM system during data migration. For more information, see chapter 6.17 Replication to SAP CRM.
3.6.3 Configuring Control Parameters
Choose IS Migration Settings Customer Settings for a configuration of the control parameters. Define control parameters for all configured migration companies by leaving the Company field empty. If you enter a migration company but leave the Mig.Object field empty, the setting of the control parameter is valid for the entered migration company only.
By entering a migration company and a migration object, you make the setting of the control parameter migration object specific. Figure 3-13 shows the maintenance screen for control parameters.
Figure 3-13: Control Parameter for Custom-Specific Function Module Figure 3-14 shows defined control parameters in a customer project.
Figure 3-14: Customer Settings of Control Parameters
3.6.4 Function Module ISU_MIG_STATUS
The application calls the function module ISU_MIG_STATUS to check the settings of the migration control parameters. The interface of the function module ISU_MIG_STATUS has the following exporting parameters:
o Y_ACTIVE Application is called by a load program (Y_ACTIVE = ‘X’) o Y_FIRMA Name of the migration company
o Y_OBJECT Name of the migration object whose load program is executed o Y_TEMSTAT Structure with all control parameters and their actual settings o Y_<parameter> Specific control parameter
You this function module to bypass implemented user-exits and BAdIs (business add-in) which do not need to be executed during data migration (for example, to improve the migration performance). Figure 3-15 shows a code snippet that calls the function module ISU_MIG_STATUS in a customer code. The customer code is executed when migrating business partners with the load program of the PARTNER migration object.
* local data definition
DATA: lv_active TYPE c, lv_object TYPE emg_object.
* check whether data migration is active CALL FUNCTION 'ISU_MIG_STATUS'
IMPORTING
y_active = lv_active y_object = lv_object.
IF lv_active = 'X' AND lv_object = 'PARTNER'.
* execute migration specific code ELSE.
* execute non-migration specific code ENDIF.
Figure 3-15: Usage of the function moduleISU_MIG_STATUS
4 Enhancing a Load Program
4.1 Motivation
This chapter shows how to handle some standard tasks when using the IS Migration Workbench for enhancing the load report or generating own migration objects. It describes the layout of the generated load program and details where and how own ABAP code can be inserted. Finally, the chapter describes how to incorporate customer fields in the data migration process.