Avaloq ACP

#rules in a set * #balance structures N for each balance structure.

No. Reverse-compilation is only possible for descriptive Avaloq sources, not for those which create or contain PL/SQL.

Balance Account Loading (615) Balance Structure Rule Loading (599) Balance Structure Rule by Balance Account L (612) Balance Sheet (214)

Yes

A workflow action triggers a change of the workflow status. For each workflow status, exactly one event status can be defined. A change in the event status triggers the Book Engine.

In ICE under the instance tab, or in the Central Services Desk.

Yes, we call these functions in Avaloq the field validation and the order validation.

Views are parts of the user interface for data display and manipulation. A perspective is a certain arrangement of the views in the user interface.

notify

A rule set is a group of rules that belong together. A rule set must model the whole business situation in that context. Only one rule set for each RULE_KIND can be active.

Yes, with Avaloq Script (e.g. in order validation, reports, etc.)

E.g. Workflow, Costs, Accounting, Default Accounts, Default Field Values

With an API (balstru#.put).

a) Excel sheets (OMD), b) scripts like genwfc

To check the new developed or updated source code (Quality check).

The outcome is unpredictable. Avoid this situation by always setting clear priorities.

With a label which must be defined via out_text_norm. There is no direct naming possible.

Order validations are triggered by workflow actions.

SEC_*_ACCESS

Credit card charge, fund transfer charge, discretionary portfolio management fee, brokerage fee (railway ticket, car rental, flat rental, parking fee, cinema ticket, flight ticket).

Wherever there is a context menu on the Avaloq GUI (Graphical User Interface) available and the user has the access right to perform this context action.

Task, flat datamart, report/hierarchical datamart, layout definition.

Business specifications are defined. Rules are designed and entered in the corresponding rule loader table. The rules are loaded with the task that is specific to that rule loader table. If there are no errors, the rules are entered into the operational rule table by the system. The output can then be tested in Avaloq.

Override codes are parameterised in the code_override table, using the code_override source

This string is displayed, where this form is listed in the menu.

There will be an error message on the screen or an entry in the error log table. No rules of the set are loaded the rules within Avaloq remain unchanged.

Generate counter bookings Check posting differences (bookings must be balanced). Check posting check rules (e.g. "Costs should be debited"). Ensure position rules (e.g. "Blocked or pledged positions cannot be debited"). Enforce Short position rules (e.g. "short positions are not allowed")

If a source is not accepted by Oracle, the status is set to "corrupt".

Block structure Modularity Separate compilation

The task 598 "Booking Rule Loading" requires you to define the rule set and the business unit.

BALSTRU ACTION ACCLEVEL OWNER SYM CRED_DEB NAME_XX RULE_SET SEQ_NR VAL_TYPE CRED_DEB BALACC_P PRIO, PRIO_A, RULE_A

WFC_STATUS, WFC_ACTION, WFC_RULE_LD and WFC_RULE

Classifications and classes, keys, additions, remarks, relations, collections.

Sources which have a "+" in the source type field "CODE_SRC_TYPE.REV_