Com.sap.dictionary.ccts.Date Issue

I am not able to find com.sap.dictionary.ccts.Date under my local dictionary>Data type>simple type.
please tell me what to do.
Sriram

Hi Sriram
If you are not able to find then you can create the simple type then it will available in the dictionary
Simple type name: Date
Simple type package: com.sap.dictionary.ccts.Date
Best Regards
Arun Jaiswal

Similar Messages

Com.sap.dictionary.runtime.DdException: 'WD_FLIGHTLIST_RFC_METADATA_DEST

Hi, finally i obtain the correct configuration in jco destination, i press in test and work, the test is satisfactory..... but when i start the application appear this error: "com.sap.dictionary.runtime.DdException: 'WD_FLIGHTLIST_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_FLIGHTLIST_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)"
What happend?
Thanks,

Victor,
While configuring 'WD_FLIGHTLIST_RFC_METADATA_DEST' you should choose Connection type as 'Dictionary Meta Data'. The message shows that you have choosen Connection type as 'Application Data.
Remove and recreate the JCO Destination for 'WD_FLIGHTLIST_RFC_METADATA_DEST' .
Regards
Abhilash

Unable to resolve "Missing Required java Project : com.sap.dictionary"

HI ,
Iam praveen , working on web dynpro's , I imported a project template and repaired it and all the .jar files are included in the project . But still am getting some errors like the below...
Error               Missing required Java project: com.sap.dictionary.services.     com.sap.dictionary.runtime          Build path
Error               Missing required Java project: com.tssap.sap.libs.logging.     com.sap.dictionary.runtime          Build path
Error               Missing required Java project: com.tssap.sap.libs.xmltoolkit.     com.sap.dictionary.runtime          Build path
Error               Missing required Java project: org.eclipse.core.resources.     com.sap.dictionary.runtime          Build path
Error               Missing required Java project: org.eclipse.ui.     com.sap.dictionary.runtime          Build path
Error               The project was not built due to classpath errors (incomplete or involved in cycle).     com.sap.dictionary.runtime
can anyone help me in resolving these problems, i have been trying to resolve this problem , but failed. send me solution if any one can solve it
-Praveen

Hi praveen,
your project refers to a dictionary that you haven't in the project. Besides, right click on the WD project and check all the external references to others projects. You must open the external projects pointed by your WD.
Hope this help you,
Vito

ClassNotFound for com.sap.dictionary.designtime.generation.TemplateHelper

Just installed app server and developer studio. Completed first web dynpro application, but it will not run. Get "Page cannot be displayed" in browser. Get ClassNotFound for com.sap.dictionary.designtime.generation.TemplateHelper. You can only see this by the way, when running the tool in "console" mode. I don't see the file in the files that I downloaded. There is no com.sap.dictionary.designtime.generation. Do others have this library?

Hi,
check your Jco destination in the content administrator http://hostname:port/webdynpro/dispatcher/sap.com/tcwdtools/Explorer, goto Maintain Jco Destinations and look for jco SAP_R3_HumanResources and SAP_R3_HumanResources_MetaData.
The first one should use SSO/ticket and other one should use a system user that is used to sync metaData.
regards,
sangeeta

ERROR:com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException

