Details

    • Customer:
      OMAN-Tel

      Description

      INPUT :
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
      <soapenv:Header/>
      <soapenv:Body>
      <ser:hasValidateDevice>
      <!-Optional:->
      <woNo>519664001</woNo>
      <!-Optional:->
      <subNo>45002577</subNo>
      <!-Optional:->
      <deviceType>MODEM</deviceType>
      </ser:hasValidateDevice>
      </soapenv:Body>
      </soapenv:Envelope>

      OUTPUT :
      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
      <ns2:hasValidateDeviceResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
      <return>Device(s) not valid with POS</return>
      </ns2:hasValidateDeviceResponse>
      </soap:Body>
      </soap:Envelope>

        Activity

        Hide
        Ayed Bada added a comment -

        Hello,

        The reported error is a *business validation error*, indicating that the provided data is not valid.

        To help identify *valid data*, please use the following query, which returns valid combinations of device type, work order number, and subscriber number:

        ```sql
        SELECT
        d.device_type,
        wo.wo_no,
        s.subscriber_number
        FROM FN_DEVICE d
        JOIN FN_WORK_ORDER wo
        ON wo.id = d.wo_id
        JOIN SUBSCRIBER s
        ON s.id = d.subscriber_id;
        ```

        However, even when *valid data is used, we are still encountering an error returned by an **external POS service*, as shown below:

        *Error message:*

        ```
        POS ERROR: Item serial number is not available in POS
        (Item - HWY_HG8245X6_8NE_ONT, Serial no - 48575443B83F17AB)
        ```

            1. Request Payload (SOAP)

        ```xml
        <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
        <SOAP-ENV:Header/>
        <SOAP-ENV:Body>
        <ns3:SubmitProductOrderRq xmlns:ns3="http://www.omantel.om/esb/messages/submitproductorder">
        <ns3:RequestHeader>
        <FunctionId>16002068</FunctionId>
        <Version>1.0</Version>
        <TransactionId>0</TransactionId>
        <RequestId>AR_487506</RequestId>
        <RequestorId>ARBOR</RequestorId>
        <RequestorChannelId>ARBOR</RequestorChannelId>
        <RequestorUserId>ARBOR</RequestorUserId>
        <RequestorLanguage>E</RequestorLanguage>
        </ns3:RequestHeader>
        <ns3:RequestBody>
        <ns3:OfferOrder>
        <ProductOffer>
        <ProductOfferId>90653749</ProductOfferId>
        <Category>Huawei</Category>
        <ServiceType>HWY_HG8245X6_8NE_ONT</ServiceType>
        <Type>ACT</Type>
        <SerialNo>abc126</SerialNo>
        </ProductOffer>
        <Subscriber>
        <SubscriberNo>45001641</SubscriberNo>
        </Subscriber>
        <User>
        <UserId>NEP</UserId>
        </User>
        </ns3:OfferOrder>
        </ns3:RequestBody>
        </ns3:SubmitProductOrderRq>
        </SOAP-ENV:Body>
        </SOAP-ENV:Envelope>
        ```

            1. Response Payload (SOAP)

        ```xml
        <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
        <soapenv:Body>
        <NS1:SubmitProductOrderRs xmlns:NS1="http://www.omantel.om/esb/messages/submitproductorder">
        <NS1:ResponseHeader>
        <FunctionId>16002068</FunctionId>
        <TransactionId>0</TransactionId>
        <RequestId>AR_487506</RequestId>
        <ReturnCode>350101</ReturnCode>
        <ReturnDesc>
        Item (Serial No - abc126) is already sold/installed.
        Kindly use another valid item.
        </ReturnDesc>
        </NS1:ResponseHeader>
        </NS1:SubmitProductOrderRs>
        </soapenv:Body>
        </soapenv:Envelope>
        ```

        Show
        Ayed Bada added a comment - Hello, The reported error is a * business validation error *, indicating that the provided data is not valid. To help identify * valid data *, please use the following query, which returns valid combinations of device type, work order number, and subscriber number: ```sql SELECT d.device_type, wo.wo_no, s.subscriber_number FROM FN_DEVICE d JOIN FN_WORK_ORDER wo ON wo.id = d.wo_id JOIN SUBSCRIBER s ON s.id = d.subscriber_id; ``` However, even when * valid data is used , we are still encountering an error returned by an **external POS service *, as shown below: * Error message: * ``` POS ERROR: Item serial number is not available in POS (Item - HWY_HG8245X6_8NE_ONT, Serial no - 48575443B83F17AB) ``` Request Payload (SOAP) ```xml <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:SubmitProductOrderRq xmlns:ns3="http://www.omantel.om/esb/messages/submitproductorder"> <ns3:RequestHeader> <FunctionId>16002068</FunctionId> <Version>1.0</Version> <TransactionId>0</TransactionId> <RequestId>AR_487506</RequestId> <RequestorId>ARBOR</RequestorId> <RequestorChannelId>ARBOR</RequestorChannelId> <RequestorUserId>ARBOR</RequestorUserId> <RequestorLanguage>E</RequestorLanguage> </ns3:RequestHeader> <ns3:RequestBody> <ns3:OfferOrder> <ProductOffer> <ProductOfferId>90653749</ProductOfferId> <Category>Huawei</Category> <ServiceType>HWY_HG8245X6_8NE_ONT</ServiceType> <Type>ACT</Type> <SerialNo>abc126</SerialNo> </ProductOffer> <Subscriber> <SubscriberNo>45001641</SubscriberNo> </Subscriber> <User> <UserId>NEP</UserId> </User> </ns3:OfferOrder> </ns3:RequestBody> </ns3:SubmitProductOrderRq> </SOAP-ENV:Body> </SOAP-ENV:Envelope> ``` Response Payload (SOAP) ```xml <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <NS1:SubmitProductOrderRs xmlns:NS1="http://www.omantel.om/esb/messages/submitproductorder"> <NS1:ResponseHeader> <FunctionId>16002068</FunctionId> <TransactionId>0</TransactionId> <RequestId>AR_487506</RequestId> <ReturnCode>350101</ReturnCode> <ReturnDesc> Item (Serial No - abc126) is already sold/installed. Kindly use another valid item. </ReturnDesc> </NS1:ResponseHeader> </NS1:SubmitProductOrderRs> </soapenv:Body> </soapenv:Envelope> ```

          People

          • Assignee:
            Mbaye Lo
            Reporter:
            Mbaye Lo
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:

              Drag and Drop