SAP ALE_BAPI_GET_UNIQUE_RECEIVER Function Module for Determines precisely one receiver for a synchronous BAPI

Search SAP Function Modules

ALE_BAPI_GET_UNIQUE_RECEIVER is a standard ale bapi get unique receiver SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines precisely one receiver for a synchronous BAPI 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 bapi get unique receiver FM, simply by entering the name ALE_BAPI_GET_UNIQUE_RECEIVER into the relevant SAP transaction such as SE37 or SE38.

Function Group: BDAPI
Program Name: SAPLBDAPI
Main Program:
Appliation area: S
Release date: 30-Mar-1998
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_BAPI_GET_UNIQUE_RECEIVER 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_BAPI_GET_UNIQUE_RECEIVER'"Determines precisely one receiver for a synchronous BAPI
  EXPORTING
   OBJECT =  "BOR object of BAPI
   METHOD =  "BOR method of BAPI

 IMPORTING
   RECEIVER =  "Receiver system of BAPI

TABLES
   FILTEROBJECTS_VALUES =  "Filter object types and values

EXCEPTIONS
   ERROR_IN_FILTEROBJECTS = 1    ERROR_IN_ALE_CUSTOMIZING = 2    NOT_UNIQUE_RECEIVER = 3    NO_RFC_DESTINATION_MAINTAINED = 4 

.

IMPORTING Parameters details for ALE_BAPI_GET_UNIQUE_RECEIVER

OBJECT - BOR object of BAPI

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

METHOD - BOR method of BAPI

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

EXPORTING Parameters details for ALE_BAPI_GET_UNIQUE_RECEIVER

RECEIVER - Receiver system of BAPI

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

TABLES Parameters details for ALE_BAPI_GET_UNIQUE_RECEIVER

FILTEROBJECTS_VALUES - Filter object types and values

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

EXCEPTIONS details

ERROR_IN_FILTEROBJECTS - Filter objects either have errors or are incomplete

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

ERROR_IN_ALE_CUSTOMIZING - Error in ALE Customizing

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

NOT_UNIQUE_RECEIVER - There are several receiver systems for the BAPI

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

NO_RFC_DESTINATION_MAINTAINED - RFC destination has not been specified for the logical system

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

Copy and paste ABAP code example for ALE_BAPI_GET_UNIQUE_RECEIVER 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.

ABAP code using 7.40 inline data declarations to call FM ALE_BAPI_GET_UNIQUE_RECEIVER

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