SAP ABAP IMG Activity BSPER_VC_PERIOD (Define Periods and Due Date Rules)
Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation
   CA-EPT (Application Component) Processes and Tools for Enterprise Applications
     BS_PERIOD_API (Package) API for period toolset
IMG Activity
ID BSPER_VC_PERIOD Define Periods and Due Date Rules  
Transaction Code S_BTD_53000143   (empty) 
Created on 20091030    
Customizing Attributes BSPER_VC_PERIOD   Define Periods and Due Date Rules 
Customizing Activity BSPER_VC_PERIOD   Define Periods and Due Date Rules 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BSPER_VC_PERIOD    

Use

In this Customizing activity you define the settings for period and due date rule calculation. The following functions are available:

  • Define frequencies on a daily, weekly and monthly basis.
  • Create periods that are derived from a mapping between a source frequency and a destination frequency.
  • Generate due dates at the beginning or at the end of periods.
  • Embed the ISO norm calender functions.
  • Enhance the frequency mapping logic and due date rule modifier according to customer specific requirements.

Define Frequency

In this activity, you define the frequency types you need using the standard frequency units Day, Week, and Month. In addition, you can combine the frequency units with a frequency factor to define composite frequency types, such as bi-weekly or 3-monthly.

The frequency types can be aligned with the calendar periods by means of the following adjustments:

  • Frequency types with a frequency unit of 1 are automatically aligned with the calendar periods.

    Periods of one week begin on Mondays; periods of one month begin on the 1st of the month.

  • If you choose Flexible, the period begins on the specfied time period.

    A period of one week can also begin on a Tuesday, if this is the specified start date.

  • If you define a composite frequency type with a frequency unit greater than 1, you determine the corresponding first calendar period by specifying a key date.

    If the key date 02/04/20xx is a Tuesday, the first period of one week begins on Monday 02/03/20xx.

As regards the frequency mapping procedure, you must also decide whether a frequency type is to be used as a source frequency, a destination frequency, or both.

Define Period Mapping Category

In this activity you create period mapping categories that are mandatory entries for the frequency mapping procedure. By default, no category entries are delivered. At least you have to create the following two period mapping categories that are supported by SAP as BAdI implementations:

  • BOP (Begin of Period)

    If you use this category, the first day of source period is relevant for the correlation to the destination period.

  • EOP (End of Period)

    If you use this category, the last day of source period is relevant for the correlation to the destination period.

If you wish to use further customer-specific period mapping categories you must first define the category entries. After this, you have to define the mapping logic as a customer-specific BAdI implementation in the Period Toolset Customizing under Business Add-Ins -> BAdI: Enhance Period Mapping Categories (BAdI BS_PERIOD_TOOLSET_FRQ_MAPPING).

Define Frequency Mapping

In this activity you define the mapping between a source frequency and a destination frequency. This mapping is defined as the frequency mapping type.

If the mapping between two frequency types are not unique, you need to assign the period mapping category BOP or EOP for the source frequency. You also have to specify the entity correlation between the source frequency and the destination frequency.

Define Due Date Rules Modifier

In this activity you create due date rule modifier that are mandatory entries for the definition of due date rules (DDR). By default, no DDR-modifier entries are delivered. You must create at least the following two DDR modifiers (that are supported by SAP as BAdI implementations):

  • BOP (Beginning of Period)

    If you use this DDR modifier, the first day of a period is relevant for the due date determination.

  • EOP (End of Period)

    If you use this DDR modifier, the last day of a period is relevant for the due date determination.

If you wish to use further customer-specific due date rule modifiers, you must first define the modifier entries. After this, you have to define the due date determination as a customer-specific BAdI implementation in the Period Toolset Customizing under Business Add-Ins -> BAdI: Enhance Due Date Rules (BAdI BS_PERIOD_TOOLSET_DUE_DATE).

Define Due Date Rules

In this activity you define due date rules for the calculation of due dates according to an assigned period. A due date rule consists following parameters:

Due Date Rule Modifier    Rough determination according to a period

Due Date Rule Factor    Adds or subtracts a number of days

Factory Calendar    Considers country-specific working days and public holidays

Factory Calendar Indicator    Indicates the direction shift of a due date to the next or previous working day

In the activity Assign Frequencies to Due Date Rules, you assign the due date rule to a frequency type that reflects a sequence of periods.

Requirements

Standard settings

SAP does not deliver any Customizing entries. However a set of period mapping categories (BOP and EOP) and due date rule modifier (BOP and EOP) are delivered as BAdI implementations. To use these BAdI implementations, you must create them as Customizing entries.

Activities

  1. Specify the number of frequencies, frequency mapping types and due date rules according to your needs in the Customizing activity.
  2. If the Period Toolset is not already embedded in your application component, you need to integrate the Period Toolset for your application component using the class methods of the package BS_PERIOD_API.

    The simulation program BS_PERIOD_TOOLSET_CUSTOMIZING provides you with an example of the usage of the Period Toolset class methods. Here, you can simulate your Period Toolset Customizing. The simulation program is available under Check Periods and Due Date Rule Settings.

Example

You want to map a two-weekly frequency to a monthly frequency. You do the following:

  1. Create an application area, where your settings are stored.
  2. Define the two-weekly frequency as the source frequency and the monthly frequency as the destination frequency.
  3. Specify a frequency mapping type with the two-weekly frequency as source and the monthly frequency as destination, choose the mapping entity "n : 1", and assign one of the period mapping categories.

You want to create a due date rule with a due date of four days before the last day of the month. You do the following:

  1. Select the due date rule modifier "EOP" (end of period).
  2. Specify the factor "-4"
  3. Specify your country-specific factory calendar (includes the specified country's holiday calendar).
  4. Specify the factory calendar indicator "+" (move forward).
  5. Enter a due date rule description.
  6. Assign an monthly frequency type to the due date rule type.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BSPER_VC_PERIOD 0 BTD0000161 Tools and Services in BS Foundation 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
BSPER_VC_PERIOD C - View cluster SM34  
History
Last changed by/on SAP  20091102 
SAP Release Created in 702