The API is currently returning an empty response.

To retrieve data, please run the following SQL query to get valid request_id and service_name values:

SELECT
scd.request_id,
ssd.SERVICE_NAME,
scd.ACCOUNT_NAME
FROM
SRD_CUSTOMER_DETAILS scd
INNER JOIN
SRD_SERVICE_DETAILS ssd
ON scd.id = ssd.CUSTOMER_ID
INNER JOIN
SRD_HQ_NE_DETAILS_V shqnd
ON scd.ACCOUNT_NAME = shqnd.customer_name;

This query will help you identify valid data to use when testing the API.

Note: I attempted to test this on my local environment, but no valid data was available.

Please provide a sample in Omantel platforms 179 and 84 and to be demoed in SRD UI

What it does: Returns the HQ network element details for a customer associated with an SRD service request. It resolves the customer name from the SRD request using the serviceName, then looks up that customer's HQ NE from db.
Note: hqLat and hqLong parameters are accepted but not used in the current implementation.

How to construct a valid request:

Pick an SRD request that has customer details with a serviceName — use REQUEST_ID as requestId and the service name as serviceName
The customer name resolved from that request must exist in vue SRD_HQ_NE_DETAILS_V
Example structure:

<ns3:getHQ>
<requestId>214312</requestId>
<serviceName>1319442_FBB</serviceName>
<hqLat>0</hqLat>
<hqLong>0</hqLong>
</ns3:getHQ>

How to verify from SRD UI:
Open the request in SRD -> Customer Details tab -W the customer name shown there is what the API uses to look up the HQ NE. The returned objectId and type correspond to that customer's headquarters node in NEP inventory.

How to construct the request:

Step 1 — Find a valid requestId + serviceName from DB:
SELECT sr.REQUEST_ID, sd.SERVICE_NAME, cd.ACCOUNT_NAME
FROM SRD_CUSTOMER_DETAILS cd
JOIN SRD_SERVICE_REQUEST sr ON sr.ID = cd.REQUEST_ID
JOIN SRD_SERVICE_DETAILS sd ON sd.CUSTOMER_ID = cd.ID
WHERE cd.ACCOUNT_NAME IN (SELECT CUSTOMER_NAME FROM SRD_HQ_NE_DETAILS_V)
FETCH FIRST 5 ROWS ONLY;

Step 2 — Use the result in the SOAP call:
<ser:getHQ>
<hqLat>0</hqLat>
<hqLong>0</hqLong>
<requestId>REQUEST_ID_FROM_STEP1</requestId>
<serviceName>SERVICE_NAME_FROM_STEP1</serviceName>
</ser:getHQ>

How to verify the result:
DB confirm the HQ exists in the view:
SELECT * FROM SRD_HQ_NE_DETAILS_V
WHERE CUSTOMER_NAME = 'ACCOUNT_NAME_FROM_STEP1';

The API response (name, objectId, type) must match
HQ_NAME, OBJECT_ID, TYPE columns from that view row.

It worked fine on .84 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.internal.api.srd.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:getHQ>
<!-Optional:->
<hqLat>0</hqLat>
<!-Optional:->
<hqLong>0</hqLong>
<!-Optional:->
<requestId>383</requestId>
<!-Optional:->
<serviceName>1083481_FBB</serviceName>
</ser:getHQ>
</soapenv:Body>
</soapenv:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:getHQResponse xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/">
<return>
<name>CARILLION ALAWI LLC</name>
</return>
</ns2:getHQResponse>
</soap:Body>
</soap:Envelope>

BUT I'M GETTING ERROR ON THE STAGING .179

DO YOU HAVE THE CREDENTIALS OF THE  DB .80 TO VERIFY THAT THE SAME DATA ARE THERE FOR THE INPUT?

Hostname : wat-sf-db01t-p.omantel.om
username : NEP_80
password : qfHslnbOlQpYilHHdISY
service name : WFMSTG19C

Getting this error when fetching test data on the old platform DB .179:

ORA-00942: table or view does not exist
00942. 00000 - "table or view does not exist"
*Cause:
*Action:
Error at Line: 6 Column: 53

The new SQL script has been applied on the main trunk and cloud database, so the ORA-00942 issue is resolved there.

For the cloud environment, we need to deploy the new patch 4.0.0.8.

For staging, I have requested the integration team to refresh the server.