SAP J_3G_LOADING_COST_DEFAULT Function Module for Default Billing Indicator on Item Level

Search SAP Function Modules

J_3G_LOADING_COST_DEFAULT is a standard j 3g loading cost 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 loading cost default FM, simply by entering the name J_3G_LOADING_COST_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_LOADING_COST_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_LOADING_COST_DEFAULT'"Default Billing Indicator on Item Level
  EXPORTING
   I_ATYP =  "Recipient Type Sender
   I_ETYP =  "Recipient Type Recipient
   I_BEWEG =  "Internal Indicator for Transaction Type
   I_ABSDEB =  "Debtor of Sender
   I_EMPDEB =  "Debtor of Recipient
   I_BLART =  "Document Type - ETM

TABLES
*  XBELP =  "Shipping Document Item (Equipment)
*  XBELP_BAL =  "Document Item (Material)

.

IMPORTING Parameters details for J_3G_LOADING_COST_DEFAULT

I_ATYP - Recipient Type Sender

Data type: KNA1-J_3GETYP
Optional: No
Call by Reference: Yes

I_ETYP - Recipient Type Recipient

Data type: KNA1-J_3GETYP
Optional: No
Call by Reference: Yes

I_BEWEG - Internal Indicator for Transaction Type

Data type: J_3GBELK-J_3GBEWEG
Optional: No
Call by Reference: Yes

I_ABSDEB - Debtor of Sender

Data type: J_3GBELK-J_3GABSDEB
Optional: No
Call by Reference: Yes

I_EMPDEB - Debtor of Recipient

Data type: J_3GBELK-J_3GEMPDEB
Optional: No
Call by Reference: Yes

I_BLART - Document Type - ETM

Data type: J_3GBELK-J_3GBLART
Optional: No
Call by Reference: Yes

TABLES Parameters details for J_3G_LOADING_COST_DEFAULT

XBELP - Shipping Document Item (Equipment)

Data type: J_3GBELP_S
Optional: Yes
Call by Reference: No ( called with pass by value option)

XBELP_BAL - Document Item (Material)

Data type: J_3GBELP_S
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for J_3G_LOADING_COST_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.

ABAP code using 7.40 inline data declarations to call FM J_3G_LOADING_COST_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.

Search for further information about these or an SAP related objects