SAP RECIPIENT_GET_FROM_ALE_MODEL Function Module for Find receiving logical system for the given partner

Search SAP Function Modules

RECIPIENT_GET_FROM_ALE_MODEL is a standard recipient get from ale model SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find receiving logical system for the given partner 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 recipient get from ale model FM, simply by entering the name RECIPIENT_GET_FROM_ALE_MODEL into the relevant SAP transaction such as SE37 or SE38.

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

Function RECIPIENT_GET_FROM_ALE_MODEL 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 'RECIPIENT_GET_FROM_ALE_MODEL'"Find receiving logical system for the given partner
  EXPORTING
   NAST =  "Message status of message control

 IMPORTING
   PARTNER_FUNCTION =  "Partner role of receiver system
   PARTNER_NUMBER =  "Partner number of receiver system

CHANGING
   PARTNER_TYPE =  "Partner type

EXCEPTIONS
   NO_RECIPIENT_FOUND = 1    OWN_SYSTEM_NOT_DEFINED = 2    OTHER_ERROR = 3    NO_MESSAGE_TYPE_FOUND = 4    MULTIPLE_MESSAGE_TYPES_FOUND = 5    MULTIPLE_RECIPIENTS_FOUND = 6    WRONG_PARTNER_TYPE = 7 

.

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_SAPLBDMO_001 Changes/Enhancements to ALE Distribution Reference Model

IMPORTING Parameters details for RECIPIENT_GET_FROM_ALE_MODEL

NAST - Message status of message control

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

EXPORTING Parameters details for RECIPIENT_GET_FROM_ALE_MODEL

PARTNER_FUNCTION - Partner role of receiver system

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

PARTNER_NUMBER - Partner number of receiver system

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

CHANGING Parameters details for RECIPIENT_GET_FROM_ALE_MODEL

PARTNER_TYPE - Partner type

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

EXCEPTIONS details

NO_RECIPIENT_FOUND - Bo recipient found

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

OWN_SYSTEM_NOT_DEFINED - Own logical system not defined

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

OTHER_ERROR - Other error

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

NO_MESSAGE_TYPE_FOUND - No message type found

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

MULTIPLE_MESSAGE_TYPES_FOUND - Multiple message types found

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

MULTIPLE_RECIPIENTS_FOUND - Multiple recipients found

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

WRONG_PARTNER_TYPE - Wrong partner type passed

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

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

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