SAP MAP2I_BAPI_COUNT_ITEMS_2_IISEG Function Module for NOTRANSL: bapi_physinv_count_items -> iiseg









MAP2I_BAPI_COUNT_ITEMS_2_IISEG is a standard map2i bapi count items 2 iiseg 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: bapi_physinv_count_items -> iiseg 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 bapi count items 2 iiseg FM, simply by entering the name MAP2I_BAPI_COUNT_ITEMS_2_IISEG into the relevant SAP transaction such as SE37 or SE38.

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



Function MAP2I_BAPI_COUNT_ITEMS_2_IISEG 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_BAPI_COUNT_ITEMS_2_IISEG'"NOTRANSL: bapi_physinv_count_items -> iiseg
EXPORTING
BAPI_PHYSINV_COUNT_ITEMS = "BAPI Communication Structure: Count Data for Item

CHANGING
IISEG = "Import ISEG for FM physical inventory

EXCEPTIONS
ERROR_CONVERTING_ISO_CODE = 1 ERROR_CONVERTING_CURR_AMOUNT = 2
.



IMPORTING Parameters details for MAP2I_BAPI_COUNT_ITEMS_2_IISEG

BAPI_PHYSINV_COUNT_ITEMS - BAPI Communication Structure: Count Data for Item

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

CHANGING Parameters details for MAP2I_BAPI_COUNT_ITEMS_2_IISEG

IISEG - Import ISEG for FM physical inventory

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

EXCEPTIONS details

ERROR_CONVERTING_ISO_CODE -

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

ERROR_CONVERTING_CURR_AMOUNT -

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

Copy and paste ABAP code example for MAP2I_BAPI_COUNT_ITEMS_2_IISEG 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_iiseg  TYPE IISEG, "   
lv_bapi_physinv_count_items  TYPE BAPI_PHYSINV_COUNT_ITEMS, "   
lv_error_converting_iso_code  TYPE BAPI_PHYSINV_COUNT_ITEMS, "   
lv_error_converting_curr_amount  TYPE BAPI_PHYSINV_COUNT_ITEMS. "   

  CALL FUNCTION 'MAP2I_BAPI_COUNT_ITEMS_2_IISEG'  "NOTRANSL: bapi_physinv_count_items -> iiseg
    EXPORTING
         BAPI_PHYSINV_COUNT_ITEMS = lv_bapi_physinv_count_items
    CHANGING
         IISEG = lv_iiseg
    EXCEPTIONS
        ERROR_CONVERTING_ISO_CODE = 1
        ERROR_CONVERTING_CURR_AMOUNT = 2
. " MAP2I_BAPI_COUNT_ITEMS_2_IISEG




ABAP code using 7.40 inline data declarations to call FM MAP2I_BAPI_COUNT_ITEMS_2_IISEG

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!