SAP ABAP Data Element WSDAT (Value Date for Currency Translation)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KACC (Package) Cost Accounting: Cost collector RK-A
Basic Data
Data Element WSDAT
Short Description Value Date for Currency Translation  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type DATUM    
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 WSD  
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Value Date 
Medium 15 Value date 
Long 20 Value date 
Heading 10 Value Date 
Documentation

Definition

The value date is the date of the exchange rate used for currency conversion.

Supplementary Documentation - WSDAT 0001

Use

Procedure

Examples

Dependencies

If you do not enter a date, the posting date is used as value date.

Supplementary Documentation - WSDAT 0002

Use

Assessment, distribution, and periodic reposting can all process different currencies. To do this, you have to activate the indicator "All currencies" for your controlling area.

The controlling area currency is the master currency.

If you also wish to carry the object currency, such as order or cost center currency, in your controlling area, you have the following alternatives for assessment, distribution, and periodic transfers:

  • the object currency is carried independently
  • the object currency is determined from the controlling area currency during posting.

The latter case requires a currency translation. You define the exchange rates during Customizing.

You maintain the object currency in the master record of the relevant object.

To allow the system to find the correct translation rates in the rate table, it needs a value date, which you can enter in this window.

If you do not enter a value date, the system will try to translate by period. In planning, it uses the first day of the period, while for actual values, it takes the last day.

Examples

You are processing an assessment, distribution, or periodic transfer for periods January through March. The object currency is to be derived from the controlling area currency.

Assume the controlling area currency is US$, and one cost center has the currency DM.

  1. You enter February 15 as value date.

    The translation uses the rate valid on February 15 for all three periods.

  2. You do not enter a value date.

    The translation uses the rate valid on 01/01 for January, the rate valid on 02/01 for February, and the rate valid on 03/01 for March.

Supplementary Documentation - WSDAT 0003

Use

The calculation of imputed costs processes different currencies.

The controlling area currency is the main currency.

When the object currency differs, the corresponding posting value must be computed from the controlling area currency.

The value date is needed to find the conversion rate in the currency table.

If you do not enter a value date, the system attempts to convert by period using

  • the first day of the period for planning data
  • the last day of the period for actual data

Examples

You are calculating the imputed costs for March 2015. Assume the controlling area currency is US$, one cost center uses DM.

  • You enter a value date of March 15, 2015.
    • During posting, the amount in US$ is converted to DM using the rate of 03/15/2015.
  • You do not enter a value date.
    • The conversion for the planned calculation of imputed costs uses the rate of 03/01/2015.
    • The conversion for the actual calculation of imputed costs uses the rate of 03/31/2015.

Supplementary Documentation - WSDAT 0004

Use

When performing a summarization, the final cost center and any of its superior cost centers in the hierarchy may have different object currencies.

In these circumstances, the currency has to be translated.

To find the appropriate rates in the exchange rate table, the system needs a value date which you can enter in this field. If you do not enter a value date, the system will attempt to translate by period. For plan values, it uses the first day of the period, for actual values, it takes the last day.

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