Issue while processing xml file

Hi guys -
I am getting error 7000 : null : com.sunopsis.sql.l: Oracle Data Integrator Timeout : connection with URL jdbc:snps:xml ...... while processing data from an xml file which is located in linux directory. I have changed the timout parameter from 30 to 500 in my client. Also modified the userpref.xml as suggested by many in forums but no use. When I checked the failed stage it shows that it gets timed out in 30 seconds. The same when i processed from my local window machine worked fine.
Could you please help me overcome this trouble.? Please help.
Thanks

Hi
You can edit userpref.xml file reside inside bin directory of ODI_HOME (oracledi folder). You need to edit the field name "value" (eg: [30] to [60]). Then restart the application and ODI Agent.
<Object class="com.sunopsis.dwg.dbobj.SnpUserParam">
<Field name="Key" type="java.lang.String"><![CDATA[DEFAULT_REPOSITORY_CONNECTION_TIMEOUT]]></Field>
*<Field name="Value" type="java.lang.String"><![CDATA[30]]></Field>*
<Field name="Label" type="java.lang.String"><![CDATA[Oracle Data Integrator Timeout]]></Field>
<Field name="Type" type="java.lang.String"><![CDATA[com.sunopsis.graphical.userparam.SnpsTextFieldEditor]]></Field>
<Field name="Help" type="java.lang.String"><![CDATA[Timeout used by Oracle Data Integrator for the database connections.]]></Field>
<Field name="Visible" type="boolean"><![CDATA[true]]></Field>
<Field name="Updatable" type="boolean"><![CDATA[true]]></Field>
<Field name="Position" type="int"><![CDATA[4]]></Field>
</Object>
or increase your machine virtual memory
Regards,
Phanikanth

Similar Messages

Facing issue while reading XML file 'LPX-00217: '

Hi Gurus,
I am facing one issue while reading the xml file in the one my 11g database instance. The same file if I ran in another instance then it is working fine for me.
I presume it will be related to NLS character. Please help me in finding out character set.
And the issue where I am getting instance character set is 'US7ASCII', and I am not getting this issue in another instance where the character set is 'UTF8'.
And here is the issue I am getting when I was trying to load that file.
Error Occurred :=ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML
processing
LPX-00217: invalid character 150 (U+0096)
Error at line 1
Pls help me in debugging this issue.
Regards,
Nagendra
Edited by: 838961 on Jul 12, 2011 9:32 PM

Hi,
Pls help me in debugging this issue.There's not much to debug actually.
The US7ASCII charset stores 7-bit characters, but you're trying to insert a value out of range (150). So that's expected behaviour.
There were some "tricks" to allow that on some versions, using NLS settings, but it's definitely not the clean way to do it so I won't develop.
The best thing you have to do is to migrate to character set AL32UTF8, which is fully compliant with XML.

Issue while Processing the Huge File in BPEL

Hi,
We are facing an Issue while Processing a Hige file in BPEL Process (More than 1MB File). When i test the files with more than 1500 transactions (More than 1MB file) then the BPEL Process is automatically goes to OFF Mode or it goes to Perform Manually Recovery Queue.
Even we are facing this issue in Production also so we are using UNIX Script to Split the file before place the file in BPEL Input directory.Any Pointers to resolve this issue will be helpful.
Thanks,
Saravana

