Table control lines cannot be controlled in Batch Input session ?

[Former Member]

I am using a program which creates Batch Input sessions for the transaction FCHR (Online cashed checks) . The second screen is that of a table control where the check number is entered.

I observed that while doing SHDB, if we tick the default size then changing the desktop resolution has no effect on the number of lines in table control - we see 14 lines in both cases.However, when the batch input session is processed, the number of table control lines varies according to the resoution(9 lines for 800600 and approx 15 for 1024768). Selecting the 'Dynpro standard size' option while processing the session has no effect.

I know call transaction with 'default' parameter in optparam will take care of this problem. But I want to know whether Batch Input Session is known to have a problem with different resolutions.

[Former Member]

HI..

i had the same problem once.... i dealt in the following way

while entering values in table control

1) enter value in the first line

2) look for button on application toolbar using which you can increment line

3) you will not find difference for first line but you will find it when you insert second line and go for next line.

4) now for every increment you will get table conrol as (02) if you are going for recording.

this will surely solve all issue related to table control as it solved for me

regards

Edited by: Mohit Kumar on Feb 19, 2009 12:04 PM

[Former Member]

Mohit,

Do you mean the '' or the new entries button we see in SM30. Unfortunately , there is no such button in FCHR screen.. Only next page/last page buttons can be seen.. At the moment, the program presses 'Enter' after each line followed by 'P' okcode for page down.

[Former Member]

Hi,

The number of lines of table control seen at the time of recording using SHDB, are the default number of lines irrespective of your monitor resolution.

Based on these number of lines, use P+, page down using MOD and DIVIDE (to add the records)

This will eliminate use of optparam and can be used in the background job.

Thanks,

Kartavya