SAP ALE_PRDSRVAPS_REMOVECLASSES Function Module for BAPI -> IDoc: ALE_PRDSRVAPS_REMOVECLASSES









ALE_PRDSRVAPS_REMOVECLASSES is a standard ale prdsrvaps removeclasses SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_PRDSRVAPS_REMOVECLASSES 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 ale prdsrvaps removeclasses FM, simply by entering the name ALE_PRDSRVAPS_REMOVECLASSES into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_PRDSRVAPS_REMOVECLASSES 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 'ALE_PRDSRVAPS_REMOVECLASSES'"BAPI -> IDoc: ALE_PRDSRVAPS_REMOVECLASSES
EXPORTING
* LOGICALSYSTEM = "
* COMMITCONTROL = "
* OBJ_TYPE = 'BUS10001' "
* SERIAL_ID = '0' "

TABLES
PRODUCTCLASSKEY = "
* EXTENSIONIN = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "

EXCEPTIONS
ERROR_CREATING_IDOCS = 1
.




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_SAPL10001_001 User Exit for Method 'SaveMultiple' of Business Object BUS10001
EXIT_SAPL10001_002 User Exit for Method 'GetList' of Business Object BUS10001
EXIT_SAPL10001_003 User Exit for Method 'DeleteProduct' of Business Object BUS10001
EXIT_SAPL10001_004 User Exit for Method 'DeleteLocationProduct' Business Object BUS10001

IMPORTING Parameters details for ALE_PRDSRVAPS_REMOVECLASSES

LOGICALSYSTEM -

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

COMMITCONTROL -

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS10001'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_PRDSRVAPS_REMOVECLASSES

PRODUCTCLASSKEY -

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

EXTENSIONIN -

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

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

Copy and paste ABAP code example for ALE_PRDSRVAPS_REMOVECLASSES 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_logicalsystem  TYPE BAPISCMBGENFIELDS-LOGICAL_SYSTEM, "   
lt_productclasskey  TYPE STANDARD TABLE OF BAPI10001PRDCLASSKEY, "   
lv_error_creating_idocs  TYPE BAPI10001PRDCLASSKEY, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_commitcontrol  TYPE BAPI10001GENFIELDS-COMMIT_CONTROL, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'BUS10001'
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_serial_id  TYPE SERIAL-CHNUM, "   '0'
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID. "   

  CALL FUNCTION 'ALE_PRDSRVAPS_REMOVECLASSES'  "BAPI -> IDoc: ALE_PRDSRVAPS_REMOVECLASSES
    EXPORTING
         LOGICALSYSTEM = lv_logicalsystem
         COMMITCONTROL = lv_commitcontrol
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         PRODUCTCLASSKEY = lt_productclasskey
         EXTENSIONIN = lt_extensionin
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_PRDSRVAPS_REMOVECLASSES




ABAP code using 7.40 inline data declarations to call FM ALE_PRDSRVAPS_REMOVECLASSES

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_logicalsystem).
 
 
 
 
"SELECT single COMMIT_CONTROL FROM BAPI10001GENFIELDS INTO @DATA(ld_commitcontrol).
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'BUS10001'.
 
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 
 
 


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!