SAP ABAP Data Element PRS_ACT_WP (Activation of "Pricing with Work Period" Function)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ SD-SLS (Application Component) Sales
     ⤷ ERP_PRS_SD (Package) Professional Services; parts in SD Core
Basic Data
Data Element PRS_ACT_WP
Short Description Activation of "Pricing with Work Period" Function  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type BOOLE    
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   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Act. WP 
Medium 15 Activate WP 
Long 20 Activation of WP 
Heading 55 Activation of Function 'Pricing with Work Period' 
Documentation

Definition

By activating this function, you can use the Work Period of the sales order item to determine the Date for pricing and exchange rate (pricing date) when carrying out pricing in the sales document or billing document.

Dependencies

This function is only available if the Commercial Project Inception and Lean Staffing (PRS_ERP_CPILS_1) business function has been activated and if the Pricing with Working Period function has been subsequently switched on in Customizing for Sales and Distribution (SD) with this indicator.

The work period is only available if it has been determined with the previous process steps and has been transferred to SD.
The process starts in the Cross-Application Time Sheet (CATS) application, which transfers the time and expense entries to Controlling (CO), and the Dynamic Item Processor (DIP) aggregates the CO documents for work periods before the data is sent to the sales documents.

Switching Off

If you switch off this Customizing indicator, the system does not proceed with the work period function.
This means, for example, that:

  • An existing work period is no longer used to determine the pricing date.
  • The BADI_SLS_BIL_PRS_PRSDT is no longer called.
  • Work period dates are no longer transferred from DIP to SD.

Use

The scope of functionality incorporates the following functions:

  • The working period contains the period to which the time and expense entry actually belongs, regardless of when it was posted and regardless of subsequent changes.
    • In the standard system, only period type month is used.
    • The period type week can be incorporated if desired by using the BAdIs provided in DIP and SD.
  • When pricing is carried out in the sales or billing document, the work period is converted into the Date for pricing and exchange rate (data element PRSDT) of the relevant item as follows:
    • Period Type 1: The pricing date is the 15th of the given month.
    • Period Type 2: The pricing date is the 1st day of the given week.
  • In addition to this conversion logic, the pricing date can be adapted by the BADI_SLS_BIL_PRS_PRSDT Business Add-In for the ES_BADI_SLS_PRS enhancement spot, which provides a hook for sales document item pricing (method ADAPT_PRSDT_SLS) and for billing document pricing (method ADAPT_PRSDT_BIL).
  • The internal representation YYYYPPT (NUMC7) of the work period specifies the following data:

Field Part        Data

YYYY        year

PP        period

T        period type

The period types indicates the following data:

  • Period Type T=1 indicates month and PP can contain the set {01-12}.
  • Period Type T=2 indicates week and PP can contain the set {01-53}.

  • Conversion exit PRSWP converts the work period between external and internal representation.

    In the external representation TTT_PP.YYYY, the first three characters TTT show the 3-character language-dependent external unit of measurement of the corresponding internal (primary) unit of measurement of the relevant ISO unit.

    Example:
    If we use month as the period (the seventh character in the internal representation is 1), the ISO unit is MON and the corresponding primary internal unit of measurement is used. If we assume this key is also called MON, its external 3-character representation is determined using the CUNIT_OUTPUT conversion based on the current logon language.

  • In the sales item, the pricing date field (data element PRSDT) remains ready for input in the user interface or can still be set via API, BAPI, and so on. This pricing date no longer impacts pricing once the logic described above is active and a work period is populated.
    You can continue to use the pricing date field (data element PRSDT) even if you want to transfer it using a BAdI from, for example, the sales or billing item to the database table KOMK (Communication Header for Pricing), pricing date field PRSDT.

Example

History
Last changed by/on SAP  20110901 
SAP Release Created in 605