FUNCTION ZCONVERT_SPOOL_2LOCAL_PDF.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(SPOOLNO) TYPE  TSP01-RQIDENT
*"     VALUE(P_FILE) TYPE  RLGRAP-FILENAME DEFAULT 'C:\FILE.PDF'
*"----------------------------------------------------------------------
*
* External Ref : RSTXPDFT4
*
DATA download VALUE 'X'.
DATA otf LIKE itcoo OCCURS 100 WITH HEADER LINE.
DATA cancel.
DATA pdf LIKE tline OCCURS 100 WITH HEADER LINE.
DATA doctab LIKE docs OCCURS 1 WITH HEADER LINE.
DATA: numbytes TYPE i,
        arc_idx LIKE toa_dara,
        pdfspoolid LIKE tsp01-rqident,
        jobname LIKE tbtcjob-jobname,
        jobcount LIKE tbtcjob-jobcount,
        is_otf.
DATA: client LIKE tst01-dclient,
        name LIKE tst01-dname,
        objtype LIKE rststype-type,
type LIKE rststype-type.
TABLES: tsp01.  SELECT SINGLE * FROM tsp01
WHERE rqident = spoolno.  IF sy-subrc <> 0.
MESSAGE e001(zmsd) WITH text-001.  " Fail
EXIT.
ENDIF.  client = tsp01-rqclient.
  name   = tsp01-rqo1name.
CALL FUNCTION 'RSTS_GET_ATTRIBUTES'
EXPORTING
            authority     = 'SP01'
client        = client
            name          = name
            part          = 1
IMPORTING
type          = type
            objtype       = objtype
EXCEPTIONS
            fb_error      = 1
            fb_rsts_other = 2
            no_object     = 3
            no_permission = 4.
IF objtype(3) = 'OTF'.
    is_otf = 'X'.
ELSE.
    is_otf = space.
ENDIF.  IF is_otf = 'X'.
CALL FUNCTION 'CONVERT_OTFSPOOLJOB_2_PDF'
EXPORTING
              src_spoolid              = spoolno
              no_dialog                = ' '
IMPORTING
              pdf_bytecount            = numbytes
              pdf_spoolid              = pdfspoolid
              btc_jobname              = jobname
              btc_jobcount             = jobcount
TABLES
              pdf                      = pdf
EXCEPTIONS
              err_no_otf_spooljob      = 1
              err_no_spooljob          = 2
              err_no_permission        = 3
              err_conv_not_possible    = 4
              err_bad_dstdevice        = 5
              user_cancelled           = 6
              err_spoolerror           = 7
              err_temseerror           = 8
              err_btcjob_open_failed   = 9
              err_btcjob_submit_failed = 10
              err_btcjob_close_failed  = 11.
CASE sy-subrc.
WHEN 0.
WHEN OTHERS.
MESSAGE e001(zmsd) WITH text-002.
"CONVERT_OTFSPOOLJOB_2_PDF Fail
EXIT.
ENDCASE.
ELSE.
CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
EXPORTING
              src_spoolid              = spoolno
              no_dialog                = ' '
IMPORTING
              pdf_bytecount            = numbytes
              pdf_spoolid              = pdfspoolid
              btc_jobname              = jobname
              btc_jobcount             = jobcount
TABLES
              pdf                      = pdf
EXCEPTIONS
              err_no_abap_spooljob     = 1
              err_no_spooljob          = 2
              err_no_permission        = 3
              err_conv_not_possible    = 4
              err_bad_destdevice       = 5
              user_cancelled           = 6
              err_spoolerror           = 7
              err_temseerror           = 8
              err_btcjob_open_failed   = 9
              err_btcjob_submit_failed = 10
              err_btcjob_close_failed  = 11.
CASE sy-subrc.
WHEN 0.
WHEN OTHERS.
MESSAGE e001(zmsd) WITH text-003.
"CONVERT_ABAPSPOOLJOB_2_PDF Fail
EXIT.
ENDCASE.
ENDIF.
*************** download PDF file ***********
CHECK download = 'X'.
IF NOT ( jobname IS INITIAL ).
EXIT.
ENDIF.
CALL FUNCTION 'WS_DOWNLOAD'
EXPORTING
            filename            = p_file
            filetype            = 'BIN'
            bin_filesize        = numbytes
