SAP BAPI_REQSRVAPS_RECRESPONSE Function Module for Receive CLP Request Response
BAPI_REQSRVAPS_RECRESPONSE is a standard bapi reqsrvaps recresponse SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Receive CLP Request Response 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 bapi reqsrvaps recresponse FM, simply by entering the name BAPI_REQSRVAPS_RECRESPONSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: 10510
Program Name: SAPL10510
Main Program: SAPL10510
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BAPI_REQSRVAPS_RECRESPONSE 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 'BAPI_REQSRVAPS_RECRESPONSE'"Receive CLP Request Response.
EXPORTING
RESPONSE_HEADER = "Header Information Response for CLP Request for Quotation Process
* RESPONSE_SENDERADDRESS = "Address Information for CLP Request Process
* RESPONSE_RECEIVERADDRESS = "Address Information for CLP Request Process
* SEND_INFO = "Send Information
* COMMIT_CONTROL = 'E' "COMMIT Control
TABLES
RESPONSE_ITEMS = "Response for CLP Request for Quotation Process
* RETURN = "Return Parameter
* EXTENSION_IN = "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
* COMMUNICATION_DOCUMENTS = "Communication information
IMPORTING Parameters details for BAPI_REQSRVAPS_RECRESPONSE
RESPONSE_HEADER - Header Information Response for CLP Request for Quotation Process
Data type: ANYOptional: No
Call by Reference: No ( called with pass by value option)
RESPONSE_SENDERADDRESS - Address Information for CLP Request Process
Data type: ANYOptional: Yes
Call by Reference: No ( called with pass by value option)
RESPONSE_RECEIVERADDRESS - Address Information for CLP Request Process
Data type: ANYOptional: Yes
Call by Reference: No ( called with pass by value option)
SEND_INFO - Send Information
Data type: ANYOptional: Yes
Call by Reference: No ( called with pass by value option)
COMMIT_CONTROL - COMMIT Control
Data type: BAPI10510GENFIELDS-COMMIT_CONTROLDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_REQSRVAPS_RECRESPONSE
RESPONSE_ITEMS - Response for CLP Request for Quotation Process
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
EXTENSION_IN - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
COMMUNICATION_DOCUMENTS - Communication information
Data type: BAPIAPOCOMDOCUMENTSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_REQSRVAPS_RECRESPONSE 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: | ||||
| lt_response_items | TYPE STANDARD TABLE OF STANDARD TABLE, " | |||
| lv_response_header | TYPE ANY, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_response_senderaddress | TYPE ANY, " | |||
| lt_extension_in | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_response_receiveraddress | TYPE ANY, " | |||
| lv_send_info | TYPE ANY, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF BAPIAPOCOMDOCUMENTS, " | |||
| lv_commit_control | TYPE BAPI10510GENFIELDS-COMMIT_CONTROL. " 'E' |
|   CALL FUNCTION 'BAPI_REQSRVAPS_RECRESPONSE' "Receive CLP Request Response |
| EXPORTING | ||
| RESPONSE_HEADER | = lv_response_header | |
| RESPONSE_SENDERADDRESS | = lv_response_senderaddress | |
| RESPONSE_RECEIVERADDRESS | = lv_response_receiveraddress | |
| SEND_INFO | = lv_send_info | |
| COMMIT_CONTROL | = lv_commit_control | |
| TABLES | ||
| RESPONSE_ITEMS | = lt_response_items | |
| RETURN | = lt_return | |
| EXTENSION_IN | = lt_extension_in | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| . " BAPI_REQSRVAPS_RECRESPONSE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_REQSRVAPS_RECRESPONSE
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.| "SELECT single COMMIT_CONTROL FROM BAPI10510GENFIELDS INTO @DATA(ld_commit_control). | ||||
| DATA(ld_commit_control) | = 'E'. | |||
Search for further information about these or an SAP related objects