IBM Support

IJ40338: BMXAA4196E - ATTRIBUTE JOB PLAN MUST BE SET BEFORE JOB PLAN REVISION NUMBER CAN BE SET.

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

  • The error BMXAA4196E - Attribute Job Plan must be set before Job
    Plan Revision Number can be set is received when user defined
    fields are copied from a Job Plan over to a Work Order when we
    try and apply a job plan to a work order.
    
    STEPS TO REPRODUCE:
    
    Stepes to add user defined fields to both work order and job
    plan objects.
    
    1.Open the datbase configuration application and bring the Job
    plan application to the screen. Move the attributes tab, 3 user
    defined attributes need to be added. BYSERVICE (Type: UPPER,
    Length: 16) and BYSERVICELINE (Type: UPPER, Length: 16).
    
    2. Add the same 2 fields from step 1 to the work order object as
    well. Save and perform a databse configuration.
    
    The next step will be to add the user created fields to the
    screen via the application designer.
    
    4. Open the application designer for the job plan applicaiton
    and add 2 text boxes to the job plan tab. Open the properties
    and associate one line to the BYSERVICE attribute and the other
    to BYSERVICELINE. Save and repeate the same steps for the work
    order tracking application.
    
    We now need to create the crossover domain that will move the
    data from the job plan application to the work order tracking
    application.
    
    5. Open the domains application and create a new crossover
    domain. Object=jobplan.
    
    List Where Clause:  jpnum=:jpnum and ((orgid=:orgid and
    siteid=:siteid) or (orgid=:orgid and siteid is null) or (orgid
    is null and siteid=:siteid) or (orgid is null and siteid is
    null)) and PLUSCREVNUM=:PLUSCJPREVNUM and status in (select
    value from synonymdomain where domainid='JOBPLANSTATUS' and
    maxvalue ='ACTIVE')
    
    Validation Where clause: 1=1
    
    Crossover Fields:
    
    Source Field = BYSERVICE, BYSERVICELINE
    
    The Destination field will match the name of the source:
    
    Destination Field: BYSERVICE, BYSERVICELINE
    
    Save the new domain and make note of the name. Move to the
    database configuration application and open the work order
    tracking application.
    
    6. In database configuration with the work order obect on
    screen, move to the attributes tab and search for the
    PLUSCJPREVNUM attribute. Once found add the name of the
    crossover domain created earlier to the domains field. Save the
    changes and perform another database configuration.
    
    We have set up Maximo as needed, we can now test the issue.
    
    7. Create a new job plan and populate all needed fields, make
    sure to add details to the 2 text fields we added in earlier
    steps. Approve the job plan.
    
    8. Create a new Preventive Maintenance record and add the job
    plan created earlier, add an asset and the needed frequency
    information. Approive the record and generate a new work order,
    note the work order number.
    
    9. Open the work order and notice that the job plan has been
    attached and the data has crossover as needed.
    
    10. From the more actions menu use the remove work plan option,
    the job plan is removed. Now try and add a new job plan and the
    error is thrown:
    
    
    BMXAA4196E - Attribute Job Plan must be set before Job Plan
    Revision Number can be set.
    
    The same error is thrown if we open the work order tracking
    application and try and attach a job plan to a work order that
    has no job plan.
    
    
    EXPECTED RESULTS:
    
    That new job plan would have been attached.
    
    
    Reported in Version:
    
    Tivoli's process automation engine 7.6.1.1
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Users encounter BMXAA4196E when attempting to set a Job Plan *
    * on a Work Order that has user defined fields and a crossover *
    * domain.                                                      *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ40338

  • 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

    2022-06-07

  • Closed date

    2022-09-16

  • Last modified date

    2022-09-16

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