IBM Support

IV94978: MAXIMO IS RECORDING A WRONG DATA WHEN YOU DUPLICATE A JOB PLAN WITH PREDECESSORS.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • PROBLEM: Job Plan Predecessors are not recorded correctly in
    the database when autonumber is on.
    
    PERFORMANCE ISSUE: N/A
    
    STEPS TO REPRODUCE:
    1.Verify Auto-numbering is not activated for Job Plans
    2.Create a Job Plan with two tasks. Assign the 2nd task a
    Predecessor
    of the first task. Save.
    3.Query the db to see the predecessor link.
    select * from JPTASKRELATION where jpnum='xxx'
    One record displays for the job plan (as expected)
    4.Duplicate the Job Plan. Give it a new jpnum. Save.
    5.Query the db to see the predecessor link for the new jpnum.
    One record displays for the new jp.
    6.Turn on autonumbering for Job Plans.
    7.Repeat above steps, letting the autonumber populate the jpnum.
    
    ISSUE: Two records are generated for the first job plan, and
    none for
    the 2nd. In this case I created 1003, duplicated to 1004. The
    JOBPLANID
    is accurate, but the JPNUM is not.
    select * from JPTASKRELATION where jpnum in ('xxx','xxx')
    
    CURRENT ERRONEOUS RESULT: Genarating wrong data in the database.
    
    EXPECTED RESULT: Generate only one record in the JPTASKRELATION
    table.
    
    ENVIRONMENT (SYSTEM INFO):
    IBM Maximo for Oil And Gas 7.6.0.0-20160715-1424 Build
    20160715-1424 DB
    Build V7600-133
    Tivoli's process automation engine 7.6.0.5-IFIX20160714-2200
    Build
    20160611-0100 DB Build V7605-45 HFDB Build HF7605-02
    IBM TPAE Integration Framework 7.6.0.5 Build 20160610-2330 DB
    Build
    V7605-50
    IBM Maximo Asset Management Work Centers 7.6.0.0 Build
    20160610-1318 DB
    Build V7600-38
    IBM Maximo Asset Management 7.6.0.5 Build 20160611-0100 DB Build
    V7604-01
    
    Server OS
    Linux 2.6.32-642.1.1.eI6.x86_64
    
    Server DB
    Oracle 12.1 (Oracle Database 12c Enterprise Edition Release
    12.1.0.2.0
    - 64bit Production With the Partitioning, OLAP, Advanced
    Analytics and
    Real Application Testing options)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * maximo users who use the predecessor functionality on        *
    * jobplan                                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The JPNUM is not populated correctly on the duplicated       *
    * JPTASKRELATION records during the duplication of a job plan  *
    * with predecessors defined in job tasks. This happened when   *
    * JPNUM on jobplan is autokeyed.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This is fixed in code.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.6.0.9 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV94978

  • Reported component name

    MAXIMO PLANNING

  • Reported component ID

    5724R46PL

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-11

  • Closed date

    2017-05-26

  • Last modified date

    2017-05-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • maximo
    

Fix information

  • Fixed component name

    MAXIMO PLANNING

  • Fixed component ID

    5724R46PL

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management

Software version: 760

Reference #: IV94978

Modified date: 26 May 2017