...
Every row within a DataInterface defines a parameter to be used during archiving or linking. The parameter names can be used in the default value column of other parameters by prefixing them with an @-sign, like in the example above.
Special fields
Fields can reuse values of other fields.
For example in a scenario where no index file exist, all for archive and link relevant information are fetched from file name. So you need to split up the file name an maybe join if you want create additional information for e.g. linking.
Sub-Value by Position
Code Block |
---|
[positionBasedSchema]
FileName = f || |0 |
ArchiveType = C || |0 |N1
DOC_TYPE = c || |0 |
SAP_OBJECT = B || |0 |BKBF
AR_OBJECT = T || |0 |ZFILENAME
ObjectID = O || |0 |@Filename[1,18]
SYS_ID = S || |0 |@Filename[20,22]
MANDANT = M || |0 |@Filename[24,26] |
ObjectID
is an sub string ofFilename
. It uses position 1 until 18 of it.
Sub-Value by Separator
Code Block |
---|
[separatorBaseSchema]
ImageFileName = f |, |0 |
CONTREP = C |, |0 |@ImageFileName[_,1]
ARCHDOCID = D |, |0 |@ImageFileName[_,2] |
field
ImageFileName
is split by_
and then position 1 is used forCONTREP
and position 2 forARCHDOCID
Join
Code Block |
---|
[joinSchema]
FileName = f || |0 |
ArchiveType = C || |0 |N1
DOC_TYPE = c || |0 |
SAP_OBJECT = B || |0 |BKBF
AR_OBJECT = T || |0 |ZFILENAME
ObjectID = O || |0 |@Filename[1,18]
SYS_ID = S || |0 |@Filename[20,22]
MANDANT = M || |0 |@Filename[24,26]
another = X || |0 |@ObjectID@MANDANT |
here the field
another
which is used while linking is a concatenation of the contents ofObjectId
andMandant
.
ArchiveLink Connection mapping
...