SAP ARTICLES_LAYOUT_AREA_GET Function Module for NOTRANSL: Zu den Materialien werden die Layoutbereiche gelesen

Search SAP Function Modules

ARTICLES_LAYOUT_AREA_GET is a standard articles layout area get 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: Zu den Materialien werden die Layoutbereiche gelesen 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 articles layout area get FM, simply by entering the name ARTICLES_LAYOUT_AREA_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: WBBR
Program Name: SAPLWBBR
Main Program: SAPLWBBR
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ARTICLES_LAYOUT_AREA_GET 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 'ARTICLES_LAYOUT_AREA_GET'"NOTRANSL: Zu den Materialien werden die Layoutbereiche gelesen
  EXPORTING
   PI_I_STORE =  "Assortment Owners
*  PI_LAYVR =  "Layout
*  PI_ART_DEL = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  PI_SORT_BY_DEPARTMENT = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  PI_SORT = ' ' "Sort

TABLES
   PE_T_ARTNR =  "Materials

EXCEPTIONS
   NO_STORE_DATA = 1    NO_DEPARTMENT_DATA = 2 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLWBBR_001 Sort Modification for Materials in the Assortment List

IMPORTING Parameters details for ARTICLES_LAYOUT_AREA_GET

PI_I_STORE - Assortment Owners

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

PI_LAYVR - Layout

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

PI_ART_DEL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: WDL_FLAG-XFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_SORT_BY_DEPARTMENT - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: WDL_FLAG-XFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_SORT - Sort

Data type: WDL_FLAG-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ARTICLES_LAYOUT_AREA_GET

PE_T_ARTNR - Materials

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

EXCEPTIONS details

NO_STORE_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NO_DEPARTMENT_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

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

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