Why would you use the ONLY BASE TABLES parameter in your EIM configuration files?
-
To eliminate duplicate data
-
To verify import success
-
To speed up processing
-
To truncate EIM tables after import
The ONLY BASE TABLES parameter in EIM configuration files tells EIM to process only base tables and skip intersection tables during import. This speeds up processing because EIM doesn't have to process the many-to-many intersection table mappings - it directly populates the base tables. It's a performance optimization parameter, not related to duplicate handling, verification, or truncation. By reducing the number of table operations, import jobs complete faster when this parameter is used appropriately.
The ONLY BASE TABLES parameter in an EIM (Enterprise Integration Manager) configuration file restricts the import/export/merge/delete process to work directly against the base tables only, skipping the normal (much heavier) processing against interface-table staging/validation steps that aren't needed for a given run. Since a large share of EIM's runtime cost comes from validating and processing interface-table rows against all the associated base-table columns, limiting scope to just the base tables in play significantly speeds up processing — that's the documented reason to use this parameter, not deduplication, verifying success, or truncating tables (which are separate, unrelated EIM behaviors/parameters).