Multiple counter Plan – How to identify the Cycle responsible for each Call Object generated

This post will be helpful for people who are working with Multiple counter Plan and especially who are building custom reports related to such Plans.

Requirement :

A way to identify the specific Cycle responsible for each Call object generated from a Multiple counter Plan.

Scenario:

Consider the below case of Multiple counter Plan(75247) with Cycles; 1 MON / 2000 KM

After some time period, a Call object (Order) is generated as part of scheduling.

However, there is no information mentioned about Cycle responsible for the Call object(Order) generated neither in the Order nor in the Maintenance Plan. This information is essential to rightly identify between cycles – 1 MON  / 2000 KM, whether the former or later reached first and resulted in the Order generation.

Solution:

As part of solution, we are going to utilize data from KNASR field of MHIS table.

KNASR field with it’s “X” value indicates which particular package/Cycle is leading and is responsible for Call object generated.

In our case, the above screenshot indicates that out of Cycles 1 MON and 2000 KM,

later (2000 KM) is responsible for the first generated Call object(Order).

Conclusion:

Through the above example, I hope we have learnt a easy way to identify the specific Cycle responsible for each Call object generated from a Multiple counter Plan.

Thanks for the read.

Hanniel Paul.