Key conditions for object upgrades

The following conditions apply to the upgrade of objects.

General rules:

• Most object updates are performed in correction mode.

• The iteration indicator (in the element object navigator) is updated in update mode, using the effective date defined in the process configuration parameter.

• All formula changes during the upgrade are applied in correction mode.

Object	Conditions
Balance Feeds	Input values must be created before balance feeds are defined.
Balance Types	No specific conditions, unless the dependent object already exists.
Calculation Card Components	These are upgraded to link component detail flexfields with calculation components: CIR Comp Flex CIR Comp Flex Usages CIR Comp Flex Relationships
Calculation Card Override Usages	No specific conditions.
Calculation Unit	No specific conditions.
Defined Balances	No specific conditions.
Element Eligibility Input Values	Input values must be created before adding eligibility input values.
Element Entries	Entries are created for all date-effective records for new input values.
Fast Formulas	Depends on the selected Formula Upgrade Option value.
Formula Results	No specific conditions, unless the dependent object already exists.
Input Values	The following validations apply: The element must not be retro-enabled. Input value must not be marked as required. Input value must not have default values. Default at runtime must not be enabled. Duplicate input values (same name) must not be created. If enabled for Database Items (DBI), ensure the DBI is created. Special purpose value must not duplicate existing values within the same element. Note: The above validations (retro, required, default values, and default at runtime) don't apply to Pretax elements, as they're required for enabling iteration functionality. These validations remain applicable for all other classifications.
Status Processing Rules	No specific conditions, unless the dependent object already exists.