SAP MAP2E_RCPS_API_REPLBY_TO_1194 Function Module for NOTRANSL: rcps_api_replby -> bapi1194_gr_replby
MAP2E_RCPS_API_REPLBY_TO_1194 is a standard map2e rcps api replby 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_replby -> bapi1194_gr_replby 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 replby to 1194 FM, simply by entering the name MAP2E_RCPS_API_REPLBY_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_REPLBY_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_REPLBY_TO_1194'"NOTRANSL: rcps_api_replby -> bapi1194_gr_replby.
EXPORTING
I_API_REPLBY = "RMS-RCP: API - Recipe Replaced by Structure
I_REPLACE_ID = "Internal Identification for PVS Objects
I_LINEMODE = "
I_CHANGE_NO = "Change Number
CHANGING
X_BAPI_REPLBY = "
IMPORTING Parameters details for MAP2E_RCPS_API_REPLBY_TO_1194
I_API_REPLBY - RMS-RCP: API - Recipe Replaced by Structure
Data type: RCPS_API_REPLBYOptional: No
Call by Reference: Yes
I_REPLACE_ID - Internal Identification for PVS Objects
Data type: PVS_GUIDOptional: No
Call by Reference: Yes
I_LINEMODE -
Data type: COptional: No
Call by Reference: Yes
I_CHANGE_NO - Change Number
Data type: AENNROptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2E_RCPS_API_REPLBY_TO_1194
X_BAPI_REPLBY -
Data type: BAPI1194_GR_REPLBYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP2E_RCPS_API_REPLBY_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_i_api_replby | TYPE RCPS_API_REPLBY, " | |||
| lv_x_bapi_replby | TYPE BAPI1194_GR_REPLBY, " | |||
| lv_i_replace_id | TYPE PVS_GUID, " | |||
| lv_i_linemode | TYPE C, " | |||
| lv_i_change_no | TYPE AENNR. " |
|   CALL FUNCTION 'MAP2E_RCPS_API_REPLBY_TO_1194' "NOTRANSL: rcps_api_replby -> bapi1194_gr_replby |
| EXPORTING | ||
| I_API_REPLBY | = lv_i_api_replby | |
| I_REPLACE_ID | = lv_i_replace_id | |
| I_LINEMODE | = lv_i_linemode | |
| I_CHANGE_NO | = lv_i_change_no | |
| CHANGING | ||
| X_BAPI_REPLBY | = lv_x_bapi_replby | |
| . " MAP2E_RCPS_API_REPLBY_TO_1194 | ||
ABAP code using 7.40 inline data declarations to call FM MAP2E_RCPS_API_REPLBY_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