SAP FVD_VBUDAT_GET_BUDAT_RULES Function Module for Determine Additional Posting Information
FVD_VBUDAT_GET_BUDAT_RULES is a standard fvd vbudat get budat rules SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Additional Posting Information 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 vbudat get budat rules FM, simply by entering the name FVD_VBUDAT_GET_BUDAT_RULES into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_VBUDAT
Program Name: SAPLFVD_VBUDAT
Main Program: SAPLFVD_VBUDAT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_VBUDAT_GET_BUDAT_RULES 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_VBUDAT_GET_BUDAT_RULES'"Determine Additional Posting Information.
EXPORTING
I_APPLICATION = "Open Item Tool: Application Key
* I_COMPANY_CODE = "
* I_CONTRACT = "
* I_DDISPO = "Payment Date
* I_EOD_FLAG = "End of day flag for posting date
IMPORTING
E_DATE = "Date in CHAR format
E_SHOW_POPUP = "Display Posting Dialog Box (Yes / No)
E_NO_DEFAULT = "Checkbox
E_DISPYN = "Display Posting Date (Yes / No)
EXCEPTIONS
NO_ENTRY = 1
IMPORTING Parameters details for FVD_VBUDAT_GET_BUDAT_RULES
I_APPLICATION - Open Item Tool: Application Key
Data type: TB_OPAPPLOptional: No
Call by Reference: Yes
I_COMPANY_CODE -
Data type: VDARL-BUKRSOptional: Yes
Call by Reference: Yes
I_CONTRACT -
Data type: VDARL-RANLOptional: Yes
Call by Reference: Yes
I_DDISPO - Payment Date
Data type: DDISPOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EOD_FLAG - End of day flag for posting date
Data type: TB_EOD_FLG_CMLCHNOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_VBUDAT_GET_BUDAT_RULES
E_DATE - Date in CHAR format
Data type: SY-DATUMOptional: No
Call by Reference: Yes
E_SHOW_POPUP - Display Posting Dialog Box (Yes / No)
Data type: TB_POPUPYNOptional: No
Call by Reference: Yes
E_NO_DEFAULT - Checkbox
Data type: XFELDOptional: No
Call by Reference: Yes
E_DISPYN - Display Posting Date (Yes / No)
Data type: TB_DISPYN_CMLCHNOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRY - Keine Vorgabe gepflegt
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_VBUDAT_GET_BUDAT_RULES 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_e_date | TYPE SY-DATUM, " | |||
| lv_no_entry | TYPE SY, " | |||
| lv_i_application | TYPE TB_OPAPPL, " | |||
| lv_e_show_popup | TYPE TB_POPUPYN, " | |||
| lv_i_company_code | TYPE VDARL-BUKRS, " | |||
| lv_i_contract | TYPE VDARL-RANL, " | |||
| lv_e_no_default | TYPE XFELD, " | |||
| lv_e_dispyn | TYPE TB_DISPYN_CMLCHN, " | |||
| lv_i_ddispo | TYPE DDISPO, " | |||
| lv_i_eod_flag | TYPE TB_EOD_FLG_CMLCHN. " |
|   CALL FUNCTION 'FVD_VBUDAT_GET_BUDAT_RULES' "Determine Additional Posting Information |
| EXPORTING | ||
| I_APPLICATION | = lv_i_application | |
| I_COMPANY_CODE | = lv_i_company_code | |
| I_CONTRACT | = lv_i_contract | |
| I_DDISPO | = lv_i_ddispo | |
| I_EOD_FLAG | = lv_i_eod_flag | |
| IMPORTING | ||
| E_DATE | = lv_e_date | |
| E_SHOW_POPUP | = lv_e_show_popup | |
| E_NO_DEFAULT | = lv_e_no_default | |
| E_DISPYN | = lv_e_dispyn | |
| EXCEPTIONS | ||
| NO_ENTRY = 1 | ||
| . " FVD_VBUDAT_GET_BUDAT_RULES | ||
ABAP code using 7.40 inline data declarations to call FM FVD_VBUDAT_GET_BUDAT_RULES
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 DATUM FROM SY INTO @DATA(ld_e_date). | ||||
| "SELECT single BUKRS FROM VDARL INTO @DATA(ld_i_company_code). | ||||
| "SELECT single RANL FROM VDARL INTO @DATA(ld_i_contract). | ||||
Search for further information about these or an SAP related objects