SAP MAP2E_LIPSVB_TO_BAPIOBDLVITEM Function Module for NOTRANSL: lipsvb -> bapiobdlvitem









MAP2E_LIPSVB_TO_BAPIOBDLVITEM is a standard map2e lipsvb to bapiobdlvitem 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: lipsvb -> bapiobdlvitem 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 map2e lipsvb to bapiobdlvitem FM, simply by entering the name MAP2E_LIPSVB_TO_BAPIOBDLVITEM into the relevant SAP transaction such as SE37 or SE38.

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



Function MAP2E_LIPSVB_TO_BAPIOBDLVITEM 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 'MAP2E_LIPSVB_TO_BAPIOBDLVITEM'"NOTRANSL: lipsvb -> bapiobdlvitem
EXPORTING
LIPSVB = "

CHANGING
BAPIOBDLVITEM = "
.




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_SAPLV50K_005 User Exit BAPI Inbound Delivery Replication (Outbound from Sending System)
EXIT_SAPLV50K_006 User Exit BAPI Inbound Deliv. Confirmation (Outbound from Sending System)
EXIT_SAPLV50K_007 User Exit BAPI Outbound Delivery Replication (Outbound from Sender System)
EXIT_SAPLV50K_008 User Exit BAPI Outbound Deliv. Confirmation (Outbound from Sending System)
EXIT_SAPLV50K_011 User Exit BAPI for Changing Inbound Deliveries (Outbound)
EXIT_SAPLV50K_012 User Exit BAPI for Changing Outbound Deliveries (Outbound)

IMPORTING Parameters details for MAP2E_LIPSVB_TO_BAPIOBDLVITEM

LIPSVB -

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

CHANGING Parameters details for MAP2E_LIPSVB_TO_BAPIOBDLVITEM

BAPIOBDLVITEM -

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

Copy and paste ABAP code example for MAP2E_LIPSVB_TO_BAPIOBDLVITEM 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_lipsvb  TYPE LIPSVB, "   
lv_bapiobdlvitem  TYPE BAPIOBDLVITEM. "   

  CALL FUNCTION 'MAP2E_LIPSVB_TO_BAPIOBDLVITEM'  "NOTRANSL: lipsvb -> bapiobdlvitem
    EXPORTING
         LIPSVB = lv_lipsvb
    CHANGING
         BAPIOBDLVITEM = lv_bapiobdlvitem
. " MAP2E_LIPSVB_TO_BAPIOBDLVITEM




ABAP code using 7.40 inline data declarations to call FM MAP2E_LIPSVB_TO_BAPIOBDLVITEM

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!