SAP ABAP Data Element IND_MCP_EXT (Enhancement Multiple Counter Plan)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ IPRM (Package) Application Development R/3 Preventive Maintenance
Basic Data
Data Element IND_MCP_EXT
Short Description Enhancement Multiple Counter Plan  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type XFELD    
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 Enh. MCP 
Medium 15 Enh. MCP 
Long 25 Enh. MultipleCounterPlan 
Heading 0   
Documentation

Definition

You can use this indicator to activate additional functions in the multiple counter plan.

Note that after saving you cannot revoke the activation.

The additional functions are also available to pre-existing multiple counter plans after saving.

Use

The following functions can be activated for the multiple counter plan:

Maintenance and Scheduling of Different Cycle Sets in a Plan.

Without this enhancement, only one "cycle set" (that is, a combination of various cycles) can be defined in a plan. This is used to calculate all the schedules, and generates a corresponding maintenance call object for all the maintenance items for each schedule.

The enhancement allows the maintenance of multiple cycle sets in one plan. Thus you can define different cycle sets, and thus cycles, for calculating the dates within a plan. You can use the assignment between cycle sets and the maintenance item to control that only certain maintenance items generate a call object for certain dates. In the simplest case, a cycle set such as A - B - A - B can be defined. "A" leads to a small inspection and "B" leads to a big inspection.

If cycle sets should be performed more than once, then you can define a repeat factor for each cycle set. The system does not change to the next cycle set until the first set has run as often as scheduled. The default value for this repeat factor is 1.

Note

Cycle sets are always scheduled after one another. This means, that for the example above, cycle set 1 follows cycle set 2, and so on. The cycle sets are never scheduled in parallel.

Additional Scheduling Parameters

  • Scheduling Period

    You can also generate a schedule preview for multiple counter plans.

  • Completion Requirement

    The next call object of a multiple counter plan is not generated until the preceding date has been completed.

  • Start Time

    By specifying a start date and time, schedule monitoring (IP30) can start a multiple counter plan automatically.

Additional Functions for Scheduling

  • Start/Restart

    A multiple counter plan can be started for a particular date - not in the future.

  • Start in the cycle

    A multiple counter plan can be started for a particular date - not in the future - and any cycle set of your choice.

Dependencies

Example

Here is an example of a vehicle maintenance. The vehicle should have a minor inspection after 15,000 kilometers or one year. After another 15,000 kilometers and/or two years, a major inspection should be performed.

In a multiple counter plan you can define two cycle sets for this with the above cycles. Assign a maintenance item to each cycle set (for example, cycle set 1 and cycle set 2). One maintenance item has the minor inspection, the other the major inspection.

Scheduling process

  1. The scheduling takes cycle set 1 into account to calculate the first date, and only generates one call object for the maintenance item assigned to cycle set 1 for this date.
  2. Building on this date, the scheduling uses the cycles of cycle set 2 to determine the next planned date and also only generates one call object here for the corresponding maintenance item.
  3. After the second and thus highest cycle set were scheduled, the scheduling considers the first cycle set again.

History
Last changed by/on SAP  20030714 
SAP Release Created in 470