TABLES
            data_tab            = pdf
EXCEPTIONS
            file_open_error     = 1
            file_write_error    = 2
            invalid_filesize    = 3
            invalid_table_width = 4
            invalid_type        = 5
            no_batch            = 6
            unknown_error       = 7
OTHERS              = 8.  IF sy-subrc <> 0.
MESSAGE 'Download local file fail!' type 'E' DISPLAY LIKE 'E'.    "Fail
ENDIF.
ENDFUNCTION.

FUNCTION ZGET_SO_OUTSTD.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(I_BUKRS) TYPE  BSID-BUKRS
*"     VALUE(I_KUNNR) TYPE  VBAK-KUNNR OPTIONAL
*"     VALUE(I_MATNR) TYPE  MARA-MATNR
*"     VALUE(I_AUART) TYPE  VBAK-AUART
*"  TABLES
*"      OUT_VBEP STRUCTURE  ZVBEP
*"  EXCEPTIONS
*"      NO_FOUND
*"----------------------------------------------------------------------
TABLES:
      vbrk,vbrp,lips.
DATA: l_index LIKE sy-tabix.
DATA: BEGIN OF  it_vbep OCCURS 0.
INCLUDE STRUCTURE Zvbep.
DATA: UEPOS like VBAP-UEPOS. "Heigh LEVEL
*DATA:   KWMENG  LIKE VBAP-KWMENG,
*        NETWR   LIKE VBAP-NETWR,
*        NETPR   LIKE VBAP-NETPR,
*        KPEIN   LIKE VBAP-KPEIN.
*DATA:   auart   LIKE vbak-auart.
*DATA:   blmng   LIKE vbep-bmeng. "Confirmed Qty
*DATA:   osmng   LIKE vbep-bmeng. "O/s Qty
*DATA:   matnr   LIKE vbap-matnr.
*DATA:   DMBSH   LIKE VBAP-NETWR.
*DATA:   WAERK   LIKE VBAP-WAERK.
DATA:   END OF  it_vbep.
data: lt_vbep like it_vbep OCCURS 0 WITH HEADER LINE.
SELECT * INTO CORRESPONDING FIELDS OF TABLE it_vbep
FROM vbak AS a
     INNER JOIN vbap AS b
ON a~vbeln = b~vbeln
     INNER JOIN vbep AS c
ON b~vbeln = c~vbeln
AND b~posnr = c~posnr
WHERE a~vkorg = I_BUKRS
and b~matnr = I_MATNR
AND c~bmeng > 0
AND c~ettyp = 'CP'
AND c~lfrel = 'X'.
if not it_vbep[] is INITIAL.
Loop at it_vbep.
READ TABLE lt_vbep with key vbeln = it_vbep-vbeln
                                   posnr = it_vbep-posnr
                                   matnr = it_vbep-matnr.
if sy-subrc eq 0.
         lt_vbep-WMENG = lt_vbep-WMENG + it_vbep-WMENG.
         lt_vbep-BMENG = lt_vbep-BMENG + it_vbep-BMENG.
modify lt_vbep index sy-tabix.
else.
MOVE-CORRESPONDING it_vbep to lt_vbep.
if it_vbep-uepos <= 0.
        lt_vbep-uepos = it_vbep-posnr.
endif.
append lt_vbep.
endif.
ENDloop.
endif.
it_vbep[] = lt_vbep[].
clear it_vbep.
LOOP AT it_vbep.
    l_index = sy-tabix.
IF it_vbep-auart EQ  I_auart.
PERFORM cal_delivery_qty  USING it_vbep-vbeln
                                      it_vbep-posnr
                                      it_vbep-vrkme
                                      it_vbep-matnr
CHANGING it_vbep-blmng.
     it_vbep-osmng = it_vbep-bmeng - it_vbep-blmng.
     it_vbep-DMBSH = ( it_vbep-bmeng - it_vbep-blmng ) * it_vbep-NETPR  / it_vbep-kpein.
