RFC_ERROR_SYSTEM_FAILURE -Exception condition 'INCONSISTENCY' rasied .

Hi
I created a report with 'Calculated KeyFigure' and 'Restricted KeyFigure' . And i transported to BI-Quality System.
Then i opened the query in BI-Quality Query Designer and try to see the 'Calculated KeyFigure' and 'Restricted KeyFigure' .
And im getting the below error
RFC_ERROR_SYSTEM_FAILURE -Exception condition 'INCONSISTENCY' rasied .
why it is coming like that . And delete the infocube from the BI-Quality System . And transported the query five times . But again im getting the same problem .
pls let me knw
kumar

Hi Ravi,
Please check this thread:
Exception Condition "inconsistency" raised, RFC_ERROR_SYSTEM_FAILURE
Hope it helps.
Regards,
Mona

Similar Messages

RFC_ERROR_SYSTEM_FAILURE: Exception condition "CNTL_ERROR" raised.

I wrote a function.This read codes from a .txt file, create an abap program dinamically and after run it.
I wrote a java program with jco and i wrote an abap program for calling function .İf i runned abap program not happened any problem.But i runned java program.i saw this error :
RFC_ERROR_SYSTEM_FAILURE: Exception condition "CNTL_ERROR" raised.
My function :
FUNCTION Z_MS_FUNC2.
*"*"Local Interface:
*" IMPORTING
*" EXPORTING
*"     VALUE(RESULT) TYPE ZMS_SONUC-SONUC
DATA: code TYPE TABLE OF rssource-line.
data : p_file TYPE string.
p_file = 'C:\deneme.txt'.
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        filename                      = p_file
        FILETYPE                      = 'ASC'
      tables
        data_tab                      = code.
INSERT REPORT 'zms_dinamik002' FROM code.
SUBMIT zms_dinamik002 AND RETURN.
result = 'Successfull.'.
ENDFUNCTION.
this code show error row :
38     CALL METHOD CL_GUI_FRONTEND_SERVICES=>DIRECTORY_LIST_FILES
    39       EXPORTING
    40         DIRECTORY                   = FILE
    41         FILTER                      = ''
    42         FILES_ONLY                  = 'X'
    43 *    DIRECTORIES_ONLY            = 'X'
    44       CHANGING
    45         FILE_TABLE                  = filetab
    46         COUNT                       = count
    47       EXCEPTIONS
    48         CNTL_ERROR                  = 1
    49         DIRECTORY_LIST_FILES_FAILED = 2
    50         WRONG_PARAMETER             = 3
    51         ERROR_NO_GUI                = 4
    52         others                      = 5.
    53
54     IF SY-SUBRC <> 0.
>>>>>       RAISE CNTL_ERROR.
    56     ENDIF.
deneme.txt
report mehmet.
data wa like zms0005.
wa-jop_id = 14.
wa-jop_name = 'UZAK4'.
modify zms0005 from wa.

Hi,
wa-jop is not defined (data: wa-jop type...)!
Try to insert the coding-lines in a new report. Than make a syntax check.
Regards Mario
Edited by: Mario Müller on Mar 11, 2008 6:47 AM

RFC_ERROR_SYSTEM_FAILURE: Exception condition "FAILED" raised on Publish of

Hi,
When i preview my Bi query in potal i am getting following exception :
RFC_ERROR_SYSTEM_FAILURE: Exception condition "FAILED" raised
Earlier i had already published some query which is working properly, but the new one which i am publishing now is giving me above exception.
Regards,
Jigar Oza

Hi,
Check the target on which the query is built is active in the same server.

Exception condition "INCONSISTENCY" raised

