Is posssible to create Document structure in KM ?

Hi All,
Similar to DMS, Is it possible to Create a Document Structure in KM?. or Is it possible to link various documents ?
Thanks
Badri

Hi Jenn,
As such Km doesn't allow document structure. The only possibilities is to have an iview of DMS or use the DMS connector ( This is based on the Variants in the search of documents). Both were not much of help.
- As of records management we were able to get the repositories into the KM. We couldn't use KM for records management because of the regulations as well as KM is meant for sharing the information where as records management has very specific conditions to satisfy.
How ever we are thinking of using the Public sector Records management and intergrate within KM.
Hope this helps
Cheers
Badri

Similar Messages

How to create Document Structure for existing project in Solution Manager

Hi gurus
We have all the project document saved using Solution manager . we have ended with Phase1.
We are starting Phase2 and they are asking me to creat different folder as Phase to in existing project and store all the Documents
Can any one please tell me how to create New folder and store the documents in Existing project
Point will given for helpfull Answer
Thanks
Bhaskar

Hi Bhaskar,
Assuming you have full authorisations, the procedure is simple.
Please go SOLAR_PROJECT_ADMIN transaction.
From the menu please select Project -> Copy
In the ensuing screen, key in your desired project name, scroll through the other checkboxes to see if you are happy with the default choices; if not, take corrective actions.
In the last set of radi buttons "Desired behaviour at later version comparison", the default choice (2nd entry there - Adjust target project to the original of the source project) is fine.
From your scenario, since you do not have a Template -> Implementation Project functionality and instead are copying from one Implementation to the other, this radio button is of little consequence.
Execute the process.
In the window that comes up, please choose Local Object, assuming that you do not want to capture the whole contents into a 'Transport'. This is more required if you are aiming to copy the project from one SolMan instance to another.
It would give an information message "Generating in batch job (Name ......)
In a few minutes, you'd receive an intimation of the Project being copied.
That's pretty much about it. Have a check on the newly created project in SOLAR01.
Please let me know if you have any doubts.
Best regards,
Srini

Create a structure type at runtime

Hi friends,
is it possible to create a local structure type dynamically(at run time).My situation is as follows :
The user gives a period of time - for Example from "05.03.2009" to "04.03.2010"
Depending on the number of months between the period of time
I have to create a structure with field names as follows:
I have calculated the number of months between a period of time and the field name also(Mar-09.Apr-09 extra) using function modules.
The question that is running around my head now is how to create the local structure type at run time with the field names.
TYPES: BEGIN of st_testStruct
     matnr type string,
     land type string,
     "The above to fields in the structure will always be there but depending on the period of time.
     the following fields have to created dynamically.
     Mar-09 type string,     " as the time period starts from "05.03.2009"
     apr-09 type string,
     may-09 type string,
     ........so on
     dec-09 type string,
     jan-10 type string,
     feb-10 type string,
     mar-10 type string,
end of st_testStruct.
depending on the time range the number of field could be more or less in the structure type.Thats why I want to create it dynamically.
Any sample code for this purpose is useful.....
Thanks
P

