topic Re: Conversion exit problem. in Application Development and Automation Discussions

Conversion exit problem.

kowong — Wed, 01 Aug 2007 11:58:23 GMT

Dear Expert,

I am using CABN-ATINN as one of the parameter input in the report, and glad to use the functionality of the standard conversion exit and search help of this field.

The problem here is, when the user enter incorrect value, the input box turn to empty, but I want the wrong entries to be shown in the error message.

Because of the conversion exit, the Incorrect Value is disappeared, and gave me 0000000, which is an numeric value stored in the table, converted because the text entered is not found.

Any way to get the value before the conversion exit ?

Thank you .

Re: Conversion exit problem.

Former Member — Wed, 01 Aug 2007 12:06:38 GMT

Hi Kokwei,

it is a standard functionality of the conversion exit.

to get rid of this:

chekc the value entered by the user before using conversion exit and if it is a wrong value fire a error message without conversion exit.

Regards,

Krishnendu

Re: Conversion exit problem.

Former Member — Wed, 01 Aug 2007 12:07:46 GMT

hi,

go to the screen which you use CABN-ATINN, and in the PAI of screen, write following code

field CABN-ATINN module XXX on input.

this will prevent you from the default value check for the field, and in module XXX you can write your own check.

regards.

Re: Conversion exit problem.

Former Member — Wed, 01 Aug 2007 12:16:54 GMT

sorry,

the module excuted before field check is module.....at exit_command

Re: Conversion exit problem.

kowong — Wed, 01 Aug 2007 12:32:18 GMT

This is a report,

selection screen

parameter: p_atinn for cabn-atinn.

i have made an debug stop at PAI in that report, the conversion ve already done.

where can i get the place before the conversion exit ?

Message was edited by:

Kokwei Wong

Message was edited by:

Kokwei Wong

Re: Conversion exit problem.

Former Member — Wed, 01 Aug 2007 12:47:55 GMT

Put a simple character field af the appropriate length as the parameter on the screen for the user to type their input into and then validate it and call the conversion exit in your program to convert it into an appropriate field for further processing.

You may need extra processing to handle value-request as the screen field is no longer linked to the data element, and possible some selection-screen output processing to show the converted value back to the user if you need to.

Bit more programming, but can achieve your desired result.

Andrew

Re: Conversion exit problem.

Former Member — Wed, 01 Aug 2007 12:55:03 GMT

Re: Conversion exit problem.

Former Member — Wed, 01 Aug 2007 12:58:54 GMT

hi, sorry for my first reply

module......at exit-command will be triggered before field check, but note it only will be excuted when the function type is E, and if this constrain not trouble you, you can use FM FM_FYC_DYNPRO_VALUE_READ in the module to get the field value. and then do your check, then call the screen again.

Re: Conversion exit problem.

Former Member — Wed, 01 Aug 2007 13:20:13 GMT

hi,

or you can just put

field CABN-ATINN. in the last line of your PAI. and before that use the FM to get the field value, do your own check and then leave the current screen before 'field CABN-ATINN' line .

Re: Conversion exit problem.

kowong — Thu, 02 Aug 2007 01:46:03 GMT

My purpose on this is to capture whatever the user input.

When the user input the incorrect value, the value input will be converted to 00000000 , due the the build in conversion exit from that field.

For example the user key in 'AAAB' , the conversion exit try to get the correspondance numeric value , which is ATINN, but not found, so returned 0000000000 to the parameter atinn.

But i need to return a message saying 'Characteristic AAAB not found.' but not 'Characteristic 000000000 not found.'

Message was edited by:

Kokwei Wong