3498894 - Connection Validation Error: Virtual Table Empty in Model Import - SAP Datasphere

When validation the connection in Datasphere, the Model Import feature shows error "Virtual table for importing metadata (CSN) is empty. For more information, please refer to SAP Note 3081998."

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

SAP Datasphere

1. Select the connection.
2. Click validate button.

The prerequisites of this feature are not meet. The CSN metadata is not provisioned in the source SAP S/4HANA on-premise system.

Follow "Provision of CSN metadata" part in SAP Note 3081998 - Metadata import of CSN entities from SAP S/4HANA, on-premise edition to SAP Datasphere Cloud - central initial note

=== Quote ===

• Proceed as follows to make the entities to be imported available in your SAP S/4HANA on-premise system for import into SAP Datasphere Cloud: 
   
  Report ESH_CSN_CDS_TO_CSN  
   
  Parameters: 
   
  
  • We recommend that you start the report for all available entities on your system:
    Do not set any filters in the "CDS" (entity name) and "Annotations" (filters for entities with specific annotations) fields.
    However, you can use these filters to subsequently load individual entities at a later point in time.   
     
  • If you use only English on your SAP Datasphere tenant and do not want to load any other language, you can set the "Consider Texts in English only" indicator. Otherwise leave this field blank. In this case, I18N files in all languages are made available for import into SAP Datasphere.
      
  • The report has a test mode.
    (You normally do not need to execute it in test mode first.)   
   
  Since the report may run for some time depending on the data volume, we recommend that you schedule it in the background. 
  (If there is a large number of entities to be processed, the report also asks you whether you really want to execute it in dialog mode when you start it in the dialog process. In this case, choose "No" and schedule the report in the background instead.) 
   
• After you have executed the report, you can check the search again in transaction ESH_TEST_SEARCH:
  The search connector CD$ALL~CSNEXPCDSDEF~ (or <SYS>ALL~CSNEXPCDSDEF) should now find all prepared entities for import. 
   
• You can use the report ESH_CSN_DISPLAY_CSN to display the formatted CSN content of each entity (source file and I18N file).

=== End Quote ===

SAP Note 3081998 - Metadata import of CSN entities from SAP S/4HANA, on-premise edition to SAP Datasphere Cloud - central initial note

Model Import, Datasphere , KBA , DS-MD-ESH , Repository Explorer , DS-DI-CON , Connections , Problem