SAP ISM_COMPL_SUBSEQ_PROCESSOR_CHK Function Module for IS-M: Check Subsequent Processor of Complaint
ISM_COMPL_SUBSEQ_PROCESSOR_CHK is a standard ism compl subseq processor chk 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: Check Subsequent Processor of Complaint 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 compl subseq processor chk FM, simply by entering the name ISM_COMPL_SUBSEQ_PROCESSOR_CHK into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHA2
Program Name: SAPLJHA2
Main Program: SAPLJHA2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_COMPL_SUBSEQ_PROCESSOR_CHK 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_COMPL_SUBSEQ_PROCESSOR_CHK'"IS-M: Check Subsequent Processor of Complaint.
EXPORTING
PV_XFLAG_R3_USER = "
PV_SUBSEQU_PROCESSOR = "IS-M: Subsequent Processor
* PV_DIALOG = 'X' "IS-M: Dialog Functions Admissible
IMPORTING
PS_MSG = "IS-M: Internal Structure for Transferring Error Messages
CHANGING
* PT_RETURN = "Return Table
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_SAPLJHA2_001 IS-M/AM: Copy Order Objects
IMPORTING Parameters details for ISM_COMPL_SUBSEQ_PROCESSOR_CHK
PV_XFLAG_R3_USER -
Data type: XREKLBEARB_USROptional: No
Call by Reference: Yes
PV_SUBSEQU_PROCESSOR - IS-M: Subsequent Processor
Data type: WEITERBEAROptional: No
Call by Reference: Yes
PV_DIALOG - IS-M: Dialog Functions Admissible
Data type: ISM_DIALOG_ALLOWEDDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISM_COMPL_SUBSEQ_PROCESSOR_CHK
PS_MSG - IS-M: Internal Structure for Transferring Error Messages
Data type: RJMSGOptional: No
Call by Reference: Yes
CHANGING Parameters details for ISM_COMPL_SUBSEQ_PROCESSOR_CHK
PT_RETURN - Return Table
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ISM_COMPL_SUBSEQ_PROCESSOR_CHK 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_ps_msg | TYPE RJMSG, " | |||
| lv_pt_return | TYPE BAPIRET2_T, " | |||
| lv_pv_xflag_r3_user | TYPE XREKLBEARB_USR, " | |||
| lv_pv_subsequ_processor | TYPE WEITERBEAR, " | |||
| lv_pv_dialog | TYPE ISM_DIALOG_ALLOWED. " 'X' |
|   CALL FUNCTION 'ISM_COMPL_SUBSEQ_PROCESSOR_CHK' "IS-M: Check Subsequent Processor of Complaint |
| EXPORTING | ||
| PV_XFLAG_R3_USER | = lv_pv_xflag_r3_user | |
| PV_SUBSEQU_PROCESSOR | = lv_pv_subsequ_processor | |
| PV_DIALOG | = lv_pv_dialog | |
| IMPORTING | ||
| PS_MSG | = lv_ps_msg | |
| CHANGING | ||
| PT_RETURN | = lv_pt_return | |
| . " ISM_COMPL_SUBSEQ_PROCESSOR_CHK | ||
ABAP code using 7.40 inline data declarations to call FM ISM_COMPL_SUBSEQ_PROCESSOR_CHK
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_dialog) | = 'X'. | |||
Search for further information about these or an SAP related objects