Landscape Verification returns short dump

Dear All,
I'm trying to run transaction LVSM -Landscape Verification for SolMan- but a short dump is appearing. We recently updated solman from ehp1 SP 19 to SP 27 (latest available) and installed Landscape Verification 1.0
Runtime error ASSERTION_FAILED while running transaction LVSM
the short dump is in the function module SMSY_BASIC_GET_DATA
in the following check:
* Security check ======================================================
DATA: lv_secu_violation_occured TYPE c VALUE '',
        lv_secu_exception_disabled TYPE c.
PERFORM check_security TABLES select_condition
                         USING tabname
                                updatemode
                                version
                                systemtype
                       CHANGING lv_secu_violation_occured.
PERFORM get_smsy_option_value USING 'SCUEXC_DIS'
                             CHANGING lv_secu_exception_disabled.
IF lv_secu_violation_occured = smsy4_c_true AND
     lv_secu_exception_disabled = smsy4_c_false.
*   Throw exception SECURITY_VIOLATION
" >> 23.12.10 D049273
" Don't throw an exception here, because user of this FM don't expect/handle a
" security exception. This leads to errors/ program behaviour which blurs
" the root cause of the error. Instead we dump because security violation here
" is a realy unexpected case.
*    RAISE security_violation.
    ASSERT 0 = 1.
ENDIF.
* Security check ======================================================
Any help will be really appreciated.
Best Regards,
Erick Acosta

Yes, I have the role SAP_SMSY_LV_ALL and SAP_SMSY_ALL according to config. guide.
I've updated ST-LV to SP 2 and now the dump is not longer happening.
Thanks anyway!
BR,
Erick Acosta

Similar Messages

Dynnamic Field Symbol returning short dump ASSIGN_TYPE_CONFLICT

Hi everyone,
I have a RFC FM and make a dynamic access via SYMBOL FIELD, declared as ANY TABLE. The problem is that sometimes I can get a structure instead of a table and then the error occurs. How do I handle this error if the check IS ASSIGN not work? How do I capture and return an error message?
I tryed this:
FIELD-SYMBOLS: <fs_tabela> TYPE ANY TABLE.
     TRY.
                 ASSIGN (st_b2b_text-tabname) TO <fs_tabela>.   <<<<----
DUMP HERE!
              CATCH cx_root INTO v_erro.
                v_text = v_erro->get_text( ).
                MOVE v_text TO st_return-message.
                APPEND st_return TO t_return.
                PERFORM f_return_error_pi USING event.
      ENDTRY.
            IF <fs_tabela> IS ASSIGNED.
              CONCATENATE 'S' st_b2b_text-tabname INTO vl_wkarea.
              CONDENSE vl_wkarea NO-GAPS.
              ASSIGN (vl_wkarea) TO <fs_wkarea>.
              IF <fs_wkarea> IS ASSIGNED.
                LOOP AT <fs_tabela> ASSIGNING <fs_wkarea>.
                  ASSIGN COMPONENT c_posnr
                  OF STRUCTURE <fs_wkarea> TO <fs_posnr>.
Does anyone have any tips?
Tnks,
Marco Antonio
from Brazil

I solved with this test that I did:
TABLES: vbak.
TYPES: BEGIN OF ty_ctrlimo,
         equnr          TYPE equnr,
         anln1          TYPE anln1,
         anln2          TYPE anln2,
         aufnr          TYPE aufnr,
         bukrs          TYPE bukrs,
         zanln1_andam       TYPE anln1,
         zanln2_andam       TYPE anln2,
       END   OF ty_ctrlimo.
DATA: estrutura TYPE ty_ctrlimo,
      tabela    TYPE STANDARD TABLE OF ty_ctrlimo
                     INITIAL SIZE 0 WITH HEADER LINE,
      tabela2   TYPE TABLE OF ty_ctrlimo,
      variavel TYPE char30.
DATA: is_tabela.
Evento: START-OF-SELECTION                                       ***
START-OF-SELECTION.
BREAK-POINT.
PERFORM f_check_is_tabela USING 'TABELA' CHANGING is_tabela.
WRITE: / '1 ', 'TABELA =', is_tabela.
SKIP 1.
PERFORM f_check_is_tabela USING 'TABELA2' CHANGING is_tabela.
WRITE: / '2 ', 'TABELA2 =', is_tabela.
SKIP 1.
PERFORM f_check_is_tabela USING 'ESTRUTURA' CHANGING is_tabela.
WRITE: / '3 ', 'ESTRUTURA =', is_tabela.
SKIP 1.
PERFORM f_check_is_tabela USING 'VARIAVEL' CHANGING is_tabela.
WRITE: / '4 ', 'VARIAVEL =', is_tabela.
SKIP 1.
PERFORM f_check_is_tabela USING 'VBAK' CHANGING is_tabela.
WRITE: / '5 ', 'VBAK =', is_tabela.
SKIP 1.
*&      Form F_CHECK_IS_TABELA
FORM f_check_is_tabela USING value(p_nome_tabela_estrutura)
                     CHANGING p_is_tabela.
FIELD-SYMBOLS <check> TYPE ANY.
DATA: lcls_strdscr TYPE REF TO cl_abap_structdescr,
        lcls_typdscr TYPE REF TO cl_abap_typedescr.
