Hi all,
I am trying to open the attached email file using GUI frontend services and calling FM : BDS_OBJECT_DISPLAY_INTERN.
Here is a code:
w_objkey = wa_mtratch_disp-matter.
wa_signature-doc_count = 1.
wa_signature-doc_id = wa_loio-class.
wa_signature-doc_id+10 = wa_loio-objid.
APPEND wa_signature TO it_signature.
call method CL_GUI_FRONTEND_SERVICES=>GET_TEMP_DIRECTORY
changing TEMP_DIR = W_TMP_FOLDER
exceptions CNTL_ERROR = 1
ERROR_NO_GUI = 2
NOT_SUPPORTED_BY_GUI = 3
OTHERS = 4
.
if SY-SUBRC <> 0.
* message ID SY-MSGID type SY-MSGTY number SY-MSGNO
* with SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
else.
endif.
*TO PASS THE LOGICAL SYSTEM AND SY-MANDT
*data: w_logical_sys type TBDLS-LOGSYS.
*
* CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
* IMPORTING
* OWN_LOGICAL_SYSTEM = w_logical_sys
** EXCEPTIONS
** OWN_LOGICAL_SYSTEM_NOT_DEFINED = 1
** OTHERS = 2
* .
* IF SY-SUBRC <> 0.
** MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
** WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
* ENDIF.
CALL FUNCTION 'BDS_OBJECT_DISPLAY_INTERN'
EXPORTING
* logical_system = w_logical_sys
classname = w_classname "'/INTALEC/M' " changed by madhuri 20.11.2013 ff-1062
classtype = w_classtype "'BO' " changed by madhuri 20.11.2013 ff-1062
client = sy-mandt
object_key = w_objkey
TABLES
signature = it_signature
EXCEPTIONS
error_kpro = 1
internal_error = 2
OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
I have declared all the variables globally; still getting dump of system_pointer_pending:
| Short Text |
| Use of local result variables in a Control/Automation call. |
| What happened? |
| Error in the ABAP Application Program |
| The current ABAP program "/zzz/CLIENT_AND_MAT_V2" had to be terminated |
| because it has |
| come across a statement that unfortunately cannot be executed. |
| What can you do? |
| Note down which actions and inputs caused the error. |
| To process the problem further, contact you SAP system |
| administrator. |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
| Error analysis |
| The use of a local variable to receive a return value in a call to a |
| control or automation server is not permitted. |
| For performance reasons calls to front-end components, such as controls, |
| are collected in a queue and are only transferred to the front-end for |
| processing at the so called flush. The processing of these calls to the |
| front-end takes place asynchronously to the calls in the ABAP code. |
| When local variables are used in calls to controls to receive return |
| values (for example, the ID of the selected node of a tree) it is |
| possible that the local variable will no longer exist at the time of the |
| flush. This makes the transfer of the return value to the variable |
| impossible. |
| It must be assumed that without the return value the processing cannot |
| be correctly carried out. As a precaution, further processing was |
| interrupted. |
| Check your application for local variables that should be used for the |
| return values of control/automation calls. |
| The variable used here points to the area "stack area" to the data object |
| "\PROGRAM=/zzz/CLIENT_AND_MAT_V2\CLASS=LCL_APPLICATION\METHOD=HANDLE_CHECKB |
| OX_CHANGE\DATA=???". |