J_7L_GET_PACKAGING_VALIDITY SAP Function module - REA Packing Administration: Validity Periods of Packing

J_7L_GET_PACKAGING_VALIDITY is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name J_7L_GET_PACKAGING_VALIDITY into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: J7LPACK
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM J_7L_GET_PACKAGING_VALIDITY - J 7L GET PACKAGING VALIDITY

CALL FUNCTION 'J_7L_GET_PACKAGING_VALIDITY' "REA Packing Administration: Validity Periods of Packing
  EXPORTING
    i_vrpnr =                   " j_7lvrp       Packaging Number
*   i_variante =                " j_7lvariante
*   i_flg_partner_version = 'X'  " boolean      Include Recycling Partner Version
*   i_flg_fraction_version = 'X'  " boolean     Include Packing Versions
*   i_flg_pricelist_version = 'X'  " boolean    Include Price List Versions
* TABLES
*   o_version =                 " j_7lbapi_version  Version Table
    .  "  J_7L_GET_PACKAGING_VALIDITY

ABAP code example for Function Module J_7L_GET_PACKAGING_VALIDITY

The ABAP code below is a full code listing to execute function module J_7L_GET_PACKAGING_VALIDITY including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_o_version  
 
 TYPE STANDARD TABLE OF J_7LBAPI_VERSION,"TABLES PARAM
wa_o_version
 
 LIKE LINE OF it_o_version
.


DATA(ld_i_vrpnr) = 'Check type of data required'.

DATA(ld_i_variante) = 'Check type of data required'.

DATA(ld_i_flg_partner_version) = 'Check type of data required'.

DATA(ld_i_flg_fraction_version) = 'Check type of data required'.

DATA(ld_i_flg_pricelist_version) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_o_version to it_o_version.
.

CALL FUNCTION 'J_7L_GET_PACKAGING_VALIDITY'
  EXPORTING
    i_vrpnr =                    ld_i_vrpnr
*   i_variante =                 ld_i_variante
*   i_flg_partner_version =      ld_i_flg_partner_version
*   i_flg_fraction_version =     ld_i_flg_fraction_version
*   i_flg_pricelist_version =    ld_i_flg_pricelist_version
* TABLES
*   o_version =                  it_o_version
    .  "  J_7L_GET_PACKAGING_VALIDITY

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_i_vrpnr
 
 TYPE J_7LVRP ,
it_o_version
 
 TYPE STANDARD TABLE OF J_7LBAPI_VERSION ,
wa_o_version
 
 LIKE LINE OF it_o_version,
ld_i_variante
 
 TYPE J_7LVARIANTE ,
ld_i_flg_partner_version
 
 TYPE BOOLEAN ,
ld_i_flg_fraction_version
 
 TYPE BOOLEAN ,
ld_i_flg_pricelist_version
 
 TYPE BOOLEAN .


ld_i_vrpnr = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_o_version to it_o_version.
ld_i_variante = 'Check type of data required'.
ld_i_flg_partner_version = 'Check type of data required'.
ld_i_flg_fraction_version = 'Check type of data required'.
ld_i_flg_pricelist_version = 'Check type of data required'.