Dear @Ayed Bada,

During SIT testing on the staging platform, we observed that orders are moving to "History" even after NEP receives an error response from Arbor during cancellation.

The SIT team has requested that these orders be interrupted instead, based on the specific Arbor response shown below.

As discussed, we will ask the OT to raise a GTM or CR, as this change is considered an enhancement.

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<ns3:CancelOrderRequest xmlns:ns3="http://omantel.om/ordermanagementservice">
<OT_EAI_HEADER>
<MsgFormat>CancelOrder.Req</MsgFormat>
<MsgVersion>0000</MsgVersion>
<RequestorId>ARBOR</RequestorId>
<RequestorChannelId>WS</RequestorChannelId>
<RequestorUserId>ARBOR</RequestorUserId>
<RequestorLanguage>E</RequestorLanguage>
<RequestorSecurityInfo>Eai</RequestorSecurityInfo>
<EaiReference>0</EaiReference>
<ReturnCode>0000</ReturnCode>
</OT_EAI_HEADER>
<Request>
<chgWho>v6272498</chgWho>
<orderId>91409551</orderId>
<itemId>520319366</itemId>
</Request>
</ns3:CancelOrderRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

<NS1:Envelope xmlns:NS1="http://schemas.xmlsoap.org/soap/envelope/">
<NS1:Body>
<NS2:cancelOrderResponse xmlns:NS2="http://omantel.om/ordermanagementservice">
<OT_EAI_HEADER>
<MsgFormat>CancelOrder.Req</MsgFormat>
<MsgVersion>0000</MsgVersion>
<RequestorId>ARBOR</RequestorId>
<RequestorChannelId>WS</RequestorChannelId>
<RequestorUserId>ARBOR</RequestorUserId>
<RequestorLanguage>E</RequestorLanguage>
<RequestorSecurityInfo>Eai</RequestorSecurityInfo>
<EaiReference>0</EaiReference>
<ReturnCode>0000</ReturnCode>
</OT_EAI_HEADER>
<Response>
<ReturnCode>0752</ReturnCode>
<ReturnMessage>Order cannot be cancelled after completion of BIP Milestone</ReturnMessage>
</Response>
</NS2:cancelOrderResponse>
</NS1:Body>
</NS1:Envelope>"

Thank U!!!