Maximo Open Forum

Expand all | Collapse all

Inventory Usage App - Prevent removing default GL Debit Acct

  • 1.  Inventory Usage App - Prevent removing default GL Debit Acct

    Posted 18 days ago
    Hello MORE Maximo Community,

    I have created a Default Table data in the Inventory Usage app to default the GL Debit Acct and Issue To in all the Usage Lines.

    However, when adding an item in the new line, it removes the Gldebitacct previously defaulted by default app table data.

    I tried writing an attribute launch point automation script on item number run action to set the gldebitacct readonly but that doesn't work.

    Any ideas how I can accomplish this?

    Thanks,
    Megha
    #Customizations

    ------------------------------
    Megha Tatiya
    MIL Corp
    ------------------------------


  • 2.  RE: Inventory Usage App - Prevent removing default GL Debit Acct

    Posted 14 days ago
    Any ideas or thoughts, anyone?

    ------------------------------
    Megha Tatiya
    ------------------------------



  • 3.  RE: Inventory Usage App - Prevent removing default GL Debit Acct

    Posted 13 days ago
    What version of Maximo are you using?

    When you add the item in the new line, you said it is removing the GL account:
    1) When you create the row, the GL account field is definitely populated with the value from your Default Table Data section?
    2) Is the item number the only piece of information you added?
    3) When you add the item number, the GL account field gets NULL'd, or is it overwritten with a different value?

    ------------------------------
    Travis Herron
    Pensacola Christian College
    ------------------------------



  • 4.  RE: Inventory Usage App - Prevent removing default GL Debit Acct

    Posted 13 days ago
    Travis,

    Thanks for your response.

    We're on Maximo v7.6.0.9

    1) Yes, when I first add the new row the GL Account gets copied from the default table data.
    2) Yes, item # is the only information I add after hitting the new row button.
    3) As soon as I add the item number, the GL Debit Account field gets null'ed, not overwritten with a new value.

    I hope this helps.

    Thanks,
    Megha​

    ------------------------------
    Megha Tatiya
    ------------------------------



  • 5.  RE: Inventory Usage App - Prevent removing default GL Debit Acct

    Posted 13 days ago
    I can't say I'm super-experienced with Inventory Usage, but I did make a Default Table Data section for the Issues & Transfers application, so it should be pretty similar.  And we're on 7.6.0.8, so I can't speak for any changes (or bugs) that may exist in 7.6.0.9.  That said:

    --Have you tried using different From Storerooms?  Does it behave the same way regardless of which Storeroom you use?
    --Chart of Accounts is an Org-level object.  Is the account code you're testing with valid (not expired) and part of the Org you're using to test?
    --Any chance there's some other customization causing it to NULL the field?  Assuming you're doing this in a development environment, can you turn off ALL Automation Scripts and see if it works?
    --In Application Designer, for the Section you added to contain your Default Table Data controls, are you certain that the Data Source ID is set correctly?  In a default configuration, the value should be main_invuselinetab_table
    --When putting values in your Default Table Data section, are you using anything else alongside GL Account?  For example, if you also put Location or Asset, those objects will try to pull in their own default GL Accounts, and it should override what you've put in your Default Table Data section.  So maybe that's happening and the processing logic is a little out-of-order?

    ------------------------------
    Travis Herron
    Pensacola Christian College
    ------------------------------



  • 6.  RE: Inventory Usage App - Prevent removing default GL Debit Acct

    Maximo Certified
    Posted 12 days ago
    I'm not a GL expert so I can't explain to you exactly why it is this way. But in the java class on item that clears out the GLDEBITACCT when item is set if it's not a transfer. In both cases (it going to a null value or it being set to a value) IBM suppresses access control so you can't prevent it by making it read-only. In the case that an item is being provided they even suppress ACTION & VALIDATION so you can't even tie an automation script on GLDEBITACCT to set it back to the previous value when it's set to null. 

    If the line is a tool and the transaction type is ISSUE they then go and make the field read-only so it can't be modified at all (without suppressing access control). In the case of an item that is a transfer they set the GLDEBITACCT based on either the INVCOST's CONTROLACC or storeroom's controlacc depending on whether it exists in the storeroom already or not. 

    I don't think there's a great way to accomplish this unfortunately. The best option I can think of is you extend their java class on item and after they nullify it you retrieve the previous value to set it back to.

    ------------------------------
    Steven Shull
    Projetech Inc.
    ------------------------------



  • 7.  RE: Inventory Usage App - Prevent removing default GL Debit Acct

    Posted 12 days ago
    Do you think it would be possible if she used an Automation Script with an Attribute Launch Point on the ITEMNUM field, that it could grab the value of gldebitacct_previous and set that as the value for gldebitacct?

    ------------------------------
    Travis Herron
    Pensacola Christian College
    ------------------------------



  • 8.  RE: Inventory Usage App - Prevent removing default GL Debit Acct

    Maximo Certified
    Posted 12 days ago
    Yes actually that should work if you choose an action launch point because the script should fire after IBM clears out the value. In that scenario, to get the previous value you need to do something like below.

    glMboValue=mbo.getMboValue("GLDEBITACCT")
    if not mbo.getString("GLDEBITACCT") and glMboValue.getPreviousValue().asString():
        mbo.setValue("GLDEBITACCT",glMboValue.getPreviousValue().asString(),mbo.NOACCESSCHECK)​

    I would suggest handling other situations where GL debit acct isn't allowed (such as tools when it's an issue) to prevent having values when Maximo doesn't want a value in the field.

    ------------------------------
    Steven Shull
    Projetech Inc.
    ------------------------------



  • 9.  RE: Inventory Usage App - Prevent removing default GL Debit Acct

    Posted 11 days ago
    Edited by Megha Tatiya 11 days ago
    Thank you Travis and Steven for your help! I will give these a try and let you know if it works!


    ------------------------------
    Megha Tatiya
    ------------------------------