IBM Support

IV59247: IN SCHEDULER THE CALCULATE COSTS BUTTON ON THE WORK COST TAB GETS ORA-00913 ERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible.

Error description

  • When the client clicks the Calculate Cost button  on the WOrk
    Cost tab in the Scheduler, they get this error:
    
        BMXAT0048E - The activities did not populate. For more
    information,  check the Maximo log file (in your application
    server directory) or contact your system administrator.
        ORA-00913: too many values
    
    The problem is due to a badly formed SQL statement shown below
    that only happens if your skdprojectid is greater than 1000.
    In one place in the SQL statement it puts the value in with a
    comma separating the thousands from the hundreds, for example
    1,309 instead of 1309.
    
    [4/14/14 11:27:17:689 EDT] 00000075 SystemOut O
    executeStatement insert into skdcosttemp (skdprojectid,
    timeperiod, year, period, startweekdate, cestlabcost,
    cestmatcost, cestservcost, cesttoolcost, contentuid) select
    skd.skdprojectid, skd.timeperiod, skd.year, skd.period,
    skd.startweekdate, sum(estlabcost), sum(estmatcost),
    sum(estservcost), sum(esttoolcost),
    1,309||to_char(max(workorderid))||'_WEEK_WAPPR_CEST' from
    (select 1309 as skdprojectid, '13' as timeperiod,
    to_char(schedstart,'YYYY') as year, to_char(schedstart, 'WW')
    as period, to_char(schedstart+ (2-to_char(schedstart,'D'))) as
    startweekdate, estlabcost, estmatcost, estservcost,
    esttoolcost, workorderid from workorder where workorderid in
    (select objectid from skdactivity where objectname='WORKORDER'
    and skdprojectid=1309) and status in (select value from
    synonymdomain where domainid='WOSTATUS' and maxvalue in
    ('WAPPR')) and schedstart is not null) skd group by
    skd.skdprojectid, skd.timeperiod, skd.year, skd.period,
    skd.startweekdate order by skd.year, skd.period
    
    Development reviewed this and said to put in this APAR.
    
    Steps to reproduce: (at least on Oracle)
    1. Increase the seed number on skdprojectid to be over 1000
    2. Create a new Schedule.
    3. Click on the Work Cost tab.
    4. Click the Calculate Cost button and the error appears.
    

Local fix

  • Not really a workaround but use skdprojectid's less than 1000.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * NONE                                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Norep even if skdprojectid > 999. It was a problem in        *
    * previous releases.                                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * NONE                                                         *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IV59247

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    750

  • Status

    CLOSED UR5

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-04-14

  • Closed date

    2014-04-18

  • Last modified date

    2014-04-18

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

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

Fix information

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
18 April 2014