SAP ABAP Data Element PRS_WORK_PERIOD (Work Period (Internal Representation))
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_WORK_PERIOD
Short Description Work Period (Internal Representation)  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type PRS_WORK_PERIOD    
Data Type NUMC   Character string with only digits 
Length 7    
Decimal Places 0    
Output Length 11    
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 Work Per. 
Medium 15 Work Period 
Long 20 Work Period 
Heading 20 Work Period 
Documentation

Definition

Working period of the sales item that is used to determine the Date for pricing and exchange rate (pricing date) when pricing is carried out in the sales document or billing document.

Use

The working period holds 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.
  • If desired, the period type week can be incorporated by using the BAdIs provided in Dynamic Item Processor (DIP) and Sales and Distribution (SD).

Example for month

The employees record their August working times at the beginning of September. The working period of these recorded work time entries thus refer to August and not September, and so the pricing date also falls in August.

Note the following:

  • This field is solely used for the work period functionality. This functionality 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 functionality has been subsequently switched on in Customizing for Salesand Distribution, using activity Activate Professional Service Functionality.
  • The field cannot be filled via API or UI but only at application runtime when creating or changing sales items using the Dynamic Item Processor (DIP).
    The process starts in CATS, which then transfers the time and expense entries to CO, and DIP subsequently aggregates the CO documents for work periods before this data is sent to the sales documents.
  • When pricing is carried out in the sales or billing document, the work period is converted as follows into the pricing date of the relevant item:
    • Period Type 1
      Pricing Date: 15th of given month
    • Period Type 2
      Pricing Date: 1st day of given week
  • In addition to this conversion logic, the pricing date can be adapted by the BADI_SLS_BIL_PRS_PRSDT for enhancement spot ES_BADI_SLS_PRS, 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 is translated as follows:

Field Part        specifies the

YYYY        year

PP        period

T        period type

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 indicate 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 last 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_OUTPUTconversion based on the current logon language.

  • In the sales document item, the pricing date field remains ready for input in the UI or can still be set via API, BAPI, and so on. This value no longer impacts pricing once the logic described above is active and a work period is populated.

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