RHPA_APP_PROCESS_FINAL_PATTERN SAP Function module

RHPA_APP_PROCESS_FINAL_PATTERN 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 RHPA_APP_PROCESS_FINAL_PATTERN into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM RHPA_APP_PROCESS_FINAL_PATTERN - RHPA APP PROCESS FINAL PATTERN

CALL FUNCTION 'RHPA_APP_PROCESS_FINAL_PATTERN' "
* EXPORTING
*   plvar =                     " p1000-plvar   Plan Version
*   objid =                     " p1000-objid   Appraisal ID
*   vtask = 'D'                 " hrrhap-vtask  Update (B=Buffer,D=Online,V=Update,S=Sync)
*   check_dialogue = ' '        " char1
*   no_dialogue = 'X'           " char1
  IMPORTING
    e_dialogue =                " char1
  EXCEPTIONS
    CANCELLED = 1               "               Function aborted
    ERROR = 2                   "
    .  "  RHPA_APP_PROCESS_FINAL_PATTERN

ABAP code example for Function Module RHPA_APP_PROCESS_FINAL_PATTERN

The ABAP code below is a full code listing to execute function module RHPA_APP_PROCESS_FINAL_PATTERN 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_e_dialogue  
 
 TYPE CHAR1
.



DATA(ld_plvar) = some text here


DATA(ld_objid) = Check type of data required


DATA(ld_vtask) = some text here

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

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

CALL FUNCTION 'RHPA_APP_PROCESS_FINAL_PATTERN'
* EXPORTING
*   plvar =                      ld_plvar
*   objid =                      ld_objid
*   vtask =                      ld_vtask
*   check_dialogue =             ld_check_dialogue
*   no_dialogue =                ld_no_dialogue
  IMPORTING
    e_dialogue =                 ld_e_dialogue
  EXCEPTIONS
    CANCELLED =                  1
    ERROR =                      2
    .  "  RHPA_APP_PROCESS_FINAL_PATTERN

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
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_e_dialogue
 
 TYPE CHAR1 ,
ld_plvar
 
 TYPE P1000-PLVAR ,
ld_objid
 
 TYPE P1000-OBJID ,
ld_vtask
 
 TYPE HRRHAP-VTASK ,
ld_check_dialogue
 
 TYPE CHAR1 ,
ld_no_dialogue
 
 TYPE CHAR1 .



ld_plvar = some text here

ld_objid = Check type of data required

ld_vtask = some text here
ld_check_dialogue = 'Check type of data required'.
ld_no_dialogue = 'Check type of data required'.