You must migrate metadata in this specific sequence to ensure a successful deployment.
You must migrate context definitions before any pricing procedures. If multiple pricing procedures are linked to various context definitions, include all associated definitions in the migration.
You must deploy all decision tables (DTs) before you migrate the pricing procedures that reference them.
Pricing recipe migration also migrates the associated default pricing procedure.
You must manually refresh decision tables after migration within the target environment to make sure that the data is updated and active. If a decision table migration encounters missing metadata, such as a custom field or element, the deployment fails.
You must manually update any pricing procedure constants that contain reference sandbox org IDs to the corresponding production org IDs. This step is required before migration to avoid logic failures in the production environment.
You must manually update the price adjustment schedule IDs in the pricing procedure constants of the production org before or after migration.
Subsequent Production Migrations
You must migrate context definitions before you migrate pricing procedures. If multiple pricing procedures are linked to various context definitions, then you must migrate all associated metadata to ensure system integrity.
You must migrate decision tables along with any relevant metadata changes. If a decision table migration fails, the system must roll back to the previous snapshot, making sure that the existing decision tables are usable.
You must migrate pricing procedures and expression set versions after the successful deployment of context definitions, decision tables, and pricing recipes in a sequential order.
j