SAP RCP327_PROC_PAR_WRITE Function Module for NOTRANSL: Prozessparameter schreiben









RCP327_PROC_PAR_WRITE is a standard rcp327 proc par write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prozessparameter schreiben 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 rcp327 proc par write FM, simply by entering the name RCP327_PROC_PAR_WRITE into the relevant SAP transaction such as SE37 or SE38.

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



Function RCP327_PROC_PAR_WRITE 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 'RCP327_PROC_PAR_WRITE'"NOTRANSL: Prozessparameter schreiben
  EXPORTING
   I_WRITE_SCENARIO =  "Data Scenario for API Recipe
*  I_VALFROM =  "Valid-From Date
   I_GUID_OBJ =  "Internal Identification for PVS Objects
   I_GUID_ROOT =  "Internal Identification for PVS Objects
   I_AENNR =  "Change Number
*  I_SUBCAT =  "Object Type
*  IT_RCP_OBJ =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

 IMPORTING
   ET_EVT_RELOBJ_CHANGE =  "RMS-ATL: API - Table Type for Event Handling Dep. Objects

CHANGING
   XT_PP_N =  "RMS-RCP: API - Table Type New Process Parameters

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for RCP327_PROC_PAR_WRITE

I_WRITE_SCENARIO - Data Scenario for API Recipe

Data type: RCPE_DATASCEN
Optional: No
Call by Reference: Yes

I_VALFROM - Valid-From Date

Data type: RCPE_ADATUM
Optional: Yes
Call by Reference: Yes

I_GUID_OBJ - Internal Identification for PVS Objects

Data type: PVS_GUID
Optional: No
Call by Reference: Yes

I_GUID_ROOT - Internal Identification for PVS Objects

Data type: PVS_GUID
Optional: No
Call by Reference: Yes

I_AENNR - Change Number

Data type: AENNR
Optional: No
Call by Reference: Yes

I_SUBCAT - Object Type

Data type: RCPE_SUBCAT
Optional: Yes
Call by Reference: Yes

IT_RCP_OBJ - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: RCPTY_PP_POB
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for RCP327_PROC_PAR_WRITE

ET_EVT_RELOBJ_CHANGE - RMS-ATL: API - Table Type for Event Handling Dep. Objects

Data type: RMSATY_EVT_RELOBJ_CHANGE
Optional: No
Call by Reference: Yes

CHANGING Parameters details for RCP327_PROC_PAR_WRITE

XT_PP_N - RMS-RCP: API - Table Type New Process Parameters

Data type: RCPTY_API_PP_N
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR - Internal Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RCP327_PROC_PAR_WRITE 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_error  TYPE STRING, "   
lv_xt_pp_n  TYPE RCPTY_API_PP_N, "   
lv_i_write_scenario  TYPE RCPE_DATASCEN, "   
lv_et_evt_relobj_change  TYPE RMSATY_EVT_RELOBJ_CHANGE, "   
lv_i_valfrom  TYPE RCPE_ADATUM, "   
lv_i_guid_obj  TYPE PVS_GUID, "   
lv_i_guid_root  TYPE PVS_GUID, "   
lv_i_aennr  TYPE AENNR, "   
lv_i_subcat  TYPE RCPE_SUBCAT, "   
lv_it_rcp_obj  TYPE RCPTY_PP_POB. "   

  CALL FUNCTION 'RCP327_PROC_PAR_WRITE'  "NOTRANSL: Prozessparameter schreiben
    EXPORTING
         I_WRITE_SCENARIO = lv_i_write_scenario
         I_VALFROM = lv_i_valfrom
         I_GUID_OBJ = lv_i_guid_obj
         I_GUID_ROOT = lv_i_guid_root
         I_AENNR = lv_i_aennr
         I_SUBCAT = lv_i_subcat
         IT_RCP_OBJ = lv_it_rcp_obj
    IMPORTING
         ET_EVT_RELOBJ_CHANGE = lv_et_evt_relobj_change
    CHANGING
         XT_PP_N = lv_xt_pp_n
    EXCEPTIONS
        ERROR = 1
. " RCP327_PROC_PAR_WRITE




ABAP code using 7.40 inline data declarations to call FM RCP327_PROC_PAR_WRITE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!