SAP J_7L_MELDUNG Function Module for NOTRANSL: REA Bewegungsdaten Faktura und Materialbelege für Periodenmeldun

Search SAP Function Modules

J_7L_MELDUNG is a standard j 7l meldung 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 Bewegungsdaten Faktura und Materialbelege für Periodenmeldun 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 meldung FM, simply by entering the name J_7L_MELDUNG into the relevant SAP transaction such as SE37 or SE38.

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

Function J_7L_MELDUNG 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_MELDUNG'"NOTRANSL: REA Bewegungsdaten Faktura und Materialbelege für Periodenmeldun
  EXPORTING
   ENTNA =  "Recycling Partner
   BUKRS =  "Company Code
   LAND1 =  "Country
*  WAERK =  "Document Currency
*  BLART =  "Document Type
   DATAB =  "
   DATBI =  "
*  TEST = 'X' "
*  REPID = SY-REPID "Report

TABLES
*  RSPARAMS_TAB =  "
*  J_7LV1K_TAB =  "
*  J_7LV1P_TAB =  "
*  J_7LV1M_TAB =  "
*  BALMI_TAB =  "

EXCEPTIONS
   DATA_INCONSISTENCY = 1 

.

IMPORTING Parameters details for J_7L_MELDUNG

ENTNA - Recycling Partner

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

BUKRS - Company Code

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

LAND1 - Country

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

WAERK - Document Currency

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

BLART - Document Type

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

DATAB -

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

DATBI -

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

TEST -

Data type: J_7LMS-TLKNZ
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

REPID - Report

Data type: SY-REPID
Default: SY-REPID
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for J_7L_MELDUNG

RSPARAMS_TAB -

Data type: RSPARAMS
Optional: Yes
Call by Reference: Yes

J_7LV1K_TAB -

Data type: J_7LV1K
Optional: Yes
Call by Reference: Yes

J_7LV1P_TAB -

Data type: J_7LV1P
Optional: Yes
Call by Reference: Yes

J_7LV1M_TAB -

Data type: J_7LV1M
Optional: Yes
Call by Reference: Yes

BALMI_TAB -

Data type: BALMI
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

DATA_INCONSISTENCY - Inconsistent Data

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for J_7L_MELDUNG 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_MELDUNG

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