ELSE.
PERFORM get_inv_qty USING it_vbep-vbeln
                                it_vbep-posnr
                                it_vbep-matnr
CHANGING it_vbep-blmng.
      it_vbep-osmng = it_vbep-bmeng - it_vbep-blmng.
      it_vbep-DMBSH = ( it_vbep-bmeng - it_vbep-blmng ) * it_vbep-NETPR  / it_vbep-kpein.
ENDIF.
modify it_VBEP index l_index.
ENDLOOP.
   OUT_VBEP[] = IT_VBEP[].
ENDFUNCTION.
*&---------------------------------------------------------------------*
*&      Form  CAL_DELIVERY_QTY
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*      -->RVBELN     text
*      -->RPOSNR     text
*      -->RVRKME     text
*      -->ZMATNR     text
*      -->RLFIMG     text
*----------------------------------------------------------------------*
FORM cal_delivery_qty USING rvbeln rposnr rvrkme zmatnr CHANGING rlfimg.
DATA: zlfart LIKE likp-lfart.
  rlfimg = 0.
SELECT *
FROM   lips CLIENT SPECIFIED
WHERE  mandt EQ sy-mandt AND vgbel EQ rvbeln AND vgpos EQ rposnr AND matnr = zmatnr.
SELECT SINGLE lfart INTO zlfart
FROM   likp CLIENT SPECIFIED
WHERE  mandt EQ sy-mandt AND vbeln EQ lips-vbeln AND lfart EQ 'LF'.
IF sy-subrc EQ 0.
IF lips-vrkme EQ rvrkme.
        rlfimg = rlfimg + lips-lfimg.
ELSE.
        rlfimg = rlfimg + ( lips-lfimg * lips-umvkz / lips-umvkn ).
ENDIF.
ENDIF.
ENDSELECT.
ENDFORM.                    "cal_delivery_qty
*&---------------------------------------------------------------------*
*&      Form  GET_INV_QTY
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*      -->ZAUBEL     text
*      -->ZAUPOS     text
*      -->ZMATNR     text
*      -->ZFKIMG     text
*----------------------------------------------------------------------*
FORM get_inv_qty USING zaubel zaupos zmatnr CHANGING zfkimg.
  zfkimg = 0.
SELECT * FROM vbrp CLIENT SPECIFIED
WHERE mandt EQ sy-mandt
AND aubel EQ zaubel
AND aupos EQ zaupos
AND matnr EQ zmatnr
AND shkzg NE 'X'. "Return item.
SELECT SINGLE * FROM vbap CLIENT SPECIFIED
WHERE mandt EQ sy-mandt
AND vbeln EQ vbrp-aubel
AND posnr EQ vbrp-aupos
AND matnr EQ zmatnr.
SELECT SINGLE * FROM vbrk CLIENT SPECIFIED
WHERE mandt EQ sy-mandt
AND vbeln EQ vbrp-vbeln
AND fksto NE 'X'. "Cancelled INV.
IF vbrk-fkart EQ 'F2' OR vbrk-fkart EQ 'ZF2'.
IF vbrp-vrkme EQ vbap-vrkme.
        zfkimg = zfkimg + vbrp-fkimg.
ELSE.
        zfkimg = zfkimg + ( vbrp-fkimg * vbrp-umvkz / vbrp-umvkn ).
ENDIF.
ELSEIF vbrk-fkart EQ 'S1'.
IF vbrp-vrkme EQ vbap-vrkme.
        zfkimg = zfkimg - vbrp-fkimg.
ELSE.
        zfkimg = zfkimg - ( vbrp-fkimg * vbrp-umvkz / vbrp-umvkn ).
ENDIF.
ENDIF.
ENDSELECT.
ENDFORM.                    "GET_INV_QTY

FUNCTION ZGET_SALES_OUSTANDING.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(SALESDOCUMENT) TYPE  VBAK-VBELN
*"     REFERENCE(I_POSNR) TYPE  VBAP-POSNR
*"  EXPORTING
*"     REFERENCE(EX_MSMNG) TYPE  VSMNG
*"----------------------------------------------------------------------
DATA: L_VSMNG LIKE vbepvb-vsmng.
Data: lT_VBFA type VBFA occurs 0 with header line,
      lT_VBUP type VBUP occurs 0 with header line,
      lT_VBEP type VBEPVB occurs 0 with header line,
      lT_VBAP type VBAPVB occurs 0 with header line.
