SAP FPB_EXP_TRANSFER_USER_INSTANCE Function Module for Deletion of an Express Planning User Instance
FPB_EXP_TRANSFER_USER_INSTANCE is a standard fpb exp transfer user instance SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Deletion of an Express Planning User Instance processing and below is the pattern details for this FM, 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 exp transfer user instance FM, simply by entering the name FPB_EXP_TRANSFER_USER_INSTANCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPB_EXP_UTILITIES
Program Name: SAPLFPB_EXP_UTILITIES
Main Program: SAPLFPB_EXP_UTILITIES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FPB_EXP_TRANSFER_USER_INSTANCE 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_EXP_TRANSFER_USER_INSTANCE'"Deletion of an Express Planning User Instance.
EXPORTING
ID_SCENARIO = "Planning Scenario
ID_INSTANCE = "Express Planning Instance
ID_UNAME_OLD = "Old User Name
ID_UNAME_NEW = "Old User Name
IMPORTING
ET_RETURN = "Table Type for BAPIRETURN1
EXCEPTIONS
USER_INSTANCE_NOT_FOUND = 1 NO_AUTHORITY = 2 TRANSFER_NOT_POSSIBLE = 3
IMPORTING Parameters details for FPB_EXP_TRANSFER_USER_INSTANCE
ID_SCENARIO - Planning Scenario
Data type: FPB_EXP_SCENARIOOptional: No
Call by Reference: Yes
ID_INSTANCE - Express Planning Instance
Data type: FPB_EXP_INSTANCEOptional: No
Call by Reference: Yes
ID_UNAME_OLD - Old User Name
Data type: SYUNAMEOptional: No
Call by Reference: Yes
ID_UNAME_NEW - Old User Name
Data type: SYUNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FPB_EXP_TRANSFER_USER_INSTANCE
ET_RETURN - Table Type for BAPIRETURN1
Data type: FPB_EXP_T_BAPIRETURN1Optional: No
Call by Reference: Yes
EXCEPTIONS details
USER_INSTANCE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TRANSFER_NOT_POSSIBLE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FPB_EXP_TRANSFER_USER_INSTANCE 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_et_return | TYPE FPB_EXP_T_BAPIRETURN1, " | |||
| lv_id_scenario | TYPE FPB_EXP_SCENARIO, " | |||
| lv_user_instance_not_found | TYPE FPB_EXP_SCENARIO, " | |||
| lv_id_instance | TYPE FPB_EXP_INSTANCE, " | |||
| lv_no_authority | TYPE FPB_EXP_INSTANCE, " | |||
| lv_id_uname_old | TYPE SYUNAME, " | |||
| lv_transfer_not_possible | TYPE SYUNAME, " | |||
| lv_id_uname_new | TYPE SYUNAME. " |
|   CALL FUNCTION 'FPB_EXP_TRANSFER_USER_INSTANCE' "Deletion of an Express Planning User Instance |
| EXPORTING | ||
| ID_SCENARIO | = lv_id_scenario | |
| ID_INSTANCE | = lv_id_instance | |
| ID_UNAME_OLD | = lv_id_uname_old | |
| ID_UNAME_NEW | = lv_id_uname_new | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| EXCEPTIONS | ||
| USER_INSTANCE_NOT_FOUND = 1 | ||
| NO_AUTHORITY = 2 | ||
| TRANSFER_NOT_POSSIBLE = 3 | ||
| . " FPB_EXP_TRANSFER_USER_INSTANCE | ||
ABAP code using 7.40 inline data declarations to call FM FPB_EXP_TRANSFER_USER_INSTANCE
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