ALE throws dump Message_Type_X

Hi All,
I did ALE configuration on my DEV and PRD for transferring data from DEV to PRD. Although i know, we should not move any data from DEV to PRD, but it's client requirement.
So i did ALE and model view successfully generated on DEV and RFC is perfectly fine even by connection test or authorization test.
When i run bd10 on DEV, it successfully generated idoc with message type MATMAS. and when i get the materail via BD11, it successfully created idoc on PRD. but when i see the material in MM03, it throws error material does not exist or is not activated.
it also throws dump Message_Type_X
WORKFLOW_LOCAL_400
RFC_READ_DESTINATION_TYPE
DESTINATION_NOT_EXIST
What steps should follow now?
Regards
Disha

Hi Krishnendu,
Status is in red when i check from t-code WE02.
When i check it in MM90 and execute it, it does not show any log.
Please tell if i am missing any step..
Regards
Disha

Similar Messages

Function module ISR_GET_DATA_FROM_XML throwing dump.

Hi All,
Function module ISR_GET_DATA_FROM_XML throwing dump.
The dump says,
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "ISR_GET_DATA_FROM_XML" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
Can you please help me in resolving this error.
PERFORM set_tag_constants.
set size of XML document
ld_size = id_size.
create the input stream
lr_stream = ir_ixml_stream_factory->create_istrea
     table = it_xml
     size = ld_size ). create XML document object
lr_dom = ir_ixml_factory->create_document( ).
create parser
lr_parser = ir_ixml_factory->create_parser(
     stream_factory = ir_ixml_stream_factory
     istream        = lr_stream
     document       = lr_dom ).
Thanks
Rohini.

Hi,
SELECT MBLNR
           MJAHR
           FROM MSEG
           INTO TABLE I_MKPF
           WHERE MBLNR IN S_MBLNR AND
                       MJAHR IN S_MJAHR.
IF I_MKPF IS NOT INITIAL.
SELECT * FROM MSEG INTO TABLE O_MSEG FOR ALL ENTRIES IN I_MKPF
      WHERE MBLNR   =    I_MKPF-MBLNR
        AND MJAHR   =    I_MKPF-MJAHR
        AND MATNR   IN   I_MATNR
        AND WERKS   IN   I_WERKS
        AND LGORT   IN   I_LGORT.
ENDIF.
ALSO CHECK FM u2018/BEV2/ED_REA_MSEG_MKPFu2019.
Regards,
Deepa Kulkarni

Archiving Transaction SARA throws dumps.

S0003731475
Hi Gurus
I am trying to run archiving transaction SARA but it throws dumps and I canu2019t seem to find the reasonu2026u2026
Here is the dumpu2026u2026..Anyone who faced similar problemu2026u2026.Please help.
Runtime errors         SYNTAX_ERROR
       Occurred on     12/08/2009 at   13:45:09
