2007 Mar 13 2:44 PM
OK, I've pulled enough hair out on this and so it is time to post a plea of assistance. I have been away from dialog programming and am rusty when it comes to handling amounts and currency.
I have a table with these fields....
APPROVAL_MAX ZEBPAPRVL_MAX CURR 13
APPROVAL_CURR WAERS CUKY 5
APPROVAL_MAX has a reference to APPROVAL_CURR.
When I am trying to enter a value into APPROVAL_MAX like '1' and a value of 'USD" in APPROVAL_CURR, I get a error...
Message 00088. Input must be in the format __,___,___,__~.__
The two fields are in the same CHAIN ENDCHAIN.
FYI, I am working on an SRM box and there is not T001 table. So I am not sure what I am doing wrong.
Any assistance is appreciated.
2007 Mar 16 11:03 AM
Hi Dean,
Let the screen field be of a numeric character rather than a currency datatype...Once you are done with your formatting at the backend, move it to the screen field which is a numeric character.
You will not any errors in this case.
Hope this solves your problem
PS : Please reward points if solution is helpful
OK, I've pulled enough hair out on this and so it is time to post a plea of assistance. I have been away from dialog programming and am rusty when it comes to handling amounts and currency.
I have a table with these fields....
APPROVAL_MAX ZEBPAPRVL_MAX CURR 13
APPROVAL_CURR WAERS CUKY 5
APPROVAL_MAX has a reference to APPROVAL_CURR.
When I am trying to enter a value into APPROVAL_MAX like '1' and a value of 'USD" in APPROVAL_CURR, I get a error...
Message 00088. Input must be in the format __,___,___,__~.__
The two fields are in the same CHAIN ENDCHAIN.
FYI, I am working on an SRM box and there is not T001 table. So I am not sure what I am doing wrong.
Any assistance is appreciated.
2007 Mar 13 9:04 PM
More information... The currnecy USD has 4 decimal places, even though the field in the table has 2. I can convert with no problem, but what happens is that the entry is re-displayed in the format of the currency (4 decimals) by the input field (aka table field) is 2 decinal places. Therefore, the message as reported above.
How can I fix this?
2007 Mar 16 11:03 AM
Hi Dean,
Let the screen field be of a numeric character rather than a currency datatype...Once you are done with your formatting at the backend, move it to the screen field which is a numeric character.
You will not any errors in this case.
Hope this solves your problem
PS : Please reward points if solution is helpful
2007 Mar 16 11:11 AM
Well, I finally found the answer. I have been out of ABAping for quite sometime and thought I would forget alot of things. Well, this was one of them. I found an OSS Note to solve my issue...OSS Note 201925 - Using Currency Fields on Screens.
That Currency Key field needs to be prior to the Currency field in the CHAIN.. ENDCHAIN. Duh.
Thanks to all who provided any assistance.
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |