APAR status
Closed as program error.
Error description
Environment: IBM WebSphere Application Server 8.5.5.3 Tivoli's process automation engine 7.6.0.2 Build 20150903-2113 DB Build V7602-31 IBM TPAE Integration Framework 7.6.0.2 Build 20150901-2100 DB Build V7602-05 IBM Maximo for Service Providers 7.6.1.0 Build 20150902-1515 DB Build V7610-23 IBM Maximo Asset Management 7.6.0.2 Build 20150903-2113 DB Build V7601-01 IBM WebSphere Application Server 8.5.5.3 Windows Server 2012 R2 Standard Version 6.3.9600 Build 9600 Microsoft SQL Server 11.0 (11.00.3449) Concerns/Problem: Service Provider: WO Status CAN availability issue in Multi-Site environment Check for availability of WO Status CAN appears to be based on WONUM only and does not consider SiteID/ORGID Steps to reproduce the issue: Test environment must be a multi-site, mutli-org configuration. At site, BEDFORD: 1. Service Provider (SP)> Customers(SP), add a new Customer. Customer Currency:USD Change Status: Active 2. Service Provider (SP)> Customer Agreement(SP), add a new Customer Agreement for the above Customer Click on "Price Schedules" Tab On section Price Schedules click on "New Row" Schedule:TEST Applies To: WorkOrder Ranking:1 Click on Save button Change Status to "Approved" 3. Work Orders > Work Order Tracking (SP), add a new WO. add the above Customer Click on Save button Change Status to "Approved" Click on "Actuals" tab and "Materials" subtab add material Item. Click on "Save" button Click on Select Action > Apply Customer Agreement Change Status to "Complete" 4. Service Provider (SP) > Customer Billing(SP), add a new bill batch add the above Customer add the above Agreement Bill end date:today +1 day Click on Save button Click on "WO's , Tickets, and SO's" button to add the above WO. 5. Change to site CHILEHDQ, EAGLESA. Change the person profile with another default site in a different organisation (e.g. CHILEHDQ, EAGLESA). 6. Create a new WO in the new site (CHILEHDQ) with the same WONUM above. Try to change this WO status to cancel (CAN), but this status is not available. Business Impact: This issue was identified during our cutover to PROD yesterday. As this is severely impacting the business, and there is no work around, we have logged it as a P1. Current Problem: Check for availability of WO Status CAN appears to be based on WONUM only and does not consider SiteID/ORGID Expected Result: The WO Status CAN should be based on WONUM and SiteID/ORGID Additional Info: Test environment must be a multi-site, mutli-org configuration.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * All users that use Maximo for Service Provider 7.6.1 or * * high. * **************************************************************** * PROBLEM DESCRIPTION: * * SERVICE PROVIDER: WO STATUS CAN AVAILABILITY ISSUE IN * * MULTI-SITE ENVIRONMENT * **************************************************************** * RECOMMENDATION: * * N/A * ****************************************************************
Problem conclusion
Changed sql query
Temporary fix
Comments
APAR Information
APAR number
IV79300
Reported component name
SERVICE PROVIDE
Reported component ID
5724R46SV
Reported release
762
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-11-30
Closed date
2015-12-23
Last modified date
2015-12-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SP
Fix information
Fixed component name
SERVICE PROVIDE
Fixed component ID
5724R46SV
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"762","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
23 December 2015