SAP MAP2I_BAPIDLVSERIALNUMBER_TO_S Function Module for NOTRANSL: bapidlvserialnumber -> shp_sernr









MAP2I_BAPIDLVSERIALNUMBER_TO_S is a standard map2i bapidlvserialnumber to s 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: bapidlvserialnumber -> shp_sernr 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 map2i bapidlvserialnumber to s FM, simply by entering the name MAP2I_BAPIDLVSERIALNUMBER_TO_S into the relevant SAP transaction such as SE37 or SE38.

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



Function MAP2I_BAPIDLVSERIALNUMBER_TO_S 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 'MAP2I_BAPIDLVSERIALNUMBER_TO_S'"NOTRANSL: bapidlvserialnumber -> shp_sernr
EXPORTING
BAPIDLVSERIALNUMBER = "Serial Number

CHANGING
SHP_SERNR = "Serial Number
.




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_SAPLV50I_001 User Exit BAPI Inbound Delivery Replication
EXIT_SAPLV50I_002 User Exit BAPI Inbound Delivery Confirmation
EXIT_SAPLV50I_003 User Exit BAPI Outbound Delivery Replication
EXIT_SAPLV50I_004 User Exit BAPI Outbound Delivery Confirmation
EXIT_SAPLV50I_009 User Exit BAPI for Changing Inbound Deliveries
EXIT_SAPLV50I_010 User Exit BAPI for Changing Outbound Deliveries

IMPORTING Parameters details for MAP2I_BAPIDLVSERIALNUMBER_TO_S

BAPIDLVSERIALNUMBER - Serial Number

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

CHANGING Parameters details for MAP2I_BAPIDLVSERIALNUMBER_TO_S

SHP_SERNR - Serial Number

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

Copy and paste ABAP code example for MAP2I_BAPIDLVSERIALNUMBER_TO_S 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_shp_sernr  TYPE SHP_SERNR, "   
lv_bapidlvserialnumber  TYPE BAPIDLVSERIALNUMBER. "   

  CALL FUNCTION 'MAP2I_BAPIDLVSERIALNUMBER_TO_S'  "NOTRANSL: bapidlvserialnumber -> shp_sernr
    EXPORTING
         BAPIDLVSERIALNUMBER = lv_bapidlvserialnumber
    CHANGING
         SHP_SERNR = lv_shp_sernr
. " MAP2I_BAPIDLVSERIALNUMBER_TO_S




ABAP code using 7.40 inline data declarations to call FM MAP2I_BAPIDLVSERIALNUMBER_TO_S

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!