The document structure is corrupt

Hi all
When prelighting a PDF in Acrobat 8.3.1 it is coming up with the error -
"The document structure is corrupt"
And it won't continue. A similar machine running 8.1.1 will preflight the file without producing the error.
Any ideas before I reinstall?
Cheers

Is it only this one file which fails? Reinstalling is unlikely to help, it's more likely that one of the checks has become more vigilant in 8.3.1 so the fact 8.1.1 passes is the issue, not the other way around.
Acrobat 8 is now end-of-line so you won't get any support from Adobe.

Similar Messages

How to get the document structure with the document number"?"

Hello experts,
I have now a big trouble. There is a document with the number '?' in our syste. And for this document a document structure was builded. Now I can't acess the document structure, because the system doesn't accept '?' as a document number...
Can you help me?
Thanks a lot!
best regards,
Ying

Hi Sarita,
thank you very much! My problem is now solved, and the documents in the structure are free again _
best regards,
Ying

To View the Document Structure

Hi All
I want to view the Document Structure (Product Structure) in the SAP PLM Table.
If any body knows, could you please share the table information?
My requirement is to get the Product Name (Doc Type: CE2) which are Empty (meaning - no parts or product under it).
Currently we are checking manually, by going through CDESK - Select Document - SAP View.
Regards,
Abirami

Thanks a lot Christoph.
But My requirement is to identify the empty Product (Product without any parts or product in it).
For Example.
Prod1
     SubProd1
           SubProd1-Part1
            SubProd1-Part2
     SubProd2
     SubProd3
             SubProd3-Part1
              SubProd3-Part2
In the above case, SubProd2 is empty. Normally I used to check using Display SAP-View Option. But my Main Product has thousands of subproduct. Here I find difficult to verify manually.
is there any other easy way for this?
Best Regards,
Abirami

Exporting the Document structure from CDESK

Hi,
I have a requirement to export the Document structure coming in Tcode CDESK for assemblies to Excel format with the fields like MM#, Description,ECM#, User etc.... How to get it ?
Thanks,
Suresh HP

Hi Suresh,
The structures can be brought to screens as a view only with enhancement and you need tio cinsult with abap'r and ask to make a view for the structure in respective screen like MM# ,ECM#. The views can resolve your requirement.
I hope this will help.
Regards,
Ravindra

How to find the Internal Document Structure Number STLNR from the DIR Key

Hello:
Our requirement: When a user moves the Header DIR of a Document BOM to Released Status, we need to check if all the BOM Items in this Document BOM have also been released (in Status Released). If not, we need to give the user an error message informing them which component DIRs need to be released before the system will allow them to release the Header DIR. We can do this by entering the DIR Key of the Header DIR and find out the Internal Document Structure Number (Document BOM Number = STLNR for BOM Category Document Structure STLTY = D) from the available input of the DIR Key DOKARDOKNRDOKTL+DOKVR. Then we need to use the value of STLNR in Table STPO to find the Document BOM Items and check the status of each BOM Item DIR.
If Table STKO had DIR Key as an input we would have our solution, but alas it does not. Can anyone point us in the right direction by suggesting how to get to STLNR from the DIR Key? Your help would be much appreciated!
Niraj Pant

Hi Niraj,
the STLNR should be contained in structure rc29k. You can also use the DMS BAPI DOCUMENT_GETDETAIL2 with parameter GetStructure or DOCUMENT_GETSTRUCTURE. With these BAPIs you should be able to determine the document structure to an existing document info record. For further information on the mentioned BAPIs please see SAP note <a href="https://service.sap.com/sap/support/notes/766277">766277</a> which contains a complete documentation on all existing DMS BAPIs.
Best regards,
Christoph
P.S.: Please reward points if this information was usefull.

Document structure & Document Hierarchy

Hi,
Can any one reply me the difference between Document structure & Document Hierarchy with suitable example for more clarification? Write me in your own words dont give me the link from sap help, I know that.
Waiting for your valuable response.
Regards,
Seema Pilankar