Hi Experts,
Greetings!
I was revising the configuration of my FG Inventory Report when I
encountered this error after saving the Query Designer and running the BEx Analyzer:
Exception condition "INCONSISTENCY" raised.
Afterwards, I cannot able to continue working on BEx Query Designer on the report anymore because of the error.
In the reporting tool ANALYZE_RSZ_TABLES in SE38, I got the following result:
Table RSZELTXREF
Unresolved relations between query elements.
Missing elements in existing query components
Critical error: listed query elements are parts of definitions of
existing queries or query components. Elements are not found in the
table RSZELTDIR in required objects version and can not be used.
Further investigations are required at SAP. Create an OSS message for
BW-BEX-ET-QDEF
Missing element ELTUID
48NRDU7QW9H30633XZDD0G9V3
Check results:
Exception condition INCONSISTENCY dump accesing listed components.
List of affected query components:
Technical Name: ZPP_JMV1_Q001
Technical ID: 484ZV76Y10KGXAALQJ2K78YY9
Component Type: REP
Info Provider: ZPP_JMV1
Package: ZBIDEV
Created in: BID
How should I fix the missing element?
Missing element ELTUID
48NRDU7QW9H30633XZDD0G9V3
You assistance is appreciated.
Thank you.
Regards,
Btup

Hi,
If You have an element in another system I would suggest to perform a transport of a query using this element from one system to the other.Just from the investigations done by you, I see that there is only 1 'missing' element which is used in other queries. Please find out in which queries exactly this element is used. This can be done using the same report ANALYZE_RSZ_TABLES (table RSZELTXREF).You will find
'affected queries or query component'. This is WHERE-USED list for this 'missing' element. Check the existence and consistency of those queries in the QAS and if they are correct, You may simply transport them to this system.
Rgds
Manoj Kumar

Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILUR

Hi,
I am getting the following message when I click on workitems for CATS timesheet approval(TS3100007) that are received in UWL tasks inbox in MSS.
Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.cat.approve.blc.FcCatApprove.rfcExecute(FcCatApprove.java:307)
at com.sap.xss.hr.cat.approve.blc.FcCatApprove.rfcReview(FcCatApprove.java:435)
at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApprove.rfcReview(InternalFcCatApprove.java:220)
at com.sap.xss.hr.cat.approve.blc.FcCatApproveInterface.onReview(FcCatApproveInterface.java:379)
at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApproveInterface.onReview(InternalFcCatApproveInterface.java:153)
at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApproveInterface$External.onReview(InternalFcCatApproveInterface.java:333)
at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownListInterface.onEvent(VcCatApproveDrillDownListInterface.java:128)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownListInterface.onEvent(InternalVcCatApproveDrillDownListInterface.java:127)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownListInterface$External.onEvent(InternalVcCatApproveDrillDownListInterface.java:217)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:533)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseReviewAndSaveEvent(FPMComponent.java:946)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseReviewAndSaveEvent(FPMComponent.java:1109)
at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownList.fireEvent(VcCatApproveDrillDownList.java:330)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownList.fireEvent(InternalVcCatApproveDrillDownList.java:166)
at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownListInterface.blcEvent(VcCatApproveDrillDownListInterface.java:228)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownListInterface.blcEvent(InternalVcCatApproveDrillDownListInterface.java:163)
at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownListView.onActionReview(VcCatApproveDrillDownListView.java:303)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownListView.wdInvokeEventHandler(InternalVcCatApproveDrillDownListView.java:178)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
at com.sap.xss.hr.cat.approve.model.approval.CatsApproval.hrmss_Cat_Wd_Approval(CatsApproval.java:178)
at com.sap.xss.hr.cat.approve.model.approval.Hrmss_Cat_Wd_Approval_Input.doExecute(Hrmss_Cat_Wd_Approval_Input.java:137)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
Does anyone have any idea?
Thanks.
BNP

Hi,
It looks to me like the RFC Hrmss_Cat_Wd_Approval does not exist. Is your back-end system ECC 6.0? If not then I don't believe this will work. See page 93 of the document at this link:
https://www2.iviewstudio.com/support_content/_17296/BP_MSS_mySAPERP2005_SR1_EN.pdf
Bert

