Regarding creation of service interface in PI7.0

Hi friends,
If i try to create a service interface in PI7.10 it shhows error like
<b>You cannot create new objects in component CCBPM, 1.0 of sap.com because no original language is defined for the components</b>
how can i solve this issue,plz help me out regarding this.
Thanks & Regards,
saran
Message was edited by:
Srinivasa D Rao

Hi...
Tools------> Personal settings.
Set the logon and original language to English and try...
I hope it will work...
Regards
San
Remember to set the thread to solved when you have received a solution there is a Way.

Similar Messages

Creation of Service Registry

Dear Experts
Im new to web services, i created a web service and i want to configure it in service registry, but i cant find suitable document for creating the service registry, help regarding creation of service registry will be highly appreciable
Regards
Arun.P

Hi Arun,
You don't need to create Services Registry, SAP provides it with AS Java versions 7.1 and later. If you have for example CE 7.1, 7.1.1, 7.2 or PI 7.1 or 7.1.1 in your landscape, you already have Services Registry.
Services Registry is something like yellow pages for Web services - it only contains information about services that have been published. What you can do with it is to publish information about Web services, classify them in categories, and retrieve this information. For more details, see [Services Registry|http://help.sap.com/saphelp_nwpi711/helpdata/en/d9/0f7e2c1c644992a195d38cfec1b1f2/frameset.htm].
The configuration of Web services is performed outside of Services Registry. For ABAP Web services you should do this in [SOA Manager|http://help.sap.com/saphelp_nwpi711/helpdata/en/b0/787748cf3a4200bb1ba32a62aa8519/frameset.htm], and for Java Web services you should do this in [NetWeaver Administrator|http://help.sap.com/saphelp_nwpi711/helpdata/en/44/4d2bb1c6b00597e10000000a155369/frameset.htm].
Hope this helps,
Rossen

Regarding Message Interface , Service Interface

Hi All
My scenario is File to File from 1 application server to another application server ,without any transformation in PI 7.1 for service interface to be involved for Interface Pattern Stateless and Stateless (XI 3.0) compatible can only be used with Category Abstract
only abstract catgory is possible , can'nt i make 1 outbound & another inbound for this ?
Regards
Abhishek
Edited by: Abhishek Agrahari on Feb 9, 2009 11:08 AM

Search SDN for this there is Blog for this i dont have info on this
Need to do follwoing in the ID
1. Sender and receiver Business system/services
2. respective File communication channels
3. Receiver Agreement
4. interface determination
5. Finally receiver agreement and sender agreement
Rajesh

Service Interfaces not showing in the IP when imported in ID in PI7.1

HI Experts,
     I have developed an Integration process(IP) in ESR using some Service interfaces and Operation mapping for implementing BPM.
I am trying to import the IP into my Integration Directory. But the imported Integration process(which is now as good as a Business Service) does not show the Interfaces i have used in the BPM in the ESR.
   Without the interfaces being attached to the IP, i cannot create RD and ID's.
This is the first time BPM is being configured in this server.
Please guide me if there are any settings specific to ccBPM to be done in ECC.
Please help me resolve this issue... i am in a crictical condition to meet the deadline..
Thanx in advance,
Nandan

Hi Neetesh,
         Thanx for your reply. If there are any initial settings to be done in PI, please list them so that i can check if they exist in our system.
Also,when i check(f7) my IP , its showing a message that " Container element my_interface in step Send1 is initialized but is not used ". Is this a concern ?
I have copy pasted my interface names in the RD and InterfaceDtrmn in my ID and completed the ID part of configuration.When i test the BPM by triggering my Purchase Orders from my sender service,it is showing the following error in moni:
"<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">UNKNOWN_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No object type found for the message. Check that the corresponding process is activated</SAP:Stack> " in error section and in TRace its showing this error:
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="1" type="T">could not create BPE proxy for message, no XML object definition found for message 70126C4C0C4D0B11E1000000AC113034</Trace>
</Trace>
</Trace>
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
Please suggest how these can be resolved????

Exception on creation of service metadata for WSDL URL

Hi expert,
im consuming a wsdl file in my wdj dc , and on trying to execute im getting exception as follows .
WsdlApp--com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'E:\***********\MIOS_*********_********.wsdl' and service factory configuration 'null'
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:422)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
at com.*****.wsdlwdj.batch.****************Batch.<init>(******************Batch.java:51)
at com.*****.wsdlwdj.comp.*************Component.test**********Auth(************Component.java:266)
at com.*****.wsdlwdj.comp.wdp.Internal****Component.test****Auth(Internal********Component.java:331)
at com.*****.wsdlwdj.comp.WsdlView.wdDoInit(WsdlView.java:97)
at com.*****.wsdlwdj.comp.wdp.InternalWsdlView.wdDoInit(InternalWsdlView.java:129)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
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:182)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:177)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.setSpnegoParameter(RequestManager.java:963)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:157)
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: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:1064)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:158)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:56)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:92)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:114)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:420)
... 55 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:155)
... 59 more
Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:/usr/sap/*****/JC**/j2ee/cluster/server1/E:/****/FolderName/WSDLNAME.wsdl (No such file or directory) -> java.io.FileNotFoundException: /usr/sap/***/JC**/j2ee/cluster/server1/E:/WSDL FILE/FolderName/wsdlname.wsdl (No such file or directory)
at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
... 60 more
Caused by: java.io.FileNotFoundException: /usr/sap/***/JC**/j2ee/cluster/server1/E:/WSDL FILE/FolderName/wsdlname.wsdl (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:69)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:156)
at java.net.URL.openStream(URL.java:913)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1023)
... 62 more
Regards
Govardan

im using 7.01 and here we have options to use No Logical Destinations , but now i created destinations at visual admin at Server>Services>Web Service Security>WebService Clients>Sap.com-->Dynamic WS Proxies., as WS_METADATA_DEST and WS_MODELDATA_DEST and have filled in other details too like url , user name , password etc
now im getting another error like as shown below please help
com.****.wsdlwdj.applicaiton.WsdlApp
[EXCEPTION]
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'WS_METADATA_DEST' and WS interface '{http://****.com/****}MIOS_Matrix***********'. One possible reason is that the metadata destination 'WS_METADATA_DEST' has not been properly configured; check configuration.
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
at com.****.wsdlwdj.model.test.TestModel.<init>(TestModel.java:51)
at com.****.wsdlwdj.comp.VcWsdlComponent.matrixAuthExecut(VcWsdlComponent.java:448)
at com.****.wsdlwdj.comp.wdp.InternalVcWsdlComponent.matrixAuthExecut(InternalVcWsdlComponent.java:280)
at com.****.wsdlwdj.comp.VcWsdlComponent.wdDoInit(VcWsdlComponent.java:132)
at com.****.wsdlwdj.comp.wdp.InternalVcWsdlComponent.wdDoInit(InternalVcWsdlComponent.java:225)
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:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.setSpnegoParameter(RequestManager.java:963)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:157)
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: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:1064)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.engine.services.webservices.espbase.discovery.BaseIOException: Invalid Response Code 500 while accessing URL: http://devpid:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=BS_****_PORTAL&Interface=http%3A%2F%2F****.com%2Fbank_report%5EMIOS_Authorizers_List_Portal&sap-user=xi_portal&sap-password=****1234. Response Message: Empty HTTP request received. Content Type: text/xml. Body Content: <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Empty HTTP request received</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Empty HTTP query received; message processing not possible
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
at com.sap.engine.services.webservices.server.management.discovery.DestinationsResolver.resolveURL(DestinationsResolver.java:246)
at com.sap.engine.services.webservices.server.management.discovery.DestinationsResolver.resolveEntity(DestinationsResolver.java:130)
at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.initialize(WSQueryImpl.java:184)
at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSInterfaces(WSQueryImpl.java:151)
at com.sap.engine.services.webservices.server.management.discovery.ServiceDiscoveryImpl.getWSDLUrl(ServiceDiscoveryImpl.java:71)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:134)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429)
... 49 more

