SAP JV_GB01_DIRECT_INPUT Function Module for JV GB01 Direct Input
JV_GB01_DIRECT_INPUT is a standard jv gb01 direct input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for JV GB01 Direct Input 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 jv gb01 direct input FM, simply by entering the name JV_GB01_DIRECT_INPUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJPO
Program Name: SAPLGJPO
Main Program: SAPLGJPO
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function JV_GB01_DIRECT_INPUT 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 'JV_GB01_DIRECT_INPUT'"JV GB01 Direct Input.
EXPORTING
* E_DOCNR = ' ' "
E_BUKRS = "
E_YEAR = "
* E_BUDAT = SY-DATUM "
* E_WUDAT = 00000000 "
* E_ZEROCHK = ' ' "
E_ACTIV = "
IMPORTING
I_DOCNR = "
TABLES
T_GLU1 = "
EXCEPTIONS
DOCUMENT_NUMBER_NOT_FOUND = 1 LOCAL_CURRENCY_NOT_CORRECT = 2
IMPORTING Parameters details for JV_GB01_DIRECT_INPUT
E_DOCNR -
Data type: GLU1-DOCNRDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
E_BUKRS -
Data type: GLU1-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
E_YEAR -
Data type: GLU1-RYEAROptional: No
Call by Reference: No ( called with pass by value option)
E_BUDAT -
Data type: BKPF-BUDATDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
E_WUDAT -
Data type: BKPF-BUDATDefault: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)
E_ZEROCHK -
Data type: BSEG-BUZIDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
E_ACTIV -
Data type: GLU1-ACTIVOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for JV_GB01_DIRECT_INPUT
I_DOCNR -
Data type: GLU1-DOCNROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for JV_GB01_DIRECT_INPUT
T_GLU1 -
Data type: GLU1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DOCUMENT_NUMBER_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOCAL_CURRENCY_NOT_CORRECT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JV_GB01_DIRECT_INPUT 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: | ||||
| lt_t_glu1 | TYPE STANDARD TABLE OF GLU1, " | |||
| lv_e_docnr | TYPE GLU1-DOCNR, " ' ' | |||
| lv_i_docnr | TYPE GLU1-DOCNR, " | |||
| lv_document_number_not_found | TYPE GLU1, " | |||
| lv_e_bukrs | TYPE GLU1-BUKRS, " | |||
| lv_local_currency_not_correct | TYPE GLU1, " | |||
| lv_e_year | TYPE GLU1-RYEAR, " | |||
| lv_e_budat | TYPE BKPF-BUDAT, " SY-DATUM | |||
| lv_e_wudat | TYPE BKPF-BUDAT, " 00000000 | |||
| lv_e_zerochk | TYPE BSEG-BUZID, " ' ' | |||
| lv_e_activ | TYPE GLU1-ACTIV. " |
|   CALL FUNCTION 'JV_GB01_DIRECT_INPUT' "JV GB01 Direct Input |
| EXPORTING | ||
| E_DOCNR | = lv_e_docnr | |
| E_BUKRS | = lv_e_bukrs | |
| E_YEAR | = lv_e_year | |
| E_BUDAT | = lv_e_budat | |
| E_WUDAT | = lv_e_wudat | |
| E_ZEROCHK | = lv_e_zerochk | |
| E_ACTIV | = lv_e_activ | |
| IMPORTING | ||
| I_DOCNR | = lv_i_docnr | |
| TABLES | ||
| T_GLU1 | = lt_t_glu1 | |
| EXCEPTIONS | ||
| DOCUMENT_NUMBER_NOT_FOUND = 1 | ||
| LOCAL_CURRENCY_NOT_CORRECT = 2 | ||
| . " JV_GB01_DIRECT_INPUT | ||
ABAP code using 7.40 inline data declarations to call FM JV_GB01_DIRECT_INPUT
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 DOCNR FROM GLU1 INTO @DATA(ld_e_docnr). | ||||
| DATA(ld_e_docnr) | = ' '. | |||
| "SELECT single DOCNR FROM GLU1 INTO @DATA(ld_i_docnr). | ||||
| "SELECT single BUKRS FROM GLU1 INTO @DATA(ld_e_bukrs). | ||||
| "SELECT single RYEAR FROM GLU1 INTO @DATA(ld_e_year). | ||||
| "SELECT single BUDAT FROM BKPF INTO @DATA(ld_e_budat). | ||||
| DATA(ld_e_budat) | = SY-DATUM. | |||
| "SELECT single BUDAT FROM BKPF INTO @DATA(ld_e_wudat). | ||||
| DATA(ld_e_wudat) | = 00000000. | |||
| "SELECT single BUZID FROM BSEG INTO @DATA(ld_e_zerochk). | ||||
| DATA(ld_e_zerochk) | = ' '. | |||
| "SELECT single ACTIV FROM GLU1 INTO @DATA(ld_e_activ). | ||||
Search for further information about these or an SAP related objects