The files kcusap.jar and jcoadapter.jar have to be copied to the LOAD-directory on the server, the file kcusap.ini has to be copied to the SYSTEM-directory on the client. These files are copied to their destination during isntallation or maintenance. The parameters contained in the section [CONNECTION] have to be adapted to the facts of the customers SAP-system.
This version uses the SAP Java Connector (JCo) Version 2.1.4 or higher to connect to the SAP-System. Unfortunately the free distribution of the SAP Java Connector is not allowed. Therefore it is necessary to download this component from the SAP support portal (http://service.sap.com). To get access ot the SAP support portal you have to be a registered member of the SAP service marketplace.
The SAP Java Connector zip archive contains two JCo libraries:
sapjco.jar sapjcorfc.dll librfc32.dll
These Libraries can be copied to any directory (e.g. C:\IDL:\thirdPartyJars). Afterwards this component just have to be set in the IDLIDL Konsis options dialog.
This setting will be available and activ after a IDL Konsis restart.
In the transport requests all necessary objects of the development class are included. This means that with every new installation or upgrade not more than three transport requests have to be put in the SAP-System.
| Module | 4.0B | 4.5 | 4.6 | 4.7 (also Unicode) |
|---|---|---|---|---|
| FI | 9A2UAP | 9A2UAP | 9A2UAX | 9A2UVS |
| CO | - | 9A2UCX | 9A2UCX | 9A2UCT |
| FI-AA | - | 9A2W32 | 9A2W32 | 9A32WO |
The respective transport request for the FI-module are the basic transport request, that contains all data dictionary object and development classes. This transport request is always the first that has to be entered to the SAP-system
The IDL Konsis-SAP-R/3 interface (module FI) consists of six function modules
and a report:
The function modules are bundled in a function group named ZBSF . This function group is located in the development class ZIDLKONSIS_FIBU . All elements are located inside the SAP-system. No external components exist. The development class is shipped in one transport request (see ahead).
The IDL Konsis-SAP-R/3 interface (module CO) consists of two function modules
and two reports:
The function modules are bundled in a function group named ZBKS . This function group is located in the development class ZIDLKONSIS_CO . All elements are located inside the SAP-system. No external components exist. The development class is shipped in one transport request (see ahead).
The IDL Konsis-SAP-R/3 interface (module AM) is one function module
Further it contains a report:
The function modules are bundled in a function group named ZBAN_NEU . This function group is located in the development class ZIDLKONSIS_ANBU. All elements are located inside the SAP-system. No external components exist. The development class is shipped in one transport request (see ahead).
Technical processing
In the following steps the installation process is described for using the command line. The GUI transport management system can of cause also be used.
For the installation you need the password for the user <SID>adm or another user who has access to the SAP transport management system. It has to be checked, if the ABAP/4-Job RDDIMPDP in client 000 (user DDIC) is planned event triggered. Eventually this job has to be planned by the user DDIC in client 000 by calling the report RDDNEWPP. If this job does not exist, the transport files cannot be imported correctly. To start the transport you need on a unix system a telnet-emulation (or rlogin, ssh etc). On Windows systems you have to start the program cmd.
The files have to be copied to the following SAP directories
Please note sensitivity is depending on your system settings. Copying the files with FTP the BIN mode (BINARY) has to be chosen.
Change to the directory /usr/sap/trans/bin. With the command
tp addtobuffer <TA> <SID>
the transport files are loaded into the transport buffer of the system. <TA> means transport request and <SID> is the SAP-system name.
You can check inconsistencies with a test import. It is recommended to execute a test import with the following command.
tp tst <TA> <SID>
The import of the operativ components is realized by the command:
tp import <TA> <SID> client=<MANDANT> u18
If you work with several clients, the transport request has to be imported in every single client (client specification always three characters). When the installation is complete the import protocols should be checked for errors and warnings. Because the actual transport files are created on systems with a relativ new release, importing them in an older system can lead to warnings.
Finally three cross-client logical file names and one logical file path have to be defined:
The logical file path is Z_KONSIS_TEMP_BELEG_PFAD (path for IDL-Interface). This logical file path has to be assigned to a physical path (z.B. /usr/temp/<filename>). SAP users working with the IDL Konsis-Interface need create, write and delete access on this path. They need also the SAP authorization object S_DATASET).
Background:on one hand, the reports write their results to a file; on the other hand the function module Z_GET_DEBKRED_PERIOD_DETAILS needs a temporary working file due to the amount of data being processed in this task (Reading vouchers from SAP-table BSEG). This working file is deleted when the processing of the function module has finished.
The logical files are named:
All files have the data format ASC and the application area FI.
The SAP-user needs for executing the function modules the authorization for executing remote function calls (RFCs). Using the SAP-RFC-Library (librfc32.dll), usernames and passwords cannot contain any special characters like vowel mutations (ä, ö, ü), ß or other country specific characters.
If you have any problems please contact the Hotline.
Maintaining file names and paths in the SAP system is located:
SAP-Menue --> Tools --> Accelerated SAP --> Customizing --> SPRO-Edit Project
In the IMG display please choose
Basis Components --> System Administration --> Plattformindependant File Names --> Cross-client Maintenance of File Names and Paths
Example for a logical file path
Example for a logical file name
INI-file settings
After copying the files KCUSAP.EXE and KCUSAP.INI to the directories (see ahead) you have to set the following parameters in the KCUSAP.INI file.
Example connection settings
Section Connection
The parameters and their meaning:
Settings in IDL Konsis
To call the SAP interface from the application IMPORT the following changes in some menu items (application MEN in project IDL Konsis) have to be maintained:
kcusap.jar
kcusap.jar
kcusap.jar
kcusap.jar
kcusap.jar
kcusap.jar
kcusap.jar
kcusap.jar
kcusap.jar
If you wish to read data from the UKV-Ledger (operational format of p/l), it is recommended to use the menu item UNLICKONV.
kcusap.jar
Attention:
All settings for the specific functions can be maintained in the options dialog for the SAP settings.
If you chose the option Read from Summary data preparations for consolidation (GLT3) you should provide the name Z_GET_IC_SALDEN as the alternative name of the function module