Hi,
Please find the answers.
1. Currently we are using SOA 10.1.2 Version and JDev10g
2. we are using File Adapeter
3. yes. We used debatching.
4. Yes. I am able to recover from Manual Recovery Queue
5. Please find the error message
<2009-05-21 04:32:38,461> <DEBUG> <ESIBT.collaxa.cube.engine.dispatch> <Dispatcher::adjustThreadPool> Allocating 1 thread(s); pending threads: 1, active threads: 0, total: 83
<2009-05-21 04:32:44,077> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> File : /harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B is ready to be processed.
<2009-05-21 04:32:44,077> <INFO> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Processing file : /harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B
<2009-05-21 04:32:44,077> <DEBUG> <ESIBT.collaxa.cube.activation> <AdapterFramework::Inbound> onBatchBegin: Batch 'bpel://localhost/ESIBT/BPELProcess_810~1.0//Input5162009.B2B_1242894594000' (/harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B) starting...
<2009-05-21 04:32:44,077> <DEBUG> <ESIBT.collaxa.cube.translation> <TranslatorFactory::log> Inside TranslatorFactory
<2009-05-21 04:32:44,078> <DEBUG> <ESIBT.collaxa.cube.translation> <TranslatorFactory::log> using version attribute = NXSD
<2009-05-21 04:32:44,078> <DEBUG> <ESIBT.collaxa.cube.translation> <TranslatorFactory::log> loading xlator class...oracle.tip.pc.services.translation.xlators.nxsd.NXSDTranslatorImpl
<2009-05-21 04:32:44,081> <DEBUG> <ESIBT.collaxa.cube.translation> <TranslatorFactory::log> class loaded
<2009-05-21 04:32:44,081> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Created translator : oracle.tip.pc.services.translation.xlators.nxsd.NXSDTranslatorImpl@46908ae8
<2009-05-21 04:32:44,098> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Setting up Control dir for debatching error recovery
<2009-05-21 04:32:44,121> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Control dir for debatching error recovery : /opt01/app/ESIBT/oracle/esibt10gR2iAS/BPEL10gR2/iAS/j2ee/home/fileftp/controlFiles/localhost_ESIBT_BPELProcess_810~1.0_/inbound
<2009-05-21 04:32:44,121> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Invoking inbound translation for : Input5162009.B2B
<2009-05-21 04:32:44,121> <DEBUG> <ESIBT.collaxa.cube.translation> <NXSDTranslatorImpl::log> Starting translateFromNative
<2009-05-21 04:32:44,139> <DEBUG> <ESIBT.collaxa.cube.translation> <NXSDTranslatorImpl::log> Done with translateFromNative
<2009-05-21 04:32:44,139> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Completed inbound translation for : Input5162009.B2B
<2009-05-21 04:32:44,139> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> isTextFile : true
<2009-05-21 04:32:44,139> <INFO> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Translated inbound batch index 1 of file {Input5162009.B2B} with corrupted message count = 1
<2009-05-21 04:32:44,139> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Error Reader created using charset :ASCII
<2009-05-21 04:32:44,139> <INFO> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Sending message to Adapter Framework for rejection to user-configured rejection handlers : {
fileName=/harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B, startLine=1, startColumn=1, endLine=-1, endCol=-1, Exception=ORABPEL-11167
Error while reading native data.
[Line=1, Col=70] Expected "\t" at the specified position in the native data, while trying to read the data for "element with name HDR_STORE_NUM", using "style" as "terminated" and "terminatedBy" as "\t", but not found.
Ensure that "\t", exists at the specified position in the native data.
<2009-05-21 04:32:44,139> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Setting batchId in NativeRecord to bpel://localhost/ESIBT/BPELProcess_810~1.0//Input5162009.B2B_1242894594000
<2009-05-21 04:32:44,139> <WARN> <ESIBT.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(Object)] - onReject: The resource adapter 'File Adapter' requested handling of a malformed inbound message. However, the following bpel.xml activation property has not been defined: 'rejectedMessageHandlers'. Please define it and redeploy the business process. Will use the default Rejection Directory file:///opt01/app/ESIBT/oracle/esibt10gR2iAS/BPEL10gR2/iAS/integration/orabpel/domains/ESIBT/archive/jca/BPELProcess_810/rejectedMessages for now.
<2009-05-21 04:32:44,140> <WARN> <ESIBT.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(Object)] - onReject: Sending invalid inbound message to Exception Handler:
<2009-05-21 04:32:44,140> <INFO> <ESIBT.collaxa.cube.activation> <AdapterFramework::Inbound> Handing rejected message to DEFAULT rejection handler: file:///opt01/app/ESIBT/oracle/esibt10gR2iAS/BPEL10gR2/iAS/integration/orabpel/domains/ESIBT/archive/jca/BPELProcess_810/rejectedMessages since none of the configured rejection handlers [] succeeded.
<2009-05-21 04:32:44,140> <DEBUG> <ESIBT.collaxa.cube.activation> <AdapterFramework::Inbound> Finished persisting rejected message to file system under the name: /opt01/app/ESIBT/oracle/esibt10gR2iAS/BPEL10gR2/iAS/integration/orabpel/domains/ESIBT/archive/jca/BPELProcess_810/rejectedMessages/INVALID_MSG_BPELProcess_810_Read_20090521_043244_0140.dat
<2009-05-21 04:32:44,141> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Setting last error record to : -1
<2009-05-21 04:32:44,141> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Translator has failed to translate any message from batch number: 1
<2009-05-21 04:32:44,141> <INFO> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Message not published as translation failed: {
File=/harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B, batchIndex=1, PublishSize=1
<2009-05-21 04:32:44,141> <ERROR> <ESIBT.collaxa.cube.activation> <AdapterFramework::Inbound> onBatchFailure: Batch 'bpel://localhost/ESIBT/BPELProcess_810~1.0//Input5162009.B2B_1242894594000' (/harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B) has failed due to: ORABPEL-11167
Error while reading native data.
[Line=1, Col=70] Expected "\t" at the specified position in the native data, while trying to read the data for "element with name HDR_STORE_NUM", using "style" as "terminated" and "terminatedBy" as "\t", but not found.
Ensure that "\t", exists at the specified position in the native data.
<2009-05-21 04:32:44,141> <INFO> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Deleting file : /harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B after processing.
<2009-05-21 04:32:44,141> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Deleting file : Input5162009.B2B
<2009-05-21 04:32:44,141> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Deleted file : true
<2009-05-21 04:32:44,141> <DEBUG> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Removing file /harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B from files to be processed Map.
<2009-05-21 04:32:44,141> <INFO> <ESIBT.collaxa.cube.activation> <File Adapter::Inbound> Done processing File : /harbinger/prod/xlate/Outbound_Input_LDS_810/Input5162009.B2B
<2009-05-21 04:33:09,698> <DEBUG> <ESIBT.collaxa.cube.engine.data> <ConnectionFactory::getConnection> GOT CONNECTION 4 Autocommit = false
For this error message this shows due to some /t its not picking up the file. but even i am facing the same issue for all the files where load is huge.
Thanks,
Saravana

Problem while reading XML file from Aplication server(Al11)

Hi Experts
I am facing a problem while reading XML file from Aplication server using open data set.
OPEN DATASET v_dsn IN BINARY MODE FOR INPUT.
IF sy-subrc <> 0.
EXIT.
ENDIF.
READ DATASET v_dsn INTO v_rec.
WHILE sy-subrc <> 0.
ENDWHILE.
CLOSE DATASET v_dsn.
The XML file contains the details from an IDOC number , the expected output is XML file giving all the segments details in a single page and send the user in lotus note as an attachment, But in the present output after opening the attachment i am getting a single XML file which contains most of the segments ,but in the bottom part it is giving the below error .
- <E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803<The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'file:///C:/TEMP/notesD52F4D/SHPORD_0080005842.xml'.
/SPAN></NTEND>
<NTENZ>000000</NTENZ>
for all the xml its giving the error in bottom part , but once we open the source code and if we saved in system without changing anything the file giving the xml file without any error in that .
could any one can help to solve this issue .

Hi Oliver
Thanx for your reply.
see the latest output
- <E1EDT13 SEGMENT="1">
<QUALF>003</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
- <E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803<The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'file:///C:/TEMP/notesD52F4D/~1922011.xml'.
/SPAN></NTEND>
<NTENZ>000000</NTENZ>
E1EDT13 with QUALF>003 and <E1EDT13 SEGMENT="1">
with <QUALF>001 having almost same segment data . but E1EDT13 with QUALF>003 is populating all segment data
properly ,but E1EDT13 with QUALF>001 is giving in between.

Error while uploading .xml file for Customer/Vendor List for Italy

Hi All,
We are facing problem while uploading the .xml file in DMEE transaction for the new Customer/Vendor List for Italy.
We have followed the entire process given in the OSS Note(1090857).
We have SAP 4.6c and followed the below steps:
1. Created ID-FI-IT Development class
2. Added domains
3. Added Data elements
4. Tried to upload the given .xml file and got any error saying ".xml file could not be interpreted".
Also there is a .SAR file mentioned to upload if we receive any errors while uploading .xml file.
Tried uploading the .SAR file also. STill we are recieving the same Error.
Can any one of you help us out.
Thanks in Advance.
Ramesh

Ok, we upload .SAR file in this way:
1. unpack .SAR file with SAPCAR.EXE program. Yuo obtain 2 files
R492445.P9C and K492445.P9C
2. put K492445.P9C in directory \SAPMNT\TRANS\COFILES and put R492445.P9C in directory \SAPMNT\TRANS\DATA of your system (DEV, TST or PRD)
3. Use Tx STMS. If You want create DMEE tree in DEV system, go to DEV import queue. Choose menu Extras | Other requests | Add. Insert P9CK492445 in Transp. request field.
4. Import the request. This creates the DMEE tree. You don't need ti upload XML file after. You can see the DMEE tree created with Tx DMEE and inserting
Tree type UMS1
Format tree IT_CUST_VEN_LIST
5. after continue follow the note
I hope this help you
Roberto

Product Instance Registration Error: "System Failure: Error while retrieving xml file from database"

Hi S9 installation Gurus,
Please try to resolve this long awaited issue with Planning installation as this is purely configuration related issue.
Detail of Problem:-
After Susessful configuration of
1) Foundation Services (Hyperion Shared Services)
2) Essbase administration services
3) Essbase Server
4) Hyperion reporting and analysis
5) Planning -----> Product options, Register with shared services, configure database, deploy to application server (Appache)
Error Point: when i tick ckeck box in front of Product instance registration
click next
create instance
click next
instance name-Plan1
Web tier host name: my machine name (neeraj-pc, as i installed locally all component of hyperion)
server port: 8300 (system suggesting)
tick on active instance
click next
Error Pop Up "System Failure: Error while retrieving xml file from database"
Details of PlanningSystemDB (file :- \Hyperion\common\config\PlanningSystemDB.properties)
SYSTEM_DB_DRIVER=hyperion.jdbc.sqlserver.SQLServerDriver
SYSTEM_DB_URL=jdbc:hyperion:sqlserver://neeraj-PC:1433
SYSTEM_DB_USER=puser
SYSTEM_DB_PASSWORD=GGAKFJ
SYSTEM_DB_CATALOG=p1db
SYSTEM_DB_TYPE=SQL
INSTANCE=
Note: puser (SQL Authenticated user)
Thanks
Kumar
Edited by: user10385300 on Dec 4, 2008 5:44 AM