Syntax error in program "SAPLARCH ".
What happened?
The following syntax error occurred in the program SAPLARCH :
"Method "GET_DATA" is unknown or PROTECTED or PRIVATE."
Error in ABAP application program.
The current ABAP program "SAPMAADM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLARCH ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
The following syntax error was found in the program SAPLARCH :
"Method "GET_DATA" is unknown or PROTECTED or PRIVATE."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "M3SAPA01"
Network address.......... "136.133.230.177"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "M3SAPA01"
Database type............ "MSSQL"
Database name............ "RDS"
Database owner........... "rds"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Mar 10 2009 01:13:21"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "274"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 220
User................ "RHEMNANI"
Language key........ "E"
Transaction......... "SARA "
Program............. "SAPMAADM"
Screen.............. "SAPMAADM 0001"
Screen line......... 2
Information on where terminated
The termination occurred in the ABAP program "SAPMAADM" in "D0001_DISPLAY".
The main program was "SAPMAADM ".
The termination occurred in line 278 of the source code of the (Include)
program "MAADMO01"
of the source code of program "MAADMO01" (when calling the editor 2780).
Source code extract
002480   * check if parameters exists
002490     progname = arch_obj-retrie_prg.
002500     answer = 'YES'.
002510     CALL FUNCTION 'RS_SELSCREEN_EXISTS'
002520       EXPORTING
002530         report            = progname
002540       IMPORTING
002550         answer            = answer
002560       EXCEPTIONS
002570         no_report         = 01
002580         program_incorrect = 02
002590         program_not_found = 03.
002600     IF sy-subrc EQ 0.
002610       IF answer EQ 'NO'.
002620         LOOP AT SCREEN.
002630           CHECK screen-group1 = 'VAR'.
002640           screen-active = 0.
002650           MODIFY SCREEN.
002660         ENDLOOP.
002670       ENDIF.
002680     ENDIF.
002690   ENDMODULE.                             " D0300_DISPLAY OUTPUT
002700
002710   *&---------------------------------------------------------------------*
002720   *&      Module D0001_DISPLAY OUTPUT
002730   *&---------------------------------------------------------------------*
002740   *       text                                                           *
002750   *----------------------------------------------------------------------*
002760   MODULE d0001_display OUTPUT.
002770     SUPPRESS DIALOG.
----->     CALL FUNCTION 'ARCHIVE_DISABLE_MONITORING'.
002790   ENDMODULE.                             " D0001_DISPLAY OUTPUT
002800   *&---------------------------------------------------------------------*
002810   *&      Module INIT_0120 OUTPUT
002820   *&---------------------------------------------------------------------*
002830   *       text
002840   *----------------------------------------------------------------------*
002850   MODULE d0120_display OUTPUT.
002860     DATA: format1(12) TYPE c.
002870     DATA: format2 TYPE i.
002880     LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
002890     SET PF-STATUS 'SPACE'.
002900     SET TITLEBAR '105'.
002910     WRITE: / 'Archivverzeichnis:'(060), file_path.
002920     ULINE.
002930     MOVE freespace TO format2.           "to format with points
002940     WRITE format2 TO format1.
002950     WRITE: / 'Verfügbarer Freiplatz:'(061),format1 NO-ZERO,'KB'.
002960     LEAVE SCREEN.
002970
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 0
SY-TABIX 0                             SY-DBCNT 0
SY-FDPOS 0                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1                             SY-PFKEY
SY-UCOMM                               SY-TITLE Archive Management Module Pool
SY-MSGTY                               SY-MSGID
SY-MSGNO 000                           SY-MSGV1
SY-MSGV2                               SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
       Program
       Include                                  Line
       Class
     2 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
     1 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
Chosen variables
     2 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
%_DUMMY$$
                               2222
                               0000
                               0000
                               0000
     1 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
No dump information available
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "ab_genprog" of the SAP
Basis System, specifically in line 1423 of the module
"//bas/640_REL/src/krn/runt/abgen.c#14".
The internal operation just processed is "FUNC".
The internal session was started at 20091208134509.
Program name.........: "SAPLARCH ".
Error message........: "Method "GET_DATA" is unknown or PROTECTED or PRIVATE.".

Rajesh,
This might happen if the orginal function module ARCHIVE_GET_INFORMATION in LARCHF03 program is altered, bring back the the function module to original, it might solve your problem.
Anand B Vodnala

Assign Syntax throwing DUMP!!!

Before Unicode check active, the syntax is:
ASSIGN ELBP-KRT01+OFFSET TO <X>.
I changed into
ASSIGN ELBP-KRT01+OFFSET(*) TO <X>.
after reading SAP help.
KRT01 is DEC field from DB ELBP
FIELD-SYMBOLS: <X> type any.
Dump says:
Part of the source field "ELBP-KRT01" was assigned to a field symbol,
but this is not possible for fields of type "P".
When I test this change...it throws dump.Am I missing something?
Thanks
Kiran

I dont see any option like Accessing Fields Using Offset and Length Addressing".
I am on 4.7EE
I can see only below.
ASSIGN f TO <fs>.
Extras:
1. ... CASTING ... or
2. ... TYPE type
3. ... DECIMALS dec
4. ... RANGE range
Hope you can help me paste the syntax from what you se rather than increasing the iterations .
Thanks
Kiran
Edited by: kiran dasari on Oct 11, 2008 2:31 AM

GRC: Control Design Plan Task dump MESSAGE_TYPE_X

