Avaloq ACCP (Complete Questions 2020)
From the avaloq course ACCP. Questions to all Chapters of all 3 Books
From the avaloq course ACCP. Questions to all Chapters of all 3 Books
-
- 1 / 248
-
Lernkarten
What is an Order Validation Check?
check to ensure all necessary data has been entered into an order (read-only, doesn't modify data), that can produce error/warning-messages
What is a rule-based workflow action?
Action with when...then...else Construct -> tests if a condition is true or false and then decides wheter state to transition into
In which source type the Workflow Commands are stored?
WFCL
An order has to be persisted when transitioning into a non-stransient state.
True
For what are Workflow Action Commands used?
Used to perform functions associated with a workflow phase
eg.: phase: work & command: chk_4_eyes
phase: create & command: init
phase: persist & command: store_obj ; store ; book
Workflow Definition: Actions contain of what 4 things?
- Attributes (descn, allow_direct_exec)
- Declaration
- Phases (csy_level, create, work, trans, persist, after_action)
- Commands (chk_4_eyes, store_obj, store, init, book)
Workflow Definition: States contain of what?
- Attributes (General attributes (descn, edit_status, csy_level) & Persist-driven attributes (book_status, obj_status...)
- Declaration (name ...)
CTX-Actions: for what do the parameters "i_seq_nr" and "i_proc" stand for?
i_seq_nr = define HIRA Position of the CTX-Action, i_proc = procedure that is executed
In the REP SCREEN source you should use "assign" and not "inherit" for variables.
True
The name of a hierarchical datamart in the REP DTM source starts with "dtm_"
True
A (flat) datamart created by a task provided by Avaloq is always customizable.
False -> NEVER customizable
A Task is a PL/SQL procedure made available in the User Interface (Smart Client)
True
A TASK DEF source represents the interface between the Kernel and Report definition layer. A TASK DEF source describes basic task information and all available task parameters in it.
True
You use the TASK TEMPL source for what?
The TASK TEMPL source stores the combination of a Task, Layout and the Filter Criteria.
Example: Task = bp_list, Filter Criteria = bp_name = "Roland", Layout = "SCREEN REP"
The task input parameters are passed to the TASK DEF source, which triggers a procedure to filter the data according to the parameters. Then it creates a flat datamart. This flat datamart can either be shown directly in a Report Screen, or can be processed in a REP DTM source, where it is converted into a hierarchical datamart.
Finally we can use a REP SCREEN source to define the Layout. Output = Screen Report of a BP-List containing entries, where the BP-Name is "Roland".
Multiple matching criteria can be set for a rule clause and these can have either AND or OR conditions.
True
The Condition between different clauses in a Rule Loader Table is AND.
True -> in other words, a rule is only executed if all matching critera are satisfied (not only one)
If the parameter OFFSET in the Cost Rule Engine is set to eg. "- 40" the cost are lowered by the given amount.
False -> "-" means costs that are charged! So the amount gets added to the Costs
The Cost Rule Engine has different parameters like: OFFSET, ROUNDING_1, ROUNDING_2, MIN_MAX(), FACTOR.
Sort them by their sequence!
ROUNDING_1 -> FACTOR -> MIN_MAX(), OFFSET, ROUNDING_2
In which DDIC are dynamic values stored?
In the BTT-DDIC
The Naming Convention for KEY DEF sources is: ...
ACD$"intl_id of code_obj_type"_INSERTNAME (eg. ACD$ADDR_INSERTNAME)
Derived Classifications are ...
classifications, which are automatically calculated/set through certain factors (eg. when domicile of a BP is Switzerland, the classification for Branch-Office is set to Zurich)
Order Keys and Object Keys are stored in the sourcetype KEY DEF.
False -> only Object Keys, not Order Keys
What is partitioning?
Instead of creating huge code tables (CODE TAB), we split them into smaller ones grouped by object type or businesstype
eg.: ACD$CODE_INSERTNAME.BP, ACD$CODE_INSERTNAME.CONT etc.
If a Kernel CODE TAB DEF source has no public range, it means the existing rows cannot be modified.
False -> it means a customization specialist cannot add rows to the CODE TAB table
Whenever you compile a CODE TAB DEF and CODE TAB source DDIC entries are generated (first time) or updated (all other times)
True
What means the term "any_status" and "any_row" in CODE TAB DEF sources?
any_status = ability to set rows to active/inactive (in CODE TAB)
any_row = ability to override values of any row (in CODE TAB)
CODE TAB source defines actual values stored in the table, while CODE TAB DEF defines metadata like columns, type of data (number, text ...) and which columns are mandatory or optional.
True
What is the Naming Convention for CDOE TAB and CODE TAB DEF sources?
ACD$CODE_INSERTNAME
The MDB is the new baseline for implementation projects, while the ABR/S is the old baseline.
False -> ABR/S is the new baseline and MDB the old
What is the difference between a procedure and a function?
A procedure re-calculates / creates something with methods/constructors, while a function returns a value (which can be used in a procedure)
PL/SQL accesses data via SQL queries, while Avaloq Script access data via DDIC's
True
The ASMD is used for sources in a Context as a Coding support.
True
The ADAI (Avaloq Database Automation & Integration) has what purpose?
enables the clients to manage their ACP development infrastructure through continous integration, quality assurance & automation tasks
DDIC's for Reports use the dtm_ || dtm_doc -Format
DDIC's for Code Tables / Extensions use the code_ || code_obj_extn / code_doc_extn -Format.
True
Not supported source types are stored in BTC sources or Component Config sources (this source type is installed first before all others).
True
API's do not speed up the development process, but the application.
False -> API's do not speed up the application, but do speed up the development process
API's enable external tools to interact with the ACP instance
True
A source can have exactly one status at a time and several attributes.
False -> only ONE or NONE attribute per source possible (corrupt, error, warning)
If a source type doesn't have a compiler it can only be installed.
True
The Avaloq Ice Workbench connects to two things: ...
- source repository (dev1 -> default database)
- Development instance (SAXX user)