This has been resolved at :- Product Instance Registration Error Message: "System Failure: Error while retrieving xml file from database"
Cheers
John
http://john-goodwin.blogspot.com/

System Failure:-Error while retreiving xml file from database

I install Planning 9.3.1 at Windows2003 server SP1 and MS SQL 2000 SP3A. In Hyperion Planning Instance Registration I take "System Failure:-Error while retreiving xml file from database" error in Configuration .
Please help
Thanks

I also have the same error. Win2000 Server and MS SQL 2005.
Maybe someone made request for official information from Oracle about this issue?
I'd like to change MS SQL to Oracle 10g, I hope this can helps (if reason in RDBMS). But if reason in logic of scripts... I dont't know...

Error while importing .xml files in informatica

Dear Rajendra, Please use this.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<my:MainFields xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.microsoft.com/office/infopath/2003/myXSD/2010-10-14T12:46:24 myschema.xsd " xmlns:my="http://schemas.microsoft.com/office/infopath/2003/myXSD/2010-10-14T12:46:24"> i used same like this my side its working. Please let me know. Thanks & RegardsKasireddy+966545281845

Hi All, Please help out getting below error while reading .xml file in informaitca 9.5.0 error:: FATAL: Error at (file D:/userdata/local/Desktop/documents/2015_07_22_NE_5003.xml, line 2, char 52 ): An exception occurred! Type:RuntimeException, Message:Could not open DTD file 'D:/userdata/ongole/Desktop/documents/InventoryInfo.xml'. Let me know. how to overcome this issue. Regards,Rajendra

