Solution : https://service.sap.com/sap/support/notes/644516 (SAP Service marketplace login required)
Summary :
When executing a client copy in an SAP system with installed components like FINBASIS, EACC, SEM-BW, or BANK-ALYZE, and where the source client is not client ‘000’, certain unique configurations and DDIC structures necessitate special handling. These must be regenerated post-copy to function correctly. The solution involves establishing an RFC connection for the source client, followed by mandatory postprocessing involving updates of configuration information and generation of DDIC structures and programs using SCCL for local copies or SCC9 for remote ones. Additionally, attention is required for components like EACC, where transaction data does not automatically transfer and requires specific steps to ensure complete data migration in the target client. For postprocessing and transaction data handling, different SAP transactions and reports are utilized.
Key words :
industry solution 'catch weight management', data tables copying transaction data, 'issue messages online' option, bank-alyze components installed, 'copy transaction data' option, copying transaction data, transactiondata tables' option, 'transaction data' option, package size specifies, start transaction finb_tr_exec_ai
Related Notes :
| 1166677 | FINBASIS/SEM-BW customizing transports - errors & help |
| 1129375 | Client copy post-processing fails: acc. system not found |
| 756843 | Client copy postprocessing: FINB_TR045 |
| 692388 | Transports and client copy for Bank Analyzer |
| 568784 | Termination with client copy (Financials Basis) |