CONVERSION_EXIT_ALPHA_INPUT — ALPHA Conversion Exit for Numeric Key Fields

CONVERSION_EXIT_ALPHA_INPUT implements the ALPHA conversion routine assigned to domains such as MATNR, KUNNR, LIFNR or BELNR. Its job is to take a value as a user or an external system would type it, typically a plain digit string without leading zeros, and produce the padded, fixed-length internal representation that the database actually stores. ABAP triggers it automatically whenever a value is moved into a field whose domain carries the ALPHA conversion exit, for example on a selection screen or a dynpro input field. It is released for customer use and is commonly called explicitly whenever the automatic conversion does not fire, such as building a WHERE clause dynamically, preparing a BAPI or RFC-enabled function module parameter, or comparing a raw external key against an internal table field.

The interface is deliberately minimal.

This function module declares no exceptions in its interface. There is no EXCEPTIONS list to raise and no SY-SUBRC set by the call itself, so wrapping it in error handling or checking the return code afterward accomplishes nothing and often hides a stale SY-SUBRC value left over from an earlier statement. The real failure mode is not an exception being swallowed, it is a length mismatch being swallowed. If the OUTPUT variable is declared shorter than the target field's domain length, the padding is wrong and the resulting key never matches what is stored in the database, with no error surfaced anywhere. If INPUT contains non-numeric characters, the routine generally passes the value through with minimal or no padding, which looks harmless in a debugger but produces a key that will never match a purely numeric stored value.

Call it directly with CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT' EXPORTING input equal to the raw external value, IMPORTING output into a variable declared with exactly the same type and length as the target field, for example a variable typed against MATNR rather than a generic string. After the call, compare the length of OUTPUT against the expected domain length rather than trusting the call to have failed loudly if something was wrong. When the converted value feeds into a dynamic SELECT or an RFC call to another system, confirm the padded value against a known existing record before trusting it in production logic, since a silently wrong length will simply return zero rows rather than an error.

The conversion exit and its behavior are unchanged in S/4HANA; the domains that carry ALPHA, such as MATNR, still rely on it, and the extended material number length in S/4HANA makes correct use of this exit more important, not less, because the padding length now differs from older ECC installations for that field. There is no newer replacement function module. Calling it directly from custom code, including extensions built with a clean-core mindset, is considered acceptable since it is a stable, side-effect-free, released conversion utility rather than a business-logic API.

Most incidents trace back to a handful of repeated mistakes.

This sits squarely with the ABAP developer, not with functional or basis teams. When a lookup or interface fails because of an ALPHA mismatch, the fix is in custom code, either adding a missing explicit conversion call or correcting the length of a declared variable. Functional consultants get pulled in only when the symptom looks like missing master data, which is why ruling out a conversion mismatch early saves a wasted master data investigation.

CONVERSION_EXIT_ALPHA_OUTPUT is the direct counterpart, stripping leading zeros for display instead of adding them for storage; the two are almost always discussed together. RFC_READ_TABLE and similar remote table access function modules bypass the domain's automatic conversion entirely, so callers must run values through ALPHA_INPUT themselves before building the selection options. Value help function modules such as F4IF_INT_TABLE_VALUE_REQUEST also depend on correctly converted key ranges to match records as the user expects.