Expiring Currencies

Scope of Functions

You can use this new function to allow currencies to expire. This means that you can attach warning or error messages to the creation/change of objects in these currencies.
You can use this function, for example, for the currencies participating in the European Monetary Union that then lose their validity after the end of the dual currency phase. Here you can set a date for a warning or error message for the creation/change of longer running objects, e.g. sales orders. This means that you can prevent objects in these expiring currencies being created/changed after the end of the dual currency phase.
Another possible application of this function is for the expiry of currencies in high inflation countries.

Effects on Customizing

In the Implementation Guide (IMG) there is a new IMG node under General Settings -> Currencies:

Expiring currencies

This node contains the following three Customizing activities:

Define expiry reasons

Define expiring currencies

Define warning and error dates

These are optional activities.

Example of expiring currency participating in the EMU:

The Austrian Schilling loses its validity at the end of the dual currency phase. You want to prevent any objects being created/changed in this currency leading up to or after the close of the dual currency phase. You define an expiry reason, e.g. the euro (1 IMG node) and assign this expiry reason ATS as the currency and the euro as the subsequent currency (2 IMG activity). Then you define, according to your requirements, e.g. 01.01.2002 as a warning date and 06.30.2002 as the error date for the object types made available by SAP. For company code dependent objects you can restrict the check by company code. When a user then wants to create/change an object in ATS from the 01.01.2002 a warning message and from the 06.30.2002 an error message will appear for the assigned object types and company codes.