Cross-Organization Document Structure Standards

Sept. 12, 2007
Where each of many document providers are sending similar documents to many document receivers, could standard document stuctures be developed for Live Cycle so that document providers that have Live Cycle could use the standard document structures and avoid having to independently develop a structure similar to structures developed by its peers?
For example, title insurance companies provide documents to loan underwriters at banks, including duplicate policies. Could industry-wide standard documents be developed so that all title companies could use them? The receiving banks would store them in their underwriting file.
Another example is building property managers (among others) often ask for certification that a tenant's sub-contractor (or supplier) provide certfication that it has liability insurance or that the property manager be added to the liability insurance policy. The liability insurance companies print the certificate and mail it (US Postal Service). Could this postal mail be replaced by a Live Cycle industry-wide certificate structure?
Milo Fleck

Hi Sai,
mainly you can work with both ways. The creation of a class which enables your users to classify each document info record and then control the permissions with the suitable authorization objects or by a BADI implementation will work.
Another solution would be to create a document BOM structure in CV11 or with the help of the new browser function in ECC 600 release. For further information on the browser function please see also the following link http://wiki.sdn.sap.com/wiki/display/PLM/NewFunctionalitiesinERP2005.
Additionally I think that EasyDMS could also be a solution to setup this scenario for your user. In the above SDN WIKI area for DMS you will also find a special content part for EasyDMS too.
In the release ECC 600 with EA-PLM extenstion you can use the ACL authorization concept to add individual authorizations for
users to single document info records. This could be useful to allow one user to enter folder A and another to enter only folder B.
I hope that this information could be useful for you.
Best regards,
Christoph

Similar Messages

Cross-reference between structured and unstructured FM documents

Hello,
Is it possible to retain FM cross-references from structured to unstructured FM documents during an XML round trip?
From what I know, cross-references between or inside structured documents form pairs of ID and IDREF, while cross-references to unstructured documents are dumped as normal text and lose their functionality.
The unstructured target documents might be converted to Structured FM at some point, but for the time being I'd like to find another solution. Do you know any solution to this?
Thanks,
Johannes

Johannes,
This is just a guess, because I do not do this.
First, of course, you cannot export the unstructured file to XML, because it is unstructured.
Second, IF the cross-reference from the structured file to the unstructured file were done via your cross-reference ELEMENT, then the cross-reference element should export to XML as an XML element with one of its IDref attribute set to the ID of something in the unstructured file. When you open the XML file in FrameMaker, the cross-reference is re-established.
In other words, when exporting to XML, FrameMaker does not care to what you are referencing. It just converts the cross-reference element into an element with an attribute in the XML file. So, it should work as expected when opened in FrameMaker. Of course, I am assuming your read-write file is set up to handle cross-references.
On the other hand, IF you are creating your cross-reference from the structured file by simply inserting a cross-reference, that is NOT as an element, then I do not know what happens. If it is being exported as text, then I am not sure FrameMaker will know what to do with it when you reopen the XML file.
Hope this helps,
Van

Cross references in structured documents

Hi there,
Perhaps someone of you has a tip for me regarding cross references in structured FrameMaker.
The problem we have at the moment:
We were working with FM8 structured. But - as we worked with FM documents most of the times - very often the xml files are not on the latest version.
When we now want to update these documents with FM9 and save them as xml documents, there are lot's of errors that the attribute type is not defined for the element fm-xref.
Perhaps some of you know this error message.
At the moment we do exchange all those cross reference for new ones.
Of course, when we have a xml document which contains the latest status, this is not a problem.
You just open the xml file and save it as FM9 document. No problem with any cross reference...
But what can I do with those FM8 documents?
Would it help to use some application just for fixong the cross references in those (if possible)?
This definitly seems to be an error in FM itself.
Is there perhaps some fix for FM9 I don't know about?
And how about FM10: Will I have the same problems, if we switch to that version?
Regards,
Anna

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

DMS Document structure

Hi Friends,
We are implementing DMS in our organization. Our file storing system is explained below.
1st level - Vendor name (like Nyro / Hydraulics / techno )
2nd level - Project name (like A1 / A2/ A3)
3rd level - Dept. (like Civil / electric/ admin)
4th level - Type (like Drawings / docs / memos)
Can we do thru Document structure or by classification (by creating characteristics / class and attaching to doc. type)
Which one is better way ? If we use document structure can we authorization for each level objects like in 2nd level one person is authorized for A1 another for A2 like way other levels also.
Regards,
Sai Krishna

Hi Sai,
mainly you can work with both ways. The creation of a class which enables your users to classify each document info record and then control the permissions with the suitable authorization objects or by a BADI implementation will work.
Another solution would be to create a document BOM structure in CV11 or with the help of the new browser function in ECC 600 release. For further information on the browser function please see also the following link http://wiki.sdn.sap.com/wiki/display/PLM/NewFunctionalitiesinERP2005.
Additionally I think that EasyDMS could also be a solution to setup this scenario for your user. In the above SDN WIKI area for DMS you will also find a special content part for EasyDMS too.
In the release ECC 600 with EA-PLM extenstion you can use the ACL authorization concept to add individual authorizations for
users to single document info records. This could be useful to allow one user to enter folder A and another to enter only folder B.
I hope that this information could be useful for you.
Best regards,
Christoph

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 Structure (BOM)