Hi,
from my point of view I would recommend you to use the functionality of document structure.
The main difference is that for document structure you can create a header in transaction CV11 and then link as many document info records to it. Further transactions are CV12 (edit) and CV13 (display). So the document structure is easier to handle. Due to the position interval it should be possible to add up to 999 documents here.
The document hierachy is nearly the same but you have to go the transaction CV02N and enter the superior document info record for each sub-document and this needs a lot more time than in CV12 for example. For the document hierarchy there is no limit on the number documents which are linked to a superior document info record.
For more information please see the SAP Online documentation (http://help.sap.com) under:
SAP R/3 Enterprise Application Components
- Cross-Application Components
- Document Management
- Document Structures
I hope this inrformation could be useful for you.
Best regards,
Christoph
P.S.: Please don't forget to reward points for good information.

Document hierarchy and document structure....

Can anyone give me a clear picture of document hiererchy band document structure
i have read the material, could not distinguish both...need a clarity with an example
Regards
surya

See By simple words
Document Structure
Similar to document BOM.This will help you to create a BOM comprising of various DIR's under one Library
Usage: In production order instead of attaching various documnets in line Item , Instead create a Document stucture and assign it under Production BOM which will occupy under single Line Item.
The function for exploding a document structure from top to bottom gives a list of all the documents and text items contained in the structure. Each document contained in such a structure can have its own document structure, as well as being a component of others. These document structures are exploded completely, level by level. The depth of the explosion levels is unlimited. The document structure can be accessed directly from the processing functionality of the document info record.
Document Hyrarchy
You can Create a link between the originals attached in the DIR, by defining the superiority status .
By defining a superior document, a direct predecessor for a simple document hierarchy can be set. The hierarchy is not limited to this level; it can be expanded from the superior document.
The superior document can:
u2022 Be superior to other documents
u2022 Be inferior to another document
Documents of different document types can be put into a document hierarchy. Recursiveness is not supported; the same document may not appear in two different places in the hierarchy. This means that a document can only be entered once in the entire u2018explosion pathu2019. By entering superior documents, an entire document hierarchy can be represented in the system.
Let me know if you need More info.
Regards,
Muralidharan

How to export a document structure to a local file (spreadsheet)

Hi,
We are using document structures now to manage our NPI project data through EasyDMS. What we are looking to achive is to be able to take a snapshot of the document structure at a critical moment in time. Specifically, when we launch the new product. On the material side, we have CS11 which will explode a BOM and let you export the results to a spreadsheet. I am looking for the same functionality for a document structure. How can we do this? I don't see an option to export with the CV13 transaction. Is there another transaction available to achive this? I know that we can enter CV13 with a validity date to browse and drill down into the contents at the time of launch, but we are looking to create a listing of the documents in the structure instead, which is easier to review "at a glance".
Thanks,
Joseph Whiteley

Interesting question. I tried looking around, but didnt find anything perfect.
The best option is the document structure browser as found in the PLM7 document work center. It gives you an export, but doesn't keep the levels. All you get is a flat excel file...
Screenshots below
Espen

ALE Document Structure

We currently ALE documents from one SAP system to another using DOCMAS and CLFMAS message types. Now we would also like to ALE the document structure for our 3D assemblies. I'm not sure of the proper method to do this. We have set up a new ALE path for the message type BOMDOC. Now when we ALE documents using BDA5 the document structure is ALE'd through BOMDOC along with DOCMAS and CLFMAS to the target system. However, the document structure is not updating properly. The document structure on the target system grows each time you send the same document, instead of deleting and updating appropriately. We are on ECC 6.

Hi Meenakshi
Document structures help you organize complex information (documents) by creating information units. For example, you can use a document structure to manage the entire documentation on a very complex product, which consists of a text file, several technical drawings, photographs, various service manuals, and films containing operating instructions.
You can use a document structure as an assembly more than once in different BOM categories . You can create a where-used list to determine the BOMs and document structures in which the assembly is used.
For More Info Check this help in details.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/c1/1c296d43c711d1893e0000e8323c4f/content.htm
Yess you can use this functionality of Document Structure in scenario where design depart ment prepares various design drawings of a reactor vessel.So this reactor is broken down into various parts ( BOM).With the help of Document structure these relation can be maintained in SAP DMS.
If you have IDES system installed in your company go through the examples given in it .
With Regards
Mangesh Pande

Appreance of Document structure

Hi Gurus,
My client is asking to suppress the document structure appearence which is in the DIR screen, where i could suppress Hierrarchy, CAD interface but iam unable to hide Document structure.
Kindly get me the solution for this.
Regards
Kannan

Hi Kanna,
In standard behaviour it's not feasible to hide the document structure. Kindly discuss with abap'r and ask him to hide this with z-program.
Hope this will help.
Regards,
Ravindra

Moving pages using Manage Site content and structure is corrupting the version history

Hi,
I am using share point 2010 manage site content and structure feature to move pages from one sub site to other. After doing several edits and check ins of a page and if I try to move the page using manage site content and structure , the version history
is corrupted in the destination site (i.e., all the versions are not showing).
Note: Sometimes content is also getting replicated after performing move operation.
Is it a Bug/ Known issue in SharePoint?
Any info on this issue is very helpful to us.
Thanks in advance!!

Hi,
Using Site Content and Structure unable to move documents,pages and getting weird error message
We are getting Below error:
When Moving Document items from one site to another site in the same site collection using Site content and structure(But it's working in same site,we can move documents from one library to another library)
1576|/wEWwwECuLLErw0Cy+nFYwK84baBAgK6zNqsAgLs0Le0BQK1s8uaCAL5qrm3CAKk7K6pDwKo9a0GArm+xr4NApKe9KUKAoajpK4CAqqU/2sChJXBtAIC052rYQKS+LTPAgLe+7uQAwLO0re/BwLgoaw2AojAlIMOApSO4JoNAuvW7MoKAojz2P4OAuOMt9EGAv/ns1wC64qI7gEC0LymmAcCro3lnQkCj7viwAsC8Met9QEC3a/DHALg4ZO6AQKAn8ebCALvr72DAwKm/NGmAgKN4aayCQLmmczsCgL+46qSAQKH7paCDgLouOHjDwKGuNCBCQKwuob2CQKP78n3BwLQ7vSYCALxlcvIBALRuajXAwK6/vr4AwKx8YasCQLti5igAQKay7JZAta625IFAuTy6rUKAvnC7eQKApvB3ugPAoTBua8BAoyajvgMAsGdloEJAvH+2KECAua7k9AGAv3Lzd8HAtPD3ocOAuX7hM4GAqO1g9sIAtn65sgFAuDkr9QEAt7I1KkMAryhltsIAtizx/kBAvzS7IcBAr+YhK4PAsO3rtADAvea+sADAsvc4IgKAp/1vIoMApelp3ICl+PqiwwC/KX1gwUC3fv58gIC7ZG/pwIC4cnupQgCq7mdlgYCjciR+AwC8/ue4gkC4YWJywUCs+rviAECpuyJigECkfr5rgkC08rHoQ0C+erayQUCjMqStQkCpIuKtwEC+dG5ngICoZ3/og0CspXoxwwC+pzgmwwCkoD5mAYCn/qH2AcC/N/pvAcCv5OtwAICuZquqgcC0/OFnwkC2/2wzQMCrJrO9woC69G52ggC64nunggCtLOIsQEC9LyC7gUC0ry/zgIC1ZDvgQ0C98OfMgL4kaj3CQKXhebCCwKi3bjPBQKYuojTCAKc4+fxCAKyjLfoBALVxO8SAsXSyuQLAqyvkNIPApDV5PgDAtufwJwEAu2BsoYLAs3Oqd8PAo6i+YMDAsy706oCAsLjx7kLApu3+9gKAuLnvMoIAtWywo8OAv6MjvIHAtSDhJwNArXRmL0LAraZvUcC5cGygQoCz5HN7A0C+YzY9AMCmtWQ6AUC/oHF8w4CxeTgmg8CgszujQECss22vgYCp6HBuggCkfm+FAKngqb5BgKkuIzAAQKPspKCCQLu+eDvCwKf5YrEBQKl0M3ACgKm85DvDALCu/nfCwLbwO38DgLoz5eyDQLfr9XLCwL20/eUDgL7hpr3DAKh1tfbCgL48OuNBwK4tuKaCALpgbn5CgLC4dKvBgKKlu76CwKfhKLJAQLurPTIAwLG0o+hAgKI5Y6dDALq+OOlCQKxjuuICAK8yrLHBwLcrOSSAwLoiJfQCwKKyvrtBALXkbCBCgKt4bG9BQLr6qnxCwLC2pz2DQKQ7OuZBALt7t+DDAKR47b8CAKi6pPGCQKLl4r3CQK5yfj+AwLgzYvjDwKUjerODQK7mOPTCQL9qP3qBgKYiOL9AgLA8pSaBwKay8fBDQLqw93DCgKkjpf/CwLsyquQCwKtpbGsDALMtKmxBwKPpvCmBOAFHtmBuG3iNmIT9fQ8Z1TWMpjZ122|cccccccccnncnnnnn|

Corrupted .docx file. Word 2007. Can't open the document. Tags mismatch. Help?

The Office Open XML file *.docx cannot be opened because there are problems with the contents.
Details: The name at the end tag of the element must match the element type in the start tag.
Location: Part: /word/document.xml, Line: 2, Column: 3487212
Hmm, I guess I should give some background info and what I've tried so far, right?
The document is in word 2007, Windows 7. Last night, I was in a hurry, and got a lot of things open. I was opening the document to do a few quick spontaneous revisions, but it was so laggy and I was late for an appointment, so I was feeling panicky
and frustrated. In hindsight, it probably wasn't the best option to just force shut the PC down cause word stopped responding in the middle of opening the document. Still, while I'm no Sherlock, I knew stopping it while it's in the middle of saving the document
would bebad, I didn't think stopping it while opening the document (and not really modifying the document at all, at least that was what I thought before), could have drastic consequences! The document's quite
large, a few hundred words, and about 500 or so pages. It's this really big project I was doing at work, for months now really, and because it's somewhat business confidential in nature, I can't exactly share it freely, or I would've uploaded a copy, sorry.
Anyway, I woke up this morning and opened it, and the error came up. By the way, the document was saved in a 2TB external hard with a few disk errors in the past, if that helps, even if I'm pretty much sure its not a problem with the hard. The error
came up... and yeah. I first made a copy, which I've been trying everything on, in case I do end up making things worse. I have no previous versions of it, just a relatively very old backup. Anything less than 80% recovery would set me back weeks with a wage
cut. The good news is that I was able to open the document in WordPad, managing to recover the first 287 pages (131,543 words), with no errors or data loss, and saved it in a separate file. Apparently, according to information I obtained later, MSWord tends
to not open at all when it encounters an error, but Wordpad tends to stop reading the rest of the code once it encounters an error. So, naturally, I assumed (so correct me if I'm wrong), that behind a few sentences I might lose due to the error, the rest could
also be salvageable. I then looked up the problem all over the internet. Read a microsoft article on troubleshooting/recovering corrupted documents (Open & Repair, Draft Mode, Creating Link, Recover text from any file converter, etc). No dice.
I first saw a similar question on answers.microsoft, and tried to use Tony Jollan's Rebuilder, macros enabled and all. Sadly, no luck.
I managed to make my first breakthrough when I found out that .docx was just a .zip file, and could be renamed as such, with the document.xml extracted and manually fixed using an XML editor (not that I knew how to do that, but I was desperate and
willing to learn). So, made another copy, changed extensions, and tried to specifically extract the document.xml. I believe that it is the main body text, right? That is the only thing really necessary for me, since everything I've done so far is entirely
spartan, with no fancy fonts, formatting, header/footer/notes, media objects, formulas, tables, bullet points, numbered lists, etc. All pure sans-serif text, with some Japanese Kanji thrown in. 500 pages of pure text.
I then hit a snag, when WinRAR encountered an error on extracting document.xml, stating that "CRC failed in word\document.xml. The file is corrupt". So I tried to fix this using several ZIP repair programs and stuff. Nothing worked. At
least not so far. Managed to extract an incomplete version of document.xml using WinRAR's 'Keep Broken Files' option when extracting. The extracted
document.xml came up to 3.31 MB while the original in archive is 7.53 MB. Viewed it in the Windows XML Editor which opened up the text in Internet Explorer, a jumble of text with no line breaks or paragraphs. Still, it actually extracted a few pages less than
the open-using-Wordpad method tried earlier. So trying to fix the archive again...
So I decided to give up the manual route for the meantime and focus on readymade solutions. I came across yet another microsoft article, but this one was at least more relevant than the last. It had this auto FixMe thing. I ran it, didn't
work. Apparently, as I found out later, "This fix will work for one specific tag error where there are equations and graphics in the same paragraph AND Office 2010 SP1 has not been applied."
Tried several (read: dozens) corrupt Word recovery software, from freeware to pro trials, to varying degrees of effect, although unsuccessful
in goal. Some failed to read it, saying it was too corrupted for them to handle, the best managed to recover about three-pages-worth less data compared to the Wordpad method. So yeah, anybody with a similar problem, always open it with wordpad first and recover
what you can. That doesn't mean I'm giving up though.
So here I am, tearing my hair out in frustration. Whew, I feel like I told you guys my life story. I guess worst case scenario, I report this to my boss, so I personally or from the company, I/we'll hire a team of professionals to deal with it.
But that's not an ideal scenario. It's gonna be out of my salary either way (the company has a firm policy of 'You reap what you sow'), along with a wage cut for making such an amateurish mistake even with continuous reminders to back it up every two sentences,
so I'd rather avoid that.
I'm currently looking to see whether there's a way to recover a previous version of an overwritten document somehow using a third-party software or something. (I didn't have Windows Backup enabled, so no previous version on Windows). So far, no
autosaved documents on MSWord AutoRecover, even though I have it enabled set to every 3 mins (or maybe I'm just not seeing it since I'm trying to look for it manually?). Or are the temporary files wiped on shutdown? I don't have 'Always save backup copy' option
enabled on word either.
So yeah, an auto fix, or a lengthy answer detailing what exactly I should do (from the very very basics), or a link to a site with such info, would be much appreciated. Seriously :D
Please. Thanks for at least making an effort :)

When a Word document file is corrupted, then you can try several methods to recover it:
1. First of all, you can try the recovery function integrated with Microsoft Word, as follows:
1) On the File menu, click Open.
2) In the Look in list, click the drive, folder, or Internet location that contains the file that you want to open.
3) In the folder list, locate and open the folder that contains the file.
4) Select the file that you want to recover.
5) Click the arrow next to the Open button, and then click Open and Repair.
You may find more information about this at:
http://office.microsoft.com/en-us/word-help/recover-the-text-from-a-damaged-document-HP005189610.aspx (for Word 2003)
http://support.microsoft.com/kb/893672/en-us (for Word 2007/2010/2013)
2. If you have multiple corrupt Word documents, then you can use the VBA macro provided in article
http://support.microsoft.com/kb/893672/en-us so that all the files will be opened in "Open and Repair" option automatically.
3. There are also free tools from third-parties that can open and read Microsoft Word documents, for example,
3.1 OpenOffice at http://www.openoffice.org. This is a very famous open source project that is designed to support Office file formats, including Word documents. The software can run under Windows.
3.2 LibreOffice at http://www.LibreOffice.org. Another free office suite.
3.3 AbiWord at http://www.abisource.com. This is a cross-platform tool that works under Unix and Windows.
3.4 Google Drive at https://drive.google.com/ also support to load Word document files.
Sometimes when Word fails to open your document, these tools may be able to open it successfully. If that is the case, then after the document is opened, you can just save it as a new document which will be error-free.
4. For docx files, they are actually a group of files compressed in Zip file format. Therefore, sometimes, if the corruption is only caused by the Zip file, then you can use Zip repair tools such as WinRAR at
http://www.rarlab.com to repair the file, as follows:
4.1 Assuming the corrupt document is a.docx, then you need to rename it to a.zip
4.2 Start WinRAR, go to "Tools > Repair Archive" to repair a.zip and generated a fixed file a_fixed.zip.
4.3 Rename a_fixed.zip back to a_fixed.doc
4.4 Using Word to open a_fixed.doc.
There may still be some warnings when opening the fixed file in Word, just let ignore it and Word will try to open and repair the fixed file. If the file can be opened successfully, then you can just save the contents into another error-free file.
5. If all above methods does not work, then you may try third-party tools such as DataNumen Word Repair at
http://www.datanumen.com/word-repair/
I have used it to repair some word documents successfully. It provides a free demo version so that you can try to see if the data you want can be recovered or not.
Good luck!

