tia® Document Router uses the standard SAP ArchiveLink protocol in order to communicate with any ArchiveLink certified DMS. To enable the SAP ArchiveLink functionality, KGS provides an SAP transport, which has to be imported into the connected SAP systems.

Interfaces

An interface describes the type of input data tia® Document Router receives. The following types of interfaces are supported by tia® Document Router.

Streamserve

The Streamserver interfaces is used by output management systems (OMS) of the type streamserve. The input format of the index files is being defined like this.

<SAP Business Object>,<SAP AL Doc-Type>, <SAP Repository>, <SAP Object Key>, <SAP SysID>, <doc file file>

Example:

VBRK,SDOINVOICE,T1,095092046,U8P,strs234BA33A41676152310144089686720.pdf

RDI

The SAP Raw Data Interface (RDI) is the standard protocol by SAP to deliver the data of outgoing documents to an external OMS. The RDI file contains all information required by tia® Document Router in order to store the image file in an external DMS (defined within SAP using standard ArchiveLink customizing as well as linking the archived documend to an SAP Business Object in order to allow an user to access the archived image using SAP ArchiveLink functionality. Information like the ContentRepository, Object Type as well as the ObjectID will be contained within the RDI file.

B4Activator

The B4Activator interface is specifically designed for transfering multiline index data with attachments and table data to SAP (e.g. to be processed further by KGS Activator). The first line within the index file contains information regarding the main document with ContentRepository, SAP (Workflow) document type as well as the image filename. All attributes are being separated by semicolon ( ; ).

Generic DataInterface definition

In addition to the already mentioned interface definitions Streamserve, RDI and B4Activator theres also a more generic index format specification, which allows you setup an INI file which holds various sections each describing a specific index format fitting your requirements. The generic DataInterface approach is being described further in the following section DR4 - Defining DataInterfaces, SIDMappings and Archive Link Mappings .