Dear All,
We have taken a par file from another project and deployed in the J2EE engine using SDM.It was succesfully deployed with out any warnings.I have created an iview also.When we are trying to access that i view i am getting an error as follows:
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    ... 51 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Version     null
DOM version     null
Client Type     msie6
Client Type Profile     ie6
ActiveX     enabled
Cookies     enabled
Frames     enabled
Java Applets     enabled
JavaScript     enabled
Tables     enabled
VB Script     enabled
Server
Web Dynpro Runtime     Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Mon Mar 03 21:11:10 GMT+05:30 2008
J2EE Engine     7.00 patchlevel
Java VM     Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system     Windows 2003, version: 5.2, architecture: ia64
Session & Other
Session Locale     en
Time of Failure     Thu Apr 10 14:31:31 GMT+05:30 2008 (Java Time: 1207818091497)
Web Dynpro Code Generation Infos
local/WDHolidayCalendar
SapDictionaryGenerationCore     7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:24:21[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     (unknown)
SapGenerationFrameworkCore     7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:12:57[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:30:00[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:13:46[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:13:38[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:21:59[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:26:52[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:45:29[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCore     7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:30:11[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:45:29[UTC], changelist=413534, host=pwdfm101)
sap.com/tcwddispwda
No information available     null
sap.com/tcwdcorecomp
No information available     null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:com.bel.holidaycal.model.types.WDModelHolical:com.bel.holidaycal.model.types.Zhrt029 could not be loaded: com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
     at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:234)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:448)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:386)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:415)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
     at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:212)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
     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.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     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.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
     at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
     at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
     at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
     at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
     at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
     at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
     ... 49 more
I have created the JCO connections also ,i am able to test them also.I have imported the same into NWDS and deployed the application , its deploying but the out put is the same error.
I have cross checked the models and found that the Model is there in the model types.
Can any one help me regarding this.
Waiting for the response ASAP.
Thanks
Ravi.S

Hi,
I think you mean ear file and not par file. Check these threads. The exception is mentioned to be because of JCo problems only.
Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
WDTypeNotFoundException: type model.types.Zbtr_Wbselement could not be load
WebDynpro using BAPI has an error
Regards,
Harini S

Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist

Hi there,
same Thread I post in "Portal Developement". Now I try my luck in ths category...
we implement ESS (ERP2004 with WebDynpros) in our testsystem, but we got an error and don´t know what to do...
System Landscape:
- mySAP Enterprise Portal 6.0 SP17
- Java Application Server (excluding from HR)
- mySAP ERP2004 HR-System
The Connections from the portal runs to the Java-App-Server, not direct to the HR-System (HR-System has no Java Installation and our Customer don´t want a installation, because it could be a bad performance)
We implement the Jco´s and fill out the usermapping. If we want to call the firstpage of the new ESS-Role we get this error.
Can anyone help us? Do we need some installations?
Best regards
Christian
Error
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
... 54 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4015.00.0000.20051123162612.0000 (release=630_VAL_REL, buildtime=2005-12-14:21:51:22[UTC], changelist=377533, host=PWDFM026)
J2EE Engine No information available
Java VM Classic VM, version:1.4.2, vendor: IBM Corporation
Operating system AIX, version: 5.2, architecture: ppc64
Other
Session Locale de
Time of Failure Thu Jan 11 16:14:11 GMT+00:00 2007 (Java Time: 1168532051021)
Web Dynpro Code Generation Infos
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
sap.com/tcwddispwda
No information available
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.xss.ser.xssmenu.model.types.P_Pernr could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:314)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:669)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:855)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:158)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:143)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:135)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:628)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:773)
at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeader.onInit(VcXssMenuHeader.java:196)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeader.onInit(InternalVcXssMenuHeader.java:225)
at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeaderInterface.onInit(VcXssMenuHeaderInterface.java:162)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface.onInit(InternalVcXssMenuHeaderInterface.java:144)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface$External.onInit(InternalVcXssMenuHeaderInterface.java:220)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:466)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:179)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
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:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
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(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 52 more

Hi,
uhm... good question, long time ago...
Error should be in the JCO-Destinations, where you can choose a targetsystem for each Jco-Destination.
Since them we installed a java on the abap-system, so we have a doublestack.
In the Jco Destiantions must be the ABAP-System.
Application via SAPTicket and MetaData via fix User like DDIC.
Regards
Christian

FPN error: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException

Hi, all.
I am trying to initiate a webdynpro page from the producer to the consume portal via RDL. It works fine for a day. Then it starts giving me the error:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page ...
This error cannot be cleared by clearning the FPN cache or synchronize with the producer. Of course, you can also delete the page from the consumer and copy it over from the producer again. It will work. But this is not a good workaround for a production system. We also don't know the cause either. Here is the stack trace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:528)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
     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:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     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:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.portal.fpn.exception.unchecked.FpnUnMarshallingException: Could not find a marshaller for 'com.sapportals.portal.page' from path 'pcd:consumer_content/DEP/portal_content/ca.ottawa.sap.supportcentre/ca.city.ottawa.OttawaRoles/ca.city.ottawa.ManagerInfo/ca.city.ottawa.ManagerInfo-FinanceOnly/ca.city.ottawa.ManagerInfo_MSS_Finance/ca.city.ottawa.Mileage_Parking_Managers'
     at com.sap.portal.fpn.marshal.ContentMarshallerService.unMarshallDLChain(ContentMarshallerService.java:323)
     at com.sap.portal.fpn.entrypoint.RuntimeFederatedPersistance.retrieveDLRemoteState(RuntimeFederatedPersistance.java:103)
     at com.sap.portal.fpn.FpnRuntimeService.bringRemoteState(FpnRuntimeService.java:134)
     at com.sap.portal.fpn.FpnRuntimeService.doFpnLookup(FpnRuntimeService.java:97)
     at com.sap.portal.fpnprovider.fpn.GenericContext.lookup(GenericContext.java:49)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:72)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:526)
     ... 31 more
