SAP FPB_PERS_POST_FOR_DIALOG Function Module for









FPB_PERS_POST_FOR_DIALOG is a standard fpb pers post for dialog 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 pers post for dialog FM, simply by entering the name FPB_PERS_POST_FOR_DIALOG into the relevant SAP transaction such as SE37 or SE38.

Function Group: FPB_CMPERS
Program Name: SAPLFPB_CMPERS
Main Program: SAPLFPB_CMPERS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function FPB_PERS_POST_FOR_DIALOG 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_PERS_POST_FOR_DIALOG'"
EXPORTING
IT_VALUES = "
* ID_ORIGIN = 'I' "
* ID_DELETE = 'X' "
* ID_NO_COMMIT = ' ' "
* ID_FRONTEND = ' ' "
* ID_DIALOG = "
* ID_APPLID = "
* ID_SUBCONTEXT = "
* ID_PERSKEYTP = 'U' "
* ID_PERSKEY = SY-UNAME "
* ID_TEST = "
* ID_DATEFROM = "
* ID_DATETO = "

IMPORTING
ED_ERROR = "

TABLES
ET_WRONG_VALUE = "
ET_RETURN = "

EXCEPTIONS
AUTHORITY_CHECK_FAILED = 1 ORIGIN_NOT_VALID = 10 EXISTENCE_CHECK_FAILED = 2 DATA_INCONSISTENCE = 3 NO_INPUT = 4 OVER_DEFINED = 5 DIALOG_NOT_FOUND = 6 APPLID_NOT_FOUND = 7 FIELDNAME_NOT_FOUND = 8 FIELDTYPE_NOT_VALID = 9
.



IMPORTING Parameters details for FPB_PERS_POST_FOR_DIALOG

IT_VALUES -

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

ID_ORIGIN -

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

ID_DELETE -

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

ID_NO_COMMIT -

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

ID_FRONTEND -

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

ID_DIALOG -

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

ID_APPLID -

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

ID_SUBCONTEXT -

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

ID_PERSKEYTP -

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

ID_PERSKEY -

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

ID_TEST -

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

ID_DATEFROM -

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

ID_DATETO -

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

EXPORTING Parameters details for FPB_PERS_POST_FOR_DIALOG

ED_ERROR -

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

TABLES Parameters details for FPB_PERS_POST_FOR_DIALOG

ET_WRONG_VALUE -

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

ET_RETURN -

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

EXCEPTIONS details

AUTHORITY_CHECK_FAILED -

Data type:
Optional: No
Call by Reference: Yes

ORIGIN_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

EXISTENCE_CHECK_FAILED -

Data type:
Optional: No
Call by Reference: Yes

DATA_INCONSISTENCE -

Data type:
Optional: No
Call by Reference: Yes

NO_INPUT -

Data type:
Optional: No
Call by Reference: Yes

OVER_DEFINED -

Data type:
Optional: No
Call by Reference: Yes

DIALOG_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

APPLID_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FIELDNAME_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FIELDTYPE_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FPB_PERS_POST_FOR_DIALOG 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_ed_error  TYPE INT4, "   
lv_it_values  TYPE FPB_T_VALUES, "   
lt_et_wrong_value  TYPE STANDARD TABLE OF FPB_T_ERROR, "   
lv_authority_check_failed  TYPE FPB_T_ERROR, "   
lv_id_origin  TYPE CHAR1, "   'I'
lv_origin_not_valid  TYPE CHAR1, "   
lv_id_delete  TYPE FLAG, "   'X'
lv_id_no_commit  TYPE FLAG, "   SPACE
lv_id_frontend  TYPE CHAR1, "   SPACE
lt_et_return  TYPE STANDARD TABLE OF BAPIRETURN1, "   
lv_id_dialog  TYPE FPB_DIALOGID, "   
lv_existence_check_failed  TYPE FPB_DIALOGID, "   
lv_id_applid  TYPE FPB_APPID, "   
lv_data_inconsistence  TYPE FPB_APPID, "   
lv_no_input  TYPE FPB_APPID, "   
lv_id_subcontext  TYPE FPB_APPSUBCON, "   
lv_id_perskeytp  TYPE FPB_KEYTP, "   'U'
lv_over_defined  TYPE FPB_KEYTP, "   
lv_id_perskey  TYPE FPB_KEY, "   SY-UNAME
lv_dialog_not_found  TYPE FPB_KEY, "   
lv_id_test  TYPE FLAG, "   
lv_applid_not_found  TYPE FLAG, "   
lv_id_datefrom  TYPE DATUM, "   
lv_fieldname_not_found  TYPE DATUM, "   
lv_id_dateto  TYPE DATUM, "   
lv_fieldtype_not_valid  TYPE DATUM. "   

  CALL FUNCTION 'FPB_PERS_POST_FOR_DIALOG'  "
    EXPORTING
         IT_VALUES = lv_it_values
         ID_ORIGIN = lv_id_origin
         ID_DELETE = lv_id_delete
         ID_NO_COMMIT = lv_id_no_commit
         ID_FRONTEND = lv_id_frontend
         ID_DIALOG = lv_id_dialog
         ID_APPLID = lv_id_applid
         ID_SUBCONTEXT = lv_id_subcontext
         ID_PERSKEYTP = lv_id_perskeytp
         ID_PERSKEY = lv_id_perskey
         ID_TEST = lv_id_test
         ID_DATEFROM = lv_id_datefrom
         ID_DATETO = lv_id_dateto
    IMPORTING
         ED_ERROR = lv_ed_error
    TABLES
         ET_WRONG_VALUE = lt_et_wrong_value
         ET_RETURN = lt_et_return
    EXCEPTIONS
        AUTHORITY_CHECK_FAILED = 1
        ORIGIN_NOT_VALID = 10
        EXISTENCE_CHECK_FAILED = 2
        DATA_INCONSISTENCE = 3
        NO_INPUT = 4
        OVER_DEFINED = 5
        DIALOG_NOT_FOUND = 6
        APPLID_NOT_FOUND = 7
        FIELDNAME_NOT_FOUND = 8
        FIELDTYPE_NOT_VALID = 9
. " FPB_PERS_POST_FOR_DIALOG




ABAP code using 7.40 inline data declarations to call FM FPB_PERS_POST_FOR_DIALOG

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_origin) = 'I'.
 
 
DATA(ld_id_delete) = 'X'.
 
DATA(ld_id_no_commit) = ' '.
 
DATA(ld_id_frontend) = ' '.
 
 
 
 
 
 
 
 
DATA(ld_id_perskeytp) = 'U'.
 
 
DATA(ld_id_perskey) = SY-UNAME.
 
 
 
 
 
 
 
 


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!