SAP J_3G_LGBELEGE_CHECK Function Module for Check Existence of PBE Document
J_3G_LGBELEGE_CHECK is a standard j 3g lgbelege check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Existence of PBE Document 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 j 3g lgbelege check FM, simply by entering the name J_3G_LGBELEGE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: J3GB
Program Name: SAPLJ3GB
Main Program: SAPLJ3GB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_3G_LGBELEGE_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 'J_3G_LGBELEGE_CHECK'"Check Existence of PBE Document.
EXPORTING
I_DATUM_VON = "
* I_EMPDEB = ' ' "Debtor of Recipient
* I_EMPEXT = ' ' "External Ship-To Party - Recipient
* I_EMPPSP = ' ' "Receiving WBS Element
* I_DATUM_BIS = SY-DATUM "
* I_EMPFAENGER = ' ' "
* I_EQUNR = ' ' "
* I_LVART = ' ' "
* I_PERNR = ' ' "
* I_BLART = ' ' "Document Type
* I_BELNRI = ' ' "Document Number
* I_EBELNR = ' ' "External Document Number
TABLES
T_BELEGE = "
EXCEPTIONS
KEIN_BELEG_VORHANDEN = 1 DATUM_FEHLERHAFT = 2
IMPORTING Parameters details for J_3G_LGBELEGE_CHECK
I_DATUM_VON -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_EMPDEB - Debtor of Recipient
Data type: J_3GBELK-J_3GEMPDEBDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_EMPEXT - External Ship-To Party - Recipient
Data type: J_3GBELK-J_3GEMPEXTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_EMPPSP - Receiving WBS Element
Data type: J_3GBELK-J_3GEMPPSPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATUM_BIS -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_EMPFAENGER -
Data type: J_3GBELK-J_3GEMPFAEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_EQUNR -
Data type: J_3GBELK-EQUNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LVART -
Data type: J_3GBELP-J_3GLVARTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PERNR -
Data type: J_3GBELK-PERNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BLART - Document Type
Data type: J_3GBELK-J_3GBLARTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BELNRI - Document Number
Data type: J_3GBELK-J_3GBELNRIDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_EBELNR - External Document Number
Data type: J_3GBELK-J_3GBELNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for J_3G_LGBELEGE_CHECK
T_BELEGE -
Data type: J_3GMATRIXOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
KEIN_BELEG_VORHANDEN -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATUM_FEHLERHAFT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_3G_LGBELEGE_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: | ||||
| lt_t_belege | TYPE STANDARD TABLE OF J_3GMATRIX, " | |||
| lv_i_datum_von | TYPE SY-DATUM, " | |||
| lv_kein_beleg_vorhanden | TYPE SY, " | |||
| lv_i_empdeb | TYPE J_3GBELK-J_3GEMPDEB, " SPACE | |||
| lv_i_empext | TYPE J_3GBELK-J_3GEMPEXT, " SPACE | |||
| lv_i_emppsp | TYPE J_3GBELK-J_3GEMPPSP, " SPACE | |||
| lv_i_datum_bis | TYPE SY-DATUM, " SY-DATUM | |||
| lv_datum_fehlerhaft | TYPE SY, " | |||
| lv_i_empfaenger | TYPE J_3GBELK-J_3GEMPFAE, " SPACE | |||
| lv_i_equnr | TYPE J_3GBELK-EQUNR, " SPACE | |||
| lv_i_lvart | TYPE J_3GBELP-J_3GLVART, " SPACE | |||
| lv_i_pernr | TYPE J_3GBELK-PERNR, " SPACE | |||
| lv_i_blart | TYPE J_3GBELK-J_3GBLART, " SPACE | |||
| lv_i_belnri | TYPE J_3GBELK-J_3GBELNRI, " SPACE | |||
| lv_i_ebelnr | TYPE J_3GBELK-J_3GBELNR. " SPACE |
|   CALL FUNCTION 'J_3G_LGBELEGE_CHECK' "Check Existence of PBE Document |
| EXPORTING | ||
| I_DATUM_VON | = lv_i_datum_von | |
| I_EMPDEB | = lv_i_empdeb | |
| I_EMPEXT | = lv_i_empext | |
| I_EMPPSP | = lv_i_emppsp | |
| I_DATUM_BIS | = lv_i_datum_bis | |
| I_EMPFAENGER | = lv_i_empfaenger | |
| I_EQUNR | = lv_i_equnr | |
| I_LVART | = lv_i_lvart | |
| I_PERNR | = lv_i_pernr | |
| I_BLART | = lv_i_blart | |
| I_BELNRI | = lv_i_belnri | |
| I_EBELNR | = lv_i_ebelnr | |
| TABLES | ||
| T_BELEGE | = lt_t_belege | |
| EXCEPTIONS | ||
| KEIN_BELEG_VORHANDEN = 1 | ||
| DATUM_FEHLERHAFT = 2 | ||
| . " J_3G_LGBELEGE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM J_3G_LGBELEGE_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 DATUM FROM SY INTO @DATA(ld_i_datum_von). | ||||
| "SELECT single J_3GEMPDEB FROM J_3GBELK INTO @DATA(ld_i_empdeb). | ||||
| DATA(ld_i_empdeb) | = ' '. | |||
| "SELECT single J_3GEMPEXT FROM J_3GBELK INTO @DATA(ld_i_empext). | ||||
| DATA(ld_i_empext) | = ' '. | |||
| "SELECT single J_3GEMPPSP FROM J_3GBELK INTO @DATA(ld_i_emppsp). | ||||
| DATA(ld_i_emppsp) | = ' '. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_datum_bis). | ||||
| DATA(ld_i_datum_bis) | = SY-DATUM. | |||
| "SELECT single J_3GEMPFAE FROM J_3GBELK INTO @DATA(ld_i_empfaenger). | ||||
| DATA(ld_i_empfaenger) | = ' '. | |||
| "SELECT single EQUNR FROM J_3GBELK INTO @DATA(ld_i_equnr). | ||||
| DATA(ld_i_equnr) | = ' '. | |||
| "SELECT single J_3GLVART FROM J_3GBELP INTO @DATA(ld_i_lvart). | ||||
| DATA(ld_i_lvart) | = ' '. | |||
| "SELECT single PERNR FROM J_3GBELK INTO @DATA(ld_i_pernr). | ||||
| DATA(ld_i_pernr) | = ' '. | |||
| "SELECT single J_3GBLART FROM J_3GBELK INTO @DATA(ld_i_blart). | ||||
| DATA(ld_i_blart) | = ' '. | |||
| "SELECT single J_3GBELNRI FROM J_3GBELK INTO @DATA(ld_i_belnri). | ||||
| DATA(ld_i_belnri) | = ' '. | |||
| "SELECT single J_3GBELNR FROM J_3GBELK INTO @DATA(ld_i_ebelnr). | ||||
| DATA(ld_i_ebelnr) | = ' '. | |||
Search for further information about these or an SAP related objects