SAP IMMO_PM_KEY_TRANSFER Function Module for









IMMO_PM_KEY_TRANSFER is a standard immo pm key transfer 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 immo pm key transfer FM, simply by entering the name IMMO_PM_KEY_TRANSFER into the relevant SAP transaction such as SE37 or SE38.

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



Function IMMO_PM_KEY_TRANSFER 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 'IMMO_PM_KEY_TRANSFER'"
EXPORTING
I_OBART = "
* I_CHANGE_XNOTPL = ' ' "
I_VIOB01 = "
* I_VIOB02 = "
* I_VIOB03 = "
* I_VIMI01 = "
* I_ANLN1 = "
* I_ANLN2 = "
* I_MODE = ' ' "
* I_MODE_ADD = ' ' "

CHANGING
* C_REPID = "
* C_DYNPRO = "

EXCEPTIONS
WRONG_OBART = 1
.



IMPORTING Parameters details for IMMO_PM_KEY_TRANSFER

I_OBART -

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

I_CHANGE_XNOTPL -

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

I_VIOB01 -

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

I_VIOB02 -

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

I_VIOB03 -

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

I_VIMI01 -

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

I_ANLN1 -

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

I_ANLN2 -

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

I_MODE -

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

I_MODE_ADD -

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

CHANGING Parameters details for IMMO_PM_KEY_TRANSFER

C_REPID -

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

C_DYNPRO -

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

EXCEPTIONS details

WRONG_OBART -

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

Copy and paste ABAP code example for IMMO_PM_KEY_TRANSFER 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_c_repid  TYPE SY-REPID, "   
lv_i_obart  TYPE J_OBART, "   
lv_wrong_obart  TYPE J_OBART, "   
lv_i_change_xnotpl  TYPE J_OBART, "   SPACE
lv_c_dynpro  TYPE SY-DYNNR, "   
lv_i_viob01  TYPE VIOB01, "   
lv_i_viob02  TYPE VIOB02, "   
lv_i_viob03  TYPE VIOB03, "   
lv_i_vimi01  TYPE VIMI01, "   
lv_i_anln1  TYPE ANLN1, "   
lv_i_anln2  TYPE ANLN2, "   
lv_i_mode  TYPE ANLN2, "   SPACE
lv_i_mode_add  TYPE ANLN2. "   SPACE

  CALL FUNCTION 'IMMO_PM_KEY_TRANSFER'  "
    EXPORTING
         I_OBART = lv_i_obart
         I_CHANGE_XNOTPL = lv_i_change_xnotpl
         I_VIOB01 = lv_i_viob01
         I_VIOB02 = lv_i_viob02
         I_VIOB03 = lv_i_viob03
         I_VIMI01 = lv_i_vimi01
         I_ANLN1 = lv_i_anln1
         I_ANLN2 = lv_i_anln2
         I_MODE = lv_i_mode
         I_MODE_ADD = lv_i_mode_add
    CHANGING
         C_REPID = lv_c_repid
         C_DYNPRO = lv_c_dynpro
    EXCEPTIONS
        WRONG_OBART = 1
. " IMMO_PM_KEY_TRANSFER




ABAP code using 7.40 inline data declarations to call FM IMMO_PM_KEY_TRANSFER

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 REPID FROM SY INTO @DATA(ld_c_repid).
 
 
 
DATA(ld_i_change_xnotpl) = ' '.
 
"SELECT single DYNNR FROM SY INTO @DATA(ld_c_dynpro).
 
 
 
 
 
 
 
DATA(ld_i_mode) = ' '.
 
DATA(ld_i_mode_add) = ' '.
 


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!