R/3 stores G/L account numbers differently depending on whether they are stored internally or externally. This can cause problems when a user searches for G/L account data using transactions SE16 or SE17. The author explains conversion exits and their implications and also provides tips for user-friendly G/L account searches.
A conversion exit is a piece of ABAP code that translates data from an internal to an external format and vice versa. R/3 uses conversion exits to ensure consistent sorting and storage of data across multiple databases and languages. Conversion exit ALPHA is used for G/L accounts, cost elements, cost centers, asset numbers, customer numbers, vendor numbers, and other business objects.
Often, the way that R/3 stores data differs from the user's expectation of how data should appear. This difference can cause a lot of confusion to users, especially when they search for data.
Let's consider users who run a report for a range of G/L accounts: They want to select all of the loan accounts in the 140000 range using report RFSSLD00, G/L account balances. When they enter the range 140000 to 149999, they get all of the accounts they want (Figures 1 and 2). However, if they use the pattern 14*, then they find nothing (Figure 3).
RFSSLD00 selection with a G/L account range