Caused by: com.sap.portal.pcm.OperationFailedException: Creating DL outside the PCD
     at com.sap.portal.pcm.iviewserver.CiViewSLObjectsManager.instantiateDescriptor(CiViewSLObjectsManager.java:687)
     at com.sap.portal.pcm.page.PagesSrv.instantiateDescriptor(PagesSrv.java:79)
     at com.sap.portal.pcm.page.PagesSrv.instantiateDescriptor(PagesSrv.java:71)
     at com.sap.portal.fpn.marshal.IViewMarshaller.instantiateRelatedItemDescriptor(IViewMarshaller.java:582)
     at com.sap.portal.fpn.marshal.IViewMarshaller.performSemanticActions(IViewMarshaller.java:506)
     at com.sap.portal.fpn.marshal.PageMarshaller.performSemanticActions(PageMarshaller.java:499)
     at com.sap.portal.fpn.marshal.IViewMarshaller.unmarshalResolvedDLChain(IViewMarshaller.java:715)
     at com.sap.portal.fpn.marshal.PageMarshaller.unmarshalResolvedDLChain(PageMarshaller.java:328)
     at com.sap.portal.fpn.marshal.ContentMarshallerService.unMarshallDLChain(ContentMarshallerService.java:320)
     ... 38 more
So far I found nothing on OSS or SDN on this FpnUnMarshallingException. Has anyone seen this error before?
Thanks.
Jonathan.
Edited by: Jonathan Ma on Apr 23, 2009 12:25 AM

Hi Jonathan,
you may deactivate the GPN cache as well as the old navigation cache. About the GPN there is note 1172433. Both caches are not used in FPN scenario and can lead to such strange problems. If this won't help please open a support message for this that we can analyse further.
Cheers,
Anja

VPD date issue between 10.1 and 10.2 databases

