1.1.2 Possible Operations in Child screen

This topic briefs the important considerations to be made when designing a Child screen.

Note the following while designing a Child screen:

• The developer will not be allowed to delete or rename elements created in the parent function.
• New data sources or adding columns to existing data sources are allowed.
• The addition of new LOVs and modification of existing LOVs are allowed.
• Modifying properties of existing block fields(of the parent) is allowed.
• New Screens, tabs, sections, etc can be added by the developer.
• Deletion and Renaming of screens, tabs, sections, etc are not allowed. Instead, the developer has the option to hide them.
• Addition or removal of fields from fieldset is allowed. Properties of fields can also be modified. Note that the block to which the fieldset is attached cannot be changed at the child level.
• New fieldsets can be defined.
• The developer can add a new Launch Form and Call Form in the child screen. The existing launch Form/Call form can be made inactive, if not required at the child level.
• Amendable fields can be modified.
• The summary screen can also be completely redesigned at the child level.

Note:

If enhancement on the parent screen happens parallel to the child screen design developer can use the child refresh option to upgrade the latest changes in the parent screen to the child screen.

The Child screen design is similar to normal screen design. Refer to the Development Workbench – Screen Development I document for the detailed information.