SELECT * FROM vbup INTO TABLE lt_vbup
WHERE vbeln EQ salesdocument AND
posnr EQ i_posnr.
SELECT * FROM vbfa INTO TABLE lt_vbfa
WHERE vbelv EQ salesdocument AND
posnv EQ i_posnr.
SELECT * FROM vbep INTO TABLE lt_vbep
WHERE vbeln EQ salesdocument AND
posnr EQ i_posnr .
SELECT * FROM vbap INTO TABLE lt_vbap
WHERE vbeln EQ salesdocument AND
posnr EQ i_posnr .
call function 'RV_SCHEDULE_CHECK_DELIVERIES'
exporting
fbeleg = salesdocument
fposnr = i_posnr
tables
fvbfa = lt_vbfa
fvbup = lt_vbup
fxvbep = lt_vbep
fvbap = lt_vbap.
loop at lt_vbep where posnr eq i_posnr.
add lt_vbep-vsmng to l_vsmng. " tot.deliv.quan
endloop.
MOVE l_vsmng to EX_MSmng.
ENDFUNCTION.

*&---------------------------------------------------------------------*
*& Report  ZGET_SO_OS
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT  ZGET_SO_OS.
Data:
lT_VBFA type VBFA occurs 0 with header line,
lT_VBUP type VBUP occurs 0 with header line,
lT_VBEP type VBEPVB occurs 0 with header line,
lT_VBAP type VBAPVB occurs 0 with header line,
l_vsmng like vbepvb-vsmng.
PARAMETERS: P_VBELN LIKE VBAK-VBELN DEFAULT '8911000008',
            P_POSNR LIKE VBAP-POSNR DEFAULT '000010'.
START-OF-SELECTION.
SELECT * FROM vbup INTO TABLE lt_vbup
WHERE vbeln EQ p_vbeln AND
posnr EQ p_posnr.
SELECT * FROM vbfa INTO TABLE lt_vbfa
WHERE vbelv EQ p_vbeln AND
posnv EQ p_posnr.
SELECT * FROM vbep INTO TABLE lt_vbep
WHERE vbeln EQ p_vbeln AND
posnr EQ p_posnr .
SELECT * FROM vbap INTO TABLE lt_vbap
WHERE vbeln EQ p_vbeln AND
posnr EQ p_posnr .
call function 'RV_SCHEDULE_CHECK_DELIVERIES'
exporting
fbeleg = P_vbeln
fposnr = P_posnr
tables
fvbfa = lt_vbfa
fvbup = lt_vbup
fxvbep = lt_vbep
fvbap = lt_vbap.
loop at lt_vbep where posnr eq p_posnr.
add lt_vbep-vsmng to l_vsmng. " tot.deliv.quan
endloop.
WRITE: 'Delivered Qty is :' ,l_vsmng.
end-of-SELECTION.

Input formatThe values entered in the input fields on the screen must correspond to the data format of the corresponding screen field. For example, the format of a date field (type DATS) is eight characters and has the format YYYYMMDD. All of the characters must be numeric. MM must be 12 or less, and DD must be 31 or less. The system also checks that the specified day is valid for the month.
ABAP Dictionary ChecksIf you create an input field in the Screen Painter by copying an ABAP Dictionary field, the screen checks whether:
·        The value satisfies any foreign key relationship to another database table, that is, the system checks whether the value is contained in the check table as a foreign key. This is only checked if the Foreign key attribute is set in the Screen Painter for the input field. The input check is not necessarily identical with the input help. The programmer is responsible for ensuring that the input help presents values that will all pass any foreign key check.
·        That the value is one of the fixed values of the domain of the fields, that is, the system checks the definition of the underlying domain in the ABAP Dictionary. The fixed values of the domain can also be used as input help. However, the value table of a domain is not checked. It is only used as a default value for the check tables of the fields that refer to the domain.

