SAP FPB_CMPERS_RESOLVE Function Module for









FPB_CMPERS_RESOLVE is a standard fpb cmpers resolve 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 fpb cmpers resolve FM, simply by entering the name FPB_CMPERS_RESOLVE into the relevant SAP transaction such as SE37 or SE38.

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



Function FPB_CMPERS_RESOLVE 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 'FPB_CMPERS_RESOLVE'"
EXPORTING
ID_APPLID = "
IT_CMPERS = "
* ID_KOKRS = "
* ID_PERS_KEYTP = 'U' "
* ID_PERSKEY = "

IMPORTING
ET_CMPERS_RESOLVE = "

EXCEPTIONS
NO_DATA_FOUND = 1 KOKRS_NOT_FOUND = 2
.



IMPORTING Parameters details for FPB_CMPERS_RESOLVE

ID_APPLID -

Data type: FPB_APPID
Optional: No
Call by Reference: Yes

IT_CMPERS -

Data type: FPB_T_CMPERSPARMRESOLVE
Optional: No
Call by Reference: Yes

ID_KOKRS -

Data type: KOKRS
Optional: Yes
Call by Reference: Yes

ID_PERS_KEYTP -

Data type: FPB_KEYTP
Default: 'U'
Optional: Yes
Call by Reference: Yes

ID_PERSKEY -

Data type: FPB_KEY
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FPB_CMPERS_RESOLVE

ET_CMPERS_RESOLVE -

Data type: FPB_T_CMPERSPARMRESOLVE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_DATA_FOUND -

Data type:
Optional: No
Call by Reference: Yes

KOKRS_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FPB_CMPERS_RESOLVE 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_id_applid  TYPE FPB_APPID, "   
lv_no_data_found  TYPE FPB_APPID, "   
lv_et_cmpers_resolve  TYPE FPB_T_CMPERSPARMRESOLVE, "   
lv_it_cmpers  TYPE FPB_T_CMPERSPARMRESOLVE, "   
lv_kokrs_not_found  TYPE FPB_T_CMPERSPARMRESOLVE, "   
lv_id_kokrs  TYPE KOKRS, "   
lv_id_pers_keytp  TYPE FPB_KEYTP, "   'U'
lv_id_perskey  TYPE FPB_KEY. "   

  CALL FUNCTION 'FPB_CMPERS_RESOLVE'  "
    EXPORTING
         ID_APPLID = lv_id_applid
         IT_CMPERS = lv_it_cmpers
         ID_KOKRS = lv_id_kokrs
         ID_PERS_KEYTP = lv_id_pers_keytp
         ID_PERSKEY = lv_id_perskey
    IMPORTING
         ET_CMPERS_RESOLVE = lv_et_cmpers_resolve
    EXCEPTIONS
        NO_DATA_FOUND = 1
        KOKRS_NOT_FOUND = 2
. " FPB_CMPERS_RESOLVE




ABAP code using 7.40 inline data declarations to call FM FPB_CMPERS_RESOLVE

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.

 
 
 
 
 
 
DATA(ld_id_pers_keytp) = 'U'.
 
 


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!