Data Type - XSD IMPORT

Hi friends,
I need a new DATA TYPE .The structure is just like a bapi structure. I would not like to write everything by hand.
I would like to import XSD of bapi.
It is possible?
if yes, how then?

Hi,
Hey just checked,
If you Import the RFC and then open the Request and Response, then in the menu on the right side,
Select TOOLS-->EXPORT XSD. This XSD then can be made as External defination and then you can use it as MT for mapping.
Is this what you need or am I just missing the point.
Regards
Vijaya

Similar Messages

Multi language description of data types - xsd export

Hi,
with PI 7.1 there is a new feature for multi language field description (http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/fdd13fa69a4921e10000000a1550b0/content.htm) in the repository.
If you change the display language, the description language is also changed.
If you want to export the XSD of the data type, the description in XSD depends on the display language.
Does anybody knows a way to export a XSD with both language description.
I remember seen a XSD with the xml:lang tag.
regard,
Torsten

If assuming if a Element is only present in 1 Language pack, that SCSM defaults to that?
yes. Hence you should be able to get away with manually removing the secondary language packs. There is however a slight chance that some Ids have no displaystring in the primary language pack.
http://codebeaver.blogspot.dk/

Using Complex Data Types in Import JavaBean Model

Hi,
I have searched and read forums and weblogs related to import javabean model.
But I am not clear about how to use complex data types like ArrayList, Collection etc in my java bean.
If I use these complex datatypes in my bean, when creating model in WDF it displays the Complex data elements in Model Relation. I dont know how to use this model relation in my WD project.
Anyone please explain the step by step solution about using complex data type(used in Bean) in WD Project.
Thanks,
Krishna Kumar

