SAP BAPI_ALE_MODEL_GET Function Module for BAPI: read ALE distribution model









BAPI_ALE_MODEL_GET is a standard bapi ale model get 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: read ALE distribution model 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 ale model get FM, simply by entering the name BAPI_ALE_MODEL_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: BD02
Program Name: SAPLBD02
Main Program:
Appliation area: S
Release date: 20-Nov-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_ALE_MODEL_GET 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_ALE_MODEL_GET'"BAPI: read ALE distribution model
IMPORTING
RETURN = "Return

TABLES
* VIEWS = "model view
* FILTEROBJECTTYPES = "Filter objects
* FILTEROBJECTS = "Filter values
* SYSTEMS = "System in model
* SYSTEMSINVIEWS = "Systems per view
* MESSAGETYPELINKS = "Message links
* BAPIS = "BAPIs in the model
* BAPILINKS = "BAPI links
* MESSAGETYPES = "Messages in model
* BAPIFILTERS = "BAPI filters
* MESSAGETYPEFILTERS = "Message filters
.



EXPORTING Parameters details for BAPI_ALE_MODEL_GET

RETURN - Return

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

TABLES Parameters details for BAPI_ALE_MODEL_GET

VIEWS - model view

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

FILTEROBJECTTYPES - Filter objects

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

FILTEROBJECTS - Filter values

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

SYSTEMS - System in model

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

SYSTEMSINVIEWS - Systems per view

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

MESSAGETYPELINKS - Message links

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

BAPIS - BAPIs in the model

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

BAPILINKS - BAPI links

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

MESSAGETYPES - Messages in model

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

BAPIFILTERS - BAPI filters

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

MESSAGETYPEFILTERS - Message filters

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

Copy and paste ABAP code example for BAPI_ALE_MODEL_GET 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_views  TYPE STANDARD TABLE OF BAPI_VIEW, "   
lv_return  TYPE BAPIRET2, "   
lt_filterobjecttypes  TYPE STANDARD TABLE OF BAPI_FOBJT, "   
lt_filterobjects  TYPE STANDARD TABLE OF BAPI_FOBJV, "   
lt_systems  TYPE STANDARD TABLE OF BAPI_LSYS, "   
lt_systemsinviews  TYPE STANDARD TABLE OF BAPI_SYSV, "   
lt_messagetypelinks  TYPE STANDARD TABLE OF BAPI_MLINK, "   
lt_bapis  TYPE STANDARD TABLE OF BAPI_API, "   
lt_bapilinks  TYPE STANDARD TABLE OF BAPI_BLINK, "   
lt_messagetypes  TYPE STANDARD TABLE OF BAPI_MTYP, "   
lt_bapifilters  TYPE STANDARD TABLE OF BAPI_BFLT, "   
lt_messagetypefilters  TYPE STANDARD TABLE OF BAPI_MFLT. "   

  CALL FUNCTION 'BAPI_ALE_MODEL_GET'  "BAPI: read ALE distribution model
    IMPORTING
         RETURN = lv_return
    TABLES
         VIEWS = lt_views
         FILTEROBJECTTYPES = lt_filterobjecttypes
         FILTEROBJECTS = lt_filterobjects
         SYSTEMS = lt_systems
         SYSTEMSINVIEWS = lt_systemsinviews
         MESSAGETYPELINKS = lt_messagetypelinks
         BAPIS = lt_bapis
         BAPILINKS = lt_bapilinks
         MESSAGETYPES = lt_messagetypes
         BAPIFILTERS = lt_bapifilters
         MESSAGETYPEFILTERS = lt_messagetypefilters
. " BAPI_ALE_MODEL_GET




ABAP code using 7.40 inline data declarations to call FM BAPI_ALE_MODEL_GET

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!