How to restrict the user to change the project structure but not the documents?

Hi,
I have created one project assigning different users in Solution manger. I want to risitrict some of the users to change the project structure but simultaneously allwoing the project documents to be created, edited or deleted using solar01 under Project documentation tab. For that I have followed the steps provided in the follwoing link.
http://wiki.scn.sap.com/wiki/display/SM/Howto+Restrict+Changes+to+Project+Nodes+to+Assigned+Team+Members
I am able to restrict the users to change the project structure, but I am not able to allow access to the project documents. It gives me the message "You are not authorised to change the project". This fulfills my one of the requirements. But, Is there any way to restrict the user to change the project structure but not the documents?. Any help will be apperitiated.
Thanks,
Rutvik Uapdhyay.

Hi Rutvik,
Basically there are 2 different authorization role ...you should look for and customize as per requirement in Z* namespace.
role - SAP_SOLAR01_ALL
this take care of objects in Solar01 like tab access etc
role -SAP_SOL_KW_ALL
this takes care of entire documentation within solman
hope this helps
Regards
Prakhar

XML document structures must start and end within the same entity

Hi there,
I'm working with a client/server application and using SaxParser for reading in xml. I get the SaxParserException: XML document structures must start and end within the same entity. I understand what that means, but it isn't applicable! The xml data being used is well-formed. I checked the well-formedness with Stylus Studio to make sure. Here's the data:
<?xml version='1.0' encoding='UTF-8'?>
<vcmessage>
     <vcsource>3</vcsource>
     <processevent>16</processevent>
     <shape>
          <llindex>0</llindex>
          <shapetype>9</shapetype>
          <shapeproperties>
               <shapelocation>
                    <xcoord>54</xcoord>
                    <ycoord>184</ycoord>
               </shapelocation>
               <bounds>
                    <width>24</width>
                    <height>24</height>
               </bounds>
               <fgcolor>
                    <fgred>0</fgred>
                    <fggreen>0</fggreen>
                    <fgblue>0</fgblue>
               </fgcolor>
               <bgcolor>
                    <bgred>255</bgred>
                    <bggreen>255</bggreen>
                    <bgblue>255</bgblue>
               </bgcolor>
               <thickness>1</thickness>
               <isfilled>false</isfilled>
          </shapeproperties>
     </shape>