ORA-22288:file or LOB operation FILEOPEN failed while loading XML file.

Hello all,
I am getting the following error messages while loading XML file to Oracle 9i table.
declare
ERROR at line 1:
ORA-22288: file or LOB operation FILEOPEN failed
No such file or directory
ORA-06512: at "SYS.DBMS_LOB", line 504
ORA-06512: at line 10
The script I am using is all follows:-
1. Created a file ldxmldata.sh on unix server directory
dd conv=ucase if=$1|sed 's/<?XML/<?xml/'|sed 's/VERSION/version/'|sed 's
/RECORD/ROW/'|sed 's/DATE/TRANSDATE/'|sed 's/&/-/'|sed 's/\/DATE>// TRANSDATE>/'>$1.UCASE
sqlplus sales/sales@rac @upld.sql $1.UCASE
2. Created SQL file upld.sql on unix server
set serveroutput on
exec DBMS_JAVA.SET_OUTPUT(1000000);
@ldxml.sql bsl.xml.UCASE
commit;
exit
3. Created sql file ldxml.sql on unix server
declare
insCtx DBMS_XMLSave.ctxType;
rows number;
file bfile := bfilename('XML_DIR','&1');
charContent CLOB := ' ';
targetFile bfile;
warning number;
begin
targetFile := file;
DBMS_LOB.fileopen(targetFile, DBMS_LOB.file_readonly);
DBMS_LOB.loadfromFile(charContent,targetFile,DBMS_LOB.getLength(tar
getFile),1,1);
insCtx := DBMS_XMLSave.newContext('sales.s_price');
rows := DBMS_XMLSave.insertXML(insCtx,charContent);
DBMS_XMLSave.closeContext(insCtx);
DBMS_LOB.fileclose(targetFile);
end;
4. As Sys,
Created a directory XML_DIR and assigned it the path of Unix server directory
where the script files reside.
Granted read priviledge on XML_DIR to user sales.
I am getting the above error messages. Kindly help with some possible solution.
Arun Patodia
Bokaro Steel City

Hi guys,
Sybrand, aplogoies, the second line of the error stack was on one line in the first post, full error stack below:
ORA-22288: file or LOB operation FILEOPEN failed
The program issued a command but the command length is incorrect.
ORA-06512: at "SYS.DBMS_LOB", line 716
ORA-06512: at "JLMS.LOAD_DATA_UTIL", line 417
ORA-06512: at line 2I have looked at that error code as you mentioned, but the second line here doesn't really help much.
Hoek, i took your advice and tried to replace FILEOPEN with OPEn but got the same error.
Just to clarify as well, I am not using UNC or relative file paths as I know that these can cause problems.
Rgds
Dan

PL/SQL procedure to process XML file

I am just starting to work on xml, and we are using PL/SQL stored procedures to process xml file. I did find the sample code in the package (family.sql). This sample print out all element names and attributes. My questions are :
(1) I tried to modify the code to print out the element values (or Node values). Here is the code:
-- get all elements and values
nl := xmlparser.getElementsByTagName(doc, '*');
len := xmlparser.getLength(nl);
-- loop through elements
for i in 0..len-1 loop
n := xmlparser.item(nl, i);
dbms_output.put_line('NodeName: ' | | xmlparser.getNodeName(n) | | ' ');
dbms_output.put_line('NodeValue: ' | | xmlparser.getNodeValue(n) | | ' ');
end loop;
However, it did not print out the values, although it did print out the name. what's wrong with it? how can I get the value?
(2) I have the following xml file:
<?xml version="1.0"?>
<profile>
<id>1</id>
<name>Company</name>
<des>master profile</desc>
<subprofile>
<subid>1</subid>
<subname>group1</subname>
<subdesc>group profile</subdesc>
</subprofile>
</profile>
now, I'd like to print out all the children of the <subprofile> node, that is <subid>, <subname> and <subdesc>. Here is my code:
-- get subprofile nodelist
qnlist := xmlparser.getElementsByTagName(doc, 'subprofile');
-- get length of the nodelist
len := xmlparser.getLength(qnlist);
-- loop through elements
for i in 0..len-1 loop
qnode := xmlparser.item(qnlist, i);
qnnode := xmlparser.getFirstChild(qnode);
qnchild := xmlparser.getFirstChild(qnnode);
dbms_output.put_line(xmlparser.getNodeName(qnnode));
dbms_output.put_line(xmlparser.getNodeValue(qnchild));
LOOP
if (xmlparser.isNULL(xmlparser.getNextSibling(qnnode))) then exit;
END IF;
qnnode := xmlparser.getNextSibling(qnnode);
qnchild := xmlparser.getFirstChild(qnnode);
dbms_output.put_line(xmlparser.getNodeName(qnnode));
dbms_output.put_line(xmlparser.getNodeValue(qnchild));
END LOOP;
end loop;
when I execute the procedure, I get the following output:
#text
I am not sure what's wrong with it. Basically, I didn't know the procedure to traverse the tree since here it's a little different from OO programming. Could someone give a sample code which demonstrate the procedure which can get a specific element's name and values? (for my exapmle, the name and value of the <subname>, or <subid>, <subdesc>).
Also, is there a way to insert a part of xml file into a DB table? in my case, insert the subprofile into a table. I know the xmlgen package has a procedure to insert a xml file into a table, but not a part of xml. And can I insert a xml file into several tables instead of one table, using xmlgen package?
looking forward to hearing from you. any suggestion and sample code would be helpful. thank you very much.
null

