SAP MY_EXECUTE_CUSTOM_TEST Function Module for









MY_EXECUTE_CUSTOM_TEST is a standard my execute custom test 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 my execute custom test FM, simply by entering the name MY_EXECUTE_CUSTOM_TEST into the relevant SAP transaction such as SE37 or SE38.

Function Group: SRM_BOR_TEST_EXT
Program Name: SAPLSRM_BOR_TEST_EXT
Main Program: SAPLSRM_BOR_TEST_EXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MY_EXECUTE_CUSTOM_TEST 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 'MY_EXECUTE_CUSTOM_TEST'"
  EXPORTING
   BOR_TYPE =  "BOR Type
   SOURCE_RMF_POID =  "
*  ANCHOR =  "Anchor
   LOGICAL_SYSTEM =  "Logical System
*  BOR_ID =  "
*  SUBTYPE =  "
   POID_STATE =  "POID Status
   BOR_RMF_POID =  "
   AREA_POID =  "
*  BOR_SP_POID =  "
   ACTIVITY_ID =  "Activity - ID
*  SOURCE_SP_POID =  "

 IMPORTING
   TARGET_SP_POID =  "

TABLES
   RETURN =  "Return Parameters

EXCEPTIONS
   INTERNAL_ERROR = 1
.



IMPORTING Parameters details for MY_EXECUTE_CUSTOM_TEST

BOR_TYPE - BOR Type

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

SOURCE_RMF_POID -

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

ANCHOR - Anchor

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

LOGICAL_SYSTEM - Logical System

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

BOR_ID -

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

SUBTYPE -

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

POID_STATE - POID Status

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

BOR_RMF_POID -

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

AREA_POID -

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

BOR_SP_POID -

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

ACTIVITY_ID - Activity - ID

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

SOURCE_SP_POID -

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

EXPORTING Parameters details for MY_EXECUTE_CUSTOM_TEST

TARGET_SP_POID -

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

TABLES Parameters details for MY_EXECUTE_CUSTOM_TEST

RETURN - Return Parameters

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

EXCEPTIONS details

INTERNAL_ERROR - Internal Error

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

Copy and paste ABAP code example for MY_EXECUTE_CUSTOM_TEST 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_bor_type  TYPE STRING, "   
lv_internal_error  TYPE STRING, "   
lv_target_sp_poid  TYPE SRM_LIST_POID, "   
lv_source_rmf_poid  TYPE SRM_LIST_POID, "   
lv_anchor  TYPE STRING, "   
lv_logical_system  TYPE STRING, "   
lv_bor_id  TYPE STRING, "   
lv_subtype  TYPE STRING, "   
lv_poid_state  TYPE STRING, "   
lv_bor_rmf_poid  TYPE SRM_LIST_POID, "   
lv_area_poid  TYPE SRM_LIST_POID, "   
lv_bor_sp_poid  TYPE SRM_LIST_POID, "   
lv_activity_id  TYPE SRMACTID, "   
lv_source_sp_poid  TYPE SRM_LIST_POID. "   

  CALL FUNCTION 'MY_EXECUTE_CUSTOM_TEST'  "
    EXPORTING
         BOR_TYPE = lv_bor_type
         SOURCE_RMF_POID = lv_source_rmf_poid
         ANCHOR = lv_anchor
         LOGICAL_SYSTEM = lv_logical_system
         BOR_ID = lv_bor_id
         SUBTYPE = lv_subtype
         POID_STATE = lv_poid_state
         BOR_RMF_POID = lv_bor_rmf_poid
         AREA_POID = lv_area_poid
         BOR_SP_POID = lv_bor_sp_poid
         ACTIVITY_ID = lv_activity_id
         SOURCE_SP_POID = lv_source_sp_poid
    IMPORTING
         TARGET_SP_POID = lv_target_sp_poid
    TABLES
         RETURN = lt_return
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " MY_EXECUTE_CUSTOM_TEST




ABAP code using 7.40 inline data declarations to call FM MY_EXECUTE_CUSTOM_TEST

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



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!