IBM Support

IV72623: BMXAA4146E Not a valid GL account Either required components not filled or component values not valid

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • BMXAA4146E - Not a valid GL account. Either the required
    components are not filled or the component values are not valid.
    Make sure the GL account value is entered in the appropriate
    fromat as defined in the GL Account application
    
    Maximo Asset Management  7.5.0.7
    
    WO portion works: The Enter by labor in the labor reporting app
    failed with the  gl validation error:
    "BMXAA4146E - Not a valid GL account. Either the required
    components are not filled or the component values are not valid.
    Make sure the GL account value is entered in the appropriate
    format as defined in the GL Account Applation"
    
    
    Steps to Replicate:
     1) In Chart of Accounts -> Validation Options -> "Validate GL
     Component Combinations" is checked
     2) In Chart of Accounts -> Resource Codes -> Internal GL
     Account has one component selected, with placeholder values
     (???) for the rest of the components eg: (???-???-123)
     3) Create a Work Order with a fully specified GL Account in
     APPR status. We will need a GL Account that can't be merged
     with the Internal Resource Code
             eg: Chart of Accounts list
             111-222-333
             111-222-222
             Work Order GL Account: 111-222-333
             This means that when entering Labor Actuals, the WO
     GL Account will automatically merge with the resource code
     to: 111-222-123 (which is an invalid GL Account because it is
     not in the Chart of Accounts list)
             *note: When entering actuals, the labor GL Debit
     Account will automatically update to "111-222-123" although
     the record can't be saved because it is an invalid
     combination.  This can be fixed however, by changing the
     last component         to either 333 or 222*
     4) Go to Labor Reporting
     5) Enter By Labor
     6) Enter in Labor Record
     7) Select "New Row" under Daily Time
     8) Erase the GL Account in GL Debit Account Field (defaulted
     to ???-???-123)
     9) Enter Work Order that was created in Step 3.
         *Gives you an error saying it is not a valid GL Account
     even though the Work Order GL Account is:
     11436-775-73220000-B8011000, and the defaulted ???-???-123 is
     erased on the field*
     However, if you use "Enter By Work Order" instead:
     10) Enter Work Order that was created in Step 3
     11) Select "New Row"
     12) Enter a labor Record
      *Entering a labor record will change the GL Debit Account,
     but the component is still editable to create the record*
     It looks like it is only the "Enter By Labor" functionality
     that does not let you change the GL Account, even though you
     are able to do this in WOTRACK and "Enter By Work Order".
    
    
    Note - the enter by workorder portion works,
    - but the enter by labor is not working  receiving
    error.
    "BMXAA4146E - Not a valid GL account. Either the required
    components are not filled or the component values are not valid.
    Make sure the GL account value is entered in the appropriate
    format as defined in the GL Account Applation"
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users who use the Enter By Labor function in the      *
    * Labor Reporting application.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Invalid GL Account error when entering a wonum in the Enter  *
    * By Labor dialog of the Labor Reporting application.  The     *
    * issue is: as soon as you tab out the wo num field, it        *
    * prompts the GL account error and the user has no way to      *
    * correct the account.                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Request hotfixes.                                            *
    ****************************************************************
    

Problem conclusion

  • This is fixed in code.  I fixed the Enter By Labor code to work
    the same way as the Enter by WO.  It now lets you enter the wo
    num and does not prompt the error message until OK is clicked.
    That way, user is given a chance to correct the invalid GL.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.5.0.9 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV72623

  • Reported component name

    WORK ORDERS

  • Reported component ID

    5724R46WO

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-04-22

  • Closed date

    2015-04-26

  • Last modified date

    2015-04-26

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

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

Modules/Macros

  • Maximo
    

Fix information

  • Fixed component name

    WORK ORDERS

  • Fixed component ID

    5724R46WO

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPPU","label":"Work Order Tracking"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
26 April 2015