SAP RCP990_CONVERT_GR_API_TO_BAPI Function Module for NOTRANSL: Konvertiert RCP-API-Daten -> RCP-BAPI-Daten









RCP990_CONVERT_GR_API_TO_BAPI is a standard rcp990 convert gr api to bapi 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: Konvertiert RCP-API-Daten -> RCP-BAPI-Daten 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 rcp990 convert gr api to bapi FM, simply by entering the name RCP990_CONVERT_GR_API_TO_BAPI into the relevant SAP transaction such as SE37 or SE38.

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



Function RCP990_CONVERT_GR_API_TO_BAPI 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 'RCP990_CONVERT_GR_API_TO_BAPI'"NOTRANSL: Konvertiert RCP-API-Daten -> RCP-BAPI-Daten
EXPORTING
IT_RCP = "RMS-RCP: API - Table Type for Recipe Data
IT_DOC = "RMS-RCP: API - Table Type for Document Links
IT_CLA = "RMS-RCP: API - Table Type for Classification
IT_IDENT = "RMS-RCP: API - Table Type for Identifiers
IT_ASCOPE = "RMS-RCP: API - Table Type for Scope of Application
IT_REPLACE = "RMS-RCP: API - Table Type for Recipe Replacement
IT_OP_SUC = "RMS-RCP: API - Table Type f. Process Operation - Successor
IT_PP = "RMS-RCP: API - Table Type for Process Parameters
IT_PVS_STRUCT = "Structure Information
I_FIRST_CREATE = "
IT_PRO = "RMS-RCP: API - Table Type for Process
IT_PST = "RMS-RCP: API - Table Type for Process Stage
IT_POP = "RMS-RCP: API - Table Type for Process Operation
IT_PAC = "RMS-RCP: API - Table Type for Process Action
IT_EQR = "RMS-RCP: API - Table Type for Equipment Requirement
IT_STX = "RMS-RCP: API - Table Type for Short Texts
IT_RCTX = "RMS-RCP: API - Table Type for Creation Reason Texts
IT_LTX = "RMS-RCP: API - Table Type for Long Texts

IMPORTING
ET_RCP = "BAPI - Table Type for Recipe Data
ET_RCTX_TX = "BAPI - Table Type for Text Attributes
ET_LTX = "BAPI - Table Type for Long Texts
ET_LTX_TLINE = "BAPI: Text Lines
ET_DOC = "BAPI - Table Type for Document Links
ET_CLA = "BAPI - Table Type for Classification
ET_CLA_VAL = "BAPI - Table Type : Characteristic Value Classification
ET_IDENT = "BAPI - Table Type for Identifiers
ET_IDENT_TXT = "BAPI - Table Type for Identifier Texts
ET_IDENT_TXT_TLINE = "BAPI: Text Lines
ET_ASCOPE = "BAPI - Table Type: Scope of Application
ET_PRO = "BAPI - Table Type for Process
ET_ASCOPE_EHS_ASCOPE = "BAPI - Table Type: Scope of Application Details
ET_REPLACE = "BAPI - Table Type for Replacement Recipes
ET_REPLACE_REPL = "BAPI - Table Type for Replaced Recipes
ET_REPLACE_REPLBY = "BAPI - Table Type for 'Recipe Replaced By'
ET_OP_SUC = "BAPI - Table Type for Process Operation - Successors
ET_PP = "BAPI - Table Type for Process Parameters
ET_PP_VH = "BAPI - Table Type for Process Param. Value Assignment Header
ET_PP_VA = "BAPI - Table Type for Process Parameter Value Assignments
ET_PP_PROP = "
ET_PP_DF = "BAPI - Table Type for Process Parameter Value Assgnmnt Texts
ET_PST = "BAPI - Table Type for Process Stage
ET_PP_FL = "BAPI: API - Table Type: Process Parameters Val.Ass.U.D.Texts
ET_PVS_STRUCT = "Structure Information
ET_POP = "BAPI - Table Type for Process Operation
ET_PAC = "BAPI - Table Type for Process Action
ET_EQR = "BAPI - Table Type for Equipment Requirement
ET_STX = "BAPI - Table Type for Short Texts
ET_STX_TX = "BAPI - Table Type for Text Attributes
ET_RCTX = "BAPI - Table Type for Creation Reason Texts
.



IMPORTING Parameters details for RCP990_CONVERT_GR_API_TO_BAPI

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

IT_PVS_STRUCT - Structure Information

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

I_FIRST_CREATE -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

EXPORTING Parameters details for RCP990_CONVERT_GR_API_TO_BAPI

