SAP MAP2E_RCPS_API_RCTX_TX_TO_1194 Function Module for NOTRANSL: rcps_api_tx -> bapi1194_gr_tx









MAP2E_RCPS_API_RCTX_TX_TO_1194 is a standard map2e rcps api rctx tx to 1194 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: rcps_api_tx -> bapi1194_gr_tx 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 map2e rcps api rctx tx to 1194 FM, simply by entering the name MAP2E_RCPS_API_RCTX_TX_TO_1194 into the relevant SAP transaction such as SE37 or SE38.

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



Function MAP2E_RCPS_API_RCTX_TX_TO_1194 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 'MAP2E_RCPS_API_RCTX_TX_TO_1194'"NOTRANSL: rcps_api_tx -> bapi1194_gr_tx
EXPORTING
RCPS_API_TX = "
I_IDENTIFIER = "iPPE GUID in (External) CHAR32 Format
I_CHANGE_NO = "Change Number

CHANGING
BAPI1194_GR_TX = "BAPI - General Texts Structure
.



IMPORTING Parameters details for MAP2E_RCPS_API_RCTX_TX_TO_1194

RCPS_API_TX -

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

I_IDENTIFIER - iPPE GUID in (External) CHAR32 Format

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

I_CHANGE_NO - Change Number

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

CHANGING Parameters details for MAP2E_RCPS_API_RCTX_TX_TO_1194

BAPI1194_GR_TX - BAPI - General Texts Structure

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

Copy and paste ABAP code example for MAP2E_RCPS_API_RCTX_TX_TO_1194 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_rcps_api_tx  TYPE RCPS_API_TX, "   
lv_bapi1194_gr_tx  TYPE BAPI1194_GR_RCTX_TX, "   
lv_i_identifier  TYPE PVS_GUID_EXT, "   
lv_i_change_no  TYPE AENNR. "   

  CALL FUNCTION 'MAP2E_RCPS_API_RCTX_TX_TO_1194'  "NOTRANSL: rcps_api_tx -> bapi1194_gr_tx
    EXPORTING
         RCPS_API_TX = lv_rcps_api_tx
         I_IDENTIFIER = lv_i_identifier
         I_CHANGE_NO = lv_i_change_no
    CHANGING
         BAPI1194_GR_TX = lv_bapi1194_gr_tx
. " MAP2E_RCPS_API_RCTX_TX_TO_1194




ABAP code using 7.40 inline data declarations to call FM MAP2E_RCPS_API_RCTX_TX_TO_1194

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!