Ansicht
Dokumentation
/SCWM/R_CONV_BSKEY - EWM Business System Key Conversion
RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Purpose
This transaction allows you to change a business system key in all EWM tables. Its purpose is to prepare a new client after a client copy or system copy. This new client has a new business system key in the system landscape directory (SLD). However, the EWM tables still contain the old business system key. In order to be able to use EWM functionality in this client with the new business system key, the EWM tables must be adjusted. You can perform this adjustment with this transaction.
Integration
Prerequisites
This transaction cannot be executed in:
- A productive system (if any client is set to productive)
- A client that is locked due to client copy
- A system that is currently being upgraded
You have already maintained the new business system in the list of business systems. For more information, see Define Business System.
If the new business system is the business system of the local client, you can change this configuration before you execute the transaction. For more information, see Define Own Business System. The configuration can also be changed afterwards.
Features
The transaction offers a test run. The test run determines which tables are relevant and the number of records to be updated in each table. Then it shows a log with the results.
To execute the transaction in productive mode, you can run it in dialog mode or in a batch job. If you expect longer processing times due to the size of the client, it might be better to use a batch job. If you experience any timeouts, you should use a batch job to avoid this.
Furthermore, the transaction offers parallelization to improve performance. For this, a logon/server group must be specified.
In the field “Restrict Tables”, you can enter a subset of tables that are to be updated by the transaction.
In the field “Additional Tables”, you can enter specific tables that are not part of the EWM standard but that are to be updated by the transaction.
If necessary, you can change the number of “Records per Commit Work”. The transaction may use multiple LUWs per table if the table is very large. This is to avoid database errors due to the size of the roll area. If you encounter database errors, you can reduce the number of records, but note that this may lead to worse performance.
Selection
Standard Variants
Output
The transaction will create and display an application log listing all affected tables and the number of records that were updated.
Activities
Example
In the previous client, you were using the business system key ABC_100. You copied client 100 to client 200, but now in client 200, you want to change the business system key to ABC_200. You perform the following steps:
- In client 200, change the configuration for business systems and for your own business system to ABC_200.
- Remove ABC_100 from the list.
- Execute this transaction, using the following parameters:
- Old Business System = ABC_100
- New Business System = ABC_200
If you have custom tables containing the business system key, you can add them under “Additional Tables”. First, you can perform a test run to see the scope of the conversion. Then, you can execute the transaction in productive mode.
Afterwards, the business system key is changed. If you also need to change further business system keys (for example, for the ERP system if you are using decentralized EWM), you can repeat the transaction for these business systems as well.
rdisp/max_wprun_time - Maximum work process run time Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 4254 Date: 20240419 Time: 012041 sap01-206 ( 67 ms )
