By default, the job inserts default entity steps. However, only the Insert into Archive Tables step is enabled. The Insert into Archive Tables step determines from where the retirement job reads data for tables in the entity. By default, the step reads data directly from the database. SAP applications includes special tables that the retirement job cannot read directly from the database. The job cannot read data directly from the database for pool and cluster tables and any tables that have archived data in ADK files. The tables require a additional procedure for the Insert into Archive Tables step.

In addition, the retirement job may need to read data from the same table from multiples sources. SAP tables can store data in both the database and in archived ADK files in an external file system. For a table that has data in the database and in ADK files, the table is included in two separate entities. Separate entities are required because entities can only use one source to read data from. One entity reads data from the database. The other entity reads data from the ADK files in the external file system. Although the retirement job uses two entities to read data for the same table, the table data is consolidated when the Data Vault Loader job loads the data in to the Data Vault. You only see one table in the Data Vault.

The job uses the following naming convention to create the entities for SAP applications:

<Prefix>_<Entity Number>_<Suffix>_<SAP-Specific Suffix>

The following table describes the parameters in the naming convention:

Parameter	Description
Prefix	User-defined entry in the job parameters.
Entity Number	Job-defined entry.
Suffix	User-defined entry in the job parameters.
SAP-Specific Suffix	Job-defined entry. The job appends the following SAP-specific suffixes: _SAP . For entities that include pool and cluster tables. _SAP_ADK . For entities that include tables with archived data.