I sloved my first question: to get the Nodevalue, I need to use getFirstChild(n);
But, I still didn't figure out the second
problem. Actually, It works when I modified my xml file as following:
<?xml version="1.0"?>
<profile>
<id>1</id>
<name>Company</name>
<des>master profile</desc>
<subprofile><subid>1</subid><subname>group1</subname><subdesc>groupprofile</subdesc></subprofile>
</profile>
All the <subprofile>....</subprofile> must be in one line without any return. This is unbelievable! It suppose that xml does not matter new lines. I tested my code, it seems space is fine, but new line. Something must be wrong in my code.
please give any suggestion. Thanks,
Yudong
null

Error while importing .xml file in Datatype

Hi SDN,
I am getting this error while importing .xml file in Datatype.
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
Actually I have created datatype in my development box..
but my client doesn't want to develop in development box.
so i have exported that datatype as xsd from datatype editor.
and while importing into sandbox datatype editor i am getting this error..
Any help please......

Hi Rajeev,
now i have an .xml file its not importing into datatype...
error is
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8))
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema targetNamespace="http://abc.com/xa" xmlns="http://abc.com/xa" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="DT_PLANNINGSCHEDULE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">3c6ae480f2f111dbc7ac0002556ad065</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="PlanningSchedule_Output">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c0f15b11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PlanningScheduleHeader">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c1f15b11dbb6ef00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">6c804600f15d11dbc02400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleIssueDate" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d0f15d11db8dd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SchedulePurpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d1f15d11dbac4100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Purpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd50f15e11db9eb600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PurposeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd51f15e11dbc47a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d2f15d11dbbc3900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d3f15d11dba00200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d4f15d11dbc7e000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d5f15d11db969a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec100f16411dba2e900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec101f16411db997a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec102f16411dbb75900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec103f16411db8fa500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec104f16411dba93f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec105f16411dba20f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">0de2f450f16511dbaa4700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d0f16711dbbdd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d1f16711dbcd2600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d2f16711db82f800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d3f16711dbcf6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d4f16711dbcb6200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SellerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b80f16711dba8c100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb80f16811db82e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb81f16811dba6ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb82f16811db8b4e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb83f16811dbc0ff00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb84f16811dbb8f700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb85f16811dba46200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb86f16811db98c000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb87f16811dbb25200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb88f16811dbc7d100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e99ffa30f16811dba27100123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d30f16a11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipFromParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b81f16711dbbfce00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d31f16a11db9adf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d32f16a11dbbef100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d33f16a11db9e5600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d34f16a11dbba6d00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d35f16a11db855400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d36f16a11db877300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipToParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b82f16711db84ec00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac0f16b11dba49600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac1f16b11db80c700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac2f16b11db8ea300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac3f16b11dbb5bb00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac4f16b11dbb7bc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac5f16b11db92a300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Language">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d6f15d11db9f9a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LanguageCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd52f15e11dbc06300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationGroupedPlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c2f15b11dba9fd00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationGroupedPlanningDetail" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">89515130f17f11db98e400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Location">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832980f17f11db8d4600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d0f18011db8ce800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d1f18011db839900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d2f18011dba45300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d3f18011db9ac700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d4f18011dbc4ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d5f18011dbcd4400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832981f17f11db856100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257410f18111db8b6f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BasePlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257411f18111db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LineItemNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257412f18111db847f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerLineItemNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257413f18111dbcf7200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemIdentifiers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257414f18111dba6f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNumbers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257415f18111db968700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257416f18111db9f9100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257417f18111dbc32500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257418f18111dbcfa900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="StandardPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67960f18211db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67961f18211dbc78900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierQualifierCoded" type="xsd:integer">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67962f18211dbae6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ProductIdentifier" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815570f18411dbb4e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemDescription" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815571f18411db876f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfItemReferences">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef0f18711dbbafe00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef1f18711db8a7600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef2f18711db935200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef3f18711dba69c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ReferenceTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef4f18711db942b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PrimaryReference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef5f18711db93a800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Reference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef6f18711dbcebc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="RefNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef7f18711dbce6300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForecastFrequencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef8f18711db937b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef9f18711dba61400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefaf18711db9d4800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CommitmentLevelCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefbf18711dba59800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleDates">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefcf18711db947900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfDateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefdf18711dbc43e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefef18711dbaa5000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Date">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefff18711dbcde600123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="DateQualifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af00f18711db87f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af01f18711dbc9cf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleQuantities">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af02f18711dbc24100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfQuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af03f18711db842900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af04f18711dbb59400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityValue" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af05f18711dba6d900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="UnitOfMeasurement">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2580f18711dbc66f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="UOMCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2581f18711db89a000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2582f18711db9a1500123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Error while retreiving xml file from database

