Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-SA-ALM (Application Component) Asset/Liability Management⤷
JBRA (Package) Risk Management: Asset/Liability Management
Basic Data
| Data Element | JBRSELDAT_ALM |
| Short Description | ALM: Horizon |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SYDATS | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Horizon |
| Medium | 20 | Horizon |
| Long | 40 | Horizon |
| Heading | 10 | Horizon |
Documentation
Definition
This controls which transactions the system selects for analysis in gap analysis and ALM simulation. The horizon date must always be >= than the evaluation date.
The evalation date and the horizon date are also used to control which market data is used in the analyses. The scenarios specified in the analyses are always valid on the horizon date.
Use
All real transactions that have been closed before or on the evaluation date (contract date <= evaluation date) and have not expired by the horizon date are included in gap analysis/ALM simulation
In addition the system selects all saved simulated transactions that exist up to the horizon date.
For more information on the horizon see SAP Banking -> SEM -> ALM -> Simulation/Planning -> Evaluation Date versus Horizon in the SAP Library.
Dependencies
Example
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in | 462_10 |
