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
Similar Messages
-
WebService for Document Structure (BOM)
Hi,
can someone tell me if there is a Webservices for DocumentStructures?
Thanks a lot, BiagioHello,
you can easily create a webservice on your own from within the function builder SE37.
Open BAPI_DOCUMENT_GETSTRUCTURE and then
>Hilfsmittel >weitere Hilfsmittel >Webservice erzeugen >aus dem Funktionsbaustein
kind regards
Daniel Kasimirowicz -
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
Benhi,
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 -
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 KrishnaHi 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 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
suryaSee 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 -
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 FleckHi 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 -
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 WhiteleyInteresting 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 -
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 -
Changes documents for BOM and Routing
How Can I find the change documents for a BOM and routing?
Change Documents For BOM
CS80 - Material BOM
CV80 - Document Structure
IB80 - Equipment BOM
IB81 - Functional Location BOM
CS81 - Standard BOM
CS82 - Order BOM
CS83 - WBS BOM
Change Documents for Routings
CA60 - Task List Changes
CA61 - Routing
CA62 - Reference Operation Set
CA63 - Rate Routing
CA64 - Reference Rate Routing
Hope the above may help you. -
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 PantHi 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. -
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/ -
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.
MarkusHello 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?
-
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
RaneDear 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 -
DOCUMENT STRUCTURE INCONSISTENT ERROR
Hi all,
We are on SRM 5.0 ECS
When w etry to create a PO and click on the CHECK button,we get the foll error:
DOCUMENT STRUCTURE INCONSISTENTYour description is too generic - try to create yourself an example and hold it - no save. Then debug the transfer BBPPROCDOCTRANSFER. You should figure out more than this very general error description.
Richard
Maybe you are looking for
-
Events in table maintenance generator 01
Hi all, I have an urgent requirement regarding the events in table maintenance generator.The requirement is i have a qty field in table i want to change the existing value it should allow only a lesser value.How to use TOTAL and EXTRACT struct
-
How do i fix this install error. Very fustrating.
-
Search Criteria With in block in Essbase.
Hello everyone. could anyone tell me which searching technique is use with in a block in a essbase to search data cell or entire procedure to search a data cell with in a block in essbase ?
-
Late 2009 MacPro Grainy Resolution
My dad bought a used late 2009 macpro and it has worked great until the last couple of days. The screen has all of a sudden turned grainy and the color is off. At times it almost looks like the screen is shaking. I have played around with the display
-
i am trying to copy and paste a button from one menu to the next. i have about 10 menus. the look of the button comes over but not its attributes in terms of color, hightlight, etc. this makes no sense to me. can someone help?