conversion error WRITE vbrk-fkdat TO billdate.

[Former Member]

Data : billdate(10).

WRITE vbrk-fkdat TO billdate.

In a print program i'm using code as under

WRITE vbrk-fkdat TO billdate.

20100217 & final converts to 17.02.2010

But in case of export billing

WRITE vbrk-fkdat TO billdate.

20100217 & final converts to 20.10.0217

Can u pls suggest

[Former Member]

Data : billdate(10).

WRITE vbrk-fkdat TO billdate.

In a print program i'm using code as under

WRITE vbrk-fkdat TO billdate.

20100217 & final converts to 17.02.2010

But in case of export billing

WRITE vbrk-fkdat TO billdate.

20100217 & final converts to 20.10.0217

Can u pls suggest

[Former Member]

Hi,

Try this

WRITE vbrk-fkdat to field DD/MM/YYY.

Hope this helps.

Ernesto

[venkat_o]

But in case of export billing

What does it mean ? Thanks Venkat.O

[Former Member]

when i am issuing the print for export billing the date conversion is not correct.

For same scenario on Development it is working fine.But on LIve system it thows error Specify a valid date

[Former Member]

Hi,

data date type sy-datum.
data str type string.
your date values is date =  20100220. Assume

data : date type char2,
          month type char2,
          year type char4.
date = sy-datum. 
year = date+0(4). " gives you 20
month = date+4(2).  "gives you 02
date = date+6(2). Gives you 2010

now concatenate date '.' month '.' year into str.

Now the result willl be 20.02.2010

Hope this serves your purpse.

Cheerz

Ram

[venkat_o]

But in case of export billing

WRITE vbrk-fkdat TO billdate.

20100217 & final converts to 20.10.0217

<li>Put breakpoint at WRITE vbrk-fkdat TO billdate in case of export billing and check whether the value of vbrk-fkdat is 20100217 or not because WRITE statement does not behave differently in different places. Thanks Venkat .O

[Former Member]

Hi,

Use CONCATENATE STATEMENT.

CONCATENATE vbrk-fkdat+6(2) '.' vbrk-fkdat+4(2) '.' vbrk-fkdat+0(4) TO billdate.

Regards,

Shankar.

[Former Member]

Actaully in case of export the configuration was maintained as yyyymmdd instead of ddmmyyyy.

Thanks 4 ur answers.