SAP FVD_ARC_COND_BAS_REC_CHECK Function Module for Checks Whether There Is a Condition-Based Flow That Has Not Been Reversed
FVD_ARC_COND_BAS_REC_CHECK is a standard fvd arc cond bas rec check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks Whether There Is a Condition-Based Flow That Has Not Been Reversed 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 fvd arc cond bas rec check FM, simply by entering the name FVD_ARC_COND_BAS_REC_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_DOCUMENTS_ARCHIVE
Program Name: SAPLFVD_DOCUMENTS_ARCHIVE
Main Program: SAPLFVD_DOCUMENTS_ARCHIVE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_ARC_COND_BAS_REC_CHECK 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 'FVD_ARC_COND_BAS_REC_CHECK'"Checks Whether There Is a Condition-Based Flow That Has Not Been Reversed.
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Loan Contract Number
IMPORTING
E_ORG_COND_BASED_DOC_EXISTS = "Gebuchte konditionsbasierte Bewegung liegt vor (1=JA oder 0=NEIN)
E_ARC_COND_BASED_DOC_EXISTS = "Reorganisierte konditionsbasierte Bewegung liegt vor (1=JA oder 0=NEIN)
E_DBUDAT = "Buchungsdatum der konditionsbasierten Bewegung
EXCEPTIONS
KEY_NOT_FILLED = 1
IMPORTING Parameters details for FVD_ARC_COND_BAS_REC_CHECK
I_BUKRS - Company Code
Data type: VDARL-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_RANL - Loan Contract Number
Data type: VDARL-RANLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_ARC_COND_BAS_REC_CHECK
E_ORG_COND_BASED_DOC_EXISTS - Gebuchte konditionsbasierte Bewegung liegt vor (1=JA oder 0=NEIN)
Data type: TB_YES_OR_NOOptional: No
Call by Reference: No ( called with pass by value option)
E_ARC_COND_BASED_DOC_EXISTS - Reorganisierte konditionsbasierte Bewegung liegt vor (1=JA oder 0=NEIN)
Data type: TB_YES_OR_NOOptional: No
Call by Reference: No ( called with pass by value option)
E_DBUDAT - Buchungsdatum der konditionsbasierten Bewegung
Data type: VDBEKI-DBUDATOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
KEY_NOT_FILLED - Schlüsselfelder unzureichend gefüllt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVD_ARC_COND_BAS_REC_CHECK 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_bukrs | TYPE VDARL-BUKRS, " | |||
| lv_key_not_filled | TYPE VDARL, " | |||
| lv_e_org_cond_based_doc_exists | TYPE TB_YES_OR_NO, " | |||
| lv_i_ranl | TYPE VDARL-RANL, " | |||
| lv_e_arc_cond_based_doc_exists | TYPE TB_YES_OR_NO, " | |||
| lv_e_dbudat | TYPE VDBEKI-DBUDAT. " |
|   CALL FUNCTION 'FVD_ARC_COND_BAS_REC_CHECK' "Checks Whether There Is a Condition-Based Flow That Has Not Been Reversed |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| IMPORTING | ||
| E_ORG_COND_BASED_DOC_EXISTS | = lv_e_org_cond_based_doc_exists | |
| E_ARC_COND_BASED_DOC_EXISTS | = lv_e_arc_cond_based_doc_exists | |
| E_DBUDAT | = lv_e_dbudat | |
| EXCEPTIONS | ||
| KEY_NOT_FILLED = 1 | ||
| . " FVD_ARC_COND_BAS_REC_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FVD_ARC_COND_BAS_REC_CHECK
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 BUKRS FROM VDARL INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single RANL FROM VDARL INTO @DATA(ld_i_ranl). | ||||
| "SELECT single DBUDAT FROM VDBEKI INTO @DATA(ld_e_dbudat). | ||||
Search for further information about these or an SAP related objects