Document hierarchy

Hi,
Im trying to release a version of a document from CV02n transaction.
But system is giving this below message on click of save.
u201CHierarchy below document contains documents which are not releasedu201D
Current status of the document is in AL.Previous versions of this document is in CN statuses.
The document has a object link,whose status is in OB.
Please let us know,how to overcome this error and release the document from CV02N transaction.
Regards
Keerthi

Hi,
Thank you for the replies.
The previous versions of the parent documents are in CN statuses.
And in my development server,this validation does not occur.
Is there a way to manage this.
Regards
Keerthi

Similar Messages

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

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 migrate document hierarchy from DEV to PROD?

Need some suggestions as to migration of the document hierarchy. The migration wizard is great for migration objects such as portlets, but it's cumbersome to migrate the entire document hierarchy from DEV to PROD as we will have to select all the leaves in the hierarchy to retain the tree. Does any one have the similar experience and have some suggestions? Thanks!

This is wrong forum for such question, you might want to post it here
General EBS Discussion

Enable Document Structure and Document Hierarchy

We have enable the document browser in SPRO, but the folder do not appear in a hierarchy. In other words, I can create a FOL type DIR, but it looks like any other document type. I can not navigate into the folder and add sub folder and documents to it in the Document Browser.
Is there a configuration that we are missing?
Max points to the first correct answer.

Dear Andrew
First of all please note that in SAP DMS, you cannot view Folder structure as you would expect.
If you want to create a Folder in SAP DMS follow these steps :
- First create a DIR using CV01n
- Convert the DIR into Document structure in CV11 giving Doc. type and Document number
- Now the DIR is a Document Structure ( Folder) and add other DIR s into it
- You can also add other Document Structures into this and those will become Sub Folders.
This is a very time cosuming procedure and if u have large requirment of creating Folders and Subfolders, better install SAP Easy DMS
In SAP Easy DMS you can create Folders and Subfolders as in Microsoft Explorer.
You can dowload SAP Easy DMS from http://service.sap.com and install.
SAP Easy DMS is very user friendly tool and requires little training for end users to understand compared to SAP DMS.
Regards
Aby

FormDesigner.exe crashed when I attempt to move an object in the document hierarchy

I'm using LiveCycle Designer ES2 to create a dynamic XML form.
I have a flowed page layout with a series of subforms arranged from top to bottom. The order of the subforms is necessary. When I attempt to move a subform up or down in the Hierarchy panel, the entire application freezes, then crashes. This happens regardless of what type of object is selected, number of selected objects, etc. Can anyone provide some assistance? I've tried rebooting, as well as running the application in comatibility mode with Windows XP (SP3); I have not yet tried uninstalling and reinstalling the application.
I can't attach the pdf as the content is sensitive in nature.
Technical Details:
Running Windows 7 x64 with all updates installed.
LiveCycle Designer ES2 version 8.0.0.2.20101008.1.734229
I have the latest version of CS5.5 Design Premium installed, as well as the latest version of Premier.

I got it figured out. I had a number of actions that pointed to nonexistant objects I had deleted.

How to restrict document types in hierachy

Hi
My scenario is
For DIR of document type A only DIRs of document type B and C should be attached in the document hierarchy. How to restrict the user from attaching other type of documents?
What will be the best solution for this scenario?
Thanks in advance
Prasad K

Hi
Plz
Any inputs on this?
Regards
Prasad

Help: document migration RPM 4.5 to PPM 5.0

