Unable To Delete Resource Instance When Switching Schedule Flag To Schedule In Plant Resources Form
(Doc ID 2386113.1)
Last updated on FEBRUARY 15, 2019
Applies to:Oracle Process Manufacturing Process Planning - Version 12.2.6 and later
Information in this document applies to any platform.
On : 12.2.6 version, Setup Issues
<Patch 26835944> addressed some issues with trying to change a resource from "Schedule to Instance" to "Schedule". There are still some issues, however, after applying the patch. After changing a resource from "Schedule to Instance" to just "Schedule", the resource instances are not automatically deleted, marked inactive, or end-dated. This may be as designed, I'm not sure, as the form allows you to enter instances even if a resource is not set to Schedule to Instance. Prior to patch 26835944, however, a warning message used to display, "APP-GMP-84490: Resource Instances Exist - Change Schedule Indicator". This no longer displays. If you do not delete the instances, then the following problems are seen.
1. After running Generate Resource Availability program, when you try to view resource availability by navigating to the Resource Instance Available Time form (Setup > Resource Availability), when you enter the resource name on the Find window, an LOV pops up showing the resource repeated multiple times, as if it were showing each instance. The Instance Number on the LOV is blank, however.
2. This also causes issues with resource unavailability. If you go to the Resource Unavailablity form, and enter resource unavailablity, for example making a Count of 2 unavailable from 12/27 to 12/29, and then run Generate Resource Availability, if you then go to Resource Instance Available Time form, it still shows the full count of 5 available 24 hours a day. If you do the same on a resource that had never been instance controlled, then the Count is correctly reduced to 3.
In addition, three other issues were noted when using Schedule to Instance.
3. After creating a resource as Schedule to Instance and creating five instances, run Generate Availability. Then set the Inactive flag on instance 5, for example. The Count on the Resource Information form remains at 5, even though there are only four active instances. Run Generate Availability again. Go to Resource Instance Available Time form, enter resource name, LOV pops up still showing instance 5. Select it, and the form still shows this instance as being available.
4. When first creating the resource as Schedule to Instance and clicking Instances button the first time, you must enter Instance Default Values. End Date is a required field. Why is an end date required? On just about all other OPM entities we can leave end date blank. This was not mentioned by the customer but was noticed when doing internal testing. Should this really not be required? And If you click Accept without entering an end date, the error message that the field is required is displayed multiple times.
5. After entering the default values, the Resource Instances screen displays. If you want to change a start or end date for an instance, or insert a new instance, there is no date LOV available. And again, end date is required.
Expect that after making the resource no longer Schedule to Instance, a warning will be displayed as before, assuming that the design is intended to allow instances even if the resource is not Schedule to Instance. If it is intended that ONLY Schedule to Instance resources should be allowed to have instances, then it is expected that the instance records should either be marked Inactive or deleted, so that the other issues caused by having active instances with the resource set to only "Schedule" no longer occur.
Expect the Resource Instance Available Time form to not pop up an LOV with the same resource shown multiple times but Instance blank.
Expect entered Resource Unavailability to be reflected correctly on Resource Instance Available Time.
Expect an Inactive instance to not show as available.
Expect End Date to not be required on an instance unless there is a technical reason for it (this was noticed in internal testing, not mentioned by the customer).
Expect there to be a date LOV on the date fields on the Resource Instances screen.
The issue can be reproduced at will with the following steps:
1. Create a resource as Schedule to Instance, with several instances.
2. Change the Scheduling Indicator to "Schedule", without deleting the instances
The issue has the following business impact:
Due to this issue, resource availability is incorrect and other issues.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document