Solution : https://service.sap.com/sap/support/notes/38298 (SAP Service marketplace login required)
Summary :
Starting from SAP Release 3.0, no specific transport function needs to be specified for transporting general table entries (R3TR TABU). The system automatically handles all needed entries in both object lists and key data during transport requests. When creating manual transports, users have to use transactions such as SE01 for listing maintenance or specifying new entries. For entries with large keys, a detailed maintenance screen helps specify each key field. If a table entry exists in the source, it's transferred to the target; missing entries are also deleted in the target. Generic keys can be specified with an asterisk for batch transport.
Key words :
additional key words se01 se09 se10, transporting general table entries, general table entries manually, ' -> 'object list' -> 'display<->change', total key length, greater key lengths, generic key area, subsequent key field, entryr3tr tabu <table, special transport functions
Related Notes :
| 18727 | Client control in Release 3.0 |
| 2857 | What table delivery classes are there? What is their signifi |