SAP ISM_WWW_COMPLAINT_TEMPDATA_ADD Function Module for IS-M/SD: Store Entry in Temporary Internet Table
ISM_WWW_COMPLAINT_TEMPDATA_ADD is a standard ism www complaint tempdata add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Store Entry in Temporary Internet Table 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 ism www complaint tempdata add FM, simply by entering the name ISM_WWW_COMPLAINT_TEMPDATA_ADD into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKWWWCOMPL
Program Name: SAPLJKWWWCOMPL
Main Program: SAPLJKWWWCOMPL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function ISM_WWW_COMPLAINT_TEMPDATA_ADD 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 'ISM_WWW_COMPLAINT_TEMPDATA_ADD'"IS-M/SD: Store Entry in Temporary Internet Table.
EXPORTING
PS_ORDER_COMPL = "IS-M/SD: Order Data for Complaint in Internet
* PT_TXLINE = "IS-M: Table Type for Text Lines with Counter
* PS_RJMSG = "IS-M/SD: Internal Structure for Transferring Error Messages
PV_GPNR = "IS-M: Business Partner Key
PV_XIAC_PROTOCOL = "IS-M: Log Orders/Changes from Internet
PV_TEXT_IAC = "IS-M: Text Describing Variant of an IAC
* PV_ERFDATE = SY-DATUM "Created On
* PV_ERFTIME = SY-UZEIT "Time Created
* PV_XNO_ERROR = ' ' "
EXCEPTIONS
WRONG_INPUT = 1 ERROR_OCCURRED = 2
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_SAPLJKWWWCOMPL_004 IS-M/SD: Complaint - Assign Default Complaint Category
IMPORTING Parameters details for ISM_WWW_COMPLAINT_TEMPDATA_ADD
PS_ORDER_COMPL - IS-M/SD: Order Data for Complaint in Internet
Data type: RJKWWW_ORDER_COMPLOptional: No
Call by Reference: Yes
PT_TXLINE - IS-M: Table Type for Text Lines with Counter
Data type: RJKWWW_TXLINE_TABOptional: Yes
Call by Reference: Yes
PS_RJMSG - IS-M/SD: Internal Structure for Transferring Error Messages
Data type: RJMSGOptional: Yes
Call by Reference: Yes
PV_GPNR - IS-M: Business Partner Key
Data type: GPNROptional: No
Call by Reference: Yes
PV_XIAC_PROTOCOL - IS-M: Log Orders/Changes from Internet
Data type: XIAC_PROTOCOLOptional: No
Call by Reference: Yes
PV_TEXT_IAC - IS-M: Text Describing Variant of an IAC
Data type: TEXTIAC_CONTROLOptional: No
Call by Reference: Yes
PV_ERFDATE - Created On
Data type: ERFDATEDefault: SY-DATUM
Optional: Yes
Call by Reference: Yes
PV_ERFTIME - Time Created
Data type: ERFTIMEDefault: SY-UZEIT
Optional: Yes
Call by Reference: Yes
PV_XNO_ERROR -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
WRONG_INPUT -
Data type:Optional: No
Call by Reference: Yes
ERROR_OCCURRED - An Error Has Occurred
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_WWW_COMPLAINT_TEMPDATA_ADD 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_wrong_input | TYPE STRING, " | |||
lv_ps_order_compl | TYPE RJKWWW_ORDER_COMPL, " | |||
lv_pt_txline | TYPE RJKWWW_TXLINE_TAB, " | |||
lv_error_occurred | TYPE RJKWWW_TXLINE_TAB, " | |||
lv_ps_rjmsg | TYPE RJMSG, " | |||
lv_pv_gpnr | TYPE GPNR, " | |||
lv_pv_xiac_protocol | TYPE XIAC_PROTOCOL, " | |||
lv_pv_text_iac | TYPE TEXTIAC_CONTROL, " | |||
lv_pv_erfdate | TYPE ERFDATE, " SY-DATUM | |||
lv_pv_erftime | TYPE ERFTIME, " SY-UZEIT | |||
lv_pv_xno_error | TYPE XFELD. " SPACE |
  CALL FUNCTION 'ISM_WWW_COMPLAINT_TEMPDATA_ADD' "IS-M/SD: Store Entry in Temporary Internet Table |
EXPORTING | ||
PS_ORDER_COMPL | = lv_ps_order_compl | |
PT_TXLINE | = lv_pt_txline | |
PS_RJMSG | = lv_ps_rjmsg | |
PV_GPNR | = lv_pv_gpnr | |
PV_XIAC_PROTOCOL | = lv_pv_xiac_protocol | |
PV_TEXT_IAC | = lv_pv_text_iac | |
PV_ERFDATE | = lv_pv_erfdate | |
PV_ERFTIME | = lv_pv_erftime | |
PV_XNO_ERROR | = lv_pv_xno_error | |
EXCEPTIONS | ||
WRONG_INPUT = 1 | ||
ERROR_OCCURRED = 2 | ||
. " ISM_WWW_COMPLAINT_TEMPDATA_ADD |
ABAP code using 7.40 inline data declarations to call FM ISM_WWW_COMPLAINT_TEMPDATA_ADD
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.DATA(ld_pv_erfdate) | = SY-DATUM. | |||
DATA(ld_pv_erftime) | = SY-UZEIT. | |||
DATA(ld_pv_xno_error) | = ' '. | |||
Search for further information about these or an SAP related objects