A hyperlink links a document of any document class to a second document, without physically including the document in the second document. Both documents must have been created in a format that supports hyperlinks, for example, HTML, Microsoft Word, or Microsoft Excel.
A distinction is made between the following document stores:
Stored in knowledge management (see Migration of Documents into the CM Repository)
Stored in the BW System (SKWF) and Accessed using the BW Document Repository Manager
Stored in the BW system (SKWF) and accessed using the SAP NetWeaver Application Server (ABAP)
Stored in the BW system (SKWF) and accessed using the BW Document Repository Manager
The following types of link are possible:
You need the following information if you want to create a link from outside of the BW system to a document belonging to a BW object:
Portal server
Port
Name of the document that you want to link to
From this information, you build the URL as follows:
Document Class |
URL |
---|---|
Metadata |
http://<Portal Server>:<Port>/irj/go/km/docs/<BW Document Repository Prefix>/MetaData/ <Object Type>/ <Object Name>/ <Names des Dokumentes> |
Master Data |
http://<Portal Server>:<Port>/irj/go/km/docs/BW Document Repository Prefix/MasterData/ <Characteristic Name>/ <Characteristic Value>/ <DOCUMENT> |
InfoProvider data |
http://<Portal Server>:<Port>/irj/go/km/docs/BW Document Repository Prefix/InfoProviderData/... Documents that are assigned to InfoProviders and queries: /BW Document Repository Prefix/InfoProviderData/ <InfoProvider>/ <Query>/ <Name of Document> Documents that are only assigned to InfoProviders (cross query): /BW Document Repository Prefix/InfoProviderData/ <InfoProvider>/ <Name of Document> Documents that are used across InfoProviders: /BW Document Repository Prefix/InfoProviderData/ <Name of Document> |
The <BW Document Repository Prefix> placeholder includes the prefix that is configured for the BW Document Repository Manager (for example /bw_documents).
For more information about this type of storage, access and the significance of the <BW Documents Prefix> placeholder, see BW Document Repository Manager.
Stored in BW System (SKWF) and Accessed Using SAP NetWeaver Application Server (ABAP)
The following types of link are possible:
You need the following information if you want to create a link from outside of the BW system to a document belonging to a BW object:
Server (meaning the SAP NetWeaver Application Server, not the ITS)
Port
Name of the document that you want to link to
From this information, you build the URL as follows:
Document Class |
URL |
---|---|
Metadata |
http://<Server>:<Port>/SAP/BW/DOC/META/FLDMETA/<Document Name> |
Master Data |
http://<Server>:<Port>/SAP/BW/DOC/MAST/FLDMAST/<Document Name> |
InfoProvider data |
http://<Server>:<Port>/SAP/BW/DOC/TRAN/FLDTRAN/<Document Name> |
Make sure that the name of the document is unique within the document class.
You use relative links to link documents that belong to the same document class.
To link to document 02, add the HTML code to document 01, using the following template:
<a href = "Name of document 02"> Text </a>
You can enhance the HTML code to link documents that do not belong to the same document class.
For example, if you want to set a link from document 01 (belonging to the META document class) to document 02 (belonging to the TRAN document class), add the HTML code to document 01 as follows:
<a href = "../../TRAN/FLDTRAN/"Name of document 02"> Text </a>
Stored in Knowledge Management (Migrated Documents)
The following types of link are possible:
You need the following information if you want to create a link from outside of the BW system to a document belonging to a BW object:
Portal server
Port
Name of the document that you want to link to
From this information, you build the URL as follows:
Document Class |
URL |
---|---|
Metadata |
http://<Portal Server>:<Port>/irj/go/km/docs/<BW CM Repository Prefix>/<System Alias>/MetaData/<Object Type>/<Object Name>/<Name of Document> We recommend that you only migrate metadata documents if the metadata is not going to be transported. |
Master Data |
http://<Portal Server>:<Port>/irj/go/km/docs/<BW CM Repository Prefix>/<System Alias>/MasterData/ <Characteristic Name>/ <Characteristic Value>/ <Name of Document> |
InfoProvider data |
http://<Portal Server>:<Port>/irj/go/km/docs/<BW CM Repository Prefix>/<System Alias>/InfoProviderData/... Documents that are assigned to InfoProviders and queries: /<BW CM Repository Prefix>/<System Alias>/InfoProviderData/ <InfoProvider>/ <Query>/ <Name of Document> Documents that are only assigned to InfoProviders (cross query): /<BW CM Repository Prefix>/<System Alias>/InfoProviderData/ <InfoProvider>/ <Name of Document> Documents that are used across InfoProviders: /<BW CM Repository Prefix>/<System Alias>/InfoProviderData/ <Name of Document> |
The <BW CM Repository Prefix> placeholder includes the prefix that is configured for the BW Document Repository Manager (for example, /bw_documents).
The <System Alias> placeholder corresponds to the system alias that is maintained for the system object in the BW system.
For more information about this type of storage, access and the significance of placeholders, see Migration of Documents into the CM Repository.