SAP ABAP Data Element FTI_UEBMO (Overdue Period in Months)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FIN-FSCM-TRM-TM-IS (Application Component) Information System
     ⤷ FTI (Package) Application development R/3 Treasury information system
Basic Data
Data Element FTI_UEBMO
Short Description Overdue Period in Months  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type NUMC3    
Data Type NUMC   Character string with only digits 
Length 3    
Decimal Places 0    
Output Length 3    
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 Overd.Mths 
Medium 20 Overdue (Months) 
Long 40 Overdue Period in Months 
Heading 13 Overdue(Mths) 
Documentation

Definition

Difference between a date field and the end of the term of a financial product. The date field can contain:

  1. A fixed reference date (entered in the selection screen)
  2. Today's date
  3. The key date of the position

UEBTGK = MX0( DATUM - DELFZ )

The "remaining term" and the "overdue period" are available as both reporting characteristics and key figures. You can use the respective key figure (available in days) for calculations. By contrast, the characteristic (available in days, months, and years) is primarily intended for defining forms. You can use it to group items that have recently become overdue, and those that are long overdue, for example.

The remaining term and overdue period have both been defined for positions and flows.

Both the remaining term and the overdue period are determined by calculating the difference between two date fields. The following section describes how these date fields are filled.

One of these date fields depends on whether the value is a position or a flow:

  1. For positions, this date field contains the end of the term for the financial product. If this is not defined (as is the case for stocks, for example), the remaining term and the overdue period are set to zero.
  2. For flows, this date field is filled with the due date.

The other date field

  1. The following dates are available for positions:
    1. An explicit reference date, which has to be specified (for example, 12/31/2002)
    2. Today, i.e. the current date
    3. The characteristic "Key Date", which can differ for each position (this is often clear in the context of the report)
  2. The following dates are available for flows:
    1. An explicit reference date, which has to be specified (for example, 12/31/2002), as above
    2. Today, i.e. the current date, as above
    3. The Day Before "From Date", which can differ for each flow (this is often clear in the context of the report)
    4. The "To Date", which can differ for each flow (this is often clear in the context of the report)

The remaining term and the overdue period are opposing values in the sense that one value has to be zero if the other differs from zero. However, both values can be zero at the same time. Both values have been defined as the difference between the two date fields above.

Example:
You want to calculate the remaining term or overdue period for planned flows. For the second date field, you specify a fixed reference date "12/31/1998".

  1. Due date = 01/05/1999 -->
    • Remaining term = 5 days
    • Overdue period = 5 days
  2. Due date = 12/29/1998 -->
    • Remaining term = 0 days
    • Overdue period = 2 days (if the flow has not yet been posted and has not been reversed)

Special case:
The following logic applies for position trend lists:

  • Records that change the position: The above rules for flows apply (for example, due date)
  • Opening and closing position: The above rules for positions apply (for example, end of term)
  • Day Before "From Date" or "To Date" has been entered on the selection screen for the position trend list: For opening and closing positions, this reference date is taken to refer to the "Key Date".

Important exception:
When determining the overdue period for flows, the system ignores any flows with the statuses:

  • Posted
  • Reversed

As a result, the overdue period for posted and reversed flows is zero.

History
Last changed by/on SAP  20020520 
SAP Release Created in 110