SAP CHECK_BATCH_POSTING Function Module for
CHECK_BATCH_POSTING is a standard check batch posting 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 check batch posting FM, simply by entering the name CHECK_BATCH_POSTING into the relevant SAP transaction such as SE37 or SE38.
Function Group: GLCF
Program Name: SAPLGLCF
Main Program: SAPLGLCF
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CHECK_BATCH_POSTING 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 'CHECK_BATCH_POSTING'".
EXPORTING
BUKRS = "Company code
RLDNR = "Ledger
EXCEPTIONS
NO_BATCH_POSTING = 1
IMPORTING Parameters details for CHECK_BATCH_POSTING
BUKRS - Company code
Data type: GLT0-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
RLDNR - Ledger
Data type: T881-RLDNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_BATCH_POSTING - Direct posting company code/ledger not in background
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CHECK_BATCH_POSTING 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_bukrs | TYPE GLT0-BUKRS, " | |||
| lv_no_batch_posting | TYPE GLT0, " | |||
| lv_rldnr | TYPE T881-RLDNR. " |
|   CALL FUNCTION 'CHECK_BATCH_POSTING' " |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| RLDNR | = lv_rldnr | |
| EXCEPTIONS | ||
| NO_BATCH_POSTING = 1 | ||
| . " CHECK_BATCH_POSTING | ||
ABAP code using 7.40 inline data declarations to call FM CHECK_BATCH_POSTING
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 GLT0 INTO @DATA(ld_bukrs). | ||||
| "SELECT single RLDNR FROM T881 INTO @DATA(ld_rldnr). | ||||
Search for further information about these or an SAP related objects