IBM Support

IJ30247: USING THE MIF, A PO LINE CAN BE REMOVED FROM A NEW REVISION EVEN THOUGH THE LINE HAS BEEN RECEIVED

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:
    
    Using the MIF, a PO Line can be removed from a new
    revision even though the line has been received
    This happens
    when:
    1. A flat file is imported using the MIF
    2. A PO line
    exists on the latest PO revision and has the same item number
    as a previous line.
    3. This line is not included in the flat
    file
    STEPS TO REPRODUCE:
    First you need to create a PO using
    the UI:
    1.) Create a PO and approve it
    2.) Create a revision
    (revision 1) and add two lines with the same ITEM number
    For
    example:
    line 1 - 61503
    line 2 - 61503
    3.) Approve the PO
    revision and receive the items
    4.) Create a new revision using
    MIF:
    Duplicate the MXPO Object Structure
    - Name it TESTPO or
    whatever you want and Save
    - Remove POCOST and POTERM Source
    Objects and Save
    Select Support Flat Structure
    5.) Create an
    Enterprise Service
    Name it TESTPO or whatever you want and
    Save
    6.) Add the Enterprise Service to an External System and
    save.
    7.) Import a flat file without adding the second PO line
    to create a new revision (revision 2):
    EXTSYS1,TESTPO,AddChange,
    EN
    ALLOWRECEIPT,BILLTO,BILLTOATTN,CHANGEBY,CHANGEDATE,CONTACT,CU
    RRENCYCODE,ORDERDATE,ORGID,POID,PONUM,POTYPE,PRIORITY,REVCOMMENT
    S,REVISIONNUM,SENDERSYSID,SHIPTO,SITEID,STATUS,STATUSDATE,STATUS
    IFACE,TOTALCOST,VENDOR,COMMODITYGROUP,CONVERSION,DESCRIPTION,POL
    _DESC_LD,ENTERBY,ENTERDATE,GLDEBITACCT,ISSUE,ITEMNUM,ITEMSETID,L
    INECOST,LINECOST1,LINETYPE,ORDERQTY,ORDERUNIT,POL_ORGID,POLINEID
    ,POLINENUM,RECEIPTREQD,RECEIPTSCOMPLETE,RECEIVEDQTY,POL_RCVDTOTA
    LCOST,RECEIVEDUNITCOST,REQUESTEDBY,RESTYPE,POL_SHIPTO,TOSITEID
    1
    ,BEDFORDMAIN,KATHYB,MAXADMIN,2020-09-24T09:16:44-07:00,Stewart W
    ood,USD,2020-09-25T08:03:53-07:00,EAGLENA,312,TESTPO3,STD,0,test
    ing,2,MX,BEDFORDMAIN,BEDFORD,APPR,2020-09-24T09:15:19-07:00,0,10
    20,A0001,MECH,1,Brake Shoe Kit,,MAXADMIN,2020-09-24T09:10:57-07:
    00,6100-300-300,1,61503,SET1,1000,1000,ITEM,10,EACH,EAGLENA,2092
    913899,1,1,1,10,1000,100,MAXADMIN,AUTOMATIC,BEDFORDMAIN,BEDFORD
    
    RESULTS:
    The PO line 2 with the same ITEM number was deleted
    from the new revision even though the line has been received
    If
    you try the same using the UI:
    BMXAA3334E - You cannot delete a
    purchase order line against which receipts have taken
    place
    
    EXPECTED RESULTS:
    Do not delete the purchase order line
    that has already been received
    
    PRODUCT VERSION:
    Tivoli's
    process automation engine 7.6.1.0
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * USING THE MIF, A PO LINE CAN BE REMOVED FROM A NEW REVISION  *
    * EVEN THOUGH THE LINE HAS BEEN RECEIVED                       *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ30247

  • 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

    2021-01-11

  • Closed date

    2021-03-11

  • Last modified date

    2021-03-11

  • 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

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

Document Information

Modified date:
12 March 2021