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

Function SCPR_TEMPL_MN_NEW_RECORDS 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_TEMPL_MN_NEW_RECORDS'".
EXPORTING
PROFID = "
ORGID = "
CHANGING
PROFTEXT = "
* CATEGORY = ' ' "
* CLI_DEP = ' ' "
* CLI_CAS = ' ' "
* REFTYPE = ' ' "
* REFNAME = ' ' "
COMPONENT = "SW Component
MINRELEASE = "Valid from release
MAXRELEASE = "Valid to Release
TABLES
VALUES = "Profile values
RECATTR = "
FIELDDESCRS = "Field Descriptions
* ORIG_RECNUM_ASSIGNS = "
IMPORTING Parameters details for SCPR_TEMPL_MN_NEW_RECORDS
PROFID -
Data type: SCPRATTR-IDOptional: No
Call by Reference: No ( called with pass by value option)
ORGID -
Data type: SCPRATTR-ORGIDOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SCPR_TEMPL_MN_NEW_RECORDS
PROFTEXT -
Data type: SCPRTEXT-TEXTOptional: No
Call by Reference: No ( called with pass by value option)
CATEGORY -
Data type: SCPRATTR-CATEGORYDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLI_DEP -
Data type: SCPRATTR-CLI_DEPDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLI_CAS -
Data type: SCPRATTR-CLI_CASDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
REFTYPE -
Data type: SCPRATTR-REFTYPEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
REFNAME -
Data type: SCPRATTR-REFNAMEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
COMPONENT - SW Component
Data type: SCPRATTR-COMPONENTOptional: No
Call by Reference: No ( called with pass by value option)
MINRELEASE - Valid from release
Data type: SCPRATTR-MINRELEASEOptional: No
Call by Reference: No ( called with pass by value option)
MAXRELEASE - Valid to Release
Data type: SCPRATTR-MAXRELEASEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SCPR_TEMPL_MN_NEW_RECORDS
VALUES - Profile values
Data type: SCPRVALSOptional: No
Call by Reference: No ( called with pass by value option)
RECATTR -
Data type: SCPR_RECATTRSOptional: No
Call by Reference: No ( called with pass by value option)
FIELDDESCRS - Field Descriptions
Data type: SCPR_RECORDSOptional: No
Call by Reference: No ( called with pass by value option)
ORIG_RECNUM_ASSIGNS -
Data type: SCPR_ORIG_RECNUM_ASSIGNSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SCPR_TEMPL_MN_NEW_RECORDS 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_profid | TYPE SCPRATTR-ID, " | |||
| lt_values | TYPE STANDARD TABLE OF SCPRVALS, " | |||
| lv_proftext | TYPE SCPRTEXT-TEXT, " | |||
| lv_orgid | TYPE SCPRATTR-ORGID, " | |||
| lt_recattr | TYPE STANDARD TABLE OF SCPR_RECATTRS, " | |||
| lv_category | TYPE SCPRATTR-CATEGORY, " ' ' | |||
| lv_cli_dep | TYPE SCPRATTR-CLI_DEP, " ' ' | |||
| lt_fielddescrs | TYPE STANDARD TABLE OF SCPR_RECORDS, " | |||
| lv_cli_cas | TYPE SCPRATTR-CLI_CAS, " ' ' | |||
| lt_orig_recnum_assigns | TYPE STANDARD TABLE OF SCPR_ORIG_RECNUM_ASSIGNS, " | |||
| lv_reftype | TYPE SCPRATTR-REFTYPE, " ' ' | |||
| lv_refname | TYPE SCPRATTR-REFNAME, " ' ' | |||
| lv_component | TYPE SCPRATTR-COMPONENT, " | |||
| lv_minrelease | TYPE SCPRATTR-MINRELEASE, " | |||
| lv_maxrelease | TYPE SCPRATTR-MAXRELEASE. " |
|   CALL FUNCTION 'SCPR_TEMPL_MN_NEW_RECORDS' " |
| EXPORTING | ||
| PROFID | = lv_profid | |
| ORGID | = lv_orgid | |
| CHANGING | ||
| PROFTEXT | = lv_proftext | |
| CATEGORY | = lv_category | |
| CLI_DEP | = lv_cli_dep | |
| CLI_CAS | = lv_cli_cas | |
| REFTYPE | = lv_reftype | |
| REFNAME | = lv_refname | |
| COMPONENT | = lv_component | |
| MINRELEASE | = lv_minrelease | |
| MAXRELEASE | = lv_maxrelease | |
| TABLES | ||
| VALUES | = lt_values | |
| RECATTR | = lt_recattr | |
| FIELDDESCRS | = lt_fielddescrs | |
| ORIG_RECNUM_ASSIGNS | = lt_orig_recnum_assigns | |
| . " SCPR_TEMPL_MN_NEW_RECORDS | ||
ABAP code using 7.40 inline data declarations to call FM SCPR_TEMPL_MN_NEW_RECORDS
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 ID FROM SCPRATTR INTO @DATA(ld_profid). | ||||
| "SELECT single TEXT FROM SCPRTEXT INTO @DATA(ld_proftext). | ||||
| "SELECT single ORGID FROM SCPRATTR INTO @DATA(ld_orgid). | ||||
| "SELECT single CATEGORY FROM SCPRATTR INTO @DATA(ld_category). | ||||
| DATA(ld_category) | = ' '. | |||
| "SELECT single CLI_DEP FROM SCPRATTR INTO @DATA(ld_cli_dep). | ||||
| DATA(ld_cli_dep) | = ' '. | |||
| "SELECT single CLI_CAS FROM SCPRATTR INTO @DATA(ld_cli_cas). | ||||
| DATA(ld_cli_cas) | = ' '. | |||
| "SELECT single REFTYPE FROM SCPRATTR INTO @DATA(ld_reftype). | ||||
| DATA(ld_reftype) | = ' '. | |||
| "SELECT single REFNAME FROM SCPRATTR INTO @DATA(ld_refname). | ||||
| DATA(ld_refname) | = ' '. | |||
| "SELECT single COMPONENT FROM SCPRATTR INTO @DATA(ld_component). | ||||
| "SELECT single MINRELEASE FROM SCPRATTR INTO @DATA(ld_minrelease). | ||||
| "SELECT single MAXRELEASE FROM SCPRATTR INTO @DATA(ld_maxrelease). | ||||
Search for further information about these or an SAP related objects