Including Customer-Specific Screens on Tab Pages 

Use

This procedure is devoted to technical consultants at the customer’s site, who have both ABAP programming knowledge and are also familiar with warranty processing functionality and the customer’s business processes.

Procedure

The linking in of the additional screens takes place via customer exit WTY00002.

...

       1.      Call the display of the components for customer exit WTY00002 – subscreen in Warranty Claim Processing (tab control) – via transaction SMOD.

You see a list of the function modules used (EXIT_SAPLPVSUIWTY_003, EXIT_SAPLPVSUIWTY_004 und EXIT_SAPLPVSUIWTY_005) and the subscreens. Subscreens 1001 to 1020 of subscreen container 1501 in program SAPLXWTY are predefined but do not exist yet and are available for use as customer-specific subscreens.

       2.      Create a project for WTY00002 (transaction CMOD). All the SAP components you require are copied to this project.

       3.      Create a new screen of screen type Subscreen (transaction se51) in program SAPLXWTY. Use the Screen Painter to do this. The screen number must be between 1001 and 1020.

       4.      Double-click on function module EXIT_SAPLPVSUIWTY_003 in transaction CMOD and then on include ZXWTYU03 to create the screen. Continue in the same way for function module EXIT_SAPLPVSUIWTY_004 / include ZXWTYU04 and function module EXIT_SAPLPVSUIWTY_005 / include ZXWTYU05.

The function modules have the following tasks:

¡        EXIT_SAPLPVSUIWTY_003 transports the data from standard processing to the customer-specific function group XWTY of the customer-specific screen.

¡        EXIT_SAPLPVSUIWTY_004 transports the data from the customer-specific function group XWTY back to standard processing.

¡        EXIT_SAPLPVSUIWTY_005 assigns the customer-specific screen to the subscreen container. Subscreen containers 1502-1510 are available for customer-specific subscreens; these subscreen containers correspond 1:1 to the screen groups S1502-S1510.

For example, the customer-specific screen 1001 should be assigned to subscreen container 1502 and thus screen group S1502. The program code would be:

IF sy-dynnr = '1502'.
   EV_DYNNR = '1001'.
ENDIF.

This functionality allows you to assign different customer-specific screens to the same screen group and use, via a suitable statement in the coding, to use it, for example, for different claim types or different warranty object types.

       5.      Enhance your screen by adding fields from structures GS_PNWTYH_DYNPRO (header data) and GS_PNWTYV_DYNPRO (version data) or from table GT_PVWTY_DYNPRO (item data) – transaction se51.

       6.      Assign the import parameters to the global variants or structures in include ZXWTYU03 (run through in PBO).

¡        GV_MODE = IV_MODE.

¡        Move-corresponding:
is_pnwtyh TO gs_pnwtyh_dynpro,
is_pnwtyh TO gs_pnwtyv_dynpro.

¡        gt_pvwty_dynpro[] = it_pvwty[].

       7.      Return the data to the function group in include ZXWTYU04 (run through in PAI).

If changes have been made in the warranty claim:

¡        EV_ACTIV = 'X'

¡        Move-corresponding:
gs_pnwtyh_dynpro TO es_pnwtyh,
gs_pnwtyv_dynpro TO es_pnwtyv.

¡        et_pvwty[] = gt_pvwty_dynpro[].

¡        If you have changed structures, you have to set the change flag:

Header data:
ES_PNWTYH-CHANGE_FLAG = 'C'.
Version data:
ES_PNWTYV-CHANGE_FLAG = 'C'.
Item data:
ET_PVWTY-CHANGE_FLAG = 'N'. (or 'C' or 'D')
N stands for new, C for changed and D for deleted.

       8.      Program the PAI and PBO modules.

       9.      Enter the new screen group in Customizing for Warranty Claim Processing under Layout ® Define Screen Layouts.

   10.      Activate your project (transaction CMOD).

If you have both a customer-specific screen in the header area and a customer-specific screen with header data on tab pages, you have to ensure that the data does not overwrite each other in the customer-specific function group XWTY.