SAP ALE_MODEL_DETERMINE_IF_TO_SEND Function Module for

Search SAP Function Modules

ALE_MODEL_DETERMINE_IF_TO_SEND is a standard ale model determine if to send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 model determine if to send FM, simply by entering the name ALE_MODEL_DETERMINE_IF_TO_SEND into the relevant SAP transaction such as SE37 or SE38.

Function Group: BDMO
Program Name: SAPLBDMO
Main Program: SAPLBDMO
Appliation area: S
Release date: 01-Jan-1970
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_MODEL_DETERMINE_IF_TO_SEND 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_MODEL_DETERMINE_IF_TO_SEND'"
  EXPORTING
   MESSAGE_TYPE =  "
*  SENDING_SYSTEM = ' ' "
*  RECEIVING_SYSTEM = ' ' "
*  VALIDDATE = SY-DATUM "

 IMPORTING
   IDOC_MUST_BE_SENT =  "

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

IMPORTING Parameters details for ALE_MODEL_DETERMINE_IF_TO_SEND

MESSAGE_TYPE -

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

SENDING_SYSTEM -

Data type: BDI_LOGSYS-LOGSYS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

RECEIVING_SYSTEM -

Data type: BDI_LOGSYS-LOGSYS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

VALIDDATE -

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ALE_MODEL_DETERMINE_IF_TO_SEND

IDOC_MUST_BE_SENT -

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

EXCEPTIONS details

OWN_SYSTEM_NOT_DEFINED -

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

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

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