SAP RCP301_RECIPES_WRITE Function Module for NOTRANSL: RMS-RCP: Anlegen/Ändern/Löschen von Rezeptobjekten









RCP301_RECIPES_WRITE is a standard rcp301 recipes 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: Anlegen/Ändern/Löschen von Rezeptobjekten 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 rcp301 recipes write FM, simply by entering the name RCP301_RECIPES_WRITE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RCP301
Program Name: SAPLRCP301
Main Program: SAPLRCP301
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RCP301_RECIPES_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 'RCP301_RECIPES_WRITE'"NOTRANSL: RMS-RCP: Anlegen/Ändern/Löschen von Rezeptobjekten
  EXPORTING
*  I_DATA_SCENARIO = 'S' "Data Scenario for API Recipe
*  IT_STATUS =  "RMS-RCP: API - Table Type for Status
*  I_FLG_NO_AENNR_DATE_CHECK = ' ' "General Flag
*  IT_USTATUS =  "RMS-RCP: API - Table Type for User Status

 IMPORTING
   ET_ERROR =  "RMS-RCP: API - Table Type for Error Table
   ET_NO_AUTH =  "RMS-RCP: API - Table Type for Authorization

CHANGING
*  XT_RCP =  "RMS-RCP: API - Table Type for Recipe Data
*  XT_LTX =  "RMS-RCP: API - Table Type for Long Texts
*  XT_CLA =  "RMS-RCP: API - Table Type for Classification
*  XT_IDENT =  "RMS-RCP: API - Table Type for Identifiers
*  XT_ASCOPE =  "RMS-RCP: API - Table Type for Scope of Application
*  XT_REPLACE =  "RMS-RCP: API - Table Type for Recipe Replacement
*  XT_REL_FIT =  "RMS-RCP: API - Table Type for Formula Items Assignment
*  XT_REL_MR =  "RMS-RCP: API - Table Type for Master Recipe Generation
*  XT_REL_FRM =  "RMS-RCP: API - Table Type for Formula Assignment
*  XT_OP_SUC =  "RMS-RCP: API - Table Type f. Process Operation - Successor
*  XT_OP_PRE =  "RMS-RCP: API - Table Type f. Process Operation - Predecessor
*  XT_PRO =  "RMS-RCP: API - Table Type for Process
*  XT_PP =  "RMS-RCP: API - Table Type for Process Parameters
*  XT_PP_N =  "RMS-RCP: API - Table Type New Process Parameters
*  XT_PST =  "RMS-RCP: API - Table Type for Process Stage
*  XT_POP =  "RMS-RCP: API - Table Type for Process Operation
*  XT_PAC =  "RMS-RCP: API - Table Type for Process Action
*  XT_EQR =  "RMS-RCP: API - Table Type for Equipment Requirement
*  XT_DOC =  "RMS-RCP: API - Table Type for Document Links
*  XT_STX =  "RMS-RCP: API - Table Type for Short Texts
*  XT_RCTX =  "RMS-RCP: API - Table Type for Creation Reason Texts

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for RCP301_RECIPES_WRITE

I_DATA_SCENARIO - Data Scenario for API Recipe

Data type: RCPE_DATASCEN
Default: 'S'
Optional: No
Call by Reference: No ( called with pass by value option)

IT_STATUS - RMS-RCP: API - Table Type for Status

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

I_FLG_NO_AENNR_DATE_CHECK - General Flag

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

IT_USTATUS - RMS-RCP: API - Table Type for User Status

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

EXPORTING Parameters details for RCP301_RECIPES_WRITE

ET_ERROR - RMS-RCP: API - Table Type for Error Table

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

ET_NO_AUTH - RMS-RCP: API - Table Type for Authorization

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

CHANGING Parameters details for RCP301_RECIPES_WRITE

XT_RCP - RMS-RCP: API - Table Type for Recipe Data

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

XT_LTX - RMS-RCP: API - Table Type for Long Texts

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

XT_CLA - RMS-RCP: API - Table Type for Classification

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

XT_IDENT - RMS-RCP: API - Table Type for Identifiers

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

XT_ASCOPE - RMS-RCP: API - Table Type for Scope of Application

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

XT_REPLACE - RMS-RCP: API - Table Type for Recipe Replacement

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

XT_REL_FIT - RMS-RCP: API - Table Type for Formula Items Assignment

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

XT_REL_MR - RMS-RCP: API - Table Type for Master Recipe Generation

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

XT_REL_FRM - RMS-RCP: API - Table Type for Formula Assignment

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

XT_OP_SUC - RMS-RCP: API - Table Type f. Process Operation - Successor

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

XT_OP_PRE - RMS-RCP: API - Table Type f. Process Operation - Predecessor

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