Approval Overtime iView Error - "Exception condition "PROFILE_NOT_FOUND"

Hi There
I have looked at every forum thread loaded on this site and if I missed something I do apologise.
I keep on getting error - "Exception condition "PROFILE_NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE"
I have maintained what I deem the relevant configuration in my view and also updated the user parameters.
SAP_LINE
Field Selection Detail Screen        PERNR   Personnel Number
Field Selection Indiv. Record View   PERNR   Personnel Number
from the default
Field Selection Detail Screen        ESS     Personnel Number
Field Selection Indiv. Record View   ESS     Personnel Number
CATS Approval: Individual Record - PERNR
CATS Approval: Details - PERNR
Approval Profiles - ZLIN
Any help will be appreciated.
Regards
Maahir

Dear Maahir,
Have you defined a CATS Data Entry Profile in the CVR user parameter? Would you please also check whether the default 'ESS' profile does exist in your system? The Manager have an infotype 105 in valid period right?
Normally this error comes on ESS when the system is looking for a CATS Data Entry Profile, which has not been assigned to the user.
This CATS profile can be assigned to the user either via the User Parameter 'CVR', with the name of the Date Entry Profile entered as the parameter value, or by creating a default ESS Data Entry Profile. R/3 can then assign a profile to the employee even if the user parameter CVR has not been explicitly set. The CATS Data Entry Profiles are stored in the table TCATS.
For more information on creating the default Data Entry Profile, see the IMG, under Cross-Application Components -> Time Sheet -> Specific Settings for CATS -> CATS regular -> Set Up Data Entry Profiles.
For more information on the CVR user parameter setting, see the SAP Library, under Cross-Application Components -> Cross-Application Time Sheet (CATS) -> User Interfaces -> CATS regular.
As it is in MSS when approving, here I am giving you some information which will help you in this regard (PROFILE_NOT_FOUND):
In the IMG (transaction SPRO), go to
- SAP Customizing Implementation Guide
- Cross-Application Components
    - Time Sheet
      - Specific Setting for CATS regular
        - CATS regular
          - Approve Working Time
            - Define Field Selection for Individual Approval View
            - Define Field Selection for Detail View
Hope the above information should help.
Best Regards,
Deepak..

Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR

Dear EP Expert,
We are trying to implement ECC 6 with EP 7. When i try to browse a standard webdypro iView provide by the ess business package i.e (record working time). The system return such error.
Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:468)
     at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:822)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:248)
     at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:344)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:234)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:484)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
     at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
     at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:879)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1280)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:552)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:191)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:221)
     at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 66 more
Other page like leave request is not displaying anything at all, just the blank page. Anyone knows what is wrong? I have read some previous thread and found that they are mentioning the "CVR". Anyone know what is it?
Thanks
Regards,
Bryan

Dear Brian
This problem may be arising from the error/changes required in Entry Profile...
In R/3
- SPRO
-   Cross-Application Components
-     Time Sheet
-       Set Up Data Entry Profiles
Go there and fix the problem and this should be resolved...
Best Regards,
Aslam Riaz

Exception condition "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILU

Hi All,
After the custo of the ESSleave request in the IMG . I made some tests.
Evrethign is going fine but once i try to enter a leave request during a non wroking day, i'm getting this message
Exception condition "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILURE
I checked in st22 and they ask to find a sap note with those key words
"RAISE_EXCEPTION" " "
"SAPLSPO1" or "LSPO1F01"
"INSTANTIATE_CONTROL"
or
"SAPLSPO1" "CNTL_ERROR"
or
"SAPMSSY1 " "CNTL_ERROR"
I found nothing that can help me in sap service..
Did someone already encounter such error ?
Only usefull answers will be rewared .

Hi Adel,
Can you test the same application in the content administrator of the respective portal and check if you find the same error or another error.
Regards,
Narendra.

Exception condition "CONNECT TO ENQUE SERVER FAILED" raised.

