SAP IMMO_PM_READ_CUSTOMIZING Function Module for
IMMO_PM_READ_CUSTOMIZING is a standard immo pm read customizing 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 read customizing FM, simply by entering the name IMMO_PM_READ_CUSTOMIZING 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_READ_CUSTOMIZING 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_READ_CUSTOMIZING'".
EXPORTING
I_BUKRS = "
* I_OBART = "
* I_XNOTPL = ' ' "
* I_NO_CHECK_CUST = ' ' "
IMPORTING
E_AUTO_CREATE = "
E_EQM_OT_WE = "
E_EQM_OT_GR = "
E_EQM_OT_GE = "
E_EQM_OT_ME = "
E_EQM_OT_FL = "
E_EQM_OT_RA = "
E_FLG_PM_INSTALLED = "
E_EQM_TPLKZ = "
E_EQM_FLTYP = "
E_FLG_PM_1Z1 = "
E_EQM_TCODE = "
E_EQM_TPLNR = "
E_EQM_TCODE2 = "
E_FLG_ONE_TPL = "
EXCEPTIONS
WRONG_OBART = 1 CUSTOMIZING_ERROR = 2
IMPORTING Parameters details for IMMO_PM_READ_CUSTOMIZING
I_BUKRS -
Data type: VIOB01-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_OBART -
Data type: J_OBARTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_XNOTPL -
Data type: VIOB01-XNOTPLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NO_CHECK_CUST -
Data type: BOOLEANDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IMMO_PM_READ_CUSTOMIZING
E_AUTO_CREATE -
Data type: VVJEQM_AUTO_IMMOOptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_OT_WE -
Data type: TIPZB-EQM_OT_WEOptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_OT_GR -
Data type: TIPZB-EQM_OT_GEOptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_OT_GE -
Data type: TIPZB-EQM_OT_GROptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_OT_ME -
Data type: TIPZB-EQM_OT_MEOptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_OT_FL -
Data type: TIPZB-EQM_OT_FLOptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_OT_RA -
Data type: TIPZB-EQM_OT_RAOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_PM_INSTALLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_EQM_TPLKZ -
Data type: TIPZB-EQM_TPLKZOptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_FLTYP -
Data type: TIPZB-EQM_FLTYPOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_PM_1Z1 -
Data type: TIPZB-JEQM_1Z1Optional: No
Call by Reference: No ( called with pass by value option)
E_EQM_TCODE -
Data type: TIPZB-EQM_TCODEOptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_TPLNR -
Data type: TIPZB-EQM_TPLNROptional: No
Call by Reference: No ( called with pass by value option)
E_EQM_TCODE2 -
Data type: TIPZB-EQM_TCODE2Optional: No
Call by Reference: No ( called with pass by value option)
E_FLG_ONE_TPL -
Data type: COptional: No
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)
CUSTOMIZING_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IMMO_PM_READ_CUSTOMIZING 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_i_bukrs | TYPE VIOB01-BUKRS, " | |||
| lv_wrong_obart | TYPE VIOB01, " | |||
| lv_e_auto_create | TYPE VVJEQM_AUTO_IMMO, " | |||
| lv_e_eqm_ot_we | TYPE TIPZB-EQM_OT_WE, " | |||
| lv_e_eqm_ot_gr | TYPE TIPZB-EQM_OT_GE, " | |||
| lv_e_eqm_ot_ge | TYPE TIPZB-EQM_OT_GR, " | |||
| lv_e_eqm_ot_me | TYPE TIPZB-EQM_OT_ME, " | |||
| lv_e_eqm_ot_fl | TYPE TIPZB-EQM_OT_FL, " | |||
| lv_e_eqm_ot_ra | TYPE TIPZB-EQM_OT_RA, " | |||
| lv_i_obart | TYPE J_OBART, " | |||
| lv_customizing_error | TYPE J_OBART, " | |||
| lv_e_flg_pm_installed | TYPE J_OBART, " | |||
| lv_i_xnotpl | TYPE VIOB01-XNOTPL, " SPACE | |||
| lv_e_eqm_tplkz | TYPE TIPZB-EQM_TPLKZ, " | |||
| lv_e_eqm_fltyp | TYPE TIPZB-EQM_FLTYP, " | |||
| lv_i_no_check_cust | TYPE BOOLEAN, " SPACE | |||
| lv_e_flg_pm_1z1 | TYPE TIPZB-JEQM_1Z1, " | |||
| lv_e_eqm_tcode | TYPE TIPZB-EQM_TCODE, " | |||
| lv_e_eqm_tplnr | TYPE TIPZB-EQM_TPLNR, " | |||
| lv_e_eqm_tcode2 | TYPE TIPZB-EQM_TCODE2, " | |||
| lv_e_flg_one_tpl | TYPE C. " |
|   CALL FUNCTION 'IMMO_PM_READ_CUSTOMIZING' " |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_OBART | = lv_i_obart | |
| I_XNOTPL | = lv_i_xnotpl | |
| I_NO_CHECK_CUST | = lv_i_no_check_cust | |
| IMPORTING | ||
| E_AUTO_CREATE | = lv_e_auto_create | |
| E_EQM_OT_WE | = lv_e_eqm_ot_we | |
| E_EQM_OT_GR | = lv_e_eqm_ot_gr | |
| E_EQM_OT_GE | = lv_e_eqm_ot_ge | |
| E_EQM_OT_ME | = lv_e_eqm_ot_me | |
| E_EQM_OT_FL | = lv_e_eqm_ot_fl | |
| E_EQM_OT_RA | = lv_e_eqm_ot_ra | |
| E_FLG_PM_INSTALLED | = lv_e_flg_pm_installed | |
| E_EQM_TPLKZ | = lv_e_eqm_tplkz | |
| E_EQM_FLTYP | = lv_e_eqm_fltyp | |
| E_FLG_PM_1Z1 | = lv_e_flg_pm_1z1 | |
| E_EQM_TCODE | = lv_e_eqm_tcode | |
| E_EQM_TPLNR | = lv_e_eqm_tplnr | |
| E_EQM_TCODE2 | = lv_e_eqm_tcode2 | |
| E_FLG_ONE_TPL | = lv_e_flg_one_tpl | |
| EXCEPTIONS | ||
| WRONG_OBART = 1 | ||
| CUSTOMIZING_ERROR = 2 | ||
| . " IMMO_PM_READ_CUSTOMIZING | ||
ABAP code using 7.40 inline data declarations to call FM IMMO_PM_READ_CUSTOMIZING
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 BUKRS FROM VIOB01 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single EQM_OT_WE FROM TIPZB INTO @DATA(ld_e_eqm_ot_we). | ||||
| "SELECT single EQM_OT_GE FROM TIPZB INTO @DATA(ld_e_eqm_ot_gr). | ||||
| "SELECT single EQM_OT_GR FROM TIPZB INTO @DATA(ld_e_eqm_ot_ge). | ||||
| "SELECT single EQM_OT_ME FROM TIPZB INTO @DATA(ld_e_eqm_ot_me). | ||||
| "SELECT single EQM_OT_FL FROM TIPZB INTO @DATA(ld_e_eqm_ot_fl). | ||||
| "SELECT single EQM_OT_RA FROM TIPZB INTO @DATA(ld_e_eqm_ot_ra). | ||||
| "SELECT single XNOTPL FROM VIOB01 INTO @DATA(ld_i_xnotpl). | ||||
| DATA(ld_i_xnotpl) | = ' '. | |||
| "SELECT single EQM_TPLKZ FROM TIPZB INTO @DATA(ld_e_eqm_tplkz). | ||||
| "SELECT single EQM_FLTYP FROM TIPZB INTO @DATA(ld_e_eqm_fltyp). | ||||
| DATA(ld_i_no_check_cust) | = ' '. | |||
| "SELECT single JEQM_1Z1 FROM TIPZB INTO @DATA(ld_e_flg_pm_1z1). | ||||
| "SELECT single EQM_TCODE FROM TIPZB INTO @DATA(ld_e_eqm_tcode). | ||||
| "SELECT single EQM_TPLNR FROM TIPZB INTO @DATA(ld_e_eqm_tplnr). | ||||
| "SELECT single EQM_TCODE2 FROM TIPZB INTO @DATA(ld_e_eqm_tcode2). | ||||
Search for further information about these or an SAP related objects