Import

1 Brief description

This application supports the automatic transfer of data from the customer's financial accounting or from other external sources (e.g. IDL Connector) to the IDL Konsis system. The prerequisite is that the data is available in the form of a readable (ASCII) file.

2 Description of the IMPORT call application

2.1 Input options

Although the application offers a large number of input fields, these are not used to select data and therefore have no influence on the rows displayed in the table section. Instead, the input fields are used to control the import process or other subsequent applications. The input fields are largely pre-assigned from the user's default settings.

General mandatory entries are only required for the parameters period and data type. They are evaluated when importing report data. They are not evaluated when importing master data. As these fields are initialized from the user's default settings, manual entry is only necessary if the required keys differ. A period interval can also be specified by entering from period.

The specifications for group/subgroup, company, and business area are also primarily used to check the plausibility of the imported report data to ensure that the specified file actually contains the expected data. For the import variant < Delete data + New import> for report data, either the company or the group of companies must be specified in order to avoid other data being deleted.

In a similar way, the entries for chart of accounts, cost center plan, item plan, and report ID are used to check the plausibility of the imported data when importing accounts, cost centers, items, account/item assignments and report line descriptions.

The format that describes the line structure of the text file to be imported can be specified in the format ID. This format ID must be defined in IDL Konsis (see IEFID application). An assignment to the IDL Konsis fields must have been defined for this format ID for the respective dataset in the ALLCFLD application. The format ID can also be specified in the file dialog after starting the import process, provided it has not been suppressed. If it is not specified, the IDL Konsis standard format #TXT is assumed.

The conversion group can be used to specify how certain keys are to be converted during the import process. This is necessary if the key systems of the source system (accounting) and the target system (IDL Konsis) do not match. A typical use case is the conversion of company numbers that have been assigned differently in IDL Konsis than in the source system. The prerequisite for this is the definition of the conversion group in the TRFGRP application and the definition of the conversion rules in the UMSOBJ application.

The input fields Month > 12, Fiscal year variant, SAP client, From change date, Language, and With carryforward are primarily used to control the process for reading the required data from the source system, as supported in particular for the SAP interface. With carryforward also ensures that the data generated by the period carryforward is retained when loading transaction data in the variant < Delete data + New import>.

2.2 Table section

Data from a database is transferred with each import process. The datasets are listed in the table section of the window. They are displayed in a tree structure, with the supported datasets divided into these groups are structured:

• Master data
• Separate financial statements
• Consolidated financial statements
• Miscellaneous

Before executing an action, the line of the relevant dataset must be selected.

2.3 Actions / follow-up applications

Import file (.DSCTXT)

This action starts the import process for the selected dataset. This action is also triggered as a standard action by double-clicking on a row.

Delete data + re-import (DSCTXT file)

This action also starts the import process for the selected dataset, but in a variant in which existing data is deleted first. This is necessary, for example, if a dataset is imported repeatedly. This variant is only available for some datasets, especially report data or structural data (assignments). In order to avoid incorrect deletion, the dataset to be deleted must be restricted by making the appropriate key entries in the header. For example, the company or group of companies must be specified for reporting data. The group of companies is determined taking into account the period and the ex data type (set in the mask from the default setting). The applications ask by default before the data is deleted. Details of the effect can be found in the description of the respective import application.

Read out data from external system

This action does not start an IDL Konsis application, but an external program call if one has been defined for the selected dataset (by the user). Typically, this is a program with which data is read from the external system (accounting) and made available or with which the data provided is copied to an available drive. The external call is to be entered in the application <menu items> (MNUITM) in the input field "External call" with a menu ID that begins with 'UNL' and then designates the respective dataset. This functionality is used in particular for the SAP interface.

Edit import file (.DSCTXT)

This action calls up the standard editor to view or change the import file (default suffix '.TXT'). This can be used, for example, to check whether the specified file actually contains the expected data. Or incorrect content can be corrected before the import process. The file must then be saved after the changes have been made.

Edit log file (.PRT)

This action calls up the standard editor to view or change the log file (default suffix '.PRT'). For example, error messages that were suppressed during the import process can be viewed. As the log file also contains the incorrect data records, these can also be corrected. After saving the modified file (possibly under a different name), this file can be specified as a new import file in the file dialog so that only the initially incorrect records are imported again.

