Solution : https://service.sap.com/sap/support/notes/45951 (SAP Service marketplace login required)
Summary :
SAP Note describes ALE as a preferable method for transporting class data between clients or systems, ensuring data consistency unlike client copy which can only clone master and transaction data fully if the target client is empty. Assigned object dependencies distribution is feasible from Release 3.1G, and engineering change distributions from 4.0B. The solution involves maintaining the partner profile and port via Transaction SALE, and logical connections and message objects for distribution through 'Distribution customer model'. Object distribution must follow sequence with classification requiring preceding object distribution. IDoc types CLFMAS do not support certain class types due to mass issues.
Key words :
- sap library - basis - middleware - ale application link enabling, path 'cross application -> business framework architecture, --> ale application link enabling -> quickstart', ale introduction / ale programming guide, terms transport classestransport characteristicstransport classificationomgq, prerequisites assigned object dependencies, copying individual class tables, replace message type 'matmas', choosing 'distribution customer model', transport class data
Related Notes :
| 365604 | FAQ: Release strategies in purchasing |
| 138056 | Customizing batch: Sort rule / Selection class |
| 93334 | Transporting characteristics of class SAP_KKR_CLASS |
| 86900 | Transport of Release strategies (OMGQ,OMGS) |
| 73012 | Customizing batch: Sort term/selection class |