SAP SCPR_PR_MN_PROTOCOL Function Module for
SCPR_PR_MN_PROTOCOL is a standard scpr pr mn protocol 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 scpr pr mn protocol FM, simply by entering the name SCPR_PR_MN_PROTOCOL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCPRPROT
Program Name: SAPLSCPRPROT
Main Program: SAPLSCPRPROT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCPR_PR_MN_PROTOCOL 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 'SCPR_PR_MN_PROTOCOL'".
EXPORTING
* MAX_PROTOCOLS = "Int.
* ACT_SELECT = "
* ACTID_TABLE = "
* BCSET_TABLE = "BC Sets: BC Set Names to Pass From/To External Interface
* CATEGORY = ' ' "
EXCEPTIONS
NO_PROTOCOL = 1 WRONG_PARAMETERS = 2
IMPORTING Parameters details for SCPR_PR_MN_PROTOCOL
MAX_PROTOCOLS - Int.
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
ACT_SELECT -
Data type: SCPRACTINFOptional: Yes
Call by Reference: No ( called with pass by value option)
ACTID_TABLE -
Data type: SCPRACTIDOptional: Yes
Call by Reference: Yes
BCSET_TABLE - BC Sets: BC Set Names to Pass From/To External Interface
Data type: SCPR_BCSETSOptional: Yes
Call by Reference: Yes
CATEGORY -
Data type: SCPR_CTGRYDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_PROTOCOL -
Data type:Optional: No
Call by Reference: Yes
WRONG_PARAMETERS - Incorrect Parameter Transfer
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SCPR_PR_MN_PROTOCOL 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_no_protocol | TYPE STRING, " | |||
| lv_max_protocols | TYPE I, " | |||
| lv_act_select | TYPE SCPRACTINF, " | |||
| lv_wrong_parameters | TYPE SCPRACTINF, " | |||
| lv_actid_table | TYPE SCPRACTID, " | |||
| lv_bcset_table | TYPE SCPR_BCSETS, " | |||
| lv_category | TYPE SCPR_CTGRY. " SPACE |
|   CALL FUNCTION 'SCPR_PR_MN_PROTOCOL' " |
| EXPORTING | ||
| MAX_PROTOCOLS | = lv_max_protocols | |
| ACT_SELECT | = lv_act_select | |
| ACTID_TABLE | = lv_actid_table | |
| BCSET_TABLE | = lv_bcset_table | |
| CATEGORY | = lv_category | |
| EXCEPTIONS | ||
| NO_PROTOCOL = 1 | ||
| WRONG_PARAMETERS = 2 | ||
| . " SCPR_PR_MN_PROTOCOL | ||
ABAP code using 7.40 inline data declarations to call FM SCPR_PR_MN_PROTOCOL
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_category) | = ' '. | |||
Search for further information about these or an SAP related objects