The job uses the following naming convention to create entities:

<prefix>_<entity number>_<suffix>

The job generates the entity number in sequential order. For example, if you use

Finance

for the prefix, the job generates

Finance_1

for the first entity,

Finance_2

as the second entity, and so on. The job uses the meta schema ID and the meta table ID to determine the order in which it adds tables to the entity.

The number of entities the job creates depends on the parameters that you provide. You specify the number of tables in each entity, the prefix and suffix for the entity name, and whether you want to add tables from more than one schema.

The best practice is to create one entity for every 200 tables in the application. The job can create entities with up to 999 tables in each entity. By default, if the retirement application contains multiple schemas, the job creates an entity with tables from more than one schema. An entity can have tables from multiple schemas if the maximum number of tables in an entity exceeds the amount of tables in the first schema. For example, the application has two schemas with 150 tables in each schema. You configure the job to create 200 tables in each entity. The job uses 150 tables from the first schema and then 50 tables from the second schema to create the first entity.

If you do not want to combine tables from multiple schemas in one entity, you can disable this feature. In the example above, the job creates two entities. The first entity includes 150 tables from the first schema. The second entity includes 150 tables from the second schema.