This transaction is used to maintain entities. Entities are independent units within the current installation. Typical entities include branch offices, for example.

The following transactions can be started from here by clicking the icons in the list below for:

• Adding an Entity
• Modifying Entity
• Deleting Entity
• printing entity(ies).
• creating Entity List
• showing Version Log of the modifications to the entity(ies).

Basic settings such as the bank's own party or the system administrator for the entity are stored for the entity. Other address details, such as the bank's own BIC, are stored in the Entity Address ( see “Maintaining Entity Addresses”).

The optional field “Default Calender” defines an entity-specific calendar to be used for calculating dates based on working days. It is used e.g. in the collapsible calendars in date fields or for internal functions if no asssigned calendar has been defined. If no calendar is specified, then the system calendar defined in tdpara.ini is used by default.

A dedicated document stylesheet in which the specific entity page layout (e.g. margins, size definitions of headers and footers) is entered can be used for each entity. An XSI file is assigned to each XML panel defined in a transaction. In the standard version, for instance, for most documents this will be 'A4.xsi'. Should it be necessary to set up an entity-specific document stylesheet, it is not necessary to adjust the XML panel properties in each transaction / each message. If a value 'xxx' is entered in the “Postfix for XSI file” field, which may be the abbreviation of the respective entity, for example, the file name of the file to be used from time to time is automatically augmented, i.e. into 'A4xxx.XSI'. The corresponding XSI file must be created with transaction “Maintaining Document Formattings” (DBIXSI). If a field is blank or a file does not exist, the default value of the document (e.g. A4.XSI) will continue to be used.

The fields “Top logo on the right” and “Lower logo on the right” define the pictures to be shown right to the workspace.

Own logo files can be uploaded using the icon right to the relevant field.

The entity's default printers can be defined in the “Printer” table at the bottom of the panel.

Once selected, an existing entity can be edited by clicking the icon. All data fields can be modified. Since the administration of entities can have a major impact on other system settings, they should be done very carefully together with a member of the support team.

Opening Hours Panel

If the “Manager for interactive Queue Entries” (QUETSK) is used for the queue system to distribute the workload to be handled to the employee resources still available or if Service Level Agreements are to be supported, the working times of the entity should be known.

If the working times of the entity differ from those of the superordinate entity group ( see “Maintaining Entity Groups”), the usual working times may be defined for the entity selected for each weekday. If the fields “Start Time” and “End Time” are filled for specific days, then the difference in hours is automatically calculated. For weekdays on which the entity is closed, the checkbox “Closed” must be checked. It is sufficient to specify the dates of the days on which deviations exist.

If, in turn, individual users have working times that differ from those of the entity (group), then these can be stored in the User profile ( see “Maintaining User Profiles”) of the user in question.

Routing Information Panel

Incoming messages for an entity can be routed to a defined department for each business sector and/or channel. This routing only works if the message cannot be assigned directly to an existing contract. Also, routing definition specified on Hub level will win over the routing definition of the entity. Similarly, routing definition specified on Paryt level ( see Maintaining Parties) will win over the routing definition on the entity.

Past Due Settings

Settings to define Past due stages for a finance/loan contract can be done here. If it is not defined here, the settings defined in Entity Groups ( see Maintaining Entity Groups) will be made applicable for loan contracts. If it is defined in both entity group and entity, then the settings defined here in entity take precedence. Detailed information on this can be found in Past Due Loan.

Entity
Fee Conditions
Opening hours
Routing Information
Past Due Settings