SAP FIN_CSPC_INBOUND_REQUEST Function Module for Cross-System Process Control: Inbound Requests
FIN_CSPC_INBOUND_REQUEST is a standard fin cspc inbound request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Cross-System Process Control: Inbound Requests 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 fin cspc inbound request FM, simply by entering the name FIN_CSPC_INBOUND_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: FIN_CSPC_INBOUND_REQUEST
Program Name: SAPLFIN_CSPC_INBOUND_REQUEST
Main Program: SAPLFIN_CSPC_INBOUND_REQUEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FIN_CSPC_INBOUND_REQUEST 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 'FIN_CSPC_INBOUND_REQUEST'"Cross-System Process Control: Inbound Requests.
EXPORTING
IV_PROCESS_TYPE = "
* IV_REQUESTING_LOGSYSTEM = "Logical System
IT_REQUEST = "
* IV_TRANSFER_ALL_OR_NOTHING = "
IV_SIMULATE = "
* IV_LANGUAGE = "
* IV_LOCK_STRATEGY = "
IMPORTING
ET_REQUEST_RESULT = "Cross-System Process Control: Token Request Result
ES_ERROR = "Return Parameter
IMPORTING Parameters details for FIN_CSPC_INBOUND_REQUEST
IV_PROCESS_TYPE -
Data type: FIN_CSPC_PROC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
IV_REQUESTING_LOGSYSTEM - Logical System
Data type: LOGSYSTEMOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_REQUEST -
Data type: FIN_CSPC_T_REQUESTOptional: No
Call by Reference: No ( called with pass by value option)
IV_TRANSFER_ALL_OR_NOTHING -
Data type: XSDBOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SIMULATE -
Data type: XSDBOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
IV_LANGUAGE -
Data type: SYST_LANGUOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOCK_STRATEGY -
Data type: FIN_CSPC_LOCK_STRATEGYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FIN_CSPC_INBOUND_REQUEST
ET_REQUEST_RESULT - Cross-System Process Control: Token Request Result
Data type: FIN_CSPC_T_REQUEST_RESULTOptional: No
Call by Reference: No ( called with pass by value option)
ES_ERROR - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FIN_CSPC_INBOUND_REQUEST 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_iv_process_type | TYPE FIN_CSPC_PROC_TYPE, " | |||
| lv_et_request_result | TYPE FIN_CSPC_T_REQUEST_RESULT, " | |||
| lv_es_error | TYPE BAPIRET2, " | |||
| lv_iv_requesting_logsystem | TYPE LOGSYSTEM, " | |||
| lv_it_request | TYPE FIN_CSPC_T_REQUEST, " | |||
| lv_iv_transfer_all_or_nothing | TYPE XSDBOOLEAN, " | |||
| lv_iv_simulate | TYPE XSDBOOLEAN, " | |||
| lv_iv_language | TYPE SYST_LANGU, " | |||
| lv_iv_lock_strategy | TYPE FIN_CSPC_LOCK_STRATEGY. " |
|   CALL FUNCTION 'FIN_CSPC_INBOUND_REQUEST' "Cross-System Process Control: Inbound Requests |
| EXPORTING | ||
| IV_PROCESS_TYPE | = lv_iv_process_type | |
| IV_REQUESTING_LOGSYSTEM | = lv_iv_requesting_logsystem | |
| IT_REQUEST | = lv_it_request | |
| IV_TRANSFER_ALL_OR_NOTHING | = lv_iv_transfer_all_or_nothing | |
| IV_SIMULATE | = lv_iv_simulate | |
| IV_LANGUAGE | = lv_iv_language | |
| IV_LOCK_STRATEGY | = lv_iv_lock_strategy | |
| IMPORTING | ||
| ET_REQUEST_RESULT | = lv_et_request_result | |
| ES_ERROR | = lv_es_error | |
| . " FIN_CSPC_INBOUND_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM FIN_CSPC_INBOUND_REQUEST
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