Automatic input checks
PROGRAM demo_dynpro_automatic_checks.
DATA: ok_code TYPE sy-ucomm,
      date TYPE d.
TABLES demo_conn.
CALL SCREEN 100.
MODULE init_screen_100 OUTPUT.
  SET PF-STATUS 'STATUS_100'.
ENDMODULE.
MODULE cancel INPUT.
  LEAVE PROGRAM.
ENDMODULE.
MODULE pai INPUT.
  MESSAGE i888(sabapdocu) WITH text-001.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:

The date field date from the program is assigned to the input field Date. The other input fields are the CARRID; CONNID, and MARK components of the ABAP Dictionary structure DEMO_CONN. All of the fields are mandatory. The function code of the pushbutton is EXECUTE.
In the GUI status STATUS_100, the icon (F12) is active with function code CANCEL and function type E. Furthermore, the function key F8 is assigned to the function code EXECUTE.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
  MODULE init_screen_100.
PROCESS AFTER INPUT.
  MODULE cancel AT EXIT-COMMAND.
  MODULE pai.
The user must fill all of the input fields with valid values before the PAI module can be called:
·         All of the input fields must contain values
·         The date entry must have the correct format
·         The airline must be in the check table SCARR
·         The flight number must exist for the corresponding airline in the check table SPFLI
·         The selection MARK must be one of the fixed values of the domain S_FLAG.
The user can leave the screen using Cancel (, F12) without entering all values correctly, since the module call is programmed using AT EXIT-COMMAND.




Checking Input in the Screen Flow Logic   There are two special variants of the FIELDstatement that you can use in PAI processing to check the values of screen fields in the screen flow logic. However, this method is obsolete and should no longer be used. It is only supported for compatibility reasons.
Checking a Value ListYou can check a screen field against a value list as follows:
FIELD f VALUES (v1, v2,...).
The individual entries v1, v2,... in the list can have the following format:
·        [NOT] val
·        [NOT] BETWEEN val1 AND val2
You can check against single fields val or intervals between val1 and val2. The comparison fields must have the value range of data type CHAR or NUMC, must be enclosed in inverted commas, and must be written in uppercase. If the check fails, an error message is displayed and the corresponding field is again ready for entry.
The input help for f can also use the value list in the FIELD statement. This helps the user to enter only correct values.
The functions of the FIELD statement for controlling data transport also apply when you use the VALUES addition.
Checking Against Database TablesYou can compare a screen field with a database table follows:
FIELD f SELECT   *
            FROM  dbtab
            WHERE k1 = f1 AND k2 = f2 AND...
            [INTO  tables_area]
            WHENEVER [NOT] FOUND SEND ERRORMESSAGE|WARNING
                                      [num [WITH h1 ... h4]].
The FIELD statement is combined with a SELECTstatement. The syntax of the SELECT statement must be entered exactly as shown above. In the WHERE condition, no comparison operators other than the equals sign (=) are allowed, not even EQ. In the WHEREcondition, the fields of the primary key k1 k2 ... of the database table dbtab are checked against the screen fields f1 f2 ... If a matching entry is found, you can write it into the table work area of a screen field, which was defined by transfer from the ABAP Dictionary. You can also send an error or warning message depending on the outcome of the search, which makes the input field for f ready for input again.
num allows you to specify a message number from the message class specified in the MESSAGE-ID addition of the first statement in the program. In this case, the message class can only be two characters long. If you do not specify a message class, the system displays a default message. If you use WITH, you can pass literals or screen fields to any placeholders (&) within the message.
The input help for f can also use the SELECT statement after FIELD. This helps the user to enter only correct values.
You can also use the SELECT statement in screen flow logic without combining it with the FIELD statement. This allows you to fill screen fields with the contents of database tables without calling ABAP modules. The functions of the FIELD statement for controlling data transport also apply when you use SELECT.

Checking Inputs in the Screen Flow Logic
PROGRAM demo_dynpro_value_select MESSAGE-ID dw.
DATA: ok_code TYPE sy-ucomm,
      carrier TYPE spfli-carrid,
      connect TYPE spfli-connid.
CALL SCREEN 100.
MODULE init_screen_0100 OUTPUT.
  SET PF-STATUS 'STATUS_100'.
