IBM Support

IV47349: MULTIPLE OUTBOUND TRANSACTIONS GENERATED WHEN USING THE INVENTORY (TR) APPLCIATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM:   When using the Inventory (Tr) Application to Issue
    Current
    Items multiple outbound transactions are generated if an Issue
    crrent
    Items is done more than once.
    
    
    
    PERFORMANCE ISSUE: NO
    
    
    STEPS TO REPRODUCE:
    
    Using MaxDemo Data.
    
    Login as WILSON
    
    First configure he outbound interface.
    
    Make sure you JMSSEQCONSUMER.SQOUT is Active.
    Make sure the mxe.intglobaldir is set to a directory that exists
    ie
    C:\temp
    
    Open the Integration Publish Channels Application.
    
    Open the MXGLTXNInterface PC, Select Actions, Enable Event
    Listener.
    
    Open the Integration, End Points Application
    
    Open the MXXMLFILE End Point and set the PRETTYPRINT = 1  Save.
    
    Open the Integration, External Systems Application
    
    Open the ExtSys1 application and Enable. Save.
    
    Open the Logging application, enable the Integration logger @
    DEBUG -
    apply settings.
    
    Now Set up the Data.
    
    Open the Inventory, Item Master Application
    
    Create a  new Item - MYITEM and set status to ACTIVE.
    
    Move to the CENTRAL storeroom with Cost= 1 Quantity = 75
    
    Open Work Order, Work Order Tracking
    
    Create a new Work Order MYWO and Activate.
    
    Now to replicate the problem.
    
    First as a control test we will test in the Inventory
    Application.
    
    Open the Invetory Application and filter for MYITEM and open.
    
    Select Actions, Issue Current Item.
    
    Quantity = 1
    Work Order = MYWO
    
    Click OK. Then Save.  Now WITHOUT leaving the Item replate the
    process
    this time set Quantity to 5 on Issue Current Item.
    
    Once the SQOUT cron task has run you will haev 2 XML files save
    in
    C:\temp\xmlfiles corresponding to the 2 transactions completed.
    
    Now open the Invenroty (Tr) application and perform the asame
    test.
    
    I chagend the Quantities each time:
    
    1sy Issue Quantity = 10
    
    2nd Issue Quantity = 15
    
    Using Inventory (Tr) now you get 1 XML file for the first
    transaction
    but 3 XMls for the second transaction.
    
    
    CURRENT ERRONEOUS RESULT:
    
    In and only in Inventory (Tr) multiple Events are generated for
    the 2nd
    Item Issue.
    
    
    EXPECTED RESULT:
    
    A single Event should be generated.
    
    ADDITIONAL INFO:
    
    Please see the Replication_Data.zip for the generated XMLs and
    the Log
    Output for all of thos above tests in the Invertory and
    Inventory(tr)
    apps.  As well as the records for this Item in MATUSETRANS.
    
    
    ENVIRONMENT:
    
    -
    - MBS: 7.5.0.4 -  Tansportation 7.5 IF 26
    
    
    
    
    - OS: Windows 2008
    
    - DB: DB2
    
    - Base Language: English
    
    - Additional Language:  N/A
    
    - Browser: IE + FF
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users that use Maximo for Transportation 7.5.0.0         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * MULTIPLE OUTBOUND TRANSACTIONS GENERATED WHEN USING          *
    * THEINVENTORY (TR) APPLCIATION.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * N/A                                                          *
    ****************************************************************
    

Problem conclusion

  • The bean now controls the transaction.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV47349

  • Reported component name

    MX TRANSPORTATI

  • Reported component ID

    5724R5500

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-08-22

  • Closed date

    2013-10-31

  • Last modified date

    2013-10-31

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

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

Modules/Macros

  • UNKNOWN
    

Fix information

  • Fixed component name

    MX TRANSPORTATI

  • Fixed component ID

    5724R5500

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLL9Z","label":"Maximo for Transportation"},"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