Importing XSD

Hello Gurus,
I am using XI2.0 and now I want to import an XSD. I have been reading around and saw that the best way to do this is, importing an External Definition ot the type XSD. So I have imported my XSD as an External Definition. Now I do not have to create a data type and message type and go directly to my Message infterface definition. When I want to select my message, I go to external definitions but now I can only select elements and not the complete message. I want to select the complete message with all elements as a Message.
Hope some can help me out!

Hi,
at the external definition, go to tab "messages". Check if there's a definition for the whole message, like you expect. If not, try the following things:
1. Open the XSD with an tool other then XI und check if there is an element definition which has a reference to the root of the message. If not, create it and re-import the XSD. Now you should see it on tab "messages".
2. If you work with namespace check for the length. If it is longer than 60 characters XI will not show you the message definition.
Best regards,
Karlheinz

Similar Messages

Import XSD to create Data type in Design

hi,
I know that we can import XSD in Design and create data type,my question is:
1. Can i import an XSD thats been created in message mapping and use that to create my data type in design.
(or)
2.Should i have to write an XSD on my own and then import it to create my data type, and is there any standard format to write it.

Hello Prashanth,
For your first question: i don't know exactly what you mean that the the xsd you create in the data mapping steps. So can you explain it in details?
For your 2nd question: Sure you can write your own XSD to create a data type. And i will give you an example xsd file format. Then you can import it in the XSD tab view.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/XI/hansteel" targetNamespace="http://sap.com/xi/XI/hansteel">
 <xsd:complexType name="CustomerInfo">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a6c26c80000f11dac45e00096b1669b3
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="ID">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 dfe699c0e7bc11d9c736d51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="10" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="NAME">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 dfe82060e7bc11d9b2efd51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="35" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="CUSTTYPE">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 dfe82061e7bc11d9c193d51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="4" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="POSTCODE">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 e93039a0e7bc11d9c7c6d51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="10" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="CITY">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 f0122850e7bc11d99189d51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="35" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>
Hope this will be helpful.
Eric Ma

Imported xsd's not installed in Service Registry

Folks:
I am using the AIA2.2 vmware image. I am wondering why and how core xsd's are not searchable in Services Registry (Business Service Control). First, the import statement of an xsd like "invoice.xsd" has a realtive path in it like "../../../../CommonComponents.xsd". Obviously, this is invalid when you import the schema into a JDEV project. One would think that the xsd's would be available in a services registry and have a http location to be of any use so JDEV can add an invoice schema to a project and be able to build a mapping. Without the ability to see these imports, JDEV chokes on the invoice.xsd and you cannot do a simple thing like transform one variable into another.
What am I doing wrong here? Why are things like "CommonComponents.xsd" not searchable in the services registry? This looks like a big oversight because I wonder how anyone can use a xsd that has imports which are not visible to JDEV (at least without hacking the file system to find the core component). The steps to rep[roduce are simple:
1) Create a BPEL project (Asynchronous)
2) Create a UDDI connection to Services Registry (BSR)
3) Add any xsd that imports "CommonComponents.xsd" to your BPEL project
4) Try to change the payload of the request or response message for the BPEL project to one that takes my imported xsd such as invoice
5) JDEV will give you an error because it does not have access to the imported schema and thus cannot interpret the types correctly and therefore you cannot do step 4 above or even do an XSLT mapping.
Thanks

So, my oversight -- you can view these xsd's properly by simply accessing them via Apache url which is the better way to go. They are, in fact, in the registry albeit the search feature does not seem to function properly.
In any case, just putting this in the thread so others find it easier to do AIA development from the start.

