IBM Support

IZ84206: ON A MULTIPLE LINE PO, IF ONE LINE ITEM HAS HAD ITS STATUS CHANGED TO PENDOBS, THE PO IS UNABLE TO BE APPROVED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Unable to re-approve a PO on which, of multiple PO lines, a
    FULLY
    received
    line's item is marked as PENDOBS but as not has been fully
    received, however, another
    line's item is ACTIVE but not yet fully received.
    We are having trouble with POs that were created with items that
    were
    active at the time the PO was created.  Now at least one item on
    the
    PO became inactive after the PO was created but the item has
    been already been
    fully received. We can receive the
    POs if the PO status in not change to WAPPR. However, once the
    status
    is changed to WAPPR, for reasons necessary to our business
    process,
    the PO can't be re-approved and the item's status whose
    status prevents the PO's approval can't be changed
    becasue there are open transactions against the item.
    
    Steps to Replicate
    1. Go to PO application and insert new PO.
    2. Fill out a Company.
    3. Go to the PO Lines tab and hit new row. Enter the following
    values
    for that row, ITEM=217224, QTY=1, STOREROOM=CENTRAL.
    4. Hit New Row again and enter the following values,
    ITEM=560-00, QTY=1, STOREROOM=CENTRAL
    5. Click SAVE.
    6. Change status of PO to APPR
    7. Go to the Receiving app
    8. Enter the PO no. from above.
    9. Go to the Material Receipts tab.
    10. Click the Select Ordered Items button.
    11. Select the checkbox against item 217224.
    12. Click OK, click SAVE.
    13. Go to Inventory app and recall item 217224
    14. Change status of item to PENDOBS (ensure you are changing
    the status
    for the item in the CENTRAL storeroom.
    Note:
    No message is thrown that the item is on an open PO.
    
    15. Go back to the PO app and recall the PO created above.
    16. Change status of PO back to WAPPR.
    Note: No message is thorwn advising that the PO will not be able
    to be
    re-approved due to the reference of an item having a status of
    PENDOBS.
    
    17. Go to the PO Lines tab
    18. For the line not yet fully received, change the qty=2 (not
    really
    necessary)
    19. Save.
    20. Change the status to APPR.
    Result: Even though the line with the item in status PENDOBS as
    been
    completely received and the line with the ACTIVE item NOT yet
    received,
    Maximo does not allow the approval of the PO and throws the
    following
    error messages.
    
    BMXAA3279E - Could not change PO XXXX status to APPR.
    BMXAA2119E - item(s) [xyz] is in PLANNING or PENDOBS status.
    
    Environment
    
    App Server: IB< WebSphere Application Server 6.1
    Version: SAP ERP 6.0 Adapter 7.1.0.0 Build 010 DB Build V7100-04
    ITIM
    PMP 7.2.0.00 Build 1 DB Build V710-02
    Common PMP 7.1.1.6 Build 20091130D DB Build V7116-05
    IBM Maximo Adapter for Primavera 7.1.1.0
    Build 20091209-1102DB Build V7120-24
    Base Services 7.1.1.6-LA20100531-2150 Build 2091208-1415 DB
    Build
    HFDB Build V7116-173 7116-09
    IBM Maximo Project Adaptor 7.1.1.02 Build 14 DB Build V7110-02
    Server OS Windows Server 2003 5.2 Build 3790 Service Pack2
    
    Tested and replicated in Base 7.1.1.6
    
    Searched and found the following KB doc
         http://www-01.ibm.com/support/docview.wss?uid=swg21428208
    However, in the client's scenario, the problem is a little
    different.
    Their PO was created when the item
    status was ACTIVE and the PO was approved and the specific line
    was
    received in full.  The PO has more than one line on it and the
    buyer had
    to un-approve the PO so they could manage the open PO line
    (which has
    NOT been received at all and whose status is in ACTIVE mode).
    Now they
    can't re-approve the PO because of one of the item's status
    listed on the PO and they can't change
    the item's status because of the PO.
    
    They need to be able to manage PO's and if the status logic can
    change they
    need to include logic to prevent un-approving PO's where this
    condition
    exists.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: maximo                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: ON A MULTIPLE LINE PO, IF ONE LINE ITEM *
    *                      HAS HAD ITS STATUS  CHANGED TO PENDOBS, *
    *                      THE PO IS UNABLE TO BE APPROVED         *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    ON A MULTIPLE LINE PO, IF ONE LINE ITEM HAS HAD ITS STATUS
    CHANGED TO PENDOBS, THE PO IS UNABLE TO BE APPROVED
    

Problem conclusion

  • <This is fixed per the product designer:  the best way to
    resolve this is to allow the item status to be changed to
    ACTIVE directly from PENDOBS. >
    
    
    
    
    
    The fix for this APAR is contained in the following maintenance
    package:
    
      | release\fix pack | REL 7.1.1.8 - BS
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ84206

  • Reported component name

    PURCHASING

  • Reported component ID

    5724R46PU

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-09-01

  • Closed date

    2010-09-17

  • Last modified date

    2010-09-17

  • 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

  • R711 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPN3","label":"Purchase Requisitions"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"711","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 September 2010