Display overview

This action branches to the overview application for the selected dataset. The keys specified in the header are adopted where appropriate. This action can be used to check whether data already exists for the specified keys before the import process. After the import process, the imported data can be viewed. The "Changed date" and "AndDate" columns can be used to distinguish which data has been inserted or changed by the import process.

Processing controls

This action branches to the CMPCNT overview, which displays the status of the report data in the form of message numbers. This application is therefore only of interest for report data in the individual financial statements.

Import/export format ident

This action branches to the IEFID overview, in which the format IDs defined for the selected dataset are listed. In addition to the standard format "#TXT", the formats defined by the user are displayed.

Assignment of IDL consis fields to formats

This action branches to the ALLCFLD overview, in which the format descriptions defined for the selected dataset are listed. In addition to the standard format "#TXT", the formats defined by the user are displayed.

Show help text

This action opens the help text for the respective import process. It describes the special features of the import application (keys to be specified, insert only or also change, availability of the variant with deletion, etc.) and also contains a description of the standard import format "#TXT", including the specification of mandatory fields. This action can also be triggered by pressing the <F1> key after selecting a line.

The following import applications are currently available for master data:

The following import applications are currently available for company financial statements:

The following import applications are currently available for the consolidated financial statements:

The following import applications are currently available for processing currency conversion:

The following import applications are currently available for Others:

3 General sequence of an import process

3.1 Reading from external system and transferring the import file

The transfer from an external system takes place in 3 steps for each dataset:

• Reading the data from the respective external system and providing it as a readable (ASCII) file
• Transfer/data transfer of the provided data sets by e-mail or file transfer to a drive that can be accessed by the IDL Konsis recipient
• Transfer of data to IDL Konsis using the IMPORT application from the respective directory

The first two steps are performed outside of IDL Konsis. However, if the processes are such that they can be specified as a command line call of the operating system (for Windows DOS command line), a call from IMPORT is possible. The action < Read data from external system> is used for this purpose. This is followed by a menu item that begins with the character string "UNL" (see MNUITM application). The user can enter the command line for the respective menu item, which is then executed when this action is called up.

3.2 File dialog

The structure of the file lines, file name and directory can be freely selected. They must then be specified in the file dialog during the import process. If the file dialog should be omitted (can be set via the menu item <Extras> --> <Options> --> <Import/Export>), the default values are

• Standard export/import format of IDL Konsis, described under the format ID "#TXT" in the application "Assignment of IDL Konsis fields to formats" (ALLCFLD)
• The standard file name is always "KPxxxxxxxx.TXT", where "xxxxxx" is a 6-digit number for the dataset and corresponds to the menu ID in IDL Konsis (e.g. "ANLBEW"). If the menu ID is shorter than 6 digits, it is filled with 'X' (e.g. "GESXXX"). Historical exceptions: "KPSALDEN.TXT" for "KTOSAL" and "KPKONTEN.TXT" for "KTO". Out of consideration for existing interfaces, no adjustment is made here. The standard file name is displayed (without the suffix '.TXT') in a column in the IMPORT table.
• The default import directory can be set via the menu item <Extras> --> <Options> --><Import/Export>.

Note: When a text file includes the entry “HERKUNFT=KONSIS”, any fields left empty will cause the corresponding attributes to be deleted from the database during import. However, if the origin is not KONSIS, attributes are only deleted when an asterisk (*) is explicitly placed in the relevant field within the text file; otherwise, existing database values are preserved even if the field appears empty.

3.3 Control parameters

The import file contains different lines:

• Blank lines are ignored during processing.
• Comment lines always begin with '**'. They are also ignored during processing. Comment lines are created, for example, during IDL Konsis export when outputting headers and totals lines.
• Control lines always begin with '$$'. They have a special function, which is described below.
• All other lines are treated as normal data lines and lead to a change in the database or to an error message.

The control lines must have the following structure: "$$ <control word>=<value>". An export file created with IDL Konsis can serve as a sample. The following control words have functional effects:

