IV32365: BILLBATCH CRONTASK IS FAILING TO OUTPUT ERROR MESSAGE DUE TO FIELD LENGTH ISSUE 7.5.0.3

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • Prob: Billbatch Crontask is failing to output error message due
    to field length issue.
    
    Envir: BS7503, Oracle 11g, Websphere 7.21, OS win2003
    
    Addon:
    
    Service Provider 7.5.1.1 (ISSUE)
    Linear Asset  7.5.0
    Transportation 7.5.0
    Client customisation 7.5.0
    Scheduler 7.5.1.0
    
    Error:
    
    Billbatch cron task fails with "Value specified exceeds maximum
    field length" message
    
    --
    
    Raised as a APAR request by development.
    
    --
    
    Steps to Reproduce.
    
    This PMR is being raised on advice of (IBM Service
    Provider
    
    Architect) who  confirmed that this is a bug and PMR needs to be
    raised.   The error is that the value in the
    PluspActualUsage.UserMeter should not be moved to
    PluspGBTrans.MeterName.
    
    
    1 Create usage meter with ID longer than 10 symbols ( say
    241DPM862_DAILY )
    
    2 Create a new Customer agreement with a billing schedule for
    this usage meter and approve it
    
    3 In Assets(SP) application create usage meter entry for the
    usage meter created on step 1
    
    4 Wait until PLUSPBILLGEN crontask to execute and check the
    error log file (stderr).
    
    
    There should be a message "BMXAA4049E - The value specified
    241DPM862_DAILY exceeds the maximum field length. Enter a value
    that fits into the length of this attribute."
    
    --
    
    Fix an error outputed to the system log report the crontask
    failure.
    
    There should be a message "BMXAA4049E - The value specified
    241DPM862_DAILY exceeds the maximum field length. Enter a value
    that fits into the length of this attribute."
    
    --
    
    Client description:
    
    Billbatch cron task fails with "Value specified exceeds maximum
    field length" message .
    
    
    This PMR is being raised on advice of (IBM Service Provider
    Architect) who  confirmed that this is a bug and PMR needs to be
    raised.
    
    The error is that the value in the PluspActualUsage.UserMeter
    should not be moved to PluspGBTrans.MeterName.
    
    1 Create usage meter with ID longer than 10 symbols ( say
    241DPM862_DAILY )
    
    2 Create a new Customer agreement with a billing schedule for
    this usage meter and approve it
    
    3 In Assets(SP) application create usage meter entry for the
    usage meter created on step 1
    
    4 Wait until PLUSPBILLGEN crontask to execute and check the
    error log file (stderr).
    
    
    There should be a message "BMXAA4049E - The value specified
    241DPM862_DAILY exceeds the maximum field length. Enter a value
    that fits into the length of this attribute."
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * <span><span>IBM Maximo for Service Providers                 *
    * 7.5.1.1</span></span>                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * BILLBATCH CRONTASK IS FAILING TO OUTPUT ERROR MESSAGE DUE    *
    * TOFIELD LENGTH ISSUE 7.5.0.3                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * No                                                           *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IV32365

  • Reported component name

    SERVICE PROVIDE

  • Reported component ID

    5724R46SV

  • Reported release

    711

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-22

  • Closed date

    2013-01-28

  • Last modified date

    2013-01-28

  • 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

  • R751 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Maximo Asset Management

Software version:

711

Reference #:

IV32365

Modified date:

2013-01-28

Translate my page

Machine Translation

Content navigation