IBM Support

IJ47115: REPORTEDBYID IS POPULATING WRONGLY WHEN TWO PERSON HAVING SAME DISPLAY NAME IN SR WHEN INTEGRATION IS USED.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Problem Description
    ReportedByID is populating wrongly when two person having same
    display name in SR when Integration is used.
    
    STEPS TO REPRODUCE:
    The steps below use MAXDEMO as an example:
    1)Go to People application and create two new person with the
    same display name:
    
    PERSONID: HYVEE
    PERSONID: HYVEE-FG
    
    DISPLAYNAME: Eemeli Hyvönen
    
    2)Go to the Object Structure application, and search for MXSR.
    
    Click on Exclude/Include Fields => Non-Persistent Fields.
    
    Include the fields: REPORTEDBYID and REPORTEDBYNAME.
    
    3)Make the POST below:
    
    URL: http://MXSERVER/maximo/oslc/os/mxsr?lean=1
    
    Body:
    { "ticketid":"PF01",
    "reportedbyid":"HYVEE",
    "reportedbyname":"Eemeli Hyvönen" }
    
    RESULTS:
    SR will be created but REPORTEDBY field will have the value
    HYVEE-FG.
    
    EXPECTED RESULTS:
    REPORTEDBY field must have the value HYVEE.
    
    
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.3
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * REPORTEDBYID IS POPULATING WRONGLY WHEN TWO PERSON HAVING    *
    * SAME DISPLAY NAME IN SR WHEN INTEGRATION IS USED.            *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 9.x Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ47115

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-06-05

  • Closed date

    2023-09-13

  • Last modified date

    2023-09-13

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

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

Fix information

  • Fixed component name

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
13 September 2023