SAMPLE_PROCESS_00511074 SAP Function module

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

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

Pattern for FM SAMPLE_PROCESS_00511074 - SAMPLE PROCESS 00511074

CALL FUNCTION 'SAMPLE_PROCESS_00511074' "
  EXPORTING
    iv_event =                  " c
    iv_scenario =               " char01
*   iv_popup =                  " char01
*   iv_updkz =                  " updkz_d
*   is_vbak =                   " vbak
*   is_bapisdhd1 =              " bapisdhd1
  IMPORTING
    ev_scenario =               " char01
    ev_popup =                  " char01
* CHANGING
*   cs_sales_view =             " order_view
    .  "  SAMPLE_PROCESS_00511074

ABAP code example for Function Module SAMPLE_PROCESS_00511074

The ABAP code below is a full code listing to execute function module SAMPLE_PROCESS_00511074 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_ev_scenario  
 
 TYPE CHAR01
,
ld_ev_popup  
 
 TYPE CHAR01
.


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

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

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

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

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

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

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

CALL FUNCTION 'SAMPLE_PROCESS_00511074'
  EXPORTING
    iv_event =                   ld_iv_event
    iv_scenario =                ld_iv_scenario
*   iv_popup =                   ld_iv_popup
*   iv_updkz =                   ld_iv_updkz
*   is_vbak =                    ld_is_vbak
*   is_bapisdhd1 =               ld_is_bapisdhd1
  IMPORTING
    ev_scenario =                ld_ev_scenario
    ev_popup =                   ld_ev_popup
* CHANGING
*   cs_sales_view =              ld_cs_sales_view
    .  "  SAMPLE_PROCESS_00511074

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_cs_sales_view
 
 TYPE ORDER_VIEW ,
ld_ev_scenario
 
 TYPE CHAR01 ,
ld_iv_event
 
 TYPE C ,
ld_ev_popup
 
 TYPE CHAR01 ,
ld_iv_scenario
 
 TYPE CHAR01 ,
ld_iv_popup
 
 TYPE CHAR01 ,
ld_iv_updkz
 
 TYPE UPDKZ_D ,
ld_is_vbak
 
 TYPE VBAK ,
ld_is_bapisdhd1
 
 TYPE BAPISDHD1 .


ld_cs_sales_view = 'Check type of data required'.
ld_iv_event = 'Check type of data required'.
ld_iv_scenario = 'Check type of data required'.
ld_iv_popup = 'Check type of data required'.
ld_iv_updkz = 'Check type of data required'.
ld_is_vbak = 'Check type of data required'.
ld_is_bapisdhd1 = 'Check type of data required'.