SAP FPB_EXP_EDIT_INSTANCE Function Module for









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

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



Function FPB_EXP_EDIT_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_EDIT_INSTANCE'"
EXPORTING
* ID_SCENARIO = "
* ID_MODE = 3 "

IMPORTING
ES_INSTANCE = "

EXCEPTIONS
CANCELED_BY_USER = 1
.



IMPORTING Parameters details for FPB_EXP_EDIT_INSTANCE

ID_SCENARIO -

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

ID_MODE -

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

EXPORTING Parameters details for FPB_EXP_EDIT_INSTANCE

ES_INSTANCE -

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

EXCEPTIONS details

CANCELED_BY_USER -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FPB_EXP_EDIT_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_es_instance  TYPE FPB_EXP_INST, "   
lv_id_scenario  TYPE FPB_EXP_SCENARIO, "   
lv_canceled_by_user  TYPE FPB_EXP_SCENARIO, "   
lv_id_mode  TYPE CHAR1. "   3

  CALL FUNCTION 'FPB_EXP_EDIT_INSTANCE'  "
    EXPORTING
         ID_SCENARIO = lv_id_scenario
         ID_MODE = lv_id_mode
    IMPORTING
         ES_INSTANCE = lv_es_instance
    EXCEPTIONS
        CANCELED_BY_USER = 1
. " FPB_EXP_EDIT_INSTANCE




ABAP code using 7.40 inline data declarations to call FM FPB_EXP_EDIT_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.

 
 
 
DATA(ld_id_mode) = 3.
 


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!