PTV Logistics Product Forum

{
  "faultInfo": {
    "$type": "ParameterConflictFault",
    "hint": "Either change the calculation mode or remove the tweaks to objective from the plan tours options.",
    "parameterA": "/planToursRequest/planToursOptions/@tweaksToObjective",
    "parameterB": "/planToursRequest/planToursOptions/@calculationMode",
    "valueA": "not null",
    "valueB": "CUSTOM"
  },
  "message": "To use calculation mode CUSTOM the tweaks to objective may not be set."
}

  "planToursOptions": {
    "tweaksToObjective": null,
    "considerOrderPriorities": true,
    "calculationMode": "QUALITY",
    "customCalculationModeConfiguration": null
    "planningHorizon": {
      "$type": "StartEndInterval",
      "start": "2025-10-19T22:00:00+02:00",
      "end": "2025-10-20T21:59:59+02:00"
    },
    "restrictions": { "mixedLoadingProhibitions": [] }
  }

• "theProperty" : null
• not at all

If you want to use a custom blob (CalculationMode="CUSTOM") you are supposed to not set the tweaks...

"tweaksToObjective": { ...content... }	runs into the error - not part of this thread, the client knows how to populate a property , /td]	http-400
"tweaksToObjective": {}	Is not NULL but an object which has the properties with their default values: avoidIntersections=false, minimizeNumberOfTours=true and therefore creates the error	http-400
"tweaksToObjective": null	works as designed	http-200
"tweaksToObjective" doesn't appear in the request	works fine	http-200

JSON wrote:{
"faultInfo": {
"$type": "ParameterConflictFault",
"hint": "Either change the calculation mode or remove the tweaks to objective from the plan tours options.",
"parameterA": "/planToursRequest/planToursOptions/@tweaksToObjective",
"parameterB": "/planToursRequest/planToursOptions/@calculationMode",
"valueA": "not null",
"valueB": "CUSTOM"
},
"message": "To use calculation mode CUSTOM the tweaks to objective may not be set."
}

This is a common challenge when integrating SAP systems with external services via JSON-based APIs. SAP’s serialization behavior—especially when using ABAP structures or classes—can indeed result in empty objects ({}) being serialized instead of null or omitting the property entirely.
Here are a few approaches your client can explore, depending on their SAP setup (e.g., using ABAP, SAP PI/PO, or SAP CPI):

Option 1: Force null in JSON Output
If the goal is to explicitly send "tweaksToObjective": null, the ABAP structure or class must have the field set to INITIAL (i.e., not instantiated) and the JSON serializer must be configured to include nulls.
In ABAP:

Code: Select all

ABAPDATA: ls_payload TYPE zmy_structure.
CLEAR ls_payload-tweaksToObjective. " Ensures it's initial (null)

Then, when serializing:

Code: Select all

ABAPDATA(lo_writer) = cl_sxml_string_writer=>create( type = if_sxml=>co_xt_json ).
CALL TRANSFORMATION id  
  SOURCE mydata = ls_payload  
  RESULT XML lo_writer.Show more lines

But this may still omit the field entirely unless you use a custom serializer or enhancement.

Option 2: Omit the Property Entirely
If the server prefers the property to be absent rather than null, then the field should be left unpopulated and the serializer should be configured to skip initial fields.
In ABAP, this is the default behavior for many serializers. However, if a nested structure is instantiated (even if empty), it will be serialized as {}.
So:

Code: Select all

ABAPCLEAR ls_payload-tweaksToObjective. " Do not instantiate it

Avoid:

Code: Select all

ABAPCREATE DATA ls_payload-tweaksToObjective. " This leads to {}

Option 3: Use Custom JSON Serialization
If SAP’s standard serialization doesn’t meet the requirement, your client can:

• Use cl_trex_json_serializer or cl_fdt_json for more control.
• Manually build the JSON string using string templates or cl_sxml_string_writer.

Example:

Code: Select all

ABAPDATA(json_string) = |{{ "tweaksToObjective": null, "otherField": "{ ls_payload-otherField }" }}|.

Best Practice

• Document the API contract: Ensure the receiving system clearly defines whether null or omission is preferred.
• Test with Postman or curl: Simulate both cases to confirm server behavior.
• Log the serialized JSON: To verify what SAP is actually sending.