IBM Support

IV77938: THE ASSETS WILL BE CREATED USING ASSETNUM INDICATED IN THE IMPORT FILE INSTEAD OF USING AUTONUMBER

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:
    
    Receive Rotating Items in Bulk
    
    Maximo out of the box Bulk Receipt Metered Assets functionality
    is not functioning as designed. The receiving process is not
    generating asset records after the first receipt however the
    receipt quantity/on-hand quantities are increased.
    
    Upon a new receipt we are able to import the ASN file and
    typically only the first record in the import is received and
    has a rotating asset created. In some cases multiple records
    will be processed and have their assets created upon initial
    receipt. This appears to be intermittent. Subsequent receipts
    against the same PO no longer function as expected. We will see
    the quantity adjusted on the POLINE
    but no asset is created.
    
    The above example occurs when importing through CSV. When using
    XMLwe are only able to do the initial receipt against the PO.
    Subsequentreceipts are unsuccessful and we receive a msg that
    the receipt status must be WASSET. This only occurs when
    receiving XML.
    
    PERFORMANCE ISSUE: NO
    
    STEPS TO REPRODUCE:
    
    Steps to replicate in the OOB Utilities 7.5.0.1
    
    1) In Item Master application, flag itemnum 27R2.5B26-7 as a
    rotating item
    
    2)  Select Action > Add Items to Storeroom and enter the
    following info:
    Storeroom = CENTRAL
    
    3) Create a New Purchase Order as the following:
    PO: autokey
    Company: WES
    
    4) Go to POLines tab and create a new row as the following:
    Item: 27R2.5B26-7
    Storeroom: CENTRAL
    Quantity: 1000
    
    5) Save and chage PO status to Approve (APPR)
    
    6) Go to Receiving(TD) application and bring up the PO above
    
    7) Select Action - Select Receive Rotating Items in Bulk
    
    8) Specify Import   Browse for file import
    
    9) Select PLUSDTND External System PLUSDMXRCVROTITMInterface
    Enterprise Service
    
    10) Select Flat File Radio Button
    
    11) Review IBMMETERRECEIPT.CSV file. Ensure PONUM matches the
    PONUM created. ITEMNUM should be 27R2.5B26-7. RECEIPTQUANTITY
    should be equal to the number of lines in the CSV file. For
    example, if the file has 4 receive lines, the receipt quantity
    must be 4 on all lines. ASSETNUM should be a different dummy
    number in each row (for example row 1 assetnum = 1000, = 2000
    assetnum line 2and so on)
    
    12) Specify IBMMETERRECEIPT.CSV at Import File
    
    13) Select Ok - You will be notified that the message was
    successfully processed for PO#
    
    14) Refresh PO in Receiving (TD) application
    
    15) Review the Receiving (TD) application, were created two
    lines to the same quantity with the number of lines from csv
    file. 1 line with RECEIPTS status and other with TRANSFER status
    
    16) In the Meter Assets (TD) Application query on assets with
    rotating item 27R2.5B26-7 at site BEDFORD. You will see that
    were created assets with the dummy numbers of
    IBMMETERRECEIPT.CSV document instead of using the Asset
    autonumber
    
    
    Summary
    
    The assets will be created using ASSETNUM indicated in the file
    - this is not expected. Integration process must use autonum to
    generate those assets and this is a issue
    
    
    CURRENT ERRONEOUS RESULT: The assets will be created using
    ASSETNUM indicated in the file - this is not expected.
    Integration process must use autonum to generate those assets.
    
    
    EXPECTED RESULT: The assets created using the autonumber
    
    
    ENVIRONMENT (SYSTEM INFO):
    
    App Server IBM WebSphere Application Server 8.5.5.3
    
    Version Tivolis process automation engine 7.6.0.0 Build
    20141117-2230
    DB Build V7600-218
     IBM TPAE Integration Framework 7.6.0.0 Build 20141117-1800 DB
    Build
    V7600-15
     TPAE OSLC Object Structure 7.5.1.1 Build 20141118_165910-0600
    DB Build
    V7511-02
     IBM Maximo Asset Management Scheduler 7.5.3.0 Build
    20141117-2230 DB
    Build V7530-19
     IBM Maximo Spatial Asset Management 7.5.0.1-20141210-1253 Build
    20120714-2208 DB Build V7501-13 HFDB Build HF7501-06
     IBM Maximo for Utilities 7.5.0.1-20141119-2127 Build
    20120710-0136 DB
    Build V7501-14 HFDB Build HF7501-09
     IBM Maximo Asset Management 7.6.0.0 Build 20141117-2230 DB
    Build V7600-
    00
    
    Server OS Linux 2.6.32-431.11.2.el6.x86_64
    
    Server DB Oracle 11.2 (Oracle Database 11g Express Edition
    Release
    11.2.0.2.0 - 64bit Production)
    
    (c) Copyright IBM Corp. 2011
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Users that use Maximo for Utilities 7.5.0.1              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * HE ASSETS WILL BE CREATED USING ASSETNUM INDICATED IN THE    *
    * IMPORT  FILE INSTEAD OF USING AUTONUMBER                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * N/A                                                          *
    ****************************************************************
    

Problem conclusion

  • Dummy asset num in .csv document is now working
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV77938

  • Reported component name

    MAXIMO UTILITIE

  • Reported component ID

    5724R5600

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-10-09

  • Closed date

    2015-11-06

  • Last modified date

    2015-11-06

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

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

Modules/Macros

  • UTIL
    

Fix information

  • Fixed component name

    MAXIMO UTILITIE

  • Fixed component ID

    5724R5600

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLLAM","label":"Maximo for Utilities"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
29 September 2021