KGS DocumentRouter 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.
...
An interface describes the type of input data KGS DocumentRouter tia® Document Router receives. The following types of interfaces are supported by KGS DocumentRoutertia® 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 KGS DocumentRouter 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.
...
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 KGS DocumentRouter (DR4 ) - Defining DataInterfaces, SIDMappings and SIDMappingsArchive Link Mappings .