SAP SCPR_IF_RELEASE_MODIFY Function Module for

Search SAP Function Modules

SCPR_IF_RELEASE_MODIFY is a standard scpr if release modify 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 if release modify FM, simply by entering the name SCPR_IF_RELEASE_MODIFY into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCPRPR
Program Name: SAPLSCPRPR
Main Program: SAPLSCPRPR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCPR_IF_RELEASE_MODIFY 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_IF_RELEASE_MODIFY'"
  EXPORTING
   PROFID =  "
   PROFTYPE =  "
*  SHOW_ONLY = ' ' "

 IMPORTING
   FCODE =  "

CHANGING
   TEXT =  "Short Text for Profile
   ORGID =  "
   ACT_INFO =  "
   COMPONENT =  "SW Component
   MINRELEASE =  "
   MAXRELEASE =  "
*  CATEGORY = ' ' "
   CLI_DEP =  "
   CLI_CAS =  "
   REFTYPE =  "
   REFNAME =  "

.

IMPORTING Parameters details for SCPR_IF_RELEASE_MODIFY

PROFID -

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

PROFTYPE -

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

SHOW_ONLY -

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

EXPORTING Parameters details for SCPR_IF_RELEASE_MODIFY

FCODE -

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

CHANGING Parameters details for SCPR_IF_RELEASE_MODIFY

TEXT - Short Text for Profile

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

ORGID -

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

ACT_INFO -

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

COMPONENT - SW Component

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

MINRELEASE -

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

MAXRELEASE -

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

CATEGORY -

Data type: SCPRATTR-CATEGORY
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLI_DEP -

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

CLI_CAS -

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

REFTYPE -

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

REFNAME -

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

Copy and paste ABAP code example for SCPR_IF_RELEASE_MODIFY 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.

ABAP code using 7.40 inline data declarations to call FM SCPR_IF_RELEASE_MODIFY

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.

Search for further information about these or an SAP related objects