</vcmessage>The parser generally stops around the </bgcolor> tag.
I'm using Eclypse as my IDE. I'm wondering if there's something wrong with it? Or maybe there's something wrong with the class I'm using for reading in the XML? Followng is the class.
Please advise,
Alan
package vcclient;
import java.io.*;
import org.xml.sax.*;
import org.xml.sax.helpers.*;
import javax.xml.parsers.*;
public class XMLDocumentReader extends DefaultHandler
private VCClient client = null;
private Writer out;
private String lineEnd = System.getProperty("line.separator");
private boolean haveSourceType = false;
private boolean haveUserName = false;
private boolean haveMessage = false;
private boolean haveProcessEvent = false;
private boolean haveLinkedListIndex = false;
private boolean haveOpeningShapePropertiesTag = false;
private boolean haveShapeType = false;
private boolean haveOpeningShapeLocationTag = false;
private boolean haveShapeLocation = false;
private boolean haveOpeningXCoordTag = false;
private boolean haveOpeningYCoordTag = false;
private boolean haveOpeningBoundsTag = false;
private boolean haveBoundsWidth = false;
private boolean haveBoundsHeight = false;
private boolean haveOpeningFGColorTag = false;
private boolean haveOpeningBGColorTag = false;
private boolean haveOpeningThicknessTag = false;
private boolean haveOpeningIsFilledTag = false;
private boolean haveOpeningImageDataTag = false;
private boolean haveOpeningTextDataTag = false;
private boolean haveFGRed = false;
private boolean haveFGGreen = false;
private boolean haveFGBlue = false;
private boolean haveBGRed = false;
private boolean haveBGGreen = false;
private boolean haveBGBlue = false;
private boolean haveThickness = false;
private boolean haveIsFilled = false;
private boolean haveImageData = false;
private boolean haveTextData = false;
private VCMessage vcmessage = null;
public XMLDocumentReader(VCClient value)
       client = value;
       vcmessage = new VCMessage();
