SAP MB_SIMULATE_SERIALNUMBER Function Module for NOTRANSL: Lesen serialnummernrelevanter Informationen zur Warenbewegung









MB_SIMULATE_SERIALNUMBER is a standard mb simulate serialnumber SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Lesen serialnummernrelevanter Informationen zur Warenbewegung processing and below is the pattern details for this FM, 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 mb simulate serialnumber FM, simply by entering the name MB_SIMULATE_SERIALNUMBER into the relevant SAP transaction such as SE37 or SE38.

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



Function MB_SIMULATE_SERIALNUMBER 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 'MB_SIMULATE_SERIALNUMBER'"NOTRANSL: Lesen serialnummernrelevanter Informationen zur Warenbewegung
EXPORTING
IMSEG = "MMIM: Input Structure for General FM to Post Goods Movement
IMKPF = "MMIM: Input Structure for General FM to Post Goods Movement
* ITCODE = ' ' "ABAP System Field: Current Transaction Code

IMPORTING
EBSTUP = "Stock Information for the Serial Number
EBSTCH = "Stock Information for the Serial Number
ESHKZG = "Debit/Credit Indicator
EVRGNG = "Business Transaction
ESNBWG = "Movement Type Group for Serial Number Profile
E_EMKPF = "MMIM: Output Structure For General FM To Post Goods Movement
E_EMSEG = "MMIM: Output Structure For General FM To Post Goods Movement
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLMBWL_400 call customer function: transfer of details to GR

IMPORTING Parameters details for MB_SIMULATE_SERIALNUMBER

IMSEG - MMIM: Input Structure for General FM to Post Goods Movement

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

IMKPF - MMIM: Input Structure for General FM to Post Goods Movement

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

ITCODE - ABAP System Field: Current Transaction Code

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

EXPORTING Parameters details for MB_SIMULATE_SERIALNUMBER

EBSTUP - Stock Information for the Serial Number

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

EBSTCH - Stock Information for the Serial Number

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

ESHKZG - Debit/Credit Indicator

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

EVRGNG - Business Transaction

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

ESNBWG - Movement Type Group for Serial Number Profile

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

E_EMKPF - MMIM: Output Structure For General FM To Post Goods Movement

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

E_EMSEG - MMIM: Output Structure For General FM To Post Goods Movement

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

Copy and paste ABAP code example for MB_SIMULATE_SERIALNUMBER 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_imseg  TYPE IMSEG, "   
lv_ebstup  TYPE BSINF, "   
lv_imkpf  TYPE IMKPF, "   
lv_ebstch  TYPE BSINF, "   
lv_eshkzg  TYPE T156-SHKZG, "   
lv_itcode  TYPE SY-TCODE, "   SPACE
lv_evrgng  TYPE ST156S-VRGNG, "   
lv_esnbwg  TYPE ST156S-SNBWG, "   
lv_e_emkpf  TYPE EMKPF, "   
lv_e_emseg  TYPE EMSEG. "   

  CALL FUNCTION 'MB_SIMULATE_SERIALNUMBER'  "NOTRANSL: Lesen serialnummernrelevanter Informationen zur Warenbewegung
    EXPORTING
         IMSEG = lv_imseg
         IMKPF = lv_imkpf
         ITCODE = lv_itcode
    IMPORTING
         EBSTUP = lv_ebstup
         EBSTCH = lv_ebstch
         ESHKZG = lv_eshkzg
         EVRGNG = lv_evrgng
         ESNBWG = lv_esnbwg
         E_EMKPF = lv_e_emkpf
         E_EMSEG = lv_e_emseg
. " MB_SIMULATE_SERIALNUMBER




ABAP code using 7.40 inline data declarations to call FM MB_SIMULATE_SERIALNUMBER

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 SHKZG FROM T156 INTO @DATA(ld_eshkzg).
 
"SELECT single TCODE FROM SY INTO @DATA(ld_itcode).
DATA(ld_itcode) = ' '.
 
"SELECT single VRGNG FROM ST156S INTO @DATA(ld_evrgng).
 
"SELECT single SNBWG FROM ST156S INTO @DATA(ld_esnbwg).
 
 
 


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!