Ansicht
Dokumentation
Copy delivery customizing to target client ( RELNISB_303_CUST_ALL )
ABAP Short Reference ABAP Short ReferenceThis documentation is copyright by SAP AG.
Short text
Copy delivery customizing to target client
Description
The sample customizing for Bank Controlling is delivered in client 000. The following documentation describes the procedure for transferring this customizing to a target client. You can do this by making a client copy of the corresponding tables. Note, however, that the IS-B customizing settings are not only used by IS-B; they also have an effect on other applications. There are therefore two possible starting situations:
1. The IS-CD SAP Banking is newly installed and no other application is active in the target client.
2. Other applications are already active in the target client.
Solution for situation 1:
Make a client copy. You can find the relevant function in the menu under Tools-> Administration->Administration->Client admin. You are advised to read the online documentation for this function. Existing standard system customizing settings are overwritten. You must therefore only use this procedure if there are no active R/3 applications in the target client.
Solution for situation 2:
In this case we strongly recommend that you DO NOT make a client copy. Instead, proceed as follows:
Important Requirement
First create a data backup before copying parts of the customizing!
Division of IS-B Sample Customizing
The sample customizing is sub-divided based on content and on importance for other applications. The latter sub-division in turn differentiates between critical and uncritical customizing settings.
Critical and Uncritical settings
The IS-B sample customizing is sub-divided based on importance for other applications. Uncritical settings are those which only affect IS-B, while critical settings may also affect other applications (such as Treasury). These differentiations allow you to only copy parts of customizing.
Only copy critical settings if you are certain no settings will be overwritten. You can check this by comparing the table entries in the transport requests with the table entries which already exist in the target client.
Procedure
The following functions are for importing cross-application customizing.
Copy critical organizational data
This transport request contains the objects in the enterprise structure (company code, controlling area, operating concern 0MB1) which are a prerequisite for importing further customizing settings.
Copy critical basic data
Basic data mainly comprises the settings in the interest rate tables (yield curve type 0001, ...) which are also of prime importance for importing further customizing settings.
Copy critical Treasury data
This transport request contains the settings in the Treasury tables such as entries for price types, leading currencies and exchange rates.
Copy uncritical product variants
The product variants are uncritical for other applications.
Since the customizing for the various bank transactions is based on the cross-application sample customizing, we recommend that you import the above four transport requests first.
Here is a list of the transport requests differentiated according to bank transaction.
Copy critical money market sttings
Copy critical forex settings
Copy critical derivatives settings
Copy critical securities settings
Copy critical loans settings
Copy critical account settings
Copy uncritical service settings
Copy uncritical interest-free position settings
Further notes
If you are unable to make a client copy for the entire customizing, you should copy the customizing settings, depending on the constellation, in several steps:
- Create a copy of the target client
- Import the necessary cross-application settings, if necessary carry out a comparison in the target client and maintain settings there manually.
- Import the bank transaction transport requests you require
- Set and check all settings and maintain the number range
- Test the system
- Import all settings from the copy client to the target client.
The customizing settings in the transport requests correspond to the entries in the cutomizing tables.
Manual comparison of table entries
When you import transport requests, settings with the same key in the target client are overwritten. When a manual comparison is made, the keys of the settings in the transport requests are compared with the settings in the target client. You can find out the name of the transport request in the next screen of the corresponding function ('Copy critical organizational data' for example). For this function, the name of the transport request is ISB1_ORK.
You can display the transport request by choosing the function Utilities-> Maintenance-> Corrections in the ABAP/4 Development Workbench, entering the name of the transport request and selecting 'Object list for transport'.
By selecting the editor you can display the object list of the request and the corresponding table entries.
General Material Data BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 6138 Date: 20240602 Time: 190008 sap01-206 ( 74 ms )