Hello all,
In CV12 and CV13 for Document Structures (BOM) there does not seem to be a way to print the BOM contents or to extract it to a file. Is this standard SAP? Is there another transaction available where the content of a BOM can be printed or extracted to an external file.
Thanks,
Bill Pickett

Hi Bill,
for document structures (BOM) I have to inform you that there is no print or export function in the standard. Maybe there could be some modification to achieve this but till now I did not came accross such a possibility.
Best regards,
Christoph

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

ADF FACES : Document structure guidelines ?

Does a paper exists that presents the adf faces globally document structure and the possible and recommended adf faces components hierarchy.
I have seen some time ago something like that for UIX (forget where) ... is it the same one ? does this paper exists in otn ?

I'm looking for a description of the pages structure we may use in adf faces. The tree of element we can use and inside each nodes which other element we can use. Something that will help to design a standard page structure in a whole. Actually we only have elements description and it is difficult to see these elements at a whole and what are the possible combinations of elements and what are the forbidden combination of elements.
I remember i have seen some years ago in a uix document a part where the structure was graphically designed and explained. It was very helpful to understand the structure. I don't remember if this was in a white paper or a reference document.
Hope you understand what i mean
Thanks

Cross Organization SOD Conflict in SAP GRC

Hi,
I have a quick question:
Does SAP GRC allow you to capture cross Organization level value conflict. I just checked the Auth. Object for Org level Company code with $BUKRS under transaction codes in Functions, this shows disabled by default.
Example: If I have access to SU01 in Company Code 1 and access to PFCG in Company Code 2 will this be risk based on SAP standard SOD Rule set.
Your quick response will be appreciated. Thaning you in advance.
Thanks & Regards,
Abhimanu Kumar Singh

Hi
As already stated by Martin, one of the option for handling adtional backup access to users could be through Superuser Privilage management(If GRC has been implemented with your client). This would allow detailed reporting at transaction level for audit purposes.
If GRC is not implemented with your client then any additional access which is resulting in SoD, there has to a proper documentation of temporary access assignment to users(For Audit purpose). Mitigation control should be documented and submitted by the supervisor of the user to the SoD team to ensure proper compliance is in place for the additional access provided to the user.
Thanks.
Anjan

I have Dreamweaver CS5.5 and all of a sudden I can't open it says XML parsing fatel error. Invalid Document Structure What do I do? Thanks

I have Dreamweaver CS5.5 and all of a sudden I can't open it says XML parsing fatel error. Invalid Document Structure What do I do? Thanks

You need to rename the Configuration folder to Configuration_BU.
The folder can be found by following this http://www.dmxzone.com/go/16740/clearing-dreamweaver-s-cache/

Document structure, Document Hierarchy, Document line Item Bom

hi, All
I m confustion in the following,
1.Document structure,
2.Document Hierarchy,
3.In Material bom- DOCUMENT [CS01/2]
We can enter so many document in the above activities.
I m confusion with Document structure and Document in material Bom [CS01/2].
I linked documents in CS02 but Those will shows in DMS but Can't opens. I don't know what is the use creating link in CS02, even though this document not triggers Production order.
[For document structure needs Change number that i know.]
But actual use or application i dont know. Could Explain with Exmple.
Rgds
Ben

hi,
niranjan,
I created a object link for Bom Item [STPO_DOC] and Bom header [STKO_DOC] using T-code CS01. This BOM item, BOM Header triggered in DMS. From DMS I am trying to display cs03, But system wonu2019t allow to display.
And secondly I am trying to link document from DMS to sap object- Material Bom [STOP]
But system wonu2019t allow.
How i can establish link materail bom and dms.
Rgds
Ben

Looking for function module to clear document structure

Hello,
we want to use Easy DMS for quick check-in of documents. Therefore we need a folder (document structure) to move all new documents in this fixed defined folder. Now we want to clear every night this folder. Does anybody know, which function module could I use?
Thanks a lot for any support.
Best regards.
Markus

Hello Iring,
thanks a lot for your answer. BAPI_DOCUMENT_CHANGE2 is a solution, but in this case I have to read everytime all documents. In my case I know already the folder number (document structure) and therefore I'm looking for a function module to give just the folder number to clear, which would be the best way from performance side.
Anyway thanks a lot for your answer.
Regards.
Markus

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?

Document Structure

Dear Experts,
Scenario:
Create document in DMS with status IE In preparation.
Change the document with status Release
Before release of the document we validate that the respective documents are stored in respetive folders.
Documents are stored manually by using CV12.
Some times user stores the document with status IE in the folder which we want to validate as
Only documents with released status should get stored in respective folders?
I could not find any BADI / USER EXIT for this functionality?
Can any body help on this ..
Thanks and Regards
Rane

Dear Kristoffer
Thanks for the reply
Document_storage01 is used for storing Originals.
What I am doing is DIR is being stored in Document structure say XYZ.
So I need to validate at the time of transaction CV12 and not while check in process.
Thanks and regards,
Rane

Cross-Organization Document Structure Standards

Similar Messages

Maybe you are looking for