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/

Similar Messages

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

Time Data Type when Exporting to Excel

Hello,
I have a report I wrote using crystal reports XI. There is a datetime field which I converted to a time field through the use of a formula and the time function. When I right click on the field and view the data type it says time.
However, when I export to excel the field comes up as a custom field. How do I get it so that the exported field will appear as a time field in excel?
Thank you for your help.

>
Vitaly Izmaylov wrote:
> As far as I know, Crystal Reports does not export field type - only data.
>
> MS Excel defines the type by reviewing first top records and there is a knowledge base article on Microsoft website on this subject.
>
> Could you please give us an example how your time fields look like in Crystal Reports?
The time looks like this:
21:38
10:53
00:14
Thanks,
Athalia

Multi Language Description and Long description update.

Hi Guru,
I would like to know the possible ways to upload the description and long description in multiple languages for the existing items in mass. For newly created items, we can enter the data in language form tied to the description.
Is it possible to do with APC WebADI.? or any other suggestion would be highly appreciable.
Venkatesh

I solved the problem by myself. It's a customizing with OBVU.
Hope it can help others.
Andy

Multi languages support of ComboBox type ahead feature

Hi
From Flex 3 livedocs (http://livedocs.adobe.com/flex/3/html/help.html?content=dpcontrols_5.html):
In its editable state, the user can type text directly into the top of the list, or select one of the preset values from the list. In its noneditable state, as the user types a letter, the drop-down list opens and scrolls to the value that most closely matches the one being entered; matching is only performed on the first letter that the user types.
Flex combo-box indeed supports that type ahead for first letter - in English.
e.g. for the combo box with the following list of items: {"apple","banana","orange"}, when the combo is focused and user is typing 'b' - "banana" will be selected.
when I tried with other languages (i.e. russian) - it doesn't work...
any ideas?
thanks
Itzik

Thanks for you reply.
how can I combine both dataProvider and List in ActionScript to a single comboBox?
in MXML it would look like:
<mx:ComboBox id="combo" dropdownFactory="the.custom.List.sub.class.goes.here">     <mx:dataProvider>
          <mx:Array>
               <mx:String>AAAAAAAA</mx:String>
               <mx:String>ABBBBBBB</mx:String>
          </mx:Array>
     </mx:dataProvider>
</mx:ComboBox>
but in ActionScript I couldn't make it work.
someone?
thanks
Itzik

Data types pls..

Hi All,
What are all the data types we have, let me know each data type purpose pls....
Akshitha.

Data types describe the technical attributes of data objects. They are purely descriptive and do not take up any memory space
Data Types in the ABAP Dictionary
The ABAP Dictionary allows you to define global data types. You can use the TYPE addition of an appropriate ABAP statement to refer to these data types in any ABAP program in the system.
There are three groups on the initial screen:
Database Tables and Views
One of the most important tasks of the ABAP Dictionary is to administer database tables in the R/3 database. The Dictionary contains metadescriptions of the database tables, and uses these to create the physical tables in the database. A view is a "virtual table" containing fields from one or more tables.
In the description of a database table, the table lines consist of single fields or columns. An elementary data type must be assigned to each column. The elementary types in the ABAP Dictionary are data elements. Like data objects in ABAP programs, database tables and views have data types as attributes. A line of a database table or view has the data type of a flat structure, which consists of individual data elements.
In ABAP programs, you can use the TYPE addition with the data type of a database table or view. You may refer to the whole structure or to individual components:
... TYPE <dbtab> ...
refers to the complex data type of the structure,
... TYPE <dbtab>-<ci> ...
refers to the elementary data type of component <ci>.
If you define a complex data type <t> as a structure using
TYPES <t> TYPE <dbtab>.
the components of the data type <t> inherit the names of the components of the database table or view, and can be addressed in the program using <t>-<ci>.
To ensure compatibility with previous releases, you can still use the LIKE addition to refer to database tables or views, except within classes. The reason for this is that in earlier releases, the physical presence of the database tables as objects was emphasized, even though the Dictionary only contains metadescriptions and data types.
Defining program-local data types by referring to database tables and views is one of the essential techniques for processing data from database tables in ABAP. Data objects that you define in this way always have the right type to contain data from the corresponding database table. ABAP Open SQL allows you to read a single field, a range of fields, or an entire database table or view into an internal table.
TYPES: city type spfli-cityfrom,
       spfli_type TYPE STANDARD TABLE OF spfli WITH DEFAULT KEY.
DATA: wa_city TYPE city,
      wa_spfli TYPE spfli_type.
SELECT SINGLE cityfrom FROM spfli
                       INTO wa_city
                       WHERE carrid = 'LH' AND connid = '400'.
SELECT * FROM spfli INTO TABLE wa_spfli.
This example defines an elementary data type CITY that refers to a single field of the database table SPFLI and an internal table SPFLI_TYPE, whose line type is the same as the structure of the database table. The SELECT statement reads data from the database into the corresponding data objects.
Data types
Data types are the actual type definitions in the ABAP Dictionary. They allow you to define elementary types, reference types, and complex types that are visible globally in the system. The data types of database tables are a subset of all possible types, namely flat structures. Global object types (classes and interfaces) are not stored in the ABAP Dictionary, but in the class library. You create them using the Class Builder.
For a detailed description of data types and their definitions, refer to the Types section of the ABAP Dictionary documentation. The following descriptions mention the types only briefly, along with how you can refer to them from ABAP programs.
Data Elements
Data elements in the ABAP Dictionary describe individual fields. They are the smallest indivisible units of the complex types described below, and are used to specify the types of columns in the database. Data elements can be elementary types or reference types.
Elementary Types
Elementary types are part of the dual-level domain concept for fields in the ABAP Dictionary. The elementary type has semantic attributes, such as texts, value tables, and documentation, and has a data type. There are two different ways to specify a data type:
By directly assigning an ABAP Dictionary type.
You can assign a predefined ABAP Dictionary type and a number of characters to an elementary type. The ABAP Dictionary has considerably more predefined types than the ABAP programming language. The number of characters here is not the field length in bytes, but the number of valid characters excluding formatting characters. The data types are different because the predefined data types in the ABAP Dictionary have to be compatible with the external data types of the database tables supported by the R/3 System.
When you refer to data types from the ABAP Dictionary in an ABAP program, the predefined Dictionary types are converted to ABAP types as follows:
Dictionary type
Meaning
Maximum length n
ABAP type
DEC
Calculation/amount field
1-31, 1-17 in tables
P((n+1)/2)
INT1
Single-byte integer
3
Internal only
INT2
Two-byte integer
5
Internal only
INT4
Four-byte integer
10
I
CURR
Currency field
1-17
P((n+1)/2)
CUKY
Currency key
5
C(5)
QUAN
Amount
1-17
P((n+1)/2)
UNIT
Unit
2-3
C(n)
PREC
Accuracy
2
X(2)
FLTP
Floating point number
16
F(8)
NUMC
Numeric text
1-255
N(n)
CHAR
Character
1-255
C(n)
LCHR
Long character
256-max
C(n)
STRING.
String of variable length
1-max
STRING.
RAWSTRING
Byte sequence of variable length
1-max
XSTRING
DATS
Date
8
D
ACCP
Accounting period YYYYMM
6
N(6)
TIMS
Time HHMMSS
6
T
RAW
Byte sequence
1-255
X(n)
LRAW
Long byte sequence
256-max
X(n)
CLNT
Client
3
C(3)
LANG
Language
internal 1, external 2
C(1)
("max" in LCHR and LRAW is the value of a preceding INT2 field. The "internal" length of a LANG field is in the Dictionary, the "external" length refers to the display on the screen.
Assigning a domain
The technical attributes are inherited from a domain. Domains are standalone Repository objects in the ABAP Dictionary. They can specify the technical attributes of a data element. One domain can be used by any number of data elements. When you create a domain, you must specify a Dictionary data type (see above table) and the number of characters.
Reference Types
Reference types describe single fields that can contain references to global classes and interfaces from the ABAP class library.
In an ABAP program, you can use the TYPE addition to refer directly to a data element. The predefined Dictionary data types of the domain are then converted into the corresponding ABAP types.
If you define a local data type in a program by referring to a data element as follows:
TYPES <t> TYPE <data element>.
the semantic attributes of the data element are inherited and will be used, for example, when you display a data object with type <t> on the screen. Since all data types in the ABAP Dictionary are based on data elements, they all contain the corresponding semantic attributes.
TYPES company TYPE s_carr_id.
DATA wa_company TYPE company.
wa_company = 'UA '.
WRITE: 'Company:', wa_company.
This example defines a local type COMPANY that refers to the data element S_CARR_ID. The data element is linked to the identically-named domain S_CARR_ID. The domain defines the technical attributes as data type CHAR with length 3. The local data type COMPANY in the program therefore has the ABAP type C(3). COMPANY also adopts the semantic attributes of the data element. In the above example, we declare a data object WA_COMPANY with this type and display it on a list. If the user chooses F1 help for the output field, the help text stored in the ABAP Dictionary will appear in a dialog box.
Structures
A structure is a sequence of any other data types from the ABAP Dictionary, that is, data elements, structures, table types, or database tables. When you create a structure in the ABAP Dictionary, each component must have a name and a data type.
In an ABAP program, you can use the TYPE addition to refer directly to a structure.
If you define a local data type in a program by referring to a structure as follows:
TYPES <t> TYPE <structure>.
the construction blueprint of the structure is used to create a local structure <t> in the program. The predefined Dictionary data types of the domains used by the data elements in the structure are converted into the corresponding ABAP types. The semantic attributes of the data elements are used for the corresponding components of the structure in the program. The components of the local structure <t> have the same names as those of the structure in the ABAP Dictionary.
To ensure compatibility with previous releases, it is still possible to use the LIKE addition in an ABAP program to refer to a structure in the ABAP Dictionary (except in classes).
Suppose the structure STRUCT is defined as follows in the ABAP Dictionary:
Field name
Type name
Description
COL1
CHAR01
Character field with length 1
COL2
CHAR08
Character field with length 8
COL3
CHAR10
Character field with length 10
The types CHAR01 to CHAR10 are data elements with corresponding domains. We can refer to this structure in ABAP:
TYPES struct_type TYPE struct.
DATA wa TYPE struct_type.
wa-col1 = '1'.
wa-col2 = '12345678'.
wa-col3 = '1234567890'.
This program creates a local structure in the program - STRUCT_TYPE - and a corresponding data object WA. We can address the components using the component names from the original structure.
Table Types
Table types are construction blueprints for internal tables that are stored in the ABAP Dictionary. When you create a table type in the ABAP Dictionary, you specify the line type, access type, and key. The line type can be any data type from the ABAP Dictionary, that is, a data element, a structure, a table type, or the type of a database table. You can also enter a predefined Dictionary type directly as the line type, in the same way that you can with a domain.
In an ABAP program, you can use the TYPE addition to refer directly to a table type.
If you define a local data type in a program by referring to a table type as follows:
TYPES <t> TYPE <table>.
the construction blueprint of the table type is used to create a local internal table <t> in the program. The predefined Dictionary data types of the domains used by the data elements in the structure are converted into the corresponding ABAP types. The semantic attributes of the data elements are used for the corresponding components of the internal table in the program.
Suppose the table type STRUCT_TABLE is defined in the Dictionary with the line type STRUCT from the previous example. We can refer to this in ABAP:
TYPES table_type TYPE struct_table.
DATA: table_wa TYPE table_type,
      line_wa LIKE LINE OF table_wa.
LOOP AT table_wa INTO line_wa.
WRITE: line_wa-col1, line_wa-col1, line_wa-col1.
ENDLOOP.
This program defines an internal table type TABLE_TYPE. From it, we define data objects TABLE_WA and LINE_WA. LINE_WA corresponds to the line type of the table type in the Dictionary, and is therefore compatible with the structure STRUCT.
Type Groups
Before Release 4.5A, it was not possible to define standalone types in the ABAP Dictionary to which you could refer using a TYPE addition in an ABAP program. It was only possible to refer to flat structures. Structures in programs corresponded to the structures of database tables or structures in the ABAP Dictionary. In ABAP programs, you could only refer to database tables and structures in the ABAP Dictionary using LIKE. It was, however, possible to refer to individual components of the Dictionary type. Complex local data types such as internal tables or deep structures had no equivalent in the ABAP Dictionary. The solution to this from Release 3.0 onwards was to use type groups. Type groups were based on the include technique, and allowed you to store any type definitions globally in the Dictionary by defining them using TYPES statements.
The definition of a type group is a fragment of ABAP code which you enter in the ABAP Editor. The first statement for the type group <pool> is always:
TYPE-POOL <pool>.
After this came the definitions of data types using the TYPES statement, as described in Local Data Types in Programs. It was also possible to define global constants using the CONSTANTS statement. All the names of these data types and constants must begin with the name of the type group and an underscore:
In an ABAP program, you must declare a type group as follows before you can use it:
TYPE-POOLS <pool>.
This statement allows you to use all the data types and constants defined in the type group <pool> in your program. You can use several type groups in the same program.
Let the type group HKTST be created as follows in the ABAP Dictionary:
TYPE-POOL hktst.
TYPES: BEGIN OF hktst_typ1,
                col1(10) TYPE c,
                col2 TYPE i,
       END OF hktst_typ1.
TYPES hktst_typ2 TYPE p DECIMALS 2.
CONSTANTS hktst_eleven TYPE i VALUE 11.
This type group defines two data types HKTST_TYP1 and HKTST_TYP2, as well as a constant HKTST_ELEVEN with the value 11.
Any ABAP program can use these definition by including a TYPE-POOLS statement:
TYPE-POOLS hktst.
DATA: dat1 TYPE hktst_typ1,
      dat2 TYPE hktst_typ2 VALUE '1.23'.
WRITE: dat2, / hktst_eleven.
The output is:
1,23
11
The data types defined in the type group are used to declare data objects with the DATA statement and the value of the constant is, as the output shows, known in the program.

Datamodeler: Structure Data Type

I am working on a design with many entities having common (audit-related) attributes applicable to all of them. I am thinking of defining a Structured Data Type which will be used in all of them. While it is easy to create new Distinct & Collection Data Types by right-clicking on their nodes, it appears there is a bug in creating a new Structured Data Type using the same method. Is there any workaround for this?
Thanks,
Chiedu

Hi Chiedu,
you need to make "Data Types" diagram visible in order to be able to create structured types - use Show from pop-up menu on "data types" node.
Structured types are created only on diagram in current release.
Best regards,
Philip
I see there is short description of Data types model in help.
Edited by: Philip Stoyanov on Mar 12, 2009 6:02 AM

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
<b>External Definition</b> 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

How to set the Data types of the Excel sheet while exporting details to it.

Hi All,
We are trying to export some order details to the excel sheet from a jsp. It is working fine when the local system language is set to English.
But when i change it to Russian. the details like Line Numbers(e.g: 1.1, 1.2, 1.3 and so on... ) are getting changed into some other data type(e.g: 01.янв, 02.янв, 03.янв and so on....).
i guess this is mainly due to some data type mismatch, so i tried setting all the possible charset for response in the jsp, but could not succeeded.
This is only for the details which or of decimal format, working fine for the details which are in String type. like Description, Item name etc...
As it is high preference issue for our client, Please help me in this regard ASAP.
Thanks & Regards,
Praveen Reddy B

hi Shiv..
Its not an OAF page but it is from Apps only (i.e.Oracle iStore).
we tried writing this:
<%response.setContentType("application/vnd.ms-excel; charset=UTF-8");%>
<%response.setHeader("Content-Disposition", "attachment; filename=downloadOrders.xls" );%>
<head>
          <title>Logitech_iStore</title>
<style>
table {
border-style: solid;
table th.mainHeader {
                                        border-style: solid;
background-color:#000099;
border-color:#000000;
color:#FFFFFF;
font-family:Arial, Helvetica, sans-serif;
font-weight:bold;
font-size:13pt;
table th {
                                        border-style: solid;
background-color:#6687C4;
border-color:#000000;
color:#FFFFFF;
font-family:Arial, Helvetica, sans-serif;
font-weight:bold;
font-size:12pt;
table td.color1 {
                                        border-style: solid;
background-color:#FFFFFF;
border-color:#000000;
color:#000000;
font-family:"Times New Roman", Times, serif;
font-weight:normal;
font-size:12pt;
table td.color2 {
                                        border-style: solid;
background-color:#C0C0C0;
border-color:#000000;
color:#000000;
font-family:"Times New Roman", Times, serif;
font-weight:normal;
font-size:12pt;
                              table td {
                                        border-style: solid;
background-color:#FFFFFF;
border-color:#000000;
color:#000000;
font-family:"Times New Roman", Times, serif;
font-weight:normal;
font-size:12pt;
</style>
</head>
          <body>
          <%
                    /*BigDecimal resp_id=RequestCtx.getResponsibilityId();
                    String respIdParam="";
                    String respkey="";
                    if(resp_id!=null)
                    respIdParam=resp_id.toString();
                    out.println("respIdParam"+respIdParam);
                    logi.oracle.apps.ibe.util.LogiDAOImpl dao=new logi.oracle.apps.ibe.util.LogiDAOImpl();
                    respkey=dao.getRespKey(respIdParam);
                    out.println("respkey"+respkey);
          logi.oracle.apps.ibe.util.LogiOrderDetailsBean orderDetailsBean = new logi.oracle.apps.ibe.util.LogiOrderDetailsBean();
                    java.util.ArrayList ls = new java.util.ArrayList();
                    String resp_key=request.getParameter("respkey");
                    System.out.println(resp_key);
                    String noofDays=request.getParameter("noOfDays");
                    String qCustAcctId=request.getParameter("qCustAcctId");
                    logi.oracle.apps.ibe.util.LogiDAOImpl daoimpl=new logi.oracle.apps.ibe.util.LogiDAOImpl();
                    String decideTab=request.getParameter("decideTab");
                    String startDate=request.getParameter("startDate");
                    String endDate=request.getParameter("endDate");
                    String queryCondition=request.getParameter("queryCondition");
                    String queryOperator=request.getParameter("queryOperator");
                    String queryValue=request.getParameter("queryValue");
                    String queryDateValue=request.getParameter("queryDate");
                    System.out.println("queryDateValue"+queryDateValue);
%>
                    <table cellspacing="1" cellpadding="1" width="100%" border="0" class="OraBGAccentDark">
<tr>
<th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ORD_NUM")%></th>
                                   <th>Customer Name</th>
                                   <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ORD_DATE")%></th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_BOOKED_DATE")%></th>
                              <th>Request Date</th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ORD_STATUS")%></th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ORD_PO")%></th>
                              <th>Currency</th>
                                        <th>Payment Terms</th>                                                                      <th>Freight Terms</th>
                                   <th>FOB</th>
                                        <th>Sales Channel</th>
                                        <th>Ship to Location</th>
                                        <th>Bill to Location</th>
                                        <th>SalesTerritory Country</th>
                                        <th>Order Type</th>
                                        <th>Order Total</th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_LINE_NUM")%></th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ITEM")%></th>
                                        <th>Customer SKU</th>
                                        <th>Description</th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_QTY")%></th>
                                        <th>Shipped Quantity</th>
                                        <th>ScheduleShip Date</th>
                                        <th>Unit Price</th>
                                        <th>Extented Amount</th>
                                        <th>Taxes Total</th>
                                        <th>Freight Charges</th>
                                        <th>Case pack charge</th>
                                        <th>Charges Total</th>
                                   <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_LINE_STATUS")%></th>
                                        <th>Ship Date</th>
                                        <th>Warehouse</th>
                                        <th>Tracking Number</th>
                                        <th>Waybill Number</th>
                                        <th>Delivery Number</th>
                                        <th>Pro Number</th>
                                        <th>Hold Applied</th>
                                        <th>Pallet Qty</th>
                                        <th>Pallet#</th>
                                        <th>Invoice Number</th>
                                        <th>Promo Number</th>
                                        <th>Ship Method</th>
</tr>
<%
                         int pSiteid=0;
                         java.math.BigDecimal mSiteId=oracle.apps.ibe.util.RequestCtx.getMinisiteId();
                         if(mSiteId!=null)
                         pSiteid=mSiteId.intValue();
                         out.println("pSiteid"+pSiteid);
               if(decideTab!=null && decideTab.trim().equalsIgnoreCase("days"))
                         if(qCustAcctId!=null)
                                   ls=daoimpl.downOrderDetails(qCustAcctId,noofDays,pSiteid);
                    else if(decideTab!=null && decideTab.trim().equalsIgnoreCase("dates"))
                         if(qCustAcctId!=null)
                                   ls=daoimpl.downOrderDateDetails(qCustAcctId,queryDateValue,startDate,endDate);
                    else if(decideTab!=null && decideTab.trim().equalsIgnoreCase("condition"))
                         if(qCustAcctId!=null)
                                   ls=daoimpl.downOrderConditionDetails(qCustAcctId,queryCondition,queryOperator,queryValue);
                    for(int i=0;i<ls.size();i++)
                         orderDetailsBean=(logi.oracle.apps.ibe.util.LogiOrderDetailsBean)ls.get(i);
                         String orderNumber= orderDetailsBean.getOrderNumber();          //Order Number
                         if(orderNumber==null)orderNumber="";
                         String customerName=orderDetailsBean.getCustomerName();          //Customer Name
                         if(customerName==null)customerName="";
                    String orderedDate=orderDetailsBean.getOrderDate();               //Order Date
                         if(orderedDate==null)orderedDate="";
                         String bookeddate= orderDetailsBean.getBookedDate();          //Booked Date
                         if(bookeddate==null)bookeddate="";
                         String requestdate= orderDetailsBean.getRequestDate();          //Requested Date
                         if(requestdate==null)requestdate="";
                         String orderstatus= orderDetailsBean.getOrderStatus();          //Order Status
                         if(orderstatus==null)orderstatus="";
                         String ponumber= orderDetailsBean.getPoNumber();               //PO Number
                         if(ponumber==null)ponumber="";
                         String currency=orderDetailsBean.getCurrencyCode();               //Currency
                         if(currency==null)currency="";
                         String paymentterms= orderDetailsBean.getPaymentTerms();     //Payment Terms
                         if(paymentterms==null)paymentterms="";
                         String frieghtterms=orderDetailsBean.getFreightTerms();          //Freight Terms
                         if(frieghtterms==null)frieghtterms="";
                         String fobterms=orderDetailsBean.getFobTerms();                    //Fob Terms
                         if(fobterms==null)fobterms="";
                         String saleschannel=orderDetailsBean.getSalesTerms();          //Sales Channel
                         if(saleschannel==null)saleschannel="";
                         String billtoloc=orderDetailsBean.getBillToLocation();          // Bill to Location
                         if(billtoloc==null)billtoloc="";
                         String shiptoloc=orderDetailsBean.getShipToLocation();          //Ship To Location
                         if(shiptoloc==null)shiptoloc="";
                         String salesterr=orderDetailsBean.getSalesCountry();          // Sales Territory
                         if(salesterr==null)salesterr="";
                         String ordertype=orderDetailsBean.getOrderType();               // Order Type
                         if(ordertype==null)ordertype="";
                         String ordertotal=orderDetailsBean.getOrderTotal();               //Order Total
                         if(ordertotal==null)ordertotal="";
                         String linenumber=orderDetailsBean.getLinenumber();               //Line Number
                         if(linenumber==null)linenumber="";
                         String item= orderDetailsBean.getItem();                         //Item Name
                         if(item==null)item="";
                         String sku= orderDetailsBean.getCustomerSKU();               // Customer SKU
                         if(sku==null)sku="";
                         String desc= orderDetailsBean.getDescription();               //Item Description
                         if(desc==null)desc="";
                         desc = URLEncoder.encode(desc);                                        // Added by Sunil
                         desc = URLDecoder.decode(desc);
                         String qty=orderDetailsBean.getQty();                              //Ordered Quantity
                         if(qty==null)qty="";
                         String shippedqty=orderDetailsBean.getShippedQty();               //Shipped Quantity
                         if(shippedqty==null)shippedqty="";
                         String scheduleqty=orderDetailsBean.getScheduleDate();          //Schedule Date
                         if(scheduleqty==null)scheduleqty="";
                         String unitprice=orderDetailsBean.getUnitPrice();               //Unit Price
                         if(unitprice==null)unitprice="";
                         String xamount=orderDetailsBean.getXAmount();                    //Extended Amount
                         if(xamount==null)xamount="";
                         String taxestotal=orderDetailsBean.getTaxesTotal();               //Taxes Total
                         if(taxestotal==null)taxestotal="";
                         String freightcharges=orderDetailsBean.getFreightCharges();//Freight Charges
                         if(freightcharges==null)freightcharges="";
                         String palletcharges=orderDetailsBean.getPalletSurcharge();     //Pallet Charges
                         if(palletcharges==null)palletcharges="";
                         String chargestotal=orderDetailsBean.getChargesTotal();          //Charges Total
                         if(chargestotal==null)chargestotal="";
                         String linestatus=orderDetailsBean.getLinestatus();               //Line Status
                         if(linestatus==null)linestatus="";
                         String shipdate=orderDetailsBean.getShipDate();                    //Ship Date
                         if(shipdate==null)shipdate="";
                         String warehouse=orderDetailsBean.getWareHouse();               //Ware House
                         if(warehouse==null)warehouse="";
                         String trackingnumber=orderDetailsBean.getTrackingNumber();//Tracking Number
                         if(trackingnumber==null)trackingnumber="";
                         String waybill=orderDetailsBean.getWayBillnumber();               //Waybill Number
                         if(waybill==null)waybill="";
                         String deliverynumber=orderDetailsBean.getDeliveryNumber();     //Delivery Number
                         if(deliverynumber==null)deliverynumber="";
                         String pronumber=orderDetailsBean.getProNumber();               //Pro Number
                         if(pronumber==null)pronumber="";
                         String holdapplied=orderDetailsBean.getHoldApplied();          //Hold Applied
                         if(holdapplied==null)holdapplied="";
                         String palletqty=orderDetailsBean.getPalletQty();               //Pallet Qty
                         if(palletqty==null)palletqty="";
                         String pallethash=orderDetailsBean.getPalletHash();               //Pallet Hash
                         if(pallethash==null)pallethash="";
                         String invoicenumber=orderDetailsBean.getInvoiceNumber();               //invoice Number
                         if(invoicenumber==null)invoicenumber="";
                         String promonumber=orderDetailsBean.getPromoNumber();               //Promonumber
                         if(promonumber==null)promonumber="";
                         String shipmethod=orderDetailsBean.getShipMethod();               //Promonumber
                    if(shipmethod==null)shipmethod="";
               %>
               <tr>
               <td><%=orderNumber%></td>
               <td><%=customerName%></td>
               <td><%=orderedDate%></td>
               <td><%=bookeddate%></td>
               <td><%=requestdate%></td>
               <td><%=orderstatus%></td>
               <td><%=ponumber%></td>
               <td><%=currency%></td>
               <td><%=paymentterms%></td>
               <td><%=frieghtterms%></td>
               <td><%=fobterms%></td>
               <td><%=saleschannel%></td>
               <td><%=billtoloc%></td>
               <td><%=shiptoloc%></td>
               <td><%=salesterr%></td>
               <td><%=ordertype%></td>
               <td><%=ordertotal%></td>
               <td><%=linenumber%></td>
               <td><%=item%></td>
               <td><%=sku%></td>
               <td><%= desc %></td>
               <td><%=qty%></td>
               <td><%=shippedqty%></td>
               <td><%=scheduleqty%></td>
               <td><%=unitprice%></td>
               <td><%=xamount%></td>
               <td><%=taxestotal%></td>
               <td><%=freightcharges%></td>
               <td><%=palletcharges%></td>
               <td><%=chargestotal%></td>
               <td><%=linestatus%></td>
               <td><%=shipdate%></td>
          <td><%=warehouse%></td>
               <td><%=trackingnumber%></td>
               <td><%=waybill%></td>
               <td><%=deliverynumber%></td>
               <td><%=pronumber%></td>
               <td><%=holdapplied%></td>
               <td><%=palletqty%></td>
               <td><%=pallethash%></td>
               <td><%=invoicenumber%></td>
               <td><%=promonumber%></td>
               <td><%=shipmethod%></td>
               </tr>
               <%     }
          %>
          </table>
          </body>
          </html>
Please suggest the needful...
Praveen Reddy

Language data type problem

I am executing a FM from XI to create a Material with several languages in the form of ES, EN, FR and so on, what is the type that I have to use in the FM for this languages? I use a simple Char 2 type and does not work from XI but If I use SPRAS works fine, the problem is SPRAS is a Char 1 type so the system get confuse with for instance PL and PR.

Hi
The language in R3 is a field of 1 char, so you have to use a data type like SPRAS, if the system gets confuse I believe you need a routine to translate the language symbols from 2 char to 1 char.
In R3 there're the table T002: here it can find both symbols: 1 char and 2 char.
U can use the fm CONVERSION_EXIT_ISOLA_INPUT for translation:
DATA: LANGUAGE_IN(2),
      LANGUAGE_OUT(1).
CALL FUNCTION 'CONVERSION_EXIT_ISOLA_INPUT'
     EXPORTING
          INPUT            = LANGUAGE_IN
     IMPORTING
          OUTPUT           = LANGUAGE_OUT
     EXCEPTIONS
          UNKNOWN_LANGUAGE = 1
          OTHERS           = 2.
Max

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

SQL Developer is not exporting the time part of date data types.

I need to export data from a table using sql developer. The column is a date data type but when I export the data to a csv, xls or an sql file with insert statements, sql developer only includes the date part without the time.
Please kindly advise.
Thanks,
Erika

What is your 4 digits Oracle version ?
What is your SQL Developer version ?
With Oracle XE and a schema named TEST I have:
select * from t
X
04-FÉVR.-2010 21:24:40 If I use Tools/Database Export with all default settings with SQL Developer 2.1.0.63 I get following SQL file:
-- Fichier créé - jeudi-février-04-2010
-- DDL for Table T
CREATE TABLE "T"
   (     "X" DATE
--   DATA FOR TABLE T
--   FILTER = none used
REM INSERTING into T
Insert into T (X) values (to_timestamp('04/02/10 21:24:40,000000000','DD/MM/RR HH24:MI:SS,FF'));
--   END DATA FOR TABLE T
---------------------------------------------------Edited by: P. Forstmann on 4 févr. 2010 21:26

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..

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

Multi language description of data types - xsd export

Similar Messages

Maybe you are looking for