public VCMessage getVCMessage()
       return vcmessage;
public boolean haveSourceType()
     return haveSourceType;
public boolean ParseXML(InputStream stream)
     boolean success = false;
     // Use the default (non-validating) parser
    SAXParserFactory factory = SAXParserFactory.newInstance();
    try
         // Set up output stream
        out = new OutputStreamWriter(System.out, "UTF-8");
        // Parse the input
        SAXParser saxParser = factory.newSAXParser();
        saxParser.parse( stream, this );
        success = true;
    catch (SAXParseException spe)
        // Error generated by the parser
        System.out.println("\n** Parsing error"
           + ", line " + spe.getLineNumber()
           + ", uri " + spe.getSystemId());
        System.out.println("   " + spe.getMessage() );
        // Unpack the delivered exception to get the exception it contains
        Exception x = spe;
        if (spe.getException() != null)
            x = spe.getException();
        x.printStackTrace();
        return success;
    catch (SAXException sxe)
         // Error generated by this application
         // (or a parser-initialization error)
         Exception x = sxe;
         if (sxe.getException() != null)
             x = sxe.getException();
         x.printStackTrace();
         return success;
    catch (ParserConfigurationException pce)
        // Parser with specified options can't be built
        pce.printStackTrace();
        return success;
    catch (Throwable t)
         t.printStackTrace();
         return success;
    return success;
