SAP Interfaces Installation Guide

Table of Contents

• 1 Requirements
• 2 Installation notes
• 2.1 Installation notes concerning SAP
• 2.2 Installation notes concerning IDLKONSIS

1 Requirements

The file kcusap.exe has 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. The parameters contained in the section [CONNECTION] have to be adapted to the facts of the customers SAP-system.

Further you need the file LIBRFC32.DLL (part of SAP) in your PATH.

2 Installation notes

2.1 Installation notes concerning SAP

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.

The respective transport request for the FI-module functions as a basic transport request, that contains all data dictionary object and development classes. This transport request is always the first that has to put in the SAP-system

The IDLKONSIS-SAP-R/3 interface (module FI) consists of six function modules

Z_GET_GL_ACCOUNT_LIST

Returns a list with all accounts of the selected chart of accounts

Z_GET_PL_BALANCE_HIERARCHIE

Returns the financial statement structure version of the selected chart of positions

Z_GET_PERIODBALANCES_ACCOUNTS

Returns the accumulated account balances per period

Z_GET_PERIODBALANCES_KRED_DEBT

Returns the accumulated trading partners account balances of debitors and creditors per period

Z_GET_DEBKRED_PERIOD_DETAILS

Returns the accumulated trading partners account balances per business area from the posting table BSEG

Z_GET_COST_OF_SALE_LEDGER

Returns controlling balances and intercompany account balances with controlling objects from the Cost-of-Sales-Ledger GLTFUNCT

and a report:

YFB_ACCOUNTS

This report has four functions:

1. Calls the function module Z_GET_PERIODBALANCES_ACCOUNTS (account balances) and writes the result
2. Calls the function module Z_GET_PERIODBALANCES_KRED_DEBT (intercompany account balances debitor/creditor) and writes the result
3. Calls the function module Z_GET_DEBKRED_PERIOD_DETAILS (intercompany account balances P/L) and writes the result
4. Logging single posting documents

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 (s.o.).

The IDLKONSIS-SAP-R/3 interface (module CO) consists of two function modules

Z_GET_KST_STAMM

Returns a list with all controlling objects of the selected chart of contr.objects

Z_GET_KST_ISTDATEN

Returns the accumulated controlling balances per period

and two reports:

YKB_KST_STAMM

Calls the function module Z_GET_KST_STAMM and writes the result

YKB_KST_ISTDATEN

Calls the function module Z_GET_KST_ISTDATEN and writes the result

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 (s.o.).

The IDLKONSIS-SAP-R/3 interface (module AM) is one function module

Z_GET_ANLAGENBUCHUNGEN_NEU

Returns the accumulated fixed assets transactions per account and posting code per period

Further it contains a report:

YAB_ANLAGENBUCHUNGEN

This report has two functions:

1. Calls the function module Z_GET_ANLAGENBUCHUNGEN_NEU und writes the result
2. Logging single transactions per fixed asset object

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 (s.o.).

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 triggerd. 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

/usr/sap/trans/data

for the R*-files and

/usr/sap/trans/cofiles

for the K*-files

Please note the case sensitivtiy 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 IDLKONSIS-Interface need create, write and delete access on this path. They need also the SAP authorization object S_DATASET).

Background:one the 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 (Lesen der Belege aus der SAP-table BSEG). This working file is deleted when the processing of the function module has finished.

The logical files are named:

• Z_KONSIS_TEMP_BELEG_DATEI
• Z_KONSIS_TEMP_BELEG_DATEI_2
• Z_KONSIS_TEMP_STAMM_DATEI

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

The following authority objects are checked within the function modules:

2.2 Installation notes concerning IDLKONSIS

INI-file settings

After copying the files KCUSAP.EXE and KCUSAP.INI to the directories (s.o.) you have to set the following parameters in the KCUSAP.INI file.

Section Connection

The parameters and their meaning:

Destination

Destination is the system identification (three characters). You can find it in the status line of your SAPGUI. (e.g.: KT2)

Client

The IDLKONSIS-SAP-R/3 Interface tries to logon at this client with the given user and password.

Hostname

Hostname is the name of the application servers. You can find it in the status line of your SAPGUI. Alternative you can put here the ip adress, too. (examples:pluto, 192.168.99.37)

Sysnr

Sysnr - transaction SM51. The last two characters of the server name indicate the SYSNR. If you have installed several instances on one physical system, the instances are distinguished bei this number. (e.g.: 00)

Gwhost

Gwhost is the name of the gateway host. If you leave this setting blank it is assumed that the gateway host is running on the computer with the name "Hostname" (s.o.).

Gwservice

The setting for Gwservice is a concatenation of the string "sapgw" and the two digit system number (SYSNR). (e.g.: sapgw00)

Trace

Trace - To log the RFC -communication to a file you can set this parameter to "on". A file ('rfc...trc' oder 'dev_rfc...trc') is created in the working directory of the application (default setting by the SAP RFC library). Usually this is within the directory e.g. s:\IDL\LOAD on the program server. Often the IDLKONSIS user only has read-access. In this case to logfile is created. Alternative you can set an environment variable with the name RFC_TRACE_DIR with the value of the directory where the logfile should be written. (e.g. c:\temp). The default setting is 'off'.

Settings inIDLKONSIS

To call the SAP interface from the application IMPORT the following changes in some menu items (application MEN in project IDLKONSIS) have to be maintained:

