BDC: Table Control Screen Resolution

[Former Member]

Hi Abapers,

1.In BDC while handling table control , how to handle screen resolution , that means in some systems i can see 5 item entries , in some systems i can see 10 item entries how to handle this , can u send the Code relating this.

With Regards

Bhaskar Rao.M

[rahulkavuri]

hi

The numeber of lines of table control for BDC depend on screen resolution, but It can't be managed by program.

So the better solution is to create a bdc doesn't depend on resolution.

It can do that using always the first two lines of table control.

When you start the simulation, first record has to be placed in first line of tc and the second in second one.

Before placing the third record, it needs to place the second record to the top and so the third record can be placed in the second line.

Before placing the next record, it needs to place the third record to the top and so the fourth record can be placed in the second line and so.

In this way your BDC'll use alwways the first two lines of tc and your program won't depend on resolution.

The problem is the transaction you need to simulate by BDC has to have a scroll functionality to allow to place the last record was elaborated to the top of tc, so the second line of tc can always be used to place the new record.

If there isn't this functionality, it's better to use a BAPI instead of BDC.

check these two

https://forums.sdn.sap.com/click.jspa?searchID=739193&messageID=823953

??

reward points if found helpful

[Former Member]

Hi,

unfortunately, I think this is very difficult to control. Pls, check in the

transaction that you are working in, if there is an option or some way,

to say explicitly, what position you need to modify.

In other way, maybe you can find a Funtion Module or a BAPI, that can do

the same work that you need to do in your batch input.

Regards,

Carles

[Former Member]

Hi Friend,

Please check the option CTU_PARAMS in call transaction.This will help you for screen resolution.

[Former Member]

hi Bhaskar Rao,

While recording for transactions with table control, always enter value only in the first row and click the + button just above or below the table control to enter the second value. Now the cursor will always be in the 1st position.

Hence, we can code the program to enter the values always in the 1st row, no matter on which resolution the screen is displayed.

For old transactions (which does not use SAP Enjoy controls), instead of PLUS icon, there would be some down arrow like icon; use that action.

Hope this helps,

Sajan Joseph.

[Former Member]

Hi Bhaskar,

Just use the following syntax for call transaction:

"Declare itab_bdcdata with type bdcdata.
 DATA:  f_option         TYPE ctu_params.
 DATA: fitab_bdcmsgcoll TYPE bdcmsgcoll OCCURS 0.

  f_option-updmode  = 'S'.
  f_option-defsize  =  'X'.
  f_option-dismode  = 'N'.

  CALL TRANSACTION <here use ur transaction> USING itab_bdcdata
                         OPTIONS FROM f_option
                        MESSAGES INTO fitab_bdcmsgcoll.

Here in this code the defsize option makes the handling of table control same across all the systems. So just do a recording of your transaction with the default screen size & then increment the index based on the no which you get in the default recording for the table control entries.

Regards,

Chetan.

PS:Reward points if this helps.

[Former Member]

Hi,

How this issues was getting solved. i am facing the same issuee.

Regards,

Prabu

[Mohammed_Nabeel]

Is this error resolved for anyone using BDC? I am getting same error ' Dynpro is too big for internal batch input' in f-36 transaction.

Maximum its accepting 22 line items