SAP ABAP Data Element FTI_REVERSED_FLOWS (Process Reversed Flows (for Query))
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FIN-FSCM-TRM-TM-IS (Application Component) Information System
     ⤷ FTI_LDB (Package) Logical Databases for the R/3 CFM Information System
Basic Data
Data Element FTI_REVERSED_FLOWS
Short Description Process Reversed Flows (for Query)  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type XFELD    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID FTI_CONDENSE_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 Rev. Flows 
Medium 20 Reversed Flows 
Long 40 Process Reversed Flows 
Heading 40 Process Reversed Flows 
Documentation

Validity

If you set this flag, reversed flows are also selected and processed.

This logic only applies to the key date reference Posting Date.

This setting is only available in reporting for parallel architecture. It is not available for:

  • Loans in valuation area 001
  • The classic operative valuation area 001 before Enterprise Extension 2.0

Logic

If you set this flag and the "posting date" key date reference is set at the same time, reversed flows are also selected and processed.

A reversed business transaction or a reversed flow is only indicated as reversed in the TM subledger of the parallel architecture while two documents appear in the general ledger. If the reversal date is not the same as the posting date of the original document, this flag facilitates the reconciliation of the position management subledger with the general ledger. If the flag is set, the following logic applies:

In order to deliver correct data for each reporting period in the subledger for a position trend, the flow must be duplicated. This enables you to correctly display the change in book value on the posting date of the original document and the second change on the different reversal date. To simplify things, the "original flow" refers here to the duplicated flow which mirrors the original business transaction.

The following logic applies:

  • The posting date fields contains
    • the posting date of the TM flow for the original flow
    • the reversal date of the TM flow for the reversed flow
    • For the derived business transactions for which the quantity changes are located in a different flow from the TRL position changes (for example, security transfers, purchase only with units not values) only the carriers of the TRL position changes are relevant for ledger posting. The flows which represent the quantity change are not. In this case the posting date field is filled anyway with the posting date or reversal date.
  • The position value date field contains the position value date common to both flows.
  • The document number field contains (except for SL postings)
    • the document number of the TM flow for the original flow
    • the document number of the reversal date of the TM flow for the reversed flow
  • The same logic applies to the reference key (AWKEY).
  • The G/L Account: Debit and G/L Account Credit fields contain the (identical) flow information (and not as in the case of offsetting postings where credit and debit are swapped).
  • The delta book value fields in their respective currencies contain the value of the flow as if it were posted and not reversed.
  • The position status field contains the indicator for both flows that this flow has been reversed from the view of the TM subledger.
  • The ledger posting status field contains value 2 (reversed) for the reversal flow and value 3 (generated ledger posted) for the original flow. Ledger posting status 3 (generated not ledger posted) is assigned to the flows of business transactions for which quantity changes and TRL position changes are located in two different flows. In this case the quantity changes are not relevant for ledger posting. These receive ledger posting status 4.
  • This logic does not apply to same-day reversals.

History
Last changed by/on SAP  20040819 
SAP Release Created in 500