Introduction
In document router it is possible to configure a repository mapping. There are 2 types of such a mapping:
Simple : The repository is mapped to another according mapping file
Prefix : the document file name is used to fetch the prefix
In the following it is explained how repository mapping can be configured and you the mapping files has to look like.
General configuration of the repository mapping file
In document rounter instance configuration inside common tab there is the item RepositoryMappingFile.
...
The type of the mapping files are java properties files. The key “Type” is responsible to determine the mapping type.
Simple Repository Mapping
Code Block |
---|
Type=simple
AB=TT
CD=FI |
The repository may be extracted from document file name AB is mapped to TT respective CD to FI.
Prefix Repository Mapping
Code Block |
---|
Type=prefix
AB=E74;newClient;TT |
Here the SID, client and repository is mapped.
Incompatibility
While the Simple type is compatible to Schemas like this:
Code Block |
---|
[QR_tut_prefix_2]
ImageFileName = f |,|0 |
SYSID = S |,|0 |@ImageFileName[_,1]
SAP_OBJECT = B |,|0 |BKPF
AR_OBJECT= T |,|0 |ZMAIK
LoginCL= S |,|0 |@SYSID
CONTREP = C |,|0 |@ImageFileName[_,2] |
The prefix mapping can’t work with this because prefix mapping is based on document file name split with underscores. An file name according the scheme above E73_AB_Vertrag.pdf, would result in an prefix E73_AB.
This may not be what it was expected.