SAP RERA_POPUP_VIMI16_DETAIL Function Module for









RERA_POPUP_VIMI16_DETAIL is a standard rera popup vimi16 detail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for rera popup vimi16 detail FM, simply by entering the name RERA_POPUP_VIMI16_DETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVMA01
Program Name: SAPLFVMA01
Main Program: SAPLFVMA01
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RERA_POPUP_VIMI16_DETAIL pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'RERA_POPUP_VIMI16_DETAIL'"
EXPORTING
IV_SACTNR = "
* IV_VIMI17 = "
* IV_COMMIT_DATE = "
* IV_REJECT_DATE = "
* IV_SET_LOCK = ' ' "
* IV_TIV11 = "
* IV_DGAB_FROM = "
* IV_DGAB_TILL = "

IMPORTING
EV_ANSWER = "

CHANGING
CR_VIMI16 = "

EXCEPTIONS
ADJUSTMENT_LOCKED = 1 PERMISSION_DENIED = 2
.



IMPORTING Parameters details for RERA_POPUP_VIMI16_DETAIL

IV_SACTNR -

Data type: VVSACTNR
Optional: No
Call by Reference: No ( called with pass by value option)

IV_VIMI17 -

Data type: VIMI17
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_COMMIT_DATE -

Data type: VIMI16-DZUSTIM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_REJECT_DATE -

Data type: VIMI16-DREJECT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SET_LOCK -

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TIV11 -

Data type: TIV11
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DGAB_FROM -

Data type: D
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DGAB_TILL -

Data type: D
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RERA_POPUP_VIMI16_DETAIL

EV_ANSWER -

Data type: CHAR01
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for RERA_POPUP_VIMI16_DETAIL

CR_VIMI16 -

Data type: VIMI16
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ADJUSTMENT_LOCKED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PERMISSION_DENIED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RERA_POPUP_VIMI16_DETAIL Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_cr_vimi16  TYPE VIMI16, "   
lv_ev_answer  TYPE CHAR01, "   
lv_iv_sactnr  TYPE VVSACTNR, "   
lv_adjustment_locked  TYPE VVSACTNR, "   
lv_iv_vimi17  TYPE VIMI17, "   
lv_permission_denied  TYPE VIMI17, "   
lv_iv_commit_date  TYPE VIMI16-DZUSTIM, "   
lv_iv_reject_date  TYPE VIMI16-DREJECT, "   
lv_iv_set_lock  TYPE XFELD, "   ' '
lv_iv_tiv11  TYPE TIV11, "   
lv_iv_dgab_from  TYPE D, "   
lv_iv_dgab_till  TYPE D. "   

  CALL FUNCTION 'RERA_POPUP_VIMI16_DETAIL'  "
    EXPORTING
         IV_SACTNR = lv_iv_sactnr
         IV_VIMI17 = lv_iv_vimi17
         IV_COMMIT_DATE = lv_iv_commit_date
         IV_REJECT_DATE = lv_iv_reject_date
         IV_SET_LOCK = lv_iv_set_lock
         IV_TIV11 = lv_iv_tiv11
         IV_DGAB_FROM = lv_iv_dgab_from
         IV_DGAB_TILL = lv_iv_dgab_till
    IMPORTING
         EV_ANSWER = lv_ev_answer
    CHANGING
         CR_VIMI16 = lv_cr_vimi16
    EXCEPTIONS
        ADJUSTMENT_LOCKED = 1
        PERMISSION_DENIED = 2
. " RERA_POPUP_VIMI16_DETAIL




ABAP code using 7.40 inline data declarations to call FM RERA_POPUP_VIMI16_DETAIL

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
"SELECT single DZUSTIM FROM VIMI16 INTO @DATA(ld_iv_commit_date).
 
"SELECT single DREJECT FROM VIMI16 INTO @DATA(ld_iv_reject_date).
 
DATA(ld_iv_set_lock) = ' '.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!