Hi Krishna,
Valery`s blog contains sample code ( http://www.jroller.com/resources/s/silaev/Employees.zip )
Another blogs from this area:
/people/anilkumar.vippagunta2/blog/2005/09/02/java-bean-model-importer-in-web-dynpro
/people/valery.silaev/blog/2005/08/30/javabean-model-import-when-it-really-works
And forum topics:
Import JavaBean Model
Problem Importing JavaBean Model in NetWeaver Developer Studio
Issue on "Import JavaBean Model"
import JavaBean Model: no executable Methods?
JavaBeans Model Import
POLL : JavaBean Model Importer
JavaBean-Model
Invalid Class - Javabean not available for import
WebDynpro Using JavaBean Model ->Please Help
Best regards, Maksim Rashchynski.

ROWID - data type export import

Hi all,
I have a table which has a column of datatype ROWID. Size of the table is 5GB. When I try to export it takes 40 mins for this table. While importing it takes 7hrs to complete.
I feel it is taking more time than it is supoposed to. Is it because of the ROWID data type. Is it doing something extra, can someone throw some ilight on this.
Thanks in Advance,
Jaggyam

No it will not be because of the ROWID column data type.
Probably because of:
- creation of indexes on the table.
- creation of constraints (PK/UK/FK/CHECK) on the table.
These actions take time, and do not happen when you export a table.
Btw:
Are you aware that the rowid values in that particular column will (very likely, depends a bit on your case) have been rendered un-usable after the import?

Unable to send structure data type as import parameter in RFC

I have one RFC to web service scenario.My sending RFC is as follows:
FUNCTION ZIXI_001_EMP_DET.
""Local Interface:
*" IMPORTING
*" VALUE(EMP_DET) TYPE ZIXI_EMP
*" VALUE(OFFER_DT) TYPE ZXI_OFFER_DATA
ENDFUNCTION.
Here ZIXI_EMP is a structure with following details:
EMP_ID INT4 INT4 10 0 Natural Number
NAME STRING128 CHAR 128 0 128 Lowercase and Uppercase Letters
SAL INT4 INT4 10 0 Natural Number
and ZXI_OFFER_DATA is another structure with following details:
REQ_ID STRING128 CHAR 128 0 128 Lowercase and Uppercase Letters
PRICE STRING128 CHAR 128 0 128 Lowercase and Uppercase Letters
QTY STRING128 CHAR 128 0 128 Lowercase and Uppercase Letters
After configuring everything in IR and ID, I called the RFC from R3 system with following data:
EMP_DET:
 EMP_ID 15
 NAME XYZ
 SAL 5.000
OFFER_DT:
 REQ_ID A235
 PRICE 50
 QTY 3
but when I am checking in sxmb_moni, payload only containing first field of each structure. i.e.,
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:ZIXI_001_EMP_DET xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <EMP_DET>
<EMP_ID>15</EMP_ID>
<NAME />
<SAL>0</SAL>
</EMP_DET>
- <OFFER_DT>
<REQ_ID>A235</REQ_ID>
<PRICE />
<QTY />
</OFFER_DT>
</rfc:ZIXI_001_EMP_DET>
Why this is happening I don't know. is there any constraint with SAP XI 3.0 that we can not pass values using structure?...
Or any configuration needs to be done?
Please help....

Guess I got it... U should define the structure as Tables parameter and not as Import Parameter...
should be like
FUNCTION ZIXI_001_EMP_DET.
""Local Interface:
*" TABLES
*" EMP_DET STRUCTURE ZIXI_EMP
*" OFFER_DT STRUCTURE ZXI_OFFER_DATA
ENDFUNCTION.
~SaNv...
Edited by: Santhosh Kumar V on Mar 18, 2010 6:35 PM

Problem in creating data type

hi..
i've problem in creating data type in xi after importing idoc from the R/3 sender
plz tell me the basic steps for creating data type in the receiver i.e xi.....
thanks in advance

Hi,
You don't need to create a data type after importing the IDOC.
Idoc itself acts as message type and message interface.
check this for creating a data type..
http://help.sap.com/saphelp_nw70/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
Thanks,
Vijaya.

IDOC - XI - IDOC scenario. I can't import XSD to Data Type

Helo!
I have some problem with creating data tape. I have to create data type similar to IDOC structure which i imported from SAP system. Similar becouse in this DT I need to add some more elements. Becouse the IDOC structure is large I wont to import IDOC structure to this DT automaticly. I try to eksport XSD structure of my IDOC and then import to data type but i can read the monit:
The tag <element> is not allowed at <<xsd:schema><xsd:element><xsd:element>>.
I'm beginer in XSD so I don't now how to change this file.
Can somebody help me on that or explain whot I can do to make this DT.
Thanks for answer!

Hi,
U can import the IDoc XSD to External defination and use it in your Message Mapping and Interfacing Mapping.
There is no need to create a data type of message type for IDoc.
External Defination
External Definition enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to be used as a description for a message.
U can use this ED as
1.Inbound/Outbound in the Message Interface.
2.Source/Target structure for the Message Mapping.
In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC steps u perform is.
1.Import the IDoc to XI.
2.Export the IDoc(i.e XSD format) and save it to the local machine.
3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
4.Save it as an XSD file Itself.
5.Import the XSD file in the IR under the External Defination.
6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
Regards
Santhosh
<a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
Use a Good Subject Line, One Question Per Posting - Award Points

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

XSD imported as Data Type

Hi All!
I am very new to XI. As in this is my first project. I did look for this question in the forum, but I probably missed it as the wording would have to be close to my own. Anyway-
I am trying to import an XSD into a data type. I keep getting an error:
Attribute "name" of element "/schema/element("Name") has the value "Name" that has already been used in the element "/schema". Ensure all attributes and elements of each element have unique names when using the xsd editor.
Well - I'm very confused. This is the XSD that I was given for an outbound process. Any suggestions on what to do? XSD is below.
Thank you!
Michelle
XSD:
<xsd:schema xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<xsd:element name='ShipperLoadPlan'>
<xsd:complexType>
 <xsd:sequence>
 <xsd:element ref='LoadNumber'/>
 <xsd:element ref='LeanLoadID'/>
 <xsd:element ref='Canceled'/>
 <xsd:element ref='DirectionCategory'/>
 <xsd:element ref='TrailerNumber' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='ReferenceNums' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='Carrier' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='Stops' minOccurs='0' maxOccurs='1'/>
 </xsd:sequence>
 <xsd:attribute name='CreateDate' type='xsd:string' use='optional'/>
 <xsd:attribute name='ExecutionEvent' type='xsd:string' use='optional'/>
 <xsd:attribute name='ExecutionEventID' type='xsd:string' use='optional'/>
</xsd:complexType>
</xsd:element>
<xsd:element name='ReferenceNums'>
<xsd:complexType>
 <xsd:sequence>
 <xsd:element ref='Reference' maxOccurs='unbounded'/>
 </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='Reference'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
 <xsd:attribute name='type' type='xsd:string' use='required'/>
 </xsd:extension>
 </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='Stops'>
<xsd:complexType>
 <xsd:sequence>
 <xsd:element ref='Stop' maxOccurs='unbounded'/>
 </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='Stop'>
<xsd:complexType>
 <xsd:sequence>
 <xsd:element ref='StopNumber'/>
 <xsd:element ref='StopType'/>
 <xsd:element ref='CalcDueDate' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='DueDate' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='Appt' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='ETADate' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='ArrivalDate' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='DepartureDate' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='Location'/>
 <xsd:element ref='LoadDates' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='ReferenceNums' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='OrderNums'/>
 </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='LoadDates'>
<xsd:complexType>
 <xsd:sequence>
 <xsd:element ref='LoadDate' maxOccurs='unbounded'/>
 </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='LoadDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
 <xsd:attribute name='DateTypeID' type='xsd:string' use='required'/>
 <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
 </xsd:extension>
 </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='OrderNums'>
<xsd:complexType>
 <xsd:sequence>
 <xsd:element ref='OrderNum' maxOccurs='unbounded'/>
 </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='OrderNum' type='xsd:string'>
</xsd:element>
<xsd:element name='Carrier'>
<xsd:complexType>
 <xsd:sequence>
 <xsd:element ref='SCAC'/>
 <xsd:element ref='Name'/>
 <xsd:element ref='VendorNumber' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='TenderSCAC' minOccurs='0' maxOccurs='1'/>
 </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='Location'>
<xsd:complexType>
 <xsd:sequence>
 <xsd:element ref='LocationRef'/>
 <xsd:element ref='Name'/>
 <xsd:element ref='Address1' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='Address2' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='Address3' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='City' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='State' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='Zip' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='Country' minOccurs='0' maxOccurs='1'/>
 <xsd:element ref='IsPoolPoint' minOccurs='0' maxOccurs='1'/>
 </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='LoadNumber' type='xsd:string'>
</xsd:element>
<xsd:element name='Canceled' type='xsd:string'>
</xsd:element>
<xsd:element name='LeanLoadID' type='xsd:string'>
</xsd:element>
<xsd:element name='DueDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
 <xsd:attribute name='Start' type='xsd:string' use='optional'/>
 <xsd:attribute name='End' type='xsd:string' use='optional'/>
 <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
 </xsd:extension>
 </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='Appt'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
 <xsd:attribute name='From' type='xsd:string' use='optional'/>
 <xsd:attribute name='To' type='xsd:string' use='optional'/>
 <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
 <xsd:attribute name='ApptRef' type='xsd:string' use='optional'/>
 </xsd:extension>
 </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='ETADate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
 <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
 </xsd:extension>
 </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='ArrivalDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
 <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
 </xsd:extension>
 </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='DepartureDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
 <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
 </xsd:extension>
 </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='CalcDueDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
 <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
 </xsd:extension>
 </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='SCAC' type='xsd:string'>
</xsd:element>
<xsd:element name='Name' type='xsd:string'>
</xsd:element>
<xsd:element name='VendorNumber' type='xsd:string'>
</xsd:element>
<xsd:element name='TimeZone' type='xsd:string'>
</xsd:element>
<xsd:element name='CreateDate' type='xsd:string'>
</xsd:element>
<xsd:element name='ExecutionEvent' type='xsd:string'>
</xsd:element>
<xsd:element name='TenderSCAC' type='xsd:string'>
</xsd:element>
<xsd:element name='ExecutionEventID' type='xsd:string'>
</xsd:element>
<xsd:element name='TrailerNumber' type='xsd:string'>
</xsd:element>
<xsd:element name='DateTypeID' type='xsd:string'>
</xsd:element>
<xsd:element name='StopNumber' type='xsd:string'>
</xsd:element>
<xsd:element name='StopType' type='xsd:string'>
</xsd:element>
<xsd:element name='DirectionCategory' type='xsd:string'>
</xsd:element>
<xsd:element name='LocationRef' type='xsd:string'>
</xsd:element>
<xsd:element name='Name' type='xsd:string'>
</xsd:element>
<xsd:element name='Address1' type='xsd:string'>
</xsd:element>
<xsd:element name='Address2' type='xsd:string'>
</xsd:element>
<xsd:element name='Address3' type='xsd:string'>
</xsd:element>
<xsd:element name='City' type='xsd:string'>
</xsd:element>
<xsd:element name='State' type='xsd:string'>
</xsd:element>
<xsd:element name='Zip' type='xsd:string'>
</xsd:element>
<xsd:element name='Country' type='xsd:string'>
</xsd:element>
<xsd:element name='IsPoolPoint' type='xsd:string'>
</xsd:element>
</xsd:schema>

Hi ,
I don't know your requirement in detail , If you are using XSD, no need to create data type message type , upload this XSD to ' EXTERNAL DEFINITIONS' , you can use this XSD directly in Message mapping ( MM) .

Issue with xsd Data type mapping for collection of user defined data type

Hi,
I am facing a issue with wsdl for xsd mapping for collection of user defined data type.
Here is the code snippet.
sample.java
@WebMethod
public QueryPageOutput AccountQue(QueryPageInput qpInput)
public class QueryPageInput implements Serializable, Cloneable
protected Account_IO fMessage = null;
public class QueryPageOutput implements Serializable, Cloneable
protected Account_IO fMessage = null;
public class Account_IO implements Serializable, Cloneable {
protected ArrayList <AccountIC> fintObjInst = null;
public ArrayList<AccountIC>getfintObjInst()
return (ArrayList<AccountIC>)fintObjInst.clone();
public void setfintObjInst(AccountIC val)
fintObjInst = new ArrayList<AccountIC>();
fintObjInst.add(val);
Public class AccountIC
protected String Name;
protected String Desc;
public String getName()
return Name;
public void setName(String name)
Name = name;
For the sample.java code, the wsdl generated is as below:
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions
name="SimpleService"
targetNamespace="http://example.org"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://example.org"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
>
<wsdl:types>
<xs:schema version="1.0" targetNamespace="http://examples.org" xmlns:ns1="http://example.org/types"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.org/types"/>
<xs:element name="AccountWSService" type="ns1:accountEMRIO"/>
</xs:schema>
<xs:schema version="1.0" targetNamespace="http://example.org/types" xmlns:ns1="http://examples.org"
xmlns:tns="http://example.org/types" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://examples.org"/>
<xs:complexType name="queryPageOutput">
<xs:sequence>
<xs:element name="fSiebelMessage" type="tns:accountEMRIO" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="accountEMRIO">
<xs:sequence>
<xs:element name="fIntObjectFormat" type="xs:string" minOccurs="0"/>
<xs:element name="fMessageType" type="xs:string" minOccurs="0"/>
<xs:element name="fMessageId" type="xs:string" minOccurs="0"/>
<xs:element name="fIntObjectName" type="xs:string" minOccurs="0"/>
<xs:element name="fOutputIntObjectName" type="xs:string" minOccurs="0"/>
<xs:element name="fintObjInst" type="xs:anyType" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="queryPageInput">
<xs:sequence>
<xs:element name="fPageSize" type="xs:string" minOccurs="0"/>
<xs:element name="fSiebelMessage" type="tns:accountEMRIO" minOccurs="0"/>
<xs:element name="fStartRowNum" type="xs:string" minOccurs="0"/>
<xs:element name="fViewMode" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.org"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://example.org" xmlns:ns1="http://example.org/types">
<import namespace="http://example.org/types"/>
<xsd:complexType name="AccountQue">
<xsd:sequence>
<xsd:element name="arg0" type="ns1:queryPageInput"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="AccountQue" type="tns:AccountQue"/>
<xsd:complexType name="AccountQueResponse">
<xsd:sequence>
<xsd:element name="return" type="ns1:queryPageOutput"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="AccountQueResponse" type="tns:AccountQueResponse"/>
</schema>
</wsdl:types>
<wsdl:message name="AccountQueInput">
<wsdl:part name="parameters" element="tns:AccountQue"/>
</wsdl:message>
<wsdl:message name="AccountQueOutput">
<wsdl:part name="parameters" element="tns:AccountQueResponse"/>
</wsdl:message>
<wsdl:portType name="SimpleService">
<wsdl:operation name="AccountQue">
<wsdl:input message="tns:AccountQueInput" xmlns:ns1="http://www.w3.org/2006/05/addressing/wsdl"
ns1:Action=""/>
<wsdl:output message="tns:AccountQueOutput" xmlns:ns1="http://www.w3.org/2006/05/addressing/wsdl"
ns1:Action=""/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SimpleServiceSoapHttp" type="tns:SimpleService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="AccountQue">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SimpleService">
<wsdl:port name="SimpleServicePort" binding="tns:SimpleServiceSoapHttp">
<soap:address location="http://localhost:7101/WS-Project1-context-root/SimpleServicePort"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
In the above wsdl the collection of fintObjInst if of type xs:anytype. From the wsdl, I do not see the xsd mapping for AccountIC which includes Name and Desc. Due to which, when invoking the web service from a different client like c#(by creating proxy business service), I am unable to set the parameters for AccountIC. I am using JAX-WS stack and WLS 10.3. I have already looked at blog http://weblogs.java.net/blog/kohlert/archive/2006/10/jaxws_and_type.html but unable to solve this issue. However, at run time using a tool like SoapUI, when this wsdl is imported, I am able to see all the params related to AccountIC class.
Can some one help me with this.
Thanks,
Sudha.

Did you try adding the the XmlSeeAlso annotation to the webservice
@XmlSeeAlso({<package.name>.AccountIC.class})
This will add the schema for the data type (AccountIC) to the WSDL.
Hope this helps.
-Ajay

Can I use Non-standard XSD Data Types in my XSD; if so how?

Please help if you can, this is a complex question, so bear with me.
Also note that I am in Livecycle 8.2 ES (not ES2 or higher).
I am working on creating XSD schemas to map to form objects.
I have created one master schema document that is wired into multiple forms, and I have one separate schema for reusable form objects, that I refer to as a "common node".
All of my individual form schemas are brought together in this one Master Schema via the use of include statements.
EXAMPLE: This is like my Master Schema
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" >
<xs:include schemaLocation="./commonElementsNode.xsd" />
<xs:include schemaLocation="./form1111.xsd" />
<xs:include schemaLocation="./form2222.xsd" />
<xs:include schemaLocation="./form3333.xsd" />
<xs:element name="form">
<xs:complexType>
<xs:sequence>
 <xs:element ref="commonElementsNode" />
 <xs:element ref="form1111" />
 <xs:element ref="form2222" />
 <xs:element ref="form3333" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
This works fine.
I can load this up in Designer in the Data View and everything appears in the Data View hierarchy correctly, with "form" as the top node.
And as long as I use standard "xs:" data types - everything works great. So if I go into LiveCycle Designer and I go to File --> Form Properties --> Preview --> Generate Preview Data and generate dummy XML data - it respects my XSD conventions.
Now here is where the problem arises:
In these schemas, I need to define the data types.
The client I am working for needs me to use their data types.
These data types are not standard xs: data types, like "xs:string" or "xs:date".
Rather, the data types are ones that have been defined in other schemas and reserved to a namespace.
For instance, rather than use xs:date I need to use something like: "myns:DateType"
This "myns:DateType" is defined as:
<xs:complexType name="DateType">
<xs:simpleContent>
 <xs:extension base="xs:date">
 <xs:attribute name="format" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation xml:lang="en">
 <mydoc:Name>Date Format Text</mydoc:Name>
 <mydoc:Definition>The format of the date content</mydoc:Definition>
 <mydoc:PrimitiveType>string</mydoc:PrimitiveType>
 </xs:documentation>
 </xs:annotation>
 </xs:attribute>
 </xs:extension>
</xs:simpleContent>
</xs:complexType>
Note that I have redacted this data type slightly and changed the namespace to protect the anonymity of my client, but we can assume that their data type is valid and currently in use with other systems.
It conforms to W3 standards.
Note also how this type is an enumeration of the base type "xs:date".
This is defined in a schema called something like "MyCoreTypes.xsd"
There is a namespace reservation in this file that looks something like this:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"
xmlns:myns="http://clinetname.com/schemas/mycoretypes" >
So there is a name space reservation there.
In my aforementioned "Master Schema" file, I have an include statement that looks like this:
<xs:include namespace="http://clinetname.com/schemas/mycoretypes" schemaLocation="./MyCoreTypes.xsd" />
(let's assume that the schema is in the same folder, as the Master Schema, so we can use the "./" relative path.)
Now the problems is that in all my forms, where I have a myns:DateType (e.g.: in form1111, a "Date of Birth" element that looks like this: <xs:element name="OwnerBirthDt" type="myns:DateType"/> ) the XSD is not respected when the XML dummy data is generated in LiveCycle Designer implying that the XSD's data types are not being recognized properly.
Has anyone had this problem before?
Is there a solution?
Is it even possible to use these kind of include or import references in LiveCycle to define a data type other that the standard "xs:" data types?
Please let me know - it would be greatly appreciated.
I am more than willing to clarify the question further if others are willing to help.
Thanks -
Ben Lyons

prf.kishorekumar wrote:
i came here with a hope that I would definitely get some help.
pls.. some one reply1) You got some help. No where do I see thanks or acknowledgment for the information given.
2) Please remember that people on the forum help others voluntarily, it's not their job.
3) Google can often help you here if the forum can't. Using Google I found this interesting link:
http://today.java.net/pub/a/today/2004/05/24/html-pt1.html
It discusses the Swing HTML EditorKit as well as some other free HTML renderers.
Edited by: petes1234 on Oct 24, 2007 7:29 PM

Error While creating Data type from a XSD

Hi,
I am trying to import a XSD into my Data type. I have changed the namespace in the XSD to match that of the target namespace. I am getting the following error.
Global definition Element: http://ls.sbc.com/OMS/ProcessSalesOrderEFE004, orderRequest in the schema to be edited will be ignored
Schema to be edited defines qualified element names (elementFormDefault = 'qualified')
Could any help me out in this regard. I don't have much knowledge about XML and XSD.
Regards,
Ravikanth

Hi Ravi,
please check once again your XSD file.
it should be like this.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://ls.sbc.com/OMS/ProcessSalesOrderEFE004, " targetNamespace="http://ls.sbc.com/OMS/ProcessSalesOrderEFE004, ">
 <xsd:complexType name="DTO_Data type">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 725b8b10c99e11dc8ff3001cc43a8a68
 </xsd:appinfo>
Please check the name of data type u mentioned in XSD while imporitng.
regards
mahesh..

Using imported data types

Hi,
While modeling a NW BPM process I wanted to create my own data types. After I have imported a Enterprise Service by SAP all the used data types are accessible in the imported namespace. I can even use them as types for DOs but unfortunately not as reference data types while creating my own xsd files. Am I doing anything wrong is it just not possible to do this?
Thanks,
Manfred

This is unfortunately a conceptial problem with WSDL: XSD types and elements that are defined in the inline schema of WSDLs cannot be imported into other WSDs.
If you have a WSDL that has the interesting types in an extenal XSD, you are lucky. In this case you can simply reference them from you new type by setting the visibility in the XSD editor to "workspace".
If not, the unnice thing is that you would need to either refactor the WSDL (taking the types out into an external XSD) or you need to copy the relevant types.
When you copy, you should us a differen namespace. As long as the original type and your copy have a similar structure - mainly the field names stay the same - the automapping is smart enough to copy field-by-field.

How to crete data type from XSD

Hi All,
can anyone tell me ...how to create data type from agiven xsd.
I need urgently....
thanks in advance....

import this XSD, load this in your mapping editor and then use this to crate the datatype manually.
Or, use XML spy, load this XSD and then you should be able to see the Structure, or,
Look into the XSD data and decipher things yourself
Regards
Bhavesh

Regarding Changing the Namespace And Data Type in XSD File

Hi All,
I am Doing File -
IDOC Interface.
I have XSD File For File Sysyetm and IDOC For ECC.
In XSD File I Have Different Name Space And Data Type ,
I Created the Data Type as Same as the XSD File Data type
I Have Namespaces Are Different,
So,I Changed the Namespace in the XSD File with the New Namespace Which I created in IR.
I Changed in Two Places Like this
<xsd:schema targetNamespace="http://Sample1.com/xi/file;" xmlns="http://Sample1.com/xi/file;"
But it is giving Error lik this
Cannot load schema with the target namespace http://xxx.com/xi/xx/vamsi/100 to namespace http://Sample1.com/xi/file;
Regards
Vamsi

Hi Vasanth,
Thats what I am Asking
I want to Import XSD File in Data Type
Before I Import the XSD File into Data type I changed the Namespace in the XSD to My Namespace Which is in IR. And I Created the Data Type Name in IR Which I Have in XSD FIle .
So I Am Getting this Error
Please Let me Know Wat to do
Regards
Vamsi

Data Type - XSD IMPORT

Similar Messages

Maybe you are looking for