SAP J_3G_BILLING_INDICATOR_DEFAULT Function Module for Default Billing Indicator on Item Level
J_3G_BILLING_INDICATOR_DEFAULT is a standard j 3g billing indicator default SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Default Billing Indicator on Item Level 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 billing indicator default FM, simply by entering the name J_3G_BILLING_INDICATOR_DEFAULT into the relevant SAP transaction such as SE37 or SE38.
Function Group: J3GM
Program Name: SAPLJ3GM
Main Program: SAPLJ3GM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function J_3G_BILLING_INDICATOR_DEFAULT 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_BILLING_INDICATOR_DEFAULT'"Default Billing Indicator on Item Level.
EXPORTING
I_ATYP = "Recipient Type Sender
I_ETYP = "Recipient Type Recipient
I_FAKTAB = "Billing Indicator - Sender
I_FAKTEM = "Billing Indicator - Recipient
I_BEWEG = "Internal Indicator for Transaction Type
I_MITTLE = "Intermediate Recipient
I_BLTYP = "CEM Document Category
IMPORTING
E_FAKTAB = "Billing Indicator - Sender
E_FAKTEM = "Billing Indicator - Recipient
TABLES
* XBELP = "Shipping Document Item (Equipment)
* XBELP_BAL = "Document Item (Material)
IMPORTING Parameters details for J_3G_BILLING_INDICATOR_DEFAULT
I_ATYP - Recipient Type Sender
Data type: KNA1-J_3GETYPOptional: No
Call by Reference: Yes
I_ETYP - Recipient Type Recipient
Data type: KNA1-J_3GETYPOptional: No
Call by Reference: Yes
I_FAKTAB - Billing Indicator - Sender
Data type: J_3GBELK-J_3GFAKTABOptional: No
Call by Reference: Yes
I_FAKTEM - Billing Indicator - Recipient
Data type: J_3GBELK-J_3GFAKTEMOptional: No
Call by Reference: Yes
I_BEWEG - Internal Indicator for Transaction Type
Data type: J_3GBELK-J_3GBEWEGOptional: No
Call by Reference: Yes
I_MITTLE - Intermediate Recipient
Data type: J_3GBELK-J_3GMITTLEOptional: No
Call by Reference: Yes
I_BLTYP - CEM Document Category
Data type: J_3GBELK-J_3GBLTYPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for J_3G_BILLING_INDICATOR_DEFAULT
E_FAKTAB - Billing Indicator - Sender
Data type: J_3GBELK-J_3GFAKTABOptional: No
Call by Reference: Yes
E_FAKTEM - Billing Indicator - Recipient
Data type: J_3GBELK-J_3GFAKTEMOptional: No
Call by Reference: Yes
TABLES Parameters details for J_3G_BILLING_INDICATOR_DEFAULT
XBELP - Shipping Document Item (Equipment)
Data type: J_3GBELP_SOptional: Yes
Call by Reference: Yes
XBELP_BAL - Document Item (Material)
Data type: J_3GBELP_SOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for J_3G_BILLING_INDICATOR_DEFAULT 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_xbelp | TYPE STANDARD TABLE OF J_3GBELP_S, " | |||
| lv_i_atyp | TYPE KNA1-J_3GETYP, " | |||
| lv_e_faktab | TYPE J_3GBELK-J_3GFAKTAB, " | |||
| lv_i_etyp | TYPE KNA1-J_3GETYP, " | |||
| lv_e_faktem | TYPE J_3GBELK-J_3GFAKTEM, " | |||
| lt_xbelp_bal | TYPE STANDARD TABLE OF J_3GBELP_S, " | |||
| lv_i_faktab | TYPE J_3GBELK-J_3GFAKTAB, " | |||
| lv_i_faktem | TYPE J_3GBELK-J_3GFAKTEM, " | |||
| lv_i_beweg | TYPE J_3GBELK-J_3GBEWEG, " | |||
| lv_i_mittle | TYPE J_3GBELK-J_3GMITTLE, " | |||
| lv_i_bltyp | TYPE J_3GBELK-J_3GBLTYP. " |
| CALL FUNCTION 'J_3G_BILLING_INDICATOR_DEFAULT' "Default Billing Indicator on Item Level |
| EXPORTING | ||
| I_ATYP | = lv_i_atyp | |
| I_ETYP | = lv_i_etyp | |
| I_FAKTAB | = lv_i_faktab | |
| I_FAKTEM | = lv_i_faktem | |
| I_BEWEG | = lv_i_beweg | |
| I_MITTLE | = lv_i_mittle | |
| I_BLTYP | = lv_i_bltyp | |
| IMPORTING | ||
| E_FAKTAB | = lv_e_faktab | |
| E_FAKTEM | = lv_e_faktem | |
| TABLES | ||
| XBELP | = lt_xbelp | |
| XBELP_BAL | = lt_xbelp_bal | |
| . " J_3G_BILLING_INDICATOR_DEFAULT | ||
ABAP code using 7.40 inline data declarations to call FM J_3G_BILLING_INDICATOR_DEFAULT
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_3GETYP FROM KNA1 INTO @DATA(ld_i_atyp). | ||||
| "SELECT single J_3GFAKTAB FROM J_3GBELK INTO @DATA(ld_e_faktab). | ||||
| "SELECT single J_3GETYP FROM KNA1 INTO @DATA(ld_i_etyp). | ||||
| "SELECT single J_3GFAKTEM FROM J_3GBELK INTO @DATA(ld_e_faktem). | ||||
| "SELECT single J_3GFAKTAB FROM J_3GBELK INTO @DATA(ld_i_faktab). | ||||
| "SELECT single J_3GFAKTEM FROM J_3GBELK INTO @DATA(ld_i_faktem). | ||||
| "SELECT single J_3GBEWEG FROM J_3GBELK INTO @DATA(ld_i_beweg). | ||||
| "SELECT single J_3GMITTLE FROM J_3GBELK INTO @DATA(ld_i_mittle). | ||||
| "SELECT single J_3GBLTYP FROM J_3GBELK INTO @DATA(ld_i_bltyp). | ||||
Search for further information about these or an SAP related objects