While invoking the PM engine in one of our functionality, we see that for some of the records ,even after passing all the input parameters including 'End Date' to the FSPrevMnt component, the 'Due' date field on the activity does not get set with the 'End Date' parameter. It gets set to the current date time after the PM component is invoked. We would like to understand the cause and fix for this behavior of PM component.
The inputs to the
The Due date on Asset's activity created by FSPrevMnt engine is set to the input End Date.
1. Create a workflow process with a business service step that invokes 'Server Requests' BS, 'SubmitRequest' method, and process properties as inputs to the FSPrevMnt engine. Basically set up to be like customer's BS step for invoking FSPrevMnt with inputs. Deploy and Activate the workflow process.
2. Create a serializable product, release it.
3. Create a Preventive Maintenance plan with a time trigger:
Administration - Preventive Maintenance
Name: Test PM Plan Created: 10/26/2012 08:39:19 AM Last Run: 8/2/2015 03:29:38 PM Priority: blank Min SRs Required: 0 Over # of Days: 365 Active: checked Optional: unchecked Real Time Trigger: unchecked
Interval: 183 Valid Start: 0 Valid End: blank
4. Create a new Asset, associate product from 2 to the asset. Set Installed = Registered = 4/24/1997.
5. Log into service_enu, go to Administration - Business Service > Simulator.
Simulate the workflow process with the inputs:
PM_spcEndDT="2015-10-05" PM_spcAsset_spcID="1-5ZT-2" ProcessName="PM Test Workflow Process" PM_spcDefActOwnerID="0-1" PM_spcPlan_spcID="1-GI6WEQ" PM_spcMode="Id"/>
FSPrevMnt creates 1 PM Action, and the Due = current date = 9/8/2015 08:00:00 AM (9/8/2015 is the current date when simulating the workflow process), like customer's which is 9/8/2015 11:00:00 AM.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!