SAP ABAP Data Element JBSALFD (Due Date Scenario)
Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   IS-B-RA (Application Component) Risk Analysis
     JBRC (Package) Customizing for SAP Banking Risk Management
Basic Data
Data Element JBSALFD
Short Description Due Date Scenario  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type JBSALFD    
Data Type CHAR   Character String 
Length 3    
Decimal Places 0    
Output Length 3    
Value Table JBRALFD    
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 DueDteSc. 
Medium 19 Due Date Scenario 
Long 25 Due Date Scenario 
Heading DueDteSc 
Documentation

Definition

The due date scenario can be used to control the future course of a position.

Use

Dependencies

Example

Supplementary Documentation - JBSALFD 0001

Use

You are able to store a different due date scenario for each portfolio hierarchy node. The due date scenarios selected here will be used within ALM simulation for all actual transactions and all saved simulated transactions in the portfolio hierarchy node. The percentual outflows and inflows contained in the due data scenario (% of the initial amount on the start date) can be based on empirical values and should add up to 100% of the initial amount in a due date scenario if a total outflow is assumed.

Dependencies

Example

Supplementary Documentation - JBSALFD 0002

Use

By assigning a due date scenario to a valuation rule you are able to define time intervals for the outflow and accumulation of transactions without fixed terms (variable transactions). The assumed percentage outflows/inflows (% of the initial amount at the start date) can be based on empirical values and should add up to 100% of the initial amount in a due date scenario if a total outflow is assumed. Variable transactions to which no due date scenario has been assigned by means of the valuation rule, fall 100% due on the evaluation date in the case of NPV analysis and on the horizon date in the case of gap analysis.

Dependencies

Example

History
Last changed by/on SAP  20011002 
SAP Release Created in