CLEAR: p_is_tabela.
ASSIGN (p_nome_tabela_estrutura) TO <check>.
lcls_typdscr ?= cl_abap_structdescr=>describe_by_data( <check> ).
IF lcls_typdscr->type_kind = cl_abap_structdescr=>typekind_table.
    p_is_tabela = cl_abap_structdescr=>true.
ENDIF.
WRITE: / 'tipo data: ', lcls_typdscr->type_kind.
ENDFORM.                    " F_CHECK_IS_TABELA

Transport with return code 12 ,short dump with 'DBIF_RSQL_SQL_ERROR'

Dear All,
My trasnport contains infoprovider. DTP,transpformations, character realtionships , aggregation levels ,web templates, programs.
I got a transport failed with Return code 12, and it is showing message :
Program terminated (job: RDDEXECL, no.: 06031600)
See job log
Execution of programs after import (XPRA)
End date and time : 20101026060421
Ended with return code: ===> 12 <===
I have short dump with 'DBIF_RSQL_SQL_ERROR' exception 'CX_SY_OPEN_SQL_DB'.
in how to correct the error :
below is the detials.
Database error text........: "ORA-01578: ORACLE data block corrupted (file #
211, block # 79950)#ORA-01110: data file 211:
'/oracle/RBW/sapdata15/xbw_188/xbw.data188'#ORA-26040: Data block was loaded
using the NOLOGGING option"
did someone has the same problem .
Help is really appreciated.
Regards
Veera

I am afraid you will need to esclate this to BASIS team.. seems some issue with database

Display Data Flow - Short Dump

Hi all,
When i select display data flow of any cube...it is going for a short dump.
I have searched for the answer in previous Forum questions. I could find only for previous BW versions but not for for BI7.
Could you please let me know the solution for this issue.
Thanks & Regards,
Eswari

Hi All,
Thank you very much for all of your responces.....
I am working on Support Package 10.
Here is the detailed description of the short dump.
Short text
    The current application triggered a termination with a short dump.
What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
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
    Short text of error message:
    GP: Control Framework returned an error; contact system administrator
    Long text of error message:
     Diagnosis
         The Graphical Framework is based on the basis technology known as
         the Control Framework. A method in the Control Framework returned
         an error.
     Procedure
         It probably involves a programming error. You should contact your
         system administrator.
     Procedure for System Administration
         Check the programming of the graphics proxy especially for the
         parameters that were sent and, if necessary, correct your program.
    Technical information about the message:
    Message class....... "APPLG"
    Number.............. 229
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MESSAGE_TYPE_X" " "
    "CL_AWB_OBJECT_NET_SAPGUI======CP" or "CL_AWB_OBJECT_NET_SAPGUI======CM005"
    "PBO"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
   4. Details about the conditions under which the error occurred or which
   actions and input led to the error.
Thanks,
Eswari.

Short Dump generating reports of EWA

Hi Experts,
I get the short dump MESSAGE_TYPE_X when I tried to see the Ewa report?
Any Idea?
Thanks in advance.

Hi,
Mi ST 400 level is 17.
Here is mi dump:
Err.tmpo.ejec.         MESSAGE_TYPE_X
Fecha y hora           10.08.2009 09:37:50
Texto breve
The current application triggered a termination with a short dump.
¿Qué ha sucedido?
The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
Anál.errores
Short text of error message:
    La creación de evento para la sesión EA0000000000881 ha fallado
Long text of error message:
     Diagnóstico
La creación de un evento ha fallado.
     Actividades en el sistema
         La transacción actual se cancela.
     Procedimiento
Procedimiento para la gestión del sistema
         El problema puede estar en el rango de números DSVASEVENT.
         Verifique si el intervalo "01" está creado y si tiene números
         libres. Notifique los resultados de esta exploración a SAP.
Technical information about the message:
    Message class....... "DSVAS"
    Number.............. 093
    Variable 1.......... "EA0000000000881"
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Posición desencadenante de error tiempo ejecución
    Programa                                SAPLDSVAS_RPGEN
    Include                                 LDSVAS_RPGENU03
    Línea                                   672
    Tp.módulo                               (FUNCTION)
    Nombre módulo                           DSVAS_RPGEN_REPORT_GET_DATA
Detalle código fuente
Lín.      Txt.fte.
642        lf_chapno_old = 0.
643      * Fehlende Kapitelnummern verdichten
644        LOOP AT report_structure.
645          AT NEW chapter.
646            IF lf_chapno_old <> report_structure-chapter.
647              lf_chapno_old = report_structure-chapter.
648              ADD 1 TO lf_chapno.
649            ENDIF.
650          ENDAT.
651          report_structure-chapter = lf_chapno.
652          MODIFY report_structure.
653        ENDLOOP.
654
655
656      * Ereignis "Reportgeneriert" vermerken
657        DATA: ls_dsvassessinstid TYPE dsvassessinstid,
658              lf_event_parameter TYPE dsvasevent-event_parameter.
659      * AH 'SL' wird durch Aufrufer erst spaeter ausgeloest
660        if lf_iCount = 0 or sy-batch is initial.
661          ls_dsvassessinstid-sessitype = sessitype.
662        ls_dsvassessinstid-sessno    = sessno.
663        lf_event_parameter           = ls_dsvassessinstid.
664        CALL FUNCTION 'DSVAS_EVENT_RAISE'
665             EXPORTING
666                  pf_event_type      = 'SL'
667                  pf_event_parameter = lf_event_parameter
668             EXCEPTIONS
669                  failed             = 1
670                  OTHERS             = 2.
671        IF sy-subrc <> 0.
>>>>>          MESSAGE x093(dsvas) WITH ls_dsvassessinstid.
673      *     Ereigniserzeugung für Sitzung &1 fehlgeschlagen
674          ENDIF.
675        endif.
676      * AH
677
678        CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
679             EXPORTING
680                  TEXT = space.
681      ENDFUNCTION.
Thanks in advance!

