SAP ABAP IMG Activity EXTRCT_PARAM_TLMAPLN (Extraction Parameters:Task List/Maintenance Plan)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ PM (Application Component) Plant Maintenance
     ⤷ PMEX (Package) PM: Extraction of Release-independent Objects
IMG Activity
ID EXTRCT_PARAM_TLMAPLN Extraction Parameters:Task List/Maintenance Plan  
Transaction Code S_EB5_05000207   (empty) 
Created on 20090304    
Customizing Attributes EXTRCT_PARAM_TLMAPLN   Extraction Parameters:Task List/Maintenance Plan 
Customizing Activity EXTRCT_PARAM_TLMAPLN   Extraction Parameters:Task List/Maintenance Plan 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EXTRCT_PARAM_TLMAPLN    

Use

In this IMG activity, you can define the extraction parameters for data source 0PM_PRM_PLCS_1.

You can make the following settings:

  • Package Size of Task List

    The system reads the number of task lists defined with this value from the database for each selection during the extraction.

    The package size basically depends on the number of operations in the task lists and on the period for which the calculation is to be performed.

    If the task lists have a lot of operations and if the calculation is spread over several years, the package size must be smaller; the value can be greater if there are a few operations and shorter calculation periods.

    If no value is maintained, the extractor uses the package size as 50.

  • Package Size of Maintenance Plan

    The system reads the number of maintenance items defined with this value from the database for each selection during the extraction.

    However, the relevant setting only takes effect if the maintenance items are entered in the selection conditions relevant for the extraction, but no task lists is entered.

    If no value is maintained, the extractor uses the package size as 50.

  • Date of the task list

    The system uses the prices that are valid for this date in the task list calculation. The date must be the same as or later than the current date. If the date is not maintained, the current date is used.

  • Order type

    This setting is used to define the order type to be taken into account for the task list calculation. The system determines the planned costs variant required for the calculation, the valuation variant and the costing sheet required for the overhead rates from the order type.

    If no order type is maintained, the extraction is not executed.

    The relevant setting does not apply to maintenance plans with order as call object.

    The order type from the planning data of the maintenance plan is used for maintenance plans.

  • Date of the maintenance plan, start date of the simulation

    Start date from which the scheduled maintenance items (calls) are taken into account for the cost determination simulation. The start date must be the same as or later than the current date. If the date is not maintained, the current date is used.

  • Date of the maintenance plan, end date of the simulation

    Date from which scheduled calls or calls to be scheduled are no longer taken into account.

    The end date must be the same as or later than the start date. If the end data is not maintained, the extraction cannot be executed.

  • Overhead rates addition

    If this indicator is set, overhead costs are also determined during the calculation. The overhead rates defined in the costing sheet are used.

    • With regard to task lists, the overheads are calculated once per task list based on the prices applicable to the key date.
    • For maintenance plans, the overheads are calculated per period based on the total costs for each related period.

Overheads can be determined only for each task list and for each period; a distribution to line items is not possible.

  • Annual cost increase in %

    By maintaining this factor, the calculation can be influenced with respect to future prices.

    • Factor is maintained
      • When the factor is maintained, the first fiscal year is calculated with the prices that are valid on the date that was scheduled by the system.
      From the second fiscal year to be calculated, the prices calculated last for the first fiscal year are used and are multiplied by the cost increase factor.
      For example: Calculation of a maintenance plan with just one operation
      Start date = 01.01.2010
      End date = 31.12.2012
      Factor = 5 %
      Cost of operation in the year 2010 (last period) = 100,00 EUR
      Cost of operation in the year 2011 -> 100 * 1,05 = 105,00 EUR
      Cost of operation in the year 2012 -> 100 * 1,05 * 1,05 = 110,25 EUR
    • Factor is not maintained
      • If the factor is not maintained, each data record is calculated with the price valid for its scheduled date. If no price is found, the system writes a corresponding error message to the log.
      Note
      If strategy sequences are defined for the price determination in the valuation variants, they are taken into account irrespective of whether the cost increase factor is maintained or not. It is recommended that you set the strategy sequence "Most Up-to-Date Plan Price" for the internal activity type in particular.

Requirements

Standard settings

Activities

Example

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 EXTRCT_PARAM_TLMAPLN 0 HLA0009530 Plant Maintenance 
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
TPM_C05 S - Table (with text table) SM30  
History
Last changed by/on SAP  20090304 
SAP Release Created in 605