Error while creating Logical Data Object Model

Can anyone from Informatica help me on this ?

Hello Everyone , I am creating new objects in Informatica BDE 9.6.1 . While I trying to create a new Logical Data Object Model using the Customer_Order.xsd file I am getting the error : [MBCM_E0031 ]MIMB HOME directory is not valid . I do not see anything in the drop-down list for Model Type .Kindly help . RegardsSatyendra

Similar Messages

Error while creating logical file using transaction FILE

Hello there,
I am facing an error while creating Logical File name definition using transaction FILE
This is the input which I'm trying to give
Logical file name: ZTEST
Name : ZTEST
Physical file : ZTEST_1<DATE><TIME>.csv
Data format: ASC
Application area: BW
Logical path:ZTEST_1_DATAOUT
when I tried to save it throws me an error like ASSIGN_SUBSTRING_NOT_ALLOWED
Please help.

Hi,
Please check the OSS Notes :
Note 792061 - SP Case Locator: Dump: ASSIGN to a substring isn't allowed.
SAP Note 1297989 - Short dump ASSIGN_SUBSTRING_NOT_ALLOWED
Hope this solves the problem.
-Vikram

Error while creating Vacancy requisition object (NB) after upgrading EHP4

Hi All,
We had alreay E-Rec system with EHP2 and using last 1 year. Now based on Client requirement, we have upgrdaed to EHP4. After completing EHP4 upgradation, we are getting error while creating vacancy requisition object after all level of approval.
Can any body help how to resolve this issue?
Thanks in advance.
Regards,
Sreelatha

Hi
Hope SAP Note 1241014 will be useful to you.
Best Regards
Reddy

Error while creating requirements data in pendulum list indirect sales.

hi all,
i am getting the following error while creating requirement data in pendulum list indirect sales. t - code - /BEV4/PLAN
" ERROR OCCURED WHILE DETERMINING PERIOD IDENTIFIER""
-- help would be much appreciated..
thanks in advance
leo

var spObj = $().SPCascade({
destListColTitles: ['Continent','Country','State','City'],
srcListColInternalNames: ['Continent','Country','State','Title'],
srcListName: 'CitiesLookupList',
srcListFilterCAMLQuery: "<Query><Where><Contains>
<FieldRef Name='Continent'/><Value Type='Text'>America</Value>
</Contains></Where></Query>"
spWebURL: 'http://sharepointurl',
getDataOnly: 'false',
debug: 'true',
});

No Functional Area Found Error while creating service data in me22n

Hello,
While creating service data for a purchase order in ME22n I am getting error like " No functional area found" .
Please tell me how to maintain the Functional area for a particular GL account
In the help i can found that we can find the functional area "The functional area can be determined either using the cost element, the account assignment object (such as the cost center or order)"
How we can determine this please through some light on this statement.
Thanks
Pradeep
Moderator message: not directly related to ABAP development, please post again in the appropriate functional forum.
locked by: Thomas Zloch on Oct 15, 2010 9:55 AM

Hello Madhav,
You have to maintain your 'business transaction profile' (SPRO->CRM->IC Web->Business Transaction->Define bus. trans. prof.) in the customizing and assign that profile to your IC WebClient profile (the one you assigned in the org. model)
In the business transaction profile you must make sure that at least one transaction type (e.g. ZSRV) is assigned as 'Dependent business transaction' and that entry is flagged as 'Service'.
Also make sure that that transaction type (ZSRV) has leading business transaction category 'Service process' (BUS2000116).
This should solve your problem!
Kind regards,
Joost

Error while creating logical port for Consumer Proxy in SOAMANGER

Hi,
While creating logical port for my consumer proxy in SOAMANGER, I am getting the error shown below
SRT Framework exception: HTTP: Current user does not have the required authorization to access the HTTP destination
I have searched in the forums but none of the answers helped me.
I have specifed my PI user ID and password and the user has the followwing roles assigned to it.
SAP_BC_WEBSERVICE_SERVICE_USER
SAP_BC_WEBSERVICE_ADMIN_TEC
SAP_BC_WEBSERVICE_CONSUMER
SAP_BC_WEBSERVICE_ADMIN
Current user in the error message refers to the PI user that i have specified or the user with which i have logged in the backend ABAP system?
Please help me reslove this issue.
Thanks and regards
Sreehari Nambiar

Hi,
Please add the following roles as well.
SAP_BC_WEBSERVICE_ADMIN_BIZ
SAP_BC_WEBSERVICE_DEBUGGER
SAP_BC_WEBSERVICE_OBSERVER
Also make sure that you are doing the role comparison after adding all SAP* roles in your profile.
Let me know if this works?
Thanks,
Sridhar

Error while creating a callable object - User Interface

Hello,
When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
Is there any body who allready had somthing like this.
Greetings
Kurt

