SPELL_AMOUNT — Convert Numeric Amount to Spelled-Out Text

SPELL_AMOUNT takes a numeric amount together with a currency and a language and returns the amount spelled out as text, split into the whole-number portion and the decimal/currency portion. It relies on a customizing table that maps language and currency combinations to spelling rules (thousands, hundreds, decimal unit names, and so on). It is a classic, released function module, still shipped and callable in current releases, and remains the standard building block for check printing programs, promissory note text, and any legal document where regulations require the amount to be shown in words as well as figures. It performs no posting, no database update, and no locking; it is a pure text-generation utility that depends entirely on the spelling customizing being maintained for the language/currency pair being requested.

Only the parameters confirmed by the module's long-standing interface are listed below. Everything else in a calling program is local handling.

There are two exceptions and both must be treated as hard failures, not cosmetic ones.

Call the module with the exact document currency, not a hardcoded default, and pass the language actually required by the document's legal jurisdiction rather than assuming the logon language is correct. Both NOT_FOUND and TOO_LARGE must be caught explicitly and checked via sy-subrc; a generic OTHERS catch that logs and continues is not acceptable for anything that ends up printed as a legal amount. After the call, inspect IN_WORDS directly rather than trusting sy-subrc alone, because some malformed customizing entries can return a technically successful call with an incomplete or garbled text. If IN_WORDS is empty or partially empty, the calling program should stop document generation for that item and route it to manual handling instead of printing it.

SPELL_AMOUNT is unchanged in S/4HANA and continues to function exactly as it did in ECC; there has been no released successor or Fiori-based replacement for this specific text-spelling logic. It is not part of any clean-core released API list, so it should not be called directly from side-by-side extensions; existing on-stack check printing and payment media programs continue to use it as before. New clean-core developments needing spelled amounts typically have to reimplement the logic or wrap the call inside a released local interface, since there is no equivalent RAP-based or API-exposed service for this function today.

The failures below are the ones that actually reach production, usually surfacing only when a new country, currency, or high-value payment appears.

Ownership sits with whoever maintains check printing programs, payment media formats, or legal document text generation, usually FI or Treasury-aligned ABAP development. Functional consultants configuring payment forms depend on developers to confirm that the spelling customizing table has entries for every language/currency pair the company actually uses; Basis has no role here.

SPELL_AMOUNT depends on the spelling customizing table that maps language and currency to number-to-text rules, and indirectly on currency master data for decimal precision. It is most commonly called from payment medium and check printing programs and from SAPscript or Smart Forms layouts that render the legal 'amount in words' line on checks and formal payment instructions.