SAP PD_OBJECT_TEXT_GET Function Module for Merge object texts from internal text buffer
PD_OBJECT_TEXT_GET is a standard pd object text 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 Merge object texts from internal text buffer 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 object text get FM, simply by entering the name PD_OBJECT_TEXT_GET 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_OBJECT_TEXT_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 'PD_OBJECT_TEXT_GET'"Merge object texts from internal text buffer.
EXPORTING
OBJECT_KEY = "Graphical object key
* TEXT_MASK = '*' "Mask: which texts should be formatted
* DISPLAY_ID = "Data set ID
* STATUSES = '1' "Status vector
* BEGIN_DATE = SY-DATUM "Evaluation start
* END_DATE = SY-DATUM "Evaluation end
* DATA_STATUS = '1' "Data status
IMPORTING
DETAIL = "Object text for detail screen
OVERVIEW = "Object text for overview screen
TABLES
* DISPLAY = "Info text for info window
IMPORTING Parameters details for PD_OBJECT_TEXT_GET
OBJECT_KEY - Graphical object key
Data type: GSUOBJC-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
TEXT_MASK - Mask: which texts should be formatted
Data type:Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DISPLAY_ID - Data set ID
Data type: T77GI-DISPLAYIDOptional: Yes
Call by Reference: No ( called with pass by value option)
STATUSES - Status vector
Data type: PCHDY-SVECTDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
BEGIN_DATE - Evaluation start
Data type: PCHDY-BEGDADefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
END_DATE - Evaluation end
Data type: PCHDY-ENDDADefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
DATA_STATUS - Data status
Data type: PCHDY-ISTATDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PD_OBJECT_TEXT_GET
DETAIL - Object text for detail screen
Data type: GSUOBJC-DISPTEXTOptional: No
Call by Reference: No ( called with pass by value option)
OVERVIEW - Object text for overview screen
Data type: GSUOBJC-AUTFTEXTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PD_OBJECT_TEXT_GET
DISPLAY - Info text for info window
Data type: GSUDISPOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PD_OBJECT_TEXT_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.| DATA: | ||||
| lv_detail | TYPE GSUOBJC-DISPTEXT, " | |||
| lt_display | TYPE STANDARD TABLE OF GSUDISP, " | |||
| lv_object_key | TYPE GSUOBJC-OBJECT, " | |||
| lv_overview | TYPE GSUOBJC-AUTFTEXT, " | |||
| lv_text_mask | TYPE GSUOBJC, " '*' | |||
| lv_display_id | TYPE T77GI-DISPLAYID, " | |||
| lv_statuses | TYPE PCHDY-SVECT, " '1' | |||
| lv_begin_date | TYPE PCHDY-BEGDA, " SY-DATUM | |||
| lv_end_date | TYPE PCHDY-ENDDA, " SY-DATUM | |||
| lv_data_status | TYPE PCHDY-ISTAT. " '1' |
| CALL FUNCTION 'PD_OBJECT_TEXT_GET' "Merge object texts from internal text buffer |
| EXPORTING | ||
| OBJECT_KEY | = lv_object_key | |
| TEXT_MASK | = lv_text_mask | |
| DISPLAY_ID | = lv_display_id | |
| STATUSES | = lv_statuses | |
| BEGIN_DATE | = lv_begin_date | |
| END_DATE | = lv_end_date | |
| DATA_STATUS | = lv_data_status | |
| IMPORTING | ||
| DETAIL | = lv_detail | |
| OVERVIEW | = lv_overview | |
| TABLES | ||
| DISPLAY | = lt_display | |
| . " PD_OBJECT_TEXT_GET | ||
ABAP code using 7.40 inline data declarations to call FM PD_OBJECT_TEXT_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.| "SELECT single DISPTEXT FROM GSUOBJC INTO @DATA(ld_detail). | ||||
| "SELECT single OBJECT FROM GSUOBJC INTO @DATA(ld_object_key). | ||||
| "SELECT single AUTFTEXT FROM GSUOBJC INTO @DATA(ld_overview). | ||||
| DATA(ld_text_mask) | = '*'. | |||
| "SELECT single DISPLAYID FROM T77GI INTO @DATA(ld_display_id). | ||||
| "SELECT single SVECT FROM PCHDY INTO @DATA(ld_statuses). | ||||
| DATA(ld_statuses) | = '1'. | |||
| "SELECT single BEGDA FROM PCHDY INTO @DATA(ld_begin_date). | ||||
| DATA(ld_begin_date) | = SY-DATUM. | |||
| "SELECT single ENDDA FROM PCHDY INTO @DATA(ld_end_date). | ||||
| DATA(ld_end_date) | = SY-DATUM. | |||
| "SELECT single ISTAT FROM PCHDY INTO @DATA(ld_data_status). | ||||
| DATA(ld_data_status) | = '1'. | |||
Search for further information about these or an SAP related objects