on 06-02-2010 3:16 AM
Hi guys,
Im getting an error while running the program. We are using this for years now, and recently we encountered error as "output field too short for converted value".
The current ABAP program had to be terminated because the ABAP processor detected an internal system error. The current ABAP program "SAPLALFA" had to be terminated because the ABAP processor detected and invalid system state.
When calling the conversion routine ALPHA the specified target field was too short.
The termination occured in the ABAP program "SAPLALFA" in "CONVERSION_EXIT_ALPHA_INPUT".
The main program was ZFIR_WTAX2307.
The termination occurred in line 10 of the source code of the program "LALFAU01" of the source code of program "LALFAU01" (when calling the editor 100).
What does this mean? Please help me...
Thanks.
Below is the error analysis...
Runtime Error CONV_EXIT_FIELD_TOO_SHORT
Date and Time 06/18/2010 11:29:30
ShrtText
Output field too short for converted value.
What happened?
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPLALFA" had to be terminated because the ABAP
processor discovered an invalid system state.
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
When calling the conversion routine ALPHA, the specified
target field was too short.
How to correct the error
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
-
"CONV_EXIT_FIELD_TOO_SHORT" C
"SAPLALFA" or "LALFAU01"
"CONVERSION_EXIT_ALPHA_INPUT"
-
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Information on where terminated
The termination occurred in the ABAP program "SAPLALFA" in
"CONVERSION_EXIT_ALPHA_INPUT".
The main program was "ZFIR_WTAX2307 ".
The termination occurred in line 10 of the source code of the (Include)
program "LALFAU01"
of the source code of program "LALFAU01" (when calling the editor 100).
Edited by: Carol Corpus on Jun 18, 2010 7:08 AM
Edited by: Carol Corpus on Jun 18, 2010 7:13 AM
We encountered this same error today. The problem wasn't that the output field was too short though that may have been a side effect. The actual problem was that the input to CONVERSION_EXIT_ALPHA_INPUT was invalid.
I've pasted the relevant portion of the short dump we received below which I believe shows the input to and output from CONVERSION_EXIT_ALPHA_INPUT. The invalid value is "TESTACCTMGR".
No. 9 Ty. FUNCTION
Name CONVERSION_EXIT_ALPHA_INPUT
INPUT
TESTACCTMGR
0000000000000000
0000000000000000
5455444544522222
45341334D7200000
OUTPUT
0000000000
0000000000
2222222222
0000000000
Edited by: Patrick Sterling on May 4, 2011 10:56 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check with ur ABAPer, It should happend because of field length.... If u have define a new fields in ur program then check the length of this field, because output field length is to short to store coverted value through function module CONVERSION_EXIT_ALPHA_INPUT.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Carol,
Have you got the solution of this problem.
IF YES THAN PLEASE HELP ME.
I am also getting same problem.
Dear Dhiraj,
We have not defined any custom field. We are using Standard program (For Foreign Currency Valuation T-Code F.05 or SAPF100). When I analyze the field it shows: <13010010expense>. While 13010010 is my GLfor which I am carrying out the FCV. Why it is adding expense, i am unable to understand.
Please help.
DSC
DSC
Dear Carol,
I think the solution is the reply from Dhiraj . Please check the length of the fields in the calling program.
Dear DSC,
What support pack level are you on?
Perhaps the following notes could help:
673286 RFBIBL00: Short dump CONV_EXIT_FIELD_TOO_SHORT w/matchcode
617437 Transaction VC05: Dump CONV_EXIT_FIELD_TOO_SHORT
642392 Short dump for document parking or RFBIBL00
I hope this information has helped.
Best regards,
Ian Kehoe
Dear Carol,
Have you got the solution of this problem.
I am also getting same problem. If you solved it. Please also help me.
DSC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.