With R2EdiViewer, EDI files (not XML/native files) can be indexed in BATCH mode
via the start parameter -IP.
A quick search is then possible from any PC via the File --> Index search menu,
that has access rights to the index directory and the EDI files.
An indexing profile is used to determine:
- which EDI files are to be indexed.
- which field contents, in addition to file name, file format and file date, are to be determined from the EDI files
and are to be included in the index as indexing fields / search fields.
- in which directory the index files are located.
- when index entries that are no longer required can be deleted.
An indexing profile is always required, even for PCs that have not created the index,
are not the index owner, but only want to access the index via the index search.
This indexing profile must be identical to the profile used for index creation
with the exception of the directory details for the EDI data and index files.
Via the customizing menu Indexing profiles --> Configuration
a maximum of 9 different indexing profiles can be created.
Profile 1 is an example default profile and determines a total of 8 indexing fields from
EDIFACT, IDoc and VDA files, e.g. sender, receiver, document number
(invoice number, delivery note number, delivery call-off number, shipment number, etc.).
The indexing fields cannot be changed from profile 1.
But you can copy profile 1 and then adapt it.
4.5.1. Buttons
Button | Meaning |
---|---|
SAVE | Changes to the current profile are saved. |
COPY | The current profile is copied to a new profile. |
RENAME | The current profile is renamed. |
DELETE |
|
VALIDATE | The profile must be validated before it can be used. This applies both to the index owner and |
CLOSE | Close dialogue without saving any changes. |
4.5.2. Status display
Status | Meaning |
---|---|
The profile is new. The next process step, validation, has not yet been carried out. | |
The profile is valid and the index owner can start an indexing run with the startup parameter -IP. | |
Indexing (start parameter -IP) was performed with the profile. With an active profile, the index directory and the start directory of the EDI files | |
The data selection instructions have been changed for an active profile with indexing data. A new validation is required. Remark: If the names of the "IDX" indexing fields have been changed due to the modified data selection instructions, it is no longer possible to search using the old "IDX" fields when performing an index search. |
4.5.3. Indexing settings
Input field | Meaning |
---|---|
Selected indexing profile | Selection of an existing profile. |
Index files directory | Base directory for storing the indexing files. Performance: |
File search filter | The EDI files to be processed can be restricted via the file name and the file format. Example: All EDI files/formats are processed by default. |
File date | As the central selection field, the file date determines which |
Start directory | Defines the base directory where the search for EDI files to be indexed is started. |
Use the file date to | If subdirectories are to be searched, |
Reorganize index entries | Index entries are deleted if the EDI file date is older than the specified days. |
4.5.3.1. Report fields / indexing fields / search fields
By default, 3 indexing fields are created for each EDI file, which are then available
as search fields in the index search:
- File name (containing any existing subdirectories and the file name)
- File format
- File date
"File size" is also included in the index, but cannot be searched for.
Indexing fields from the EDI data are added via data selection instructions.
The input syntax is identical to a layout data selection file.
Report field --> Indexing field
A report field is used as an indexing field if the report field name contains "IDX_".
Indexing field --> Search field
In the "Index search" dialogue, the IDX report field is used for the search field label, in which:
- all characters up to and including "IDX_" are removed
- all underscores are removed
This means that " C_IDX_Interchange_Sender_ID " in the index search becomes "Interchange Sender ID".
C-fields and ValueAppend
In the default profile only C-fields with ValueAppend are used for indexing.
This means that a new line is not created for each material item, for example, but that
all article numbers are concatenated into the field C_IDX_Material_number.
Ideally, an EDI file then consists of one indexing line.
Of course, several indexing lines can be created per EDI file if, for example:
- the length of the content of a report field exceeds 1000 characters
- an IDoc file contains several IDocs
This means that the number of entries in the index is not the same as the number of indexed EDI files.
4.5.3.2. Validate
After validation, the indexing lines of max. 10 files are displayed.
This allows the data selection instructions to be checked to see whether the indexing fields
have the expected content.