Convert/Cast string data type from file to DT_GUID into table
Hi to all
is there anyone who help me please?!?
I'm not able to resolve the following problem.
I have a .csv file with a string field A and its values are GUID.
I must export this .csv file into SQL Server Table which have a uniqueidentifier (GUID) field B.
I must map string field A to GUID field B of table.
But I get an error like this: "Error at Data Flow Task [Derived Column [xxx]]: Error code 0x800401F3 occurred attempting to convert from data type DT_WSTR to data type DT_GUID.".
I read other posts like this in this forum and i also tried the solution suggested in those posts.
The proposed solution had suggested of insert in the expression field of "Derived Column" Transformation this expression (DT_GUID) ("{" + [YourGuid] + "}") in place of (DT_GUID) [YourGuid].
But i get always the same error.
is there anyone who help me please to resolve this issue?!?
The derived column expression should work if the yourGuid column contains a real guid.
Does the source looks something like: 25892e17-80f6-415f-9c65-7395632f0223
And are all rows filled with a correct value or are there also empty strings or null values?
Please mark the post as answered if it answers your question | My SSIS Blog:
http://microsoft-ssis.blogspot.com |
Twitter
Similar Messages
-
Arranging Random Data Pieces From SLX/Smart Catalogue Into Table Format
Hi,
We have a performance data grid that needs to appear on our quotation report. The data is organized currently into rows in a 2-table linked format and manually entered as plain txt by the user. We are now migrating towards designing a report in Crystal Reports to try to recreate this table layout but still needing to mine data for other purposes. Therefore, the data pieces need to be distinct and separate. Further, the data pieces required for the table can vary and can be organized in up to 9 different ways depending upon the given situation. Is there an effective way to aesthetically arrange random data pieces in a table format? The data pieces are coming from SalesLogix / SmartCatalog. Has any other user of Crystal Reports attempted to do this - i.e. create a data table on a Crystal report?
Sincerely,
Sarah Imig
International Sales Administrator/Database Administrator
HayssenSandiacreHi,
We have a performance data grid that needs to appear on our quotation report. The data is organized currently into rows in a 2-table linked format and manually entered as plain txt by the user. We are now migrating towards designing a report in Crystal Reports to try to recreate this table layout but still needing to mine data for other purposes. Therefore, the data pieces need to be distinct and separate. Further, the data pieces required for the table can vary and can be organized in up to 9 different ways depending upon the given situation. Is there an effective way to aesthetically arrange random data pieces in a table format? The data pieces are coming from SalesLogix / SmartCatalog. Has any other user of Crystal Reports attempted to do this - i.e. create a data table on a Crystal report?
Sincerely,
Sarah Imig
International Sales Administrator/Database Administrator
HayssenSandiacre -
How to fix "cannot convert between unicode and non-unicode string data types" :/
Environment: SQL Server 2008 R2
Introduction:Staging_table is a table where data is being stored from source file. Individual and ind_subject_scores are destination tables.
Purpose: To load the data from a source file .csv while SSIS define table fields with 50 varchar, I can still transfer the data to the entity table/ destination and keeping the table definition.
I'm getting validation error "Cannot convert between a unicode and a non-unicode string data types" for all the columns.
Please helpHi ,
NVARCHAR = DT_WSTR
VARCHAR = DT_STR
Try below links:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ed1caf36-7a62-44c8-9b67-127cb4a7b747/error-on-package-can-not-convert-from-unicode-to-non-unicode-string-type?forum=sqlintegrationservices
http://social.msdn.microsoft.com/Forums/en-US/eb0d1519-4be3-427d-bd30-ae4004ea9e8d/data-conversion-error-how-to-fix-this
http://technet.microsoft.com/en-us/library/aa337316(v=sql.105).aspx
http://social.technet.microsoft.com/wiki/contents/articles/19612.ssis-import-excel-to-table-cannot-convert-between-unicode-and-non-unicode-string-data-types.aspx
sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **. -
CAST Not working for me - Arithmetic overflow error converting int to data type numeric - error
GPM is DECIMAL(5,2)
PRICE is DECIMAL(11,4)
COST is DECIMAL(7,2)
Trying to update the Gross Profit Margin % field and I keep getting the "Arithmetic overflow error converting int to data type numeric" error.
UPDATE SMEMODETAIL SET SMD_GPM = (SMD_PRICE-SMD_COST) / SMD_PRICE * 100
FROM SMEMODETAIL WHERE SMD_PRICE<>0 AND SMD_QUANTITY<>0
Example record:
SMD_PRICE SMD_COST GPM%
1.8500 1.62 12.4324324324324300
I added cast and I still get the error.
How do I format to get this to work?
Thanks!Hi GBerthume,
The error is caused by some value such as 1000.01 of the expression (SMD_PRICE-SMD_COST) / SMD_PRICE * 100 exceeds the
precision of the column(DECIMAL(5,2)). The example data doesn't cause the overflow error for the value of the expression is 12.43 which is in the scope of DECIMAL(5,2).
USE TestDB
CREATE TABLE SMEMODETAIL
SMD_PRICE DECIMAL(11,4),
SMD_COST DECIMAL(7,2),
SMD_GPM DECIMAL(5,2)
INSERT INTO SMEMODETAIL(SMD_PRICE,SMD_COST) SELECT 1.8500,1.62
UPDATE SMEMODETAIL SET SMD_GPM = (SMD_PRICE-SMD_COST) / SMD_PRICE * 100
FROM SMEMODETAIL WHERE SMD_PRICE<>0-- AND SMD_QUANTITY<>0
SELECT * FROM SMEMODETAIL
DROP TABLE SMEMODETAIL
The solution of your case can be either scale the DECIMAL(5,2) or follow the suggestion in Scott_morris-ga's to check and fix your data.
If you have any question, feel free to let me know.
Eric Zhang
TechNet Community Support -
How to convert a dynamic data type to array of strings
I want to perform a serial communication between two
computers that I´ll call them A and B. The computer A (transmitter)
will send a signal (sinusoidal) to computer B (receiver). I´m using a
VISA Serial Communications Set (VISA Configure Serial Port.vi, VISA
Write.vi, VISA Read.vi and VISA Close.vi). VISA Write accepts
only string data type and VISA Read reads only string data type, but
the signal that I generated (on transmitter) is dynamic data and I need
to perform this conversion to run my program sucessfully. How can I
perform this conversion?!Hi Rafael,
You can configure the From DDT Express VI to convert your dynamic data to any number of different types. By default, the Express VI will convert to a 1D array of numerics...however, you can configure it (either when you first drop it, or by double-clicking it) to convert to a 2D array of numerics...additionally, you can configure it to convert based on channel data being in columns or rows. I have attached another screenshot that shows converting the dynamic data into a 2D numeric array.
I hope this helps.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman
Attachments:
FromDDT2D.jpg 164 KB -
Column "A" cannot convert between unicode and non-unicode string data types
I am following the SSIS overview video-
https://secure.cbtnuggets.com/it-training-videos/series/microsoft-sql-server-2008-business-development/6143?autostart=true
I have a flat file that i want to import the contents onto a SQL database.
I created a Dataflow task, source file and oledb destination.
I am getting the folliwung error -
"column "A" cannot convert between unicode and non-unicode string data types"
in the origin file the data type is coming as string[DT_STR] and in the destination object it is coming as "Unicode string [DT_WSTR]"
I used a data conversion object in between, dosent works very well
Please help what to doI see this often.
Right Click on FlatFileSource --> Show Advanced Editor --> 'Input and Output Properties' tab --> Expand 'Flat File Source Output' --> Expand 'Output Columns' --> Select your field and set the datatype to DT_WSTR.
Let me know if you still have issues.
Thank You,
Jay -
Cannot convert between unicode and non-unicode string data types.
I'm trying to copy the data from 21 tables in a SQL 2005 database to a MS Access database using SSIS. Before converting the SQL database from 2000 to 2005 we had this process set up as a DTS package that ran every month for years with no problem. The only way I can get it to work now is to delete all of the tables from the Access DB and have SSIS create new tables each time. But when I try to create an SSIS package using the SSIS Import and Export Wizard to copy the SQL 2005 data to the same tables that SSIS itself created in Access I get the "cannot convert between unicode and non-unicode string data types" error message. The first few columns I hit this problem on were created by SSIS as the Memo datatype in Access and when I changed them to Text in Access they started to work. The column I'm stuck on now is defined as Text in the SQL 2005 DB and in Access, but it still gives me the "cannot convert" error.
I was getting same error while tranfering data from SQL 2005 to Excel , but using following method i was able to tranfer data. Hopefully it may also help you.
1) Using Data Conversion transformation
data types you need to select is DT_WSTR (unicode in terms of SQL: 2005)
2) derived coloumn transformation
expression you need to use is :
(DT_WSTR, 20) (note : 20 can be replace by your character size)
Note:
Above teo method create replica of your esting coloumn (default name will be copy of <coloumn name>).
while mapping data do not map actual coloumn to the destination but select the coloumn that were created by any of above data transformer (replicated coloumn). -
Hello,
I am working on one project and there is need to extract Sharepoint list data and import them to SQL Server table. I have few lookup columns in the list.
Steps in my Data Flow :
Sharepoint List Source
Derived Column
its formula : SUBSTRING([BusinessUnit],FINDSTRING([BusinessUnit],"#",1)+1,LEN([BusinessUnit])-FINDSTRING([BusinessUnit],"#",1))
Data Conversion
OLE DB Destination
But I am getting the error of not converting between unicode and non-unicode string data types.
I am not sure what I am missing here.
In Data Conversion, what should be the Data Type for the Look up column?
Please suggest here.
Thank you,
Mittal.You have a data conversion transformation. Now, in the destination are you assigning the results of the derived column transformation or the data conversion transformation. To avoid this error you need use the data conversion output.
You can eliminate the need for the data conversion with the following in the derived column (creating a new column):
(DT_STR,100,1252)(SUBSTRING([BusinessUnit],FINDSTRING([BusinessUnit],"#",1)+1,LEN([BusinessUnit])-FINDSTRING([BusinessUnit],"#",1)))
The 100 is the length and 1252 is the code page (I almost always use 1252) for interpreting the string.
Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com -
How to Convert Data type from CLOB to LONG
Hi all
We changed one Long Data type column to CLOB
We need to revert back to Long Data type,
we changed the Data type from Long to CLOB
Can we change back to Long Again
we use oracle 10g Rel 2 on Hp-Unix
thanks all in Advance
Edited by: jrDba - atm on Apr 6, 2009 4:45 AMHi Satish
thanks a alot for the Info'
Can you please provide the
Notes MOS note 437021.1 for this purpose
thanks a lot -
Unicode and non-unicode string data types Issue with 2008 SSIS Package
Hi All,
I am converting a 2005 SSIS Package to 2008. I have a task which has SQL Server as the source and Oracle as the destination. I copy the data from a SQL server view with a field nvarchar(10) to a field of a oracle table varchar(10). The package executes fine
on my local when i use the data transformation task to convert to DT_STR. But when I deploy the dtsx file on the server and try to run from an SQL Job Agent it gives me the unicode and non-unicode string data types error for the field. I have checked the registry
settings and its the same in my local and the server. Tried both the data conversion task and Derived Column task but with no luck. Pls suggest me what changes are required in my package to run it from the SQL Agent Job.
Thanks.What is Unicode and non Unicode data formats
Unicode :
A Unicode character takes more bytes to store the data in the database. As we all know, many global industries wants to increase their business worldwide and grow at the same time, they would want to widen their business by providing
services to the customers worldwide by supporting different languages like Chinese, Japanese, Korean and Arabic. Many websites these days are supporting international languages to do their business and to attract more and more customers and that makes life
easier for both the parties.
To store the customer data into the database the database must support a mechanism to store the international characters, storing these characters is not easy, and many database vendors have to revised their strategies and come
up with new mechanisms to support or to store these international characters in the database. Some of the big vendors like Oracle, Microsoft, IBM and other database vendors started providing the international character support so that the data can be stored
and retrieved accordingly to avoid any hiccups while doing business with the international customers.
The difference in storing character data between Unicode and non-Unicode depends on whether non-Unicode data is stored by using double-byte character sets. All non-East Asian languages and the Thai language store non-Unicode characters
in single bytes. Therefore, storing these languages as Unicode uses two times the space that is used specifying a non-Unicode code page. On the other hand, the non-Unicode code pages of many other Asian languages specify character storage in double-byte character
sets (DBCS). Therefore, for these languages, there is almost no difference in storage between non-Unicode and Unicode.
Encoding Formats:
Some of the common encoding formats for Unicode are UCS-2, UTF-8, UTF-16, UTF-32 have been made available by database vendors to their customers. For SQL Server 7.0 and higher versions Microsoft uses the encoding format UCS-2 to store the UTF-8 data. Under
this mechanism, all Unicode characters are stored by using 2 bytes.
Unicode data can be encoded in many different ways. UCS-2 and UTF-8 are two common ways to store bit patterns that represent Unicode characters. Microsoft Windows NT, SQL Server, Java, COM, and the SQL Server ODBC driver and OLEDB
provider all internally represent Unicode data as UCS-2.
The options for using SQL Server 7.0 or SQL Server 2000 as a backend server for an application that sends and receives Unicode data that is encoded as UTF-8 include:
For example, if your business is using a website supporting ASP pages, then this is what happens:
If your application uses Active Server Pages (ASP) and you are using Internet Information Server (IIS) 5.0 and Microsoft Windows 2000, you can add "<% Session.Codepage=65001 %>" to your server-side ASP script.
This instructs IIS to convert all dynamically generated strings (example: Response.Write) from UCS-2 to UTF-8 automatically before sending them to the client.
If you do not want to enable sessions, you can alternatively use the server-side directive "<%@ CodePage=65001 %>".
Any UTF-8 data sent from the client to the server via GET or POST is also converted to UCS-2 automatically. The Session.Codepage property is the recommended method to handle UTF-8 data within a web application. This Codepage
setting is not available on IIS 4.0 and Windows NT 4.0.
Sorting and other operations :
The effect of Unicode data on performance is complicated by a variety of factors that include the following:
1. The difference between Unicode sorting rules and non-Unicode sorting rules
2. The difference between sorting double-byte and single-byte characters
3. Code page conversion between client and server
Performing operations like >, <, ORDER BY are resource intensive and will be difficult to get correct results if the codepage conversion between client and server is not available.
Sorting lots of Unicode data can be slower than non-Unicode data, because the data is stored in double bytes. On the other hand, sorting Asian characters in Unicode is faster than sorting Asian DBCS data in a specific code page,
because DBCS data is actually a mixture of single-byte and double-byte widths, while Unicode characters are fixed-width.
Non-Unicode :
Non Unicode is exactly opposite to Unicode. Using non Unicode it is easy to store languages like ‘English’ but not other Asian languages that need more bits to store correctly otherwise truncation will occur.
Now, let’s see some of the advantages of not storing the data in Unicode format:
1. It takes less space to store the data in the database hence we will save lot of hard disk space.
2. Moving of database files from one server to other takes less time.
3. Backup and restore of the database makes huge impact and it is good for DBA’s that it takes less time
Non-Unicode vs. Unicode Data Types: Comparison Chart
The primary difference between unicode and non-Unicode data types is the ability of Unicode to easily handle the storage of foreign language characters which also requires more storage space.
Non-Unicode
Unicode
(char, varchar, text)
(nchar, nvarchar, ntext)
Stores data in fixed or variable length
Same as non-Unicode
char: data is padded with blanks to fill the field size. For example, if a char(10) field contains 5 characters the system will pad it with 5 blanks
nchar: same as char
varchar: stores actual value and does not pad with blanks
nvarchar: same as varchar
requires 1 byte of storage
requires 2 bytes of storage
char and varchar: can store up to 8000 characters
nchar and nvarchar: can store up to 4000 characters
Best suited for US English: "One problem with data types that use 1 byte to encode each character is that the data type can only represent 256 different characters. This forces multiple
encoding specifications (or code pages) for different alphabets such as European alphabets, which are relatively small. It is also impossible to handle systems such as the Japanese Kanji or Korean Hangul alphabets that have thousands of characters."<sup>1</sup>
Best suited for systems that need to support at least one foreign language: "The Unicode specification defines a single encoding scheme for most characters widely used in businesses around the world.
All computers consistently translate the bit patterns in Unicode data into characters using the single Unicode specification. This ensures that the same bit pattern is always converted to the same character on all computers. Data can be freely transferred
from one database or computer to another without concern that the receiving system will translate the bit patterns into characters incorrectly.
https://irfansworld.wordpress.com/2011/01/25/what-is-unicode-and-non-unicode-data-formats/
Thanks Shiven:) If Answer is Helpful, Please Vote -
Hey guys
i need to create Data Type from and XSD,in the beginning i had an XML document which i converted to XSD using Altova ,then i imported this XSD in IR under External definition,now how should i go ahead with creating Data Type?
my sample XSD is something like this
<?xml version="1.0" encoding="UTF-8"?>
<!W3C Schema generated by XMLSpy v2007 sp2 (http://www.altova.com)>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="WorkOrderNumber">
<xs:simpleType>
<xs:restriction base="xs:short">
<xs:enumeration value="10942"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="VendorNumber">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:enumeration value="109845"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
Its not the complete XSD,just the first few lines.
thanx
AhmadHey Prabhu
my XSD looks like this
<?xml version="1.0" encoding="UTF-8"?>
<!W3C Schema generated by XMLSpy v2007 sp2 (http://www.altova.com)>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="WorkOrderNumber">
<xs:simpleType>
<xs:restriction base="xs:short">
<xs:enumeration value="10942"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="VendorNumber">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:enumeration value="109845"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="UnitPrice">
<xs:complexType>
<xs:sequence>
<xs:element ref="MonetaryAmount"/>
<xs:element ref="UnitOfMeasureCode"/>
<xs:element ref="CurrencyCode"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="UnitOfMeasureCode">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="EA"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="TotalLineItems">
<xs:simpleType>
<xs:restriction base="xs:byte">
<xs:enumeration value="6"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="TaxTypeCode">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="GoodsAndServicesTax"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="TaxReference">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="GST"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="TaxAmount">
<xs:complexType>
<xs:sequence>
<xs:element ref="MonetaryAmount"/>
<xs:element ref="CurrencyCode"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Tax">
<xs:complexType>
<xs:sequence>
<xs:element ref="TaxTypeCode"/>
<xs:element ref="TaxAmount"/>
<xs:element ref="TaxReference"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Requisition">
<xs:complexType>
<xs:sequence>
<xs:element ref="Number"/>
<xs:element ref="LineItemNumber"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Quantity">
<xs:simpleType>
<xs:restriction base="xs:decimal">
<xs:enumeration value="1.0"/>
<xs:enumeration value="2.0"/>
<xs:enumeration value="6.0"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="PrimaryCurrency">
<xs:complexType>
<xs:sequence>
<xs:element ref="CurrencyCode"/>
<xs:element ref="ExchangeRate"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Pricing">
<xs:complexType>
<xs:sequence>
<xs:element ref="UnitPrice"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="PaymentTerms">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="NT30"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Number">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="Q173849"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="MonetaryAmount">
<xs:simpleType>
<xs:restriction base="xs:decimal">
<xs:enumeration value="1.98"/>
<xs:enumeration value="12.48"/>
<xs:enumeration value="12.63"/>
<xs:enumeration value="16.75"/>
<xs:enumeration value="24.96"/>
<xs:enumeration value="240.0"/>
<xs:enumeration value="33.84"/>
<xs:enumeration value="43.83"/>
<xs:enumeration value="5.64"/>
<xs:enumeration value="74.81"/>
<xs:enumeration value="87.66"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="LineItemTotal">
<xs:complexType>
<xs:sequence>
<xs:element ref="MonetaryAmount"/>
<xs:element ref="CurrencyCode"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="LineItemNumber">
<xs:simpleType>
<xs:restriction base="xs:byte">
<xs:enumeration value="10"/>
<xs:enumeration value="20"/>
<xs:enumeration value="30"/>
<xs:enumeration value="40"/>
<xs:enumeration value="50"/>
<xs:enumeration value="60"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="LineItemMaterialNumber">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="108739"/>
<xs:enumeration value="192740-A"/>
<xs:enumeration value="380495"/>
<xs:enumeration value="43998"/>
<xs:enumeration value="54727S"/>
<xs:enumeration value="5746"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="LineItemInformation">
<xs:complexType>
<xs:sequence>
<xs:element ref="LineItemMaterialNumber"/>
<xs:element ref="LineItemDescription"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="LineItemDescription">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="ABSRBT PAD 17 IN X 19 IN X 3/8 IN UNIV P"/>
<xs:enumeration value="BSHG HEX 1 IN X 1/2 IN THD FS A105N"/>
<xs:enumeration value="GGE 4 IN 1M / 7000 DL SCALE 1/2 IN LM WI"/>
<xs:enumeration value="PEN REC RD MED GRAPHIC 39-202"/>
<xs:enumeration value="PL ORF 3 IN .5 IN ORF SER 500 316 SS"/>
<xs:enumeration value="WPR F-200 FLC NOV LABEL 20"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Invoices">
<xs:complexType>
<xs:sequence>
<xs:element ref="Invoice"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="InvoiceTypeCode">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="ProductOrService"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="InvoiceTotal">
<xs:complexType>
<xs:sequence>
<xs:element ref="MonetaryAmount"/>
<xs:element ref="CurrencyCode"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="InvoiceSummary">
<xs:complexType>
<xs:sequence>
<xs:element ref="TotalLineItems"/>
<xs:element ref="InvoiceTotal"/>
<xs:element ref="Tax"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="InvoiceQuantity">
<xs:complexType>
<xs:sequence>
<xs:element ref="Quantity"/>
<xs:element ref="UnitOfMeasureCode"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="InvoiceProperties">
<xs:complexType>
<xs:sequence>
<xs:element ref="InvoiceNumber"/>
<xs:element ref="InvoiceDate"/>
<xs:element ref="VendorNumber"/>
<xs:element ref="InvoiceTypeCode"/>
<xs:element ref="PrimaryCurrency"/>
<xs:element ref="PaymentTerms"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="InvoiceNumber">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:enumeration value="98815236"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="InvoiceLineItem">
<xs:complexType>
<xs:sequence>
<xs:element ref="WorkOrderNumber"/>
<xs:element ref="LineItemNumber"/>
<xs:element ref="InvoiceQuantity"/>
<xs:element ref="LineItemInformation"/>
<xs:element ref="Pricing"/>
<xs:element ref="LineItemTotal"/>
<xs:element ref="Requisition"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="InvoiceDetails">
<xs:complexType>
<xs:sequence>
<xs:element ref="InvoiceLineItem" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="InvoiceDate">
<xs:simpleType>
<xs:restriction base="xs:date">
<xs:enumeration value="2007-01-25"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Invoice">
<xs:complexType>
<xs:sequence>
<xs:element ref="InvoiceProperties"/>
<xs:element ref="InvoiceDetails"/>
<xs:element ref="InvoiceSummary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ExchangeRate">
<xs:complexType/>
</xs:element>
<xs:element name="CurrencyCode">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="CAD"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:schema>
can you please tell me how to nest the structures,i m fairly new to XSD and stuffs
thanx
ahmad -
Hi,
I want to find data type from its value.
Ex- If value = 1234 then its data type is numeric.
If value = ABCD then its data type is char.
So is there any FM which can tell the data type from its value or any way to do it.
Moderator Message: Offering points is against forum RoE.
Regards,
Ashish Gupta
Message was edited by: Suhas SahaHai.
check this.
the five non-numeric types (text field (C), numeric text field (N), date field (D), time field (T), and hexadecimal field (X)), there are three numeric types, used in ABAP to display and calculate numbers. Data type N is not a numeric type. Type N objects can only contain numeric characters (0...9), but are not represented internally as numbers. Typical type N fields are account numbers and zip codes.
integers - type I
The value range of type I numbers is -2*31 to 2*31-1 and includes only whole numbers. Non-integer results of arithmetic operations (e.g. fractions) are rounded, not truncated.
You can use type I data for counters, numbers of items, indexes, time periods, and so on.
Packed numbers - type P
Type P data allows digits after the decimal point. The number of decimal places is generic, and is determined in the program. The value range of type P data depends on its size and the number of digits after the decimal point. The valid size can be any value from 1 to 16 bytes. Two decimal digits are packed into one byte, while the last byte contains one digit and the sign. Up to 14 digits are allowed after the decimal point. The initial value is zero. When working with type P data, it is a good idea to set the program attribute Fixed point arithmetic.Otherwise, type P numbers are treated as integers.
You can use type P data for such values as distances, weights, amounts of money, and so on.
Floating point numbers - type F
The value range of type F numbers is 1x10*-307 to 1x10*308 for positive and negative numbers, including 0 (zero). The accuracy range is approximately 15 decimals, depending on the floating point arithmetic of the hardware platform. Since type F data is internally converted to a binary system, rounding errors can occur. Although the ABAP processor tries to minimize these effects, you should not use type F data if high accuracy is required. Instead, use type P data.
You use type F fields when you need to cope with very large value ranges and rounding errors are not critical.
Using I and F fields for calculations is quicker than using P fields. Arithmetic operations using I and F fields are very similar to the actual machine code operations, while P fields require more support from the software. Nevertheless, you have to use type P data to meet accuracy or value range requirements.
C ---> character
D ---> date
P ---> packed
T ---> time
X ---> hexadecimal
I ---> integer.
N ---> Muneric.
Possible ABAP/4 data types:
C: Character.
D: Date, format YYYYMMDD.
F: Floating-point number in DOUBLE PRECISION (8 bytes).
I: Integer.
N: Numerical character string of arbitrary length.
P: Amount or counter field (packed; implementation depends on hardware platform).
S: Time stamp YYYYMMDDHHMMSS.
T: Time of day HHMMSS.
V: Character string of variable length, length is given in the first two bytes.
X: Hexadecimal (binary) storage.
regards.
sowjanya.b. -
Arithmetic overflow error converting expression to data type int
Hi
iam creating on sp for the database total size , used mb and free size . percentage free .
in this purpose i was creating on sps, with in the sp iam was writing one select statement . it statement is
SELECT [Drivename] ,[DataSizedUsedMB],[DriveFreeSizeMB],DriveTotalSizeMB,
CAST( (DriveFreeSizeMB/DriveTotalSizeMB)* 100 AS NUMERIC(5,2))
As
[PercentFree] ,[DateRecorded] FROM
SELECT SUBSTRING([physical_name],1,1) AS Drivename,
CAST(((SUM(COALESCE(size,0)))*8)/1024 AS NUMERIC(20,2)) AS DriveTotalSizeMB,
CAST(((SUM( COALESCE( FILEPROPERTY( [name],'SpaceUsed'),0)))*8)/1024 AS NUMERIC(20,2)) AS DataSizedUsedMB,
CAST(((SUM(COALESCE(size,0))-SUM(COALESCE(fileproperty([name],'spaceused'),0)))*8/1024)AS NUMERIC(20,2)) AS DriveFreeSizeMB
,SYSDATETIME() AS [DateRecorded]
FROM sys.master_files
GROUP BY SUBSTRING([physical_name],1,1)) AS Data
it was executive one server with out error but the same select statement is writing antoher server iam geeting belo error.
"@ErrorDesc: Line 24 - Line 13- Arithmetic overflow error converting expression to data type int."
how to slove this issue..
please help me...Change 8 to 8E0, to make it a float literal. The data type of
SUM(COALESCE(size,0)))*8)
is int, since all components are int, and it can easily overflow the size for an int. If you use 8E0, you get a float, and the entire expression will be float.
Erland Sommarskog, SQL Server MVP, [email protected] -
Arithmetic Overflow error converting float to data type numeric
Hi,
Am facing strange issue,I have function which returns money datatype and assigning the return money value to float datatype in table.
Error msg:
Msg 8115, Level 16, State 6, Procedure GBCalcCatalogPriceNewV2, Line 204
Arithmetic overflow error converting float to data type numeric.
The statement has been terminated.
Strange thing is the same stored procedure is working fine in production environment,but in the deveopment i see this error.Am scared if the same happens in the production environment.Please advice and advance
thanks
Regards
RAjStrange thing is the same stored procedure is working fine in production environment,
How could that be strange? This is an error that occurs depending on the data. Accidents that are waiting to happen will happen sooner or later.
Then again, a development database may be more prone to such errors, because data that entered are completely out of whack with real life data. Still it is a warning sign. If you have some place where you convert data from float to numeric, you must consider
the risk that the float value is outside the range for the numeric data type. How do you prevent that from happening? Maybe a CHECK constraint on the column? Of if the data origins from a money column, use a numeric data type with sufficient precision.
Erland Sommarskog, SQL Server MVP, [email protected] -
Minus date in string data type
Hi all,
i having one table in database that used to store the borrow_date and return_date, the date is in this format 06/12/2008, when i retrieve the date from the database, and i pass it into String data type, for example as follows:
private String borrow_date = 05/12/2008;
private String return_date = 10/12/2008;
if for example student A return the book on 15/12/2008, which is after the return_date in database, then i want to minus is 15/12/2008 with 10/12/2008, so that i can get the int value of 5 days. Because i want to use this integer 5 for late penalty. One day charge for 20 cent.
e.g: String borrow_date - String return_date = int total_days;
Now my problem is this, i dont know how to use string data type minus with string data type to get the integer type.
I had tried for many methods already, still cannot get it, i can get the total days in int data type if the date is in Date or Calendar data type. The problem now is the date is in String data type. Any idea from you? :)
Regards,
poh_ccpoh_cc wrote:
because in my case, i have to use string data type :)Thinking about this again, it really is stupid. You say you are even storing the dates in the database as Strings and not Dates. It can only lead to a world of hurt.
Maybe you are looking for
-
Can i copy my settings from one mac to another?
Hi Since I had a problem with my Mac's drive that suddenly failed (I am able to read ONLY), I replaced the internal HD with my emergency HD that I had backedup a few months before. I would like to know if there's a way to copy my settings from one ma
-
Full screen preview drops frames
Hi all, A continuation of the thread I opened here (with hardware specs for information): http://forums.adobe.com/thread/657008?tstart=0 Whilst I resolved the tearing issue secribed in the previous thread I still can't get smooth playback on the thir
-
Hi Guys I've filmed a wedding using a Sony Z1 in 16:9 but I have some footage in 4:3 captured by a old little handheld Panasonic GS10. I'd like to use some of that footage but I need to make that 16:3. I saw a thread a couple of days ago that had a g
-
XML parser error in OC4J_Portal/portalHelp - XmlPullParserException
Hi all! I've just discovered an error in \opmn\logs\OC4J~OC4J_Portal~default_island~1 referencing org.xmlpull.v1.XmlPullParserException. The error comes in un-even time intervals. Were running OAS 10.1.2.0.2 on WIN2003 server, with the Portal&Wireles
-
Split front panel into 2 parts
Hi I need to spli the front page into 2 parts.On top I need to put a question with picture which are fixed and on bottom a page with scroll to go up and down I would like to put all my indicators and controls in that part but as I said the top part s