Wht r CTU-Prameters in BDC & diff. screen resolution b/w client &developmen

1.what are ctu parameters
how are they usefull in
BDC
2. how to avoid problem
when the screen resolution between client system and development system are
different in case of bdc

hi,
The error message that usually comes in status bar while you are running the transaction online might appear in a popup window when you are running that in batch and makes fields disable for input .
sometimes while you are recording a particular transaction you can observe some unwanted screens which will not appear when you are manually using the transaction.
this problem is resolved by ctu_params. this also avoids the screen resolution problem.
example:
Declare a work area of type CTU_PARAMS
X_OPTIONS-DISMODE = 'E'. (dispaly mode)
X_OPTIONS-UPDMODE = 'S'. (update mode)
X_OPTIONS-DEFSIZE = 'X '. (screen resolution)
X_OPTIONS-NOBINPT = 'X'. (hide the popup and unwanted screen)
call transaction tcode using T_BDCDATA[] options from X_OPTIONS.
thanks and rewards

Similar Messages

Change screen resolution in mobile clients

Hi,
Is there a way to define resolution in RDP mobile clients (wp,android,ios) when connecting to an RDP server?
It seems mobile clients connect with their native (max) resolution to the server, but most of the time it makes no sense. Full HD and 4K, extremely high DPI mobiles are coming and the desktop is very small on these devices. I know it's possible to zoom in
the session, but using full resolution it's a waste of bandwidth, especially on 3G.
Thanks

Hi,
I am afraid that we cannot customize the screen resolution on these clients. We can only zoom the screen via Connection Bar.
Thanks.
Jeremy Wu
TechNet Community Support

BDC - standard screen resolution required?

Is screen resolution a factor to check before carrying out any BDC with table control.

hai Peterson,
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.
regards,
Srikanth

Screen resolution for remote client

I have used Windows remote desktop and it has the fuction of setting the display resolution of the target machine when you login. So if i am on using a small laptop with small screen resolution (1024 x 768) and connect to a remote machine with a high resolution i can set the remote machine to display at 1024x768 nativly (no stretching or scalling).
DOES APPLE REMOTE DESKTOP HAVE THIS FUNCTIONALITY?

Ok so the solution was to user a different VNC client in Ubuntu. "Vinagre" allows you to view your remote session scaled to any size you like. It will however retain the dimentions of your MacBook screen.
One thing to be aware of is that when authentication your VNC session (entering your username and password) Vinagre only allows you to enter a password of 8 characters max. So if your password is longer then 8 characters you will have to shorten it to user Vinagre... A bit annoying but at least it works.
Techy notes:
It is actially the VNC server Vino that Vinagre uses that is enforcing the password length limit. So if using an alternative client that uses Vino as it's VNC server this limit will apply for that client also.
Even though you are scaling the client session down VNC sends the host's full resolution so you will still transfer a lot of data over the network.

BDC: Table Control Screen Resolution

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

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
BDC - standard screen resolution required?
https://forums.sdn.sap.com/click.jspa?searchID=739193&messageID=823953
reward points if found helpful

BDC screen resolution

How to do screen resolution in BDC table control ?

so there so many threads for screen resolution check it
how to solve screen resolution in bdc
Screen Resolution in Bdc
How to make screen resolution independent in BDC
Re: Screen Resolution problem in BDC
screen resolution problem in table control
whats the screen resolution problem with bdc's how to solve it?
Screen Resolution Problem in Session Method

HOW TO ADJUST MY FRONT PANEL & ITS OBJECTS ACCORDING TO SCREEN RESOLUTION.

Hai..
I want my fp to be visible in its standard form on all screen resolutions.I've used Maintain window prop for diff screen resolutions but it didnt work.Any Solution to this problem?

Did you also set the "Scale all objects..." setting?
For me mostly there had to be only 1 control to be scaled or changed in proportions, like a graph or listbox, the other controls (buttons, menu rings) should remain in size. This is best done by using splitters. You can lock them, stick them to one side of the window, make them invisible.
greets, Dave
Greets, Dave

SCREEN RESOLUTION IN BDC

HI,
CAN ANY ONE TELL ABOUT SCREEN RESOLUTION IN BDC.
REGARDS.
B.SREENIVASULU.

Hi,
Screen resolution means different in the screen display depending on ur system screen resolution.
suppose ur system resolution is diff and another's system is different then like in Tcode VA01, there will be 3 lineitems and another there will be 5 lineitems ,
so while doing recording and page down that will bw diff so there will be some problem
So u have to set the screen resolution as default by using CTU parameters..
write this code then
f_option-updmode = 'S'.
 f_option-defsize = 'X'. f
