IBM Support

IJ26018: ANYWHERE IS NOT SYNCHRONIZING LABOR TRANSACTION BEFORE COMPLETING WORK ORDERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM DESCRIPTION:
    Unable to synchronize transaction to Maximo (desktop) when
    there is an automation script to check actual labor
    
    STEPS TO REPRODUCE:
    1. Go to Automation Scripts application in Maximo (Desktop)
    2. Click Create and select "Script with Attribute Launch Point"
    Launch Point = ACT_LAB
    object = WORKORDER
    Attribute=STATUS
    Events=Validate
    Click Next
    script=check_actlab
    script language=jython
    Go to Variables section and click New Row
    variable=Reghours
    LaunchPoint Attribute=REP_ACTLAB.REGULARHRS*
    Click New Row button
    variable=sts
    LaunchPoint Attribute=STATUS
    click Next
    Copy and paste the following in the script field:
    if Reghours is not None:
    if sts in ('COMP') and sum(Reghours)<=0:
    errorgroup = "GMW"
    errorkey = "ACTUAL_LAB"
    if Reghours is None and sts in ('COMP'):
    errorgroup = "GMW"
    errorkey = "ACTUAL_LAB"
    NOTE: the second line should be indented. errorgroup and
    errorkey  lines should also be indented
    Click Create button
    3. Go to Database Configuration application
    Go to Messages action
    Click New Row
    Message Group=GMW
    Message Key=ACTUAL_LAB
    Message ID Prefix=BMXZZ
    Value=Please enter actuals labor and create rows for work &
    travel!
    Click OK
    4. Log in to Work Execution application
    5. Enable offline mode
    6. Click timer button from any work order in a work list
    7. Click the same timer again. Change the start time to one
    hour earlier
    8. Complete work
    9. Disable offline mode
    10. Enable offline mode
    11. Add transactions for three work orders and then completed
    them in offline mode
    12. Disable offline and synchronize transactions
    
    ACTUAL BEHAVIOUR:   Receive error: "Could not change Work Order
    XXX status to COMP. BMXZZ7120E - Please enter actuals labor and
    create rows for work & travel!".  Actual labor transaction does
    not synchronize to Maximo (Desktop)
    
    EXPECTED BEHAVIOUR:   Anywhere should synchronize labor
    transaction before completing the work order
    
    PRODUCT VERSION:
    IBM Maximo Anywhere 7.6.4
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * IJ26018 ANYWHERE IS NOT SYNCHRONIZING LABOR TRANSACTION      *
    * BEFORE                                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • fixed
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ26018

  • Reported component name

    ANYWHERE APPS

  • Reported component ID

    5725M39MA

  • Reported release

    764

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-02

  • Closed date

    2020-11-19

  • Last modified date

    2020-11-19

  • 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

    ANYWHERE APPS

  • Fixed component ID

    5725M39MA

Applicable component levels

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

Document Information

Modified date:
02 June 2022