SAP DET_VALUE_DATE_FROM_VORGANG Function Module for Determine value date from table T012C
DET_VALUE_DATE_FROM_VORGANG is a standard det value date from vorgang 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 value date from table T012C 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 det value date from vorgang FM, simply by entering the name DET_VALUE_DATE_FROM_VORGANG into the relevant SAP transaction such as SE37 or SE38.
Function Group: FDV1
Program Name: SAPLFDV1
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DET_VALUE_DATE_FROM_VORGANG 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 'DET_VALUE_DATE_FROM_VORGANG'"Determine value date from table T012C.
EXPORTING
* I_BLDAT = SY-DATUM "Document date
* I_BUDAT = SY-DATUM "Posting date
I_BUKRS = "Company code
* I_FAEDT = SY-DATUM "Due date
I_HBKID = "House bank key
I_HKTID = "Bank account key
I_VORGA = "Transaction
IMPORTING
E_VALUT = "Value date
EXCEPTIONS
CAL_ID_NOT_FOUND = 1 NOT_FOUND_IN_T012C = 2
IMPORTING Parameters details for DET_VALUE_DATE_FROM_VORGANG
I_BLDAT - Document date
Data type: BKPF-BLDATDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BUDAT - Posting date
Data type: BKPF-BUDATDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BUKRS - Company code
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_FAEDT - Due date
Data type: BSEG-ZFBDTDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_HBKID - House bank key
Data type: T012A-HBKIDOptional: No
Call by Reference: No ( called with pass by value option)
I_HKTID - Bank account key
Data type: T012K-HKTIDOptional: No
Call by Reference: No ( called with pass by value option)
I_VORGA - Transaction
Data type: T012A-VORGAOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DET_VALUE_DATE_FROM_VORGANG
E_VALUT - Value date
Data type: BSEG-VALUTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CAL_ID_NOT_FOUND - Invalid calendar ID in T012C
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND_IN_T012C - Transaction not maintained in T012C
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DET_VALUE_DATE_FROM_VORGANG 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_valut | TYPE BSEG-VALUT, " | |||
| lv_i_bldat | TYPE BKPF-BLDAT, " SY-DATUM | |||
| lv_cal_id_not_found | TYPE BKPF, " | |||
| lv_i_budat | TYPE BKPF-BUDAT, " SY-DATUM | |||
| lv_not_found_in_t012c | TYPE BKPF, " | |||
| lv_i_bukrs | TYPE T001-BUKRS, " | |||
| lv_i_faedt | TYPE BSEG-ZFBDT, " SY-DATUM | |||
| lv_i_hbkid | TYPE T012A-HBKID, " | |||
| lv_i_hktid | TYPE T012K-HKTID, " | |||
| lv_i_vorga | TYPE T012A-VORGA. " |
|   CALL FUNCTION 'DET_VALUE_DATE_FROM_VORGANG' "Determine value date from table T012C |
| EXPORTING | ||
| I_BLDAT | = lv_i_bldat | |
| I_BUDAT | = lv_i_budat | |
| I_BUKRS | = lv_i_bukrs | |
| I_FAEDT | = lv_i_faedt | |
| I_HBKID | = lv_i_hbkid | |
| I_HKTID | = lv_i_hktid | |
| I_VORGA | = lv_i_vorga | |
| IMPORTING | ||
| E_VALUT | = lv_e_valut | |
| EXCEPTIONS | ||
| CAL_ID_NOT_FOUND = 1 | ||
| NOT_FOUND_IN_T012C = 2 | ||
| . " DET_VALUE_DATE_FROM_VORGANG | ||
ABAP code using 7.40 inline data declarations to call FM DET_VALUE_DATE_FROM_VORGANG
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 VALUT FROM BSEG INTO @DATA(ld_e_valut). | ||||
| "SELECT single BLDAT FROM BKPF INTO @DATA(ld_i_bldat). | ||||
| DATA(ld_i_bldat) | = SY-DATUM. | |||
| "SELECT single BUDAT FROM BKPF INTO @DATA(ld_i_budat). | ||||
| DATA(ld_i_budat) | = SY-DATUM. | |||
| "SELECT single BUKRS FROM T001 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single ZFBDT FROM BSEG INTO @DATA(ld_i_faedt). | ||||
| DATA(ld_i_faedt) | = SY-DATUM. | |||
| "SELECT single HBKID FROM T012A INTO @DATA(ld_i_hbkid). | ||||
| "SELECT single HKTID FROM T012K INTO @DATA(ld_i_hktid). | ||||
| "SELECT single VORGA FROM T012A INTO @DATA(ld_i_vorga). | ||||
Search for further information about these or an SAP related objects