Solution : https://service.sap.com/sap/support/notes/309335 (SAP Service marketplace login required)
Summary :
After importing a transport, update terminations may occur due to inconsistencies among ABAP programs or between ABAP programs and DDIC elements. Various runtime errors such as CALL_FUNCTION_CONFLICT_TYPE, LOAD_COMMON_PART, among others, may manifest. These issues arise despite successful transport imports and error-free preliminary checks, typically because changes are imported into active systems, contravening standard practices. Solutions involve addressing specific errors following guidance from SAP Notes 144382, 162991, and 162166, and ensuring transports are imported during appropriate times or implementing alternative import strategies as per SAP Note 102069.
Key words :
- load_common_part- getwa_cant_clear- getwa_wrong_length- ddic_comp_cnt_inconsistent- conne_import_wrong_comp_type, additional key words update termination, inconsistent control table entries, update terminations occur due, describes update terminations, runtime errors occur, lis inbound interface, affect running programs, abap runtime error, abap/ddic generation
Related Notes :
| 544787 | PP-IS: Deadlocks during mass processing in R/3 or from APO |
| 339691 | LIS: V3 update terminates |
| 183654 | Missing update simulation/log and new setup |
| 162991 | Generation tools for ABAP programs |
| 150376 | Composite note: INVCO in Release 4.0B to 4.6B (October 2000) |
| 144382 | CALL_FUNCTION_CONFLICT_LENG |
| 131178 | PERFORM_NOT_FOUND in the update |
| 102069 | tp impsync: Documentation |
| 99507 | Update terminations after upgrade/client copy |