Which is the following base table that would get populated after using the sample .ifb file
-
S_PROD_INT
-
EIM_PROD_INT
-
S_PROD
-
S_PARTY
When using EIM (Enterprise Integration Manager) with a .ifb file, data is first loaded into interface tables (S_*_INT pattern). The base table S_PROD_INT would be populated with the imported product data before being processed into the target base table S_PROD. EIM tables are temporary, S_PROD_INT is an interface table, and S_PARTY is unrelated.
Running a sample .ifb (interface file bootstrap) file through Siebel EIM loads data from a flat file into the corresponding EIM staging table (e.g., EIM_PROD_INT) and then, on a subsequent EIM Import process, populates the actual base table — in this case S_PROD_INT (the product interface base table). EIM_PROD_INT is the staging/interface table itself, not the base table populated as a result. S_PROD and S_PARTY are unrelated base tables for different entities. So S_PROD_INT is correct as the target base table for this specific sample interface.