I have uncovered an issue today with VPD against date fields. The issue came up at a client site on a 10.2 database. When I got back to the hotel and tried this on my own database, which is 10.1, I got no issue and everything worked ok.
Therefore, I am asking if anyone is able to try out the following for me on different Oracle databases and platforms and let me know whether it worked for you or not. I'd like to compile a list of database versions and platforms on which the issue occurs.
Step 1: create this table as a user
CREATE TABLE TST_DATE AS (
SELECT 1 PERSON_UID,
Trunc(SYSDATE) BIRTH_DATE,
To_Char(Trunc(SYSDATE), 'DD-MON-YYYY') CHAR_DATE,
123456 TAX_ID,
'Smith, Michael B.' FULL_NAME FROM dual);
Step 2: grant select rights on the table
GRANT SELECT ON TST_DATE TO PUBLIC;
Step 3: switch your login to SYS and run this script:
CREATE OR REPLACE FUNCTION F_CHECK_ITEM_TST(p_object_schema in varchar2, p_object_name varchar2)
RETURN VARCHAR2 IS
V_PREDICATE VARCHAR2(2000) := '1 = 2';
BEGIN
RETURN(V_PREDICATE);
END F_CHECK_ITEM_TST;
Step 4: As SYS, run this to grant access rights over the function
GRANT EXECUTE ON F_CHECK_ITEM_TST TO PUBLIC;
Step 5: As SYS, run this to enable the policy
BEGIN DBMS_RLS.ADD_POLICY(
OBJECT_SCHEMA => 'DRAKE',
OBJECT_NAME => 'TST_DATE',
POLICY_NAME => 'SecByTST',
FUNCTION_SCHEMA => 'SYS',
POLICY_FUNCTION => 'F_CHECK_ITEM_TST',
STATEMENT_TYPES => 'SELECT',
POLICY_TYPE => DBMS_RLS.DYNAMIC,
SEC_RELEVANT_COLS => 'BIRTH_DATE',
SEC_RELEVANT_COLS_OPT => DBMS_RLS.ALL_ROWS);
END;
Note: in the above policy change the OBJECT_SCHEMA name to be the name of the user who owns the table you created in Step 1
Step 6: Go into Discoverer Admin and import the table as a new folder.
Be sure to uncheck the "Date hierarchies" box and set "Default aggregate on data points" to detail. Grant access to any user.
Step 7: Using Desktop or Plus, log in as that user then try to query the folder with the date not included, there should be no problem.
Step 8: Now try to query with the date included
On my 10.2 database I get ORA-24334: no descriptor for this position. This happens when logged into Discoverer as the table owner, EUL owner or any other user. However, when logged into Discoverer as SYS which is exempt from all VPD policies, there is no error when the date is included.
We tried this in Discoverer Desktop, Plus and Viewer with the same results in all three. We can successfully query the table from SQL*Plus, SQL Developer and TOAD.
There also seems to be no issue at all with the 10.1 database so there seems to be an issue between Discoverer and the 10.2 database.
What do you think?
P.S. to cancel the policy use this script when logged in as SYS:
EXEC DBMS_RLS.drop_policy(
OBJECT_SCHEMA => 'DRAKE',
OBJECT_NAME => 'TST_DATE',
POLICY_NAME => 'SecByTST');
This same information is available on my blog in a more readable format here:
http://learndiscoverer.blogspot.com/2006/12/vpd-date-issue-between-101-and-102.html

Hi Rod
Well don't you just love Oracle. Obviously, whatever tests were done for certifying Discoverer against the 10.2 database did not include checking VPD policies. This merits a blog entry from me.
Your workaround for V_PREDICATE VARCHAR2(2000) := 'BIRTH_DATE=TO_DATE(''01-JAN-0001'')'; works. However, I had to write a new function to do this because my real function was trapping about a dozen items at the same time, some dates, some numbers and some varchars - exactly the way that the Oracle example code shows it in the 10.2 database manual.
So what I did was to create a new function that only handles dates and added a dedicated policy that works with only that function. Unfortuately, because I have many dates to manage, I was unabe to hard code the BIRTH_DATE so here is what I did:
V_PREDICATE VARCHAR2(2000) := 'SYSDATE = TO_DATE(''01-JAN-0001'')';
This works perfectly and Discoverer stopped complaining. It just has two policies on the same table for different data items. Isn't VPD cool? I'm hooked.
I really appreciate your time and effort on this. Now, let's see what Oracle support make of the issue because I raised a service request last night. No reply yet I'm afraid.
Best wishes
Michael

Error (com.sap.xss.per.model.mac.types.Hrxss) in ESS personal Information

Hi ALL,
When I click on Address Tab under personal Information, I am getting this exception
com.sap.dictionary.runtime.DdException: Type com.sap.xss.per.model.mac.types.Hrxss_Per_Subtype_Allowed does not exist
Please provide your inputs
Thanks
Rishi

Hi Rishi ,
Your server is dual stack?
if it is dual stack . did u maintain abap system as technical system for maintaining jco settings?
check the below thread
ESS iViews - 500 Internal Server Error
see below links for more information
http://buzz.omgili.com/preview/aHR0cHM6Ly9mb3J1bXMuc2RuLnNhcC5jb206NDQzL3RocmVhZC5qc3BhP3RocmVhZElEPTkwMDc1NA==
com.sap.dictionary.runtime.DdException
Koti Reddy

${com.sap.datasource.default} for a remote ORACLE

