Symptom
When transporting SAPUI5 object changes or importing transport requests (e.g., Your transport like: <SYSTEMID>XXXXXX) into downstream target systems (such as Sandbox E5S, Quality, or Production), the transport import fails with Return Code RC=8.
- The STMS transport log reveals the following critical errors during the main import phase:
- Table /UI5/RREP_C is not in nametab
- inconsistency in the object definition UI5V (table /UI5/RREP_C_FILE)
- Table /UI5/RREP_C_FILE is not in nametab
- Table /UI5/RREP_C_LIB is not in nametab
- Additionally, users face various blocking messages during prerequisite handling in transaction SNOTE or SPAM:
- In SPAM, queue calculation fails with: "OCS Package SAPK-75805INSAPUI does not exist in the system".
- In SNOTE, Note 3599156 displays status "Completely implemented", yet tables /UI5/RREP_C* remain missing in transaction SE11.
- In SNOTE, uploading the .SAR file displays: "File 'k75800ocpsapui.sar' successfully transferred, decompressed, and then deleted", but no database tables are created.
Read more...
Environment
- S/4HANA 2023, 2025 and others
Product
Keywords
RREP_C, /UI5/RREP_C, /UI5/RREP_C_FILE, /UI5/RREP_C_LIB, 3599156, 3759028, TCI, Nametab, RC=8, SNOTE, SPAM, Upload TCI, SAPK-75805INSAPUI, K75800OCPSAPUI.SAR, K75801DCPSAPUI.SAR, SAP_UI 758 , KBA , CA-UI5-DLV , UI5 ABAP delivery tools , CA-UI5-ABA-SAR , UI5 App Infrastructure: SAPUI5 ABAP Repository , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview