IBM Support

IJ40145: BMXAA4187E ERROR WHEN DEFINING JSON DATA USING JSON SPI FOR OUTBOUND JSON MAPPING

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

  • When defining JSON data with Json SPI the following error is
    received for outbound json mapping:
    
    BMXAA4187E - The relationship spi:xxxxxx does not exist for
    business object spi:xxxxxx. Verify that the relationship
    specified in parameter spi:action exists in the Maxrelationship
    table.
    
    Steps using maxdemo:
    
    1.) Create a new JSON Mapping using spi:attributename, like the
    example below:
    
    {
    "spi:wonum":"TEST",
    "spi:siteid":"BEDFORD",
    "spi:description":"TEST",
    }
    
    Object Structure: MXWO
    
    Direction: Outbound Processing
    
    2.) Go to Properties tab
    
    Click to create a New Row for JSON Properties Mapping for
    Process Order 1
    
    Try to add any Target Property starting with "spi:"
    
    
    RESULTS:
    
    BMXAA4187E - The relationship spi:xxxxxx does not exist for
    business object spi:xxxxxx. Verify that the relationship
    specified in parameter spi:xxxxxx exists in the Maxrelationship
    table.
    
    VERSION:
    Tivoli's process automation engine 7.6.1.2
    

Local fix

Problem summary

Problem conclusion

  • The fix for this APAR is contained in the following
    maintenancepackage:
    Release 7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ40145

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-05-19

  • Closed date

    2022-05-22

  • Last modified date

    2022-05-22

  • 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

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

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

Document Information

Modified date:
23 May 2022