Hi,
When a task plan is created, workflow WS75900001 gets triggered. This workflow sets a task for background execution to update the plan status. This step generates a dump MESSAGE_TYPE_X in background, and the workflow is held up (status remains in process).
Due to this the task plan status is not updated to "Complete" from "Planning".
What can be the root cause of this issue?
I feel some configuration is missing, but am not able to figure out what?
METHOD CONSTRUCTOR .
mo_grpc_case_api = io_grpc_case_api.
*Initiate Status Object both for the new created and the existing case entry
DATA l_status_objnr TYPE scmgstatobjnr.
TRY.
      l_status_objnr = mo_grpc_case_api->get_one_attribute( i_name = if_scmg_case_read=>stat
      CREATE OBJECT mo_case_status
              EXPORTING
                i_objnr = l_status_objnr.
    CATCH CX_GRPC_CASE.
      MESSAGE x151(00).
   ENDTRY.
ENDMETHOD.
Active call trace:
METHOD       CL_GRPC_CASE==================CP    CL_GRPC_CASE==================CM004
CL_GRPC_CASE=>CONSTRUCTOR
METHOD       CL_GRPC_ASSESSMENT============CP    CL_GRPC_ASSESSMENT============CM008
CL_GRPC_ASSESSMENT=>CONSTRUCTOR
METHOD       CL_GRPC_ASSESSMENT============CP    CL_GRPC_ASSESSMENT============CM009
CL_GRPC_ASSESSMENT=>CREATE
FUNCTION     SAPLGRPC_TASKPLAN                   LGRPC_TASKPLANU02
GRPC_TASKPLAN_CD_ASSESSSMENT
METHOD       CL_GRPC_TASKPLAN==============CP    CL_GRPC_TASKPLAN==============CM006
CL_GRPC_TASKPLAN=>EXECUTE
FORM         GRPC_BO_TASK_PLAN                   GRPC_BO_TASK_PLAN
EXECUTE
FUNCTION     SAPLSWOR                            LSWORU02
SWO_INVOKE_INTERNAL
FUNCTION     SAPLSWOR                            LSWORU33
SWO_INVOKE
METHOD       CL_SWF_UTL_RUN_SERVICES=======CP    CL_SWF_UTL_RUN_SERVICES=======CM00N
CL_SWF_UTL_RUN_SERVICES=>EXECUTE_METHOD_BOR
Thanks,
Chitrali

Another forum thread gives some hint [link|http://sap.ittoolbox.com/groups/technical-functional/sap-basis/message-type-x-error-while-creating-order-in-iw31-3605760] and refer OSS note [1052647|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1052647]

ALV Grid throwing dump in total function

Hi,
My ALV grid program, is working fine in development server, for the total and subtotal function. However, the same program is throwing a short dump in Quality server when we try to get the total.Please help!
Regards,
Anita Jeyan

Hi ,
Please go to ST22 and check what is the reason for error.
Let me know the error.
The reason might be due to some less data size or some data type mismatch.
Regards,
Uma
Edited by: UmaDave on Jun 9, 2010 12:10 PM
Edited by: UmaDave on Jun 9, 2010 12:10 PM

Short dump MESSAGE_TYPE_X in displaying data from BPC Virtualcube

Hi Experts,
I am experiencing an error when try to display data from a BPC VirtualProvider Infocube (both from Workbench and with LISTCUBE transaction).
This kind of virtualcube is auto generated by BPC.
When I do some kind of selection I obtain this error: MESSAGE_TYPE_X
Short text of error message:
System error in program SAPLRRK0 and form CHECK_KHANDLE (see long text)
Technical information about the message:
Message class....... "BRAIN"
Number.............. 299
Variable 1.......... "SAPLRRK0"
Variable 2.......... "CHECK_KHANDLE"
I have another BPC vitualprovider and this doesnu2019t happen.
I would use this cube inside a multiprovider, that has a BI cube too, and get the data through a BEx query. But the query throws the error and stopped.
I know that there could be problems with BPC structures (i.e. changes in tech name when transporting it), but at the moment I donu2019t see other solution to compare BI to BPC data.
I went through other posts in sdn forum for this issue, but I am not able to get the exact solution,
please help
Thanks,
Marco
System version:
BW: 701 level 0007
BPC: 750 level 0005

Hi Lokesh,
I read the note you have indicated.
For the first note 1479393: I donu2019t have hierarchies and the error appears in a different program to what is indicated in the note. This is where terminated:
Termination occurred in the ABAP program "SAPLRRK0" - in "CHECK_KHANDLE".
The main program was "GP4LQ7N6RS4RUB6HA69UREYGPKB ".
In the source code you have the termination point in line 34
of the (Include) program "LRRK0F05".
Furthermore, there are no calculated measures nor members in the MDX statement, because I just try to display the data from the virtualcube.
For the second 1448691: yes, it could be a performance related problem. Indeed, when I apply stronger filters, the error doesnu2019t occur and I got the data. But the system is already patched to SAPKW70107.
So, do you have any other ideas?
Thanks,
Marco

ABAP Dump: MESSAGE_TYPE_X

Dear Folks,
We are using BW 3.1 and R/3 4.6C. Daily I am getting one ABAP dump of MESSAGE_TYPE_X type.
Upon further investigation, I got the following information:
Short text of error message:
Structures have changed (sy-subrc=2)
Long text of error message:
Diagnosis
     You are using the update method 'Queued Delta'. It is not possible
     to transfer an entry from the extraction queue MCEXnn (nn = number
     of affected application from the Logistic Cockpit) to the
     corresponding delta queue with report RMBWV3nn. This is because
     since the document was updated, one of the structures used was
     changed.
System Response
     Transfer to the delta queue was not performed.
It is also referring to one note # 328181, which I felt some difficulty to follow.
Can any one please help me resolving this issue? If you need any other information, please let me know.
Thanks in adnvace!
Regards,
Fasial

Hi,
it seems you have tried to do some patch or plugin upgrade in R/3 and you havent cleaned up the extraction queue for LO data sources in LBWQ or did some ehancements to a data source belonging to LO cockpit and didnt cleaned up the queue.
Also it seems the daily delta loads are not running.
See this note which tells you what needs to be done in those cases 762951,1081287,328181
1)You need to delete the existing init which is present in the system for the data source.
2)Stop the job for collective update in LBWE->Job control for this data source.
3)Go to LBWQ in R/3 display the queue which you think is creating the issue.go inside the queue with the display function again.you will have to delete all the entries present in the queue.
4)Once deleted then you can schedule a new init without data transfer and schedule the job in LBWQ for the data source again.
This will result in loss of delta and you will have to reload the history again.
Thanks
Thanks
Ajeet