Exception on creation of service metadata for WS metadata destination

Hi,
I have imported a webservice from the backend to the model in webdynpro and i have also configured the destination for the metadata in the CE server but when i execute it its giving me error as
Exceptioncom.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination FLIGHT_GETLIST and WS interface ZBapi_Flight_Getlist. One possible reason is that the metadata destination FLIGHT_GETLIST has not been properly configured; check configuration.
and during deployment i am getting the following warning
local/SampleFlightList : References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.com/tcwdapi, sap.com/tcwdwslib~api] (described in the META-INF/application-j2ee-engine.xml)., file: SampleFlightList.ear, column 0, line 0, severity: warning
can any one please help me to solve this issue.
Thanks&Regards,
Hamsa Shree

Hi Hamsa,
Did you also create and configure an "Execution Destination"?
You can test the Metadata destination configuration on Web Service Navigator.
On the web service navigator (http://hostname:portnumber/wsnavigator) search in the metatda destination you have created for the service you imported in web dynpro as a model. If you can find it there test it on the ws navigator.
Best regards,
Yasar

Auto PO creation from service PR(ME59N)

Hi All,
We have service PR's and need to convert to PO's automatically via ME59N.
I have followed below steps but unable to convert to Po's getting message no Pr's found while executeting ME59N
checked VMR and Automatic PO check box selected.
Step1: Creating PR for services
Step2: and assigned source to this PR through t.code: ME56 (contract existed for this vendor)
Step3:Run the ME59Nby giving PR Number, but PO is not created
what could be the reason..is any idea about auto PO creation for Service PR's
Incase of material i can successfully converts PR's PO's but services i can't.
Thanks in Advance,
Warm regards,
Venkat
MM/SRM Consultant

Hi venkat
it should create a PO if the contract is valid..
Note 733045 - Wrong Interface values passed to Services for ME59N
When transaction ME59N is used to convert service purchase requisition
(PR) to purchase order (PO),the program within the ME59N transaction
calls the service package with the wrong interface values.
The following example illustrates one such case :
A Service PR is created and an Outline agreement is assigned as a source of supply to the PR.
when the transation ME59N is executed using the PR's the system performs a mandatory check against the Tax code and tax code has to be entered against each service line to complete the transaction even though the tax code is maintained as a condition.
In the above situation,system behaves in a correct manner for the
transaction ME59 but fails for the transaction ME59N.
Other terms
MS_SERVICE_PACKAGE , ME59N , ME59 , WITHOUT_SCREEN , COPY_SERVICES
Reason and Prerequisites
The calling program of the transaction ME59N calls the function
MS_SERVICE_PACKAGE of services with the wrong interface values.
is it applicable for you?

Inbound Service Interface without Input Request Message

Is it possible to create an Inbound Service Interface without Input Request Message? We are trying to create a web service to get all records from a database table hence no input parameter is needed. We have tried in both XI 7.0 and PI 7.1 but couldn't do it. Is this scenario not supported by ESR or am I missing something? Any hint will be appreciated.
Regards,
Jiannan

In the scenario I described in my initial post the table structure is only needed in the response message to receive the data.
For a web service generated from a RFC function module using the service creation wizard (SE80) a table parameter is automatically included in the request message. I can understand this as the wizard can not figure out if the table parameter is needed in the request message or not.
I have tried to use the service creation wizard to generate a web service from the function module RFCPING that has no input or output parameters. As shown in below WSDL segment the WSDL does allow not having any input or output parameters.
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style">
- <xsd:element name="Rfcping">
- <xsd:complexType>
<xsd:sequence />
</xsd:complexType>
</xsd:element>
- <xsd:element name="RfcpingResponse">
- <xsd:complexType>
<xsd:sequence />
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="Rfcping">
<wsdl:part name="parameters" element="tns:Rfcping" />
</wsdl:message>
- <wsdl:message name="RfcpingResponse">
<wsdl:part name="parameter" element="tns:RfcpingResponse" />
</wsdl:message>
Thanks,
Jiannan

Questions about PO creation / update / cancel interfaces

Hi there,
An E-Business Suite 11.5.10.2 customer wants to use the 11i PO creation / update / cancel interfaces in order to manage Purchase Orders created from a 3rd party system.
I've been through the 'Oracle Purchasing Open Interfaces' guide (115mfgapi.pdf), but it's still unclear to me whether:
1/ It is possible or not to add a new PO line to an existing PO through the interfaces ? If yes, how do one do that: what interface ? sample code ?
2/ It is possible or not to change the distribution (= accounting information) of an existing PO line ? If yes, ...
3/ It is possible or not to reject the full PO document if a single line fails during the PO creation ? Same for a batch of POs: reject the full batch if a single PO fails ?
4/ Is it possible or not to cancel a PO line even if the shipment already occured ? And even if the payment already occured ? Are there some controls here ?
Thanks for your help,
Kind regards - Hugues

1. Answer is YES. You can add a line to an existing standard purchase order by choosing the UPDATE. This can be done through Purchase Documents Open Interface.
I can not give an example. It's quite long to write it. But You should use Open interface user guide to find nessesary columns. Just insert new row with status UPDATE and try to import
2. Think You can NOT.
3. Answer is YES. You can do it. Use "Cancel PO API". Function name is PO_Document_Control_PUB.control_document ().
For technical details read Open interface UG.
You must create exception to be avoid problems if some lines can not be canceled.
4. Answer is YES. You can do it if there's still expected quantity to recive.
boldJust from UG:*bold* :)
bold1. Purchase Order Change APIs. bold
boldThe APIs enable you to do the following*bold*:
- Record Acceptance/Rejection in Oracle Purchasing
- Update quantity, price, and promise date on standard purchase orders or releases in Oracle Purchasing
boldSo only qty, promissed date, price*bold*
boldRead next*bold*:
Line Level Validation and Update: This logic occurs when LINE_NUM is not null
and SHIPMENT_NUM is null.
1. No update occurs if the line status is FINALLY CLOSED or CANCELLED.
2. The new quantity or price value must be positive.
3. If updating quantity, the new quantity must be greater than or equal to the
greater of total quantity_received of all shipments and total quantity_billed
of all shipments for this line. After the update takes place, the new quantity
will be prorated at the shipment level and for each shipment the quantity is
prorated at the distribution level if applicable.
4. If updating price, no update occurs if a receipt has been created against one
of the line’s shipments and it's been accrued upon receipt. No update
occurs if an invoice has been created against one of the line’s shipments.
After a price update takes place, price changes are rolled down to the
shipment level for standard POs. No price update occurs for a release if the
Price Override flag on the blanket purchase agreement Line is No.
boldSummary:*bold*
boldYou can update qty if still there's a qty to receive (Expected) and if PO still is not canceled*bold*
boldEXAMPLE:*bold*
Usage Example
set serveroutput on;
-- After the API completes, do not forget to commit if the result is 1
-- and rollback if the result is 0.
DECLARE
l_result NUMBER;
l_api_errors PO_API_ERRORS_REC_TYPE;
BEGIN
-- This needs to be changed according to your environment setup.
FND_GLOBAL.apps_initialize ( user_id => 1318, resp_id => 50578, resp_appl_id => 201 );
-- Record an acceptance of Y for PO 1261.
l_result := PO_CHANGE_API1_S.record_acceptance(
x_po_number => 1261,
x_release_number => null,
x_revision_number => 0,
x_action => 'NEW',
x_action_date => null,
x_employee_id => 588,
x_accepted_flag => 'Y',
x_acceptance_lookup_code => 'On Schedule',
x_note => 'All valid',
x_interface_type => 'APITEST',
x_transaction_id => null,
version => '1.0');
IF (l_result <> 1) THEN
-- Handle the errors in the PO_INTERFACE_ERRORS table.
END IF;
-- Change the quantity to 5 on line 1, shipment 1 of PO 1263.
l_result := PO_CHANGE_API1_S.update_po (
x_po_number => 1263,
x_release_number => 1,
x_revision_number => 1,
x_line_number => 1,
x_shipment_number => 1,
new_quantity => 5,
new_price => NULL,
new_promised_date => NULL,
launch_approvals_flag =>'Y',
update_source => NULL,
version => '1.0',
x_override_date => NULL,
x_api_errors => l_api_errors,
p_buyer_name => null
IF (l_result <> 1) THEN
-- Display the errors
FOR i IN 1..l_api_errors.message_text.COUNT LOOP
dbms_output.put_line ( l_api_errors.message_text(i) );
END LOOP;
END IF;

'owspe:PolicyAccess' error while invoking ADF BC Service Interface

Hi,
   I have deployed a custom ADF BC Service Interface application to a standalone weblogic server. On invoking the service interface i get the following error in response.
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault
    xmlns:owspe="http://schemas.oracle.com/ws/policy-enforcement-2007-06">
   <faultcode>owspe:PolicyAccess</faultcode>
   <faultstring>PolicySet Invalid: WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "&(@appliesTo~="WS-Service()")(policysets:global/%)" is queued for later retrieval. </faultstring>
   <faultactor/>
</env:Fault>
</env:Body>
</env:Envelope>
I have deployed the same .ear file to my local weblogic server and got no error while invoking the WS.
Please suggest if any configuration needs to be done at weblogic server or to the ADF application.
Regards,
Himanshu

Hi Timo,
           No Luck.. Still getting same error. My ADF BC Custom Service Interface deployed on integrated weblogic server works fine.When i deploy the same EAR to Standalone weblogic server then i'm getting following error on invoking WS method.
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault
    xmlns:owspe="http://schemas.oracle.com/ws/policy-enforcement-2007-06">
   <faultcode>owspe:PolicyAccess</faultcode>
   <faultstring>PolicySet Invalid: WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "&(@appliesTo~="WS-Service()")(policysets:global/%)" is queued for later retrieval. WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "/policies/oracle/wss_http_token_service_policy" is queued for later retrieval. </faultstring>
   <faultactor/>
</env:Fault>
</env:Body>
</env:Envelope>
Could it be related to some Security: Roles or policies ?
Regards,
Himanshu

Creation of Service Order from Service Plan

Hi Experts,
I am working on sap crm 5.0 version
Pls help in the service order creation from service plan document
I have Created a service plan product and maintained a service plan template with an interval of 3months
In Service Plan to service order action i am using the Standard method call
CREATE_ORDER_SRVPLAN in the action profile and Action profile Start Condtion
Start of interval equal to todays date . when i am executing the action
First service order is getting created immediately on the serviceplan Creation date.
Subsequent service orders are getting generated respectively as per defined frequency .
So I am getting one extra service order . how to restrict the additional service order creation and
order creation to happen as per template frequency
Regards,
Prajit.P

Hi vishant,
thanks for ur quick reply.
I am not able to find the scheduling type as u mentioned for changing the planning start date in template. I am using the standard date profile SERVPLAN in my service plan action profile
Please suggest me the daterule i need to select in the date type start of interval in my date profile
Regards,
Prajit.P

Error while creation of Service PO

Hi,
While creation of service PO I am not able to put Material Text as that column is grayed & system asks me to put material text which is input disabled.
Procedure I follows to create Service PO as below:
PO type standard (NB).
Then I put vendor, Org data & payment terms.
Then Account assigmnment cat. 'K' (Cost Cetner) & Item Cat. D(Service).
After that when put enter. Sytsem asks me to enter either material number or material text. But material text coulmn is grayed (Input dusabled). So I am not able to put it because of which I am not able to proceed further & not able to create Service PO.
Awaiting your reply to solve this problem.
R/-
Pradip

Hi V S,
Please change the screen layout for respective field selection key for Material description as optional, then you can edit the text in the material description
Regards,
Rao

Exception on creation of service metadata for WSDL

trying to access webservice (generated on Oracle applic. Server) as Adaptive WebServiceModel i get the following error:
Exception on creation of service metadata for WSDL
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory
Initialization problem. Could not load web service model. See nested exception for details.
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
     ... 53 more
Caused by: java.lang.UnsupportedOperationException: Type {http://schemas.xmlsoap.org/soap/encoding/}Array is not supported!
     at com.sap.engine.services.webservices.espbase.client.dynamic.types.impl.MetadataLoader.loadMetadata(MetadataLoader.java:129)
So, the code in WSDL is like:
targetNamespace="http://com.rwe.lis.webservices/IWSFidLis.xsd"
         xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="ArrayOfcom_rwe_lis_model_Flurstueck" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
            <complexContent>
               <restriction base="SOAP-ENC:Array">
                  <attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:com_rwe_lis_model_Flurstueck[]"/>
               </restriction>
            </complexContent>
         </complexType>
generated by JDeveloper on Ora Server.
So - how to get access to this WebService?!?
Bernhard

Hi,
   The use of SOAP-ENC:Array is not supported in NW because it is not WS-I compliant. For a possible solution check [this|Re: unknown namespace error when generating a client proxy; link.
Regards,
Satyajit

Dump during creation of service entry sheet (ML81N)

Dump during creation of service entry sheet (ML81N)
Hi,
ML81N>Select PO>Enter>goto entry sheet create (empty page)>service entry sheet displayed with internal no. assigned >click tab "service selection">Input PO No.--> enter (here we get Dump ABAP RUNTIME ERROR "TABLE_INVALID_INDEX").
This is happening only for some POs. What can be the problem?. Is this has something to do with SAP database ???
- rahul

Hi,
it could have the cause that the note 1113220 was missing from your system or that data are inconsistent in your PO.
If you implemented 1113220 and you still get the dump, please check in transaction ST22 the run time error long text to the dump:
Parts:
- How to correct the error?
- Information on where terminated
- Source Code Extract -> if you set a breakpoint before the line where the error occured, you could debug the process.
- Active Calls/Events: if you have an own program displayed here, please check first your program wether it has caused the issue.
If these do not help to find out the problem cause, please open a SAP ticket and include all of the relevant information regarding the dump.
Regards,
Edit

PI 7.1 "stateless" service interfaces prerequisites and limitations

are there any prerequisites and limitations for "stateless" Service interfaces.
We are directly implementing PI 7.1, (i.e not upgrading form 7.0 or 3.0).
so for all our service interfaces, shall we safely use tne interface pattern "statelss" instead of "Stateless(xi 3.0 compatible)".
if use the "stateless", are there any addition prerequisites or constraints/limitations.
can we use abap proxies, java proxies, providing webservices via xi, and consuming other webserivces in xi, all adapters, asynch, synch scenarios with "stateless" interface patterns.
In short, are there any things that can be done using "Stateless(xi 3.0 compatible)" and cannot be done using "stateless" interface
are there any specific requirements for using "Stateless(xi 3.0 compatible)" even in newly implemented PI 7.1
thanks in advance,
Madhu.

When it is an upgrade from 7.0 to 7.1 the default Interface pattern is Stateless (XI 30 Compatible)
Using Stateless Interface Patterns wont cause any harm/ restriction on any of the development.
The only twist will be in the way a condition is specified in the Receiver Determination.
For any Interface pattern (other than Stateless(XI30 Compatible)) you wont be able to see the message structure in the Condition Editor of Receiver Determination. All other functionality (Async, Sync, Proxy) will be available.
In such a case Condition should be specified as shown in this blog: /people/abhishek.salvi/blog/2009/07/15/sap-pi71-receiver-determination-xpath-and-you
Regards,
Abhishek.

Regarding creation of service interface in PI7.0

Similar Messages

Maybe you are looking for