IBM Support

IJ35130: PM WOGEN NOT COPYING LABOUR TO CHILD WORK ORDERS WHEN USING A NESTED JOB PLAN

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
    
    PM Wogen not copying labour to child work orders when using a
    nested job plan
    
    STEPS TO REPRODUCE:
    1. Go to Job Plans Application and Create a new Job Plan
    "CHILDWO1" Add a description: "Child Work Order Test" Leave all
    other fields at their defaults and save the record.
    2. Change the status of the CHILDWO job plan to ACTIVE
    3. Create a new Job Plan PARENTWO1, add a description: "Parent
    and Child Work Order Test".
    4. Under Jon Plan Task Add two tasks to the PARENTWO1 job plan:
    a. Description: Task 1, Duration: 8:00, Nested Job Plan:
    CHILDWO1
    b. Description: Task 2, Duration: 8:00, Nested Job Plan:
    CHILDWO1
    5. Add two planned labour rows to the PARENTWO1 job plan:
    a. Craft: ELECT, Qty: 1, Hours: 8, Task: 10
    b. Craft: CONSTR, Qty: 1, Hours:8, Task: 20
    6. Change the status of the PARENTWO1 job plan to ACTIVE.
    7. Create a new PM record "1025" (PM: NESTTEST, Add a
    description: Nested Job plan Test)
    a. Select an operating location
    b. Select the job plan PARENTWO1
    c. Select the work type PM
    d. Set the frequency to 1 and frequency units to DAYS
    e. Set the Estimated Next Due Date to the current date:03/08/21
    8. Save and activate the NESTTEST PM record
    9. Go to more actions and Use the Generate Work Orders option to
    create a new work order ? "1305" > click the plans tab >
    WorkOrder "1306" genrated for task 1 and "1307" generated for
    Task 2
    
    UNEXPECTED RESULTS:
    No planned labour is copied to any of the work orders when using
    the PM Wogen process.
    10.The Parent and Child work orders do not have any planned
    labour.
    11. Create a new Work Order "1309" in Work Order Tracking
    a. Desc: Manual nested job plan test
    b. Select an operating location
    c. Select the PARENTWO job plan
    12. Save the Work Order. Child work orders will be generated:
    WO "1310" generated for Task 1 and "1312" generated for Task 2
    a. The Parent work order will not have planned labour
    
    b. Child WO 1 (Desc: Task 1) will have 1 planned labour record
    with Craft: ELECT, Qty: 1, Hours: 8
    c. Child WO 2 (Desc: Task 2) will have 1 planned labour record
    with Craft: CONSTR, Qty: 1, Hours:8
    
    EXPECTED RESULTS: The PM Wogen should process the planned labour
    to the child work orders in the same way as manually creating
    the work order using the job plan does.
    
    REPORTED IN VERSION:
    IBM Maximo Asset Management 7.6.1.2
    

Local fix

  • Client needs a fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * PM WOGEN NOT COPYING LABOUR TO CHILD WORK ORDERS WHEN USING  *
    * A NESTED JOB PLAN                                            *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ35130

  • 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

    2021-09-23

  • Closed date

    2022-09-22

  • Last modified date

    2022-09-22

  • 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:
22 September 2022