S/4 1909 conversion error during import: unknown logical table T399J

[jbuttjer1]

We're down to hopefully our last import issue during the downtime phase of an S/4 1909 conversion from ECC6. The table in question is reported as T399J. Maybe pertinent background: historically, it was a pooled table but was converted to a transparent table by SAP with an SP upgrade in ECC6.

We're looking for help on resolving this R3load error in the EU_CLONE_MIG_DT_RUN phase as seen in the log below.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Phase: EU_CLONE_MIG_DT_RUN
R3LOAD IMPORT ERRORS
Find the detailed log in MIGRATE_DT_00134_IMP.LOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A1 ECOV 001 Setting up structure conversion for 'TKUPA': 1 changed
A1 ECOV 001 Setting up structure conversion for 'TLMGB': 1 changed
A1 ECOV 001 Setting up structure conversion for 'TPAER': 3 added
A1 ECOV 001 Setting up structure conversion for 'TZK05': 1 changed
A1 ECOV 001 Setting up structure conversion for 'TZST': 1 added
A1EEIMP 008 Task failed with error: Unknown logical table 'T399J'
A1EEIMP 008 Current buffer row is 7874
A1EEIMP 008 (CNV) Data conversion failed
A3 ETSK 015 Throughput: 119.99 MB in 12 chunks, 15772.32 rows/sec, 15.52 MB/sec
A2EETSK 012 Finished import for object "ATAB" of type "table" with error in 7.73 sec #20210223121255

A1 EIMP 020 Table "TISSR_BAV_R5978" fully truncated.
A1 EGEN 002 ====================================================
A1 EDMP 009 Resource usage: GENERAL times: 7.906/ 1.441/ 0.107 93.6%/77.8%/67.9% real/usr/sys
A1 EDMP 009 Resource usage: PIPE times: 0.543/ 0.411/ 0.051 6.4%/22.2%/32.1% real/usr/sys
A1 EDMP 008 Memory usage: 41/15/0 MB buffer/objectcache/disk (1 reused buffers)
A1EEGEN 000 (PIP) Internal error: Got block DATA nr=25 len=10485120 udata=10160/1 - expected STARTTABLE
A1EEGEN 000 (IMP) Table name is 'TISSR_BAV_R5978'
A1EEGEN 026 Number of error(s): 1
1 ETP111 exit code : "12"

[jbuttjer1]

SAP provided an involved conditional solution via the message we opened for the problem we shared above. Good news is, we were able use the fixes without having to reset the conversion.

Upon passing the above error, we hit a different error that also required SAP help. SAP was adding us to a forthcoming Note (not released yet), so I interpret that to mean SAP has now had 2-3 customers (or more) report the same or very similar issues, which could be arising from the particular combination of ECC to S/4 conversion, with SUM 2.0 and SP09, and 1909 release. My theory is that SAP is only recently learning about these issues because most S/4 conversions (POC or real), with the 1909 release specifically (last in the same codeline before different codeline was introduced with 2020 release), were probably halted when the pandemic hit in March 2020.