Hello!!!:
At the data-source-aliases.xml file are the following lines:
<?xml version="1.0"?>
<data-source-aliases>
<aliases>
<data-source-name>
${com.sap.datasource.default}</data-source-name>
<alias>CAR_RENTAL_POOL</alias>
</aliases>
</data-source-aliases>
I'm using a remote ORACLE instead the default SAPDB and I need to know what I have to put in the place of ${com.sap.datasource.default} (which are the parts of the path or complete name ? where I should look for them?)
Thanks for your time.

Hi Javier,
You need to deploy the jdbc driver and create data source as defined in
Deploy JDBC Driver
http://help.sap.com/saphelp_nw04/helpdata/en/ab/082484173ae045ab8dad8a41d33da3/frameset.htm
Define DataSource
http://help.sap.com/saphelp_nw04/helpdata/en/ab/082484173ae045ab8dad8a41d33da3/frameset.htm
Once you define the datasource, you can use it in your data-sources-aliases.xml
Hope this helps
Thanks and Regards,
Rohit Jaiswal

Local Dictionary Simple Data Types - RFC Model

Hi,
can somebody help out with this error message:
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.global.wdschulung3.types.String could not be loaded: com.sap.dictionary.runtime.DdException:
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
is it something to do with the JCO Connection?
I have checked in the WebDynpro Content Admin - and I don't get a green or red Status Symbol - in fact it's just grey - and buttons for "create JCO Connection" ars disabled
thanx for help,
matthias

Hi Bhavik,
thanks for the links - now i configured the sld supplier in visual admin tool and it looks good. Connection test is successful.
Now I was also able to create the JCO Connection in webdynpro content administrator for wd_model_dest and wd_metadata_dest - looks good, and I get a green icon.
Unfortunately testing the jco-connection still fails... I get this error message:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=x1t GROUP=SPACE R3NAME=X1T MSSERV=sapmsX1T PCS=1 ERROR service '?' unknown TIME Mon Sep 12 14:24:20 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
Somebody experienced this before?
thanx once more,
matthias
Message was edited by: matthias kasig

RFC Data not sending to Destination ( com.sap.aii.af.rfc.afcommunication.Rf

Hi Experts,
 i have created a TCP/IP connection in sm59 as ID4 with R/3 details. now i am calling a function module like this.
call function 'Z_CBT_RFC_SALESPERSON'
 exporting
 p_sdate = p_sdate
 p_edate = p_edate
 tables
 isalesperson = i_salesperson
 exceptions
 no_data_found = 1
 others = 2.
if sy-subrc <> 0.
 message e111(zi) with text-101.
endif.
if not i_salesperson[] is initial.
 call function 'Z_CBT_RFC_SALESPERSON' in background task destination
 'ID4'
 exporting
 p_sdate = p_sdate
 p_edate = p_edate
 tables
 isalesperson = i_salesperson.
 write: text-103.
else.
 message e111(zi) with text-101.
 exit.
endif.
commit work .
 i am getting a problem that some times the data is exported to XI system but some times not.
 and in sm58 i am getting an error message for this execution as
KOMMP2 Z_CBT_RFC_SALESPERSON ID4 05/28/2007 02:30:10 Commit fault: com.sap.aii.af.rfc.afcommunication.R 95B7F6ADB04C465A8502002E brcpfd04 SE38 ZSIOPSP 105 0000
Commit fault:
com.sap.aii.af.rfc.afcommunication.RfcChannelMismatchExcept
 For all execution iam getting this error. Anyone call tell me how to resolve this issue.
 Please suggest me, do i need any modification in the program and in connection settings.please do the needful as soon as possible.points will be awarded for all answers.
Thanks in advance.
Thanks & Regards,
Poorna

Hi Sergio,
 Actually we are using the same connections for all the interfaces the we are developing in development system, and XI guys are using the same Program-ID in all their interfaces to configure.
 So when we are triggering the interface, some times the messages are going to XI, but sometimes no data is going.
 and let me know, if any more settings are required in sm59.
Thanks & Regards,
Poorna.

SSO issue in the production server,com.sap.mw.jco.JCO$Exception: (103)

com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: This system rejects all logons using SSO tickets
in the production server.....
while testing the jco maintained for Ess applications.
if i go for uidpw method for modeldata destination i am getting the error. in the Ess pages that administrtor not in this peroid(administrator with which id i maintained jco destination)
if i assign one employee to the admin in pa30......for every employee getting the same details of admin)
I guess this problem with modeldata ......i should maintain the usermanagement method for modeldata jco destination is logon ticket.
while maintainig that ping is successfull but getting the above error.
it is the problem with production server.......of E.P
in dev and quality everything is working fine.
plz help me out.
thankyou
swapna

