(Glue 2402) Q: When creating SNP Glue™ extractor, some currency rules are automatically assigned to some fields. Why? What is happening in these rules?

In SAP, you create currency keys as part of your SAP customizing. You basically define which currencies exist, what are their abbreviations and what are the exchange rates between currencies. As part of the basic customizing of currency keys in SAP, you define how many decimal places each currency carries.

Going forward, when you use the currency keys for transactional data (e.g. purchase order), you and the SAP system use these currency keys along with value fields, e.g. the net amount of the purchased goods. However, one field on the database of your SAP ERP system may be used for any number of currency keys. To give you an example, purchasing for company code 1000 (and its associated purchasing organization) may be done in EUR, while another company code uses Vietnamese Dong. Obviously, the number of decimal places differs between these two currencies. The SAP system will store all amount values without a decimal place on the database. The SAP application then interprets the amount field based on an associated currency key. This makes the difference between "10.000,00" EUR and "100.000" Dong.

Now, when you want to use such data on external storage, you will want to normalize the amount fields. Then you don't need to program a routine or frontend application simply to make sense of the amount fields from SAP. SNP Glue™ supports you heavily by simplifying this. Our solution tries to automatically normalize currency amount fields by adjusting them to the maximum of 4 decimal places – without you needing to code, implement lookups or come up with a fancy frontend solution.