4 Screen Development

This topic describes about the Lunch Forms Screen Development

Technically Launch Forms are the same as normal maintenance or transaction screens. There is no difference in the development of a launch form from a maintenance or transaction screen.

Launch forms can be designed as of type

  1. Maintenance
  2. Transaction

Note:

A maintenance launch form can be used if it is invoked from maintenance screens and similarly for transaction launch forms.

Naming Convention

Launch Form is nothing but a normal function Id. So it has to follow the same naming convention as any other detail screen. Third letter has to be ‘D’ and it should have 8 characters.

Example: CSDEVENT, CSDACCNT are valid names for a Launch Form screen

Menu details has to be provided for the Launch form screen as it is a an independent screen . Entries has to be present in smtb_function_description unlike Call Forms

Refer documents on screen development, development of maintenance and transaction screens for designing a Launch Form screens

Screen Arguments

Screen Arguments has to be maintained for the main screen of the launch form. Launch Forms are used only for querying data. Hence ACTION_CODE has to be passed as a screen argument with argument value as EXECUTEQUERY and the Primary Key values for querying in launch Form screen should be passed as the other parameters.

Generated units

All the units for a normal maintenance or transaction screen will be generated for a Launch Form screen as well.

Note the following while deploying units for Launch Forms

  • Entry has to be made manually in CSTB_CALL_FORM_NODES for the launch form. The script won’t be generated by the Tool while designing the Launch Form. Hence it has to be inserted manually providing the screen arguments as maintained for Launch Form main screen Screen arguments has to be inserted in the SCREEN_ARGS column of CSTB_CALL_FORM_NODES separated by a tilde (~)