SAP Core | SAP core functionalities and technologies
SAP Treasury system preparation
By default, SAP Treasury and Risk Management may not be active in your system. In this case you will not see the SAP Treasury related menus in the SAP Easy Access or SAP Customizing menus (under the parent node Financial Supply Chain Management).
In such situation, you must first activate the business extension Financial Services (EA-FS) using the Switch Framework. Basically this operation will activate some code and interface elements that are already present in the system but not executed so far due to the switch being turned off.
This operation can be carried out using transaction SFW5. However some prerequisites are required. You should review at least following OSS notes before proceeding:
- Note 532670 – Activating the R/3 Enterprise Extension EA-FS
- Note 535003 – SAP R/3 Enterprise Extension Set 1.10: Activation switch
- Note 588364 – Prerequisites for activating extensions
- Note 538887 – SAP R/3 Enterprise 47×110: Software architecture/maintenance
- Note 598937 – Termination w/ error for inactive indicator EA-FINSERV
Note 588364 is particularly important since it specifies that the client role should be set as ‘Test’ instead of ‘Production’ (transaction SCC4) while activating the extension.
Note that this activation is cross-clients and it does not require the execution of SGEN afterwards.
Before starting the implementation of SAP Treasury, it may be wise as well to check the support package and/or enhancement package the ERP is running on and identify the need for more recent packages. SAP Treasury functionalities are regularly enhanced as enhancement packs are delivered. However there is not always a need to install the latest enhancement packs as ECC6 without any enhancement packs already offers a lot of functionalities treasury wise. It must be noted that while activating Financial Services (EA-FS) is a low cost operation (with a very low risk of impact on the existing ERP implementation), installing enhancement packs may turn out to be a much more costly operation involving non-regression testing.
From my own experience, it is not a good idea to bind the implementation of SAP Treasury to the implementation of enhancement packs and to try to deliver both activities within one single project. If a specific level of enhancement packs is absolutely required, their installation should be considered as a prerequisite project in itself. A SAP Treasury implementation project is already complex enough by itself not to add additional technical and planning constraints.
Initial Treasury customizing
You might encounter the situation where no initial standard SAP Treasury customizing is available in your customizing client. It doesn’t mean you have to start it from scratch because such customizing is in fact delivered by SAP but in the reference client 000. So before starting to implement SAP Treasury, you might want to “copy” this reference customizing from the client 000 into your customizing client. The safest way to proceed is to go into each of the relevant customizing activities for your implementation and to perform a customizing adjustment (this functionality can be found in the Utilities menu of any customizing transaction).
Once the reference customizing is present in your customizing client, you have a sound foundation to start elaborating your own implementation modifying the required settings to match your specific requirements.