2.1. Preparation
2.1.1. System requirements
R2EdiViewer is a Java application for Windows and runs under Java versions 8 - 21.
When R2EdiViewer is setup, a local JRE 64bit is also installed
in the R2EdiViewer subdirectory private\jre.
If you want to use the JDK/JRE installed on the computer/under Windows, the content of
private\jre can simply be deleted (the directory itself must remain unchanged).
A search is then first made for a JDK (Java Development Kit), then for a JRE (Java Runtime Environment).
Of course, you can also save your own preferred JRE version in the directory private\jre.
If R2EdiViewer is updated via the "Help->Check for new version" menu, a checkbox can be used
to decide whether the supplied JRE64 version should replace the version in private\jre.
2.1.2. Backup program directory
|
|---|
If you already have installed a version of R2EdiViewer:
|
Better safe than sorry
2.2. Setup
By starting Setup...exe the following files are installed:
| Filename | Description | SO | |
|---|---|---|---|
R2EdiViewer.exe | The main program | ||
R2EdiViewerC.exe | Main program with additional console screen. | ||
R2EdiViewer.bat | Starts main program R2EdiViewer.jar | ||
R2EdiViewer.jar | An alternative in unattended batch mode: Main program | ||
R2EdiViewerSD.zip | Syntax directories | 26.30 |
|
R2EdiViewerSH.cfg | Config file for the syntax-highlighting | 26.20 |
|
| R2EdiViewerGT.cfg | Config file to display the GoTo navigation tree | 9.10 |
|
| R2EdiViewerIP.cfg | Config file for the indexing profiles | 26.20 |
|
| R2EdiViewerSH|dark.css | Cascading style sheets for formatting syntax-highlighting | 23.20 |
|
| R2EdiViewerXL.cfg | Config file for the layout determination of XML files | 23.30 |
|
R2EdiViewer.ini | Storage of program settings | 26.30 |
|
| R2EdiViewerWL.css | Cascading style sheets for formatting the log file | 7.12 |
|
R2EdiViewerDoku_xx.pdf | User Guide DE=German / EN=English | ||
R2EdiViewerLicence.pdf | End User License Agreement | ||
R2EdiViewerExample.edi | Example of an EDI file | ||
R2EdiViewerUninstall.exe | Setup: deinstallation program | ||
install.log | Setup: installation protocol | ||
[jre64] | Local JRE (64-bit); copied to the empty directory “private/jre” | 26.30 | |
[layouts] | Directory with default delivered layout templates | ||
| [layoutsEdifileChecker] | Directory with EDI file checker layout template | ||
[libs] | Directory with external JAR files | ||
| [private] | Directory for customer customizations (is never deleted) | ||
| R2EdiViewerSD.zip | Empty syntax directories for customer adjustments | 7.12 | |
| ..ExtensionLibraryXX.jar | Five empty JAR files for customer adjustments | 8.10 | |
| [jre] | A JRE installed by the user or the JRE from the jre64 directory | ||
ZBC_R2EdiViewer.abap | ABAP ® program to view IDocs from SAP ® via R2EdiViewer | 26.20 |
2.2.1. Customer customizations
2.2.1.1. Customer adjustments can be made via customizing in the :
- user directory
- "private" directory
The directories are searched as follows :
| SO | Search order |
|---|---|
| The file is searched in the directories: "private" and program All found files will be used in the directory order. The subsequent search strategy of entry: The first match terminates the search. |
| The file is searched in the directories: user and "private" and program All found files will be used in the directory order. The subsequent search strategy of entry: The first match terminates the search. |
| The file is searched in the directories: user or "private" or program. |
| The file is searched in the directories: user or "private". Only the first found file is used. |
2.2.1.2. Customer layout directories are :
- never deleted by an installation/upgrade
- searched first in the user directory and then in the program directory
2.3. SAP ® -integration
2.3.1. ZBC_R2EdiViewer.abap
The ABAP ® ZBC_R2EDIVIEWER can be used to select IDocs in the SAP ® system,
which are then viewed by the locally installed R2EdiViewer.exe.
If more than one IDoc is found during the selection, an ALV list is displayed.
An IDoc can be selected from the ALV list by double-clicking.
The selected or single IDoc is downloaded to the local PC as a flat file (without status records)
or as an XML file (with status records) and then displayed by R2EdiViewer.
The ABAP ® program source is located in the program directory and must be entered/updated manually
in the SAP ® system with transaction SE80 in a package of your choice.
If you do not want to install the program source code, you can use the ABAP®
RCOD_DOWNLOAD_IDOC_AS_XML to download an IDoc as an XML file to your local computer.
Of course, this XML file will then need to be opened manually using R2EdiViewer.
2.3.2. WLF_IDOC
The SAP ® standard transaction WLF_IDOC is also used to view IDocs.
With a small SAP ® modification, it is possible to use the ABAP ® ZBC_R2EDIVIEWER
to display the IDoc instead of the SAP ® standard view.
In the WLF_IDOC list, double-clicking on the status number of the IDoc
(SAP column "IDoc Status") opens the display via ZBC_R2EDIVIEWER.
To do this, proceed as follows:
- Adapt the sub-program "uc_idoc_display" in the ABAP ® "WLF_IDOC_NEW_F01" accordingly
- Enter the value "ZBC_R2EDIVIEWER" in the SU3 user parameter "RWLFIDOC_NEW_EXPERT"
| form uc_idoc_display using i_docnum type edidc-docnum changing c_refresh type slis_selfield-refresh. check i_docnum is not initial. *{ REPLACE 1 *\ submit idoc_tree_control with docnum = i_docnum *\ and return. * For IDOC display use locally installed R2EdiViewer.exe * if SU3 parameter RWLFIDOC_NEW_EXPERT = ZBC_R2EDIVIEWER data: lv_su3parm(15) type c. get parameter id 'RWLFIDOC_NEW_EXPERT' field lv_su3parm. if lv_su3parm = 'ZBC_R2EDIVIEWER'. submit ZBC_R2EdiViewer with sidocnum = i_docnum and return. else. submit idoc_tree_control with docnum = i_docnum and return. endif. *} REPLACE perform refresh_single using i_docnum changing c_refresh. if c_refresh is not initial. message s023 with i_docnum. endif. endform. "uc_idoc_display |
