The condition category defines how the system calculates a condition (for example, charge or interest). Condition categories are the central element of financial conditions, which determine the basic functions of the conditions that are based upon them. You control the required and optional entries for determining and calculating a condition.
In the system, the properties of the condition category are defined by the assigned combination of amount categories , date categories and differentiation categories . A condition category can have several amount categories, date categories and differentiation categories.
Condition categories are fixed and predefined by SAP. They cannot be changed. Condition categories are assigned to a specific condition group category according to their use to prevent contradictory combinations.
The system uses the condition category to control the function for calculating a condition and makes available the input fields required for defining the corresponding condition.
If an amount category is assigned to a condition category, then the condition category can be used to calculate amounts. If a date category is assigned to a condition category, then the condition category can be used to calculate dates .
Note
For an overview of the assignment of condition categories, see the table FICOB_COND_DATE (Assignment Condition Category – Date Category) and FICOB_COND_AMT (Assignment Condition Category – Amount Category).
SAP provides many condition categories that can be used to define conditions for your application-specific business .
The following condition categories are available for cash flow conditions :
This condition category is used for interest with date updates determined based on the interest calculation capitals, and for the calculation, calling, adjustment and fixing.
This condition category is used for a defined cash flow for repayment of a loan. The repayment is independent of the specified amount. A total repayment is made at the end of the time period for final repayment. This repayment consists of the outstanding balance and any interest incurred. Another example for repayment that is not amount-based is repayment of capitalized interest, forwhich the capitalized interest is repaid without any repayment of the loan itself.
This condition category is used for a defined cash flow for repayment of a loan. The repayment is dependent on the specified amount. For annuity repayments, the amount is the constant total of repayment and interest. For installment repayments, the amount is the repayment amount, which always remains the same.
This condition category is used for a provision charge or interest determined based on the provision capital .
You use this condition category to display waiver conditions that are used for pricing conditions . This condition category is also used for payment conditons to display the amount of a loan installment and the corresponding time period .
The following condition categories are available for settlement conditions :
This condition category is used for interest calculation during settlement, and for conditions such as debit, credit and overdraft interest.
For example, this condition category is used for savings contracts with bonuses .
You use this condition category to calculate the permitted withdrawal for a PDM Plan dependent on the features and calculation methods. In doing so, you can define reference interest rates and markups/markdowns .
This condition category is used for charge calculation during settlement, and for conditions such as account maintenance charges or item charges .
You use this condition category to represent the disbursement charge for a loan, or for a one-time insurance premium. When the
Disbursement
event occurs, the system creates an individual condition for the settlement condition based on this condition category. The cash flow calculation uses this settlement condition to create the relevant calculation results. You can keep the items posted due to the settlement results when executing the
Disbursement
order .
You use this condition category to use Boolean operators to define condition determination for combined settlement, for example, with the aim of reducing charges .
You use this condition category to define automatic waiver conditions for pricing conditions . For more information about automatic waivers, see the Group Box Edit Automatic Waivers .
You use this condition category to define specific limits for each settlement period . The total settlement results for a condition type must be within these limits.
The system first calculates all conditions for the settlement period, totals the amounts for a condition type, and then compares the result with the amount limits. If the lower amount limit is exceeded, then the system should post the minimum amount defined in the
Amount Limits
condition. If the upper amount limit is exceeded, then the system should post a maximum amount. If the result falls within the limits, then the system posts the calculated amounts.
For more information about amount limits, see Edit Amount Limits .
You use this condition category to define specific limits for each
settlement period . The total settlement results for a condition type must be within these limits. The system determines the amount limits, as described for the condition category
180000 Amount Limits
.
The following example highlights the difference between the condition categories
180000
and
180001
.
The settlement period for an account is three months. The period of use is one month.
You have defined a minimum amount limit of EUR 10 and a maximum amount limit of EUR 30 for the
Item Charges
condition type. The following amounts are incurred for the account:
Item Counter/Month |
January |
February |
March |
---|---|---|---|
Cash Withdrawal |
EUR 3 |
EUR 1 |
|
Documented Transfer |
EUR 6 |
||
Online Transfer |
EUR 1 |
EUR 4 |
EUR 12 |
For the
Amount Limits
condition category, the totals are calculated for all item counters in the whole settlement period. The system determines the total of all three fields, which is then compared to the amount limits. The result is EUR 27. The system posts EUR 27.
For the
Amount Limits with Period of Use
condition category, the system determines the monthly totals for all item counters and compares each result with the amount limits. The result for January is EUR 4, so EUR 10 is posted. The result for February is EUR 11, so EUR 11 is posted. The result for March is EUR 12, so EUR 12 is posted.
For more information about amount limits, see Edit Amount Limits .
This condition category completes the data for loan accounts in
Account Management
with the settlement period. This information can then be processed by
Bank Analyzer
.
You can use this condition category as a template for settlement interest conditions. This template contains all the fields of a settlement interest conditions and makes it easier to create settlement interest .
You can use this condition category to define pricing conditions that are independent of the contract or the business partner.These condition apply to all contracts or business partners .
No calculation is made during settlement for all condition types that belong to this condition category. The info item amounts are unchanged and posted by the settlement. You would use condition types of this condition category for the charge collector in
Account Management
.
The following condition categories are available for transaction conditions :
You use this condition category if, for example, the customer makes an early withdrawal of savings deposits, meaning that a penalty charge is due to the bank. The interest penalty is linked directly to the credit interest. Dependent on the settings in Customizing, the maximum interest penalty could be the same as the credit interest, which means that the savings capital is not affected. If the interest penalty is posted in full irrespective of the credit interest, then the savings capital can be debited.
Note the difference to condition category
115070 (Early Withdrawal Penalty
).
You use this condition category if a charge is to be levied when a specific event or transaction occurs, such as account closure. As soon as the event occurs, the charge is posted to the contract master data .
You use this condition category to define a charge that is due when a payment item is posted for a specific transaction type/medium, such as withdrawal at an ATM .
For example, you use this condition category to define the penalty that is due if the customer makes an early withdrawal from a time deposit. The penalty can be a charge, an interest rate, or a combination of both. It is not linked directly to credit interest. The savings capital can be debited.
Note the difference to condition category
105040 (Early Withdrawal Penalty
).
This condition category is used to derive the value date from the posting date.
For more information about value dates, see Edit Value Date Condition .
You use this condition category for check deposits subject to final payment. You define the number of days for which the money cannot be withdrawn. For more information, see Edit Subject to Final Payment Period .
You use this condition category to define the expiry date of a prenote .
For example, if a customer wants to withdraw EUR 1,000 from his account, this amount can be reserved until a specified expiry date. If the money is not used, then the reservation is cancelled once the expiry date of the prenote is reached.
The following graphic shows the position of the condition category in the condition model :
You can see the possible combinations of condition category and amount category or condition category and date category under amount category and date category .