these days a player mentioned that SAP has an issue with the creation of some SOAP request elements. Maybe someone of you has an idea how to deal with this?
The issue is
- Some SOAP elements are defined as OPTIONAL with a boolean type (e.g. constructionStep)
xml code<complexType name="StandardParams">
<complexContent>
<extension base="tns:PlanningParams">
<sequence>
<element maxOccurs="1" minOccurs="0" name="goalImportance" nillable="true" type="tns:GoalImportance"/>
</sequence>
<attribute name="availableMachineTime" type="xsd:int" use="optional"/>
<attribute name="basicConstructionMethod" type="xsd:string" use="optional"/>
<attribute name="constructionStep" type="xsd:boolean" use="optional"/>
<attribute name="endSequencingStep" type="xsd:boolean" use="optional"/>
<attribute name="improvementMethod" type="xsd:string" use="optional"/>
<attribute name="improvementStep" type="xsd:boolean" use="optional"/>
<attribute name="maximumNumberOfUnscheduledOrdersToBeAnalyzed" type="xsd:int" use="optional"/>
<attribute name="middleSequencingStep" type="xsd:boolean" use="optional"/>
<attribute name="sequencingMethod" type="xsd:string" use="optional"/>
<attribute name="startSequencingStep" type="xsd:boolean" use="optional"/>
<attribute name="tourReductionStep" type="xsd:boolean" use="optional"/>
</extension>
</complexContent>
</complexType> - If the ABAP source mentions the value of the property as "false" it causes the whole element not to be mentioned in the SOAP request which means the server - not being aware of the source of the request - has to treat the value based on a server side configuration.
- The server standard for "constructionStep" when StandardParams are applied is TRUE.
- Can you see the problem? If an ABAP developer wants to override the step by setting the source to false it doesn't cause the proper reaction.
Any help is appreciated!
Bernd