Keys and Relationships

Archiving configuration data that is based on user-defined keys can be problematic. Since configuration tables' keys are user-defined (not system-generated), they do not have associated key tables. This means that if you archive configuration data, the system does not validate that the key has been used once it has been moved to an archive environment's database.

Fastpath: For more information on how data based on system-generated keys vs. data based on user-defined keys is handled during an archive, refer to Step 4: Move or Delete Production Data.
CAUTION:
It is possible to contort the archive and purge processes to introduce problems in an archive environment. Let's say that you archived bills with bill calculation headers that referenced a rate version, and then you purged that rate version from production. The archive environment would not have access to the rate version needed to view those archived bills.