XT_PRO - RMS-RCP: API - Table Type for Process

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

XT_PP - RMS-RCP: API - Table Type for Process Parameters

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

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

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

XT_PST - RMS-RCP: API - Table Type for Process Stage

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

XT_POP - RMS-RCP: API - Table Type for Process Operation

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

XT_PAC - RMS-RCP: API - Table Type for Process Action

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

XT_EQR - RMS-RCP: API - Table Type for Equipment Requirement

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

XT_DOC - RMS-RCP: API - Table Type for Document Links

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

XT_STX - RMS-RCP: API - Table Type for Short Texts

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

XT_RCTX - RMS-RCP: API - Table Type for Creation Reason Texts

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

EXCEPTIONS details

ERROR - General Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RCP301_RECIPES_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_rcp  TYPE RCPTY_API_RCP, "   
lv_et_error  TYPE RCPTY_API_ERROR, "   
lv_i_data_scenario  TYPE RCPE_DATASCEN, "   'S'
lv_xt_ltx  TYPE RCPTY_API_LTX, "   
lv_xt_cla  TYPE RCPTY_API_CLA, "   
lv_xt_ident  TYPE RCPTY_API_IDENT, "   
lv_xt_ascope  TYPE RCPTY_API_ASCOPE, "   
lv_xt_replace  TYPE RCPTY_API_REPLACE, "   
lv_xt_rel_fit  TYPE RCPTY_API_REL_FIT, "   
lv_xt_rel_mr  TYPE RCPTY_API_REL_MR, "   
lv_xt_rel_frm  TYPE RCPTY_API_REL_FRM, "   
lv_xt_op_suc  TYPE RCPTY_API_OP_SUC, "   
lv_xt_op_pre  TYPE RCPTY_API_OP_PRE, "   
lv_xt_pro  TYPE RCPTY_API_PRO, "   
lv_it_status  TYPE RCPTY_API_STATUS, "   
lv_et_no_auth  TYPE RCPTY_API_NO_AUTH, "   
lv_xt_pp  TYPE RCPTY_API_PP, "   
lv_xt_pp_n  TYPE RCPTY_API_PP_N, "   
lv_xt_pst  TYPE RCPTY_API_PST, "   
lv_i_flg_no_aennr_date_check  TYPE FLAG, "   SPACE
lv_xt_pop  TYPE RCPTY_API_POP, "   
lv_it_ustatus  TYPE RCPTY_API_USTATUS, "   
lv_xt_pac  TYPE RCPTY_API_PAC, "   
lv_xt_eqr  TYPE RCPTY_API_EQR, "   
lv_xt_doc  TYPE RCPTY_API_DOC, "   
lv_xt_stx  TYPE RCPTY_API_STX, "   
lv_xt_rctx  TYPE RCPTY_API_RCTX. "   

  CALL FUNCTION 'RCP301_RECIPES_WRITE'  "NOTRANSL: RMS-RCP: Anlegen/Ändern/Löschen von Rezeptobjekten
    EXPORTING
         I_DATA_SCENARIO = lv_i_data_scenario
         IT_STATUS = lv_it_status
         I_FLG_NO_AENNR_DATE_CHECK = lv_i_flg_no_aennr_date_check
         IT_USTATUS = lv_it_ustatus
    IMPORTING
         ET_ERROR = lv_et_error
         ET_NO_AUTH = lv_et_no_auth
    CHANGING
         XT_RCP = lv_xt_rcp
         XT_LTX = lv_xt_ltx
         XT_CLA = lv_xt_cla
         XT_IDENT = lv_xt_ident
         XT_ASCOPE = lv_xt_ascope
         XT_REPLACE = lv_xt_replace
         XT_REL_FIT = lv_xt_rel_fit
         XT_REL_MR = lv_xt_rel_mr
         XT_REL_FRM = lv_xt_rel_frm
         XT_OP_SUC = lv_xt_op_suc
         XT_OP_PRE = lv_xt_op_pre
         XT_PRO = lv_xt_pro
         XT_PP = lv_xt_pp
         XT_PP_N = lv_xt_pp_n
         XT_PST = lv_xt_pst
         XT_POP = lv_xt_pop
         XT_PAC = lv_xt_pac
         XT_EQR = lv_xt_eqr
         XT_DOC = lv_xt_doc
         XT_STX = lv_xt_stx
         XT_RCTX = lv_xt_rctx
    EXCEPTIONS
        ERROR = 1
. " RCP301_RECIPES_WRITE




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

 
 
 
DATA(ld_i_data_scenario) = 'S'.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_i_flg_no_aennr_date_check) = ' '.
 
 
 
 
 
 
 
 


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!