SAP LAYOUT_AREA_ITEMS_DLINKS_READ Function Module for NOTRANSL: Lesen Verknüpfungen von Dokumenten zu Layoutbereichspositionen

Search SAP Function Modules

LAYOUT_AREA_ITEMS_DLINKS_READ is a standard layout area items dlinks read 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: Lesen Verknüpfungen von Dokumenten zu Layoutbereichspositionen 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 layout area items dlinks read FM, simply by entering the name LAYOUT_AREA_ITEMS_DLINKS_READ into the relevant SAP transaction such as SE37 or SE38.

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

Function LAYOUT_AREA_ITEMS_DLINKS_READ 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 'LAYOUT_AREA_ITEMS_DLINKS_READ'"NOTRANSL: Lesen Verknüpfungen von Dokumenten zu Layoutbereichspositionen
  EXPORTING
   PI_LAYOUT =  "Layout
*  PI_AREA =  "Layout area number
*  PI_ITEM =  "Identifier for layout area item
*  PI_NO_BUFFERING = ' ' "Checkbox

TABLES
   PE_T_DLINK =  "Product Catalog: Table Links Documents - Layout Objects

EXCEPTIONS
   LAYOUT_NOT_FOUND = 1    AREA_NOT_FOUND = 2    ITEM_NOT_FOUND = 3    WRONG_CALL = 4    INTERNAL_ERROR = 5 

.

IMPORTING Parameters details for LAYOUT_AREA_ITEMS_DLINKS_READ

PI_LAYOUT - Layout

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

PI_AREA - Layout area number

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

PI_ITEM - Identifier for layout area item

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

PI_NO_BUFFERING - Checkbox

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

TABLES Parameters details for LAYOUT_AREA_ITEMS_DLINKS_READ

PE_T_DLINK - Product Catalog: Table Links Documents - Layout Objects

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

EXCEPTIONS details

LAYOUT_NOT_FOUND - Layout Not Found

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

AREA_NOT_FOUND - Layout area not found

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

ITEM_NOT_FOUND -

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

WRONG_CALL -

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

INTERNAL_ERROR -

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

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

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