DEFAULT WINDOW SIZE IN 45B

[Former Member]

Hi, I am trying to determine the line a condition type is on to be able to delete that line in a pricing screen. I am on 45b and DEFSIZE in the function CALL TRANSACTION is not available to me. Please help. I call a screen to get the number of screen rows but the static number of lines seems to change depending on font size.

I have it working in my development system but in the QA system it fails. I only have an issue with background processing.

Any help would be much appreciated. Regards Joanne

[Former Member]

Hi, I am trying to determine the line a condition type is on to be able to delete that line in a pricing screen. I am on 45b and DEFSIZE in the function CALL TRANSACTION is not available to me. Please help. I call a screen to get the number of screen rows but the static number of lines seems to change depending on font size.

I have it working in my development system but in the QA system it fails. I only have an issue with background processing.

Any help would be much appreciated. Regards Joanne

[christian_wohlfahrt]

Hi Joanne!

Try to use transaction XK15 - there is no popup (with radiobuttons). You can enter required level as number in the entry screen.

Regards,

Christian

[Former Member]

Thanks for your input - I don't think I explained correctly.

I am trying to delete a pricing condition in the pricing screen on a sales document ( quotation ) at the item level.

Regards Joanne

[christian_wohlfahrt]

Hi!

OK, then you can have a completely different answer. Try to use a BAPI instead: BAPI_CUSTOMERQUOTATION_CHANGE.

There is always a (small) probability, that users added some manual conditions -> you never can be sure, in which line you will find your specific condition.

Regards,

Christian

[former_member182371]

hi,

long ago i found this example in a forum:

"CTU_PARMS will force the BDC to use the standard default screen size (rather than being dynamic based on the user's settings. I think I explained that right, but all I know is that it keeps the BDC from behaving differently between users and makes things more consistent for coding logic".

Here's an example (note that DEFSIZE is the key to the solution here):

data: begin of tran_opts,

dismode type ctu_params-dismode value 'N',

updmode type ctu_params-updmode value 'S',

cattmode type ctu_params-cattmode,

<b>defsize type ctu_params-defsize value 'X'</b>,

racommit type ctu_params-racommit,

nobinpt type ctu_params-nobinpt,

nobiend type ctu_params-nobiend,

end of tran_opts.

call transaction 'F-02'

using bdcdata

options from tran_opts

messages into bdc_messages

Hope it helps,

Best regards