SAP IPHN_CREATE_NOTIFICATION_PHONE Function Module for









IPHN_CREATE_NOTIFICATION_PHONE is a standard iphn create notification phone 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 iphn create notification phone FM, simply by entering the name IPHN_CREATE_NOTIFICATION_PHONE into the relevant SAP transaction such as SE37 or SE38.

Function Group: IPHN
Program Name: SAPLIPHN
Main Program:
Appliation area: I
Release date: 01-Jan-1970
Mode(Normal, Remote etc): Normal Function Module
Update:



Function IPHN_CREATE_NOTIFICATION_PHONE 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 'IPHN_CREATE_NOTIFICATION_PHONE'"
  EXPORTING
*  I_QMNUM =  "
*  I_TCODE =  "
*  I_QMART =  "
*  I_QMTXT =  "
*  I_CALLING_NUMBER =  "
*  I_CALLED_NUMBER =  "
*  I_CALL_DATE =  "
*  I_CALL_TIME =  "
*  I_CALLER_ADDRESS =  "

 IMPORTING
   E_QMNUM =  "

TABLES
*  I_CALLER_DATA_TAB =  "
.



IMPORTING Parameters details for IPHN_CREATE_NOTIFICATION_PHONE

I_QMNUM -

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

I_TCODE -

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

I_QMART -

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

I_QMTXT -

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

I_CALLING_NUMBER -

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

I_CALLED_NUMBER -

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

I_CALL_DATE -

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

I_CALL_TIME -

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

I_CALLER_ADDRESS -

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

EXPORTING Parameters details for IPHN_CREATE_NOTIFICATION_PHONE

E_QMNUM -

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

TABLES Parameters details for IPHN_CREATE_NOTIFICATION_PHONE

I_CALLER_DATA_TAB -

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

Copy and paste ABAP code example for IPHN_CREATE_NOTIFICATION_PHONE 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:
lv_e_qmnum  TYPE QMEL-QMNUM, "   
lv_i_qmnum  TYPE QMEL-QMNUM, "   
lt_i_caller_data_tab  TYPE STANDARD TABLE OF SPH_CALLER, "   
lv_i_tcode  TYPE T365-TCODE, "   
lv_i_qmart  TYPE QMEL-QMART, "   
lv_i_qmtxt  TYPE QMEL-QMTXT, "   
lv_i_calling_number  TYPE SPH_CALL-NO_CALLING, "   
lv_i_called_number  TYPE SPH_CALL-NO_DIALED, "   
lv_i_call_date  TYPE SPH_CALL-CALL_DATE, "   
lv_i_call_time  TYPE SPH_CALL-CALL_TIME, "   
lv_i_caller_address  TYPE ADDR_KEY. "   

  CALL FUNCTION 'IPHN_CREATE_NOTIFICATION_PHONE'  "
    EXPORTING
         I_QMNUM = lv_i_qmnum
         I_TCODE = lv_i_tcode
         I_QMART = lv_i_qmart
         I_QMTXT = lv_i_qmtxt
         I_CALLING_NUMBER = lv_i_calling_number
         I_CALLED_NUMBER = lv_i_called_number
         I_CALL_DATE = lv_i_call_date
         I_CALL_TIME = lv_i_call_time
         I_CALLER_ADDRESS = lv_i_caller_address
    IMPORTING
         E_QMNUM = lv_e_qmnum
    TABLES
         I_CALLER_DATA_TAB = lt_i_caller_data_tab
. " IPHN_CREATE_NOTIFICATION_PHONE




ABAP code using 7.40 inline data declarations to call FM IPHN_CREATE_NOTIFICATION_PHONE

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.

"SELECT single QMNUM FROM QMEL INTO @DATA(ld_e_qmnum).
 
"SELECT single QMNUM FROM QMEL INTO @DATA(ld_i_qmnum).
 
 
"SELECT single TCODE FROM T365 INTO @DATA(ld_i_tcode).
 
"SELECT single QMART FROM QMEL INTO @DATA(ld_i_qmart).
 
"SELECT single QMTXT FROM QMEL INTO @DATA(ld_i_qmtxt).
 
"SELECT single NO_CALLING FROM SPH_CALL INTO @DATA(ld_i_calling_number).
 
"SELECT single NO_DIALED FROM SPH_CALL INTO @DATA(ld_i_called_number).
 
"SELECT single CALL_DATE FROM SPH_CALL INTO @DATA(ld_i_call_date).
 
"SELECT single CALL_TIME FROM SPH_CALL INTO @DATA(ld_i_call_time).
 
 


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!