Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

conversion problem in condition records upload program (BDC tcode: XK15)

Former Member
0 Likes
966

Hello everyone,

I have downloaded few records from table A017 using key KUMNH (cond no), by the std program RVBTCI01 , i used three structures BRG00, BKOND1, BKOND2 and BKOND3 to download the records.

into a file (.txt) on the server.

now i uploaded the same file using the standard prg RV14BTCI (after recording the the transaction XK15 using BDC).

the amount field in bkond structure BKOND2-KEBTR is giving the conversion error while uploading ,

it is giving ERROR when the session is processed in sm35

it is not accepting the decimal places while uploading the amount field.

when amount field is made integer its working fine..

this is happening with fields MXWRT and GKWRT too .... (infact in all places where the decimals are used)

any pointers to solve this ???

5 REPLIES 5
Read only

Former Member
0 Likes
756

HI,

Refer to these lines in the report documentation..

The fields in the structures refer to the data elements for the fields in the original tables.
However, numeric and packed fields are the exception. They require separate data elements of the 
type CHAR for batch input. This is because packed fields cannot be filled with the special ID. Thus, 
amounts with decimal points can be transferred to the interface.

Read only

0 Likes
756

hi avinash,

the data elt used for KONP-KBETR in table is

KBETR_KOND ( which is of type CURR , length 11 and 2 decimal)

the data elt used for BKOND2-KBETR in structure is

BKBETR ( which is of type CHAR , length 15 and 0 decimal)

so dat i can download len(11)point(1)decimal(2) total 15 digits in the structure of 15 char

now the problem comes when i am uploading the same back into the table KONP-KEBTR

which is of type CURR as mentioned above

plz help to solve dis

Read only

0 Likes
756

Hi,

Did you check the session running in the foreground. This will give you the clear picture for which field conversion is going wrong.

Read only

0 Likes
756

@avinash

yes i did it in foreground mode itself

its not accepting the amount (KBETR) field which is 45.23

but if i removed the decimal point and make it a interger like 45 or 4523 manually in the foreground ,

then its working fine.

PS: the case is with all the fields having decimal values for eg as i said before MXWRT and GKWRT

too and even the scale qty too

Read only

Former Member
0 Likes
756

reqt closed