SAP FPB_EXP_GET_UINSTS_FOR_SUBMIT Function Module for User Instances for partial submit









FPB_EXP_GET_UINSTS_FOR_SUBMIT is a standard fpb exp get uinsts for submit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User Instances for partial submit 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 get uinsts for submit FM, simply by entering the name FPB_EXP_GET_UINSTS_FOR_SUBMIT 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_GET_UINSTS_FOR_SUBMIT 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_GET_UINSTS_FOR_SUBMIT'"User Instances for partial submit
EXPORTING
ID_SCENARIO = "Planning Scenario
ID_INSTANCE = "Express Planning Instance
* ID_APPROVER = SY-UNAME "User Name of Approver

IMPORTING
ET_UINST = "Table type for Express Planning User Instances

EXCEPTIONS
NOT_AN_APPROVER = 1
.



IMPORTING Parameters details for FPB_EXP_GET_UINSTS_FOR_SUBMIT

ID_SCENARIO - Planning Scenario

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

ID_INSTANCE - Express Planning Instance

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

ID_APPROVER - User Name of Approver

Data type: SYUNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FPB_EXP_GET_UINSTS_FOR_SUBMIT

ET_UINST - Table type for Express Planning User Instances

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

EXCEPTIONS details

NOT_AN_APPROVER - ID_APPROVER is not an approver

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FPB_EXP_GET_UINSTS_FOR_SUBMIT 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_uinst  TYPE FPB_EXP_T_UINST, "   
lv_id_scenario  TYPE FPB_EXP_SCENARIO, "   
lv_not_an_approver  TYPE FPB_EXP_SCENARIO, "   
lv_id_instance  TYPE FPB_EXP_INSTANCE, "   
lv_id_approver  TYPE SYUNAME. "   SY-UNAME

  CALL FUNCTION 'FPB_EXP_GET_UINSTS_FOR_SUBMIT'  "User Instances for partial submit
    EXPORTING
         ID_SCENARIO = lv_id_scenario
         ID_INSTANCE = lv_id_instance
         ID_APPROVER = lv_id_approver
    IMPORTING
         ET_UINST = lv_et_uinst
    EXCEPTIONS
        NOT_AN_APPROVER = 1
. " FPB_EXP_GET_UINSTS_FOR_SUBMIT




ABAP code using 7.40 inline data declarations to call FM FPB_EXP_GET_UINSTS_FOR_SUBMIT

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_approver) = 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!