3650199 - Warning "No split conditions for 'xxxx' - ignore splitting!" happened during SUM DMO migration

During the SUM DMO migration process, table splitting of some tables were skipped even the tables have been configured in EUCLONEDEFS_ADD.LST, and result in longer runtime than expected.

Check EUMIGRATEDTPRP_ORG.LOG, below records can be found for the table:

4WETQ399 No split conditions for 'LTEX' - ignore splitting!

in TABSPLITCALL_ORG.SAV the detailed error message for this table has been recorded: 

EXECUTING <path>\SUM\abap\bin\SAPuptool.EXE splittable "table=LTEX" "segmentsize=0.022727" "count=estimate" filternonascii "table_suffix=~" "wherefile=<path>\SUM\abap\load\migrate_dt\LTEX_030_SPLIT.WHR"
2 ETQ399 Connecting to database 'mss'.
4 ETQ010 Date & Time: 20250811050319
2 ETQ399 Using 10 key fields for "LTEX": "MANDT" "RELID" "REPORT" "HANDLE" "LOG_GROUP" "USERNAME" "EXNAME" "TYPE" "DISVARIANT" "SRTF2"
2WETQ399 Only using 6 key fields!
2 ETQ399 LTEX: estimated 474369 entries. Using segment size of 0.022727, minimum splits limited to 11, maximum splits limited to 176
2 ETQ399 Using equidistant row number method to split table.
4WETQ399 Filter empty split position in field #4 to avoid non portable boundary with single space.
3WETQ399 No split positions left after filtering non-ASCII characters - giving up!
1 ETQ399 Wrote to where file '<path>\SUM\abap\load\migrate_dt\LTEX_030_SPLIT.WHR' 0 condition clauses.
4 ETQ010 Date & Time: 20250811050848
1 ETQ003 exit code: "0"

*Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• Upgrade tools for ABAP

SUM DMO, table splitting failure, non-ASCII characters, EUCLONEDEFS_ADD.LST, TABSPLITCALL_ORG.SAV, manual table splitting, key fields, SAP upgrade tools for ABAP, No split conditions, ignore splitting , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , Problem