CODEPAGE

specifies the character set with which the import file was created. This information relates in particular to the correct display of umlauts and special characters in the language-dependent designations and comments. Specifying this parameter causes the input record to be converted in accordance with the specified code page. If this parameter is not specified, the currently most commonly used code page "windows-1252" is assumed.

TESTSTR

contains the character string "AÖÜaööüß" in the character set (specified under CODEPAGE). This information can be used to check whether the specified CODEPAGE leads to a correct conversion of this character string.

LOCALE

specifies the country-specific form in which numerical and date values are contained, if applicable. The specification is made in the format used in Java (e.g. LOCALE=de for German formats). The values are not converted if this is not specified.

VERSION

causes the specified version number to be compared with the version number processed by the program for the input format. This is always the internally used default format ('#TXT'). Formats defined by the user are not affected by this version check.

HERKUNFT

denotes the system from which the import file was generated. Typical values are 'KONSIS' for data exported from IDL Konsis, 'CONNECTOR' for data generated with IDL Connector or the name of the external system (e.g. 'SAP', 'AXAPTA'). This information can be used to control specific special treatments in processing where this is necessary.

3.4 Processing the data

Whether a file contains the data of one, several or all companies depends on the range of functions of the programs for reading the data. It is also not possible to process report data for just one period if a <V period> (from previous period) is entered in the header of the IMPORT application in addition to the <Act.period> .

During the import process, the data records specified in the file are usually inserted. A change to existing data (update) is only possible for master data. For report data and structural data (item/account assignments, report line descriptions, import/export formats), the variant < Delete data + re-import> is available for this purpose so that deleted data is not retained.

When updating the data records, attributes from the existing record in the database are only overwritten if they are explicitly specified. If the specification is missing in the import file, the previous content is retained. By specifying an '*', it is also possible to set the content of an attribute to empty, provided this attribute is optional. The attributes for which this control is available are described in the documentation of the respective application.

Master tables contain attributes for designations that are language-dependent. These can only be specified once in a record of the import file, i.e. in one language only. The corresponding language key must also be specified in each case. If the designations are to be managed in several languages, several data records must be provided in the import file for the same master record, which differ in the language key and in the designations.

A conversion can be specified for certain keys and attributes before processing. To do this, a conversion group must be specified in the header of the IMPORT mask. Conversions from external to internal keys must have been defined for this conversion group via the application <conversion group assignments> (UMSOBJ). The conversion of company and business area keys is supported in all applications that process the corresponding data. If necessary, a distinction is also made between key and IC company or IC business area.

Certain master data must have been defined in IDL Konsis before the datasets are transferred to IDL Konsis, e.g:

• Chart of accounts for the transfer of account numbers
• Position plan for the transfer of position numbers
• Accounts for the transfer of report data and account item assignments
• Items for the transfer of account item assignments
• Data types and Periods for the transfer of report data
• Currency indicator for the transfer of IC balances with specification of a transaction currency
• Companies for the transfer of reporting data including the IC company's details in IC balances
• Divisions for the transfer of reporting data including the information of the IC divisions in IC balances

3.5 Error handling

During the import process, the data specified in the file is transferred directly to the IDL Konsis database with all plausibility checks as for dialog input. The option is available at the start of the import process and in every error window,

• to see each rejected incorrect record individually in a display window or
• without individual display up to the <end window> .

Errors detected during processing are normally reported in a display window. The error display shows the number of the faulty record, the faulty record (if displayable), the error message, the faulty field and the faulty field content. In this window, you can control whether further errors should also be displayed in the message window (<OK>) or whether further error messages should be suppressed (<Accept all>). The third option is to end processing immediately by clicking < Cancel>. This can be particularly useful if the data to be imported contains a systematic error that applies to all data records. However, records that have already been processed are already saved in the database.

Irrespective of the display of the message window, faulty records including the error messages and the current record number are each written to a separate log file. The name of the log file is always derived from the processed file by replacing the suffix '.TXT' with the suffix '.PRT'. If a file with this name already exists, it is renamed using the first free three-digit numerical suffix, i.e. '.001', '.002' etc. In this way, the logs of all import processes for a dataset are archived.

