Kontakt

Ansicht
Dokumentation

CRM_FICA_MIG_PROVIDER_CONTRACT - Report to load Provider Contracts with async RFC

CRM_FICA_MIG_PROVIDER_CONTRACT - Report to load Provider Contracts with async RFC

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use the report to:

  • Migrate provider contracts to SAP CRM
  • Generate import files for the migration of provider contracts to SAP ERP and SAP CC with the Industry Solution Migration Workbench (ISMW)

Creating Provider Contracts in SAP CRM

The file that contains the data for migrating the provider contracts can be stored on the work station or in the SAP file system.

The following details are required for the file:

  • Directory and name of the file
  • Character set (code page) of the file
  • Separator (delimiter) that is used in the file for separating field information (if you enter SPACE, tab is used as the separator)
  • Indicator, which is used to designate the field names in the file to indicate that these fields are always to be supplied with a value during migration

If you want report ISMW to create import files for provider contracts that were already migrated to SAP CRM, use the "Select Contracts from the Database" mode.

In the runtime parameters of the report, you can make the following specifications for parallelization of the migration of provider contracts:

  • Maximum number of RFCs (Remote Function Calls) to be used
  • Maximum number of provider contracts that are processed in each RFC
  • RFC logon group that determines which instances are used (you can define logon groups using transaction RZ12)
  • Set the "Synchronous Processing" parameter if you do not want to use RFCs. Only use this parameter for test purposes. In this mode, there is no parallelized creation of provider contracts.
  • Set the "Debug Mode" parameter if you want to debug the creation of provider contracts. You can only set debug mode with synchronous processing.

Additionally, you can activate the IPC Pricing Configuration Check. We recommend setting this flag only for testing purposes (to make sure that the migrated provider contracts are correct from an IPC perspective). As soon as you migrate a large number of provider contracts, make sure that the IPC Pricing Configuration Check is deactivated.

Creating Files for Migration of Provider Contracts with ISMW contracts:

  • Maximum number of RFCs (Remote Function Calls) to be used
  • Maximum number of provider contracts that are processed in each RFC
  • RFC logon group that determines which instances are used (you can define logon groups using transaction RZ12)
  • Set the "Synchronous Processing" parameter if you do not want to use RFCs. Only use this parameter for test purposes. In this mode, there is no parallelized creation of provider contracts.
  • Set the "Debug Mode" parameter if you want to debug the creation of provider contracts. You can only set debug mode with synchronous processing.

Creating Files for Migration of Provider Contracts with ISMW

In addition to parallelized migration of provider contracts to SAP CRM, the report can generate import files for ISMW. You can then subsequently use these import files to load provider contracts to SAP ERP and SAP CC using ISMW.

The system determines the data for the ISMW import files as follows:

  • File on work station or in SAP File System:
In the case of migration of contracts to SAP CRM, the function module CRM_ISX_BTX_API_CONT_CREATE is used. This function module returns the data in a form that is suitable for updating the import files.
  • Select contracts from the database:
Already existing contracts in CRM are read from the database using the static method CONTRACT_COL_GET of class CL_CRM_ISX_PROV_ORDER_API_PRXY. You have two options. You can select provider contracts to be read using the ID of the provider contracts in the SAP system. Or you can select migrated provider contracts using their key from the legacy system (in this case, the system automatically converts the key from the legacy system using table CRM_ISU_TEMKSV).

You can also generate a new legacy system key. To do so, select the appropriate checkbox.

If you want to assign the legacy system key MIG_1234 to contract 1234, enter the new legacy system key MIG_& in the "Generic New Legacy System Key" field.

You can also save the newly created legacy system key in table CRM_ISU_TEMKSV. To do so, select the corresponding checkbox.

There are three different modes available for creating the ISMW import files:

  1. The files are created online. (The files are updated continuously after each provider contract is created.)
  2. The files are created subsequently. For this mode, the system must retain a large amount of data in the main memory before the data at the end of the report can be written to the files.
  3. No data is generated.

Modes 2 and 3 are for test purposes only.

To read information about the migration objects in the ERP system, the RFC destination (to the ERP system) and migration company in the ERP system are needed.

The character set of the generated files is determined by the character set that is set up in the system.

For each ISMW import file, you can make the following settings:

  • Should a file be created?
  • Based on the configuration of which ISMW migration object in the ERP system should the files of the provider contracts be updated in the import?
  • In what directory and under what name should the file be saved? Note that file names (including endings) can be a maximum of 14 characters long. The ISMW cannot process files with longer file names.
  • If there is an existing file with the same name, is it allowed to be overwritten? If this indicator is not set, and there is already a file with the same name in the specified directory, the system issues a message in the status line.
  • For the ISMW import file for loading the contracts to SAP CC, you can also enter the block size to optimize the migration of the provider contracts SAP CC. The block size specifies how many provider contracts are transferred to SAP CC with one call of the operation chargingContractMaintainMass of the Web service ContractProvisioningServices.

The specifications in the group box CRM Migration Objects are needed for 2 reasons:

  • The report records provider contracts that were successfully created in SAP CRM in table CRM_ISU_TEMKSV. The key of the table is the migration company, the migration object, and the ID of the provider contract in the legacy system. In each record, the system persists the key of the provider contract in SAP CRM. Using this information, the report can prevent a contract from being migrated more than once from the legacy system. (The provider contract ID from the legacy system is not persisted in the provider contract in SAP CRM.)
  • Table CRM_ISU_TEMKSV can be used for converting the IDs of business partners and contract accounts from the legacy system. To use this table, store a data record for each business partner migrated to SAP CRMin table CRM_ISU_TEMKSV. For the contract account, store a record for each contract account.

For storing the data in table CRM_ISU_TEMKSV, you need a project-specific solution. In the file for creating the provider contracts in SAP CRM, you can specify in the management data that the conversion is to be made using table CRM_ISU_TEMKSV.

To do so, enter in the management data of the CRM import file that the business partner ID from the legacy system that comes from the file under PARTNER_NO should be converted using table CRM_ISU_TEMKSVl (PARTNER_NO|CRM_ISU_TEMKSV-PARTNER).

You use an analogous approach for the legacy system key of the contract accounts in the file under BUAG_ID (BUAG_ID|CRM_ISU_TEMKSV-BUAG).

If you do not use the conversion with the help of table CRM_ISU_TEMKSV, then you can leave this input parameter of the report blank.

Application Log

In the Application Log group box, you decide if an application log should be created.

You also specify if success messages are stored in the log.

The object and subobject are used for updating the application log. You can display the log created for this object/subobject in transaction SLG1.

If you set the Restart Mode indicator, the report does not issue an error message when the file contains provider contracts that were already migrated successfully. You should therefore set this indicator when a migration is interrupted and you want to try to load the provider contracts to SAP CRM again using the same file.






RFUMSV00 - Advance Return for Tax on Sales/Purchases   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 9488 Date: 20240531 Time: 114208     sap01-206 ( 152 ms )