IV33954: VIEW RELATED RECORDS FUNCTIONALITY

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

  • View Related Records Functionality
    
    
    When using the View Related Records functionality in the PR
    
    Application, irrelevant POs show up.
    Consider the case where PO 1016 (site DENVER) and PO 1256 (site
    BEDFORD) are created from PR 1052 (site DENVER).
     In the view related records window (of PR application), PO 1016
    shows
    up multiple times (an entry for every site a PO with this number
    is
    created in) even if only PO 1016 for DENVER is really related to
    the PR
    In the case that I sent you, yes, we have changed the default
    insert
    site at one point so that we could create POs with different
    sites.
    However, we have replicated this process even without touching
    the
    default insert sites.
    Steps are as follows (I am re-creating it right now and will be
    past
    screenshots below):
    1)      Create a PR with two line items (I will be working with
    site
    BEDFORD).
    2)      I then go to the PO application and create 2 POs (one
    for ea
    line item of the PR) ? I will choose a PO number that already
    exists
    another site (because this is the fundamental criteria for this
    issu
    occur)
    POs for site DENVER (another Site)
    PO 1111 (BEDFORD) ? Chose PO number corresponding to one that
    alread
    exists for DENVER
    PO 1113 (auto-numbered)
    
    3)      View related records of PR ? 1111 shows up twice, for
    both
    sites. Only the one of BEDFORD is related to my PR in reality.
    To replicate this issue, 2 things are crucial: The PO number is
    alre
    used for another site and this already existing PO has at least
    one
    item. Otherwise, the issue will not be replicated.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of PR viewing related records                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When using the View Related Records functionality in the PR  *
    * Application, irrelevant POs show up.                         *
    * Consider the case where PO 1016 (site DENVER) and PO 1256    *
    * (site                                                        *
    * BEDFORD) are created from PR 1052 (site DENVER).             *
    * In the view related records window (of PR application), PO   *
    * 1016                                                         *
    * shows up multiple times (an entry for every site a PO with   *
    * this number                                                  *
    * is created in) even if only PO 1016 for DENVER is really     *
    * related to                                                   *
    * the PR                                                       *
    *                                                              *
    * 1)      Create a PR with two line items (I will be working   *
    * with                                                         *
    * site                                                         *
    * BEDFORD).                                                    *
    * 2)      I then go to the PO application and create 2 POs     *
    * (one                                                         *
    * for ea                                                       *
    * line item of the PR) ? I will choose a PO number that        *
    * already                                                      *
    * exists                                                       *
    * another site (because this is the fundamental criteria for   *
    * this                                                         *
    * issu                                                         *
    * occur)                                                       *
    * POs for site DENVER (another Site)                           *
    * PO 1111 (BEDFORD) ? Chose PO number corresponding to one     *
    * that                                                         *
    * alread                                                       *
    * exists for DENVER                                            *
    * PO 1113 (auto-numbered)                                      *
    * 3)      View related records of PR ? 1111 shows up twice,    *
    * for                                                          *
    * both                                                         *
    * sites. Only the one of BEDFORD is related to my PR in        *
    * reality.                                                     *
    * To replicate this issue, 2 things are crucial: The PO number *
    * is                                                           *
    * alre                                                         *
    * used for another site and this already existing PO has at    *
    * least                                                        *
    * one                                                          *
    * item. Otherwise, the issue will not be replicated.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * None                                                         *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
       Release 7.5.0.5 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV33954

  • Reported component name

    PURCHASING

  • Reported component ID

    5724R46PU

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-24

  • Closed date

    2013-06-04

  • Last modified date

    2013-06-04

  • 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

    PURCHASING

  • Fixed component ID

    5724R46PU

Applicable component levels

  • R750 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Maximo Asset Management
Purchase Requisitions

Software version:

750

Reference #:

IV33954

Modified date:

2013-06-04

Translate my page

Machine Translation

Content navigation