3368782 - Runtime Errors SAPSQL_INVALID_TABLENAME when collecting the Financial Data Quality data in SAP Readiness Check Report 2.0

1. Job RC_COLLECT_ANALYSIS_DATA cancels with the following error:
   
   Error occurs with Financial Data Quality data collection job TMW_RC_FDQ_DATA_COLL.
   Job cancelled after system exception ERROR_MESSAGE 
   
2. Job TMW_RC_FDQ_DATA_COLL cancels with errors:
   
   Internal session terminated with runtime error SAPSQL_INVALID_TABLENAME (see ST22) 

The details of runtime error SAPSQL_INVALID_TABLENAME can be different. It's needed to check the detailed dump Error Analysis in transaction ST22. 

1. Dump one
   
   

   Runtime Errors         SAPSQL_INVALID_TABLENAME Exception              CX_SY_DYNAMIC_OSQL_SEMANTICS

   Error analysis     An exception occurred that is explained in detail below.     The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was not caught in     procedure "GET_MAX_RUNID" "(METHOD)", nor was it propagated by a RAISING clause.     Since the caller of the procedure could not have anticipated that the exception would occur,     the current program is terminated.     The reason for the exception is:     An invalid table name "FIN_AA_CORR_PACK" was specified in an Open SQL command:     Due to one of the following reasons, the error occurs only at runtime:     - the table name was specified dynamically, or     - the SELECT clause, WHERE clause, GROUP-BY clause, HAVING clause, or       ORDER-BY clause was specified dynamically.

   
   
   
2. Dump two
   
   

   Runtime Errors         SAPSQL_INVALID_TABLENAME Exception              CX_SY_DYNAMIC_OSQL_SEMANTICS

   Error analysis     An exception occurred that is explained in detail below.     The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was not caught in     procedure "GET_MAX_RUNID" "(METHOD)", nor was it propagated by a RAISING clause.     Since the caller of the procedure could not have anticipated that the exception would occur,     the current program is terminated.     The reason for the exception is:     An invalid table name "FIN_ML_CORR_PACK" was specified in an Open SQL command:     Due to one of the following reasons, the error occurs only at runtime:     - the table name was specified dynamically, or     - the SELECT clause, WHERE clause, GROUP-BY clause, HAVING clause, or       ORDER-BY clause was specified dynamically.

   
   
   
3. Dump three
   
   

   Category               ABAP programming error Runtime Errors         SAPSQL_PARSE_ERROR Except.                CX_SY_DYNAMIC_OSQL_SEMANTICS ABAP Program           CL_RC_FDQ_ML_MONITOR==========CP Application Component  SV-SMG-DVM

   Error analysis     An exception has occurred which is explained in more detail below. The     exception is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS' and was not      caught in procedure     "GET_MAX_RUNID" "(METHOD)", nor was it propagated by a RAISING clause.     Since the caller of the procedure could not have anticipated this     exception, the current program was terminated.     The reason for the exception is:     The current ABAP program attempted to execute an Open SQL statement     containing a dynamic entry. The parser returned the following error:     ""FIN_ML_CORR_PACK" is not defined in the ABAP Dictionary as a table,      projection view, or database view."

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

SAP ERP

ABAP program "CL_RC_FDQ_FI_AA_MONITOR=======CP" CX_SY_DYNAMIC_OSQL_SEMANTICS, GET_MAX_RUNID, RC_COLLECT_ANALYSIS_DATA, FIN_AA_CORR_PACK, FIN_ML_CORR_PACK , KBA , SV-SCS-S4R , SAP Readiness Check , CO-PC-ACT , Actual Costing , FIN-MIG-AA , Data migration for Asset Accounting , Problem