• field 'Ext.program' for UNLKTO:

KCUSAP /L=E /F=KTO /K=%15 /K=%20 /K=X /M=%41 $PROJEKT$

• field 'Ext.program' for UNLAGG:

KCUSAP /L=E /F=AGG /K=%14 /K=%15 /K=%20 /M=%41 $PROJEKT$

• field 'Ext.program' for UNLAGGKTO:

KCUSAP /L=E /F=AGGKTO /K=%14 /K=%15 /K=%20 /M=%41 $PROJEKT$

• field 'Ext.program' for UNLSALD:

KCUSAP /L=E /F=KTOSAL /K=%02 /K=%03 /K=%04 /K=%05 /K=%19 /M=%41 $PROJEKT$

• field 'Ext.program' for UNLICSAL :

KCUSAP /L=E /F=ICKTOSAL /K=%02 /K=%03 /K=%04 /K=%05 /K=%19 /M=%41 $PROJEKT$

• field 'Ext.program' for UNLKST :

KCUSAP /L=E /F=KST /K=%03 /K=%16 /K=%20 /M=%41 $PROJEKT$

• field 'Ext.program' for UNLKSTSAL :

KCUSAP /L=E /F=KSTSAL /K=%02 /K=%03 /K=%04 /K=%05 /K=%19 /M=%41 $PROJEKT$

• field 'Ext.program' for UNLANLBEW :

KCUSAP /L=E /F=ANLBEW /K= /K=%02 /K=%03 /K=%04 /K=%05 /K=%19 /K=%42 /M=%41 $PROJEKT$

• field 'Ext.program' for UNLUKVCNT :

KCUSAP /L=E /F=UKV /K=%02 /K=%03 /K=%04 /K=%05 /K=%19 /M=%41 /C $PROJEKT$

• field 'Ext.program' for UNLUKVIC :

KCUSAP /L=E /F=UKV /K=%02 /K=%03 /K=%04 /K=%05 /K=%19 /M=%41 $PROJEKT$

The parameter have the following meaning:

• $PROJEKT$ is the IDL directory e.g. c:\IDL on the client
• /L=E sets the language for texts and messages to english
• X in function KTO marks all detail accounts. Leaving the X (just /K= ) away, no additional e-accounts are created during the import of the chart of accounts
• /K=%02 company (e.g. 001)
• /K=%03 business unit (e.g. * or empty)
• /K=%04 closing date actual period (e.g. 12.2004)
• /K=%05 fact(e.g. I1)
• /K=%14 chart of positions code (e.g. BILGUV)
• /K=%15 chart of accounts (e.g. GKR)
• /K=%16 chart of cost centers (e.g. KSTP)
• /K=%19 variable of financial year (e.g. K4)
• /K=%20 language (e.g. DEU)
• /M=%41 client (e.g. 101)
• /K=%42 flag to control the carry-forward for fixed assets transactions

Attention:

If one of the keys (chart of accounts, company etc.) contains a special character like & (e.g. a&b), the parameter has to be enclosed in double quotes "".

KCUSAP /F=KTO /K="%15" /K=%20 /K=X $PROJEKT$

The external calls for the functions /F=KTOSAL, /F=ICKTOSAL, /F=UKV, /F=KSTSAL and /F=ANLBEW can be extended by an optional parameter /0. If this parameter /0 is set null balances are also written to the resulting file KPxxxxxx.

The external call for the function /F=KTOSAL can be extended by an optional addtional parameter /V=xxx. xxx is a placeholder for the version of the general ledger ist

The first /K-parameter for the function /F=ANLBEW is the depreciation area. If this parameter is left empty, the depreciation area 01 (book depreciation per trade law) is assumed.

The external call for the function /F=KTO can be extended by an optional parameter /D indicating that accounts marked for deletion in the SAP system are ignored and are not transferred KPKONTEN.TXT.

The external call for function /F=ICKTOSAL can be extended by an optional parameter /T indicating that the transaction currency and the currency's ISO-Code is also read.

The external call for function /F=ICKTOSAL can be extended by an optional parameter /A (/A implies /T), indicating that additional data like accounting document number, document date in document, referene document number and document type read.

To select external data for intercompany account balances via GLT3 (Summary data preparations for consolidation) the followings settings have to be maintained.

• Add the following line to the file kcusap.ini . Usually this is in the directory e.g. c:\IDL\SYSTEM

[Settings] GLT3=yes

• Change the following setting in the file kcusap.ini (section Function)

replace entry ;FunctIcktosal=Z_GET_PERIODBALANCES_KRED_DEBT by FunctIcktosal=Z_GET_IC_SALDEN

The external call for function /F=ANLBEW can be extended by an optional parameter /G. This parameter indicates the lower range for the account determination.

KCUSAP /F= /K= /K=%02 /K=%03 /K=%04 /K=%05 /K=%19 /K=%42 /M=%41 /G=02000000 $PROJEKT$

Returns all asset classes with an account determination greater or equal 2000000.

The external call for function /F=ANLBEW can be extended by an optional parameter /O. This parameter indicates the upper range for the account determination.

KCUSAP /F= /K= /K=%02 /K=%03 /K=%04 /K=%05 /K=%19 /K=%42 /M=%41 /O=07000000 $PROJEKT$

Returns all asset classes with an account determination less or equal 7000000.