SAP OO_ATTRIBUTE_DISPLAY Function Module for Display Attribute
OO_ATTRIBUTE_DISPLAY is a standard oo attribute display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Attribute 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 oo attribute display FM, simply by entering the name OO_ATTRIBUTE_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEOD
Program Name: SAPLSEOD
Main Program: SAPLSEOD
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OO_ATTRIBUTE_DISPLAY 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 'OO_ATTRIBUTE_DISPLAY'"Display Attribute.
EXPORTING
ATTRIBUTE = "
* WITHOUT_NAVIGATION = SEOX_FALSE "
EXCEPTIONS
NOT_EXISTING = 1
IMPORTING Parameters details for OO_ATTRIBUTE_DISPLAY
ATTRIBUTE -
Data type: SEOCMPKEYOptional: No
Call by Reference: Yes
WITHOUT_NAVIGATION -
Data type: SEOX_BOOLEANDefault: SEOX_FALSE
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_EXISTING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OO_ATTRIBUTE_DISPLAY 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_attribute | TYPE SEOCMPKEY, " | |||
| lv_not_existing | TYPE SEOCMPKEY, " | |||
| lv_without_navigation | TYPE SEOX_BOOLEAN. " SEOX_FALSE |
|   CALL FUNCTION 'OO_ATTRIBUTE_DISPLAY' "Display Attribute |
| EXPORTING | ||
| ATTRIBUTE | = lv_attribute | |
| WITHOUT_NAVIGATION | = lv_without_navigation | |
| EXCEPTIONS | ||
| NOT_EXISTING = 1 | ||
| . " OO_ATTRIBUTE_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM OO_ATTRIBUTE_DISPLAY
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_without_navigation) | = SEOX_FALSE. | |||
Search for further information about these or an SAP related objects