Error occured while importing xsd.file(Name contains invalid characters: -

Hello,
i muss import xsd.file. while importing this error occured:
İFMEXTDEF CCTS_CCT_SchemaModule-2.0 | http://example.org/XXX/XXX/OUT/NOZ (SC_NOZ V001 of example.org):
Name contains invalid characters: - .
Only a(A)-z(Z), 0-9, and "_" are permitted
This xsdfile name is CCTS_CCT_SchemaModule-2.0 but PI doesn't accept "-". But i muss use this file because this file is standart. What can i do for this?
Thanks
Nurhan
Edited by: Nurhan on Oct 18, 2011 11:22 AM

HI,
PI doestnt support special characters like '-'. first you need to change the file name as you specify '-'. to remove that and you have to give '_'. then uyou have to impot >XSD file into ESR under ExternalDefination.
i hope this will help you.
regards,
ganesh.

Error when Import XSD file

Hello expert,
 During creating Data Type in the build, I try to import XSD file, but system says:" XSD schema containing the construct "choice" are not permitted here"!
 I found in the XSD, there are this definition:
 <xsd:element name="EmploymentInfo" minOccurs="0">
 <xsd:complexType mixed="true">
 <xsd:choice>
 <xsd:element name="FullTimeEquivalence" type="xsd:decimal"/>
 <xsd:element name="WorktimeInfo" maxOccurs="unbounded">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="Duration" type="xsd:duration"/>
 <xsd:element name="Period" type="xsd:duration"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:choice>
 </xsd:complexType>
 </xsd:element>
 Could anybody tell me how to handle this? I am not quite familiar with XSD. Thanks a lot.
Best regards,
Shouxin

Hi,
replace choice with sequence
<xsd:complexType>
 <xsd:choice>
 <xsd:element name = A type=xsd:string />
 <xsd:element name= B type=xsd:string maxOccurs=unbounded />
 </xsd:choice>
</xsd:complexType>
is handled identical to
<xsd:complexType>
 <xsd:sequence>
 <xsd:element name = A type=xsd:string minOccurs=0 />
 <xsd:element name= B type=xsd:string
minOccurs=0 maxOccurs=unbounded />
 </xsd:sequence>
</xsd:complexType>
Regards
Tarun Telang

How to import xsd file inside XSD folder in Oracle SOA 11g

Hi,
I need to import xsd file inside XSD folder provided by the deafult structure while creating SOA project. When I used to import the web resource it imports it inside public_html folder not inside XSD folder.
How to do that ?
Thanks

Hi,
Are you using Jdeveloper on a windows machine? If you are then this might be a useful tip.
Click Tools -> External Tools. It will prompt you to setup common tools. Let it do this. Now when you right click on your project you will get an Explore Directory option. I use this a lot when copying XSD’s between projects.
Once you have done this you need to click the refresh button in the Application Navigator to ensure the new files appear.
Robert

Error while Importing XSD in to XI system

Dear All
I'm trying to import XSD's in to my XI system & received the following error. Can some one give me a insight in to this error.
javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoSuchMethodError: com.sap.aii.utilxi.xsd.api.XsdSchema.getParserErrorsCheckResult()Lcom/sap/aii/utilxi/misc/api/CheckResult;
java.lang.RuntimeException: java.lang.NoSuchMethodError: com.sap.aii.utilxi.xsd.api.XsdSchema.getParserErrorsCheckResult()Lcom/sap/aii/utilxi/misc/api/CheckResult;
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:80)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy1373.convertExternalDocument(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: java.lang.NoSuchMethodError: com.sap.aii.utilxi.xsd.api.XsdSchema.getParserErrorsCheckResult()Lcom/sap/aii/utilxi/misc/api/CheckResult;
at com.sap.aii.ibrep.server.extdef.XsdInternalServerExternalCategoryService.convertToXsd(XsdInternalServerExternalCategoryService.java:79)
at com.sap.aii.ibrep.server.extdef.XsdInternalServerExternalCategoryService.convert(XsdInternalServerExternalCategoryService.java:34)
at com.sap.aii.ibrep.server.extdef.ServerExternalConversionService.convert(ServerExternalCategoryServiceProvider.java:42)
at com.sap.aii.ibrep.server.misc.RepSpecMiscServicesBean.convertExternalDocument(RepSpecMiscServicesBean.java:185)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
... 32 more
javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoSuchMethodError: com.sap.aii.utilxi.xsd.api.XsdSchema.getParserErrorsCheckResult()Lcom/sap/aii/utilxi/misc/api/CheckResult;
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:80)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy1373.convertExternalDocument(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodError: com.sap.aii.utilxi.xsd.api.XsdSchema.getParserErrorsCheckResult()Lcom/sap/aii/utilxi/misc/api/CheckResult;
... 33 more
Caused by: java.lang.NoSuchMethodError: com.sap.aii.utilxi.xsd.api.XsdSchema.getParserErrorsCheckResult()Lcom/sap/aii/utilxi/misc/api/CheckResult;
at com.sap.aii.ibrep.server.extdef.XsdInternalServerExternalCategoryService.convertToXsd(XsdInternalServerExternalCategoryService.java:79)
at com.sap.aii.ibrep.server.extdef.XsdInternalServerExternalCategoryService.convert(XsdInternalServerExternalCategoryService.java:34)
at com.sap.aii.ibrep.server.extdef.ServerExternalConversionService.convert(ServerExternalCategoryServiceProvider.java:42)
at com.sap.aii.ibrep.server.misc.RepSpecMiscServicesBean.convertExternalDocument(RepSpecMiscServicesBean.java:185)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
... 32 more

Thanks to Sunil & Swetha
My issue has been resolved, it was related to Support Pack Stack level. I upgraded to SP09 for the following components
SAPXITOOL*.SCA
SAPXIESR*.SCA
SAPXIAF*.SCA.
(1) Open the Administration console at link:
- http://<Host>:<Port>/rep/support/admin/index.html
(2) Click Java Web Start Administration link in left-hand navigation menu.
(3) Click Re-initialization button (to reintialize all jars).
Thanks again for your time.

Importing XSD to Create a Msg Type.

Hi All,
Can anyone plz tell me how to create a msg type based on external XSD.I hav gone thru help.sap.com. there it is mentioned for Data Type.It is given that to go for Tools->Import XSD.but i din't find any such option there.Instead, i hav gone for creating External Definition and was successful in creating a DataType using External Definition.But to my surprise, the created Data type is not listed under Data types.Instead it is listed under External Definitions. This is for Data Types.But i need for Message Type.Plz help me out as i hav very severe dead lines.
Thnx in Advance.
Anil.

Hi Anil,
You could create Message Type (MT) in 3 ways :
1. Manual: Create Data Type (DT) & Create MT refering to it.
2. Import XSD as DT: Create a new DT by giving a name. The structure can be imported from a XSD. Tools-> Import XSD. (Note: the name of DT here should match the 'complex type' name in XSD). Then create a MT refering to this DT.
3. Import XSD as External Definition: An XSD can be imported into External definitions, and this creates the MT directly, and no DT required. They appear only under 'External Definitions'. Note: This XSD should contain a 'complex type' definition, which stands for DT. And also a root element declaration refering to this type, which stands for MT. In this case, we can have one XSD containing multiple DTs and MTs within it. All these MTs can be seen under the 'Messages' tab within an External Definition.
Once an MT is created in one of these 3 ways, the other concepts of Interfaces, mappings etc. remain the same.
Hope this gives the differences, and clarifies your concerns.
regards,
Pops V

Import XSD to create datatypes

Hello Everybody-
I want to create a datatype that is specific for my outbound message,i have the xsd of that structure,i was trying to import the xsd to form a XI structure.Here is what i have done.
1.Right clicked datatypes and clicked on new
2.It asked me for a name and i gave a name "venkat".
3.Then from menu-tools, i clicked import xsd and selected my xsd. Then i got a message that Schema to be handled does not contain a definition of type venkat.
4.So what i did this time i gave the name as OrderRelease instead of venkat(as stated in step 2) and still i get the error.
I am pasting a snippet of my xsd.
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="OrderRelease">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="MergeNode" minOccurs="0" maxOccurs="unbounded">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="ShipNodePersonInfo" minOccurs="0">
 <xsd:complexType>
 <xsd:attribute name="Suffix" type="xsd:string"/>

hi,
1. you need to import it as an external definition
2. you need to close the tags
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="OrderRelease">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MergeNode" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ShipNodePersonInfo" minOccurs="0">
<xsd:complexType>
<xsd:attribute name="Suffix" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Usage of imported XSD

Hi All,
May I ask what is the imported XSD used for? Can it be used to verify the data source XML file? If yes, how can we do that?
Thanks, Jerome

Imported XSD are stored in the Repository via MDM Console.
Import Manager can parse the XML files against these XSDs.
This way, if you have a NOT well formed XML or NOT valid XML, then these XML files go to the Exception Folders of the port you have created.
This becomes very handy if you are using automatic import via Import Server.
This gives you a flexibility to reprocess errors in a controlled way.

Import XSD from BAPI structure

Hi all,
I have a problem when export XSD scchema from BAPI structure and use this schema to create a data type using import XSD schema. The error is following displayed:
Schema to be handled does not contain a definition of type BAPI_SALESORDER_CREATEFROMDAT2.
Any idea?????
Thanks in advance,
          Michele Lazzarato

Hi Stephan,
I have created an Abap Proxy and the error message in English as follow:
Message Interface prova   http://xtel.com/xi/Sales Order references RFC
Message BAPI_SALESORDER_CREAT EFROMDAT2   urn:sap-
com:document:sap:rfc:functions    BAPI_SALESORDER_CREATEFROMDAT2.Response
and the
Message no. SPRX000
Thanks,
            Michele.

Getting response object field value as null when importing xsd file in wsdl

I have created a java webservice using X-Fire 1.2.6 framework and deployed on Tomcat 6.0 server. The response of the service is a java object named LoginDetail.
Inorder to reuse the basic elements and types we have defined them in a separate Types.xsd file which have been imported in the WSDl file using xsd:import by giving the path to the xsd file.
Below you can see the portion of the wsdl file
 <wsdl:types>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 attributeFormDefault="qualified" elementFormDefault="qualified"
 targetNamespace="http://webservices.gtl.de/xsd">
 <xsd:import namespace="http://webservices.gtl.de/xsd"
 schemaLocation="file:///D:/wsdl/LoginTypes.xsd"></xsd:import>
 </xsd:schema>
 </wsdl:types>
After deploying the application on Tomcat I could access the WSDL using a web browser and after that I could successfully generate webservice client code using using XFire wsgen ant build.
But when tried to call the service the fields of the response object(in my case it is LoginDetail object) returns null.
Follwing are the main class used for running the client and the output received as webservice respone.
Main class
public static void main(String[] args) {
CCLoginNewClient client = new CCLoginNewClient();
CCLoginNewPortType service = client.getCCLoginNewHttpPort();
LoginDetail loginDetail = service.getLogin("CCLoginNew", "DE", "DE", "100", "0", "CC", "15","9344");
System.out.println("service got in response : "+loginDetail.getService());
Output
service got in response : null
is this the right way to import an xsd file in a wsdl file?
Any input would be appreciated!
Thanks in advance

PramodDas wrote:
Output
service got in response : nullCheck with Apache TCPMonitor what response you are receiving from web service.
is this the right way to import an xsd file in a wsdl file?Make sure that you really need import, not the include. However, I guess it has nothing do with the actual issue. It just to make sure that you are using right option.

How to import XSD?

Hi Friends,
I have export the IDOC to XSD. If i want to import XSD, i get this Error:
- Schema to be handled does not contain a definition of type ....
How do you import a XSD structure?
Thanks in advance
Fatih

Can you test it?
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="urn:cts-com:BPM" xmlns="urn:cts-com:BPM" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="BANK_CREATE01">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="IDOC" type="BANK_CREATE.BANK_CREATE01"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 <xsd:complexType name="BANK_CREATE01.E1BANK_CREATE">
 <xsd:annotation>
 <xsd:documentation>Header segment</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="BANK_CTRY" minOccurs="0">
 <xsd:annotation>
 <xsd:documentation>Bank country key</xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="3"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="BANK_KEY" minOccurs="0">
 <xsd:annotation>
 <xsd:documentation>Bank Keys</xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="15"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="BANK_METHOD" minOccurs="0">
 <xsd:annotation>
 <xsd:documentation>Check digit calculation method</xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="4"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="BANK_FORMATTING" minOccurs="0">
 <xsd:annotation>
 <xsd:documentation>Format of File with Bank Data</xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="3"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="E1BP1011_ADDRESS" type="BANK_CREATE01.E1BP1011_ADDRESS" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
 <xsd:element name="E1BPADR1" type="BANK_CREATE01.E1BPADR1" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
 </xsd:sequence>
 <xsd:attribute name="SEGMENT" type="xsd:string" fixed="1" use="required" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
 </xsd:complexType>
 <xsd:complexType name="BANK_CREATE.BANK_CREATE01">
 <xsd:annotation>
 <xsd:documentation>Create Bank</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="EDI_DC40" type="EDI_DC40.BANK_CREATE.BANK_CREATE01"/>
 <xsd:element name="E1BANK_CREATE" type="BANK_CREATE01.E1BANK_CREATE" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
 </xsd:sequence>
 <xsd:attribute name="BEGIN" type="xsd:string" fixed="1" use="required" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
 </xsd:complexType>
</xsd:schema>

How to import XSD Definition

Hi All,
Pls tell me the steps to import XSD Defnition.
Shanmugam

Hi,
In your IR --> Name Space > Datatypes> External Defninitions --> Right and new and then import your External Definition and activate it.
Regards,
Bhavesh

How to import XSD with same name

Hi,
I have a Parent XSD which imports 3 XSD's.
The parents XSD name and one of the imported XSD name is same in the XSD.
Say for Ex: 1.xsd is a parent
which import 2.xsd , 3.xsd & 1.xsd ( from different directory - import path in the XSD is different - <xsd:import namespace="www.localdomain.com/1.xsd" schemaLocation="C:/container/path/1.xsd"/>
where as the parent 1.xsd is in c:/jms/path/1.xsd
So whenever i import into the workshop it is giving me compilation error.
How to fix this ? pls help.
Thanks,
-Raj..

You can try like below.
var oObject = xfa.resolveNode("Object[1]");
xfa.host.messageBox("" + oObject.rawValue);
Thanks
Srini

How to Import xsd and use it in transformation for mapping

I have constructed an xsd and want to use it in BPEL Process.I imported the xsd into development.But I am unable to understand how to further proceed.Can anybody suggest me how to import xsd and use it as it has to be defined in wsdl before using right.Is there any way we can use xsd?

Hi',
See in a BPEL (web service) we use XSD to define its input and output, inside this BPEL process you have input and output variable.
Now inside the transform you can use this variables to transform data, there can be many other variables too, when you try to invoke
some other BPEL process you again create new input and output variable.
Inside a transform activity you have a source and a target there you can decide where all the input is coming from you could have
one or many variables in source and only 1 in target, this is how your variables (or XSD) can go inside the transform, inside the transform.xsl
view you can right click on the source side(left) and include any new variable there.
-Yatan

Importing XSD

Similar Messages

Maybe you are looking for