Solution : https://service.sap.com/sap/support/notes/547971 (SAP Service marketplace login required)
Summary :
When using transaction MC8V to copy planning data between different versions, users may encounter issues such as incomplete data copying or excessive processing time. Issues stem from MC8V's design, which limits data copying to entries that match the current periodicity settings configured in transaction MC7F. As a remedy, users should copy data in phases aligned with their respective periodicities and utilize LIS Copy Management (transactions MCSZ or OLIX) for improved functionality and performance. Note, in cases of mixed period units within level-by-level planning, MC8V remains necessary since LIS Copy Management only copies current periodicity data.
Key words :
period units exist, period units contained, mixed period units, mixed planning periods, version copier reason, information structure version, lis copy management, increased performance depending, function period split, copy planning data
Related Notes :
| 537806 | Performance CopyMan: Version deletion optimization |
| 530444 | Performance CopyMan: Filling unused selections (2) |
| 458529 | CopyMan: Error when deleting initial records |
| 458063 | Performance CopyMan: filling of unused selections |
| 444726 | Poor performance when deleting version |
| 443749 | Changed storage parameters for non-planning relevant IS |
| 410247 | Copy management / version copier RMCSISCP: Performance |
| 406614 | Performance during deletion of info structure data |
| 388811 | Copy Management: various errors S032 and S035 |
| 378510 | LIS: Deleting CopyMan- and recompiling logs |
| 356473 | Copy Mangmt:performance whn deleting target vers(2) |
| 330600 | Copy Mangmt:performance whn deleting target version |