IBM Support

IV55093: CANNOT LOAD CLASSIFICATION THAT HAS THE SAME CLASSIFICATIONID AND HIERARCHY PATH FOR DIFFERENT ORAGNISATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Cannot load classification that has the same classificationID
    and hierarchy path for different Oragnisation.
    
    Error encountered.
    BMXAA1407E - The CLASSSTRUCTURE object cannot be added because
    it already exists in the application. An integration message
    cannot create an object that already exists.
    and
    BMXAQ0268E - You cannot change this to a customer-specific
    classification because there is a global classification that is
    a child of this record.
    and
    BMXAA5591E - The RAIL classification cannot be deleted by an
    inbound integration transaction because more than one
    classification exists with the same hierarchy and path value.
    
    STEPS TO REPRODUCE:
    --------------------------
    1. Go to  Admin > Classificaiton App
    a) Select one record, I chose record with classificationid =
    '1030503'
    b) Make sure it has an organisation value, I chose 'EAGLENA'
    2. Go to Integration --> Object Structures (OS) application,
    select OS = MXCLASSINTERFACE
    a) from the select action menu, open the Exclude/Include
    Fields, make sure the following fields are not excluded:
    classstructureid parent HIERARCHYPATH is included.
    b) make sure 'Support flat file structure' is ticked
    c) Save Changes
    3. Go to Integration --> Enterprise Services (ES), select ES =
    MXCLASSINTERFACE
    a) Operation = Create and save
    4. Go to Integration --> external system app
    a) from Publish Channels tab, select MXCLASSInterface.
    b) export one classification (in my testing, I selected
    CLASSIFICATIONID='1030503').
    5. modify the exported file, and set new ORGID (in my testing
    "EAGLESA') import the file again
    a) Get below error
    [ERROR] [MXServer] [] Processing failed for class. The object
    structure is 1. The primary object is CLASSSTRUCTURE. The key
    is 1132.BMXAA1407E - The CLASSSTRUCTURE object cannot be added
    because it already exists in the application. An integration
    message cannot create an object that already exists.
    
    Error processing inbound transaction document/line 6.
    BMXAA1407E - The CLASSSTRUCTURE object cannot be added because
    it already exists in the application. An integration message
    cannot create an object that already exists.
    psdi.util.MXApplicationException: BMXAA1407E - The
    CLASSSTRUCTURE object cannot be added because it already exists
    in the application. An integration message cannot create an
    object that already exists.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MIF users who tried to load the classifications data with    *
    * same hierarchypath but for a different organization          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Cannot import classification with the same hierarchypath for *
    * a different organization.                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to REL 7.5.0.7 to be released in end of 2014. *
    * Or user can request hotfixes.                                *
    ****************************************************************
    

Problem conclusion

  • This is fixed in code.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.5.0.7 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV55093

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-02-06

  • Closed date

    2014-04-03

  • Last modified date

    2014-04-03

  • 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

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

  • R750 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":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
03 April 2014