IBM Support

IJ44234: INCONSISTENT BEHAVIOUR FOR MANDATORY FIELDS IN 'CREATE SHIPMENT' DIALOG IN INVENTORY USAGE

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 DESCRIPTION:
    If you make the Expected Receipt Date field mandatory on the
    Create Shipment but do not populate it, you get errors
    BMXAA7691E and BMXAA0032E even if you actually populate it
    afterwards.
    If it is made mandatory, the Expected Receipt Date field
    should behave in the same way as for the 'Shipment Date' field
    which is compulsory out-of-the-box in the same Create Shipment
    dialog.
     
    STEPS TO REPRODUCE: 
    * Log into Maximo
    * Open Application Designer and open the Inventory Usage record
    (INVUSAGE) 
    * Click Edit Dialog icon and then select Create Shipment 
    * Change Expected Receipt Date to be a compulsory field (Input
    Mode = Required)
    * Save the record.
    * Open the Inventory Usage application.
    * Create a new Inventory Usage record to transfer an item from
    one store to another. 
    * For example: for CENTRAL storeroom, select Item 0-048 and do
    TRANSFER for Qty= 5 to GARAGE.
    * Save the record, then do Change Status to Shipped to open
    the Create Shipment dialog.
    * Note that both Shipment Date and Expected Receipt Data are now
    compulsory.
    * Fill in the 'Expected Receipt Date' field and clear the
    'Shipment Date' field and click OK. 
    * You get System message: BMXAA4195E - A value is required for
    the Shipment Date field on the {1} object.
    * Click OK on the message, fill in the Shipment Date this time
    and click OK.
    * The Status is changed to Shipped 
    * Create an identical Inventory Usage record and do Change
    Status to Shipped until you are on the Create Shipment dialog. 
    
    * The Expected Receipt Date field is blank this time. Click OK.
    * You get System message: BMXAA4195E - A value is required for
    the Expected Receipt Date field on the SHIPMENT object.
    * This time the error message picks up the object as SHIPMENT.
    * Click OK on the message, fill in the Expected Receipt Date and
    click OK.
    * You get System message: BMXAA7691E - The status of inventory
    usage xxxx cannot be changed to SHIPPED. BMXAA0032E - The status
    that you selected is the same as the current status. Select a
    different status.
     
    RESULTS: 
    The BMXAA7691E - The status of inventory usage xxxx cannot be
    changed to SHIPPED error message prevents you from proceeding
    even though both mandatory fields are populated now. 
    You therefore have to click Cancel on the Create Shipment
    dialog, copy the Inventory Usage number, refresh the record, do
    Change Status to Shipped and ensure the mandatory Expected
    Receipt Date field is populated this time. 
    
    EXPECTED RESULTS:
    
    There should be no further error message after the mandatory
    fields have been populated.
    
    REPORTED IN VERSION: 
    Maximo TPAE 7.6.1.2
    

Local fix

  • You must click Cancel on the Create Shipment dialog, copy the
    Inventory Usage number, refresh the record, do Change Status to
    Shipped and ensure the mandatory Expected Receipt Date field
    is populated this time.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Inventory Usage                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * INCONSISTENT BEHAVIOUR FOR MANDATORY FIELDS IN 'CREATE       *
    * SHIPMENT' DIALOG IN INVENTORY USAGE                          *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR will be contained in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ44234

  • 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

    2022-11-09

  • Closed date

    2022-11-29

  • Last modified date

    2022-11-29

  • 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

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

Document Information

Modified date:
29 November 2022