SAP J_7L_ARTICLE_GET_VALIDITY Function Module for REA Article Management: Validity Periods of Article









J_7L_ARTICLE_GET_VALIDITY is a standard j 7l article get validity 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: Validity Periods of Article 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 get validity FM, simply by entering the name J_7L_ARTICLE_GET_VALIDITY 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_GET_VALIDITY 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_GET_VALIDITY'"REA Article Management: Validity Periods of Article
  EXPORTING
   I_MATNR =  "Article Number
   I_BUKRS =  "Company Code
   I_LAND =  "Country of Article
   I_VRKME =  "Sales Unit
*  I_VARIANTE =  "Variant in REA Master Data
*  I_FLG_PARTNER_VERSION = 'X' "Include Recycling Partner Version
*  I_FLG_PACKAGING_VERSION = 'X' "Include Packaging Versions
*  I_FLG_PRICELIST_VERSION = 'X' "Include Price List Versions

 IMPORTING
   RETURN =  "Return Parameters

TABLES
*  O_VERSION =  "Version Table
.



IMPORTING Parameters details for J_7L_ARTICLE_GET_VALIDITY

I_MATNR - Article Number

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

I_BUKRS - Company Code

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

I_LAND - Country of Article

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

I_VRKME - Sales Unit

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

I_VARIANTE - Variant in REA Master Data

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

I_FLG_PARTNER_VERSION - Include Recycling Partner Version

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

I_FLG_PACKAGING_VERSION - Include Packaging Versions

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

I_FLG_PRICELIST_VERSION - Include Price List Versions

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

EXPORTING Parameters details for J_7L_ARTICLE_GET_VALIDITY

RETURN - Return Parameters

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

TABLES Parameters details for J_7L_ARTICLE_GET_VALIDITY

O_VERSION - Version Table

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

Copy and paste ABAP code example for J_7L_ARTICLE_GET_VALIDITY 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:
lv_return  TYPE BAPIRET2, "   
lv_i_matnr  TYPE MATNR, "   
lt_o_version  TYPE STANDARD TABLE OF J_7LBAPI_VERSION, "   
lv_i_bukrs  TYPE BUKRS, "   
lv_i_land  TYPE LAND1, "   
lv_i_vrkme  TYPE VRKME, "   
lv_i_variante  TYPE J_7LVARIANTE, "   
lv_i_flg_partner_version  TYPE BOOLEAN, "   'X'
lv_i_flg_packaging_version  TYPE BOOLEAN, "   'X'
lv_i_flg_pricelist_version  TYPE BOOLEAN. "   'X'

  CALL FUNCTION 'J_7L_ARTICLE_GET_VALIDITY'  "REA Article Management: Validity Periods of Article
    EXPORTING
         I_MATNR = lv_i_matnr
         I_BUKRS = lv_i_bukrs
         I_LAND = lv_i_land
         I_VRKME = lv_i_vrkme
         I_VARIANTE = lv_i_variante
         I_FLG_PARTNER_VERSION = lv_i_flg_partner_version
         I_FLG_PACKAGING_VERSION = lv_i_flg_packaging_version
         I_FLG_PRICELIST_VERSION = lv_i_flg_pricelist_version
    IMPORTING
         RETURN = lv_return
    TABLES
         O_VERSION = lt_o_version
. " J_7L_ARTICLE_GET_VALIDITY




ABAP code using 7.40 inline data declarations to call FM J_7L_ARTICLE_GET_VALIDITY

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_partner_version) = 'X'.
 
DATA(ld_i_flg_packaging_version) = 'X'.
 
DATA(ld_i_flg_pricelist_version) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!