FM "COM_PRCAT_CREATE_API_INT" throws DUMP!

Hi all,
I am trying to use the foll FM "COM_PRCAT_CREATE_API_INT" in a report but getting an exception:
Function module "COM_PRCAT_CREATE_API_INT" was called
with the parameter "IV_HIEARCHY_EXIST_IN_PME".
This parameter is not defined.
When i run this FM seperately and passing a blank value to this parameter,it works .However when using it in a report,if i pass a blank value to the parameter "IV_HIEARCHY_EXIST_IN_PME" the it gives the above dump.Since this parameter is a mandatory parameter,I need to pass some value to this parameter.
Can somebody throw some light?

I think UR calling the FM wrongly ...
the parameter name is : IV_HIERARCHY_EXIST_IN_PME
and not IV_HIEARCHY_EXIST_IN_PME

BADI ecc6 throws dump

Dear All,
We are getting a dump while calling a badi through our Z program.
We have created a Enhancement spot through SE18 -> z_es_spot
where I have defined badi definition as Z_BADI_DEF and interface as
ZIF_EX_LE_SHP_TAB_CUST_ITEM.
I have defined a method as ADD there.
After that we have created a enhancement implemention through Se19 ->Z_ENHANCE_IMP
there we have given badi implementation as ZTEST_BADI_IMPL and implementing class is ZIMPL_CL.
Afterwards I have created a program through Se38 ->zbadi.
class cl_exithandler definition load.
data: var2 type ref to ZIF_EX_LE_SHP_TAB_CUST_ITEM.
CALL METHOD var2->add
when the program call the method ADD it throws a dump as Access via 'NULL' object reference not possible.
Any help will be appreciated.

i am still stuck can any one help or give some advice.
thanx in advance
regards

ALE RBDMIDOC dump

Hi All,
I am getting dump while running program RBDMIDOC for message type DEBMAS. The dump is ABAP/4 processor: DBIF_REPO_SQL_ERROR. Can any one have idea why this is occuring? Thanks in advance for your valuble suggestion

Hi Jaiganesh,
You can try out folowing t-codes for error debugging
1.bd75
2.bdm2
3.sm58
4.bd87
RSEINB00 and RBAPP01 are the programs which are used to Post the IDOC to databse and process the inbound IDOC.
Also you can use following links for error debbuging
(1) /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
(2) /people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
(3)http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
(4) idoc
(5)http://help.sap.com/saphelp_erp2005vp/helpdata/en/78/2178a651ce11d189570000e829fbbd/frameset.htm--
--This is for Message Control. See the Left Pane in this web page to get the ALE implementation for BAPI's also.
(6)/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment - Converson Rules Guidelines
(7)ALE Inbound Error Handling - Inbound Error Handling in ALE
Hope this solves your problem.
Note: Reward if useful

'RS_TABLE_LIST_CREATE' - Throwing dump

