Currency and Decimal Places in SAP
The number of decimal places varies for currencies. Currencies which do not have two decimal places must be defined in SAP in table TCURX (decimal places for currency codes).
You can maintain this table in the IMG as follows: SAP Customizing Implementation Guide–>SAP NetWeaver–>General Settings–>Currencies–>Set Decimal Places for Currencies. (Transaction code Oy04)
Never delete a currency or change the decimal place value of a currency in SAP.
Some common Customizing settings for table TCURX:
ISO Currency Decimal places
Code
————————————————————————
ADP Andoran Peseta 0
AFA Afghani Afghani 0
BEF Belgian franc 0
BHD Bahraini dinar 3
BIF Burundi franc 0
BYB Belorussian rubel (old) 0
BYR Belorussian rubel (new) 0
CLP Chilean peso 0
COP Columbian peso 0
DEM3 (Internal) German Mark (3 Dec.) 3
DJF Djibouti franc 0
ECS Ecuadorian sucre 0
ESP Spanish peseta 0
GNF Guinea franc 0
GRD Greek drachma 0
HUF Hungarian forint 0
IDR Indonesian rupiah 0
IQD Iraqui dinar 3
ITL Italian lira 0
JOD Jordan dinar 3
JPY Japanese yen 0
KMF Comoros franc 0
KRW South Korean won 0
KWD Kuwaiti dinar 3
LAK Laos new kip 0
LUF Luxembourg franc 0
LYD Libyan dinar 3
MGF Madagascan franc 0
MZM Mozambique metical 0
OMR Omani rial 3
PTE Portugese escudo 0
PYG Paraguay guarani 0
ROL Roumanian Lei 0
RWF Rwanda franc 0
TJR Tadzhikistani rubel 0
TMM Turkmenistani manat 0
TND Tunesian dinar 3
TPE Timor escudo 0
TRL Turkish lira 0
TWD New Taiwan dollar 0
UGX Uganda shilling 0
USDN (Internal) US Dollar (5 dec.pl.) 5
VND Vietnamese dong 0
VUV Vanuata vatu 0
XAF CFA Franc BEAC 0
XOF CFA Franc BCEAO 0
XPF CFP Franc 0
The contents of this table is only delivered with new installations of SAP and never upgraded.
For upgrade installations, new or changed contents of Table TCURX are not delivered.
Currency codes and decimal places for currency codes are defined in ISO standard 4217. For the specification of decimal places for currency codes, SAP uses this ISO standard.
Spool – Output
The output controller – Spool Request Selection Screen can be used in transaction code SP01.
This will give you spool requests and output requests by system.
If you wish to limit a user access to their own individual spool requests you can give them access to SP02.
If you wish to completely control the spool and output functionality of a system you can use the administration transaction SPAD (or additionally transaction SPAT.)
When working with output/messages you can access the objects message status in table NAST.
If you are looking for a simple single table overview of all output/message condition types which have a condition record you can use table NACH. (This will give you the Condition Type+Access Sequence Table+Application+Partner function and a variable key which will show you the key fields for the access sequence table.)
CRM BDoc Monitor
Great information on the use of SMW01/SMW02:
Transactions: SMW01 / SMW02
Menu path:
CRM 4.0/5.0: Architecture and Technology –> Middleware –> Monitoring –> Message Flow
–> Display BDoc Messages / Display BDoc Messages Summary
SMW01 has the following features:
SAP Tips – Trouble Shooting Issues in HTTP Content Repository in SAP CRM
To troubleshoot issues in the HTTP content repository associated with SAP CRM Read more 
CRM – User menu
Tip - Sometimes you may wish a user to login to a specific area menu or transaction code. This can be easily done by assigning the area menu or transaction code to the user profile. To set the user start menu in CRM to CRM_MENU, assign the start menu to the users profile in SU01.
Smartforms – upload/download
Scenario - you have a smartform in a system and need to move it to another system and for some reason cannot get there with a transport path. Do you know that you can download a Smartform as an XML file to your desktop and then re-upload the smartform in your new system. This will copy the entire form, all logic as well as the global settings and pages and windows. This is especially useful for copying smartforms from ERP to CRM or visa versa. (obviously you will need to adapt a lot of extensive logic when delaing with CRM and ERP (due to different source tables/fields/variables etc. but you may save some time).
To do this use Read more
CRM – Bdoc Analysis Guide
Characters not displayed correctly
Q – We have a CRM system which has cyrillic characters displayed in the address fields. When the data is transferred to our ERP system, the field contents are displayed in ERP as ###. But the user can over-write the ### with the cyrillic characters, why does this happen and how can it be fixed.
A – Generally the symbol # is used for a character conversion error. The problem is not the CRM system or the ERP system, both can handle your Unicode characters, the problem is in the RFC connection between the systems. Go to SM59 and select your RFC connection between ERP and CRM and select special options, then ensure both systems are using Unicode and your RFC server uses unicode as well.
