SAP Function Modules

comments icon Comments

RET1_VIMI16_SELECT_SINGLE SAP Function module







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

Associated Function Group: RET1
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM RET1_VIMI16_SELECT_SINGLE - RET1 VIMI16 SELECT SINGLE 





CALL FUNCTION 'RET1_VIMI16_SELECT_SINGLE' "
  EXPORTING
    iv_sanpnr =                 " tiv11-sanpnr
    iv_bukrs =                  " vimimv-bukrs
    iv_swenr =                  " vimimv-swenr
    iv_smenr =                  " vimimv-smenr
*   iv_skoart = 10              " tzk01-skoart
*   iv_date = SY-DATUM          " sy-datum
*   iv_objtype = ' '            " vvsanpme
*   ir_vimi01 =                 " vimi01
*   ir_viob01 =                 " viob01
  IMPORTING
    er_vimi16 =                 " vimi16
    er_vimi17 =                 " vimi17
* TABLES
*   et_protocol =               " sprot_u
*   et_messages =               " rfvimamesg
  EXCEPTIONS
    COMPUTATION_FAILED = 1      "
    .  "  RET1_VIMI16_SELECT_SINGLE

ABAP code example for Function Module RET1_VIMI16_SELECT_SINGLE





The ABAP code below is a full code listing to execute function module RET1_VIMI16_SELECT_SINGLE 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_er_vimi16    TYPE VIMI16
,
ld_er_vimi17    TYPE VIMI17
,
it_et_protocol    TYPE STANDARD TABLE OF SPROT_U,"TABLES PARAM
wa_et_protocol  LIKE LINE OF it_et_protocol
,
it_et_messages    TYPE STANDARD TABLE OF RFVIMAMESG,"TABLES PARAM
wa_et_messages  LIKE LINE OF it_et_messages
.



 

SELECT single SANPNR 
  FROM TIV11 
  INTO @DATA(ld_iv_sanpnr).

 

SELECT single BUKRS 
  FROM VIMIMV 
  INTO @DATA(ld_iv_bukrs).

 

SELECT single SWENR 
  FROM VIMIMV 
  INTO @DATA(ld_iv_swenr).

 

SELECT single SMENR 
  FROM VIMIMV 
  INTO @DATA(ld_iv_smenr).

 

SELECT single SKOART 
  FROM TZK01 
  INTO @DATA(ld_iv_skoart).


DATA(ld_iv_date) = '20210129'.

DATA(ld_iv_objtype) = '20210129'.

DATA(ld_ir_vimi01) = '20210129'.

DATA(ld_ir_viob01) = '20210129'.
 

"populate fields of struture and append to itab
append wa_et_protocol to it_et_protocol.
 

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.
.

CALL FUNCTION 'RET1_VIMI16_SELECT_SINGLE'
  EXPORTING
    iv_sanpnr =                  ld_iv_sanpnr
    iv_bukrs =                   ld_iv_bukrs
    iv_swenr =                   ld_iv_swenr
    iv_smenr =                   ld_iv_smenr
*   iv_skoart =                  ld_iv_skoart
*   iv_date =                    ld_iv_date
*   iv_objtype =                 ld_iv_objtype
*   ir_vimi01 =                  ld_ir_vimi01
*   ir_viob01 =                  ld_ir_viob01
  IMPORTING
    er_vimi16 =                  ld_er_vimi16
    er_vimi17 =                  ld_er_vimi17
* TABLES
*   et_protocol =                it_et_protocol
*   et_messages =                it_et_messages
  EXCEPTIONS
    COMPUTATION_FAILED =         1
    .  "  RET1_VIMI16_SELECT_SINGLE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_er_vimi16  TYPE VIMI16 ,
ld_iv_sanpnr  TYPE TIV11-SANPNR ,
it_et_protocol  TYPE STANDARD TABLE OF SPROT_U ,
wa_et_protocol  LIKE LINE OF it_et_protocol,
ld_er_vimi17  TYPE VIMI17 ,
ld_iv_bukrs  TYPE VIMIMV-BUKRS ,
it_et_messages  TYPE STANDARD TABLE OF RFVIMAMESG ,
wa_et_messages  LIKE LINE OF it_et_messages,
ld_iv_swenr  TYPE VIMIMV-SWENR ,
ld_iv_smenr  TYPE VIMIMV-SMENR ,
ld_iv_skoart  TYPE TZK01-SKOART ,
ld_iv_date  TYPE SY-DATUM ,
ld_iv_objtype  TYPE VVSANPME ,
ld_ir_vimi01  TYPE VIMI01 ,
ld_ir_viob01  TYPE VIOB01 .





SELECT single SANPNR 
  FROM TIV11 
  INTO ld_iv_sanpnr.
 

"populate fields of struture and append to itab
append wa_et_protocol to it_et_protocol.

SELECT single BUKRS 
  FROM VIMIMV 
  INTO ld_iv_bukrs.
 

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.

SELECT single SWENR 
  FROM VIMIMV 
  INTO ld_iv_swenr.


SELECT single SMENR 
  FROM VIMIMV 
  INTO ld_iv_smenr.


SELECT single SKOART 
  FROM TZK01 
  INTO ld_iv_skoart.

ld_iv_date = '20210129'.
ld_iv_objtype = '20210129'.
ld_ir_vimi01 = '20210129'.
ld_ir_viob01 = '20210129'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name RET1_VIMI16_SELECT_SINGLE or its description.


   
 

RET1_VIMI16_SELECT_SINGLE - 
RET1_VIKOKO_SELECT_SINGLE - 
RET1_SET_FLAGS - 
RET1_READ_GRUNDBUCH - 
RET1_RA_SELECTION_SCREEN - 
RET1_PROCESS_ALV_DIALOG -