SAP FPB_PERS_API_POST Function Module for

Search SAP Function Modules

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

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

Function FPB_PERS_API_POST 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_API_POST'"
  EXPORTING
   IT_VALUE =  "
*  ID_PERSKEYTP = 'U' "
*  ID_PERSKEY =  "
*  ID_SUBCONTEXT =  "
*  ID_DATEFROM =  "
*  ID_DATETO =  "
*  ID_ORIGIN = 'I' "
*  ID_DELETE = 'X' "
*  ID_NO_COMMIT = ' ' "

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_API_POST

IT_VALUE -

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

ID_PERSKEYTP -

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

ID_PERSKEY -

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

ID_SUBCONTEXT -

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

ID_DATEFROM -

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

ID_DATETO -

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

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)

EXCEPTIONS details

AUTHORITY_CHECK_FAILED -

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

ORIGIN_NOT_VALID -

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

EXISTENCE_CHECK_FAILED -

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

DATA_INCONSISTENCE -

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

NO_INPUT -

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

OVER_DEFINED -

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

DIALOG_NOT_FOUND -

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

APPLID_NOT_FOUND -

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

FIELDNAME_NOT_FOUND -

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

FIELDTYPE_NOT_VALID -

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

Copy and paste ABAP code example for FPB_PERS_API_POST 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.

ABAP code using 7.40 inline data declarations to call FM FPB_PERS_API_POST

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.

Search for further information about these or an SAP related objects