The existing implementation of SAP Treasury in SAP BW is to be changed over from movement type to update type. The way that key figures are formed is to be made more transparent and flexible. New update types should also be monitored and new requirements from the specialist departments be taken into account.
Supplement
SAP Treasury was implemented at a time when there were no corresponding structures on the Business Content side. The transaction type was a crucial supporting criteria for defining key figures then. With the changeover of the old Treasury solution to the transaction manager in R/3, no adjustments were made on the BW side; instead, data extraction by Business Content's data source was changed so that the data continued to be sent to BW with transaction types. Over the course of time, this solution proved to be increasingly inefficient, so a changeover of the BW Treasury implementation to the transaction manager's update types was initiated. At the same time, the aim was to increase the system's transparency. All of this had to be done without disrupting the existing production environment; in other words, some of the existing reports had to continue to be useable.
Subject description
The changeover from CFM (R/3) to TRM (ECC 6.0) has replaced transaction types with update types. Update types are more finely segmented; one effect of this is that it is no longer easy to functionally compare the two. Update types or transaction types occur in every single posting in FI/TRM and can simultaneously supply various different key figures with the data. The functional aims of the project included separating out redundant update types and classifying key figures more finely and tidily in order to ensure better transparency when creating queries. This included a precise business definition of all key figures and update types in the company.