Hi Raja Akella,
I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
In the visual administrator i get the following errors.
Error 1
Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
[EXCEPTION]
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 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:299)
 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.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 2
Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 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:299)
 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.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 3
Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
thanks in advance
Kurt

Error while creating adaptive web service model

Hi All,
There is a requirement where the webdynpro application is deployed in backend system while the web service is created in the front end system. We need to connect to this web service and execute it in our webdynpro application to get response. For this we have created Logical Destination in backend system that points to the web service in the front end system.
The web service, when tested directly through Web Services Navigator, works fine.
Here, while creating an Adaptive Web Service Model in the webdynpro application, after giving name, package, destination name etc when I enter wsdl url and click on Next I am getting an error as u201CError in downloading the WSDL fileu201D.
The error log says u201Ccom.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException:Exception on creation of service metadata for WSDL URLu201D.
Even if I try to create model with url only by selecting u201CNo Logical Destinationsu201D, error remains the same.
What may be the reason for this and possible solution?
Appreciate an early response.
Regards,
Mitali

Hi
Plesae go thriugh the Wiki and the pdf file
https://wiki.sdn.sap.com/wiki/display/WDJava/FAQ-Models-AdaptiveWebService
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b2bc0932-0d01-0010-6d8e-cff1b2f22bc7&overridelayout=true
Thanks
Susmita

Error while creating logical port in SOAMANAGER

Hi,
Im consuming the webservice.While creating the new logical .Im getting the following error.
Error: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:401Unauthorizedhttp://vmtmasterdev.rune2emaster.rune2e.com:1080/sap/bc/srt/wsdl/sdef_Z_NUMBER/wsdl11/ws_poli
I have entered logical port name,description, URL for WSDL access.When i press enter i got the above eeror.
Please help me.
Regards,
Brahmaji

Hi,
tell me please wenn you run SOAMANAGER you have to apply an user Authentication or not?
If yes If the service that you want to configure is an Enterprise Service or Self-Modelled Service.
In case of Web Services Please Check again in The ICF Services under
sap/bc/srt/SAP and Check if your Service activated or not.
If you don´t have Access to SOAmanagement you can see the specified Roles hier
http://help.sap.com/saphelp_nw04s/helpdata/en/2b/07074155bcf26fe10000000a1550b0/frameset.htm
Regards
A.Labrache

Error while creating a system object for R3 in portal

Hi,
I am getting error while trying to create a system object in portal.
Following are the details I used :
Under WAS...
Web AS Host Name :<XXXX>:8001
Web AS path: /sap/bc/bsp/sap/
Web AS protocol : http
Under User management:
Authentication Ticket Type : SAP Logon Ticket
Logon Method :SAPLOGONTICKET
User Mapping Type : admin,user
Under Connector:
SAP Client : <Client NO>
SAP System ID : <System ID>
SAP System No : <System No>
System Type : SAP_R3
While trying with connection test... I am getting like this:
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
5. The host name <FQDN Server Name> was resolved successfully.
6. The server sapdwh01 could not be pinged successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
Kindly help.
Regards,
Niraj
Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

I created a SAP Transactional iView for transaction SE80.
Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
Got portal Runtime error :
Portal Runtime Error
An exception occurred while processing your request
Exception id: 12:57_11/12/08_0003_2795650
See the details for the exception ID in the log file.
Regards,
Niraj

Error while creating a new Dimension/Model in BPC 10.0 NW

Hello Experts,
I am using BPC 10.0 NW system.
When I try to create new Dimensions or Models I get the following Error Message.
"Error in Admin module or a component used by Admin module.
Failed to create SAP NetWeaver BI InfoObject for dimension."
I am assigned to all the needed task profiles to create Dimensions and Models.
Please assist me to resolve this issue.
Thanks & Regards,
Archana

Thanks Roberto.
The error was coming because while creating the user id "SAP_ALL" Profile was not assigned. So I was not able to create Dimensions and models.
Now the issue is solved.

Error while creating new entity object.

Hi all
I'm using Jdev 11.1.1.3. I want to create an entity object and Jdev issues an information error saying "Either this is not a valid name or an object with that name already exists."
I found that if the package I'm targeting for the new entity is called "com.test.model.whatever" I cannot create a EO called "Whatever".
I can't find any reference in the fusion developer guide that constraints the entity names to be allowed.
Is there a way to circumvent this issue or is this the way it should be?

Sudipto and Suresh, thank you very much for your replies.
I know that changing the package or entity name would work, but was expecting some other kind of workaround, something like giving a full qualified name on some xml or something to avoid the name clash or whatever the problem is.
I do not like packing all the entities together as it goes against my best practice of packing things that change together on the same package. Also I don't like suffix or prefix class names as it goes against my best practice of short descriptive names.
So well, I will have to tinker the names some more and meet you guys half way.
I will now mark this thread as answered, thanks again.

Error while creating logical port from WSDL in SOAMANAGER

