SAP BNK_API_ARC_PREPROCESS Function Module for Status setting during preprocesing stage of archiving
BNK_API_ARC_PREPROCESS is a standard bnk api arc preprocess SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Status setting during preprocesing stage of archiving 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 bnk api arc preprocess FM, simply by entering the name BNK_API_ARC_PREPROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: BNK_API_PAYMT_UTIL
Program Name: SAPLBNK_API_PAYMT_UTIL
Main Program: SAPLBNK_API_PAYMT_UTIL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BNK_API_ARC_PREPROCESS 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 'BNK_API_ARC_PREPROCESS'"Status setting during preprocesing stage of archiving.
EXPORTING
I_BNK_TAB_BATCH_NO = "Table type of Batch Numbers
EXCEPTIONS
NO_SUCCESS = 1
IMPORTING Parameters details for BNK_API_ARC_PREPROCESS
I_BNK_TAB_BATCH_NO - Table type of Batch Numbers
Data type: BNK_TAB_BATCH_NOOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_SUCCESS - Status set not successful
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BNK_API_ARC_PREPROCESS 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_no_success | TYPE STRING, " | |||
| lv_i_bnk_tab_batch_no | TYPE BNK_TAB_BATCH_NO. " |
|   CALL FUNCTION 'BNK_API_ARC_PREPROCESS' "Status setting during preprocesing stage of archiving |
| EXPORTING | ||
| I_BNK_TAB_BATCH_NO | = lv_i_bnk_tab_batch_no | |
| EXCEPTIONS | ||
| NO_SUCCESS = 1 | ||
| . " BNK_API_ARC_PREPROCESS | ||
ABAP code using 7.40 inline data declarations to call FM BNK_API_ARC_PREPROCESS
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