Customizing Freeze
Customizing Freeze initiates a phase during which Customizing changes as well as many Finance and Controlling activities are no longer possible.
The Customizing Freeze starts once the production system is copied to the sandbox to prepare the final Finance Customizing transport. From this point in time, the Finance Customizing must not be changed in the production landscape. New Finance and Controlling-related Customizing such as new company codes would require additional Finance Customizing for the conversion. In order to get the Finance Customizing request, the sandbox run must be repeated in this case.
The Hard Freeze starts during the uptime execution for the Software Update Manager. It comes
with additional restrictions that are listed in section Downtime and Business
Restrictions and in SAP Note 3211805 
.
The following tables display which Finance and Controlling activities are restricted or not possible (create, change, delete), once the Customizing Freeze has started:
Finance
-
Organizational Structure
Object Create Change Delete Details Company Code No No No The conversion can be stopped because of missing Customizig that was not identified in previous test conversions. Settings which are not compatible with New General Ledger can create inconsistencies.
Company Code Address Yes Yes No A deletion will cause inconsistencies in Customizing. Company Code Global Parameter No No No Very critical settings for the migration of line items from BSEG to ACDOCA
Posting Period No No No Very critical settings for the migration of line items from BSEG to ACDOCA Fiscal Year Variant No No No Very critical settings for the migration of line items from BSEG to ACDOCA Chart of Accounts No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Segment Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated Functional Area Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated Business Area Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated Trading Partner Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated Currency No No No A change of the currency setting will cause inconcistencies in BSEG and are not tested during the test conversions Chart of Accounts Assignment to CC No No No The change will cause inconsistencies in BSEG which will stop the MIG-Cockpit during the data conversion Company Code Assignment to Fiscal Year No No No The change will cause inconsistencies in BSEG which will stop the MIG-Cockpit during the data conversion -
Master Data
Object Create Change Delete Details General Ledger Account Description Yes Yes Yes Not relevant for migration Profit Center Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Please consider that also the historical data will be migrated General Ledger Account Control Data No No No The change of control data will cause inconsistencies in master data and BSEG and stop the MIG-Cockpit General Ledger Account (description, bank details, interest calculation)
Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated Reconciliation Account Yes No No A change or deletion of Reconciliation accounts for Fixed Assets and Materials could cause additional unexpected error messages during migration. Reconciliation accounts for customer/vendor are not technically used during migration, but a change of these might cause unexpected errors in preparation activities (SAPF190 or TFC_COMPARE_VZ). Open Item Managed Account Yes Yes No A change or deletion of open item managed accounts, or of the property <open item managed>, will cause inconsistencies in Master Data and Transactional Data tables. -
General Ledger
Object Create Change Delete Details Payment Terms Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated. Tax settings (Withholding Tax, electronic VAT Report, Tax Code)
Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated. Account Determination Yes Maybe No The migration cannot be executed if a value from source system is not existing in the target system. Please consider that also the historical data will be migrated. A changed account determination that is used for ML or FI-AA postings during migration can lead to errors if it hasn't been tested before (transactions OBYC and AO90). Changes to the CO default account assignment (OKB9) are not critical. Document Types Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated. Number Ranges Yes Maybe No The migration cannot be executed if a value from source system is not existing in the target system. Please consider that also the historical data will be migrated.
A change of the current number of a used number range can be critical.
Field Status Group Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated. Foreign Currency Valuation No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Custom Fields No No No The migration cannot be executed correctly if you have custom fields for which customizing was not performed Data Migration Balances (P&L, BS) No No No High risk that during data migration (via idoc, database migration tools) new inconsistencies will be created in database -
Asset Accounting
Object Create Change Delete Details Chart of Depreciation No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Depreciation Area No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Document Types Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated Number Ranges Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated Chart of Depreciation assignment to CC No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Asset Class Yes No No Very high risk that a made setting can be incompatible with the New Asset Accounting and New General Ledger. Creation of new asset classes is not critical unless they are already being used. Account Determination No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Integration with General Ledger No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Depreciation Calculation Rules No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Currency No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger Data Migration - Asset Values No No No Very high risk for a made setting to be incompatible with the New Asset Accounting and New General Ledger -
Bank Accounting
Object Create Change Delete Details Bank Accounts Yes Maybe Maybe Typical changes are not critical for migration. Additionally, there is an option to start the migration of house bank accounts after the technical upgrade from IMG.. For more information, see IMG Activity Switch Migration Program for House Bank Accounts, Tx SM30 FCML_BAM_MIGCONF House Banks Yes Maybe Maybe Typical changes are not critical for migration. Additionally, there is an option to start the migration of house bank accounts after the technical upgrade from IMG.. For more information, see IMG Activity Switch Migration Program for House Bank Accounts, Tx SM30 FCML_BAM_MIGCONF Payment Files Yes Yes Yes Not relevant for migration Payment Methods Yes Yes Yes Not relevant for migration Forms Yes Yes Yes Not relevant for migration Electronic Bank Statement Yes Yes Yes Not relevant for migration Payment Run Yes Yes Yes Not relevant for migration Payment Advice Yes Yes Yes Not relevant for migration Dunning Yes Yes Yes Not relevant for migration -
Accoun Payables or Account Receivables
Object Create Change Delete Details Forms Yes Yes Yes Not relevant for migration Enjoy Transactions Yes Yes Yes Not relevant for migration SD/MM Account Determination Yes Yes Yes Not relevant for migration Regrouping Yes Yes Yes Not relevant for migration Dunning Yes Yes Yes Not relevant for migration
Controlling
-
Organizational Structure
Object Create Change Delete Details CC Assignment to Controlling Area No No No A change causes inconsistencies in BSEG which will stop the MIG-Cockpit during the data conversion Currency No No No A change of the currency setting causes inconcistencies in BSEG and are not tested during the test conversions. Ledger for CO Versions No No No A change causes inconsistencies in BSEG which will stop the MIG-Cockpit during the data conversion Profitability Analysis No No No A change causes inconsistencies in BSEG which will stop the MIG-Cockpit during the data conversion Operating Concern No No No A change causes inconsistencies in BSEG which will stop the MIG-Cockpit during the data conversion Controlling Area No No No A change causes inconsistencies in BSEG which will stop the MIG-Cockpit during the data conversion -
Master Data
Object Create Change Delete Details Cost Center Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated. Internal Order Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated. WBS Elements Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated. Cost Elements Yes Yes No The migration cannot be executed if a value from source system is not existing in the target system. Consider that also the historical data will be migrated. -
General Controlling
Object Create Change Delete Details Custom Fields No No No The migration cannot be executed correctly if you have custom fields for which customizing was not performed Profitability Segments No No No You must not change the operating concern structure in Tx KEA0. If you already use account-based CO-PA you must not run correction reports that update profitability segments in the CE4* tables Operating Concern No No No The settings on operating concern should be the same between source and target system (or you will data inconsistancies) Profitability Analysis Maybe Maybe Maybe Changes to settings like derivation rules are not critical for migration. But be careful if such settings are usually maintained in production. IMG activity Transport operating concern((Tx KE3I) is part of Preparations and Customizing for Conrolling - make sure to transport basic settings only to not overwrite derivation rules or other settings in production accidentally. -
Material Ledger
Object Create Change Delete Details Material Ledger and Valuation Settings No No No The conversion can be stopped because of missing Customizing that was not identified in previous test conversions. Settings may not be compatible with Material Ledger. New inconsistencies might be created in database because of missing Customizing. Valuation Area / Plants Maybe No No The conversion can be stopped because of missing Customizing that was not identified in previous test conversions. Settings may not be compatible with Material Ledger. New inconsistencies might be created in database because of missing Customizing. It is technically possible, however, to create missing customizing in the temporary instance using the IMG activities decribed under Preparation and Migration of Customizing for Material Ledger Valuation Level No No No The conversion can be stopped because of missing Customizing that was not identified in previous test conversions. Settings may not be compatible with Material Ledger. New inconsistencies might be created in database because of missing Customizing. -
Product Cost Controlling
Object Create Change Delete Details Cost Component Structure No No No Cost Component Structure must not be changed. Assigning new cost elements to existing cost component structure is always critical and not recommended at all.