SAP ISHMED_BEW_TRANSFER Function Module for









ISHMED_BEW_TRANSFER is a standard ishmed bew transfer 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 ishmed bew transfer FM, simply by entering the name ISHMED_BEW_TRANSFER into the relevant SAP transaction such as SE37 or SE38.

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



Function ISHMED_BEW_TRANSFER 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 'ISHMED_BEW_TRANSFER'"
EXPORTING
I_NBEW = "
* I_LOCK_TAB = 'X' "

IMPORTING
E_STOID = "Cancellation Reason
E_GPART = "Employee Responsible
E_RC = "
ET_MESSAGE = "

TABLES
T_NBEW = "

EXCEPTIONS
NOT_POSSIBLE = 1 NO_INPUT = 2 READ_ERROR = 3 SAVE_ERROR = 4 FALL_LOCKED = 5 SYS_ERROR = 6
.



IMPORTING Parameters details for ISHMED_BEW_TRANSFER

I_NBEW -

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

I_LOCK_TAB -

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

EXPORTING Parameters details for ISHMED_BEW_TRANSFER

E_STOID - Cancellation Reason

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

E_GPART - Employee Responsible

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

E_RC -

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

ET_MESSAGE -

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

TABLES Parameters details for ISHMED_BEW_TRANSFER

T_NBEW -

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

EXCEPTIONS details

NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

NO_INPUT - Action was terminated by user

Data type:
Optional: No
Call by Reference: Yes

READ_ERROR - Error when reading important data

Data type:
Optional: No
Call by Reference: Yes

SAVE_ERROR - Error while saving data

Data type:
Optional: No
Call by Reference: Yes

FALL_LOCKED - Case is Already Locked

Data type:
Optional: No
Call by Reference: Yes

SYS_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISHMED_BEW_TRANSFER 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_i_nbew  TYPE NBEW, "   
lt_t_nbew  TYPE STANDARD TABLE OF VNBEW, "   
lv_e_stoid  TYPE NBEW-STOID, "   
lv_not_possible  TYPE NBEW, "   
lv_e_gpart  TYPE NGPA-GPART, "   
lv_no_input  TYPE NGPA, "   
lv_i_lock_tab  TYPE RNT40-MARK, "   'X'
lv_e_rc  TYPE ISH_METHOD_RC, "   
lv_read_error  TYPE ISH_METHOD_RC, "   
lv_et_message  TYPE ISHMED_T_BAPIRET2, "   
lv_save_error  TYPE ISHMED_T_BAPIRET2, "   
lv_fall_locked  TYPE ISHMED_T_BAPIRET2, "   
lv_sys_error  TYPE ISHMED_T_BAPIRET2. "   

  CALL FUNCTION 'ISHMED_BEW_TRANSFER'  "
    EXPORTING
         I_NBEW = lv_i_nbew
         I_LOCK_TAB = lv_i_lock_tab
    IMPORTING
         E_STOID = lv_e_stoid
         E_GPART = lv_e_gpart
         E_RC = lv_e_rc
         ET_MESSAGE = lv_et_message
    TABLES
         T_NBEW = lt_t_nbew
    EXCEPTIONS
        NOT_POSSIBLE = 1
        NO_INPUT = 2
        READ_ERROR = 3
        SAVE_ERROR = 4
        FALL_LOCKED = 5
        SYS_ERROR = 6
. " ISHMED_BEW_TRANSFER




ABAP code using 7.40 inline data declarations to call FM ISHMED_BEW_TRANSFER

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.

 
 
"SELECT single STOID FROM NBEW INTO @DATA(ld_e_stoid).
 
 
"SELECT single GPART FROM NGPA INTO @DATA(ld_e_gpart).
 
 
"SELECT single MARK FROM RNT40 INTO @DATA(ld_i_lock_tab).
DATA(ld_i_lock_tab) = '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!