Short dump "Time limit exceeded" when searching for Business Transactions

Hello Experts,
We migrated from SAP CRM 5.2 to SAP CRM 7.0. After migration, our business transaction search (quotation, sales order, service order, contract etc) ends with the short dump "Time limit exceeded" in class CL_CRM_REPORT_ACC_DYNAMIC, method DATABASE_ACCESS. The select query is triggered from line 5 of this method.
Number of Records:
CRMD_ORDERADM_H: 5,115,675
CRMD_ORDER_INDEX: 74,615,914
We have done these so far, but the performance is still either poor or times out.
1. DB team checked the ORACLE parameters and confirmed they are fine. They also checked the health of indices in table CRMD_ORDER_INDEX and indices are healthy
2. Created additional indices on CRMD_ORDERADM_H and CRMD_ORDER_INDEX. After the creation of indices, some of the searches(without any criteria) work. But it takes more than a minute to fetch 1 or 2 records
3. An ST05 trace confirmed that the selection on CRMD_ORDER_INDEX takes the most time. It takes about 103 seconds to fetch 2 records (max hits + 1)
4. If we specify search parameters, say for example a date or status, then again we get a short dump with the message "Time limit exceeded".
5. Observed that only if a matching index is available for the WHERE clause, the results are returned (albeit slowly). In the absence of an index, we get the dump.
6. Searched for notes and there are no notes that could help us.
Any idea what is causing this issue and what we can do to resolve this?
Regards,
Bala

Hi Michael,
Thanks. Yes we considered the note 1527039. None of the three scenarios mentioned in the note helped us. But we ran CRM_INDEX_REBUILD to check if the table CRMD_ORDER_INDEX had a problem. That did not help us either.
The business users told us that they mostly search using the date fields or Object ID. We did not have any problem with search by Object ID. So we created additional indices to support search using the date fields.
Regards,
Bala

Short Dump while execuition of DTP.

Hi,
I got short dump while execuiting the DTP.
Error messages shows as below:
1.The database returned a value containing an error
2.An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause
3.Exception CX_SY_NO_HANDLER logged
Could you please help us in solving this issue.
Regards,
Suman.

hi,
an error like this comes usually in 2 cases
1) not enough resources are available to carry out loads.in this case increase no of parallel processes to 2-3 in dtp setting,check the option get delta request by request(if its a delta load) and decrease packet size to 10000(from default 50000)
2)fileld to field assignment is not proper:
u need to check if there is any source field with lenth lets say 5 ans is getting assisgned to a target field length lets say 4.in this case dumps will come
please check the error message in st22 and here you can also check the termination point.please check in option Chosen variables /contents of system fileds where you can get temp values at point of termination.here you can pinpoint values at which prog is throwing dumps.

Short dump while loading master data (0material_attr).

Hi,
I am experiencing a short dump while loading 0matrial_attr from R/3.
Name of the runtime error :
DBIF_RSQL_SQL_ERROR
program is generating exception at this point.
***Try to insert the records into the ODS table
INSERT /BIC/B0002905000 FROM TABLE L_T_DATA.
pls help me.

Hi,
I am sure I am looking at the proper dump.
the code I have pasted is the standard code.. which I get to see in the dump analysis.
******************************dump analysis*********************************
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure "INSERT_ODS"
"(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The exception must either be prevented, caught within the procedure
"INSERT_ODS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0002905000 ]"
Please check the entries in the system log (Transaction SM21).
system log in SM 21 is below**************
After the attempt to access a database table the database system has
returned an error code which indicates that the operation concerned
could not be performed successfully.

ECC 6.0 bar chart short dump

We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
     if l_guisupp_data_as_string = abap_true.
     .....code not executed because the variable = abap_false.
     else.
     .....raise create_error.    <<<<< this is where the dump occurs.
     endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM

We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
     if l_guisupp_data_as_string = abap_true.
     .....code not executed because the variable = abap_false.
     else.
     .....raise create_error.    <<<<< this is where the dump occurs.
     endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM
I just installed the latest patch on the SAPgui, so I am now running:
Release: 710 Final Release
File Version: 7100.2.8.1039
Build: 983952
Patch Level: 8
But I am still getting the short dump. I have done extensive searches of SAP Help, OSS notes, and this and other forums (even just looking up the problem on "google") but can't seem to find anything that applies to this scenario. I'm not very familiar with the methods in cl_gui_frontend_services, so if anyone can give me a pointer of where else I can look, I would greatly appreciate it!
I also have edited the Subject line to be more informative about the problem

Short dump with BAPI_ACC_DOCUMENT_POST

Dear All,
When I try to use BAPI "BAPI_ACC_DOCUMENT_POST" for F-02 posting, I get the following short dump:
"Syntax error in program SAPLACC9".
"The data object GS_ACCIT does not have a component called BAPI_PARA"
Please suggest me how can this error be removed.
Regards,
Kanupriya