Hi,
I am trying to create a logical port for the webservice TerritoryCRMBasicDataByIDQueryResponse_In with the WSDL
http://usciq9e.wdf.sap.corp:50077/sap/bc/srt/wsdl/sdef_TERRITORYCRMBASICDATABYIDQUERY/wsdl11/ws_policy/document?sap-client=506
In SOA Manager, I selected the proxy object and clicked on 'Create Logical Port' ,
gave the name and description for the port and set it as default.
The other settings are :
Configuration type : WSDL based configuration
WSDL base is : Via HTTP Access
Then I gave the address of the WSDL in the URL and the proper username and password. When I clicked on 'Apply Settings' I get the following error:
"Error when building binding view: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL "
Please advise me on how to approach the problem.
Thanks,
Sashi

Creating logical ports is done here:
http://help.sap.com/saphelp_nwpi71/helpdata/en/44/cc8fd368c873dfe10000000a11466f/frameset.htm

Error while executing logical data service:XP0006

Hi,
 
I have one physical dataservice which is caps.ds based on oracle database. I created one method in caps.ds by name gatCap(String param). basically this method will fetch the data from the database based on input parameter. This method is working fine in physical data service. . Now I created one logical dataservice named as Test.ds from this physical dataservice. I added one method getCaps(string param) method in Test.ds. Noe if i try to test this method in workshop I am getting the following error. .System error
weblogic.xml.query.exceptions.XQueryTypeException: ld:NewDSProj/Test.ds, line 26, column 5: {err}XP0006: "element {ld:NewDSProj/Caps}Caps { {http://www.w3.org/2001/XMLSchema}anyType }": bad value for type element {ld:NewDSProj/Test}Test { {http://www.w3.org/2001/XMLSchema}anyType }* 
Even in Query Plan also it is showing TypeError in red color.
 
I am attaching the capa.ds, Test.ds and required .xsd file and server log file for your reference.
 Any suggestiins please...
 
Regards,
Suresh Varma.

Hi I changed the return type in Test.ds to caps.xsd. It is working fine. Thank you. 
Now I have the following data services. 
1.MRM_RESPONSE.ds--which is created from java method.This java method will read the data from xml. 
2.Caps.ds--which is created for Oracle data base. 
Now I created one logical data service named as Test.ds with function newFunction(String param).My intention is i want consolidated output from both physical data services based on join condition. I have the state field in both physical data services. So the output of newFunction() in Test.ds should be combination of caps and MRM_RESPONSE. In Query plan for newFunction() I am not getting any error. But if I try to test I am getting the following error. System error
weblogic.xml.query.exceptions.XQueryTypeException: {bea-err}TYPE003 [{bea-err}TYPE003a]: Runtime Type Mismatch: got an xdt:untypedAtomic value .
I am attaching latest code and server log file for your reference. In the attached zip file NewSchemas is the schemain schemas project.JavaClient contains java method.
 
Thanks& Regards,
Suresh Varma.

Error while creating the Ole Object (MSN Messenger)

Hi,
We are trying to send a mail by invoking MSN Messenger. We have imported "Messenger.MsgrObject" OLE Object and written the following code to logon to the Messenger.
DECLARE
     MSGOBJ123 OLEOBJ;
     SRVOBJ123 OLEOBJ;
     SRVOBJ1234 OLEOBJ;
BEGIN
     MSGOBJ123 := CREATE_OLEOBJ('Messenger.MsgrObject');
-- Get all the services from the Messenger Object
     SRVOBJ123 := Messenger_IMsgrObject.Services(MSGOBJ123);
-- Get one of the services
     SRVOBJ1234 := Messenger_IMsgrServices.Item(SRVOBJ123, 0);
     IF :TXTUSR = NULL THEN
     MESSAGE('User Name cannot be null');
     RAISE FORM_TRIGGER_FAILURE;
     ELSIF :TXTPWD = NULL THEN
     MESSAGE('Password cannot be null');
     RAISE FORM_TRIGGER_FAILURE;
     ELSE
-- Log on to the Messenger By passing the MsgObject,
-- User Name, password, Service Object
     Messenger_IMsgrObject.LogOn(MSGOBJ123, :LOGINBLK.TXTUSR, :LOGINBLK.TXTPWD, SRVOBJ1234);
     END IF;
END;
We get this error while executing this program
"FRM-40735: WHEN-BUTTON-PRESSED trigger raised unhandled exception ORA-100504"
Please advice whether there is way to solve this problem or any other method of accessing MSN Messenger.
Thanks
Vishwanath

do a check on the wsdl file and how you are passing values in the proxy. The tags for XML are not correct. Open the WSDL in IE and see there must be an error. Or probably when passing the actual values to the XML generated each element is not closed properly. Error says tags dont match.
Edited by: Kshamatha Eda on Mar 5, 2010 10:54 AM

Error while creating Logical Data Object Model

Similar Messages

Maybe you are looking for