SAP DOCHEADER_PERIOD_FIND_CHECK Function Module for
DOCHEADER_PERIOD_FIND_CHECK is a standard docheader period find check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 docheader period find check FM, simply by entering the name DOCHEADER_PERIOD_FIND_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: ACHD
Program Name: SAPLACHD
Main Program: SAPLACHD
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DOCHEADER_PERIOD_FIND_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 'DOCHEADER_PERIOD_FIND_CHECK'".
EXPORTING
I_BUKRS = "
I_BLDAT = "
I_BUDAT = "
* I_KOART = '+' "
* I_HKONT = '+' "
* I_SOFTCHECK = "
* I_LEDGER = "
* I_LDGRP = "
IMPORTING
E_GJAHR = "
E_XRUEB = "
E_CURRJ = "
CHANGING
C_MONAT = "
IMPORTING Parameters details for DOCHEADER_PERIOD_FIND_CHECK
I_BUKRS -
Data type: BKPF-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_BLDAT -
Data type: BKPF-BLDATOptional: No
Call by Reference: No ( called with pass by value option)
I_BUDAT -
Data type: BKPF-BUDATOptional: No
Call by Reference: No ( called with pass by value option)
I_KOART -
Data type: BSEG-KOARTDefault: '+'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_HKONT -
Data type: BSEG-HKONTDefault: '+'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SOFTCHECK -
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_LEDGER -
Data type: RLDNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_LDGRP -
Data type: FAGL_LDGRPOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DOCHEADER_PERIOD_FIND_CHECK
E_GJAHR -
Data type: BKPF-GJAHROptional: No
Call by Reference: No ( called with pass by value option)
E_XRUEB -
Data type: BKPF-XRUEBOptional: No
Call by Reference: No ( called with pass by value option)
E_CURRJ -
Data type: BKP1-CURRJOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for DOCHEADER_PERIOD_FIND_CHECK
C_MONAT -
Data type: BKPF-MONATOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DOCHEADER_PERIOD_FIND_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_c_monat | TYPE BKPF-MONAT, " | |||
| lv_e_gjahr | TYPE BKPF-GJAHR, " | |||
| lv_i_bukrs | TYPE BKPF-BUKRS, " | |||
| lv_e_xrueb | TYPE BKPF-XRUEB, " | |||
| lv_i_bldat | TYPE BKPF-BLDAT, " | |||
| lv_e_currj | TYPE BKP1-CURRJ, " | |||
| lv_i_budat | TYPE BKPF-BUDAT, " | |||
| lv_i_koart | TYPE BSEG-KOART, " '+' | |||
| lv_i_hkont | TYPE BSEG-HKONT, " '+' | |||
| lv_i_softcheck | TYPE XFELD, " | |||
| lv_i_ledger | TYPE RLDNR, " | |||
| lv_i_ldgrp | TYPE FAGL_LDGRP. " |
|   CALL FUNCTION 'DOCHEADER_PERIOD_FIND_CHECK' " |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_BLDAT | = lv_i_bldat | |
| I_BUDAT | = lv_i_budat | |
| I_KOART | = lv_i_koart | |
| I_HKONT | = lv_i_hkont | |
| I_SOFTCHECK | = lv_i_softcheck | |
| I_LEDGER | = lv_i_ledger | |
| I_LDGRP | = lv_i_ldgrp | |
| IMPORTING | ||
| E_GJAHR | = lv_e_gjahr | |
| E_XRUEB | = lv_e_xrueb | |
| E_CURRJ | = lv_e_currj | |
| CHANGING | ||
| C_MONAT | = lv_c_monat | |
| . " DOCHEADER_PERIOD_FIND_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM DOCHEADER_PERIOD_FIND_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 MONAT FROM BKPF INTO @DATA(ld_c_monat). | ||||
| "SELECT single GJAHR FROM BKPF INTO @DATA(ld_e_gjahr). | ||||
| "SELECT single BUKRS FROM BKPF INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single XRUEB FROM BKPF INTO @DATA(ld_e_xrueb). | ||||
| "SELECT single BLDAT FROM BKPF INTO @DATA(ld_i_bldat). | ||||
| "SELECT single CURRJ FROM BKP1 INTO @DATA(ld_e_currj). | ||||
| "SELECT single BUDAT FROM BKPF INTO @DATA(ld_i_budat). | ||||
| "SELECT single KOART FROM BSEG INTO @DATA(ld_i_koart). | ||||
| DATA(ld_i_koart) | = '+'. | |||
| "SELECT single HKONT FROM BSEG INTO @DATA(ld_i_hkont). | ||||
| DATA(ld_i_hkont) | = '+'. | |||
Search for further information about these or an SAP related objects