public void startDocument()throws SAXException
      emit("<?xml version='1.0' encoding='UTF-8'?>");
      nl();
public void endDocument()throws SAXException
      try {
          nl();
          out.flush();
      } catch (IOException e) {
          throw new SAXException("I/O error", e);
public void startElement(String namespaceURI,
                           String lName, // local name
                           String qName, // qualified name
                           Attributes attrs)throws SAXException
      String eName = lName; // element name
      if (eName.equals(""))
         eName = qName; // namespaceAware = false
      emit("<"+eName);
      if (attrs != null) {
          for (int i = 0; i < attrs.getLength(); i++) {
              String aName = attrs.getLocalName(i); // Attr name
              if (aName.equals("")) aName = attrs.getQName(i);
              emit(" ");
              emit(aName + "=\"" + attrs.getValue(i) + "\"");
      emit(">");
      if(makeStartTag(eName).equals(Constants.OPENING_SHAPEPROPERTIES))
          haveOpeningShapePropertiesTag = true;
      else if(makeStartTag(eName).equals(Constants.OPENING_SHAPELOCATION))
          haveOpeningShapeLocationTag = true;
      else if(makeStartTag(eName).equals(Constants.OPENING_BOUNDS))
          haveOpeningBoundsTag = true;
      else if(makeStartTag(eName).equals(Constants.OPENING_FGCOLOR))
             haveOpeningFGColorTag = true;
      else if(makeStartTag(eName).equals(Constants.OPENING_BGCOLOR))
          haveOpeningBGColorTag = true;
      else if(makeStartTag(eName).equals(Constants.OPENING_BGGREEN))
           System.out.println("See BGGreen");
      else if(makeStartTag(eName).equals(Constants.OPENING_BGBLUE))
           System.out.println("See BGBlue");
      else if(makeStartTag(eName).equals(Constants.OPENING_THICKNESS))
          haveOpeningThicknessTag = true;
      else if(makeStartTag(eName).equals(Constants.OPENING_ISFILLED))
          haveOpeningIsFilledTag = true;
      else if(makeStartTag(eName).equals(Constants.OPENING_IMAGEDATA))
          haveOpeningImageDataTag = true;
      else if(makeStartTag(eName).equals(Constants.OPENING_TEXTDATA))
          haveOpeningTextDataTag = true;
public void endElement(String namespaceURI,
                         String sName, // simple name
                         String qName // qualified name
                        )throws SAXException
       if(sName.equals("") && !qName.equals(""))
          sName = qName;
          emit("</"+sName+">");
       else
          emit("</"+sName+">");
       if(makeEndTag(sName).equals(Constants.CLOSING_SOURCE_TYPE))
          haveSourceType = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_USER))
          haveUserName = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_MESSAGE))
          haveMessage = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_PROCESSEVENT))
           haveProcessEvent = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_LINKEDLISTINDEX))
           haveLinkedListIndex = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_SHAPETYPE))
           haveShapeType = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_SHAPELOCATION))
            haveOpeningShapeLocationTag = false;
       else if(makeEndTag(sName).equals(Constants.CLOSING_WIDTH))
           haveBoundsWidth = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_HEIGHT))
           haveBoundsHeight = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_BOUNDS))
            haveOpeningBoundsTag = false;
       else if(makeEndTag(sName).equals(Constants.CLOSING_FGRED))
           haveFGRed = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_FGGREEN))
           haveFGGreen = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_FGBLUE))
           haveFGBlue = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_FGCOLOR))
            haveOpeningFGColorTag = false;
       else if(makeEndTag(sName).equals(Constants.CLOSING_BGRED))
           haveBGRed = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_BGGREEN))
         haveBGGreen = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_BGBLUE))
           System.out.println("See closing BGBlue");
           haveBGBlue = true;
       else if(makeEndTag(sName).equals(Constants.CLOSING_BGCOLOR))
            haveOpeningBGColorTag = false;
       else if(makeEndTag(sName).equals(Constants.CLOSING_THICKNESS))
           System.out.println("XMLDocumentReader: Step2");
            haveOpeningThicknessTag = false;
       else if(makeEndTag(sName).equals(Constants.CLOSING_ISFILLED))
           haveOpeningIsFilledTag = false;
       else if(makeEndTag(sName).equals(Constants.CLOSING_IMAGEDATA))
           haveOpeningImageDataTag = false;
       else if(makeEndTag(sName).equals(Constants.CLOSING_TEXTDATA))
           haveOpeningTextDataTag = false;
