Solution : https://service.sap.com/sap/support/notes/326801 (SAP Service marketplace login required)
Summary :
After upgrading or performing language transports, inactive SAPscript forms and styles may result, triggering SE71 or SE72 errors (TD134, TD224). Additionally, runtime may display TD427. A significant challenge is the long runtime of report RSTXINSH, exacerbated by large entries in tables STXH and STXL, particularly under the CLIENT_CASCADE parameter. Root cause is inconsistencies in TXT sections after new language transport methods. Mitigation involves configuring RSTXINSH’s search parameters and preemptively managing settings to streamline processing time. For swift resolution, updating RSTXINSH from the SAP service portal is recommended, alongside specific import guidelines.
Key words :
tp addtobuffer y9dk005599 <sid> tp import y9dk005599 <sid> <sid>, ~ftp/general/r3server/abap/note, sap ftp server sapservx, additional key words sapscript, solution report rstxinsh searches, car -xvf y9dk005599, unpacked files y9dk005599, key word 'sap', ddic table stxl, full-table scan
Related Notes :
600227 | RSTXINSH for customer forms |
494868 | RSTXINSH: client_cascade |
454421 | RSTXINSH: Performance when updating the STXL table |
432272 | Transporting language data using tp/R3trans |
422451 | Error message TD423 when you print shop floor papers |
329622 | Additions: Upgrading to Basis 4.6C SR1 (NDI upgrade) |
327285 | Additions to upgrade to 4.6C SR1 |
215655 | Current SAP Note on language import 4.6D |
195443 | Current note on language import 4.6C |
195442 | Language import and Support Packages |
192949 | Additional info for upgrade to 4.6C |