SAP RCP308_VERSION_DATA_WRITE Function Module for NOTRANSL: RMS-RCP: Schreiben der Versionierungsdaten









RCP308_VERSION_DATA_WRITE is a standard rcp308 version data 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: RMS-RCP: Schreiben der Versionierungsdaten 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 rcp308 version data write FM, simply by entering the name RCP308_VERSION_DATA_WRITE into the relevant SAP transaction such as SE37 or SE38.

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



Function RCP308_VERSION_DATA_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 'RCP308_VERSION_DATA_WRITE'"NOTRANSL: RMS-RCP: Schreiben der Versionierungsdaten
  EXPORTING
   I_DATA_SCENARIO =  "Data Scenario for API Recipe
   I_FLG_INNR =  "Name Was Generated From Internal Number Range
*  IS_PVRCPD =  "Current Recipe
   I_LINEMODE =  "Processing Status/Mode of a Record/Step Loop Line
   I_PVGUID =  "Internal Number of the PVS Variant
   I_SUBCAT =  "Specification Type
*  I_COPY_FROM =  "Internal Identification for PVS Objects
*  I_VALFROM =  "Valid-To Date
*  I_VALTO =  "Valid-To Date
   I_NAM =  "Version Name
   I_VRS_TYPE =  "Version Type

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for RCP308_VERSION_DATA_WRITE

I_DATA_SCENARIO - Data Scenario for API Recipe

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

I_FLG_INNR - Name Was Generated From Internal Number Range

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

IS_PVRCPD - Current Recipe

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

I_LINEMODE - Processing Status/Mode of a Record/Step Loop Line

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

I_PVGUID - Internal Number of the PVS Variant

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

I_SUBCAT - Specification Type

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

I_COPY_FROM - Internal Identification for PVS Objects

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

I_VALFROM - Valid-To Date

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

I_VALTO - Valid-To Date

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

I_NAM - Version Name

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

I_VRS_TYPE - Version Type

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

EXCEPTIONS details

ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RCP308_VERSION_DATA_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_i_data_scenario  TYPE RCPE_DATASCEN, "   
lv_i_flg_innr  TYPE RMSAE_FLG_INNR, "   
lv_is_pvrcpd  TYPE PPET7_TY_S_PVRCPD_LI_EHS, "   
lv_i_linemode  TYPE RCPE_LINEMODE, "   
lv_i_pvguid  TYPE PVS_PVGUID, "   
lv_i_subcat  TYPE ESESUBCAT, "   
lv_i_copy_from  TYPE PVS_GUID, "   
lv_i_valfrom  TYPE RCPE_BDATUM, "   
lv_i_valto  TYPE RCPE_BDATUM, "   
lv_i_nam  TYPE RMSAE_OBJNAM, "   
lv_i_vrs_type  TYPE RMSAE_VRSTYPE. "   

  CALL FUNCTION 'RCP308_VERSION_DATA_WRITE'  "NOTRANSL: RMS-RCP: Schreiben der Versionierungsdaten
    EXPORTING
         I_DATA_SCENARIO = lv_i_data_scenario
         I_FLG_INNR = lv_i_flg_innr
         IS_PVRCPD = lv_is_pvrcpd
         I_LINEMODE = lv_i_linemode
         I_PVGUID = lv_i_pvguid
         I_SUBCAT = lv_i_subcat
         I_COPY_FROM = lv_i_copy_from
         I_VALFROM = lv_i_valfrom
         I_VALTO = lv_i_valto
         I_NAM = lv_i_nam
         I_VRS_TYPE = lv_i_vrs_type
    EXCEPTIONS
        ERROR = 1
. " RCP308_VERSION_DATA_WRITE




ABAP code using 7.40 inline data declarations to call FM RCP308_VERSION_DATA_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!