Solution : https://service.sap.com/sap/support/notes/446294 (SAP Service marketplace login required)
Summary :
After performing a client copy in SAP, issues may arise due to the entities retaining the old logical system name from the source client, preventing proper workflow object functionality and producing message M7082 in transaction MB03. The root cause is that the target client maintains the old logical system name after data copying. To resolve this, define a new logical system with transaction BD54 and assign it via SCC4. Post-copy, use transaction BDLS for conversion if necessary. Automatic conversion post-copy is available from Release 4.6C onward with specific kernel patches. Ensure preconditions and corrections like 407854 or 407856 are applied for stability.
Key words :
terms sccl logsys m7 082 mb01 mkpf-logsys mkpf-awsys migo saplmigo vl02n sapmv50a rbdlsmap cor6rw documents, m7082 message appears, profit center document, fi document reason, relevant accounting document, material document, material document &, accounting document, document found, client copy
Related Notes :
| 781498 | MIR4: Missing follow-on documents |
| 540824 | Reporting: No display of FI documents |
| 489690 | CC INFO: Copying large production clients |
| 369758 | BDLS: New functions and better performance |
| 327602 | In table ACCTHD update logical system |
| 325470 | Activities after client copy in BW source systems |
| 320834 | Composite note: Updating own log.System in application |
| 206523 | CC-RELEASE: Client copy errors in 4.6C and 4.6D |
| 121163 | BDLS: Converting logical system names |
| 103228 | Naming the logical system |
| 67205 | CC-INFO: Copying large and productive clients |
| 28958 | Link to follow-on documents is lost |
| 24853 | CC-INFO: Client copy, functionality |
| 22514 | CC-INFO: Error analysis for client copy |