Hi Suneel,
Please look at the code below:
LOOP AT it_upload_rec.
    header-bus_act = 'RFBU'.
    header-doc_date = it_upload_rec-bldat.
    header-pstng_date = it_upload_rec-budat.               header-header_txt = 'F-02 Posting'.
    header-comp_code = 'PL10'.
    header-doc_type = 'SA'.
    header-username = sy-uname.
    APPEND header.
    CLEAR header.
    account_gl-itemno_acc = '1'.
    account_gl-gl_account = it_upload_rec-account1.
    APPEND account_gl.
    CLEAR account_gl.
    account_payable-itemno_acc = '2'.
    account_payable-vendor_no = it_upload_rec-account2.
    APPEND account_payable.
    CLEAR account_payable.
    currency_amount-itemno_acc = '1'.
    currency_amount-currency = 'INR'.
    currency_amount-amt_doccur = it_upload_rec-amount.
    APPEND currency_amount.
    CLEAR currency_amount.
ENDLOOP.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
    EXPORTING
      documentheader          = header
*   CUSTOMERCPD             =
*   CONTRACTHEADER          =
   IMPORTING
obj_type = gv_obj_type
obj_key = gv_obj_key
obj_sys = gv_obj_sys
    TABLES
     accountgl               = account_gl
   ACCOUNTRECEIVABLE       =
     accountpayable          = account_payable
*   ACCOUNTTAX              =
      currencyamount          = currency_amount
*   CRITERIA                =
*   VALUEFIELD              =
*   EXTENSION1              =
    return                  = it_return
*   PAYMENTCARD             =
*   CONTRACTITEM            =
*   EXTENSION2              =
*   REALESTATE              =
Regards,
Kanupriya

Short dump Error in BAPI_BUS2054_SET_STATUS

I am trying to set status of wbs element and have the following sequence of calls based on the
Error in BAPI_BUS2054_SET_STATUS
CALL FUNCTION 'BAPI_PS_INITIALIZATION' .
CALL FUNCTION 'BAPI_PS_PRECOMMIT'
TABLES
et_return = it_bapiret.
CALL FUNCTION 'BAPI_BUS2054_SET_STATUS'
IMPORTING
return = l_return
TABLES
i_wbs_user_status = it_wbs_user_status
e_result = lt_e_result.
IF l_return-type EQ 'E'.
gv_flg_error = 'X'.
ENDIF.
CALL FUNCTION 'BAPI_PS_PRECOMMIT'
TABLES
et_return = it_bapiret.
READ TABLE it_bapiret INTO it_bapiret WITH KEY type = 'E'.
IF sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDIF.
I am still getting the short dump :
Error analysis
    Short text of error message:
    Precommit did not run successfully
Information on where terminated
    Termination occurred in the ABAP program "SAPLPS_BAPI" - in "CHK_PRECOMMIT".
    The main program was "RS_TESTFRAME_CALL ".
In the source code you have the termination point in line 24
    of the (Include) program "LPS_BAPIF01".
Any help to make this work is appreciated.

suzzie
you are always calling precommit after set_status.you should call only if set_status is successfull.
This is how we are calling for network status.
        call function 'BAPI_PS_INITIALIZATION'.
        call function 'BAPI_BUS2002_SET_STATUS'
          exporting
            number                   = network
          tables
            i_activity_system_status = it
            e_result                 = itet.
        read table itet into wa_itet with key message_type = 'E'.
        if sy-subrc ne 0.
          call function 'BAPI_PS_PRECOMMIT'
            tables
              et_return = etit.
          call function 'BAPI_TRANSACTION_COMMIT'
            exporting
              wait = 'X'.
        else.
         MOVE wa_itet-message_text TO wa_error_tab-message_text.
         wa_error_tab-key1 = network.
         wa_error_tab-key2 = wa_itet-objectkey+12(4).
         wa_error_tab-object_type = c_activity.
         APPEND wa_error_tab TO e_error_tab.
        endif.

Short dump Error during VM container communication between ABAP and JAVA.

Hello All,
Can anybody please help with resolving the following issue:
Short dump is displayed, when I try to insert CRM product (type: material) in the document (opportunity). This CRM product was created in CRM directly.
When I try to insert ECC migrated material, everything works fine.
Here is the details of dump:
Short text
    Error during VM container communication between ABAP and JAVA
Information on where terminated
    Termination occurred in the ABAP program "SAPLPRC_INT" - in "GET_PRICING_PROCEDURE_INFO".
    The main program was "SAPMHTTP ". In the source code you have the termination point in line 100 of the (Include) program "LPRC_INTF35".
Thank you!

hi Willie,
     this is the dump, and i have used the t-code sm52 . the VMC is not active.
