Hello and thank you for visiting my blog post on creating an exchange rate worklist. In this blog post, I’ll outline the requirements and workflow for this capability.



Instead of granting users full access through transaction OB08, you can allow users to edit certain exchange rates solely in the TCURR table by defining an exchange rate worklist. This is especially helpful for businesses where discounted/negotiated exchange rates are taken into account for some ad hoc transactions and centralised currency rates are updated on a timely basis. The most important task on this list is to update the TCURR (OB08) table, from which the system selects the exchange rate for the publishing of a cross-currency document.


The following functionality can only be implemented in two steps:

Step 1

  • General Settings -> Currencies -> SPRO -> IMG -> SAP NetWeaver Create a work list for entering exchange rates.

Name, text, and maintenance interval information for the worklist. Use the same worklist name as the exchange rate type whenever possible to make things simpler for the user.

Step 2

The following currencies should be added to the worklist so that users can update the exchange rates:

As many currency pairs as necessary should be included.

  • General Settings -> Currencies -> SPRO -> IMG -> SAP NetWeaver Put the Exchange Rate on the To-Do List.

Once this is completed, request from the security team the creation of a particular role for the transaction S B20 88000153 with the relevant worklist added to the role’s object. then incorporate the just formed role into each user’s profile.

Now, instruct the user to execute transaction S B20 88000153 so that the exchange rate in his worklist can be released and maintained. Only the currency pairs that were specified in Step 2 are displayed to the user here.

The system will update the following in OB08 once the rates are made public:


This is a highly helpful tool for lump-sum transactions where special currency rates must be taken into account, and it also aids organisations in limiting user access to the whole OB08 transaction.

I hope that my blog offers guidance and solutions for the issue at hand, and I hope that my fellow consultants will find it helpful in their support and development efforts.