SAP ISU_SMS_TRIGGER_IN Function Module for Send SMS for Billing,Payment Reminder & Payment Acknowledgement

Search SAP Function Modules

ISU_SMS_TRIGGER_IN is a standard isu sms trigger in SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Send SMS for Billing,Payment Reminder & Payment Acknowledgement 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 isu sms trigger in FM, simply by entering the name ISU_SMS_TRIGGER_IN into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_SMS_TRIGGER_IN 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 'ISU_SMS_TRIGGER_IN'"Send SMS for Billing,Payment Reminder & Payment Acknowledgement
  EXPORTING
   IT_PRINT_DOC_INFO =  "table type for erdk_sms_in
*  IV_IMMEDIATE =  "set 'X' for immediate sending the sms
*  IV_INV_SEND =  "set 'X' for send sms for invoicing
*  IV_P_ACK_SEND =  "set 'X' for send sms for payment ack
*  IV_P_REM_SEND =  "set 'X' for send sms for payment reminder

 IMPORTING
   ET_GUID =  "table type for ESTATUS_SMS_GUID_IN
   EV_TEXT_INITIAL =  "Boolean Variable (X=True, -=False, Space=Unknown)
   ET_MESSAGES =  "Message META description

.

IMPORTING Parameters details for ISU_SMS_TRIGGER_IN

IT_PRINT_DOC_INFO - table type for erdk_sms_in

Data type: TY_ERDK_SMS_IN
Optional: No
Call by Reference: Yes

IV_IMMEDIATE - set 'X' for immediate sending the sms

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

IV_INV_SEND - set 'X' for send sms for invoicing

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

IV_P_ACK_SEND - set 'X' for send sms for payment ack

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

IV_P_REM_SEND - set 'X' for send sms for payment reminder

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_SMS_TRIGGER_IN

ET_GUID - table type for ESTATUS_SMS_GUID_IN

Data type: TY_ESTATUS_SMS_GUID_IN
Optional: No
Call by Reference: Yes

EV_TEXT_INITIAL - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: No
Call by Reference: Yes

ET_MESSAGES - Message META description

Data type: POWL_MSG_TTY
Optional: No
Call by Reference: Yes

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

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