|Short Text                                                                                        |
|    Error during VM Container communication between ABAP and JAVA.                                |
|What happened?                                                                                    |
|    The current program had to be terminated because of an                                        |
|    error when installing the R/3 System.                                                         |
|    Error in the RFC layer.                                                                       |
|What can you do?                                                                                  |
|    Note which actions and entries caused the error to occur.                                     |
|                                                                                                  |
|    Consult your SAP administrator.                                                               |
|                                                                                                  |
|    Using transaction ST22 for ABAP dump analysis, you can view, manage,                          |
|    and retain termination messages for longer periods.                                           |
|Error analysis                                                                                    |
|    An error has occurred in the RFC layer during communication between                           |
|    JAVA and the ABAP stack. This prevents data from being passed correctly                       |
|    between the two stacks.                                                                       |
|                                                                                                  |
|    Message    = TH_VMC_SERV_NOT_ACTIVE                                                           |
|    Return code = -1007                                                                           |
|    Pointer    = "000007DD348F6138"                                                               |
|How to correct the error                                                                          |
|    Check whether the VMC is active on your application server. To do this,                       |
|    run transaction SM52. If the VMC is not active, contact your SAP                              |
|    administrator.                                                                                |
Regards
Charles

Short Dump Error DBIF_DSQL2_SQL_ERROR

Hi All,
I am getting a Short dump error DBIF_DSQL2_SQL_ERROR when I try to selectively delete the contents of an infocube. Now, we have a custom program that does this selective deletion. I had no problem when I ran this program in Development system. But when I try to do the same in Testing system, I get a short dump error.
Additional info: We have DB2 for database.
Thanks,
Ashmith Roy

Hi All,
Thanks for your input. The exact error I am getting is in as follows:
Runtime Error          DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
An SQL error occurred when executing Native SQL.
Error "-199" occurred in the current database connection "DEFAULT".
How to correct the error
     Database error text........: "[IBM][CLI Driver][DB2] DSNT408I SQLCODE = -199,
      ERROR: ILLEGAL USE OF KEYWORD FETCH. TOKEN WAS EXPECTED DSNT418I SQLSTATE =
      42601 SQLSTATE RETURN CODE "
     Database error code .......: "-199"
     Triggering SQL statement...: "FETCH NEXT "
     Internal call code.........: "[DBDS/NEW DSQL]"
     Please check the entries in the system log (Transaction SM21).
Information on where terminated
The termination occurred in the ABAP program "GP41YKV36E6C2VFC36AKSJQXCD3" in
      "COUNT".
The termination occurred in line 0 of the source code of the (Include)
program " "
of the source code of program " " (when calling the editor 00).
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "COUNT" "(FORM)" but was not handled locally, not declared in the
RAISING clause of the procedure.
The procedure is in the program "GP41YKV36E6C2VFC36AKSJQXCD3 ". Its source code
starts in line 0
of the (Include) program "???".
So could you please advise as to how to correct the error?
Ashmith Roy

Short dump error with InfoSource

Hi All,
When i try to open Accounts Payable Infosource in BW production, It is returning with the short dump error ' Assertion was violated'.
R_AWBOBJ ->. may I know what is this error.
I created generic datasource in ECC DEV and replicated into BW DEV system, After that I created necessary infoobjects, infosource, transformations, ODS, DTP, InfoPackage and loaded data into it under Accounte Payable in BW DEV. Everything was fine, So I released every object into production successfully.
I asked our network guy to move them into production, When he try to move them they are returning with the errors. Which doesn't happen before. Is this anything effected with the existed AP infosource in production as i explained above error? But still these are not moved into production.I released generic datasource from ECC DEV to ECC PRD.
Data loading was stopped for Line Items DSO under Accounts Payable, Because of these process chains were failed.
Please let me know where i did wrong or what steps i have to follow further. We are on BI7.0 systems.
We recently installed our BI systems.
Please help me anyone ASAP, I appreciated any help.
Thanks,
Aparna.

HI,
If I can understand properly the infosource is the generated object from DSO begnining with 8*? updating AP DSO?
Or it is the self created infsource updating the AP DSO??
What I can understand is you already had a flow in production which was working fine.
Then you did some development inculding a new DSO...this new DSO contained some infoobject fields common with the already live AP DSO in production.
new DSO transport failed in production and becasue of which the data loads to the old AP DSO in production has stopped.
The issue could be that since the transport failed... these infoobjects are into incosistent state.
check these common infoobjects in prodution first.
All I can suggest is transport the DSO again production for AP DSO so that its in consistent state along with the infoobjects.
The infoobjects must be consistent for the DSO, generated data source and infosource to work properly.
Eeen if the infosource is generated one( 8*XXXXXX) transport the respective DSO again in production along with required infoobjects.
Transport the cutomized infosource as well if created.
Thanks
Ajeet

REGARDING ALV REPORT SHORT DUMP