Each log file < filename>.PRT can be displayed via a separate menu item in IMPORT after processing is complete and corrected if necessary. Once the errors have been corrected, .PRT can be converted back to .TXT (<Save as>) and only these corrected errors can be imported again. The error information shown (** in columns 1-2) from the 1st transfer run is read over. Alternatively, the corrected log file itself can be specified as the import file in the file dialog.

In addition to error messages, import applications also issue warnings. These are displayed in the same way as the error messages in the message window, but have different buttons:

• <Accept> means that this warning should be interpreted as an error. Further handling is the same as in the event of an error (e.g. inclusion in the log file).
• <Accept all> means that not only the currently displayed warning, but also all subsequent warnings should be treated as errors without the warning dialog being displayed again. This behavior is independent of the type of warning.
• <Ignore> means that this warning should be ignored. This means that the record is processed further and, if necessary, saved in the database.
• <Ignore all> means that not only the currently displayed warning, but also all subsequent warnings should be ignored without the warning dialog being displayed. This behavior is independent of the type of warning.
• <Cancel> causes processing to be canceled immediately. However, records that have already been processed are already saved in the database.

At the end of each import process, a < end window> is output with processing statistics including a count of correct and incorrect records. The information in the <end window> is also written to the log file.

The suppression of message windows can be controlled via switches that can be accessed via the menu item <Extras> --> <Options> --> <Import/Export>:

• <Suppress message dialog> causes the start window, all windows with error and warning messages and the end window to be suppressed. Warnings are ignored.
• <Suppress start window only> only suppresses the windows with error messages, but not the start window, the end window and at least the first warning.
• <Print end message> causes the end window not to be displayed on the screen, but to be printed directly on the standard printer.

4 Information on the interfaces between SAP/R3 and IDL Konsis

The range of functions and operation of the standard interfaces between SAP/R3 (Financial Accounting - FI, Controlling - CO and Asset Accounting - AA) and IDL Konsis are described in separate documentation.

5 Special information on the standard interfaces between DCW Financial Accounting (AS/400) and IDL Consis

The RPG interfaces between DCW Financial Accounting and IDL Konsis are provided by IL INTERNET LOGISTICS AG, Hamburg.

There are standard interfaces between DCW financial accounting and IDL Konsis for fast and secure transfer of the following data: DCW release version 3.3.x and higher

! In principle, only accounts and balances from clients that have an entry in the IDL company field in the DCW client master under "Financial accounting general" are transferred!

- Master/basic data (transfer from the account sheets)
- Chart of accounts per group of companies
- For main accounts with sub-accounts/address numbers, an extension main account is also created (normal main account + "E")

