Confused about DD01D-LOWERCASE initial and moving case sensitive values

[Former Member]

Hi all,

I'm wondering why a simple MOVE does not do the translation to upper case if DD01D-LOWERCASE is intial.

The write-to and conversion function does not do this either.

Check the code and watch lf_exidvb.

Seems that translation is only be done on the dynpro when using the field as parameter but when using internal

Any idieas? I'm getting the values for many different fileds from excel and only workaround for now is looking at DD01L-LOWERCASE and doing the translation manually with TRANSLATE to UPPER CASE.

Thanks & Cheers

carsten

Example

REPORT  zcawa_move.
DATA:
lf_exidv   TYPE vekp-exidv,
lf_exidvb  TYPE vekp-exidv,
lf_mask   TYPE string.

PARAMETERS: p_exidv TYPE vekp-exidv.

lf_exidv = 'ElephantLion'.                                "coming from excel normally

DESCRIBE FIELD lf_exidv
  EDIT MASK lf_mask.

WRITE lf_exidv TO lf_exidvb USING EDIT MASK lf_mask.
WRITE lf_exidv TO lf_exidvb USING EDIT MASK '==ALPHA'.

CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
  EXPORTING
    input  = lf_exidv
  IMPORTING
    output = lf_exidvb.


CHECK 1 = 1.

[former_member15255]

Hi ,

Please make use of the function module 'CONVERSION_EXIT_ALPHA_OUTPUT'.

Thanks & Regards

Suresh Nair

[former_member214857]

Hello Carsten

Actually conversion routine CONVERSION_EXIT_ALPHA_INPUT will not convert data to upper case automatically.

To do so you can create your own conversion routine to convert into upper case format and use WRITE statement with this new Function for this conversion routine

Best regards

[Former Member]

Hola Carlos,

yes, I could do so, but i cannot deal with the standard data elements then....

I think a routine which looks at DD04 and doing the TRANSLATE if LOWERCASE is intiial would be the best....

I'm really surprised about this behaviour (Ok, normally data comes from dynpro input and is convertet properly...)

It's quite not logical that the neitehr the MOVE nor the CONVERT does not do the UPPER conversion and remedy is cumbesome.

Gracias

carsten

[Pawan_Kesari]

DATA : lv_low TYPE text10 ,
       lv_cap TYPE char10 .

lv_low = 'Test' .
lv_cap = 'Test' .

CALL METHOD cl_issr_basi_ddic_services=>set_upper_case
  CHANGING
    cd_field = lv_low.


CALL METHOD cl_issr_basi_ddic_services=>set_upper_case
  CHANGING
    cd_field = lv_cap.

WRITE : / lv_low , lv_cap .

Edited by: pawankesari on Jan 30, 2012 9:18 PM

[SuhaSaha]

I'm really surprised about this behaviour (Ok, normally data comes from dynpro input and is convertet properly...)
It's quite not logical that the neitehr the MOVE nor the CONVERT does not do the UPPER conversion and remedy is cumbesome.

Hello Carsten,

Actually as per the F1 documentation the automatic conversion to UPPER case applies to screen elements only

BR,

Suhas

[Former Member]

Hi Suhas,

which F1-Docu exactly? F1 on ABAP-Keyword MOVE does not supply this Info...

Thanks & Cheers

carsten

[SuhaSaha]

Hi Carsten,

Sorry for not specifying the source. It's actually the F1 help on the "Lowercase" checkbox in the domain definition.

BR,

Suhas