In Our production in peak hours we have faced this problem.
initially we have noticed this by system lock error.we tried to kill dialog work process in with help DPMON and OS level also but it did' resolve our problem.after some time we have re-started the SAP and Database.now it is workig fine.
we have idenified in the dumps following errors:
1.Database inconsistency: Start Transaction SICK.
2.Exception condition "CONNECT_TO_ENQ_SERVER_FAILED" raised.
3. they are many dumps in system with the message "Database inconsistency"
our enque/tablesize: 20480
OS:Solaris
DB:Oracle 10g
SAP:Upgraded to ECC 6.0 from 4.6b 4 months back
can some one tell us why it happened for error analysys purpose.
Thanks in advance.
Regards,
Delip

Transaction Sick is only letting you know that a critical process is missing in this case the ENQ process... basically you need to know why the process went down... basically you need to go through the logs to check where the error occurred... I presume the database inconsistency bit is a direct result of the missing/nonresponding enque as it manage the locks.
Again the answer for all your questions should be in the logs.. check sm21 and dev_disp and dev_w0...
Regards
Juan

Short Dump, Exception condition "NOT_EXIST" raised

Dear Colleagues!
I am having a problem with short dump, I am getting the message Exception condition "NOT_EXIST" raised.
I am trying to load data to ODS with full load and filtering via a DTP.
In the monitoring the load doesn't even get started.
I have already loaded data succesfully in this ODS... But now it doesn't work anymore..
I also tried to replicate and active all the rules and objects again.
And in the source system if I test the extractor it works fine.
I saw an earlier thread on this issue, and it recommended programs ZDMDELTAREPAIR or RSBDELTAREPAIR, but this thread was especially for BW 3.5. We are using 7.0 and have SP10. Are these programs still valid or is there another note for 7.0?
Hope you can help!
Regards Silje
Does anyone have any ideas?
regards, Uros

Hi again,
I tried RSBDELTAREPAIR and it worked!
Thanks to the forum again!
Silje

"Exception condition "CONTROL_FLUSH_ERROR" raised." during background jobs

hi all,
the program ZTEST is used for downloading a txt file into D: using GUI_DOWNLOAD. this program works fine but when I schedule this porgam in background jobs in tcode SM36 using "job wizard", i am getting errors as Exception condition "CONTROL_FLUSH_ERROR" raised and the error analysis is as
'A RAISE statement in the program "SAPLSFES " raised the exception condition "CONTROL_FLUSH_ERROR".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.'
How to rectify this error???
points will be rewrded
thanks in advance

GUI_DOWNLOAD is a FM that is designed to download files by interation with the PC directories (only possible in foreground). If the file download is the requirement the u can use application server files for it.
But if you are insisting on notepad and excel documents, then you have to use CLIP and EXECUTE function modules. Refer to Class CL_GUI_FRONTEND_SERVICES that has all the required methods

Exception condition "CONVERSION_ERROR" raised.

Hi,
We have been getting short dumps in our production system daily. I was unable to locate the problem by looking at the dump. The dump says that CONVERSION_ERROR raised.
Which application raised this exception? Again no clue on the same. Please find the text of the dump.
Short text
    Exception condition "CONVERSION_ERROR" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
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
    A RAISE statement in the program "CL_SWF_CNT_CONTAINER==========CP" raised the
     exception
    condition "CONVERSION_ERROR".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
    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:
    "RAISE_EXCEPTION" " "
    "CL_SWF_CNT_CONTAINER==========CP" or "CL_SWF_CNT_CONTAINER==========CM02J"
    "IF_SWF_CNT_CONVERSION~TO_XML"
    or
    "CL_SWF_CNT_CONTAINER==========CP" "CONVERSION_ERROR"
    or
    "SAPMSSY1 " "CONVERSION_ERROR"
    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.
