Exporting Contract Data

This transaction can be used to export and compress a contract along with all dependent files from the database into a ZIP file. This makes it possible to provide stored data to the Support staff. In this way, they can better understand the nature of a problem so that they can solve the problem more easily.

The data can be imported in an appropriate test environment using the “Import Files from CONDBG” (GENDBI) transaction.

To set up a test environment for importing contracts, a basic data set of static data is needed. This contains entity groups, entities and entity addresses, the here used own parties with all corresponding data including accounts as well as currencies, countries, codetables and transaction profiles (ATP and ETP).

Using “Export Mode” 'Basic Package' this data set can be created. The path in which the ZIP file is to be created is displayed in the field File path for Export/ZIP by default. As a standard, the 'tmp' folder in the 'tmp' partition is the default setting. The name of the ZIP file is made up of 'basic_package_<timestamp>.zip'.

To export contracts the export modes 'One contract', 'All contracts of business sector' and 'subset of contracts' are available.

After selecting the business sector, the field “Reference No.” can be used to search for the desired contract. If the checkbox “Search via INR” is checked, the field “INR of the Contract” is displayed. In this case a contract can be searched via the INR (unique internal identification number of a record in a table).

Alternatively with export mode 'Subset of contracts' a “where clause” with the respective SQL selection conditions has to be entered.

Using the “Anonymize data” checkbox, the data content of the exported contract can be anonymized by pre-configured veiling processes. This can prevent e.g. the names or addresses of the parties concerned being displayed in plain text.

The following data groups can be exported:

consisting of

• Business sector tables xxD and xxT,
• for Export Finance also further (tables RZx, EAx, ERK, ECC)
• Parties (table PTS),
• Liability for the parties (table PTE),
• Contract balances (table CBS),
• General Ledger Entries (table GLE),
• Fee pool (table FEP),
• Relevant fees (table FEE),
• Fee conditions (table FEC,
• Limit system (LSx),
• Pool for foreign fees (FCP),
• Accruing records (ACx),
• Acknowledgments (ACK) and
• Settlement pool (SEP).

consisting of

• All transactions (table TRN),
• Documents (table SMH),
• Events (table EVT) and
• All files from the directory 'display' in the partition 'dokudisp'. If the data from the archive is to be exported as well, the checkbox “Include Archive” must be checked.

consisting of

• Open transactions (table SPT),
• Registration data,
• Workflow (tables WFE and WFS),
• Orders (table ORD),
• Events of the orders (table ORE),
• Transaction dependencies and signatures (tables TRS and TRO),
• All files from the directory bimdata in the partition data
• All files from the directory trndata in the partition data and
• All files from the directory delete in the partition data.
• All files from the directory sepdate in the partition data.

Files from some directories can be deleted in SRVCLN Service Cleanup in Task manager. They will be logges as missing.

consisting of

• tdpara.ini and cbsconf.ini in the ini partition

consisting of

• All files from the directory docs in the partition data. If the data from the archive is to be exported as well, the checkbox “Include Archive” must be checked.

consisting of

• Diary events (table DIA),
• Addresses of the parties (table PTA),
• Parties (table PTY),
• Addresses of the parties (table ADR),
• Mail instructions (table MLI),
• Entries of mail instructions (table MLE),
• Types of interest and interest data (tables IRS and IRT),
• the accounts (Table ACT) of the parties concerned saved to the database, and
• Object Infotexts (table OIT)

consisting of

• System modification log (table SLG) and
• the data from the log directory.

• If sub-contracts are present in a main contract, all data groups belonging to the sub-contracts and sub-sub-contracts, which have been selected for the main contract can also be exported. In order to do that, the checkbox “Export Sub-Contract” has to be checked.

At first a business sector has to be selected via the “Business Sector” combobox. Then a contract in this business sector has to be selected for export. The reference in the application for the contract can either be entered directly or selected via the Info transaction for the business sector. If the reference has not been entered in full, or if more than one contract corresponds to the data entered, the system displays the contracts found in a selection list. The particular contract can then be selected from this list.

The data set groups to be exported - and any sub-contracts which are also to be exported - can only be enabled/disabled after the contract has been selected.

If a sub-contract is selected, the main contract can be found by clicking on .

The path in which the ZIP file is to be created is displayed in the field File path for Export/ZIP by default. As a standard, the 'tmp' folder in the 'tmp' partition is the default setting. The name of the ZIP file is made up of <Contract INR>.<Business sector>.zip.

Click on the icon to create the ZIP file.

Via the icon , the ZIP file entered can be transferred to the local PC. The storage location on the local PC can be defined in the popup dialog box. The button [ Copy] is used to copy the file on the local PC. Clicking [x] closes the popup dialog.

By clicking the user can view all the events which have been carried out since the start of the transaction.

The subdirectories in TMP will be deleted automatically after the ZIP process, because these files are not needed any more afterwards.

Since sensitive data could possibly be dispatched with the ZIP file that only authorized recipients are allowed to be able to read, the data can optionally be encrypted using a password. The password desired is to be entered in the relevant field. Only if this password is known will the data be capable of being imported into the desired test environment at a later date.

Export of Contract Data