SAP J_7L_CUST3_BAGATELLREGEL Function Module for NOTRANSL: REA Bagatellregel ( Template )

Search SAP Function Modules

J_7L_CUST3_BAGATELLREGEL is a standard j 7l cust3 bagatellregel SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: REA Bagatellregel ( Template ) 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 7l cust3 bagatellregel FM, simply by entering the name J_7L_CUST3_BAGATELLREGEL into the relevant SAP transaction such as SE37 or SE38.

Function Group: J7LO
Program Name: SAPLJ7LO
Main Program: SAPLJ7LO
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_7L_CUST3_BAGATELLREGEL 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_7L_CUST3_BAGATELLREGEL'"NOTRANSL: REA Bagatellregel ( Template )
  EXPORTING
   KZBAGREG =  "Petty Rule Indicator
   LAND1 =  "Country
   ENTNR =  "Recycling Partner
   PLVRS =  "Price List Version
   BAGRGMOD =  "Petty Rule Mode
   GGEWANTBAG =  "Weight Limit
*  STOFF =  "Fraction
   VPART =  "Packaging Type
*  BAGRGGGEW =  "Weight Limit
*  GEWEI =  "Unit of Weight
*  VPEBENE =  "Packaging Level
   BUKRS =  "Company Code

CHANGING
   BAGREG =  "

TABLES
   FRAKTION =  "Fractions

EXCEPTIONS
   BAGATELLREGEL_ERROR = 1 

.

IMPORTING Parameters details for J_7L_CUST3_BAGATELLREGEL

KZBAGREG - Petty Rule Indicator

Data type: J_7LE05-KZBAGREG
Optional: No
Call by Reference: Yes

LAND1 - Country

Data type: J_7LP01-LAND1
Optional: No
Call by Reference: Yes

ENTNR - Recycling Partner

Data type: J_7LP01-ENTNR
Optional: No
Call by Reference: Yes

PLVRS - Price List Version

Data type: J_7LP01-PLVRS
Optional: No
Call by Reference: Yes

BAGRGMOD - Petty Rule Mode

Data type: J_7LE05-BAGRGMOD
Optional: No
Call by Reference: Yes

GGEWANTBAG - Weight Limit

Data type: J_7LE05-GGEWANTBAG
Optional: No
Call by Reference: Yes

STOFF - Fraction

Data type: J_7LE05-STOFF
Optional: Yes
Call by Reference: Yes

VPART - Packaging Type

Data type: J_7LE05-VPART
Optional: No
Call by Reference: Yes

BAGRGGGEW - Weight Limit

Data type: J_7LE05-BAGRGGGEW
Optional: Yes
Call by Reference: Yes

GEWEI - Unit of Weight

Data type: J_7LE05-GEWEI
Optional: Yes
Call by Reference: Yes

VPEBENE - Packaging Level

Data type: J_7LM04-VPEBENE
Optional: Yes
Call by Reference: Yes

BUKRS - Company Code

Data type: J_7LP01-BUKRS
Optional: No
Call by Reference: Yes

CHANGING Parameters details for J_7L_CUST3_BAGATELLREGEL

BAGREG -

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

TABLES Parameters details for J_7L_CUST3_BAGATELLREGEL

FRAKTION - Fractions

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

EXCEPTIONS details

BAGATELLREGEL_ERROR -

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

Copy and paste ABAP code example for J_7L_CUST3_BAGATELLREGEL 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_7L_CUST3_BAGATELLREGEL

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