Custom Fields in IW31/IW32/IW33 Transaction--Screen Visiblity Issue

[Former Member]

Hi All

I have used the enhancement IWO10018 to add custom fields in the service order(Transactions IW31/IW32/IW33).However I am not able to control the visibility of the fields by writing appropriate custom code in the PBO of the new sub-screen(SAPLXOIH/0900).The fields are still open for input in the display transaction IW33.I have added the fields in an append structure to AUFK table & on the screen the fields are defined as pointing to CAUFVD structure as is the case with the standard fields in the IW* transactions.

I am also not able to debug any code written by me in the PBO/PAI events of the subscreen. I need to incorporate some custom logic for displaying F4 for one of the fields based on the user input in some other tab.

Do we need to do some additional customizing so that::

1) The fields are not open for input in the display transaction IW33.

2) I am able to debug the code written in the PBO/PAI events of the subscreen.

Any pointers/solutions to the above problems will be appreciated.

Thanks.

Regards

Chetan

[Former Member]

Hello,

normally the user-defined subscreen used by IWO10018 would be SAPLXWOC / 0900 - you get the

userdefined fields trough EXIT_SAPLCOIH_018 in a structure named COCI_AUFK .

We defined the fields with this name (COCI_AUFK-zz...) and there was no problem

in setting attributes to that fields in PBO or debugging.

May be a new release -but are you sure that SAPLXOIH / 0900 is the correct subscreen ?

Regards

Wolfgang

[Former Member]

Hi Chetan,

I have just worked on this enhancement, and my requirement was more or less the same.

Firstly The main second screen in all the of the three T-code are same, it is just the PF status that is different in them. So though in IW33 the fields should not be in input mode they are, but it wont be of any harm as if user tries to edit the value or something he/she wont be able to save it in the table as in the tool bar SAVE BUTTON is in disabled mode,moreover if you have run the T-code in debugger you must have seen that its not in your hand or you cannot modify the std SAP code to tarck down which T-code is running, it is already been handled in the std.

Secondly and most imp to add the F4 help on the fields simply double click on the screen and go in the flow logic .

Write normal code here,and when you double click on the module name it will automatically give you the include name ZXWOCI01' ,dont change the name simply press yes, a message will be displayed saying this include will be included in 'Z.......XX',simply press yes.

Write your normal code in this with the break point to test the execution of the PAI/PBO.

Infact global decleration can be made in ZXWOCTOP included in the 'I...TOP' module,simply double click on the Z...TOP to activate it.

Any other additional code can be added same way as you do in Module programming. Every module cretaed in PBO/PAI is created in 'ZXWOCI0.' generated automatically,simply press yes.

hope this little text will help you out.

Feel free to ask any doubts.

Pooja

[Former Member]

Hi Chetan,

You may try to 'LOOP AT SCREEN' in your screen's PBO.

Code looks like this:

LOOP AT SCREEN.

IF sy-tcode = 'IW31'.

IF screen-name CS '(the assigned name to a field)' OR screen-name CS '(field2)'

OR screen-name CS '.... blah blah...

screen-input = '1'. (CAN BE 1 or 0).

MODIFY screen.

ENDIF.

ENDIF.

IF sy-tcode = 'IW32' OR sy-tcode = 'IW52'.

.......do the same logic

ENDIF.

IF sy-tcode = 'IW33' OR sy-tcode = 'IW53'.

.......do the same logic

ENDIF.

ENDLOOP.