AVQ SWISSC

Workflow actions, Packages, Reports und Tasks

mittels SQL Skritp mit Verwenderung API -->  Insert into...

a und d

Vernwenden von CODE_BOOK und COST_RULE Tabellen

• Konstate Methode = offset
• Lineare Metode = offset und factor
• Degressive Methode = boundaries, offset, factor und graduated
• Min/Max = min/max

Konstante Methode, Lineare Methode, Degressive Methode und Min/Max sowie Discount Methode

Summe von Minimum und Offset

1. non- graduated: Eingabe unterschiedlicher Faktoren im Refelset UND defnieren von unterschiedlichen offsets
2. graduated: Eingabe unterschiedlicher Faktoren im Refelset

• Booking passiert Real-Time, balaning bei Anfrage
• Booking verändert Positione, Balancing zeigt Positionen
• Bookings werden mittels Moneyaccount oder interim Accounts gemacht, Balancing mit balance account

Primary Bookings werden durch Avaloq implementiert oder durch ein Order vordefiniert. Rule-based bookings hingegen sind Bestandteile der Parametrierung

money accounts: Vertrag, externes Reporting (bank statement), Zinsberechnung, Key und Klassifikationen

interim accounts: internal Reporting, keine Zinsberechnung sowie keine Keys und Klassifikationen

1. Debit = Kredit
2. Alle Buchungen werden Nettoverbucht, nur der Total amount wird dann Brutto auf dem Konto verbucht

• Ein Order wird so schnell wie möglich, also sobald er verifiziert ist gebucht (transaktionsbasiert)
• Ein Order wird definitivb gebucht wenn das Gültigkeitsdatum eintritt (value datebasiert)

1. Definierten der Book Rules (BE_BOOK_RULE_LD)-> define, load, error check, test
2. Mapping Rule für einzelne Titel definierten (BE_ASSET_MAP_RULE_LD) -> define, load, error check, test
3. Postition Rule definieren (BE_POS_RULE_LD)

• RULE_SET
• TYPE
• Matching Criteria
• BOOK_KIND
• DEBCRED
• QTY_SGN
• DESC
• SEQ_NR
• PRIO
• PRIO_A
• RULE_A
• RULE_ID
• ERR

– Select the task to be used to provide the flat datamart, Select a layout type, Write the hierarchical datamart definition or use an existing one, Write the layout definition based on the hierarchical datamart, Compile, check results and debug

A flat datamart is the temporary view on the data provided by the referenced task. Which data can be accessed is defined by the flat datamart definition.

Each task, which supports a certain flat datamart, can be seen in DDIC: Tasks are referenced by flat datamarts.

Yes, it is. (But not at the same time! Several tasks may be used to fill one DTM, but at parameterisation time, one of the possible tasks has to be selected for a specific report.)

One. A report datamart is connected to exactly one flat datamart but may on the other hand be enhanced by referring to other DDICs in the report definition (e.g. obj_bp, obj_asset, …).

Screen, File, Print, Script, Table

An application provided by Avaloq which creates hierarchical datamart definitions and screen layout definitions based on interactive input by the user. Theses sources may be used as a template for further refinery.

Screen Report (REP SCREEN)

File report (REP FILE)

Yes. A report's developer may design any kind of file (if he knows how to do so…). One of the most common usages of file reports is generating XML–files which are further processed in other systems.

Print reports generate PostScript files which van be directly interpreted by any PostScript printer.

The fields represent the values of a certain business object, which are held in a table on the Avaloq server.

No. A form in bound to exactly one business type.

The data source 'doc' stands for an order of the bound business type (e.g. Mem_doc_bp).