SAP S_FOBU_METHOD_COPY Function Module for









S_FOBU_METHOD_COPY is a standard s fobu method copy 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 s fobu method copy FM, simply by entering the name S_FOBU_METHOD_COPY into the relevant SAP transaction such as SE37 or SE38.

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



Function S_FOBU_METHOD_COPY 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 'S_FOBU_METHOD_COPY'"
EXPORTING
CLASS_NAME = "Object Type Name
* INTERFACE_NAME = ' ' "Interface Name
METHOD_NAME = "Component Name
* EXTENSION = ' ' "Key Enhancement for Formula Builder Methods
* ENVIRONMENT = "Parameters for Formula Builder Methods
* NEW_CLASS_NAME = ' ' "
* NEW_EXTENSION = ' ' "

CHANGING
* TRANSPORT_REQUEST = "Request/Task

EXCEPTIONS
METHOD_NOT_FOUND = 1 REF_FBM_NOT_FOUND = 2 REF_FBM_INCONSISTENT = 3 FBM_ALREADY_IMPLEMENTED = 4 ACCESS_NOT_POSSIBLE = 5 INVALID_CALL = 6
.



IMPORTING Parameters details for S_FOBU_METHOD_COPY

CLASS_NAME - Object Type Name

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

INTERFACE_NAME - Interface Name

Data type: SEOITFNAME
Default: SPACE
Optional: Yes
Call by Reference: Yes

METHOD_NAME - Component Name

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

EXTENSION - Key Enhancement for Formula Builder Methods

Data type: SFBMEXTENS
Default: SPACE
Optional: Yes
Call by Reference: Yes

ENVIRONMENT - Parameters for Formula Builder Methods

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

NEW_CLASS_NAME -

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

NEW_EXTENSION -

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

CHANGING Parameters details for S_FOBU_METHOD_COPY

TRANSPORT_REQUEST - Request/Task

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

EXCEPTIONS details

METHOD_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

REF_FBM_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

REF_FBM_INCONSISTENT -

Data type:
Optional: No
Call by Reference: Yes

FBM_ALREADY_IMPLEMENTED -

Data type:
Optional: No
Call by Reference: Yes

ACCESS_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

INVALID_CALL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for S_FOBU_METHOD_COPY 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_class_name  TYPE SEOCLSNAME, "   
lv_method_not_found  TYPE SEOCLSNAME, "   
lv_transport_request  TYPE TRKORR, "   
lv_interface_name  TYPE SEOITFNAME, "   SPACE
lv_ref_fbm_not_found  TYPE SEOITFNAME, "   
lv_method_name  TYPE SEOCMPNAME, "   
lv_ref_fbm_inconsistent  TYPE SEOCMPNAME, "   
lv_extension  TYPE SFBMEXTENS, "   SPACE
lv_fbm_already_implemented  TYPE SFBMEXTENS, "   
lv_environment  TYPE IF_FBM_CONNECTOR, "   
lv_access_not_possible  TYPE IF_FBM_CONNECTOR, "   
lv_invalid_call  TYPE IF_FBM_CONNECTOR, "   
lv_new_class_name  TYPE SEOCLSNAME, "   SPACE
lv_new_extension  TYPE SFBMEXTENS. "   SPACE

  CALL FUNCTION 'S_FOBU_METHOD_COPY'  "
    EXPORTING
         CLASS_NAME = lv_class_name
         INTERFACE_NAME = lv_interface_name
         METHOD_NAME = lv_method_name
         EXTENSION = lv_extension
         ENVIRONMENT = lv_environment
         NEW_CLASS_NAME = lv_new_class_name
         NEW_EXTENSION = lv_new_extension
    CHANGING
         TRANSPORT_REQUEST = lv_transport_request
    EXCEPTIONS
        METHOD_NOT_FOUND = 1
        REF_FBM_NOT_FOUND = 2
        REF_FBM_INCONSISTENT = 3
        FBM_ALREADY_IMPLEMENTED = 4
        ACCESS_NOT_POSSIBLE = 5
        INVALID_CALL = 6
. " S_FOBU_METHOD_COPY




ABAP code using 7.40 inline data declarations to call FM S_FOBU_METHOD_COPY

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_interface_name) = ' '.
 
 
 
 
DATA(ld_extension) = ' '.
 
 
 
 
 
DATA(ld_new_class_name) = ' '.
 
DATA(ld_new_extension) = ' '.
 


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!