IBM Support

IJ41046: ERROR BMXAT0050E/ BMXAT0141E WHEN TRYING TO SAVE RECORD IN GRAPHICAL CREW MANAGEMENT

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: Error BMXAT0050E/ BMXAT0141E when trying to save record
    in Graphical Crew Management
    
    
    
    STEPS TO REPLICATE:
    1. Go to Calendar application - Create calendar
    
    - Calendar: 119
    
    - ORGID: EAGLENA
    - Start Date: 1/1/21
    - End Date: 12/31/22
    Save
    Create calendar
    - Calendar: 119
    
    - ORGID: EALGESA
    - Start Date: 1/1/21
    - End Date: 12/31/22
    Save
    
    2. Click More Actions - Define/Apply Shifts
    Create 2 shifts
    - Shift: FT005A
    
    Start Day: MONDAY
    
    Days in Pattern: 5 - from 7:00 AM - 3:00 PM 8 hr
    - Shift: FT005B
    Start Day: SUNDAY
    
    Days in Pattern: 5 - from 7:00 AM - 3:00 PM 8 hr
    
    
    3. Apply FT005A, FT005B shifts to 119 Calendar (under EALGENA)
    
    Apply FT005A, FT005B shifts to 119 Calendar (under EAGLESA)
    
    
    
    4. Go to Craft application
    Create a craft
    
    - Craft: EL&I
    
    - ORGID: EAGLENA
    - Have Crew? checked
    - In Skill level,  add a skill level
    
    Skill Level: I
    
    Save
    
    Create a craft
    - Craft: EL&I
    
    - ORGID: EAGLESA
    - Have Crew? checked
    - In Skill level,  add a skill level
    
    Skill Level: I
    
    Save
    
    
    
    5. Go to Labor application
    Create a labor
    
    - Labor: SKEARNS
    - ORGID: EALGENA
    - Default craft: EL&I
    
    - Calendar: 119
    - Work site: BEDFORD
    Save
    Create a labor
    
    - Labor: SKEARNS
    
    - ORGID: EALGESA
    - Default craft: EL&I
    
    - Default Skill level: I
    Save
    
    6. Go to Crew Type application
    Create a crew type
    - Crew Type: STD
    - ORGID: EAGLENA
    Save
    Create a crew type
    - Crew Type: STD
    - ORGID: EAGLESA
    Save
    
    7. Go to Crew application
    Create a crew
    - Crew: MOA2-A1X
    
    - Crew Type: STD
    
    - ORGID: EAGLENA
    - Calendar/Shift: 119/FT005A
    
    In Required crafts, Add line
    - Position: LEADER
    - Craft: EL&I
    
    In Labor Assignments, Add Line
    - Labor: SKEARNS
    
    - Position: LEADER
    - Craft: EL&I
    - Skill level: I
    - Effective date: 4/20
    Save
    Create a crew
    - Crew: MOA2-A1X
    
    - Crew Type: STD
    
    - ORGID: EAGLESA
    - Calendar/Shift: 119/FT005A
    
    In Required crafts, Add line
    - Position: LEADER
    - Craft: EL&I
    
    In Labor Assignments, Add Line
    - Labor: SKEARNS
    
    - Position: LEADER
    - Craft: EL&I
    - Skill level: I
    - Effective date: 5/24
    Save
    
    
    
    8. Go to Graphical Crew Management
    
    Create a new Crew List:  TESTFORCL
    Set Calendar/Shift: 119/FT005A
    
    Set ORGID: EAGLENA
    In Crew Queries, add new
    - Data Source: AMCREW
    - Where clause: (status = 'ACTIVE' and orgid = 'EAGLENA' and
    amcrew like '%MOA2%')
    Save
    
    RESULT:
    
    Record is not saved and get the following errors:
    
    "BMXAT0050E - The project data failed to populate into
    scheduler tables for project TESTFORCL.For more information,
    check the Maximo log file (in your application server directory)
    or contact your system administrator.
    BMXAT0141E - The reservation did not populate. For more
    information, see the Maximo log file (in your application server
    directory) or contact your system administrator.
    BMXAT0141E - The reservation did not populate. For more
    information, see the Maximo log file (in your application server
    directory) or contact your system administrator.
    One or more values in the INSERT statement, UPDATE statement, or
    foreign key update caused by a DELETE statement are not valid
    because the primary key, unique constraint or unique index
    identified by "3" constrains table "MAXIMO.SKDRESERVATION" from
    having duplicate values for the index key.. SQLCODE=-803,
    SQLSTATE=23505, DRIVER=4.11.69"
    
    EXPECTED RESULT:
    
    Should save without error
    
    
    REPORTED IN VERSION:
    
    Tivoli's process automation engine 7.6.1.2
    IBM Maximo Asset Management Scheduler 7.6.8.0
    
    AFFECTED APPLICATION (for Maximo Only):
    Graphical Crew Management application
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Scheduler users                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR will be included in a future Release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ41046

  • 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-07-07

  • Closed date

    2022-09-02

  • Last modified date

    2022-09-09

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