APAR status
Closed as program error.
Error description
Problem Description Object Structures will have relationships defined with SINGLE cardinality (1-to-1) will be altered to MULTIPLE (1-to-many) when published to Cognos in environments that have a base language anything other than English. You can define the Object structure with SINGLE cardinality relationships but once published to Cognos this will change to MULTIPLE. Note: This ONLY happens if the base language of Maximo is non-ENGLISH The reason this is so is the code is looking taking a string "SINGLE" and comparing that to a value pulled from the database. If the base language is English, this value in the database will be "SINGLE" but if not, it is something else. The condition won't match and a 1-many relationship will be used as default. For example, in French the word is UNIQUE, not SINGLE. The code compares SINGLE to UNIQUE, they don't match so 1-many is used as default. STEPS TO REPRODUCE: YOU need a Maximo environment that has some other language as base as opposed to English. French is a good one. It also needs to have a Cognos integration. The REP_WOPLANACT object structure has a number of objects and some have SINGLE cardinality. (ASSET, LOCATIONS, JOBPLAN, etc) Publish this object structure to Cognos Create a report in Cognos that utilizes this object structure. RESULTS: The sql will have 1-many joins as opposed to 1-1 joins. The relationships defined as SINGLE, will become MULTIPLE and this adversely affects performance of any queries generated from this Object Structure. EXPECTED RESULTS: Joins should be 1-1 for relationships defined with SINGLE cardinality PRODUCT VERSION: 7.6.1.3
Local fix
Local Fix: None
Problem summary
**************************************************************** * USERS AFFECTED: * * MAXIMO * **************************************************************** OBJECT STRUCTURE CARDINALITY COMPROMISED FOR MAXIMO ENVIRONMENTS WHERE BASE LANGUAGE IS NOT ENGLISH AND OBJECT STRUCTURES ARE US
Problem conclusion
The fix for this APAR is contained in the future release
Temporary fix
Comments
APAR Information
APAR number
IJ47910
Reported component name
MAXIMO REPORTIN
Reported component ID
TIVOREPTS
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-08-15
Closed date
2024-04-08
Last modified date
2024-04-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
MAXIMO
Fix information
Fixed component name
MAXIMO REPORTIN
Fixed component ID
TIVOREPTS
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"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 April 2024