IBM Support

IV88277: INTEGRATION OBJECT - DATA MAP DOES NOT WORK WHEN USING A BUSINESS OBJECT THAT HAS THE SAME NAME IN TWO DIFFERENT MODULES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • You may find an issue with the setup of an Integration Object
    record when using a Business Object that exists with the same
    name in 2 different modules.
    For example:
    When setting the Data Map, you select Module as triItem and
    Business Object as triChecklistCategory but then you don't get
    any options in the Form drop-down (just a blank value) so you
    are unable to continue in setting up the Data Map.
    You may observe that there is a triChecklistCategory BO in both
    the triItem and Classification modules.
    The issue is that Integration Object logic to display Business
    Objects with staging tables in the Data Map drop down list did
    not take into consideration that the same named Business Object
    can belong to multiple Modules.
    This was reported in TRIRIGA 3.5.1 / 10.5.1
    

Local fix

  • There is no workaround.
    

Problem summary

  • The issue was that sql retrieiving the the BO Staging tables
    was not looking at the module, thus if 2 BOs with the same name
    belonging to different modules had staging tables, Integration
    Object logic did not know which BO to use. The fix is to know
    pass in module name into the sql.
    

Problem conclusion

  • Resolved an Integration Object File to DC issue, where staging
    tables were not correctly loading on the Data Map tab, if the
    Business Object selected had the same name as another Business
    Object belonging to a different Module. This is targeted to the
    2h2016 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV88277

  • Reported component name

    TRI APPLCATION

  • Reported component ID

    5725F26AB

  • Reported release

    351

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-16

  • Closed date

    2016-08-17

  • Last modified date

    2016-08-17

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • 999
    

Fix information

Applicable component levels

  • R351 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"351","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
30 March 2022