private String makeStartTag(String tag_name)
       String start = "<";
       String end = ">";
       return start.concat(tag_name).concat(end);
private String makeEndTag(String tag_name)
       String start = "</";
       String end = ">";
       return start.concat(tag_name).concat(end);
public void characters(char buf[], int offset, int len)throws SAXException
       String s = new String(buf, offset, len);
      if(haveSourceType == false)
           if(vcmessage.getSourceType() == null)
              try
                if(s.equals(""))return;
               int sourcetype = Integer.parseInt(s);
               vcmessage.setSourceType(sourcetype);
              catch(NumberFormatException nfe){}
      else if(vcmessage.getSourceType() == SourceType.CHAT_SOURCE)
        if(vcmessage.getSourceType() == SourceType.CHAT_SOURCE && haveUserName == false)
             vcmessage.setUserName(s);
        else if(vcmessage.getSourceType() == SourceType.CHAT_SOURCE && haveMessage == false)
           //When the parser encounters interpreted characters like: & or <,
           //then this method gets invoked more than once for the whole message.
           //Therefore, we need to concatonate each portion of the message. The
           //following method call automatically concatonates.
           vcmessage.concatMessage(s);
      else if(vcmessage.getSourceType() == SourceType.WHITEBOARD_SOURCE)
           if(haveProcessEvent == false)
             try
               vcmessage.setProcessEvent(Integer.parseInt(s));
             catch(NumberFormatException nfe){}
           else if(haveLinkedListIndex == false)
                try
                   vcmessage.setLinkedListIndex(Integer.parseInt(s));
                 catch(NumberFormatException nfe){}
           else if(haveShapeType == false)
                try
                   vcmessage.setShapeType(Integer.parseInt(s));
                 catch(NumberFormatException nfe){}
           if(haveOpeningShapePropertiesTag)
                if(haveOpeningShapeLocationTag)
                     if(haveOpeningXCoordTag)
                          try
                            vcmessage.setXCoordinate(Integer.parseInt(s));
                          catch(NumberFormatException nfe){}
                     else if(haveOpeningYCoordTag)
                          try
                            vcmessage.setYCoordinate(Integer.parseInt(s));
                            //reset all flags for ShapeLocation, X and Y coordinates
                            haveOpeningXCoordTag = false;
                            haveOpeningYCoordTag = false;
                            //haveOpeningShapeLocationTag = false;
                          catch(NumberFormatException nfe){}
                else if(haveOpeningBoundsTag)
                     if(haveBoundsWidth == false)
                          try
                            vcmessage.setBoundsWidth(Integer.parseInt(s));
                          catch(NumberFormatException nfe){}
                     else if(haveBoundsHeight == false)
                          try
                            vcmessage.setBoundsHeight(Integer.parseInt(s));
                            //reset flag
                            //haveOpeningBoundsTag = false;
                          catch(NumberFormatException nfe){}
                else if(haveOpeningFGColorTag)
                     if(haveFGRed == false)
                          try
                            vcmessage.setFGRed(Integer.parseInt(s));
                          catch(NumberFormatException nfe){}
                     else if(haveFGGreen == false)
                          try
                            vcmessage.setFGGreen(Integer.parseInt(s));
                          catch(NumberFormatException nfe){}
                     else if(haveFGBlue == false)
                          try
                            vcmessage.setFGBlue(Integer.parseInt(s));
                            //reset flag
                            //haveOpeningFGColorTag = false;
                          catch(NumberFormatException nfe){}
                else if(haveOpeningBGColorTag)
                     if(haveBGRed == false)
                          try
                            vcmessage.setBGRed(Integer.parseInt(s));
                          catch(NumberFormatException nfe){}
                     else if(haveBGGreen == false)
                          try
                            vcmessage.setBGGreen(Integer.parseInt(s));
                          catch(NumberFormatException nfe){}
                     else if(haveBGBlue == false)
                     {   System.out.println("getting BGBlue data");
                          try
                            vcmessage.setBGBlue(Integer.parseInt(s));
                            //reset flag
                            //haveOpeningBGColorTag = false;
                          catch(NumberFormatException nfe){}
                else if(haveOpeningThicknessTag)
                     try
                        vcmessage.setThickness(Integer.parseInt(s));
                      catch(NumberFormatException nfe){}
                else if(haveOpeningIsFilledTag)
                     vcmessage.setIsFilled(s);
                else if(haveOpeningImageDataTag && vcmessage.getProcessEvent() == org.jcanvas.comm.ProcessEvent.MODIFY)
                     vcmessage.setBase64ImageData(s);
                else if(haveOpeningTextDataTag && vcmessage.getProcessEvent() == org.jcanvas.comm.ProcessEvent.MODIFY)
                     vcmessage.setTextData(s);
                //reset
                haveOpeningShapePropertiesTag = false;
      emit(s);
//===========================================================
// Utility Methods ...
//===========================================================
// Wrap I/O exceptions in SAX exceptions, to
// suit handler signature requirements
private void emit(String s)throws SAXException
      try {
          out.write(s);
          out.flush();
      } catch (IOException e) {
          throw new SAXException("I/O error", e);
// Start a new line
private void nl()throws SAXException
      try {
          out.write(lineEnd);
      } catch (IOException e) {
          throw new SAXException("I/O error", e);
//treat validation errors as fatal
public void error(SAXParseException e)
throws SAXParseException
    throw e;
// dump warnings too
public void warning(SAXParseException err)
throws SAXParseException
    System.out.println("** Warning"
        + ", line " + err.getLineNumber()
        + ", uri " + err.getSystemId());
    System.out.println("   " + err.getMessage());
}

Just out of curiosity what happens if you append a space to the end of the XML document?

Changes in the PRICING STRUCTURE FOR THE DOCUMENT TYPE

Hello Gurus,
What is pricing structure?
and what is meant by changes in pricing structure for the document type.
Could anyone let me know about pricing structure and changes in Pricing structure for document type.
prashant

Hi Prashnat,
In SAP Pricing works on Condition Techniqe.
Condition Technic consits to following things.
1.Condition Tabels ( Assigned to Access Sequence )
2.Access Sequence ( Assigned to Condition Types)
3.Condition Types ( Assigned to Pricing Procedure)
4.Pricing Procedure
5.In Pricing Procedure Determination will be assigning as fallows:
Sales Org + Dist Channel + Division + Document Pricing Procedure + Customer Pricing Procedure + Pricing Procedure.
Based on this the Pricing will be takes place in the system.
Hope this Clarifies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

The document structure is corrupt

Similar Messages

Maybe you are looking for