Application Development 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: 

Issue in table control in additional data b on VA11

Former Member
455

Hi All,

I have created a table control in screen 8309 of program SAPMV45A. After creating the table controls i am getting errors for missing entries in tables T185 and  T185V.

When I maintained the entry as per the below picture, the error was removed. But the problem is on pressing enter/insert/delete/save.... the control passes back to the screen 4900( the data does not disappears). This is very annoying and I need to correct it. this is happening because of module -

FCODE_BVFP_V.

I tried to set screen/;leave to screen but I get the error - that i cant set the subscreen.

Can anyone please help me. I have wasted a lot of time in this , but not getting a proper solution to solve it.

1 ACCEPTED SOLUTION

Former Member
0 Kudos
303

I remove the insert/delete buttons of the table control. Now I am not getting the error messages any more.

Thanks for all the help.

8 REPLIES 8

SimoneMilesi
Active Contributor
0 Kudos
303

Hi Raina,

Did you check the available notes?

SAP Note 302497 - Additional cust. fields not displayed in 'Additional data B'

SAP Note 209278 - Display of customer-specific fields in sales docSAP

SAP Note 386694 - Additional data not displayed in screen 8459 and 8309

SAP Note 420546 - Additional data B and transaction variants in sales order

Extrema ratio, check the VBFS transaction

0 Kudos
303

Hi Simone,

thanks for your inputs.

These notes are not very helpful in my case.

I tried clearing my ok-code also. but it does not help. I suppose it is mandatory to maintain entries in T185, T186V tables.

The problem comes when the flow goes back to the initial screen.

Is there any particular screen sequence to be followed for table control pbo/pai/ sub programs ?

Regards

Meenakshi

0 Kudos
303

Replying to the screen sequence part - by heart, the table control requires some LOOP AT -style coding in PBO and PAI of the screen. If this is the case, you'd have to make sure the PAI of the subscreen is executed as well (by adding a CALL SUBSCREEN statement smeewhere in the PAI of the 'main' screen)

Not sure this will help you much with your errors though.

0 Kudos
303

What do you mean with

The problem comes when the flow goes back to the initial screen

?

As stated, did you set the PAI for 8309 including the source code in include MV45AIZZ ?

0 Kudos
303

Yes Simone,

I have maintained my

PAI code -                       MV45AIZZ

PBO code -                     MV45AOZZ

data declaration  -           MV45ATOP

include subprograms -     MV45AFZZ

0 Kudos
303

Is there some set cursor statement in the PBO of screen 4900? And can't you overwrite that in the PBO of screen 8309 (in case of certain user commands of course)?

0 Kudos
303

yes set cursor is used in the include sub program part - MV45AFZZ . please find the screen shot -

Former Member
0 Kudos
304

I remove the insert/delete buttons of the table control. Now I am not getting the error messages any more.

Thanks for all the help.