SAP PD_GRAPHICAL_OBJECT_DEFINE Function Module for Convert object with relationship to graphical format
PD_GRAPHICAL_OBJECT_DEFINE is a standard pd graphical object define SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert object with relationship to graphical format 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 pd graphical object define FM, simply by entering the name PD_GRAPHICAL_OBJECT_DEFINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: PDSU
Program Name: SAPLPDSU
Main Program:
Appliation area: H
Release date: 23-Jun-1995
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PD_GRAPHICAL_OBJECT_DEFINE 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 'PD_GRAPHICAL_OBJECT_DEFINE'"Convert object with relationship to graphical format.
EXPORTING
OBJECT = "Object structure
ENTRY = "Relationship structure
* PUP = "Pointer on another parent object
IMPORTING
GRAPH_OBJECT = "Field string for graphical object definition
IMPORTING Parameters details for PD_GRAPHICAL_OBJECT_DEFINE
OBJECT - Object structure
Data type: OBJECOptional: No
Call by Reference: No ( called with pass by value option)
ENTRY - Relationship structure
Data type: STRUCOptional: No
Call by Reference: No ( called with pass by value option)
PUP - Pointer on another parent object
Data type: STRUC-PUPOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PD_GRAPHICAL_OBJECT_DEFINE
GRAPH_OBJECT - Field string for graphical object definition
Data type: GSUOBJCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PD_GRAPHICAL_OBJECT_DEFINE 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_object | TYPE OBJEC, " | |||
| lv_graph_object | TYPE GSUOBJC, " | |||
| lv_entry | TYPE STRUC, " | |||
| lv_pup | TYPE STRUC-PUP. " |
|   CALL FUNCTION 'PD_GRAPHICAL_OBJECT_DEFINE' "Convert object with relationship to graphical format |
| EXPORTING | ||
| OBJECT | = lv_object | |
| ENTRY | = lv_entry | |
| PUP | = lv_pup | |
| IMPORTING | ||
| GRAPH_OBJECT | = lv_graph_object | |
| . " PD_GRAPHICAL_OBJECT_DEFINE | ||
ABAP code using 7.40 inline data declarations to call FM PD_GRAPHICAL_OBJECT_DEFINE
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.| "SELECT single PUP FROM STRUC INTO @DATA(ld_pup). | ||||
Search for further information about these or an SAP related objects