Import WSDL with xsd:long incorrectly results in INT4

When importing a WSDL, all fields marked as xsd:long result in INT4 in the proxy class. But long is [supposed to be|http://www.w3schools.com/schema/schema_dtypes_numeric.asp] 8-byte (64 bit). We thus get the following error:
SOAP:1.001 CX_SY_CONVERSION_OVERFLOW:XSLT exception.
An error occurred when deserializing in the simple transformation program
/1SAI/TXS291D096A2B8E35E8375E.
Overflow converting from '2147483648'
<xsd:element minOccurs="0" name="Available" type="xsd:long"/>

Hello Marc
The only way is to manually edit the WSDL file and replace xsd:long
with xsd:string with pattern="\d+" and length="<n>"or
xsd:decimal with fractionDigits="0" totalDigigs="<n>"
Afterwarts regenerate proxy and you'll see that the
technical ABAP-Type is changed to STRG/DEC.
addtional info:
We recomment to use
xsd:decimal with totalDigits="19"
fractionDigits="0"
This is the shortest DEC that is big enought to accept the largest
xsd:long.
Future sight:
In release SAP_BASIS 702 this workaround is already fixed,
here you can change the technical type for xsd:long in proxy
editor directly to STRG or DEC(0,19) without modify the WSDL.
Thanks
Kenny

Similar Messages

Problem Import WSDL with XSD import Schema

Hi SCN, i have problem
I have a WSDL that references an xsd, but the structure is not visible in PI.
   <wsdl:types>
      <xsd:schema targetNamespace="http://tempuri.org/Imports">
         <xsd:import schemaLocation="http://bilbolab****.net/ServiceItemHO.svc?xsd=xsd0" namespace="http://tempuri.org/" />
         <xsd:import schemaLocation="http://bilbolab.****.net/ServiceItemHO.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
         <xsd:import schemaLocation="http://bilbolab.*****.net/ServiceItemHO.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ItemHO.BO" />
      </xsd:schema>
   </wsdl:types>
   <wsdl:message name="iVistaHO_AddItemHO_InputMessage">
      <wsdl:part name="parameters" element="tns:AddItemHO" />
   </wsdl:message>
WSDL works well using SoapUI.
When imported to PI parameters is not displayed
I Need Help
Thank you.

Hi, Dihiansan. I don't understand your proposal
I need you see the structure in PI how in SoapUI.
It is possible?
Regards

Importing WSDL with external references issue

Hi guys,
pls help me on this:
I have a WSDL file which referes to external data types. Obviously, if I want to create a message mapping I can't see the WSDL data type. How are such situations resolved? How to import external types into PI?
Thx, A.

HI,
You have to inport the WSDL alongwith all its external references.
You can refer the following threads:
Import WSDL with external reference
Re: PI 7.1: Importing a wsdl file with references to other xsd files
http://help.sap.com/saphelp_nwesrce/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm

Importing WSDLs with references to schema

Hi all,
I am trying to invoke a webservice from PI and have imported the WSDLs for the same. But i couldn't see the various data types.
When i noticed that wsdl, i could see that there are rexternal references with relative path.
schemaLocation="..\External\external-common.xsd"/>
So i have a doubt about how to bring these references to PI. Since these are relative path, do i need to change them to absolute path?
If yes, how?
Thanks and best regards,
Kulwant

Hi Kulwant,
The schema files should always be present at the relative paths.
You try out by importing these schema files also under External Definitions along with the main WSDL and check whether they are referenced.
OR
Manipulate the WSDL in any of XML editior and to Include the schema files into the main WSDL. and then import the WSDL.
Regards,
AshwinM

Very strange bug with compareTo: returning incorrect results

Hello everyone! I have used the method compareTo many times to maintain my database project's entries. However recently I have discovered a bug, in which:
a and b both being Storage type objects:
private static class Storage {
object data
int nextData //an array stores the Storage objects
int previousData //this uses an integer to locate previous in array
Problem:
((Comparable)(a.data)).compareTo((Comparable)(b.data)) returns a 3, when a.data is clearly 5, and b.data is clearly 20.
This is very strange, as the compareTo should return a -1 instead of a positive number. Is this a known bug with the compareTo method? I have been using it reliably for many programs but this is the first time it ever occurs to me.

Problem:
((Comparable)(a.data)).compareTo((Comparable)(b.data))
returns a 3, when a.data is clearly 5, and b.data is
clearly 20.
This is very strange, as the compareTo should return a
-1 instead of a positive number. Is this a known bug
with the compareTo method? I have been using it
reliably for many programs but this is the first time
it ever occurs to me.Not really... comparing Strings "5" to "20"
is really the same as comparing "5" to "2"
being the first character of the string, difference
being, surprise, surprise = 3.
If you want the Strings to be comparable that way you should left-fill them with spaces or zeros.
Or, better still, override compareTo and make your Storage implement Comparable instead of all that casting of the data objects.

Import WSDL file along with XSD

Hi,
I have a WSDL file which has complex Data types (abc.wsdl). This complex data types are defined in the XSD file (abc-data.xsd).
If I just import WSDL file in ED I am unable to find the Complex Data types in Message Mapping.
How can I use the XSD file along with the WSDL file? Is there any source path as to give or what?
Could you please help me out?

first i will tell how my wsdl file is defined
<xs:element name="authInfo" type="<b>xx:AuthInfo</b>">                                   <xs:annotation>                              <xs:documentation xml:lang="en">                                   Authentication information                         </xs:documentation>                    </xs:annotation>                              </xs:element>
and in my xsd file for xx:AuthInfo
<xs:complexType name="AuthInfo">
          <xs:sequence>
               <xs:element name="acctName" type="tns:CustName">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                         account name.
                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="password" type="tns:AcctPswd">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                        Specify the password                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
when i import wsdl file in Ed i will get two inputs there but only one as "AuthInfo"
but "AuthInfo" has two inputs.
this is how my Target Message Look like
Tree          Occurences          Type
authInfo     1..1                      xx:AuthInfo
i hope i have cleared u..

FB3B2 unable to import WSDL files that contain XSD imports

Much to my dismay, the new WSDL import wizard does not seem
to work on WSDL files that import XSD files. When "Finish" is
pressed, an error dialog states "The WSDL definition could not be
parsed. The wizard cannot complete successfully."
I created a sample WSDL that uses the most basic of XSD
files to demonstrate. Remove the import line from the WSDL and it
will import, with the line it will not.

Hi Jeff,
How are you specifying the WSDL URI?
- If as an absolute path on your machine, make sure there are
no spaces in that path – there is a known issue about path
with spaces and WSDL with imports, and we’re on it. We tried
out your sample WSDL this way and it works.
- If you are specifying it as an HTTP url (accessing it over
the Apache HTTP server, for example), the workaround is a little
more complicated. There are indeed some unresolved issues with the
ActionScript generator. Try putting the wsdl and xsd files inside a
folder in the webroot, and another copy of the xsd in the webroot.
This worked for me - the problem is about locating the imported
document correctly: the introspection correctly uses the sibling
xsd file, while the generator incorrectly looks for that file one
level up. We’ll look into this and fix it.
Please let me know if it starts working or if it still does
not generate the ActionScript client classes. Thank you.
Also, please be aware of another known issue about WSDL with
imports:
http://bugs.adobe.com/jira/browse/FB-7678
(For WSDLs that import other documents, the cached WSDL file should
include the content of the imported documents).
Lacra

PI does not combine .wsdl file with .xsd files.

Hi,
I imported .wsdl file with necessary .xsd files in PI system (7.1).
PI does not find fields in .wsdl already necessary .xsd files imported with .wsdl file.
Is there anyone to help me to solve problem with test it in PI system.
I send .wsdl file and necessary .xsd files as attachment his mail address.
Thanks.

Did you try opening the wsdl file in some XML tool...if there is problem in referring the XSD then it will be visible in the tool itself.....even I am working on PI7.1 and some of the WSDLs are referring XSDs...and i had no problem in using them.....dont know what is failing in your case
Do you want me to send .wsdl and .xsd files zipped into your mail box
instead you can post your wsdl file and the corresponding XSD here in SDN....even a dummy structure would do....we are not allowed to do personal email comunication
Regards,
Abhishek.

Webservice control generation failled with xsd:all in WSDL, why ?

Hi,
When I try to generate a WS-control out of a WSDL with a
<xsd:all> based type e.g. :
<xsd:complexType name="RemoteComment">
                    <xsd:all>
                         <xsd:element name="id" type="xsd:long"/>
                         <xsd:element name="pageId" type="xsd:long"/>
                         <xsd:element name="created" type="xsd:dateTime"/>
                         <xsd:element name="title" nillable="true" type="xsd:string"/>
                         <xsd:element name="url" nillable="true" type="xsd:string"/>
                         <xsd:element name="creator" nillable="true" type="xsd:string"/>
                         <xsd:element name="content" nillable="true" type="xsd:string"/>
                    </xsd:all>
               </xsd:complexType>
(for example Atlassion Conluence's SOAP interface uses this)
I get a ERROR: sites/javapolis/xmlrpc/confluenceservicev1.wsdl Line 3, Col 0: Error in WSDL: Cannot extend a type with 'all' content model
Any ideas anyone ?

dieterd,
Try with xsd:sequence intead of xsd:all ?

Validating WSDL with schema imports

Hello,
i'm trying to validate a WSDL that uses a schema import construction, like
<wsdl:types>
<xsd:schema>

<xsd:import namespace="http://foo" schemaLocation="http://localhost/foo.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="MyMessage">
<wsdl:part name="bar" type="foo:BarType"/>
</wsdl:message>
I keep getting the error :
Validating foo.wsdl
Schema type not found: QName(http://foo, BarType)
Validate WSDL: has errors.If I paste the content of foo.xsd inline in the wsdl file, it works ok.
The wsdl file validates in XMLSpy; it can even successfully generate SOAP requests from it.
Am I wrong somewhere ?
Did anyone succeed in importing an external schema inside a wsdl file with JDev ?
thx.

Does anyone know if this is working in JDeveloper 10.1.3?
Another (relared) question: we use multiple wsdl files to define our web services (according to the Venetian Blind design). Since the project uses WebLogic as AS we used their mechanism to generate the webservice. The only thing is that generating a stub via WebLogic JAX-RPC fails due to namespace errors.
When I try to generate a stub based on the JDeveloper 10.1.3 wizards using the top-level wsdl (the one importing other wsdl's) I get an invalid wsdl message and the options in the wizard are disabled. Anyone know whether multiple wsdl's are supported in JDeveloper 10.1.3?
Ronald

Can someone please tell me a simple but effective method for burning a slideshow to DVD? Now that the connection between iPhoto and iDVD no longer exists, I can't figure out a way to get there with an acceptable quality result.

Can someone please tell me a simple but effective method for burning a slideshow to DVD? Now that the connection between iPhoto and iDVD no longer exists, I can't figure out a way to get there with an acceptable quality result.

Export the slideshow out of iPhoto as a QT movie file via the Export button in the lower toolbar. Select Size = Medium or Large.
Open iDVD, select a theme and drag the exported QT movie file into the open iDVD window being careful to avoid any drop zones.
Follow this workflow to help assure the best qualty video DVD:
Once you have the project as you want it save it as a disk image via the File ➙ Save as Disk Image menu option. This will separate the encoding process from the burn process.
To check the encoding mount the disk image, launch DVD Player and play it. If it plays OK with DVD Player the encoding is good.
Then burn to disk with Disk Utility or Toast at the slowest speed available (2x-4x) to assure the best burn quality. Always use top quality media: Verbatim, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.
If iDVD was not preinstalled on your Mac you'll have to obtain it by purchasing a copy of the iLife 09 disk from a 3rd party retailier like Amazon.com: ilife 09: Software or eBay.com. Why, because iDVD (and iWeb) was discontinued by Apple over a year ago.
Why iLife 09 instead of 11?
If you have to purchase an iLife disc in order to obtain the iDVD application remember that the iLife 11 disc only provides themes from iDVD 5-7. The Software Update no longer installs the earlier themes when starting from the iLIfe 11 disk nor do any of the iDVD 7 updaters available from the Apple Downloads website contain them.
Currently the only sure fire way to get all themes is to start with the iLife 09 disc:
This shows the iDVD contents in the iLife 09 disc via Pacifist:
You then can upgrade from iDVD 7.0.3 to iDVD 7.1.2 via the updaters at the Apple Downloads webpage.
OT

Query with Cost Center Hierarchy giving incorrect results

Hi All,
I have a universe built based on BEx query on Cost Center cubes. When enabling hierarchy in BEx Query and building Web intelligence Report based on the universe, I get incorrect results. The levels of the hierarchy is incorrect, many of the cost centers are missing etc. I checked the universe and confirmed that all levels of hierarchy are generated correctly. The Lov generated for these levels are correct and I see the complete hierarchy when using the BEx Variable in Universe for filtering.
I tried the same query with Hierarchy disabled with a different universe and it is providing correct results. Not sure what I'm missing here. Any inputs regarding this is appreciated.
Thanks & Regards,
Sree

Ingo, Thanks for your suggestion. Of course, I did update the Universe after any changes in the query. Tried different query setting related to hierarchy to make it work, but didn't many any difference and I get consistently incorrect results.
One thing what I wanted to confirm is, if there is any known bug in SP 2 Fix Pack 2.7 related to hierarchies. If not, it might be me doing some thing wrong and I will look into in more detail.
Thanks & Regards,
Sree

Incorrect result set with using isnull() function in IQ 16

Hi team,
We have IQ 16 on HP UX.
When we use isnull() function in where clause we get incorrect result set if we do not use column name in the result set.
In first select we get result with one row but in second one we get an empty result set.
select ID, dat_start, dat_end, dat_stop
from table_test
where ID=1105935925
and isnull(dat_stop,dat_start) <> dat_end
select ID
from table_test
where ID=1105935925
and isnull(dat_stop,dat_start) <> dat_end
It depends on number of row or volume of data in table, It is possible to use option Revert_To_V15_Optimizer to get the correct result.
Do you have any different idea how to solve it?
Thanks Milos.

We have tested two versions:
Sybase IQ/16.0.0.653/131122/P/sp03/ITANIUM/HP-UXi 11.31/64bit/2013-11-22 01:49:18
SAP IQ/16.0.0.807/140507/P/sp08/ITANIUM/HP-UXi 11.31/64bit/2014-05-07 21:11:45
Both versions have given same mistake.
We have not opened any support case for this issue because it is data depended issue. It is not easy to simulate it as an example.
Do you think we should open a support case for it?
Miloš

When I take a video with my new PowerShot ELPH 340 HS with the long axis verticle, the resulting vid

When I take a video with the long axis of my new PowerShot ELPH 340 HS verticle, the resulting video is rotated 90 degrees. Is there a way to adjust the camera or is there a piece of code that can rotate the video 90 deg. I would appreciate any suggestions.

Hi rrr317!
Thanks for posting.
Unlike still images, video will always record with the long side along the bottom and the short side vertical. To rotate a video, you will need to use video editing software.
Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

Currency conversion issue in SPM. We are getting incorrect results with SPM conversion function from one of the document currency to USD.

Currently we are using SPM 2.0 version and we have been facing currency conversion issues.
Please help me in following aspects.
1) Where actually currency conversion happens in SPM. Is it the global program which does the conversion or other way.
2) We have conversion issue for one of the currency where conversion function is giving incorrect results when converting from one of the document currency to USD. here The respective document currency is considering the 1:1 ratio with Dollar which is actually incorrect.
3) We have verified in both BI side(currency tables) and even ECC side.
Please help me in understanding this issue and let me know if you need more information on this.
Its an production issue and appreciated your immediate inputs.
Thanks
Kiran

Hi Arun,
The following information may be helpful to you.The SSA_HELPER_PROGRAM has options regarding currency settings.
EXCH_RATE_TYPE: This flag governs the exchange rate type which will be used for currency conversion in data management. For example if RSXAADMIN contains an entry EXCH_RATE_TYPE = „ZSPM‟ then the conversion type used for currency conversion is ZSPM. The default value for the exchange rate type is „M‟. More details can be found in the note 1278988.
CURRENCYCONVERSION: By default data management converts all the measures in transaction currency to reporting currency and copies over to the corresponding measure in reporting currency. If the measure in reporting currency is already available in source it might be desirable to disable the currency conversion. To disable the conversion you can make an entry CURRENCYCONVERSION = „ „ in the table RSXAADMIN. This can also be achieved by running the program SSA_HELPER_PROGRAM with the option DEACTIVATE_CURRENCYCONVERSION. The conversion can be reactivated by running the same program with option ACTIVATE_CURRENCYCONVERSION.
UNITCONVERSION: Similar to above. To deactivate unit conversion you can use the program with option and DEACTIVATE_UNITCONVERSION and to reactivate ACTIVATE_UNITCONVERSION. By default both the conversions are switched on
EXTERNAL_CURRENCIES: Normally most of the international currencies are stored with two decimal places however certain currencies do have 0 and 1 decimal place too. For example JPY has 0 decimal places. SAP internal format stores even these currencies with 2 decimal places and at the time of display it changes the value to right decimal places. In case a file from external source is loaded to SPM it might have the format with 0 decimal places in the file. To convert it to SAP standard format post processing needs to be done on this value. If that is the case you can set the flat EXTERNAL_CURRENCIES = „X‟ in the table which will enable the post processing for these values. This flag can also be set and reset using the helper program using the option TURNON_EXT_CURRENCY_FORMAT and TURNOFF_EXT_CURRENCY_FORMAT.
Kind Regards,
John Harris
Senior Support Engineer, SAP Active Global Support

Import WSDL with xsd:long incorrectly results in INT4

Similar Messages

Maybe you are looking for