ET_RCP - BAPI - Table Type for Recipe Data

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

ET_RCTX_TX - BAPI - Table Type for Text Attributes

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

ET_LTX - BAPI - Table Type for Long Texts

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

ET_LTX_TLINE - BAPI: Text Lines

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

ET_DOC - BAPI - Table Type for Document Links

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

ET_CLA - BAPI - Table Type for Classification

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

ET_CLA_VAL - BAPI - Table Type : Characteristic Value Classification

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

ET_IDENT - BAPI - Table Type for Identifiers

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

ET_IDENT_TXT - BAPI - Table Type for Identifier Texts

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

ET_IDENT_TXT_TLINE - BAPI: Text Lines

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

ET_ASCOPE - BAPI - Table Type: Scope of Application

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

ET_PRO - BAPI - Table Type for Process

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

ET_ASCOPE_EHS_ASCOPE - BAPI - Table Type: Scope of Application Details

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

ET_REPLACE - BAPI - Table Type for Replacement Recipes

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

ET_REPLACE_REPL - BAPI - Table Type for Replaced Recipes

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

ET_REPLACE_REPLBY - BAPI - Table Type for 'Recipe Replaced By'

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

ET_OP_SUC - BAPI - Table Type for Process Operation - Successors

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

ET_PP - BAPI - Table Type for Process Parameters

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

ET_PP_VH - BAPI - Table Type for Process Param. Value Assignment Header

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

ET_PP_VA - BAPI - Table Type for Process Parameter Value Assignments

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

ET_PP_PROP -

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

ET_PP_DF - BAPI - Table Type for Process Parameter Value Assgnmnt Texts

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

ET_PST - BAPI - Table Type for Process Stage

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

ET_PP_FL - BAPI: API - Table Type: Process Parameters Val.Ass.U.D.Texts

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

ET_PVS_STRUCT - Structure Information

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

ET_POP - BAPI - Table Type for Process Operation

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

ET_PAC - BAPI - Table Type for Process Action

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

ET_EQR - BAPI - Table Type for Equipment Requirement

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

ET_STX - BAPI - Table Type for Short Texts

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

ET_STX_TX - BAPI - Table Type for Text Attributes

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

ET_RCTX - BAPI - Table Type for Creation Reason Texts

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

