Hierarchy
⤷ FS-RBD (Application Component) Value Adjustment
⤷ /IBS/RB (Package) iBS: Reserve for Bad Debt
Basic Data
Data Element | /IBS/E_CFCAT |
Short Description | RBD: Cash Flow Categorization |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /IBS/O_CFCAT | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | CF Cat |
Medium | 15 | Cash Flow Cat. |
Long | 20 | Cash Flow Category |
Heading | 6 | CF Cat |
Documentation
Definition
Cash flow categorizations are used to categorize cash flow categories. The following fixed values are available:
Cash flow categorization Description
01 Cash flow position (automatic)
02 Expectation (manual, temporary)
03 Cash flow Position (manual, temporary)
04 Expectation (manual, permanent)
05 Cash flow position (manual, permanent)
10 Utilization (automatic)
11 Utilization (manual, temporary)
12 Utilization (manual, temporary)
Use
You use the cash flow categorization in the RBD account dialog to define which cash flow categories can be created and deleted manually. You define and categorize cash flow categories in the Customizing activity Define Cash Flow Category.
- Cash flow categories that are defined using cash flow categories 01 to 05 are used in the valuation sheet on the 'Cash Flow' tab pages for calculation of the 'provision' and 'value adjustment' risk provision balances.
- Cash flow categories that are defined using cash flow categories 10 to 12 are used in the valuation sheet on the 'Utilization' tab pages for calculation of the 'provision' risk provision balance.
Dependencies
Cash flow categorization Description Procedure for Subsequent Evaluation
01 Categorization 01 identifies automatically supplied cash flow positions. They cannot be created or deleted in the RBD account dialog. The only thing that you can change in the RBD account dialog is the "percentage expectation used" for the cash flow position.- -
02 Categorization '02' identifies cash flow positions that can be created and deleted in the RBD account dialog. When you create a cash flow position, you must define the due date of the cash flow position and the expected amount (in the currency of the source system contract). The system changes the percentage expectation to 0% because you must enter the expected amount directly. Cash flow positions are only copied to the new evaluation sheet during subsequent evaluation if their due date is on or after the key date of the subsequent evaluation.
03 Categorization '03' identifies cash flow positions that can be created and deleted in the RBD account dialog. When you create a cash flow position, you must define the due date of the cash flow position, the amount (in the currency of the source system contract), and the percentage expectation for the cash flow position. The system calculates the expected amount by multiplying the amount of the cash flow position by the percentage expectation and displays the result. Cash flow positions are only copied to the new evaluation sheet during subsequent evaluation if their due date is on or after the key date of the subsequent evaluation.
04 Categorization '04' identifies cash flow positions that can be created and deleted in the RBD account dialog. When you create a cash flow position, you must define the due date of the cash flow position and the expected amount (in the currency of the source system contract). The system changes the percentage expectation to 0% because you must enter the expected amount directly. Cash flow positions are always copied to the new evaluation sheet. If their due date is before the key date of the subsequent evaluation, the system overwrites the due date with the new evaluation key date..
05 Cash flow positions of categorization '05' can be created and deleted in the RBD account dialog. When you create a cash flow position, you must define the due date of the cash flow position, the amount (in the currency of the source system contract), and the percentage expectation for the cash flow position. The system calculates the expected amount by multiplying the amount of the cash flow position by the percentage expectation and displays the result. Cash flow positions are always copied to the new evaluation sheet. If their due date is before the key date of the subsequent evaluation, the system overwrites the due date with the new evaluation key date..
10 Utilization positions of categorization '10' identify automatically supplied positions for defining utilization of the contingent liability (relevant for calculation of the risk 'provision'). They cannot be created or deleted in the RBD account dialog. -
11 Utilization positions of categorization '11' are used to define the utilization of a contingent liability (relevant for calculation of the risk 'provision'). You can create and delete them in the RBD account dialog. When you create a corresponding utilization position, you must define the due date and the expected amount of the utilization position (in the currency of the source system contract). Utilization positions are only copied to the new evaluation sheet during subsequent evaluation if their due date is on or after the key date of the subsequent evaluation.
12 Utilization positions of categorization '12' are used to define the utilization of a contingent liability (relevant for calculation of the risk 'provision'). You can create and delete them in the RBD account dialog. When you create a corresponding utilization position, you must define the due date and the expected amount of the utilization position (in the currency of the source system contract). Utilization positions are always copied to the new evaluation sheet. If their due date is before the key date of the subsequent evaluation, the system overwrites the due date with the new evaluation key date..
Example
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |