Enabling multicurrency is a significant, irreversible change in a Salesforce org. Before this feature is enabled, currency-specific fields, such as the CurrencyIsoCode field required for multicurrency pricing, are not available for configuration in components like decision tables. The correct and safest procedure is to first deactivate any active automation, such as the pricing procedure, that will be affected. After deactivation, enable multicurrency. This action makes the Currency field available. The consultant must then explicitly modify the decision table to include the Currency field as an input column. Once the table is updated and saved, the pricing procedure can be safely reactivated.

A. Cloning the procedure and creating a new table before enabling multicurrency is incorrect because the Currency field will still be unavailable for selection in the new decision table.

C. Enabling multicurrency while the pricing procedure is active is risky and can lead to processing errors. This option also omits the necessary step of manually adding the Currency field to the decision table's configuration.

1. Salesforce Help, "Enable Multiple Currencies": This document outlines the process and implications of enabling multicurrency. It emphasizes that this is a foundational change. While it doesn't directly mention pricing procedures, the standard best practice for any major org change is to disable related automation to prevent errors during the transition. The enablement step is what makes currency fields available throughout the org. (Reference: Salesforce Help Portal, search for "Enable Multiple Currencies" and "Considerations for Enabling Multiple Currencies").

2. Salesforce Help, "Create a Decision Table for Pricing": The documentation for creating decision tables details the process of selecting input and output columns. It implicitly confirms that only available fields can be selected. The Currency field (CurrencyIsoCode) is only available for selection after multicurrency has been enabled at the org level. The procedure to modify an existing table would be to deactivate dependent processes, edit the table structure, and then reactivate. (Reference: Salesforce Help Portal, search for "Create a Decision Table for Pricing").

3. Salesforce Architects, "Record-Triggered Automation": This guide on architecting automation solutions reinforces the principle of deactivating active automation before making underlying data model or configuration changes. It states, "When deploying changes to production, it’s a good idea to deactivate any relevant validation rules, triggers, and workflow rules before you begin your data load..." The same principle applies to enabling a feature as significant as multicurrency which impacts pricing procedures. (Reference: architect.salesforce.com, "Record-Triggered Automation Guide", section on Deployment Considerations).