ENDMODULE.
MODULE cancel INPUT.
  LEAVE PROGRAM.
ENDMODULE.
MODULE module_1 INPUT.
  MESSAGE i888(sabapdocu) WITH text-001 carrier
                        text-002 connect.
ENDMODULE.
MODULE module_2 INPUT.
  MESSAGE i888(sabapdocu) WITH text-001 carrier
                        text-002 connect.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:

The program fields carrier and connect are assigned to the input fields. The function code of the pushbutton is EXECUTE.
In the GUI status STATUS_100, the icon (F12) is active with function code CANCEL and function type E. Furthermore, the function key F8 is assigned to the function code EXECUTE.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
  MODULE init_screen_0100.
PROCESS AFTER INPUT.
  MODULE cancel AT EXIT-COMMAND.
  FIELD carrier VALUES (NOT 'AA', 'LH', BETWEEN 'QF' AND 'UA').
  MODULE module_1.
  FIELD connect SELECT  *
                  FROM  spfli
                  WHERE carrid = carrier AND connid = connect
                  WHENEVER NOT FOUND SEND ERRORMESSAGE 107
                                          WITH carrier connect.
  MODULE module_2.
The user must enter a value for carrier that is in the list following VALUES before module_1 is called. When module_1 is called, connect has not yet been transported.
Next, the user can only enter a value for connect that exists in the database table SPFLI as part of a primary key together with carrier. If not, error message 107 from message class AT is displayed in the status bar:
Unable to find any entries for key & &.
Only when a correct value has been entered will connect be transported and module_2 called.



Input Checks in Dialog Modules   You cannot perform input checks in PAI modules of programs until you have transported the contents of the input fields to the ABAP program. You can then use logical expressions to check the values that the user entered. You should then allow the user to correct any wrong entries before calling further modules.
You can do this by sending warning (type W) or error (type E) messages from PAI modules that are called in conjunction with the statements FIELD and CHAIN.
Checking Single FieldsIf you send a warning or error message from a module mod  that you called using a FIELDstatement as follows:
FIELD f MODULE mod.
the corresponding input field on the current screen is made ready for input again, allowing the user to enter a new value. If the field is only checked once, the PAI processing continues directly after the FIELDstatement, and the preceding modules are not called again.
Checking a Set of FieldsIf a warning or an error message is sent in a module mod1 mod2 … that you called within a processing chain:
CHAIN.
  FIELD: f1, f2,...
  MODULE mod1.
  FIELD: g1, g2,...
  MODULE mod2.
...
ENDCHAIN.
all of the input fields on the current screen that belong to the processing chain are made ready for input again – including those that are in FIELD statements after the MODULEstatement. All the other fields are not ready for input.  Even if a MODULE statement appears within a processing chain, combined with a FIELD statement, all of the input fields in the chain are made ready for input again – not just the field in question. The user can repeat the input. If the fields in the processing chain are only checked once, the PAI processing continues directly after the automatic checks at the CHAINstatement, and the preceding modules are not called again.
Controlling Input and Data TransportIf you use the FIELD statement outside a processing chain, only a single field is made ready for input when a warning or error message is displayed. If you use FIELD statements between CHAIN - ENDCHAIN, this controls a set of fields. All of the fields controlled by a FIELDstatement are transported back to the screen, bypassing PBO processing. This means that any changes made to the field contents before the message become visible on the screen. This also applies to information
Checking Fields RepeatedlyYou may sometimes need to specify the same field in more than one FIELD or CHAIN statement. If one of the corresponding modules sends a warning or error message, PAI processing resumes with the value that the user corrected. However, in this case, processing cannot simply resume at the corresponding FIELD or CHAIN statement if the field in question has already been included in an earlier FIELD or CHAIN statement.
Instead, all of the FIELD and CHAIN statements containing a field in which an error occurred are repeated. PAI processing resumes at the first FIELD or CHAINstatement containing one or several of the fields in which the error occurred and that the user changed the last time the screen was displayed.
         PROCESS AFTER INPUT.
         FIELD f1 MODULE m1.
         FIELD f2 MODULE m2.
         CHAIN.
            FIELD: f1, f2, f3.
            FIELD: f4, f5, f1.
            MODULE m3.
            MODULE m4.
         ENDCHAIN.
         CHAIN.
            FIELD: f6.
            MODULE m5.
         ENDCHAIN.
         CHAIN.
            FIELD f4.
            MODULE m6.
         ENDCHAIN.
