IV33590: OWNER AND/OR OWNER GROUP FIELDS POPULATED AUTOMATICALLY ON CHAN RECORD THOUGH INITIALLY EMPTY ON JOB PLAN
Closed as user error.
Same as APAR IZ54854 (Issue 09-15960) which was suppose to be fixed in 18.104.22.168. The issue exists on 22.214.171.124 Customer requires a fix on 126.96.36.199 Basic steps to reproduce: 1. Create a job plan with a task with no owner or owner group 2. Create a change record, assign an owner, and apply job plan. 3. Save change record. 4. Note that the task(s) from the applied job plan is assigned to the change owner.
<span><span>This works as design per the product designer. Here is what he wrote:<br/>I've read the pmr and this appears to be working as designed. In most cases, Maximo copies details from parent records to the children that get inserted under them. In this case it is a change record that gets tasks inserted under it. When the child record's field is null, we usually copy the parent's value down. When the child's field has a value we usually do not overwrite that value with the value from the parent. So, this seems to be working as designed.<br/><br/>***However, the client claimed that it used to work in 7114 the way they liked but not in 7117. <br/><br/>It is working as designed and has worked this way for some time now. We just had a hotfix 7114 that 'broke' it. The client saw this 'broken' behavior as correct behavior. That was unfortunate.<br/></span></span>
Reported component name
MAXIMO TASK MGM
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID