The Application System parameters reference a specific system setting. System parameters help in configuring system specific data, User-access, location of system files and other administration controlled data. 

To maintain System Configurations in the Application, DBISYS transaction is used.

Select it from the menu item[Basic Settings -> System -> General System Settings]. 

(Administrator and designer users can directly start this transaction by clicking the(Launch transaction ) available in the Panel headline without having to select the relevant menu) 

The following transaction Panels are available in the System Configuration,

• System Settings 
• Message Parameters
• Letter Layout
• Service Level Agreement
• Static Data
• Regulatory
• Technical E-Mail Settings
• Compliance
• SCF

System Settings: 

System parameters contain definitions, for example, of the languages available, the system currency, the names of the days and months for date insertions, the fonts to be used as well as other display settings

Deactivate Limit system - If the checkbox is set the limit system for all business sectors as well as corresponding services in the Task Manager (MGRTSK) such as 'Limit Check (PDL)' are deactivated.

Use Syndication Business Module - This flag describes if the new syndication business module should be used.

License expiry warning (Configuring Notification Period for Security Key Expiration) - Admins can define how many days in advance users should be notified before their security key expires.

If no value is configured, the system defaults to 10 days.

Able to set a custom notification period anywhere from 1 to 99 days.

The number define will overwrite the system default.

Compliance - Compliance can be activated in the static data transaction Maintaining System Configuration, the combo box “Compliance” allows the following options:

Compliance Old (this option is using the built-in 'old' compliance functionality)
Compliance to External System (this option is interacting with an external Sanction-Screening-System, such as WOLF)
Compliance via RIVO (through the use of RIVO as a middle point ; this option allows the interaction with an external Sanction-Screening-System, such as LESTR)
Compliance to Trade AI (this option is interacting with Trade AI which is an external Sanction-Screening-System)

Compliance to External system – Previous “Alternative Compliance active” has been renamed. The functionality remains the same.
Compliance to Trade AI – This option is for interacting with the external compliance/sanction screening system Trade AI.

The interfacing system is RIVO for “Compliance via RIVO” and the external compliance system being Trade AI for “Compliance to Trade AI”

Activate GLE-Entries for Accruing - 

The GLE table holds all the general ledger entries created in a business contract. If Activate GLE-Entries for Accruing checkbox is ticked, system is  enhanced to generate and display the accounting entries of Accrual (accrual in case of commission to be settled at end / amortization in case of
commission settled in advance).
These entries will now be available in the GLE bookings of a contract. It can be viewed
from the info view of a contract, in the GLE Bookings panel. The accrual entries will be
displayed in both contract currency and system currency.

Message Parameters:

A message communication channel is deactivated by removing the tick in the Active column of the table on the message parameter panel. In the deactivated format no messages is created when processing business transactions.

Autoconvert Standby L/C message : The free format message for Standby L/C’s is generated in two different formats/structures,  Free format message & Original message structure.

Letter Layout: 

The Letter Layout panel contains a number of settings made to enable outgoing correspondence on letterheads that is adjusted to the bank's corporate identity parameters in terms of fonts, structure and layout.

Service Level Agreement:

The panel contains the time parameters( for instance Processing time, Release time, Manager proc. time, SLA limit, Cut-Off time, Buffer time, Diary time, Order Workflow Time,...)    that are used for processing and settlement of an order.

Default values for Service Level Agreements are defined here.

Static Data:

The activation/deactivation of the 4 Eye Control for static data systems is done in this panel.

Regulatory:

The CBPR+ functionality is activated via a central switch. Banks can switch on / switch off the new functionality prior to the go-live date and thus view and test the functionality early.

• Swift interbank payment messages are by default generated as Swift MT messages.
  If activated Swift payment messages are generated as MX messages in XML from the given date.
  MT payment messages and MX (CBPR+) payment messages cannot be generated in parallel by this application.
  For production: The bank using application can decide to activate the functionality at any date between 20. March 2023 and 20. November 2025 to switch from MT- to MX-payments.
  The latest activation date for MX (CBPR+) payments is Sunday, 23. November 2025.,
• Swift 2025 Activation on.
• Fully Structured Address on.
• Swift 2026 Activation on.

For example if the dates are set as shown in above screenshot: In order to test the Fully structured address format, use transaction “Set system date (GENDAT)” to move to a date on or after 21.11.2026
In order to test the Hybrid structured address format, use GENDAT to move to a date on or after 22.11.2025, but not later than 20.11.2026.

 The full logic will be activated for all correspondence channels, 

• Swift Interbank MT 
• Swift Score 
• DTA, DTE, DTG 
• Bolero messages

When you have made your changes, click on the ()  Save function to save all the the data entered in the transaction to the database.

SCF Configuration

Integration/set-up for Front end demo system:

This Panel used to Maintain System Configuration (DBxSYS) as a placeholder for managing interface related configurations for different front end systems in the future. Currently a combo box field has been placed to select the required front-end system. This is a placeholder for future use.

SCF Front-end interaction

Program Set-up (Doka) :  Program along with limits and fees at a program level is set-up in DOKA.
This information can be shared with the Front-end system.

Supplier Onboarding (Front-end) : Once the program information is shared, the front-end system can set up the program and invite its suppliers to join the program.

Activate Pairing (Doka):  The supplier then onboards to the program following the terms and
conditions have been accepted.

Invoice upload and Approval (Front-End) : The supplier can upload invoices in the front-end system and the buyer can approve these invoices.

Financing and Repayment : When the invoices are received in DOKA, the discounting of these invoices to the supplier happens through Straight through processing. On the due-date the buyer settles the advance amount.