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

Problem in BDC using VK11

Former Member
0 Likes
934

Hi All,

I ma trying to upload the scaled prices using the VK11 transaction. For the scaled prices table control I need to enter the scaled quantity as well as the rate.

For eample if I want to upload the 5 scaled prices for a single materail, ssay Qty1, qty2,qty3,qty4 and qt5.

Rate1,rate2,rate3,rate4 and rate5.

I have written the logic to upload the data.

While executing the program using call transaction and mode as all screens I am getting a message saying that 'KONM-KBETR(1) input value is longer than the screen field..

'KONM-KBETR(2) input value is longer than the screen field..

like this I am getting for all values but the scaled prices are not getting updated to that material.

If anyone has faced this type of problem, please let me know the solution.

Thanks and Regards

Abhilash.

6 REPLIES 6
Read only

GauthamV
Active Contributor
0 Likes
867

hi,

define these variables with there length as type c.

ur problem will be solved.

for ex:

data: begin of it_mm01 occurs 0,

mbrsh(1) type c,

mtart(4) type c,

werks(4) type c,

maktx(40) type c,

meins(3) type c,

matkl(9) type c,

bklas(4) type c,

end of it_mm01.

Read only

Former Member
0 Likes
867

hai,

check wheather datas r seating in the screen field correctly r not ,

i think data r not mapped properly..

shan.

Read only

Former Member
0 Likes
867

solved myself

Read only

0 Likes
867

Hi Abhilash,

I face a similar problem but with a different transaction. What was your solution?

Thanks

SL

Read only

0 Likes
867

Hi SL,

Could you please mention the details of your problem?

Like any error messages you got...

transaction details and things like that.....

please mention the field names for which u got this problem.

I will help u out with the solution.

Regards

Abhilash.

Read only

0 Likes
867

I resolved the solution by using a char field instead of the actual type that corresponded to the screen field. Strange that it wouldn't work, but I think it had to do with the fact that the screen field holds a decimal value. Thanks for the offer.

SL