System environment
    SAP-Release 700
    Application server... "zacwtbsrv0
    Network address...... "10.27.191.
    Operating system..... "Windows NT
    Release.............. "5.2"
    Hardware type........ "4x AMD64 L
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 9
    Shortdump setting.... "full"
    Database server... "ZACWTBSRV063"
    Database type..... "MSSQL"
    Database name..... "EP1"
    Database user ID.. "ep1"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 21 2008 00:12:39"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 157
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 16384
MM Used. 8164576
MM Free. 212256
User and Transaction
    Client.............. 100
    User................ "WF-BATCH"
    Language Key........ "E"
    Transaction......... " "
Transactions ID..... "FB565CDDF6D0F1BFA292001E0B5D7336"
Program............. "CL_SWF_CNT_CONTAINER==========CP"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "EP1"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........."0A1BBF4011A4488D408222BD"
Outbound Queue Name.." "
Client.............. 100
User................ "HPRETORIUS"
Transaction......... " "
Call Program........."SAPLERFC"
Function Module..... "ARFC_DEST_SHIP"
Call Destination.... "WORKFLOW_LOCAL_100"
Source Server....... "zacwtbsrv064_EP1_00"
Source IP Address... "10.27.191.64"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
    Termination occurred in the ABAP program "CL_SWF_CNT_CONTAINER==========CP" -
     in "IF_SWF_CNT_CONVERSION~TO_XML".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 67
    of the (Include) program "CL_SWF_CNT_CONTAINER==========CM02J".
