Skip to main content

Datasource "Import All" to be enabled for SAP systems

Syniti Knowledge PlatformMigrate

Now that the list of scanned tables is limited with the new cloud scanners, the flag “Import All” for SAP system data sources should be enabled in Migrate.

Currently the maintenance of the Application tables is challenging (no bulk actions, no ability to filter by active).

Posted by Ana Garcia Rubio (Syniti) ·
Status: Planned3 comments

Log in to comment and vote

Comments3

  • John Munkberg

    Team•

    Jun 27, 2025

    Hi Ana, the goals of Migrate Snapshot Management and the broader “Catalog” list of tables are not always the same, hence today there is a hard-coded list of Catalog Tables (about 2000+ SAP tables), and a different list of Migrate Tables in Admin / Application Tables.

    Long term, the goal is to expose the Catalog list of tables in the same way (Application Type / Tables) and not have this hard coded into the product. It should be configurable, very similar to Migrate.

    But was also are working on our journey to move all our components to be full Cloud Native, and continue the consolidation of the UI. This means moving many of the Migrate features into the Catalog so we don’t have redundant screens ( Migrate Datasources / Catalog Datastores, Migrate Snapshot Management / Replicate, Migrate Application Tables / Catalog Application Tables, etc).

    So we are hesitant to spend too much time improving what we hope to eliminate - but short term I certainly understand your issue.

    I can easily keep the two lists in Synch. If we have 2000 tables in the Catalog, we can put those same 2000 tables in the Migrate Application Tables. But my fear is we don’t typically need 2000 tables in Migrate to run a project. So while our scanner today brings in LOTS of tables, check tables, etc for general catalog purposes, Migrate should be focusing on just those tables in scope for the Data Migration.

    Open to feedback here, but if we blindly just “Import All” tables from the catalog - we would get 2000+ SAP tables, or for older scanned system - potentially 150,000 SAP tables - which would be a huge waste of time and space in Migrate.

    I do agree that we can make maintaining that list of Application tables easier - so I’ll make that request to engineering. But honestly I’d rather limp along (which is easy for me to say from my chair :-) ) and focus the effort in improving the System Datastores / System Application Tables - and then maybe we just add a flag there to identify which tables are relevant for Data Migration?

    • John Sanders

      •

      Jul 11, 2025

      @John Munkberg We supplied an API to the Solution Architects team to be able to manage Application tables in Migrate. Wondering if that would be helpful.

  • Ana Garcia Rubio (Syniti)

    •

    May 29, 2025

    Add the option to download the template with the current tables.