Hi-
I am trying to configure Planning and getting the following error message at instance configuration step:
"Error while retreiving xml file from database"
We looked at PlanningSystemDB.properties, changes server name to its ip, reinstalled planning, made sure both auth methods are selected (sql server and windows), created new relational repository.. still the same error.
Here is the contents of the configtool error file:
(Dec 11, 2008, 04:36:44 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
(Dec 11, 2008, 04:37:09 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
(Dec 11, 2008, 04:38:41 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
(Dec 11, 2008, 04:39:07 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
(Dec 11, 2008, 04:39:12 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
(Dec 11, 2008, 04:39:22 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
(Dec 11, 2008, 04:40:46 PM), com.hyperion.cis.config.CmsRegistrationUtil, ERROR, Failed to authenticate user = admin
(Dec 11, 2008, 04:41:05 PM), com.hyperion.cis.config.CmsRegistrationUtil, ERROR, Failed to authenticate user = admin
(Dec 11, 2008, 04:48:28 PM), com.hyperion.cis.DBConfigurator, ERROR, Invalid SQL statement: begin transaction IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_PROPERTIES]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_PROPERTIES IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_APP_CLUSTER_DTL]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_APP_CLUSTER_DTL IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_APPLICATION]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_APPLICATION IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_DATASOURCE]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_DATASOURCE IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_CLUSTER]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_CLUSTER IF EXISTS (select * from sysobjects where id = object_id(N'[HSP_ACTION]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSP_ACTION IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_PI_INFO]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_PI_INFO commit begin transaction CREATE TABLE HSP_ACTION ( ID INTEGER NOT NULL IDENTITY, CONSTRAINT PK_HSP_ACTION PRIMARY KEY(ID) , FROM_ID INTEGER, TO_ID INTEGER, ACTION_ID INTEGER, OBJECT_TYPE INTEGER, PRIMARY_KEY VARCHAR(255), ACTION_TIME DATETIME ); CREATE TABLE HSPSYS_CLUSTER ( CLUSTER_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), CONSTRAINT PK_HSPCLUSTER PRIMARY KEY(CLUSTER_ID) ); CREATE TABLE HSPSYS_DATASOURCE ( DATASOURCE_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), APP_ID INTEGER, RDB_SERVER_URL VARCHAR(255), RDB_TYPE VARCHAR(255) NOT NULL, RDB_CATALOG_NAME VARCHAR(255) NOT NULL, RDB_USER VARCHAR(255) NOT NULL, RDB_PASSWORD VARCHAR(255), RDB_DRIVER VARCHAR(255) NOT NULL, ESS_SERVER VARCHAR(255) NOT NULL, ESS_USER VARCHAR(255) NOT NULL, ESS_PASSWORD VARCHAR(255), CONSTRAINT PK_HSPDTASRC PRIMARY KEY(DATASOURCE_ID) ); CREATE TABLE HSPSYS_APPLICATION ( APP_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), DATASOURCE_ID INTEGER NOT NULL, CONSTRAINT FK_HSPAPP_DSID FOREIGN KEY(DATASOURCE_ID) REFERENCES HSPSYS_DATASOURCE, VERSION VARCHAR(255) NOT NULL, CONSTRAINT PK_HSPAPP PRIMARY KEY(APP_ID) ); CREATE TABLE HSPSYS_APP_CLUSTER_DTL ( APP_ID INTEGER NOT NULL , CONSTRAINT FK_HSP_APP_ID FOREIGN KEY (APP_ID) REFERENCES HSPSYS_APPLICATION , CLUSTER_ID INTEGER NOT NULL, CONSTRAINT FK_HSPCS_CLID FOREIGN KEY(CLUSTER_ID) REFERENCES HSPSYS_CLUSTER, CONSTRAINT PK_APP_CLSTR_DTL PRIMARY KEY(CLUSTER_ID, APP_ID) ); CREATE TABLE HSPSYS_PROPERTIES ( PROPERTY_ID INTEGER NOT NULL, OBJECT_ID INTEGER NOT NULL, PROPERTY_NAME VARCHAR(255) NOT NULL, PROPERTY_VALUE VARCHAR(255), CONSTRAINT PK_HSPPROP PRIMARY KEY(PROPERTY_ID, OBJECT_ID, PROPERTY_NAME) ); CREATE TABLE HSPSYS_PI_INFO ( XML_FILE NTEXT NOT NULL ); commit
(Dec 11, 2008, 04:50:32 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
Thanks for any help.

After spending 2+ hrs with Hyperion Support nothing got resolved.. Just to give more background on this problem, we originally reconfigured all Hyperion components to use different SQL server, that is when the problem started happening as soon as we got to Planning Instance Configuration. Could this be the situations when old server name is still somewhere in the system?.. Could this be Shared Services problem.
Here is another quote from SharedServices_Security.log
2008-12-12 15:08:48,249 [http-58080-Processor1] WARN com.hyperion.css.spi.impl.nv.NativeProvider.getHierarchicalRoleTree(Unknown Source) - Exception getting Child Roles in hierarchy due to Illegal or invalid id.dflt passed in. Please check the argument.
2008-12-12 15:31:18,121 [main] WARN com.hyperion.css.common.configuration.CSSConfigurationImplXML.<init>(Unknown Source) - Skipping the validation of the configuration because the required validating parser library not found or errors in validation. This does not guarantee the proper initialization of the component.
2008-12-12 15:31:29,808 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.resolveCircularDependency(Unknown Source) - INFO: Time to resolve circular dependency on the Cache for provider: DIPORTAL is : 0
2008-12-12 15:31:29,808 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.refreshProviderCache(Unknown Source) - INFO: Time to build Cache for provider: DIPORTAL in millis is : 1016
2008-12-12 15:31:30,823 [main] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /F:/Hyperion/deployments/Tomcat5/SharedServices9/config/CSS.xml.
2008-12-12 15:31:41,229 [http-58080-Processor4] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
2008-12-12 15:31:41,229 [http-58080-Processor4] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.
2008-12-12 15:38:01,938 [main] WARN com.hyperion.css.common.configuration.CSSConfigurationImplXML.<init>(Unknown Source) - Skipping the validation of the configuration because the required validating parser library not found or errors in validation. This does not guarantee the proper initialization of the component.
2008-12-12 15:38:13,454 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.resolveCircularDependency(Unknown Source) - INFO: Time to resolve circular dependency on the Cache for provider: DIPORTAL is : 0
2008-12-12 15:38:13,454 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.refreshProviderCache(Unknown Source) - INFO: Time to build Cache for provider: DIPORTAL in millis is : 813
2008-12-12 15:38:35,453 [main] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /F:/Hyperion/deployments/Tomcat5/SharedServices9/config/CSS.xml.
2008-12-12 15:42:09,776 [http-58080-Processor3] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
2008-12-12 15:42:09,776 [http-58080-Processor3] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.
2008-12-12 15:42:09,776 [http-58080-Processor2] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
2008-12-12 15:42:09,776 [http-58080-Processor2] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.

Product Instance Registration Error Message: "System Failure: Error while retrieving xml file from database"

Hi Planning installation Gurus,
Did u get any luck to resolve this problem as i am also facing same problem "Error creating instance" during install of Planning 9.3.1. i tried 30-50 times reconfiguration every time same problem..
OS: Vista Premium
SQL Server 2005
Essbase:9.3.1
Error Message: "System Failure: Error while retrieving xml file from database"
Details of error:::::::::::::::::::::::::
at com.hyperion.planning.event.HspSysExtChangeHandler.run(Unknown Source
Can not get JDBC connection for SYS external changed actions.
Can not get JDBC connection.
java.lang.NullPointerException
at com.hyperion.planning.sql.HspSQLImpl.getConnection(Unknown Source)
at com.hyperion.planning.event.HspSysExtChangeHandler.actionPoller(Unkno
wn Source)
at com.hyperion.planning.event.HspSysExtChangeHandler.run(Unknown Source
Can not get JDBC connection for SYS external changed actions.
Can not get JDBC connection.
java.lang.NullPointerException
at com.hyperion.planning.sql.HspSQLImpl.getConnection(Unknown Source)
at com.hyperion.planning.event.HspSysExtChangeHandler.actionPoller(Unkno
wn Source)
at com.hyperion.planning.event.HspSysExtChangeHandler.run(Unknown Source
Can not get JDBC connection for SYS external changed actions.
Can not get JDBC connection.
Pls provide Solution

Hi John,
though i am trying with SQl server authentication with different user but still status is same of planningSystemDB.properties
SYSTEM_DB_DRIVER=hyperion.jdbc.sqlserver.SQLServerDriver
SYSTEM_DB_URL=jdbc:hyperion:sqlserver://neeraj-PC:1433
SYSTEM_DB_USER=windowsAuthentication
SYSTEM_DB_PASSWORD=CAFBAEFNBGEAABHEDOADFKADACBGBIFHBLCDFBAFFH
SYSTEM_DB_CATALOG=plandb
SYSTEM_DB_TYPE=SQL
INSTANCE=
my steps:
Using SQL Server Management Studio
Changed Widows authentication to SQL server authentication mode
In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.
On the Security page, under Server authentication, select the new server authentication mode, and then click OK.
In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.
In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.
On the Security page, under Server authentication, select the new server authentication mode, and then click OK.
In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.
To restart SQL Server from SQL Server Management Studio
To enable the sa login by using Management Studio
In Object Explorer, expand Security, expand Logins, right-click sa, and then click Properties.
On the General page, you might have to create and confirm a password for the sa login.
On the Status page, in the Login section, click Enabled, and then click OK.
In Object Explorer, expand Security, expand Logins, right-click sa, and then click Properties.
On the General page, you might have to create and confirm a password for the sa login.
On the Status page, in the Login section, click Enabled, and then click OK.}}}
anything else should i change.................

Unknown issue while loading .dbf file by sql loader

Hi guys,
I am having a unknown issue while loading .dbf file by sql loader.
I need to load .dbf data into oracle table.for this I converted .dbf file by just changing its extension as .csv . file structure after changing .dbf to .csv --
C_N_NUMBER,COMP_CODE,CPT_CODE,C_N_AMT,CM_NUMBER
1810/4,LKM,30,45,683196
1810/5,LKM,30,45,683197
1810/6,LKM,30,45,683198
1810/7,LKM,30,135,683200
1810/8,LKM,30,90,683201
1810/9,LKM,1,45,683246
1810/9,LKM,2,90,683246
1810/10,LKF,1,90,683286
2810/13,LKJ,1,50.5,680313
2810/14,LKJ,1,50,680316
1910/1,LKQ,1,90,680344
3910/2,LKF,1,238.12,680368
3910/3,LKF,1,45,680382
3910/4,LKF,1,45,680395
7910/5,LKS,1,45,680397
7910/6,LKS,1,90,680400
7910/7,LKS,1,45,680401
7910/8,LKS,1,238.12,680414
7910/9,LKS,1,193.12,680415
7910/10,LKS,1,45,680490
then I am loading it by sql loader.but I am getting always error below ...
Record 1: Rejected - Error on table C_N_DETL_TAB, column CPT_CODE.
ORA-01438: value larger than specified precision allowed for this column
Record 2: Rejected - Error on table C_N_DETL_TAB, column CPT_CODE.
ORA-01438: value larger than specified precision allowed for this column
table structure-
create table C_N_DETL_tab
"C_N_NUMBER" VARCHAR2(13),
"COMP_CODE" VARCHAR2(3),
"CPT_CODE" NUMBER(4),
"C_N_AMT" NUMBER(20,18),
"CM_NUMBER" NUMBER(7)
control file-
options(skip=1)
load data
infile '/softdump/pc/C_N_DETL.csv'
badfile '/softdump/pc/C_N_DETL.bad'
discardfile '/softdump/pc/C_N_DETL.dsc'
into table C_N_DETL_tab
truncate
FIELDS TERMINATED BY ","
OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
C_N_NUMBER CHAR,
COMP_CODE CHAR,
CPT_CODE INTEGER,
C_N_AMT INTEGER,
CM_NUMBER INTEGER
but guys when I am increasing size of all columns of tabel upto its max value then data is loaded but when I am checking column max length after data loaded then its very less..
changed table structure-
create table C_N_DETL_tab
"C_N_NUMBER" VARCHAR2(130),
"COMP_CODE" VARCHAR2(30),
"CPT_CODE" NUMBER(32), ---- max value of number
"C_N_AMT" NUMBER(32,18), ---- max value of number
"CM_NUMBER" NUMBER(32) ---- max value of number
now i ma running ...
sqlldr express/express control=C_N_DETL.ctl log=C_N_DETL.log
o/p-
Table C_N_DETL_TAB, loaded from every logical record.
Insert option in effect for this table: TRUNCATE
TRAILING NULLCOLS option in effect
Column Name Position Len Term Encl Datatype
---------- ---- ---- C_N_NUMBER FIRST * , O(") CHARACTER
COMP_CODE NEXT * , O(") CHARACTER
CPT_CODE NEXT 4 INTEGER
C_N_AMT NEXT 4 INTEGER
CM_NUMBER NEXT 4 INTEGER
Table C_N_DETL_TAB:
20 Rows successfully loaded.
0 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
select max(length( CPT_CODE))from C_N_DETL_tab ---> 9
can u tell me why I need to increase size of table columns upto max value?although length of data is soo much less.
kindly check it..thnx in advance...
rgds,
pc

No database version of course. Unimportant.
If I recall correctly, it is 'integer external ' and you would best double quoting the alphanumerics (which you didn't ).
Try changing integer in integer external in the ctl file.
Sybrand Bakker
Senior Oracle DBA

Issues while processing the BOMs using fm ''CSAP_MAT_BOM_MAINTAIN'

Hi Group,
we are facing issues while processing the BOMs using the basic type(Z-idoc type) for standard type BOMMAT04.
thing is that the segment 'E1STPOM' is defined to contain 1 to 99999 records in it.
when an Idoc is run(say with 150/200 segments of 'E1STPOM'), there was a standard error with error message id PIC01(number : 004) when the Idoc is processed with the Standard function module 'CSAP_MAT_BOM_MAINTAIN'.
the error says 'Error reading material FING_005 . Exception: 0' and Check whether the material number is blocked. but when checked, the Material seems not blocked.
kindly advise how to overcome this error and proceed further.
Regards,
Vishnu

Checj the material status, while its transfer from one server to another server the status should be different

Issue while processing xml file

Similar Messages

Maybe you are looking for