_option-dismode = 'N'.
*call transaction 'VA01' using bdcdata options from f_option messages into bdcerror.
Hope it helps.
Regards,
Sonika

How to solve screen resolution in bdc

hi experts,
please tell me how to solve screen resolution in bdc.
regards.
subhasis

Hi,
Pls check other posts in SDN before posting ur thread..there is same thread related to this on this forum on same day.
Screen resolution means different in the screen display depending on ur system screen resolution.
suppose ur system resolution is diff and another's system is different then like in Tcode VA01, there will be 3 lineitems and another there will be 5 lineitems ,
so while doing recording and page down that will bw diff so there will be some problem
So u have to set the screen resolution as default by using CTU parameters..
write this code then
f_option-updmode = 'S'.
f_option-defsize = 'X'.* f
_option-dismode = 'N'.
*call transaction 'VA01' using bdcdata options from f_option messages into bdcerror.
Hope it helps.
Regards,
Sonika

Controlling Screen Resolution in BDCs

Hi,
Can any one explain about the process for Controlling Screen Resolution in BDCs.
Thanks & Regards,
Rajesh.

Hi,
If u write table control bdc program in 14'' monitor screen, then if the same program u run at different monitor size, then the screen resolution problem comes in to the picture,
like, u get 5 records in table control in one screen, and some other records in other screen, to avoid this screen resolution problem we use CTU-PARAMS Structure.
In ur program u have to set
defsize type ctu_params-defsize value 'X',
Then u will be free of screen resolution problem.
Fill the str CTU_PARAMS-defsize = 'X' and pass in CTU stmnt as
call transaction 'XXX' options using t_bdcdata ctu_params.
Analysing :
1. If nothing works, then we have to
some ifs & buts.
2. There shall be normally
2-4 different kinds of resolution
on various users comptuers.
3. Based on this,
we have to know beforehand,
what will be the number of rows
in the table control.
4. The user can be given
a selection/paraemter
for resolution
eg. 800x600
1024x100
axb
etc.
5. Based on this, we will hardcode
in the program (based upon our knowledge/recording
which we have seen and done)
we will hardcode
the number of lines
in the VARIBLE.
6. Then we can simply use this variable
for our LOOP and logic purpose.
7. It will be the responsibiltiy of the
use to CHOOSE THE CORRECT resolution,
on the selection-screen.
For screen resolution use ctu_params, with default size
Data : f_option type ctu_params,
f_option-updmode = 'S'.
f_option-defsize = 'X'.
f_option-dismode = 'N'.
call transaction 'VA01' using bdcdata options from f_option messages into bdcerror.
CALL TRANSACTION tcode... OPTIONS FROM opt
... OPTIONS FROM opt
Effect
Allows you to control processing using the values of the componetns of the structure opt, which must have the ABAP Dictionary type CTU_PARAMS. The components have the following meanings:
DISMODE
Display mode (like the MODE addition)
UPDMODE
Update mode (like the UPDATE addition)
CATTMODE
CATT mode (controls a CATT)
CATT mode can have the following values:
' ' No CATT active
'N' CATT without single-screen control
'A' CATT with single-screen control
DEFSIZE
Use default window size
RACOMMIT
Do not end transaction at COMMIT WORK
NOBINPT
No batch input mode (that is, SY-BINPT = SPACE)
NOBIEND
No batch input mode after the end of BDC data.
The components DEFSIZE , RACOMMIT, NOBINPT, and NOBIEND always take the following values:
'X' Yes
' ' No
If you do not use the OPTIONS FROM addition, the following control parameter settings apply:
DISMODE
From addition MODE
UPDMODE
From addition UPDATE
CATTMODE
No CATT active
DEFSIZE
Do not use default window size
RACOMMIT
Successful end on COMMIT WORK
NOBINPT
Batch input mode active ( SY-BINPT = X
NOBIEND
Batch input mode remains active after the BDC data
Hope it makes u understand...
Reagrds,

I upgraded my iMac to 10.9.4. Now the feature where you can go to 4 diff. screens (Command+Control) doesn't work. How do I fix this?

I upgraded my iMac to 10.9.4. Now the feature where you can go to 4 diff. screens (Command+Control) doesn't work.
How do I fix this?

Do you have that problem when running in the Firefox SafeMode? 
[http://support.mozilla.com/en-US/kb/Safe+Mode] 
''Don't select anything right now, just use "Continue in SafeMode."''
If not, see this: 
[http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes]

Screen Resolution in table control bdc

Hi ,
Im working on bdc table control using call transaction method for vk11 and mek1.While uploading data for vk11 for the first time it is taking all the records of the input file and if i do the same for the second time by changing the amount value it is taking only 24 records .(i.e if the input file contains only 24 records it wil update else if it has 25 records or more it not updating even single record and it is showing error " No batch input data for screen sapmv13A ..)...this issue is with the production server......................whereas in development and quality servers there is no problem....................
what migh be the problem and how to solve it?
can anyone plz help me on this

if its a problem in screen resolution then while recording through SHDB mark the check box default size
or
to make the bdc execute in standard screen size check the code below
data x_ctuparams type ctu_params.
x_ctuparams-defsize = 'X'. " This would freeze the resolution in any system
x_ctuparams-dismode = 'N'.
x_ctuparams-updmode = 'S'.
call transaction <TCODE> using it_bdcdata options from x_ctuparams.
So whatever is the screen size of the users front-end, the BDC will execute in standard screen size

How to handle screen resolution in bdc session method.

hi all,
how to handle screen resolution in bdc session method.

Hello,
Why do need that for? Is it to add rows on a table control??
If it does, add new rows by using the add button instead of adding into the table control directly to each row.
Bye
Gabriel.

How to handle screen resolution in ME21 fro a bdc programme

I need to use BDC program for ME21 for that how to handle the screen resolution,
i know CTU_PARAMS structure is there ,but how to use them, please send the model code.
Thanks & Regards
krishna

got the solution

How to create screen resolution in bdc table control

hi gurus
can anyone suggest me
how to create screen resolution in bdc table control
thanks&regards
mark.

Hi ,
Using CTU_PARAMS table for screen resolution .
For this sample code.
This is for Transation FB60.
report ZZFB60
       no standard page heading line-size 255.
tables t100.
PARAMETERS : p_file1 like rlgrap-filename,
             p_doctyp like RF05A-BUSCS,
             p_invdat like INVFO-BLDAT,
             p_posdat like INVFO-BUDAT.
CONSTANTS : C_TRANS_FB60(4) VALUE 'FB60'.
*Parameter string for runtime of CALL TRANSACTION
data : l_option type ctu_params,
       l_subrc type sysubrc.
DATA : l_mstring(150).
data      accnt type char17.
data       : day   type char2,
             month type char2,
             year type char4,
             date1 type char10,
             date2 type char10.
data      : cnt(2) TYPE n,
             cnt1 type i,
             fld(25) TYPE c.
data : begin of excel occurs 0,
        fieldname(255) type c,
       end of excel.
DATA:BEGIN OF it_mess OCCURS 0,
         msgtyp(5),
         lms(200),
          msgv1(50),
     END OF it_mess.
data: begin of t_record occurs 0,
         BUKRS(004),
        ACCNT(017),
        XBLNR(016),
        WRBTR1(016),
        WAERS(005),
        SECCO(004) ,
        SGTXT(050),
        HKONT(010),
        WRBTR2(017),
        MWSKZ(002),
        GSBER(004),
        KOSTL(010),
     end of t_record.
*Internal Table for Header Data
DATA : BEGIN OF t_head OCCURS 0,
        BUKRS(004),      "Company Code
        ACCNT(017),      "Account or Vendor
        XBLNR(016),      "Reference
        WRBTR1(017),     "Amount in document currency
        WAERS(005),      "Currency
        SECCO(004),      "Section Code
        SGTXT(050),      "Text
        END OF t_head.
*Internal table for Item Data
DATA : BEGIN OF t_item OCCURS 0,
        ACCNT(017),      "Account
        HKONT(010),     "GL Account
        WRBTR2(017),    "Line item Amount in document currency
        MWSKZ(002),     "Tax Code
        GSBER(004),     " Business Area
        KOSTL(010),     "Cost centre
        END OF t_item.
DATA: IT_BDCDATA      LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
      IT_BDC_MESSAGES LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
*include bdcrecx1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
PERFORM file_selection.
PERFORM data_upload.
PERFORM table_control.
start-of-selection.
l_option-defsize = 'X'.
l_option-dismode = 'A'.
l_option-updmode = 'S'.
day = p_invdat+6(2).
month = p_invdat+4(2).
year = p_invdat+0(4).
concatenate day month year into date1 SEPARATED BY '.'.
day = p_posdat+6(2).
month = p_posdat+4(2).
year = p_posdat+0(4).
concatenate day month year into date2 SEPARATED BY '.'.
*perform open_group.
loop at t_head.
CLEAR    IT_BDCDATA.
REFRESH IT_BDCDATA.
perform bdc_dynpro      using   'SAPLACHD'         '1000'.
perform bdc_field       using   'BDC_OKCODE'        '=ENTR'.
perform bdc_field       using   'BKPF-BUKRS'        t_head-bukrs.
perform bdc_dynpro      using   'SAPMF05A'          '1100'.
perform bdc_field       using   'BDC_OKCODE'        '/00'.
perform bdc_field       using   'RF05A-BUSCS'       p_doctyp.
perform bdc_field       using   'INVFO-ACCNT'       t_head-accnt.
perform bdc_field       using   'INVFO-BLDAT'       date1.
perform bdc_field       using   'INVFO-BUDAT'       date2.
perform bdc_field       using   'INVFO-XBLNR'       t_head-xblnr.
perform bdc_field       using   'INVFO-WRBTR'       t_head-wrbtr1.
perform bdc_field       using   'INVFO-WAERS'       t_head-waers.
perform bdc_field       using   'INVFO-SECCO'       t_head-secco.
perform bdc_field       using   'INVFO-SGTXT'       t_head-sgtxt.
cnt = 1.
cnt1 = 1.
loop at t_item where accnt = t_head-accnt.
*if cnt > 4.
*cnt = 4.
*endif.
if cnt1 gt 1.
CONCATENATE 'ACGL_ITEM-MARKSP(' cnt ')' INTO fld.
perform bdc_field      using   fld                   'X'.
perform bdc_dynpro      using 'SAPMF05A'          '1100'.
perform bdc_field       using 'BDC_OKCODE'        '=0005'.
endif.
perform bdc_dynpro      using 'SAPMF05A'          '1100'.
perform bdc_field       using   'BDC_OKCODE'        '/00'.
CONCATENATE 'ACGL_ITEM-HKONT(' cnt ')' INTO fld.
perform bdc_field       using fld                t_item-hkont.
CONCATENATE 'ACGL_ITEM-WRBTR(' cnt ')' INTO fld.
perform bdc_field using       fld                t_item-wrbtr2.
CONCATENATE 'ACGL_ITEM-MWSKZ(' cnt ')' INTO fld.
perform bdc_field       using fld                t_item-mwskz.
CONCATENATE 'ACGL_ITEM-GSBER(' cnt ')' INTO fld.
perform bdc_field       using fld                t_item-gsber.
CONCATENATE 'ACGL_ITEM-KOSTL(' cnt ')' INTO fld.
perform bdc_field       using fld                t_item-kostl.
perform bdc_field      using 'BDC_CURSOR' fld.
*CONCATENATE 'ACGL_ITEM-MARKSP(' cnt ')' INTO fld.
*perform bdc_field      using   fld                   'X'.
cnt1 = cnt1 + 1.
*cnt = cnt + 1.
*if cnt > 1.
*perform bdc_dynpro      using 'SAPMF05A'          '1100'.
*perform bdc_field       using 'BDC_OKCODE'        '=0005'.
**perform bdc_field       using 'BDC_OKCODE'        '=0006'.
*endif.
endloop.
perform bdc_dynpro      using 'SAPMF05A' '1100'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BS'.
perform bdc_dynpro      using 'SAPMSSY0' '0120'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BU'.
*perform bdc_transaction using 'FB60'.
CALL TRANSACTION C_TRANS_FB60 USING IT_BDCDATA options from l_option
                             MESSAGES INTO IT_BDC_MESSAGES.
perform error.
perform errordownload.
endloop.
*perform close_group.
*Form data_upload
FORM data_upload .
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
   FILENAME              = p_file1
   FILETYPE              = 'DAT'
TABLES
    DATA_TAB             = t_record.
ENDFORM.                    " data_upload
*Form file_selection
FORM file_selection .
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
      field_name    = 'p_file1'
    IMPORTING
      file_name     = p_file1.
ENDFORM.                    " file_selection
Form BDC_DYNPRO
FORM BDC_DYNPRO using program dynpro.
CLEAR IT_BDCDATA.
IT_BDCDATA-PROGRAM = PROGRAM.
IT_BDCDATA-DYNPRO = DYNPRO.
IT_BDCDATA-DYNBEGIN = 'X'.
APPEND IT_BDCDATA.
endform.
*Form BDC_FIELD
FORM bdc_field using fnam fval.
CLEAR IT_BDCDATA.
IT_BDCDATA-FNAM = FNAM.
IT_BDCDATA-FVAL = FVAL.
APPEND IT_BDCDATA.
ENDFORM.
Table Control
FORM table_control .
LOOP AT t_record.
    ON CHANGE OF t_record-accnt.
      MOVE-CORRESPONDING t_record TO t_head.
      APPEND t_head.
    ENDON.
loop at t_head.
         t_item-accnt   = t_head-accnt.
         t_item-hkont   = t_record-hkont.
         t_item-wrbtr2 = t_record-wrbtr2 .
         t_item-mwskz   = t_record-mwskz .
         t_item-gsber   = t_record-gsber .
         t_item-kostl   = t_record-kostl.
    APPEND t_item.
endloop.
     If t_record-level = 'H'.
         t_head-bukrs   = t_record-text1.
         t_head-accnt   = t_record-text2.
         t_head-xblnr   = t_record-text3.
         t_head-wrbtr1 = t_record-text4.
         t_head-waers   = t_record-text5.
         t_head-secco   = t_record-text6.
         t_head-sgtxt   = t_record-text7.
      APPEND t_head.
     else.
        t_item-accnt   = t_head-accnt.
        t_item-hkont   = t_record-text1.
        t_item-wrbtr2 = t_record-text2.
        t_item-mwskz   = t_record-text3.
        t_item-gsber   = t_record-text4.
        t_item-kostl   = t_record-text5.
     APPEND t_item.
     endif.
ENDLOOP.
ENDFORM.
FORM error .
LOOP AT IT_BDC_MESSAGES.
    IF IT_BDC_MESSAGES-msgtyp = 'E'.
   SELECT single * FROM t100 WHERE
                                sprsl = it_BDC_MESSAGES-msgspra
                                AND   arbgb = IT_BDC_MESSAGES-msgid
                                AND   msgnr = IT_BDC_MESSAGES-msgnr.
      IF sy-subrc = 0.
        l_mstring = t100-text.
        IF l_mstring CS '&1'.
          REPLACE '&1' WITH IT_BDC_MESSAGES-msgv1 INTO l_mstring.
          REPLACE '&2' WITH IT_BDC_MESSAGES-msgv2 INTO l_mstring.
          REPLACE '&3' WITH IT_BDC_MESSAGES-msgv3 INTO l_mstring.
          REPLACE '&4' WITH IT_BDC_MESSAGES-msgv4 INTO l_mstring.
        ELSE.
          REPLACE '&' WITH IT_BDC_MESSAGES-msgv1 INTO l_mstring.
          REPLACE '&' WITH IT_BDC_MESSAGES-msgv2 INTO l_mstring.
          REPLACE '&' WITH IT_BDC_MESSAGES-msgv3 INTO l_mstring.
          REPLACE '&' WITH IT_BDC_MESSAGES-msgv4 INTO l_mstring.
        ENDIF.
        CONDENSE l_mstring.
        it_mess-msgtyp = IT_BDC_MESSAGES-msgtyp.
        it_mess-lms = l_mstring.
        it_mess-msgv1 = IT_BDC_MESSAGES-msgv1.
        APPEND it_mess.
      ELSE.
        it_mess-msgtyp = IT_BDC_MESSAGES-msgtyp.
        it_mess-lms = l_mstring.
        it_mess-msgv1 = IT_BDC_MESSAGES-msgv1.
        APPEND it_mess.
      ENDIF.
    ENDIF.
ENDLOOP.
ENDFORM.
form errordownload.
*down the internal table to excel file.
call function 'EXCEL_OLE_STANDARD_DAT'
           EXPORTING
                file_name                 = 'c:/Error.xls'
           TABLES
                data_tab                  = it_mess
                fieldnames                = excel
           EXCEPTIONS
                file_not_exist            = 1
                filename_expected         = 2
                communication_error       = 3
                ole_object_method_error   = 4
                ole_object_property_error = 5
                invalid_filename          = 6
                invalid_pivot_fields      = 7
                download_problem          = 8
                others                    = 9.
endform.
Reward if useful
Regards,
Narasimha
Edited by: narasimha marella on May 13, 2008 12:12 PM

Wht r CTU-Prameters in BDC & diff. screen resolution b/w client &developmen

Similar Messages

Maybe you are looking for