SAP J_7L_ARTICLE_CHECK Function Module for REA Article Management: Consistency Check
J_7L_ARTICLE_CHECK is a standard j 7l article check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for REA Article Management: Consistency Check 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 article check FM, simply by entering the name J_7L_ARTICLE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: J7LART_MAIN_INTERFACE
Program Name: SAPLJ7LART_MAIN_INTERFACE
Main Program: SAPLJ7LART_MAIN_INTERFACE
Appliation area:
Release date: 22-Oct-2007
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function J_7L_ARTICLE_CHECK 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_ARTICLE_CHECK'"REA Article Management: Consistency Check.
EXPORTING
I_MATNR = "Article
I_BUKRS = "Company Code
I_LAND1 = "Country of Article
I_VRKME = "Sales Unit
* I_DATAB = "Date valid from
* I_DATBI = "Valid To
* I_FLG_FILTER_ON = 'X' "'X' => Result Filtered in Accordance with Customizing
* I_VARIANTE = "Variant in REA Master Data
IMPORTING
O_CHECK_SUMMARY = "Summary of Check
RETURN = "Return Parameters
TABLES
* I_ENTNR = "Restriction to Individual Recycling Partners
* O_MESSAGE_TAB = "Result of Article Consistency Check
IMPORTING Parameters details for J_7L_ARTICLE_CHECK
I_MATNR - Article
Data type: MATNROptional: No
Call by Reference: No ( called with pass by value option)
I_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_LAND1 - Country of Article
Data type: LAND1Optional: No
Call by Reference: No ( called with pass by value option)
I_VRKME - Sales Unit
Data type: VRKMEOptional: No
Call by Reference: No ( called with pass by value option)
I_DATAB - Date valid from
Data type: DATABOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATBI - Valid To
Data type: DATBIOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_FILTER_ON - 'X' => Result Filtered in Accordance with Customizing
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VARIANTE - Variant in REA Master Data
Data type: J_7LVARIANTEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for J_7L_ARTICLE_CHECK
O_CHECK_SUMMARY - Summary of Check
Data type: MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for J_7L_ARTICLE_CHECK
I_ENTNR - Restriction to Individual Recycling Partners
Data type: J_7LENTNR_RANGEOptional: Yes
Call by Reference: Yes
O_MESSAGE_TAB - Result of Article Consistency Check
Data type: J_7LCHECKCONPACKOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for J_7L_ARTICLE_CHECK 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_i_entnr | TYPE STANDARD TABLE OF J_7LENTNR_RANGE, " | |||
| lv_i_matnr | TYPE MATNR, " | |||
| lv_o_check_summary | TYPE MSGTY, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lt_o_message_tab | TYPE STANDARD TABLE OF J_7LCHECKCONPACK, " | |||
| lv_i_land1 | TYPE LAND1, " | |||
| lv_i_vrkme | TYPE VRKME, " | |||
| lv_i_datab | TYPE DATAB, " | |||
| lv_i_datbi | TYPE DATBI, " | |||
| lv_i_flg_filter_on | TYPE XFELD, " 'X' | |||
| lv_i_variante | TYPE J_7LVARIANTE. " |
|   CALL FUNCTION 'J_7L_ARTICLE_CHECK' "REA Article Management: Consistency Check |
| EXPORTING | ||
| I_MATNR | = lv_i_matnr | |
| I_BUKRS | = lv_i_bukrs | |
| I_LAND1 | = lv_i_land1 | |
| I_VRKME | = lv_i_vrkme | |
| I_DATAB | = lv_i_datab | |
| I_DATBI | = lv_i_datbi | |
| I_FLG_FILTER_ON | = lv_i_flg_filter_on | |
| I_VARIANTE | = lv_i_variante | |
| IMPORTING | ||
| O_CHECK_SUMMARY | = lv_o_check_summary | |
| RETURN | = lv_return | |
| TABLES | ||
| I_ENTNR | = lt_i_entnr | |
| O_MESSAGE_TAB | = lt_o_message_tab | |
| . " J_7L_ARTICLE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM J_7L_ARTICLE_CHECK
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.| DATA(ld_i_flg_filter_on) | = 'X'. | |||
Search for further information about these or an SAP related objects