IBM Support

IJ00209: TPAE 7608-BMXAA4195E- IT IS NOT POSSIBLE TO ASSIGN LABOR IN A WORK ORDER WITH A DURATION OTHER THAN 0 OR 1

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM:
    Seeing a weird bug in the 7.6.0.8 environments where assignment
    manager errors out if the work order you are assigning doesn't
    have a duration of 1 or 0 and there's not a planned
    assignment/labor.  If it has a duration of 0 or 1, you can
    assign any number of labor hours you want.
    If it it has a duration of 2, however, even if you tried to
    change the labor hours to 1 it errors out with the error: A
    value is required for the Assignment Status field on the
    WMASSIGNMENT object.
    
    PERFORMANCE ISSUE: NO
    
    STEPS TO REPRODUCE:
    
    1) Go to Assignment Manager Application
    
    2) In the Labor List, click the Modify Availability (far right
    icon) for Labor ADAM (craft ELECT).
    
    3) Add an entry to the Modify Work dates for some date in the
    future with 9 hours and a reason code of WORK (I used 9/29/17
    at 8 AM but time doesn't matter as long as the date is in the
    future)
    
    4) Filter the Work List for WO 1218. Click the checkbox next to
    the 1218 WO with the craft of ELECT in the Work List table and
    the checkbox next to the ADAMS labor (craft ELECT) in the Labor
    List.
    
    5) Click Assign Labor in the Common Actions.
    
    This works correctly, even though the WO 1218 has a duration of
    2.
    
    1) Go to Work Order Tracking
    
    2) Find WO 1013. Change estimated duration from a 0 to a 2.
    
    3) Go to Assignment Manager and filter for WO 1013.
    
    4) Click the checkbox next to 1013 and next to our ADAMS labor
    record (craft ELECT) and click Assign Labor.
    
    Expected: The labor (ADAMS) be assigned to the work order
    
    Actual: A dialog will pop up, click OK.
    You'll receive the BMXAA4195E - A value is required for the
    Assignment Status field on the WMASSIGNMENT object. error,
    which is the issue.
    
    To make it work, you have to modify the Work Order in Work Order
    tracking to have a duration of 1 or 0. If you do that, it'll
    work, but then the work order is incorrect.
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of the Assignment Manager application.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * IT IS NOT POSSIBLE TO ASSIGN LABOR IN A  WORK ORDER WITH A   *
    * DURATION OTHER THAN 0 OR 1                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A code fix has been delivered.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ00209

  • Reported component name

    WORK ORDERS

  • Reported component ID

    5724R46WO

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-21

  • Closed date

    2017-11-06

  • Last modified date

    2017-11-06

  • 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

  • R760 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":"760","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 November 2017