Hi @boubcher, I think it's a typical case to which Dynamic Workflow can be applied effectively.
- Add an Excel reader to read the table which defines mapping rule between source feature type name and destination feature type name.
- Add a Geodatabase reader using the Single Merged Feature Type option, in order to read all the features from every table in the source dataset with a single reader feature type <All>. Expose "fme_feature_type" if it wasn't exposed automatically.
- Merge destination table name (Table_zone) to all features with a FeatureMerger using source feature type name as the join key. Alternatively the DatabaseJoiner could also be used here.
- Reproject the coordinate system for every feature.
- Write the features into a destination dataset with a dynamic writer feature type.


Just be aware the source feature types which would be combined into the same destination feature type should have the same schema definition (i.e. structure of user attributes and geometry type).
See also this article and some related articles to learn more about Dynamic Workflows.
Thanks Takashi
How can I combine in this process all the table with the same table name ?
Thanks Takashi
How can I combine in this process all the table with the same table name ?
Do you need to combine all the source tables into a single destination table?
I thought the destination table for each source table should be determined by the Excel table. For example, "AdminBoundaries_MadZ37/Governorates_MadZ37", "AdminBoundaries_tabZ37/Governorates_tabZ37", ... should be combined into "Governorates_37", and so on.
The dynamic workflow I posted does that automatically. That is, for each feature, the destination table would be determined by the value of "Table_zone", and the schema of each destination table would be configured according to the schema of a source feature type which would be determined by the value of "fme_feature_type".
Am I wrong?