Hello,
I am looking for a solution regarding the document migration from RPM 4.5 to PPM 5.0 (document stored in a DMS Sap content server).
Manually I have no problem for creating documents in PPM (config ok) but given the fact that I have a large number of document I want to do this migration automatically.
I choose the option to do that by creating an ABAP program... but by this way I have big issues. I try to do that by calling method CREATE_DOC_IN_FOL from /RPM/CL_UI_DOC_LOGIC class but I have a strange return code... :-(
--> at this point, I think that is impossible to use this method to do what I want...
Do someone face with similar questions ?
Is there another way to do this document migration ?
Already thank's...

Hello Ravi,
I want to migrate pdf documents stored in a DMS.
I use KPRO customizing to define a new content repository. (the old one as "DMS" as STORAGE_CATEGORY entity attribute of the default content model but for PPM the value has to be set to "CFF")
In our migration RPM projects are copied in new PPM project. So I want to link to this new projects the documents of the old project... in another content repository.
In my investigation I tried to insert my code "call method CREATE_DOC_IN_FOL" in a SAP method called when a project is modified (IF_EX_RPM_PROJ_CUST_FIELDS~ATTRIBUTE_MODIFY)... and there, my coding works !
... but for sure I don't want to insert my coding there given the fact that I have a huge amount of documents.
So, a this point, I'm looking forward trying to reproduce the same context as in this "exit" which is inside the portal.
My coding that doesn't works looks like that :
- retrieve project item (table /RPM/ITEM_D)
- load object managers
lr_rpm_obj_manager = cl_rpm_obj_manager=>get_instance( ).
lr_ppm_obj_manager = /rpm/cl_obj_manager=>get_instance( ).
   CALL METHOD lr_rpm_obj_manager->load_projects
-   CALL METHOD LR_DOC_LOG->GET_DOCUMENTS_FOR_BASEOBJ (get document hierarchy... it works / this is only to test the object)
-   lr_doc_log->create_doc_in_fol (--> this doesn't works)

ISO Document in DMS

Dear Sir
I have to attached my ISO document in DMs with hierarch level
Apex document>Quality manual>Departmet Manual>format in this manner i want to maintain my document
Awaiting foe your valuable answer.
regards
kunal

Dear Kunal,
first of all it is necessary to create three document info records. This can be done in transaction CV01N. For storing originals I would recommend you to choose a document type which uses the KPRO storage concept. You can search for such a document type in transaction DC10 and check which type has set the flag 'Use KPRO'.
Back to CV01N. At the 'Document Data' screen you can add original files by using the 'Create' button at the bottom of the screen. This button looks like a white sheet of paper.
After you entered the document file path and choose a suitable workstation application the original file will be added to the document info record. If possible you can also add all three original also to one document info record if you store them in a KPRO storage category.
Otherwise you have to create one document info record per original file. If you have created all three document info records, you can go to transaction CV11 to create a document BOM. In transaction CV11 you have to choose one document info record which should be the header of this BOM. On the following screen you can add the other two document info records as items. This way a document BOM will be created.
In case you want to create a document hierarchy which is slightly different, you also need three document info records. But then you do enter transaction CV02N. In transaction CV02N you will find an area called 'superior document' on the first tab. Here you can enter one document number, type, part and version. If you enter a document here you create a hierarchy like
Superior document info record
> sub-document info record
And this can be done for each involved document info record. But there can be always only one superior document for one document info record.
I hope this information could be useful for achieving the desired behavior.
Best regards,
Christoph

How do I clear the recent documents screen on the android application when the clear icon is no longer visible?

I have uninstalled and reinstalled the software but the clear recent documents icon is no longer visible as formerly experienced.

Hi,
The 'Clear Recents' button which was provided in previous releases only *cleared* the Recent list and did not delete the files. The files stayed in your document hierarchy. This button has been removed in the latest release. For deleting the files, you can go to the Documents/Acrobat.com tab and delete the files individually. However, please note that the files will be permanently deleted from your device. Please let us know if this is not a viable option for you. We would like to hear more about your use case.
Thanks,
Mehwish

Document deletion - MCDOKDEL

Hello Friends,
I have a problem with document deletion in SAP DMS.
Documents were marked with deletion indicator which i deleted with report MCDOKDEL. These documents are no longer available in the system (no result with CV03N). Document hierarchy was maintained for these docuemnts.
These documents are still visible in document hierarchy (with decription deleted) under superior document. I want to permanently remove these document records from the system. Please help.
Regards,
Rohit

Hi Rohit,
The activities to delete the doucment are all correct. Kindly check in the transaction SE38 as soon as when you Enter
MCDOKDEL, here you can find the system gives three options as Document Type, Test Mode, and Execute Checks. When u want
to delete the document from the system then u should not mark for TEST MODE option.
After doing this activity kind now check the Hierrarchy u will find only one document. so kindly, DONOT MARK "x" IN THE
TEST MODE.
hope this will help your query
Regards
Kannan

How to view the Form Fields in Process data model?

Hi all,
I have made a form in LC Designer containing some name,ID and other generic details.Is there a way by which i can see those nodes in Proces data model when i load that document?.As of now it shows only attribute as Object. Can't I access those fields like name, id etc thru model directly.??

You have to define an XML Schema for the form and bind the form fields to the XML Schema. Additionally, embedding the XML Schema in the form makes life easier.
Given an XML Schema you will be able to navigate through the document hierarchy and access form fields in the XPath navigator.
If you would like a sample form, just send me a request at [email protected]

How to parse XML to Java object... please help really stuck

Thank you for reading this email...
If I have a **DTD** like:
<!ELEMENT person (name, age)>
<!ATTLIST person
     id ID #REQUIRED
>
<!ELEMENT name ((family, given) | (given, family))>
<!ELEMENT age (#PCDATA)>
<!ELEMENT family (#PCDATA)>
<!ELEMENT given (#PCDATA)>
the **XML** like:
<person id="a1">
<name>
     <family> Yoshi </family>
     <given> Samurai </given>
</name>
<age> 21 </age>
</person>
**** Could you help me to write a simple parser to parse my DTD and XML to Java object, and how can I use those objects... sorry if the problem is too basic, I am a beginner and very stuck... I am very confuse with SAXParserFactory, SAXParser, ParserAdapter and DOM has its own Factory and Parser, so confuse...
Thank you for your help, Yo

Hi, Yo,
Thank you very much for your help. And I Wish you are there...I'm. And I plan to stay - It's sunny and warm here in Honolulu and the waves are up :)
A bit more question for dear people:
In the notes, it's mainly focus on JAXB,
1. Is that mean JAXB is most popular parser for
parsing XML into Java object? With me, definitely. There are essentially 3 technologies that allow you to parse XML documents:
1) "Callbacks" (e.g. SAX in JAXP): You write a class that overrides 3 methods that will be called i) whenever the parser encounters a start tag, ii) an end tag, or iii) PCDATA. Drawback: You have to figure out where the heck in the document hierarchy you are when such a callback happens, because the same method is called on EACH start tag and similarly for the end tag and the PCDATA. You have to create the objects and put them into your own data structure - it's very tedious, but you have complete control. (Well, more or less.)
2) "Tree" (e.g. DOM in JAXP, or it's better cousin JDOM): You call a parser that in one swoop creates an entire hierarchy that corresponds to the XML document. You don't get called on each tag as with SAX, you just get the root of the resulting tree. Drawback: All the nodes in the tree have the same type! You probably want to know which tags are in the document, don't you? Well, you'll have to traverse the tree and ask each node: What tag do you represent? And what are your attributes? (You get only strings in response even though your attributes often represent numbers.) Unless you want to display the tree - that's a nice application, you can do it as a tree model for JTree -, or otherwise don't care about the individual tags, DOM is not of much help, because you have to keep track where in the tree you are while you traverse it.
3) Enter JAXB (or Castor, or ...): You give it a grammar of the XML documents you want to parse, or "unmarshall" as the fashion dictates to call it. (Actually the name isn't that bad, because "parsing" focuses on the input text while "unmarshalling" focuses on the objects you get, even though I'd reason that it should be marshalling that converts into objects and unmarshalling that converts objects to something else, and not vice versa but that's just my opinion.) The JAXB compiler creates a bunch of source files each with one (or now more) class(es) (and now interfaces) that correspond to the elements/tags of your grammar. (Now "compiler" is a true jevel of a misnomer, try to explain to students that after they run the "compiler", they still need to compile the sources the "compiler" generated with the real Java compiler!). Ok, you've got these sources compiled. Now you call one single method, unmarshall() and as a result you get the root node of the hierarchy that corresponds to the XML document. Sounds like DOM, but it's much better - the objects in the resulting tree don't have all the same type, but their type depends on the tag they represent. E.g if there is the tag <ball-game> then there will be an object of type myPackage.BallGame in your data structure. It gets better, if there is <score> inside <ball-game> and you have an object ballGame (of type BallGame) that you can simply call ballGame.getScore() and you get an object of type myPackage.Score. In other words, the child tags become properties of the parent object. Even better, the attributes become properties, too, so as far as your program is concerned there is no difference whether the property value was originally a tag or an attribute. On top of that, you can tell in your schema that the property has an int value - or another primitive type (that's like that in 1.0, in the early release you'll have to do it in the additional xjs file). So this is a very natural way to explore the data structure of the XML document. Of course there are drawbacks, but they are minor: daunting complexity and, as a consequence, very steep learning curve, documentation that leaves much to reader's phantasy - read trial and error - (the user's guide is too simplicistic and the examples too primitive, e.g. they don't even tell you how to make a schema where a tag has only attributes) and reference manual that has ~200 pages full of technicalities and you have to look with magnifying glas for the really usefull stuff, huge number of generated classes, some of which you may not need at all (and in 1.0 the number has doubled because each class has an accompanying interface), etc., etc. But overall, all that pales compared to the drastically improved efficiency of the programmer's efforts, i.e. your time. The time you'll spend learning the intricacies is well spent, you'll learn it once and then it will shorten your programming time all the time you use it. It's like C and Java, Java is order of magnitude more complex, but you'd probably never be sorry you gave up C.
Of course the above essay leaves out lots and lots of detail, but I think that it touches the most important points.
A word about JAXB 1.0 vs. Early Release (EA) version. If you have time, definitively learn 1.0, they are quite different and the main advantage is that the schema combines all the info that you had to formulate in the DTD and in the xjs file when using the EA version. I suggested EA was because you had a DTD already, but in retrospect, you better start from scratch with 1.0. The concepts in 1.0 are here to stay and once your surmounted the learning curve, you'll be glad that you don't have to switch concepts.
When parser job is done,
what kind of Java Object we will get? (String,
InputStream or ...)See above, typically it's an object whose type is defined as a class (and interface in 1.0) within the sources that JABX generates. Or it can be a String or one of the primitive types - you tell the "compiler" in the schema (xjs file in EA) what you want!
2. If we want to use JAXB, we have to contain a
XJS-file? Something like:In EA, yes. In 1.0 no - it's all in the schema.
I am very new to XML, is there any simpler way to get
around them? It has already take me 4 days to find a
simple parser which give it XML and DTD, then return
to me Java objects ... I mean if that kind of parser
exists....It'll take you probably magnitude longer that that to get really familiar with JAXB, but believe me it's worth it. You'll save countless days if not weeks once you'll start developing serious software with it. How long did it take you to learn Java and it's main APIs? You'll either invest the time learning how to use the software others have written, or you invest it writing it yourself. I'll take the former any time. But it's only my opinion...
Jan

Trying to understand Javascript collection numbers

I found this bit in the Adobe introduction to scripting:
JS collection numbers are static; they don’t shift when you add a new object to the collection. Object
numbering in JS indicates the order in which the objects were added to the collection. Because the
first object you added was assigned the number 0, the next object you add to the collection is number
1; if you add a third object, it is number 2. For example, when you add a document, the document
automatically contains a layer. The layer’s index is [0]. If you add a layer, the new layer’s index is [1]; if
you add a second layer, its index is [2]. If you drag layer [2] to the bottom position in the Layers palette,
it still has index [2].
If I understand this correctly the original layer is always layer[0], however when I try this slightly modified script from later in the guide:
var myDoc = app.activeDocument
var myLayerCount = 4
for(var myCounter = 0; myCounter < myLayerCount; myCounter++)
{var myLayer = myDoc.layers[myCounter]
myLayer.visible = false}
the top 4 layers are set to invisible, while I was expecting it to be the bottom 4.
What am I missing?

If your document has no groups, then doc.layers and doc.artLayers will be the same. But if you groups then doc.layers will give all
art layers in the doc root
the groups you have an doc root
any art layers and sub groups in the root level groups.
I.e. doc.layers will return the full document hierarchy as a flat list, but the order that list is not guaranteed to be something (as far as I know). Most likely order is always the visual top to bottom. I.e. item 0 is always the visually topmost element.
Also note that if you use doc.layers, you need to check if the item is a layer or a group (=folder=layerset). That's why you also have the collections .artLayers and .layerSets that give just layers and groups respectfully.

Document hierarchy

Similar Messages

Maybe you are looking for