Issue: Incomplete Payload Received at Consumer API for Multi-Line SAP Purchase Order

Connectors & Integrations
, ,
1

Ihave observed that when a Purchase Order (PO) with multiple line items is created in SAP and published to the Solace Broker, the payload received by the Consumer Azure API contains details for only a single line item.

Given that Solace acts as a message broker and does not inspect, modify, or truncate message payloads, this behavior is unexpected. I would like to understand the potential reasons behind this discrepancy.

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Looking at the scenario described, let me break down the reasoning:

  1. The issue involves a message payload being truncated or incomplete when received by the consumer, specifically showing only one line item from a multi-line item PO.

  2. The documentation indicates that Solace event brokers act as message brokers and do not modify message payloads during transmission.

  3. Since Solace does not inspect, modify, or truncate message contents, the issue is likely occurring either at:

    • The publishing side (SAP system)
    • The consuming side (Azure API)
    • Or in the message handling/processing logic

  4. The documentation shows examples of message handling patterns and potential issues that can arise with message processing, but none indicate that Solace would truncate or modify message contents.

Given this analysis, Solace is unlikely to be the source of the truncation issue. The problem is more likely occurring in one of these areas:

  1. Message serialization/formatting at the SAP source
  2. Message deserialization/parsing in the Azure API consumer
  3. Application-level message handling logic in either system

To properly diagnose this issue, you should:

  1. Verify the complete message payload at the SAP publishing point
  2. Inspect the raw message contents in the Solace event broker
  3. Check the message handling code in the Azure API consumer

Here are relevant sources for investigating message handling:

3

Hi @swapnil_mahajan ,

The obvious explanations I can think of to explain the behaviour you are seeing are:
a) The publishing application (SAP) is only publishing a Purchase Order with a single line item.
b) The consumer application (Azure API) is only processing the first line item in a multi line Purchase Order.

Have you tried inspecting the payload in the broker before it is being consumed?
Or wire-tapping the payload by adding another subscriber to the same topic that can print out the payload (maybe try using sdkperf, solace-pretty-dump, or the Try-Me tab in the broker)?

Best regards,
Christian