why single work order created merging 2 work def. having 2 different work requirements in PM program
In oracle maintenance cloud for Preventive maintenance program concurrent requirement is set to Merge on header level. specific Maintenance asset having 2 different work requirements having different work definitions with calendar pattern weekly . System is creating single work order merging both the work definitions. Is it expected behavior?
Also same PM program and Work requirement is created in different instance but there it is creating 2 different work orders with single work definition. Plant Maintenance parameters and PM program is same in both the instance, What could be the reason for this behavior?