SAP BAPI_TZSRVSCMB_DELMULTI Function Module for Deletion of Transportation Zones









BAPI_TZSRVSCMB_DELMULTI is a standard bapi tzsrvscmb delmulti SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Deletion of Transportation Zones 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 bapi tzsrvscmb delmulti FM, simply by entering the name BAPI_TZSRVSCMB_DELMULTI into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCMB0008
Program Name: SAPLSCMB0008
Main Program: SAPLSCMB0008
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_TZSRVSCMB_DELMULTI 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 'BAPI_TZSRVSCMB_DELMULTI'"Deletion of Transportation Zones
EXPORTING
LOGICAL_SYSTEM = "Logical System
* BUSINESS_SYSTEM_GROUP = "Business System Group
* COMMIT_CONTROL = 'A' "COMMIT Control

TABLES
* ZONE_HD = "Zone BAPI: Zone Header
* ZONE_DESCRIPTION = "Zone BAPI: Zone Description
* ZONE_LOCATION = "Zone BAPI: Directly assigned Locations
* ZONE_PCODE_INTERVAL = "Zone BAPI: Postal Code Interval
* ZONE_REGION = "Zone BAPI: Region
* ZONE_HIERARCHY = "Transportation Zone: Hierarchy
* EXTENSION_IN = "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
* RETURN = "Return Parameter
.



IMPORTING Parameters details for BAPI_TZSRVSCMB_DELMULTI

LOGICAL_SYSTEM - Logical System

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

BUSINESS_SYSTEM_GROUP - Business System Group

Data type: BAPISCMBGENFIELDS-LOGQS
Optional: Yes
Call by Reference: No ( called with pass by value option)

COMMIT_CONTROL - COMMIT Control

Data type: BAPI10002GENFIELDS-COMMIT_CONTROL
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_TZSRVSCMB_DELMULTI

ZONE_HD - Zone BAPI: Zone Header

Data type: BAPISCMB0008ZONEHEAD
Optional: Yes
Call by Reference: Yes

ZONE_DESCRIPTION - Zone BAPI: Zone Description

Data type: BAPISCMB0008ZONEDESC
Optional: Yes
Call by Reference: Yes

ZONE_LOCATION - Zone BAPI: Directly assigned Locations

Data type: BAPISCMB0008ZONELOC
Optional: Yes
Call by Reference: Yes

ZONE_PCODE_INTERVAL - Zone BAPI: Postal Code Interval

Data type: BAPISCMB0008PCODEINT
Optional: Yes
Call by Reference: Yes

ZONE_REGION - Zone BAPI: Region

Data type: BAPISCMB0008REGION
Optional: Yes
Call by Reference: Yes

ZONE_HIERARCHY - Transportation Zone: Hierarchy

Data type: BAPISCMB0008ZONEHIER
Optional: Yes
Call by Reference: Yes

EXTENSION_IN - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameter

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_TZSRVSCMB_DELMULTI 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:
lt_zone_hd  TYPE STANDARD TABLE OF BAPISCMB0008ZONEHEAD, "   
lv_logical_system  TYPE BAPISCMBGENFIELDS-LOGICAL_SYSTEM, "   
lt_zone_description  TYPE STANDARD TABLE OF BAPISCMB0008ZONEDESC, "   
lv_business_system_group  TYPE BAPISCMBGENFIELDS-LOGQS, "   
lt_zone_location  TYPE STANDARD TABLE OF BAPISCMB0008ZONELOC, "   
lv_commit_control  TYPE BAPI10002GENFIELDS-COMMIT_CONTROL, "   'A'
lt_zone_pcode_interval  TYPE STANDARD TABLE OF BAPISCMB0008PCODEINT, "   
lt_zone_region  TYPE STANDARD TABLE OF BAPISCMB0008REGION, "   
lt_zone_hierarchy  TYPE STANDARD TABLE OF BAPISCMB0008ZONEHIER, "   
lt_extension_in  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_TZSRVSCMB_DELMULTI'  "Deletion of Transportation Zones
    EXPORTING
         LOGICAL_SYSTEM = lv_logical_system
         BUSINESS_SYSTEM_GROUP = lv_business_system_group
         COMMIT_CONTROL = lv_commit_control
    TABLES
         ZONE_HD = lt_zone_hd
         ZONE_DESCRIPTION = lt_zone_description
         ZONE_LOCATION = lt_zone_location
         ZONE_PCODE_INTERVAL = lt_zone_pcode_interval
         ZONE_REGION = lt_zone_region
         ZONE_HIERARCHY = lt_zone_hierarchy
         EXTENSION_IN = lt_extension_in
         RETURN = lt_return
. " BAPI_TZSRVSCMB_DELMULTI




ABAP code using 7.40 inline data declarations to call FM BAPI_TZSRVSCMB_DELMULTI

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 LOGICAL_SYSTEM FROM BAPISCMBGENFIELDS INTO @DATA(ld_logical_system).
 
 
"SELECT single LOGQS FROM BAPISCMBGENFIELDS INTO @DATA(ld_business_system_group).
 
 
"SELECT single COMMIT_CONTROL FROM BAPI10002GENFIELDS INTO @DATA(ld_commit_control).
DATA(ld_commit_control) = 'A'.
 
 
 
 
 
 


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!