SAP J_3G_FAKTKENNUNG_CHECK_ABS Function Module for Check Billing Indicator Sender - Header
J_3G_FAKTKENNUNG_CHECK_ABS is a standard j 3g faktkennung check abs 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 Billing Indicator Sender - Header 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 faktkennung check abs FM, simply by entering the name J_3G_FAKTKENNUNG_CHECK_ABS into the relevant SAP transaction such as SE37 or SE38.
Function Group: J3GI
Program Name: SAPLJ3GI
Main Program: SAPLJ3GI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_3G_FAKTKENNUNG_CHECK_ABS 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_FAKTKENNUNG_CHECK_ABS'"Check Billing Indicator Sender - Header.
EXPORTING
I_BLTYP = "
I_BEWEG = "Movement/Transaction Indicator
I_TYP = "Recipient Type
I_MITTLE = "
I_FAKTAB = "
IMPORTING
E_FAKTAB = "Billing Indicator
EXCEPTIONS
NO_TYP = 1
IMPORTING Parameters details for J_3G_FAKTKENNUNG_CHECK_ABS
I_BLTYP -
Data type: J_3GBELK-J_3GBLTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_BEWEG - Movement/Transaction Indicator
Data type: J_3GBELK-J_3GBEWEGOptional: No
Call by Reference: No ( called with pass by value option)
I_TYP - Recipient Type
Data type: KNA1-J_3GETYPOptional: No
Call by Reference: No ( called with pass by value option)
I_MITTLE -
Data type: J_3GBELK-J_3GMITTLEOptional: No
Call by Reference: No ( called with pass by value option)
I_FAKTAB -
Data type: J_3GBELK-J_3GFAKTEMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for J_3G_FAKTKENNUNG_CHECK_ABS
E_FAKTAB - Billing Indicator
Data type: J_3GBELK-J_3GFAKTEMOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_TYP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_3G_FAKTKENNUNG_CHECK_ABS 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_no_typ | TYPE STRING, " | |||
| lv_i_bltyp | TYPE J_3GBELK-J_3GBLTYP, " | |||
| lv_e_faktab | TYPE J_3GBELK-J_3GFAKTEM, " | |||
| lv_i_beweg | TYPE J_3GBELK-J_3GBEWEG, " | |||
| lv_i_typ | TYPE KNA1-J_3GETYP, " | |||
| lv_i_mittle | TYPE J_3GBELK-J_3GMITTLE, " | |||
| lv_i_faktab | TYPE J_3GBELK-J_3GFAKTEM. " |
|   CALL FUNCTION 'J_3G_FAKTKENNUNG_CHECK_ABS' "Check Billing Indicator Sender - Header |
| EXPORTING | ||
| I_BLTYP | = lv_i_bltyp | |
| I_BEWEG | = lv_i_beweg | |
| I_TYP | = lv_i_typ | |
| I_MITTLE | = lv_i_mittle | |
| I_FAKTAB | = lv_i_faktab | |
| IMPORTING | ||
| E_FAKTAB | = lv_e_faktab | |
| EXCEPTIONS | ||
| NO_TYP = 1 | ||
| . " J_3G_FAKTKENNUNG_CHECK_ABS | ||
ABAP code using 7.40 inline data declarations to call FM J_3G_FAKTKENNUNG_CHECK_ABS
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 J_3GBLTYP FROM J_3GBELK INTO @DATA(ld_i_bltyp). | ||||
| "SELECT single J_3GFAKTEM FROM J_3GBELK INTO @DATA(ld_e_faktab). | ||||
| "SELECT single J_3GBEWEG FROM J_3GBELK INTO @DATA(ld_i_beweg). | ||||
| "SELECT single J_3GETYP FROM KNA1 INTO @DATA(ld_i_typ). | ||||
| "SELECT single J_3GMITTLE FROM J_3GBELK INTO @DATA(ld_i_mittle). | ||||
| "SELECT single J_3GFAKTEM FROM J_3GBELK INTO @DATA(ld_i_faktab). | ||||
Search for further information about these or an SAP related objects