Please note:
If you work with summarization keys in DCW, these are not supported in the interface! In such cases, IDL Konsis works via summarization accounts. These settings via summarization accounts must therefore be made manually once in IDL Konsis via the company chart of accounts and ongoing changes must be maintained in parallel. If this is not done, the balance sheet/P&L from KONSIS cannot be compared with that from DCW.
- Account assignments to balance sheet and income statement items according to 1st version structure (DCW tab. B0702 and B0703)
- Account balances/key date data (transfer from main/sub-accounts)
- One balance record per main account
- for main accounts with sub-accounts/address numbers in the case of a 'balance rotates' item, a further balance record; for companies with 'non-genuine clients'/see below, the 'balance rotates' function is only triggered after the total balance of all associated clients.
- For intercompany balance sheet main accounts with sub-accounts, a balance record for each sub-account if you have defined the main account as an 'I' account in the DCW table B3201 (or N0301, N0401 or N0501...).
- IC group clearing balances (transfer from the individual posting lines for affiliated companies, which are updated on an ongoing basis in the DCWM/BICOBAL table)
- The prerequisite for this is that the corresponding balance sheet main accounts in the DCW account sheet are marked with "05" = intercompany clearing and their sub-accounts are provided with corresponding client numbers. This means that affiliated companies that are not in the DCW accounting system of the computer must also be entered as "remote" clients with IDL company numbers in the DCW accounting system of your computer. We recommend that you also enter the clients that are not currently consolidated at your company. If this is not desired, you should create a so-called DUMMY client with a DUMMY IDL company and assign the corresponding sub-accounts to this DUMMY client. This avoids error messages during the batch transfer of intercompany balances.
ATTENTION: The transfer of IC group clearing balances alone cannot be repeated, as main account balances are changed. If a repetition is necessary, the corresponding main accounts must first be deleted via KTOSAL and read in again. Scheme of the transfer -----------------------------------------------
+----------------------------+ | | | 1.Provision AS/400 | | DCW Financial Accounting | |  Menu item: IDL | | | +----------------------------+ DCW v DCW *) | +==================+ +--------------+ | |- Transfer | | DCW/IDL | | Chart of Accounts | + |  Conversion |-> | | | Tables | | -<| | | B3201+03/N0xxx | | +==================+ +--------------+ | | - without | |  error log | | | DCW **) v DCW | +------------------+ +==================+ +==================+ | |= IDL account master |-->|- Accept | |- Accept |>| G/L/main accounts | | account balances | | IC-KonzVerrechn | | DCW:IKOBMST | | | | | | IDL:KPKONTEN.TXT| -<| with DCW:IKOBMST | -<| from DCW:BICOBAL | | +------------------+ | +==================+ | +==================+ | | - please edit | | |  Protocols 1-3 | | | | | +------------------+ | +------------------+ | | |= IDL KtnZuordn.to| | |= IDL Account Balances| | |>| Balance/P&L Position| |>| G/L/Main Accounts| | | DCW:IAGGEXP | | | DCW:ISALEXP | | | IDL:KPAGGKTO.TXT| | | IDL:KPSALDEN.TXT| | | +------------------+ | +------------------+ | | | +------------------+ | | |= IDL IC-Unter- | | |= IDL IC-KonzVerr | | |>|  account balances | |>|  posting balances | | | DCW:ISICEXP | | | DCW:ISCCEXP | | | IDL:KPICSALD.TXT| | | IDL:KPICKONV.TXT| | | +------------------+ | +------------------+ | v v | +----------------------------+ | | ***) | ----------------->| 2.Data transfer DCW/IDL | | 3.FIBU - transfer | | IDL Konsis: IMPORT | | | +----------------------------+

The provision files can be created and deleted on the DCW page
- for a single client
- for several clients consecutively updating the same staging file(s), i.e. one selection per client without the staging file(s) being deleted in the meantime
- Group-wide transfer in accordance with DCW terminology, i.e. all clients in the same group RECOMMENDATION: Deletion should always be carried out on a group-wide basis.

The following entries must be entered correctly in the DCW client master records under 'Change general financial accounting':
- the IDL company
- the IDL company division, provided the DCW client does not correspond to a legally independent company; otherwise empty, as this is no longer a mandatory field in IDL since EURO Release 98.

IMPORTANT: If you copy client masters in DCW, be sure to change or delete the IDL company or the IDL company division in the new client. Otherwise you will get incorrect balances.

By omitting both entries in the DCW client master, you can, among other things, ensure that special budget or test clients with all data for IDL consis remain hidden and are therefore not transferred. If the data is not read out completely for all clients with IDL company numbers of the same group of companies, you must check whether there may be restricted client authorizations according to DCW standard conventions.

*) Before the transfer can be started, some DCW/IDL conversion tables must be filled with additional data that was not previously contained in the DCW tables. By default, the table names B2301 Accounts with account indicator1+2 N0303 Key table for permitted account indicators1+2 are used for this.
Since DCW Release 3.3.x, the entry in the account sheet in the Account definition field for 05=Group clearing is interpreted with the following special features:
- Account master data the account ID1 is automatically set to 'I' for Intercompany, even if the account is not in the conversion table B3201 (or N0301, N0401 or N0501...)
- IC/Intercompany sub-account balances (currently the corresponding main accounts must also still be defined in table B3201 with account ID1 = 'I') the client no. from the <Affiliated company> field of the DCW sub-account is used directly for conversion to the IDL company. In all other cases, an attempt is made to find the DCW client master via the DCW address number, from which the IDL company is then retrieved.