Hi,
I am trying to call a table with the function module 'RS_TABLE_LIST_CREATE'. System is throwing a dump sayin <b>Function parameter "SELTAB" is unknown</b>.
Do i have to declare SELTAB?... What shud i do ?
Thanks in advance.
CALL FUNCTION 'RS_TABLE_LIST_CREATE'
      EXPORTING
        table_name               = 'ZTVWORDERS'
        ACTION                   = 'ANZE'
      WITHOUT_SUBMIT           = ' '
      GENERATION_FORCED        =
      NEW_SEL                  =
      NO_STRUCTURE_CHECK       = ' '
      DATA_EXIT                = ' '
    IMPORTING
      PROGNAME                 =
    TABLES
        SELTAB                   = GV_PONUM
    EXCEPTIONS
      TABLE_IS_STRUCTURE       = 1
      TABLE_NOT_EXISTS         = 2
      DB_NOT_EXISTS            = 3
      NO_PERMISSION            = 4
      NO_CHANGE_ALLOWED        = 5
      OTHERS                   = 6
    IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
<b></b>

Hi
Look at the below thread, this is having the same question and having the answer also
call transaction
Regards
Sudheer

Abap dump MESSAGE_TYPE_X in SAPLSLVC - in "FILL_DATA_TABLE

Gurus ,
we get the MESSAGE_TYPE_X error in saplslvc in "FILL_DATA_TABLE ' when we execute our custmized program .
but the same program was executed successfully in the Development system .
i get this error in quality and production alone
we have dev , qua & pro at the same level .
what could be the problem ?
hoping for your valuable response

Look if these OSS notes are applicable in your system (april 2008)
- [ Note 1034895 - ALV mean value: Decimal places in mean value calculation|https://service.sap.com/sap/support/notes/1034895]
- [Note 840240 - ALV total: Average with P fields without decimal places|https://service.sap.com/sap/support/notes/840240]
- [Note 717669 - ALV grid: Hidden columns result in unreadable grid|https://service.sap.com/sap/support/notes/717669]
- [Note 442295 - ALV toolbar: Change Layout dial. box contains hidden functs|https://service.sap.com/sap/support/notes/442295]
- [Note 1136738 - ALV-Total: Subtotals of numeric columns without values|https://service.sap.com/sap/support/notes/1136738]
Regards

Dynamic sql is throwing dump after upgrade to EHP 7.0

Hi All,
My customer recently upgraded to EHP 7.0.
I have one query like below :
select * from (ls_table_list-tabname) into
                         table <table>
                         where (condition).
where ls_table-tabname is the table name, <table> is with the structure of same table and condition is very simple where condition. (id = 'XXXXX').
We are getting dump with "CX_SY_DYNAMIC_OSQL_SYNTAX" and the dump message is "
When parsing a dynamic statement, an error occurred.
Before upgrade same statements were working fine.
Please send us the response asap. Its urgent.
Thanks in advance,
Sreedhar

Hi Divyanshu,
Following is the text of Short dump :
Category ABAP Programming Error
Runtime error SAPSQL_PARSE_ERROR
Exception CX_SY_DYNAMIC_OSQL_SYNTAX
ABAP program / GETPF / SAPLTABLE_CONTENT_CHECK
Application component not assigned
Date and Time 07.02.2014 14:57:48
Short text
When parsing a dynamic statement, an error occurred.
What happened?
Error in ABAP application program.
The current ABAP program "/ GETPF / SAPLTABLE_CONTENT_CHECK" had to be canceled
be as it appears on
an instruction is encountered, which unfortunately can not be executed.
Error Analysis
There is an exception has occurred, which is discussed further below.
The exception, which is assigned to the class 'CX_SY_DYNAMIC_OSQL_SYNTAX'
was in the procedure "/ GETPF / TABLE_CONTENT_CHECK" "(FUNCTION)" neither
intercepted,
still propagated by a RAISING clause.
Since the caller of the procedure is not with the occurrence of the exception
could be expected, the running program was terminated.
Error was at below statement :
      SELECT * FROM (ls_table_list-tabname) INTO
TABLE <table>
WHERE (condition).

Mapping node from UIcust &View throws dump in result

hello all,
Need ur urgent help!!
I hav already posted one thread bout dis but didnt got any response.... So doing it again
Not able to map UICust node to View.Till UICust the app works fine but as i map the node to View........ Error comes of contact administrator without any exception
Contact Administrator error is coming after mapping node from UICust with View.
Its not happpening in case of 1 single attribute but while mapping the node this error is encountered even if that node consists of single attribute.
Urgent help required....Kindly help
Thanks n regards
Mandeep

Hi Siva,
4 attr under 1 node in modal node and same i craeted in value node in uicust. but even if i try to map the replicated value node in uicust and map dat to value node of view. still its showin dump (Contact administrator wid no exception)
I hav reopnened the project....... rebuild. it doesnt show any error.... as soon as i go for mapping in view and uicust . it starts throwin dump
Thanks n Regards
Mandeep

ALE throws dump Message_Type_X

Similar Messages

Maybe you are looking for