AVQ Zusammenfassung Homepage www.cram.com Teil 2
Karteikarten aus Seite http://www.cram.com/flashcards/export/2711515
Karteikarten aus Seite http://www.cram.com/flashcards/export/2711515
-
- 1 / 170
-
Lernkarten
Business Partner, Container, Country, Address, etc.
No, a static data order generates or modifies objects. Events are generated by a transactional order.
– Memory DDIC, Table DDIC, Datamarts, Pillar DDIC
– Fields, Methods, Constructors
Has to be in upper case letters: Academy à Message #3 is "Has to be in upper case letters:"
number
The first ID is retrieved directly out of the uppermost level of the DDIC. The second is retrieved out of the business object residing persistently in the database. The third expression is syntactically wrong, because the result is a link to a obj_curry b
The definition of order validation is to check the validity of an order and to inform the user of a constraint which is violated. However, since Avaloq Script is used in an order validation source, you could – but you should never change data!, he use of
– Header, Constraint, Check, Footer
Check in the Docu ID 1055, chapter 5.
Show the order fields, which can be filled in by default rules.
Avaloq Script can be used in the Matching Criteria fields, the COND field and the RESULT field.
With and; i.e. if 'matching criterion' and if 'matching criterion' and if ... then ... .
Priorities determine which rule is checked first and which ones will follow next.
The system checks the rules in the lowest sequence first, e.g. 1, then checks the rules of the next sequence, etc.
The outcome is unpredictable. Avoid this situation by always setting clear priorities.
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 of a kind can be active.
Business specifications are defined. Rules are deigned and entered in the correspondent Rule Loader Table. The rules are loaded with the task that is specific to this Rule Loader Table. If there are no errors, the rules are entered in the Rule Table by th
In the Avaloq GUI only one set can be loaded at a time.
It may be important to think about performance, i.e. the case that occurs the most should have the highest priority.
– not recommended: delete the rows in the table, recommended: create a new set without these rules, recommended: load an empty Rule set
Mr Willis:BP, bp_symbol=MRWIL, Stock Exchange: intl_id_stex, Medium: field intl_id=medium, values: fax user_id=1, intl_id=fax, etc.
Cost
Cost
Fees
Fees
Defines the minimum/maximum value of cost. (Added to the Offset!)
Defines if different rules with the same book kind and matching criteria are aggregated or not.
The QTY_TYPE field is taken out of CODE_COST_QTY_TYPE. It defines for example, a tariff is calculated on number of shares or on the gross price.
When a process is very system specific, it usually is workflow driven.
– 0 Start, 65 Rejected, 80 Ready for print, 90 Done, 91 Discarded, 92 Storno, mandatory are: 0, 90 and 91
Translations will be done in table OUT_TEXT.
Workflow Actions, Avaloq Script Packages, Reports and Tasks
Yes
The right mix of general and specialised orderbooks makes the difference. Depending on the usage, both make sense.
Order Validations are triggered by workflow execution.
Constraints are built by parameterising persons on specification done by the bank / client.
Workflow –Status, –Actions, –Commands and –Rules.
One Orderbook is the absolute minimum. Depending on the workflow, it makes sense to have an Orderbook per status or for a group of statuses.
The combination of expert knowledge and a knowledge interpreter is called an engine. There are engines for instance for bookings, for balancing, for costs and fees., n difference to procedural programming languages, where code is defined statement by stat