ABAP RTTS is what you're looking for - check out this [Wiki page|http://wiki.sdn.sap.com/wiki/display/ABAP/RuntimeTypeServices+%28RTTS%29], which should answer your questions... (here's the link to the [ABAP online docu|http://help.sap.com/abapdocu_70/en/ABENRTTI.htm])
Cheers, harald
p.s.: Don't use the hyphen in your field names. This was a bad practice that was used in some old releases. The problem is that fields in a structure are addressed with a hyphen, e.g. like mara-matnr.

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, 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

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

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 INCONSISTENT

Your 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

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 Solution

Hi all
I'm reading about Document Structure and I have a question.
I wanna create a Structure (1) for user and they only base on this structure to create new Document Structure themself
I mean Structure (1) is something like the process and user just base on this...
Can I create this ? And where can I create this in DMS.
For example:
I have a Structure (1) [not Document Structure]
A (1)
|
|____|B (2)
|____|C (2)
|____|_________D (3)
A,B,C,D are Document type
And when user create Document DIR they have to base on this Structure (1)
I try to make my problem clearly with everyone... But so hard to get it. If you don't understand me you can ask for more information.
Regard
An NLP
Edited by: An NLP on Mar 18, 2010 3:16 AM
Edited by: An NLP on Mar 18, 2010 3:17 AM
Edited by: An NLP on Mar 18, 2010 3:18 AM

Hi Amaresh Makal
Thanks for your caring my problem. I use another example and hope you can understand what I want.
A,B,C,D are Document Types.
And have a rule: A must have B,C,D
I mean
When users create a document in Document Type A, they have to create the documents in other Document Types: B,C,D.
And document in A is only released when the documents in B,C,D are released.
I want a structure (like Document Structure) for Document Type and it is used for all of documents in that Document Type.You should notice that I'm talking about Document Type not Document
Maybe, It's impossible to do because I can't find out anything to link the Document Types in DMS.
Finally, If it cannot be done and do you think SAP DMS need a system like that ?
Regards
An NLP

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

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

Correction Invoice and "invalid document structure" problem

Hello!
Can anybody explain what properties are obligatory for correction invoices? I'm trying to add() one and it always say -5002: invalid document structure.
In the CSI1 table I see linenum has to be unique, every baseline is twice. Do I make any stupid mistake? If so - where? What's wrong? Something is ommitted?...
                                                                                Thanks in advance!
                                                                                This is a snippet (two loops are unnecessary, I was looking for other ways). I'm trying just to zero the invoice. Should quantity in was lines be negative? It does not matter - everytime -5002...
     @Test
     public void testSAPCorrectionInvoice() throws SBOCOMException {
          ICompany company = sapConnector.getCompany();
          // Integer srcDocEntry = 6457;
          Integer srcDocEntry = 7084;// this one has no batches
          logger.debug("Creating correction to: " + srcDocEntry);
          // source doc
          IDocuments srcDoc = SBOCOMUtil.getDocuments(company,
                    SBOCOMConstants.BoObjectTypes_Document_oInvoices, srcDocEntry);
          logger.debug("srcDoc: " + srcDoc.getDocObjectCode() + ", "
                    + srcDoc.getDocNum());
          IDocuments sapDoc = SBOCOMUtil.newDocuments(company,
                    SBOCOMConstants.BoObjectTypes_Document_oCorrectionInvoice);
          // header:
          sapDoc.setHandWritten(SBOCOMConstants.BoYesNoEnum_tNO);
          sapDoc.setSeries(317);
          sapDoc.setDocType(SBOCOMConstants.BoDocumentTypes_dDocument_Items);
          sapDoc.setCardCode(srcDoc.getCardCode());
          sapDoc.setCardName(srcDoc.getCardName());
          sapDoc.setAddress(srcDoc.getAddress());
          String federalTaxID = srcDoc.getFederalTaxID();
          if (federalTaxID.length() > 0)
               sapDoc.setFederalTaxID(federalTaxID);
          sapDoc.setDocDate(new Date());
          sapDoc.setDocDueDate(new Date());
          sapDoc.setSalesPersonCode(srcDoc.getSalesPersonCode());
          sapDoc.setDocCurrency(srcDoc.getDocCurrency());
          sapDoc.setPaymentGroupCode(srcDoc.getPaymentGroupCode());
          sapDoc.setTransportationCode(srcDoc.getTransportationCode());
          sapDoc.setContactPersonCode(srcDoc.getContactPersonCode());
          // sapDoc.setDiscountPercent(0.0);
          sapDoc.setComments("zwrot towaru");
          // sapDoc.setDocTotal(0.0);
          sapDoc.setVatDate(srcDoc.getVatDate());
          // items
          IDocument_Lines lines = sapDoc.getLines();
          int lineno = 0;
          IDocument_Lines srcLines = srcDoc.getLines();
          for (int i = 0; i < srcLines.getCount(); i++) {
               srcLines.setCurrentLine(i);
               logger.debug("line " + i + ", item: " + srcLines.getItemCode());
               if (lineno > 0)
                    lines.add();
               lines.setCurrentLine(lineno++);
               lines.setItemCode(srcLines.getItemCode());
               lines.setItemDescription(srcLines.getItemDescription());
               lines.setWarehouseCode(srcLines.getWarehouseCode());
               lines.setPrice(srcLines.getPrice());
               lines.setDiscountPercent(srcLines.getDiscountPercent());
               lines.setTaxCode(srcLines.getTaxCode());
               lines.setBaseEntry(srcDocEntry);
               lines.setBaseType(srcDoc.getDocObjectCode());
               lines.setBaseLine(i);
               lines.setVatGroup(srcLines.getVatGroup());
               lines
                         .setCorrectionInvoiceItem(SBOCOMConstants.BoCorInvItemStatus_ciis_Was);
               double quantity_was = srcLines.getQuantity();
               lines.setQuantity(quantity_was);
          for (int i = 0; i < srcLines.getCount(); i++) {
               srcLines.setCurrentLine(i);
               logger.debug("line " + i + ", item: " + srcLines.getItemCode());
               if (lineno > 0)
                    lines.add();
               lines.setCurrentLine(lineno++);
               double quantity_diff = 0;
               lines.setItemCode(srcLines.getItemCode());
               lines.setWarehouseCode(srcLines.getWarehouseCode());
               lines.setPrice(srcLines.getPrice());
               lines.setDiscountPercent(srcLines.getDiscountPercent());
               lines.setTaxCode(srcLines.getTaxCode());
               lines.setBaseEntry(srcDocEntry);
               lines.setBaseType(srcDoc.getDocObjectCode());
               lines.setBaseLine(i);
               lines.setVatGroup(srcLines.getVatGroup());
               lines
                         .setCorrectionInvoiceItem(SBOCOMConstants.BoCorInvItemStatus_ciis_ShouldBe);
               double quantity_was = srcLines.getQuantity();
               double quantity_is = 0; //quantity_was - quantity_diff;
               lines.setQuantity(quantity_is);
          int result = sapDoc.add();
          String info = company.getLastErrorDescription();
          logger.debug("res = " + result + ", info: " + info);
          if (result != 0)
               throw new EBladKorektyNrPartii(
                         "Cannot create document: " + info);
Edited by: WodzGalopujacySkleroz on Jul 4, 2011 5:03 PM

Hello,
Maybe it's an old thread, and you might have the solution or workaround for this. Nonetheless i try to answer, it might be useful for those trying to find a solution for the same problem.
The two loops are necessary indeed. DI API expects only this structure: Start with all the "ShouldBe" lines, and follow them with all the "Was" lines. So your code is almost good, but you should have swap the two loops with each other.

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

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

Is posssible to create Document structure in KM ?

Similar Messages

Maybe you are looking for