Solution : https://service.sap.com/sap/support/notes/86900 (SAP Service marketplace login required)
Summary :
This SAP Note addresses limitations in the transport function for Customizing data concerning 'Release strategies.' The primary issue is that while the 'Transport' function under 'Table view' in Customizing supports release strategies (table T16FS), it does not automatically include dependent data such as release prerequisites (table T16FV), release statuses (table T16FK), and classification data. To ensure a complete transport, users must manually implement data from these tables into the transport request using Transaction SE16, specifying the relevant release group and strategy for each table. Program ID (R3TR), Object type (TABU), and other metadata must be correctly referenced in the transport request.
Key words :
t16fv client client release group release group release strategy release strategy release code 3, t16fk client client release group release group release strategy release strategy release code 4, release procedure area 'release strategies', release strategy read note 45951, additional key words omgq, corrresponding release strategy, release group, release strategy, table display transaction se16, transport release strategies
Related Notes :
| 365604 | FAQ: Release strategies in purchasing |
| 45951 | Transporting class data: system / client |
| 10745 | Copying classification data to another client |