Professional Documents
Culture Documents
For TST, we used an internal number range with a prefix, but also allowed the possibility
of an external number range. It will depend on the requirements what to use here. We
may want to s
Before the documents are stored in the archive (iXOS), they are typically found in the
user’s front-end computer. The entry ‘External DMS’ is used to control this.
We created Data Carrier type ‘ED’, and with this, data carrires ‘ABCD’ and ABCD2’.
For reasons described below, only ABCD is the only functional one.
The data carrier ‘BA’ defined above must point to a ‘Content Repository’ with the same
name. Content Repository ‘BA’ was configured by Ron Parker.
The parameters of the content repository are defined such that a SAP knows the
address of the storage system, uses HTTP protocol for communication, and knows
that this is for DMS purposes. The use of HTTP allows us to use secure HTTP.
Security is achieved through certificates installed in the SAP and content server.
The content server ‘Yucca’ is the machine where the iXOS application runs.
Another Content Repository is defined for storing documents in the SAP database.
This is not the method to be used beyond prototyping, but has been useful for comparison
between storing in iXOS and in SAP.
Storage categories are used to group Document Areas that use the same Content
Repository (for our purposes, Document area DMS, content repository BA).
Only one entry is needed here, so far defined as DMS_C1_ST. Other entries were found
in the table as delivered.
Each DMS document can contain a number of files. To these files, information can be
attached to facilitate their retrieval. Mostly, when a file is stored, the user has to choose
an application that can open the file later.
The following application/file-types are relevant for EHS:
GIF, JPG, PDF, TXT, WRD, XLS. They will be later downloaded in the users frontend
computers with their corresponding extensions. Moreover, by checking ‘NoRename’, the
files will be downloaded with the same name as they are found in the archive (overriding
any file in the same name).
1. Even though it was initially thought that we will connect to iXOS via the Archivelink
interface, we didn’t have to in the end. Therefore, no customizing under ‘Basis
components’ -> Basis Services -> SAP Archivelink was necessary.
2. By logging into yucca and using a tool called iXOS administration, we can see the
archive ‘BA’ defined in iXOS, and confirm that it is the receiver of the DMS documents.
Below is the a document called ‘SALMA1.DOC’ stored in the iXOS repository, under
archive BA. It is given an internal document number by SAP, so that SAP knows how to
retrieve this document from the DMS system.