Hi Swapna,
Please check the logon group properties for SAP system in t-code SMLG. If there is any issue with logon group then it might cause for this issue.
Refer to [Click here|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20configure%20the%20jco%20destination%20settings.pdf] and [System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?QuickLink=index&overridelayout=true]
Hope it will helps
Regards, Arun Jaiswal

Com.sap.aii.adapter.file.ftp.FTPEx: 550 You are not allowed to issue this

hi All,
We are getting below error while connecting to an FTP location through File Adapter:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: An error occurred while connecting to the FTP server XYZ. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 You are not allowed to issue this command'. For details, contact your FTP server vendor.
Also when we tried to connect to this FTP location through PI server we able to connect, but when we connect to it through channel we are getting above error.
Please Help!
Thanks,
Mayank

hi All,
The usedid we are using to connect to FTP location has appropriate access to write(we have an receiver file adapter) the files, when we connected to FTP location from PI server using same useid(as used in channel) we are able to connect to FTP location and also able to write the file there.
Now error soming is:
An error occurred while connecting to the FTP server XYZ. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Operation is not supported under Connect:Enterprise FTP server.'. For details, contact your FTP server vendor.
Thanks,
Mayank

Intermittent issue in PI-com.sap.aii.af.ra.ms.api.MessageExpiredException

Hi everbody,
We are with Intermittent problem in SAP PI 7.0.
Some messages have this error below:
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessageExpiredException:
Message 4bdefeac-f3e8-01de-e100-8000ac103265(INBOUND)
expired</SAP:AdditionalText>
The error above is appearing in Synchronous messages in trx sxi_monitor.
We read the note 730870 and the timeout parameters is ok.
We tried to stop/start in 'SAP XI AF CPA Cache' and 'SAP XI AF Messaging' but it not worked.
We have one message in a SAP but I think they do not have idea yet.
The adapters are involved are RFC and SOAP.
We changed the parameters:
- 'xiadapter.inbound.timeout.default' from 180000 to 300000 .
- 'syncMessageDeliveryTimeoutMsec' from 300000 to 600000 .
- 'syncMessageRemover.checkInterval' from 60 to 5 .
Please, could you have some idea to resolve this issue ?
ps: The error started after the stop/start for renew certification in keystore (j2ee) .
Best Regards,
Victor Yamanaka

Hi victor,
could you please refer the Note 791379
Extract from a FAQ :
At the beginning of a synchronous RFC call the RfcAdapter (sender channel) builds up the XI request-message and will send this to the Adapter Engine with a timeout. After this it will wait till the response-message reaches or the timeout expires. In case of timeout the exception named above is thrown. The timeout used by RfcAdapter for synchronous calls can be configured for the whole RfcAdapter as a property of the RfcAdapter J2EE Service. To change it's value open the service properties sheet like and change the value of "syncMessageDeliveryTimeoutMsec". Notice that this value is specified in milliseconds. After changing the property store the properties by clicking the save-button (disk symbol) on top of the page.If a similar error messages is shown for a receiver channel the timeout setting is done in the inbound XI-Adapter of the Adapter Engine and not via the above described setting in the RFC-Adapter. The value of xiadapter.inbound.timeout.default from J2EE Service 'SAP XI Adapter: XI' is used in this case.
similar forum post :com.sap.aii.af.ra.ms.api.MessageExpiredException
see if you have not referred this already.
Regards,
Srinivas

Com.sap.dictionary.ccts.Date Issue

Similar Messages

Maybe you are looking for