hI ALL,
IAM GETTING FOR THE FOLLOWING CODE,
PLEASE WHY THE ERROR IN ECC 6.0
TABLES AND DATA DECLARATION.
*TABLES: mara,makt.",marc.
data syrepid like sy-repid.
data sydatum(10). " LIKE sy-datum.
data sypagno(3) type n.
WHEN USING MORE THAN ONE TABLE IN ALV WE NEEED TO DECLARE THE TYPE
GROUP (TYPE-POOLS--------->SLIS)
type-pools : slis.
INTERNAL TABLE DECLARATION.
INTERNAL TABLE TO HOLD THE VALUES FROM THE MARA TABLE
data: begin of t_mara occurs 0,
matnr like mara-matnr,
meins like mara-meins,
mtart like mara-mtart,
matkl like mara-matkl,
end of t_mara.
INTERNAL TABLE TO HOLD THE CONTENTS FROM THE EKKO TABLE
data : begin of t_marc occurs 0,
matnr like mara-matnr,
werks like marc-werks,
minbe like marc-minbe.
data: end of t_marc.
INTERNAL TABLE TO HOLD THE VALUES FROM MAKT TABLE.
data : begin of t_makt occurs 0,
matnr like mara-matnr,
maktx like makt-maktx,
spras like makt-spras,
end of t_makt.
INTERNAL TABLE WHICH ACTUALLY MERGES ALL THE OTHER INTERNAL TABLES.
data: begin of itab1 occurs 0,
matnr like mara-matnr,
meins like mara-meins,
maktx like makt-maktx,
spras like makt-spras,
werks like marc-werks,
minbe like marc-minbe,
end of itab1.
THE FOLLOWING DECLARATION IS USED FOR DEFINING THE FIELDCAT
AND THE LAYOUT FOR THE ALV.
HERE AS slis_t_fieldcat_alv IS A INTERNAL TABLE WITHOUT A HEADER LINE
WE EXPLICITELY DEFINE AN INTERNAL TABLE OF THE SAME STRUCTURE AS THAT
OF slis_t_fieldcat_alv BUT WITH A HEADER LINE IN THE DEFINITION.
THIS IS DONE TO MAKE THE CODE SIMPLER.
OTHERWISE WE MAY HAVE TO DEFINE THE STRUCTURE AS IN THE NORMAL SAP
PROGRAMS.
IN THE FIELDCATALOG TABLE WE ACTUALLY PASS THE FIELDS FROM ONE OR
MORE TABLES AND CREATE A STRUCTURE
IN THE LAYOUT STRUCTURE WE BASICALLY DEFINE THE FORMATTING OPTIONS
LIKE DISPLAY IN THE ZEBRA PATTERN ,THE HOTSPOT OPTIONS ETC.
data: fieldcatalog type slis_t_fieldcat_alv with header line,
fieldlayout type slis_layout_alv.
DECLARING THE EVENTTABLE INTERNL TABLE FOR USING EVENTS LIKE
TOP-OF-PAGE ETC.
data : eventstab type slis_t_event with header line.
DECLARING AN INTERNAL TABLE TO HOLD THE DATA FOR THE TOP-OF-PAGE
data : heading type slis_t_listheader with header line.
data : heading1 type slis_t_listheader with header line.
data : heading2 type slis_t_listheader with header line.
data : heading3 type slis_t_listheader with header line.
data : heading4 type slis_t_listheader with header line.
data : heading5 type slis_t_listheader with header line.
data : heading6 type slis_t_listheader with header line.
data : heading7 type slis_t_listheader with header line.
data : heading8 type slis_t_listheader with header line.
STRUCTURE TO PASS THE COLOR ATTRIBUTES FOR DISPLAY.
data : colorstruct type slis_coltypes.
INITIALIZATION. *
initialization.
syrepid = sy-repid.
sypagno = sy-pagno.
clear fieldcatalog.
START-OF-SELECTION. *
start-of-selection.
SUBROUTINE TO POPULATE THE COLORSTRUCT
perform fill_colorstruct using colorstruct.
SUBROUTINE TO POPULATE THE FIELDS OF THE FIELD CATALOGUE
perform populate_fieldcatalog.
SUBROUTINE TO SELECT DATA FROM VARIOUS TABLES AND POPULATE IT IN THE
INTERNAL TABLE.
perform selectdata_and_sort.
SUBROUTINE TO POPULATE THE LAYOUT STRUCTURE.
perform populate_layout using fieldlayout.
SUBROUTINE TO CALL THE FUNCTION MERGE TO ENSURE PROPER DISPLAY.
perform merge_fieldcatalog.
SUBROUTINE TO POPULATE THE EVENTSTAB.
perform fill_eventstab tables eventstab.
SUBROUTINE TO POPULATE THE HEADING TABLES.
perform fill_headingtable tables heading using 'HEADING'.
perform fill_headingtable tables heading1 using 'HEADING1'.
perform fill_headingtable tables heading2 using 'HEADING2'.
perform fill_headingtable tables heading3 using 'HEADING3'.
perform fill_headingtable tables heading4 using 'HEADING4'.
perform fill_headingtable tables heading5 using 'HEADING5'.
perform fill_headingtable tables heading6 using 'HEADING6'.
perform fill_headingtable tables heading7 using 'HEADING7'.
perform fill_headingtable tables heading8 using 'HEADING8'.
SUBROUTINE TO DISPLAY THE LIST.
perform display_alv_list.
FORMS
IN THIS SUBROUTINE WE POPULATE THE FIELDCATALOG TABLE WITH THE NAMES
OF THE TABLE,FIELDNAME,WHETHER IT IS KEY FIELD OR NOT,HEADING AND
COLUMN JUSTIFICATION.
form populate_fieldcatalog.
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MATNR' 'X' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MEINS' ' '.
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MAKTX' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MTART' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MATKL' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'SPRAS' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'WERKS' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MINBE' ' ' .
endform. " POPULATE_FIELDCATALOG
FORM FILL_FIELDS_OF_FIELDCATALOG *
--> FIELDCATALOG *
--> P_TABNAME *
--> P_FIELDNAME *
--> P_KEY *
--> P_KEY *
form fill_fields_of_fieldcatalog tables fieldcatalog
structure fieldcatalog
using p_tabname
p_fieldname
p_key.
p_no_out.
fieldcatalog-tabname = p_tabname.
fieldcatalog-fieldname = p_fieldname.
fieldcatalog-key = p_key.
fieldcatalog-emphasize = '1234'.
*fieldcatalog-no_out = p_no_out.
append fieldcatalog.
endform. " FILL_FIELDSOFFIELDCATALOG
FORM POPULATE_LAYOUT *
--> FIELDLAYOUT *
form populate_layout using fieldlayout type slis_layout_alv.
fieldlayout-f2code = '&ETA' .
fieldlayout-zebra = 'X'.
FOR THE WINDOW TITLE.
fieldlayout-window_titlebar = 'ALV with Events'.
fieldlayout-colwidth_optimize = 'X'.
fieldlayout-no_vline = ' '.
*fieldlayout-no_input = 'X'.
fieldlayout-confirmation_prompt = ''.
fieldlayout-key_hotspot = 'X'.
This removes the column headings if the flag is set to 'X'
fieldlayout-no_colhead = ' '.
*fieldlayout-hotspot_fieldname = 'MAKTX'.
fieldlayout-detail_popup = 'X'.
fieldlayout-coltab_fieldname = 'X'.
endform. " POPULATE_LAYOUT
FORM SELECTDATA_AND_SORT *
form selectdata_and_sort.
select matnr meins mtart matkl from mara
into corresponding fields of t_mara
up to 500 rows .
select matnr maktx spras from makt
into corresponding fields of t_makt
where matnr = t_mara-matnr and
spras = sy-langu.
select matnr werks minbe from marc
into corresponding fields of t_marc
where matnr = t_mara-matnr.
append t_marc.
endselect.
append t_makt.
endselect.
append t_mara.
endselect.
perform populate_itab1.
sort itab1 by matnr.
endform. " SELECTDATA_AND_SORT
FORM MERGE_FIELDCATALOG *
form merge_fieldcatalog.
call function 'REUSE_ALV_FIELDCATALOG_MERGE'
exporting
i_program_name = syrepid
i_internal_tabname = 'ITAB1'
i_structure_name = 'COLORSTRUCT'
I_CLIENT_NEVER_DISPLAY = 'X'
i_inclname = syrepid
changing
ct_fieldcat = fieldcatalog[]
exceptions
inconsistent_interface = 1
program_error = 2
others = 3.
endform. " MERGE_FIELDCATALOG
IN THIS FUNCTION THE MINIMUM PARAMETERS THAT WE NEED TO PASS IS AS
FOLLOWS:-
i_callback_program --> CALLING PROGRAM NAME
i_structure_name --> STRUCTURE NAME.
is_layout --> LAYOUT NAME.
it_fieldcat ---> BODY OF THE FIELD CATALOGUE INTERNAL TABLE
form display_alv_list.
call function 'REUSE_ALV_LIST_DISPLAY'
exporting
I_INTERFACE_CHECK = ' '
i_callback_program = syrepid
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
i_structure_name = 'ITAB1'
is_layout = fieldlayout
it_fieldcat = fieldcatalog[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
THE FOLLOWING PARAMETER IS SET AS 'A' INORDER TO DISPLAY THE STANDARD
TOOL BAR
i_save = 'A'
IS_VARIANT = ' '
it_events = eventstab[]
IT_EVENT_EXIT =
IS_PRINT =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
tables
t_outtab = itab1
exceptions
program_error = 1
others = 2.
endform. " DISPLAY_ALV_LIST
*& Form POPULATE_ITAB1
text
--> p1 text
<-- p2 text
form populate_itab1.
loop at t_mara.
loop at t_makt where matnr = t_mara-matnr.
loop at t_marc where matnr = t_mara-matnr.
move-corresponding t_mara to itab1.
move-corresponding t_makt to itab1.
move-corresponding t_marc to itab1.
append itab1.
endloop.
endloop.
endloop.
endform. " POPULATE_ITAB1
*& Form FILL_EVENTSTAB
text
-->P_EVENTSTAB text *
form fill_eventstab tables p_eventstab structure eventstab.
WHEN THE FOLLOWING FUNCTION IS CALLED THE SYSTEM POPULATES THE
INTERNAL TABLE EVENTSTAB WITH A LIST OF EVENTS NAME.
AS SHOWN BELOW WHEN USING I_LIST_TYPE = 0 THE FUNCTION RETURNS 14
EVENTS NAME.
call function 'REUSE_ALV_EVENTS_GET'
exporting
i_list_type = 0
importing
et_events = p_eventstab[]
exceptions
list_type_wrong = 1
others = 2.
BY CALLING THE ABOVE FUNCTION WE FIRST POPULATE THE EVENTSTAB WITH
THE PREDEFINED EVENTS AND THEN WE MOVE THE FORM NAME AS SHOWN BELOW.
WE ASSIGN A FORM NAME TO THE EVENT AS REQUIRED BY THE USER.
FORM NAME CAN BE ANYTHING.THE PERFORM STATEMENT FOR THIS FORM
IS DYNAMICALY CALLED.
read table p_eventstab with key name = slis_ev_top_of_page.
if sy-subrc = 0 .
move 'TOP_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_top_of_coverpage.
if sy-subrc = 0 .
move 'TOP_OF_COVERPAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_coverpage .
if sy-subrc = 0 .
move 'END_OF_COVERPAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_foreign_top_of_page.
if sy-subrc = 0 .
move 'FOREIGN_TOP_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_foreign_end_of_page.
if sy-subrc = 0 .
move 'FOREIGN_END_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_list_modify.
if sy-subrc = 0 .
move 'LIST_MODIFY' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_top_of_list.
if sy-subrc = 0 .
move 'TOP_OF_LIST' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_page.
if sy-subrc = 0 .
move 'END_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_list .
if sy-subrc = 0 .
move 'END_OF_LIST' to p_eventstab-form.
append p_eventstab.
endif.
endform. " FILL_EVENTSTAB
*& Form FILL_HEADINGTABLE
text
-->P_HEADING text *
form fill_headingtable tables p_heading structure heading
using tablename.
case tablename.
when 'HEADING'.
p_heading-typ = 'H'.
concatenate
' REPORT NAME:-' syrepid
' ABB Industry Pte Ltd' into p_heading-info.
append p_heading.
write sy-datum using edit mask '__/__/____' to sydatum.
concatenate
' DATE:-' sydatum ' USER: ' sy-uname 'PAGE NO:' sypagno
into p_heading-info.
append p_heading.
when 'HEADING1'.
p_heading-typ = 'H'.
p_heading-info = 'TOP-OF-COVER-PAGE'.
append p_heading.
when 'HEADING2'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-COVER-PAGE'.
append p_heading.
when 'HEADING3'.
p_heading-typ = 'H'.
p_heading-info = 'FOREIGN-TOP-OF-PAGE'.
append p_heading.
when 'HEADING4'.
p_heading-typ = 'H'.
p_heading-info = 'FOREIGN-END-OF-PAGE'.
append p_heading.
WHEN 'HEADING5'.
P_HEADING-TYP = 'H'.
P_HEADING-INFO = 'LIST-MODIFY'.
APPEND P_HEADING.
when 'HEADING6'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-PAGE'.
append p_heading.
when 'HEADING7'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-LIST'.
append p_heading.
when 'HEADING8'.
p_heading-typ = 'H'.
p_heading-info = 'TOP-OF-LIST'.
append p_heading.
endcase.
endform. " FILL_HEADINGTABLE
FORM TOP_OF_PAGE *
form top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading[]
exceptions
others = 1.
endform.
*& Form FILL_COLORSTRUCT
text
-->P_COLORSTRUCT text *
form fill_colorstruct using p_colorstruct type slis_coltypes .
p_colorstruct-heacolfir-col = 6.
p_colorstruct-heacolfir-int = 1.
p_colorstruct-heacolfir-inv = 1.
endform. " FILL_COLORSTRUCT
FORM TOP_OF_COVERPAGE *
form top_of_coverpage.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading1[]
exceptions
others = 1.
endform.
FORM END_OF_COVERPAGE *
form end_of_coverpage.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading2[]
exceptions
others = 1.
endform.
FORM FOREIGN_TOP_OF_PAGE *
form foreign_top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading3[]
exceptions
others = 1.
endform.
FORM FOREIGN_END_OF_PAGE *
form foreign_end_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading4[]
exceptions
others = 1.
endform.
FORM LIST_MODIFY *
*FORM LIST_MODIFY.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = HEADING5[]
EXCEPTIONS
OTHERS = 1.
*ENDFORM.
FORM END_OF_PAGE *
form end_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading6[]
exceptions
others = 1.
endform.
FORM END_OF_LIST *
form end_of_list.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading7[]
exceptions
others = 1.
endform.
FORM TOP_OF_LIST *
form top_of_list.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading8[]
exceptions
others = 1.
endform.
SHORT DUMP IS
This error may occur if
- You address a typed field symbol before it has been set with
   ASSIGN
- You address a field symbol that pointed to the line of an
   internal table that was deleted
- You address a field symbol that was previously reset using
   UNASSIGN or that pointed to a local field that no
   longer exists
- You address a global function interface, although the
   respective function module is not active - that is, is
   not in the list of active calls. The list of active calls
   can be taken from this short dump.
PLEASE GIVE ME ANSWER.
REGARDS

HI I MADE SOME CHANGES TO UR CODE...
RUN IF THIS IS THE REQ ...
IN SELECT QUERIES OF RETRIEVING DATA..
form selectdata_and_sort.
select matnr meins mtart matkl from mara
into corresponding fields of TABLE t_mara
WHERE MATNR = T_MARA-MATNR.
up to 200 rows .
IF SY-SUBRC = 0.
    MESSAGE I001 WITH ' DATA RET FROM MARA'.
ENDIF.
IF T_MARA[] IS NOT INITIAL .
select
       matnr
       maktx
       spras
       From
       makt
       into corresponding fields of TABLE t_makt
        FOR ALL ENTRIES IN T_MARA
       where matnr = t_mara-matnr and
       spras = sy-langu.
ENDIF.
IF SY-SUBRC = 0 .
MESSAGE I001 WITH ' DATA RET FROM MAKT'.
ENDIF.
IF T_MAKT[] IS NOT INITIAL.
      select matnr
             werks
             minbe
             from marc
             into corresponding fields of TABLE t_marc
             FOR ALL ENTRIES IN
             T_MAKT where matnr = t_maKT-matnr.
    ENDIF.
ENDFORM.                    "selectdata_and_sort
JUST TRY THIS CODE..

Landscape Verification returns short dump

Similar Messages

Maybe you are looking for