If module m6contains a warning or error message, the screen is displayed again, after which processing resumes with the first CHAIN statement. Module m3 is called since this is the first occurrence of the field f4.
Remaining Functions in the FIELD StatementAll of the functions of the FIELD and CHAINstatements for controlling data transport and conditional module calls can also be used in combination with warning and error messages. The contents of each field are transported at the FIELD statement in which the field occurs. If a warning or error message occurs in a conditional module of a processing chain, all of the fields in that chain will be ready for input when the screen is redisplayed, although not all of the fields will have been transported.
If a warning or error message occurs in a module that is not linked with a FIELD or CHAIN statement, none of the fields on the screen will be ready for input. In this case, the user can only exit the program, but only if a corresponding unconditional module call is provided.

Input Checks in Dialog Modules
PROGRAM demo_dynpro_field_chain.
DATA: ok_code TYPE sy-ucomm,
      input1 TYPE i, input2 TYPE i, input3 TYPE i,
      input4 TYPE i, input5 TYPE i, input6 TYPE i,
      sum TYPE i.
CALL SCREEN 100.
MODULE init_screen_100 OUTPUT.
  CLEAR: input1, input2, input3, input4, input5, input6.
  SET PF-STATUS 'STATUS_100'.
ENDMODULE.
MODULE cancel INPUT.
  LEAVE PROGRAM.
ENDMODULE.
MODULE module_1 INPUT.
  IF input1 < 50.
    MESSAGE e888(sabapdocu) WITH text-001 '50' text-002.
  ENDIF.
ENDMODULE.
MODULE module_2 INPUT.
  IF input2 < 100.
    MESSAGE e888(sabapdocu) WITH text-001 '100' text-002.
  ENDIF.
ENDMODULE.
MODULE module_3 INPUT.
  IF input3 < 150.
    MESSAGE e888(sabapdocu) WITH text-001 '150' text-002.
  ENDIF.
ENDMODULE.
MODULE chain_module_1 INPUT.
  IF input4 < 10.
    MESSAGE e888(sabapdocu) WITH text-003 '10' text-002.
  ENDIF.
ENDMODULE.
MODULE chain_module_2 INPUT.
  CLEAR sum.
  sum = sum + : input4, input5, input6.
  IF sum <= 100.
    MESSAGE e888(sabapdocu) WITH text-004 '100' text-002.
  ENDIF.
ENDMODULE.
MODULE execution INPUT.
  MESSAGE i888(sabapdocu) WITH text-005.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:

The screen fields input1 through input6 are assigned to the input fields. The function code of the pushbutton is EXECUTE.
In the GUI status STATUS_100, the icon (F12) is active with function code CANCEL and function type E. Furthermore, the function key F8 is assigned to the function code EXECUTE with the function type <blank>.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
  MODULE init_screen_100.
PROCESS AFTER INPUT.
  MODULE cancel AT EXIT-COMMAND.
  FIELD input1 MODULE module_1.
  FIELD input2 MODULE module_2.
  FIELD input3 MODULE module_3.
  CHAIN.
    FIELD input4.
    MODULE chain_module_1.
    FIELD input5.
    FIELD input6 MODULE chain_module_2.
  ENDCHAIN.
  MODULE EXECUTION.
This program demonstrates how you can check input fields in dialog modules.
The fields input1 through input3 are checked independently of each other in the modules module_1 through module_3. As long as the user does not enter a corresponding value, the screen is repeatedly displayed with the appropriate field ready for input.
The fields input4 through input6 are checked together in a processing chain. If input4 does not satisfy the condition in chain_module_1, all three fields are again ready for input. The same applies if the three fields do not satisfy the condition in chain_module_2.
The EXECUTION module, from which an information message is displayed, is not executed until all six fields satisfy the appropriate conditions.