FAQ - Documents
This Page contains the most frequently asked questions about documents in the Implementation area inside Solution Manager.
CONTENT VALID FOR SAP SOLUTION MANAGER 7.1
- When we link to a solution manager document, how do we determine if the document is a link or the original document?
- Why does it takes so long to search for source documents when trying to link a document inside SOLAR01/SOLAR02 transactions?
- Why the document extension is lost when I check out a document in a project, edit it and then check in the document again?
When we link to a solution manager document, how do we determine if the document is a link or the original document?
A: A document have a LOIO and a PHIO value. The PHIO is the value that points to the Physical document in it's original folder. The LOIO is the dinamic reference of a document that points to the PHIO, It is the Logical Information of the Object.
When you add a document as link, you're assigning a reference to this document to the project structure, in other words, you're creating an assignment for this document.
If you delete the assignment where the document was first created, this document will still exist physically because of it's PHIO value.
So basically, it makes no difference where the document was firstly created if the point is just to manage it after adding as link.
A possibility to see where the document was first created is to check in it's attributes, it's folder. Depending on the name of the folder, you'll know where it was first created and it is stored physically, according to the information on the wiki page for "Documents in Solar01 and Solar02" in the following link, session "STORING DOCUMENTS IN KNOWLEDGE WAREHOUSE FOLDERS" :
Another option is to select the document row and click on the button "where used". The system will list all the places that have an assignment pointing to the same PHIO, and you'll be able to check in the "history" button for the structures that have each assignment when this entry was added and compare the dates.
All documents will be treated as assignment in the projects, since every assignment of the same document just points to the physical one. It really makes no difference in which project it was first created. One way you could use to see if a document was first created in the structure you're looking or not is just comparing the history tab in the document attributes and the history button in the structure. If the date of creation of the document is older than the date it was added in the structure, then it was created originally elsewhere. But please keep in mind that this assignment will be just equal to the first one.
Why does it takes so long to search for source documents when trying to link a document inside SOLAR01/SOLAR02 transactions?
A: The search function used when linking is the same search function in the menu “Business Blueprint/Configuration -> Find Document…”, it is directly affected by the amount of documents in your project folder(in case you have specified a project). This search will include also the unused documents, what sometimes is not taken into account.(to understand how the documents became unused and how to delete this documents, please check the wiki page for “Documents in Solar01 and Solar02” in the following link, sessions “Assignment of the documents” and “STORING DOCUMENTS IN KNOWLEDGE WAREHOUSE FOLDERS” to understand which documents are stored in the project’s folder: http://wiki.sdn.sap.com/wiki/display/SM/Documents+in+Solar01+and+Solar02 ). Additionaly, it is not recommended to search for a blank selection because the search function will search in the system for almost every document and this will certainly take some time.
Why my documents are not being included in the generated Business Blueprint document?
A: To have your document inclued in the generated business blueprint document, in this document’s attributes, the flag “Business Blueprint-Relevant” must be checked. It is important to have in mind that the documents under "Gen. Documentation" tab can only be edited in the original template project, so this flag should be edited in the template project and then the document should be updated in the implementation project.
How can I check the PHIO and LOIO of a document?
A: The LOIO and PHIO can be checked by the following way:
Select the row of the document in the structre that it is assigned (SOLAR01/SOLAR02) and in the transaction box type in "doc_info", then press enter. It'll open a window with some attributes of the document, The "Object ID" field is the LOIO(Logical Information of the Object) of the document.
Then in SE16 transaction you'll be able to check the table SA01PHIO which is the table that maintain the PHIOs. Put the value you saw in the "Object ID" field before in the field LOIO and press the "execute" button.
Then you'll see the PHIO entry for this LOIO.
What is the "Link" tab inside the document attributes for?
A: The Link tab in the attributes of the documents basically exists to link other existing document that are connected in any context to this document. You're also able to create new documents or copy, so it'll be assigned there and stored. This is just a matter of how you prefer to organize your documents related in some aspect.
Why the document extension is lost when I check out a document in a project, edit it and then check in the document again?
A: This is usually very simple, You just need to set in the user's computer the following option:
Open any windows folder, navigate through "tools -> Folder Options ->
Uncheck the option Hide extensions for known file types.
Then after that, it should work correctly.
What is stored in the table SACONT01 and how can I shrink it?
A: This table contains content of documents, e.g. word documents, excel files, pdf, ...
The usual way to reduce the size of these tables is move the content to an external content server.
In transaction OCA0 you can change the customizing of a content repository and assign an external content server instead of the currently maintained DB table.
Please see SAP note 546685
Also regarding the SACONT01 size, please have a look at the following link:
and into the notes:
- 1360988 Error in the program SOLMAN_DOCU_VERSION_ARCHIVE
- 1360436 Error in the program SOLMAN_DOCU_VERSION_DEL
- 923203 Deleting unused documents from the Solution Manager
The reports mentioned there can help to reduce the data.