PT_GUI_WORKSCHEDULE_POPUP SAP Function module

PT_GUI_WORKSCHEDULE_POPUP is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name PT_GUI_WORKSCHEDULE_POPUP into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: PT_GUI_WORKSCHEDULE
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM PT_GUI_WORKSCHEDULE_POPUP - PT GUI WORKSCHEDULE POPUP

CALL FUNCTION 'PT_GUI_WORKSCHEDULE_POPUP' "
  EXPORTING
    p_datum =                   " datum
    p_tprog =                   " tprog
    p_varia =                   " varia
    p_tagty =                   " tagty
    p_ftkla =                   " ftkla
    p_zeity =                   " dzeity
    p_mofid =                   " hident
    p_mosid =                   " mosid
    p_schkz =                   " schkn
    .  "  PT_GUI_WORKSCHEDULE_POPUP

ABAP code example for Function Module PT_GUI_WORKSCHEDULE_POPUP

The ABAP code below is a full code listing to execute function module PT_GUI_WORKSCHEDULE_POPUP including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA(ld_p_datum) = 'Check type of data required'.

DATA(ld_p_tprog) = 'Check type of data required'.

DATA(ld_p_varia) = 'Check type of data required'.

DATA(ld_p_tagty) = 'Check type of data required'.

DATA(ld_p_ftkla) = 'Check type of data required'.

DATA(ld_p_zeity) = 'Check type of data required'.

DATA(ld_p_mofid) = 'Check type of data required'.

DATA(ld_p_mosid) = 'Check type of data required'.

DATA(ld_p_schkz) = 'Check type of data required'.
.

CALL FUNCTION 'PT_GUI_WORKSCHEDULE_POPUP'
  EXPORTING
    p_datum =                    ld_p_datum
    p_tprog =                    ld_p_tprog
    p_varia =                    ld_p_varia
    p_tagty =                    ld_p_tagty
    p_ftkla =                    ld_p_ftkla
    p_zeity =                    ld_p_zeity
    p_mofid =                    ld_p_mofid
    p_mosid =                    ld_p_mosid
    p_schkz =                    ld_p_schkz
    .  "  PT_GUI_WORKSCHEDULE_POPUP

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_p_datum
 
 TYPE DATUM ,
ld_p_tprog
 
 TYPE TPROG ,
ld_p_varia
 
 TYPE VARIA ,
ld_p_tagty
 
 TYPE TAGTY ,
ld_p_ftkla
 
 TYPE FTKLA ,
ld_p_zeity
 
 TYPE DZEITY ,
ld_p_mofid
 
 TYPE HIDENT ,
ld_p_mosid
 
 TYPE MOSID ,
ld_p_schkz
 
 TYPE SCHKN .


ld_p_datum = 'Check type of data required'.
ld_p_tprog = 'Check type of data required'.
ld_p_varia = 'Check type of data required'.
ld_p_tagty = 'Check type of data required'.
ld_p_ftkla = 'Check type of data required'.
ld_p_zeity = 'Check type of data required'.
ld_p_mofid = 'Check type of data required'.
ld_p_mosid = 'Check type of data required'.
ld_p_schkz = 'Check type of data required'.