3.2, sub-screen 210
The subscreen is used to output the basic information of the customer, including the customer's city, address, contact name, phone number, etc.
1) Screen basic properties
Referring to the main screen 110, after entering the program name and screen number in the initial screen designer interface, click Create, the properties interface shown in FIG. 9-26 will be displayed, change the screen type to "child screen", and the rest remains unchanged.
FIG. 9-26 Subscreen 210 basic properties
2) Screen format design
Add the city, address, contact name, phone number fields (as shown in Figure 9-27) of the customer table ZTCUSTOMER (as shown in Figure 9-27) to the screen through the "Dictionary/Program Data Element" button, and adjust the position of the element, which is shown in Figure 9-28 after completion.
FIG. 9-27 adds sub-screen 210 interface elements
FIG. 9- 28 subscreen 210 interface elements
3) List of screen elements
After the screen format design is completed, the list of visible data elements is shown in Figure 9-29.
Figure 9-29 Subscreen 210 element list
4) Screen logic flow
LOOKING AT THE SCREEN LOGIC FLOW, THE DEFAULT PBO AND PAI EVENTS ARE INCLUDED HERE, BECAUSE THE DATA ACQUISITION AND TOOLBAR OPERATION HAS BEEN IMPLEMENTED BY THE LOGIC FLOW OF THE SCREEN 100, THIS SUB-SCREEN 210 DOES NOT NEED TO BE DEFINED, SO THE DEFAULT CAN BE, 2 MODULES REMAIN IN THE COMMENT STATE.
Figure 9-30 sub-screen 210 logic flow
3.3, subscreen 220
Referring to the process of establishing a subscreen 210 to establish a subscreen 220, the screen is described as a "customer order", the type is also subscreen.
1) Screen format design
Click the table control, then drag in the client area to specify the table area, and name the table control "ORDER_ITEMS", and then through the "dictionary program element", get the field that needs to be output from the order table ZTORDERS_H (as shown in Figure 9-30) and place it in the table control area, and the result is shown in Figure 9-31.
FIG. 9-31 Add dictionary program elements to the subscreen 220
Figure 9- 32 Sub-screen 220 format design
2) List of screen elements
After completing the format design of the sub-screen 220, the list of elements is shown in FIG. 9-32.
Figure 9- 33 Sub-screen 220 element list
3) Screen logic flow
The logic flow code of the sub-screen 220 is as follows, wherein the LOOP AT statement of PBO is to read the record of a customer's related order in the order_tab of the inner table before the output of the customer's order detail data interface, and transfer it to the ztorders_h structure contained in the table control order_items, so that the corresponding data can be displayed; The data order_tab the inner table can be processed through PAI events.
According to the screen design specification, if a table control is used in the screen, then the LOOP AT statement must be included in the PBO and PAI, even if the function is not implemented (such as PAI's LOOP AT in this practice).