If the N03 tables are already occupied by the customer, other names for IDL consis must be agreed individually. Further information can be found in the installation instructions for the DCW/IDL interfaces; they are documented on the IDL Konsis CD in the path DOKU\DCW.

**) For the correct transfer of balances, the current IDL account master must always first be provided on the AS/400 (IKOBMST), which is formed from the DCW account sheets plus additional information from the DCW/IDL conversion tables.
If this is not followed, the following error situations can occur:
- Missing carryforward values for balance sheet accounts due to missing balance sheet/P&L indicator
- Missing balance splitting for debtors/creditors/e-accounts receivable
- Missing reconciliation of IC/intercompany sub-account balances

The following balance logs are created and must be processed: 
1. list with - missing accounts in the IDL account master on the AS/400 - non-convertible address numbers in the sub-account area
2. list of balances
3. reconciliation log for <balance-turned-items>  with total balances across all clients of a company (corresponds to DCW DEF12)

On the DCW side, there is an additional interface option for providing plan balances in the same file formats as for account balances. If necessary, IDL should be addressed.

***)The transfer files are provided by default on the DCW side in the DCWM library, while the BICOBAL base table is managed as a DCW table in the DCWD library. After executing the transfer programs on the AS/400, the interface files mentioned are provided. A simple file transfer function is now required to transfer the staging files from the AS/400 to the local IDL\BATCH directory at the recipient (one file transfer icon per file at the client).

There is therefore a clear division of functions for the 3 phases:
1. provision on the AS/400
2. file transfer from the AS/400 to the IDL Konsis client/PC
3. transfer to the IDL consis client/PC

Further prerequisites that must be fulfilled in the DCW-Fibu organization for automatic transfer:

Note on the DCW client no. field:
1. if available, a distinction should be made between < real> and <unreal> DCW clients: real =  legally independent, accounting companies within the meaning of the German Commercial Code (HGB) unreal =  permanent establishments/branches that are only part of a legally independent, accounting company within the meaning of the German Commercial Code (HGB) It must be agreed in advance for the reconciliation in IDL Konsis whether this should take place under the key <IDL company no.> or <IDL company division>  . For further clarification of terms, use the action < Help/Application> of the IDL Konsis applications GES and UBR.
2. since company numbers must be assigned uniformly throughout the group, client master records must also be created in DCW for those companies for which accounting is not processed via DCW. These client numbers can then also be used as < Affiliated company>  for group clearing accounts as described below.
3. the chart of accounts no. for IDL Konsis is set in all DCW selection screens with DCW + XXX (= no. of the DCW group) by default, but can be overwritten if necessary.

Recommendation for account setup:
1 All <IC/Intercompany balance sheet main accounts>  are managed in DCW in all clients, i.e. uniformly across the group with sub-accounts.
2 All <IC/Intercompany main balance sheet accounts>  are assigned the account definition < Group clearing=05> in DCW.
3 All sub-accounts for these IC/intercompany main balance sheet accounts are provided with the corresponding client entry in DCW in the <Affiliated company>  field.

The following only applies if the above recommendation could not be followed:
- Client/company master data
- All group parent companies and subsidiaries as defined by the German Commercial Code (HGB) must have a unique DCW address number across all DCW clients and be assigned to the same DCW address group, especially when working with several AS/400 installations. This also means that all clients not billed via DCW must be set up as so-called < remote clients> in DCW.
The corresponding DCW address number must therefore be assigned in all DCW client master records
- All <unreal>  clients must be assigned to the same DCW address group as the corresponding 'real' client.
- If you are working with several group groups in DCW, e.g. to include foreign standard charts of accounts, and intercompany relationships are to be read out, it is necessary to enter the corresponding DCW address number for all group groups in this separate DCW/IDL client table N0302. (Table N0302 has been omitted since DCW Release 3.3.1)

Account sheets/account master
- The DCW balance sheet/P&L item allocations and structures to be used for IDL Konsis (1st struct. DCW tab. B0702, B0703) must be the same for all DCW clients (<real> and <unreal>) to be included.

