ACP (Comprehension Checks)
ACP (Comprehension Checks)
ACP (Comprehension Checks)
Set of flashcards Details
Flashcards | 250 |
---|---|
Students | 32 |
Language | English |
Category | Computer Science |
Level | Other |
Created / Updated | 30.11.2013 / 25.06.2022 |
Weblink |
https://card2brain.ch/box/acp_comprehension_checks
|
Embed |
<iframe src="https://card2brain.ch/box/acp_comprehension_checks/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
Yes
Yes
Correct answers are: a) & d)
Credit card charge, fund transfer charge, discretionary portfolio management fee, brokerage fee (railway ticket, car rental, flat rental, parking fee, cinema ticket, flight ticket). fee, cost, fee, cost
Constant method, linear method (offset and slope), degressive method, minimum/maximum, discount
Using the CODE_BOOK and COST_RULE table, Constant method -> offset, Linear method -> offset and factor, Degressive method (boundaries, offset, factor and graduated), Minimum/maximum (Minim_Maxim), Discount
The sum of minimum and offset.
Without graduation: Enter different factors in a set of rules AND define different offsets. With graduation: Enter only different factors in a set of rules and set the field graduated. The offsets will be calculated automatically.
Cost rule loading, evaluation of COST_RULE, verify, bookings are done
# rules per book kind * #Book Kinds * #Business Units N rules per book kind for each business unit.
Definition of cost master data (CODE_BOOK_KIND) and definition of cost rules (COST_RULE_LD).
ID, USER_ID, INTL_ID, ACTIVE
We use task 762 "Cost Rule Loading" and specify the rule set, business unit and booking kind.
No. Depending on the meta type and order type, different attributes are sent to the Cost Engine. Details can be found in the document attached (chapter 6).
Business Partner (Client), Business Partner (Bank), Container, Positions, Assets
Booking is real-time <-> balancing is on demand. Booking changes positions <-> balancing shows positions. Booking is done on money accounts and interim accounts <-> balancing on balance accounts. Booking is done on positions <-> balancing is the process of aggregating and valuating positions with the help of balance accounts
Primary bookings are implemented by Avaloq or predefined by the order. Rule-based bookings are the subject of parameterisation.
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")
Legal contract, external reporting (bank statement), interest calculation, keys, classification vs. No account statement (internal reporting), no interest calculation, no keys, no classification
Debit = Credit: The total quantities of all event packets (bookings) of defined assets involved in one event (transaction) must be balanced. The Book Engine implements this check with a catch all rule and generates bookings on the difference accounts if necessary. Net positions: Details are booked on net position and only the total amount is booked to the money account of the customer.
An order is booked as soon as it is verified (transaction-based). An order is booked definitively when the value date is reached (value date-based). Revaluation is possible for value date-based booking.
PKOs are booking dimensions. Different Book Engines, i.e. different booking logics can be defined for different PKOs. This can lead to different positions in the different PKOs. If Multi GAAP is applied, multiple balance structures and book engines are defined on different PKOs. Where lot accounting is applied, a position is composed by one or several lots.
If you want to book to the accounts of all branches you can use the placeholder B in the Destination field of a booking rule (indicating to which account a transaction is booked).
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.
#rules in one set * #Business Units (*# PKOs) 50
Defining the book rules (BE_BOOK_RULE_LD), the asset mapping rules (BE_ASSET_MAP_RULE_LD) and the position rules (BE_POS_RULE_LD). (For each: define, load, error check, test)
RULE_SET, TYPE,
The task 598 "Booking Rule Loading" requires you to define the rule set and the business unit.
var x number; exec k.balstru#.put(x_id => :x, i_name => 'BALSTRUXX', i_bp_id => 9, i_key_sym => 'AAAXX')
You can build a chart of accounts with the BALACC_LD loader table after you have created a new Balance Structure with an API. You can create a Balance Engine by creating a chart of accounts and loading its balancing rules (with BALSTRU_RULE_LD).
A chart of accounts consists of an object (with object type 12 BALSTRU) and all the alance accounts (object type 13). The lowest balance accounts in a chart of accounts are called leaves, the others are called owner.
The position pillar and in some cases the collateral pillar are needed to calculate the balance pillar. To show the balance you need the balance pillar.
#rules in a set * #balance structures N for each balance structure.
Create an object called a balance structure. Enter the chart of accounts (BALACC_LD). Define the balancing rules (BALSTRU_RULE_LD).
With an API (balstru#.put).
BALSTRU ACTION ACCLEVEL OWNER SYM CRED_DEB NAME_XX RULE_SET SEQ_NR VAL_TYPE CRED_DEB BALACC_P PRIO, PRIO_A, RULE_A
Balance Account Loading (615) Balance Structure Rule Loading (599) Balance Structure Rule by Balance Account L (612) Balance Sheet (214)
The grantor grants the rights to the grantee. The grantee inherits the rights from the grantor.
Passwords can be reset on the User tab in the Central Services Desk. Provided you have suitable access rights, you can right click on a user displayed on the screen and use the Reset password context action.
He inherits the strongest general access right of his grantors.