Source Code Extract
Line SourceCde
   37     lv_xml_table_req = 'X'.
   38   ENDIF.
   39   IF xml_stream IS REQUESTED.
   40     lv_xml_stream_req = 'X'.
   41   ENDIF.
   42
   43   IF use_xslt NE space.
   44
   45     cl_swf_cnt_conversion_service=>to_xml_xslt(
   46       EXPORTING
   47         container                  = me
   48         include_null_values        = include_null_values
49         include_initial_values     = include_initial_values
50         include_change_data        = include_change_data
51         include_texts              = include_texts
52         include_extension_elements = include_extension_elements
53         save_delta_handling_info   = save_delta_handling_info
54         xml_dom_req                = lv_xml_dom_req
55         xml_table_req              = lv_xml_table_req
56         xml_stream_req             = lv_xml_stream_req
57       IMPORTING
58         xml_dom                    = xml_dom
59         xml_table                  = xml_table
60         xml_stream                 = xml_stream
61         xml_rendered_size          = xml_rendered_size
62       EXCEPTIONS
63         conversion_error           = 1
64         OTHERS                     = 2
65            ).
66     IF sy-subrc <> 0.
>>>>       RAISE conversion_error.
68     ENDIF.
69
70   ELSE.
71
72     cl_swf_cnt_conversion_service=>to_xml_ixml(
73       EXPORTING
74         container                  = me
75         include_null_values        = include_null_values
76         include_initial_values     = include_initial_values
77         include_typenames          = include_typenames
78         include_change_data        = include_change_data
79         include_texts              = include_texts
Could you please help me out in resolving this issue?
Is there any need to apply any OSS notes?
Thanks in advance. And reward points will be given for the solution..
Thanks,
Ravikumar.

Hi,
U will receive this error when ever it is not possible to achieve runtime conversion.
i.e When u r passing the data from one type variable to another type if the conversion is not defined or not possible u will get this dump. Just analyze the dump in ST22.
Look at this simple example. Here i am trying to assign 101.23 to l_p for which length is not sufficient. So i will get dump. But if u do the same with character variable it will truncate the data.
DATA: l_p(2) TYPE P DECIMALS 2.
l_p = '103.23'.
WRITE l_p.
So check the place where u r getting the dump. It must be some assignment statement.
Hope it gave some idea on ur case.
Thanks,
Vinod.

Exception condition "FAILED" raised.

My TRM functional consultant has been trying to run end of day processes in the Transaction RKLNACHT but the following dump appears:
Runtime Errors         RAISE_EXCEPTION
Date and Time          16.05.2008 10:33:21
Short text
Exception condition "FAILED" raised.
What happened?
The current ABAP/4 program encountered an unexpected
    situation.
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
A RAISE statement in the program "CL_POSITIONSERVICE_TRQ========CP" raised the
     exception
condition "FAILED".
Since the exception was not intercepted by a superior
    program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
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:
"RAISE_EXCEPTION" " "
    "CL_POSITIONSERVICE_TRQ========CP" or "CL_POSITIONSERVICE_TRQ========CM00I"
    "GET_POSITIONS_BY_DIFF"
or
"CL_POSITIONSERVICE_TRQ========CP" "FAILED"
or
"RKLNACHT " "FAILED"
    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.
System environment
SAP-Release 700
Application server... "tetradev"
    Network address...... "192.168.1.81"
    Operating system..... "SunOS"
    Release.............. "5.9"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
Database server... "tetradev"
    Database type..... "ORACLE"
    Database name..... "DEV"
    Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
    created (date)... "Aug 31 2006 20:59:23"
    create on........ "SunOS 5.9 Generic_117171-13 sun4u"
    Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 16192
EM...... 16759392
Heap.... 0
Page.... 180224
MM Used. 10608952
MM Free. 1957592
User and Transaction
Client.............. 300
    User................ "DARLINGTON"
    Language key........ "E"
    Transaction......... "KLNACHT "
    Program............. "CL_POSITIONSERVICE_TRQ========CP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    Termination occurred in the ABAP program "CL_POSITIONSERVICE_TRQ========CP" -
     in "GET_POSITIONS_BY_DIFF".
    The main program was "RKLNACHT ".
In the source code you have the termination point in line 37
    of the (Include) program "CL_POSITIONSERVICE_TRQ========CM00I".
Source Code Extract
Line      SourceCde
7              l_selector         TYPE REF TO cl_flow_selector_dif,
    8      * workarea for table with positions
    9              l_tab_position     TYPE trqy_position_obj,
   10              l_position         TYPE REF TO if_position_trq,
   11              l_count            type i.
   12
13      * initialization
14        CLEAR re_tab_position.
   15
16      * Get positions for ranges
   17        CALL METHOD ca_pos_identifier_dif=>agent->get_persistent_by_range
   18          EXPORTING
19            im_context     = trqco_con_trq
   20            im_ranges      = im_ranges
   21          RECEIVING
22            re_identifiers = l_tab_identifier.
   23        CHECK NOT l_tab_identifier IS INITIAL.
   24
25        LOOP AT l_tab_identifier INTO l_identifier.
   26
27          l_selector = l_identifier->derive_selector( ).
   28
29      *   get TRQ positions for selectors
   30          CALL METHOD read_positions_by_selector
   31            EXPORTING
32              im_selector      = l_selector
   33            RECEIVING
34              re_tab_positions = l_tab_position.
   35          DESCRIBE TABLE l_tab_position LINES l_count.
   36          IF l_count <> 1.
>>>>>            raise failed.
   38          ENDIF.
39          APPEND LINES OF l_tab_position TO re_tab_position.
   40        ENDLOOP.
41
42      ENDMETHOD.
Contents of system fields
Name          Val.
SY-SUBRC      0
SY-INDEX      0
SY-TABIX      2
SY-DBCNT      1
SY-FDPOS      0
SY-LSIND      0
SY-PAGNO      0
SY-LINNO      1
SY-COLNO      1
SY-PFKEY
SY-UCOMM
SY-TITLE      End-of-Day Processing
SY-MSGTY      E
SY-MSGID      64
SY-MSGNO      030
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO      0
SY-DATUM      20080516
SY-UZEIT      103319
SY-XPROG      SAPLSBAL_DB
SY-XFORM      %_CONTROL_EXIT_DYNPRO
Does anyone have suggestions as to how I can solve this problem?
Assistance will be appreciated.

bumping...any suggestions...welcome

Exception condition "INTERNAL_ERROR" raised

Runtime Errors         RAISE_EXCEPTION
Date and Time          21.08.2014 21:53:43
What happened?
     The current ABAP/4 program encountered an unexpected
     situation.
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
     A RAISE statement in the program "SAPLCEI0" raised the exception
     condition "INTERNAL_ERROR".
     Since the exception was not intercepted by a superior
     program, processing was terminated.
     Short description of exception condition:
     For detailed documentation of the exception condition, use
     Transaction SE37 (Function Library). You can take the called
     function module from the display of active calls.
How to correct the error
    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:
    "RAISE_EXCEPTION" " "
    "SAPLCEI0" or "LCEI0U30"
    "VC_I_GET_CONFIGURATION"
    or
    "SAPLCEI0" "INTERNAL_ERROR"
    or
    "SAPMSSY1 " "INTERNAL_ERROR"
    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.
System environment
    SAP-Release 700
    Application server... "sap01717"
    Network address...... "10.61.89.105"
    Operating system..... "Linux"
    Release.............. "2.6.40-0.8-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 15
    Shortdump setting.... "full"
    Database server... "sap01716"
    Database type..... "ORACLE"
    Database name..... "QWT"
    Database user ID.. "SAPDAT"
    Terminal................. "10.61.31.114"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Mar 17 2013 18:46:25"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr121116"
    Database version. "OCI_102, 11.2.0.3.0, V1, default"
    Patch level. 420
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 16759232
    Heap.... 0
    Page.... 16384
    MM Used. 14978448
    MM Free. 1777544
User and Transaction
    Client.............. 500
    User................ "RFC_TAULIA"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "53F6515E320E5BBBE10000000A3D5969"
    Program............. "SAPLCEI0"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "########"
    Database Release.... 720
    Kernel Release...... 720
    Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. "###"
    User................ "############"
    Transaction......... " "
    Call Program........."SAPJCo30"
    Function Module..... "/TAULIA/CT_RFC_BUS_DOC_GET"
    Call Destination.... "SAPR3"
    Source Server....... "SWDETDOLPHPODD"
    Source IP Address... "10.61.31.114"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
Information on where terminated
    Termination occurred in the ABAP program "SAPLCEI0" - in
     "VC_I_GET_CONFIGURATION".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 259
    of the (Include) program "LCEI0U30".

Hi Arun,
the exception INTERNAL_ERROR of function module VC_I_GET_CONFIGURATION hasn't been caught, which leads to a short dump.
Check, where INTERNAL_ERROR is raised in your system In our system the only remaining code is after call of function module CUCQ_GET_CONFIGURATION_PARAMS.
Please try to debug, why this exception is raised.
Regards,
Klaus

Error in BEx Analyzer Exception condition "HIERARCHY_NOT_FOUND" raised.

When i run report 0FIAA_C02_Q1001 with input variable as "My controlling area" i get this error.
ERROR:
Exception condition "HIERARCHY_NOT_FOUND" raised.
ERROR Analysis:
A RAISE statement in the program "SAPLRRH1" raised the exception
condition "HIERARCHY_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Please sugggest how to resolve this.
HOw to see which hierarachy it is talking about?
Thanks,
Harika.
Edited by: harikag on Oct 12, 2011 7:11 AM
Edited by: harikag on Oct 12, 2011 7:12 AM

HI
FOr 0Costcenterinfoobject->attribute tab->no hierarhcies
                                         ->hierarchy tab->i see hierarchy tables are enabled.But when i click on
                                             "MaintainHierachy" there are no hierrachies in it.
For 0CO_AREA infoobject->attribute tab->0CCA_HIENM,0PCA_HIENM hierarchies are there.
                                         ->hierarchy tab->nothing is there.
please help out.I didnt load 0COSTELMNT_0102_HIER master datasource in CO_IO.
Is that the reason?

RFC_ERROR_SYSTEM_FAILURE -Exception condition 'INCONSISTENCY' rasied .

Similar Messages

Maybe you are looking for