Account balances
- The basis for the IDL consis data is always the DCW account level with
- Main account balances for all accounts and
- Sub-account balances with address numbers for
IC current accounts (balance sheet)
IC interchange of services (income statement)
IC group clearings
- This is based on the posting lines updated in DCW in the BICOBAL file
ATTENTION: Please note that the transfer of IC group clearings for a company/division can only be repeated correctly if the corresponding main account balances have previously been deleted and transferred again. Otherwise the data will be multiplied in the intercompany accounts with each run and reduced from the balance of the corresponding main account. - You should also check whether new intercompany accounts have been created in the company chart of accounts and in the group chart of accounts (7th digit of an account = "I") and whether the automatic assignments of these accounts to the income statement item are correct. They are generated by the system in the same way as the corresponding main accounts, without the "I" in the 7th position. If they are not included in the AE consolidation, the group processing indicator must first be removed from the group account and then also from the company account.

6 Starting the import via the command line

IDL Konsis provides the option of starting the import via the command line. To do this, the call

java -jar import.jar [options] 

in the "load" directory.

The "/help" option provides the following list of possible options with a brief description:

java -jar import.jar /help
usage: java -jar import.jar [options]
option: /help              this Helptext
        /mode=j|n          (j = jni, n = new socket)
        /debug             turn on debug output
        /i=...             ini-File Name
        /ServerLogDebug    turn on debug output into the logfile of the server
        /dbms=...          the dbms
        /dbname=           database name
        /username=         username
        /hostname=         appserver hostname
        /pass=...          the users pass word
        /port=             appserver port
        /modulname=        eg. TXTSALD, TXTANLBEW ...
        /filename=         eg.  KPKONTEN.txt
        /logfile=          logfile
        /jobid=            for running IEJobs,  the id number of job (in this case: 
FORMATNAME "#DB", FILENAME void)
        /formatname=       IEFID Import/Export-Format-Id   defined in application ALLCFLD
        /KTK=              <group/sub-group>        /CODT=              <company>        /BUDT=              <business unit>        /CLSDTE=              <closing date actual period>        /VABR=             <from period>        /FCT=              <chart of accounts>        /AGB=              <chart of positions>        /AGG=              <position>        /COADFN=              <chart of cost centers>        /KST=              <cost center>        /LGNCDE=              <language>        /UMS_GUI=          <transformation group>        /EX_FAC=           <ex fac>        /LANG=             language of messages: DEU (default) | ENG | USA | FRA | REPCLCDSC
        /MIT_VORTRAG=      <with carry-forward: X>        /IMPORT_WARNING_IGNORE=false|true (true: ignore all WARNINGS-MESSAGES, false= ERROR)

Example of starting a file import:

java -jar import.jar /i=C://Konsis//system//idldb.ini /formatname=#DSCTXT /modulname=TXTANLBEW 
/filename=c://tmp/anlbew_Import.txt /dbms=DB2 /dbname=IDLDB /username=idladmin 
/pass=idladminpass /logfile=//C://TMP//import.log /UMS_GUI=MEINE_UMS

Example of starting an existing IE job:

java -jar import.jar /i=C://Konsis//system//idldb.ini /formatname=#DB /jobid=100 /dbms=DB2 
/dbname=IDLDB /username=idladmin /pass=idladminpass /logfile=//C://TMP//import.log 
/UMS_GUI=MEINE_UMS

Special option "IMPORT_WARNING_IGNORE":

With this option and the value 'TRUE', any WARN messages from the import programs, which normally automatically become errors when importing via the command line, can be ignored. This corresponds to the "Ignore all" button when starting the import via the import menu. The check of the data record is then automatically continued until the next error or the end of the checks.

6.1 Error handling

It is possible to specify a log file in addition to the log in the /logfile= parameter. If this parameter does not contain a value, i.e. "/logFile=", the output is output to Standard Out. If this parameter is not specified, the output is written to <module name>.log as before.

This log file is written in addition to the log with technical details of the execution, including the return code.

The return codes are defined as follows:

0

error-free

200

technical import error

-1

Other error

-5

Login error

-202

File error

-203

Format not found

-204

Module not found

-205

Conversion group not found

-206

Error during job initialization

-207

IEJob not executable

-208

IEJob already started

java -jar import.jar /help 

outputs the help with all possible parameters for the call.