Copy and paste ABAP code example for RCP990_CONVERT_GR_API_TO_BAPI 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_et_rcp  TYPE RCPTY_BAPI_RCP, "   
lv_it_rcp  TYPE RCPTY_API_RCP, "   
lv_it_doc  TYPE RCPTY_API_DOC, "   
lv_et_rctx_tx  TYPE RCPTY_BAPI_RCTX_TX, "   
lv_et_ltx  TYPE RCPTY_BAPI_LTX, "   
lv_it_cla  TYPE RCPTY_API_CLA, "   
lv_it_ident  TYPE RCPTY_API_IDENT, "   
lv_et_ltx_tline  TYPE RCPTY_BAPI_LTX_TLINE, "   
lv_et_doc  TYPE RCPTY_BAPI_DOC, "   
lv_it_ascope  TYPE RCPTY_API_ASCOPE, "   
lv_et_cla  TYPE RCPTY_BAPI_CLA, "   
lv_it_replace  TYPE RCPTY_API_REPLACE, "   
lv_it_op_suc  TYPE RCPTY_API_OP_SUC, "   
lv_et_cla_val  TYPE RCPTY_BAPI_VAL, "   
lv_it_pp  TYPE RCPTY_API_PP, "   
lv_et_ident  TYPE RCPTY_BAPI_IDENT, "   
lv_et_ident_txt  TYPE RCPTY_BAPI_IDENT_TXT, "   
lv_it_pvs_struct  TYPE RCPTY_PVS_STRUCT, "   
lv_i_first_create  TYPE C, "   
lv_et_ident_txt_tline  TYPE RCPTY_BAPI_IDENT_TLINE, "   
lv_et_ascope  TYPE RCPTY_BAPI_ASCOPE, "   
lv_et_pro  TYPE RCPTY_BAPI_PRO, "   
lv_it_pro  TYPE RCPTY_API_PRO, "   
lv_et_ascope_ehs_ascope  TYPE RCPTY_BAPI_APPL_SCOPE, "   
lv_et_replace  TYPE RCPTY_BAPI_REPLACE, "   
lv_et_replace_repl  TYPE RCPTY_BAPI_REPL, "   
lv_et_replace_replby  TYPE RCPTY_BAPI_REPLBY, "   
lv_et_op_suc  TYPE RCPTY_BAPI_OP_SUC, "   
lv_et_pp  TYPE RCPTY_BAPI_PP, "   
lv_et_pp_vh  TYPE RCPTY_BAPI_PP_VH, "   
lv_et_pp_va  TYPE RCPTY_BAPI_PP_VA, "   
lv_et_pp_prop  TYPE RCPTY_BAPI_PP_PROP, "   
lv_et_pp_df  TYPE RCPTY_BAPI_PP_DF, "   
lv_et_pst  TYPE RCPTY_BAPI_PST, "   
lv_it_pst  TYPE RCPTY_API_PST, "   
lv_et_pp_fl  TYPE RCPTY_BAPI_PP_FL, "   
lv_et_pvs_struct  TYPE RCPTY_BAPI_PVS_STRUCT, "   
lv_et_pop  TYPE RCPTY_BAPI_POP, "   
lv_it_pop  TYPE RCPTY_API_POP, "   
lv_et_pac  TYPE RCPTY_BAPI_PAC, "   
lv_it_pac  TYPE RCPTY_API_PAC, "   
lv_et_eqr  TYPE RCPTY_BAPI_EQR, "   
lv_it_eqr  TYPE RCPTY_API_EQR, "   
lv_et_stx  TYPE RCPTY_BAPI_STX, "   
lv_it_stx  TYPE RCPTY_API_STX, "   
lv_it_rctx  TYPE RCPTY_API_RCTX, "   
lv_et_stx_tx  TYPE RCPTY_BAPI_TX, "   
lv_it_ltx  TYPE RCPTY_API_LTX, "   
lv_et_rctx  TYPE RCPTY_BAPI_RCTX. "   

  CALL FUNCTION 'RCP990_CONVERT_GR_API_TO_BAPI'  "NOTRANSL: Konvertiert RCP-API-Daten -> RCP-BAPI-Daten
    EXPORTING
         IT_RCP = lv_it_rcp
         IT_DOC = lv_it_doc
         IT_CLA = lv_it_cla
         IT_IDENT = lv_it_ident
         IT_ASCOPE = lv_it_ascope
         IT_REPLACE = lv_it_replace
         IT_OP_SUC = lv_it_op_suc
         IT_PP = lv_it_pp
         IT_PVS_STRUCT = lv_it_pvs_struct
         I_FIRST_CREATE = lv_i_first_create
         IT_PRO = lv_it_pro
         IT_PST = lv_it_pst
         IT_POP = lv_it_pop
         IT_PAC = lv_it_pac
         IT_EQR = lv_it_eqr
         IT_STX = lv_it_stx
         IT_RCTX = lv_it_rctx
         IT_LTX = lv_it_ltx
    IMPORTING
         ET_RCP = lv_et_rcp
         ET_RCTX_TX = lv_et_rctx_tx
         ET_LTX = lv_et_ltx
         ET_LTX_TLINE = lv_et_ltx_tline
         ET_DOC = lv_et_doc
         ET_CLA = lv_et_cla
         ET_CLA_VAL = lv_et_cla_val
         ET_IDENT = lv_et_ident
         ET_IDENT_TXT = lv_et_ident_txt
         ET_IDENT_TXT_TLINE = lv_et_ident_txt_tline
         ET_ASCOPE = lv_et_ascope
         ET_PRO = lv_et_pro
         ET_ASCOPE_EHS_ASCOPE = lv_et_ascope_ehs_ascope
         ET_REPLACE = lv_et_replace
         ET_REPLACE_REPL = lv_et_replace_repl
         ET_REPLACE_REPLBY = lv_et_replace_replby
         ET_OP_SUC = lv_et_op_suc
         ET_PP = lv_et_pp
         ET_PP_VH = lv_et_pp_vh
         ET_PP_VA = lv_et_pp_va
         ET_PP_PROP = lv_et_pp_prop
         ET_PP_DF = lv_et_pp_df
         ET_PST = lv_et_pst
         ET_PP_FL = lv_et_pp_fl
         ET_PVS_STRUCT = lv_et_pvs_struct
         ET_POP = lv_et_pop
         ET_PAC = lv_et_pac
         ET_EQR = lv_et_eqr
         ET_STX = lv_et_stx
         ET_STX_TX = lv_et_stx_tx
         ET_RCTX = lv_et_rctx
. " RCP990_CONVERT_GR_API_TO_BAPI




ABAP code using 7.40 inline data declarations to call FM RCP990_CONVERT_GR_API_TO_BAPI

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!