SAP FB_MIGRATE_FORM_FP_CUST Function Module for









FB_MIGRATE_FORM_FP_CUST is a standard fb migrate form fp cust 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 fb migrate form fp cust FM, simply by entering the name FB_MIGRATE_FORM_FP_CUST into the relevant SAP transaction such as SE37 or SE38.

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



Function FB_MIGRATE_FORM_FP_CUST 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 'FB_MIGRATE_FORM_FP_CUST'"
  EXPORTING
*  I_SMARTFORM_NAME = ' ' "Smart Form
*  I_FPFORM_NAME =  "
*  I_RUNTIME =  "
*  I_WITH_DIALOG = 'X' "

 IMPORTING
   O_SMARTFORM_NAME =  "
   O_FPFORM_NAME =  "
   O_RUNTIME =  "

EXCEPTIONS
   NO_NAME = 1    NO_FORM = 2    NO_ACCESS_PERMISSION = 3    ILLEGAL_NAME = 4    NO_SUCCESS = 5    WRONG_TYPE = 6
.



IMPORTING Parameters details for FB_MIGRATE_FORM_FP_CUST

I_SMARTFORM_NAME - Smart Form

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

I_FPFORM_NAME -

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

I_RUNTIME -

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

I_WITH_DIALOG -

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

EXPORTING Parameters details for FB_MIGRATE_FORM_FP_CUST

O_SMARTFORM_NAME -

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

O_FPFORM_NAME -

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

O_RUNTIME -

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

EXCEPTIONS details

NO_NAME -

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

NO_FORM -

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

NO_ACCESS_PERMISSION -

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_NAME -

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

NO_SUCCESS - Other Error

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

WRONG_TYPE - Incorrect Type

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FB_MIGRATE_FORM_FP_CUST 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_no_name  TYPE STRING, "   
lv_i_smartform_name  TYPE TDSFNAME, "   SPACE
lv_o_smartform_name  TYPE TDSFNAME, "   
lv_no_form  TYPE TDSFNAME, "   
lv_i_fpform_name  TYPE FPNAME, "   
lv_o_fpform_name  TYPE FPNAME, "   
lv_i_runtime  TYPE TDSFMTYPE, "   
lv_o_runtime  TYPE TDSFMTYPE, "   
lv_no_access_permission  TYPE TDSFMTYPE, "   
lv_illegal_name  TYPE TDSFMTYPE, "   
lv_i_with_dialog  TYPE TDSFFLAG, "   'X'
lv_no_success  TYPE TDSFFLAG, "   
lv_wrong_type  TYPE TDSFFLAG. "   

  CALL FUNCTION 'FB_MIGRATE_FORM_FP_CUST'  "
    EXPORTING
         I_SMARTFORM_NAME = lv_i_smartform_name
         I_FPFORM_NAME = lv_i_fpform_name
         I_RUNTIME = lv_i_runtime
         I_WITH_DIALOG = lv_i_with_dialog
    IMPORTING
         O_SMARTFORM_NAME = lv_o_smartform_name
         O_FPFORM_NAME = lv_o_fpform_name
         O_RUNTIME = lv_o_runtime
    EXCEPTIONS
        NO_NAME = 1
        NO_FORM = 2
        NO_ACCESS_PERMISSION = 3
        ILLEGAL_NAME = 4
        NO_SUCCESS = 5
        WRONG_TYPE = 6
. " FB_MIGRATE_FORM_FP_CUST




ABAP code using 7.40 inline data declarations to call FM FB_MIGRATE_FORM_FP_CUST

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_i_smartform_name) = ' '.
 
 
 
 
 
 
 
 
 
DATA(ld_i_with_dialog) = 'X'.
 
 
 


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!