[LS-490] P2P order Feasibility failure || Staging ---Urgent--- - Mobinets-JIRA

Details

Type: Bug
Status: Open Bug (View Workflow)
Priority: Normal
Resolution: Unresolved
Component/s: FN
Labels:
None Labels

Customer:

OMAN-Tel

Description

While calling below API for creating P2P order getting an error on stagging platform(.80)
On further investigation it is observed that while calling internal FN service i.e checkNewActivationP2PFeasibility, NEP is parsing exchange A value as KWR1 instead of QUR2 due to which NEP is rejecting order.
Please support.

@integration please share latest FN logs of .80 server.

Secondly FN API exposed to CRM should throw proper error message instead of this generic roll back error.

<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:ser=http://server.api.nep.mobinets.com/>
<soapenv:Header/>
<soapenv:Body>
<arborP2PLL_fCNA xmlns=http://server.api.nep.mobinets.com/>
<fAppType xmlns="">I</fAppType>
<fExc xmlns="">QUR2</fExc>
<fCabinet xmlns="">001</fCabinet>
<fDpoint xmlns="">0001</fDpoint>
<fDpoint2 xmlns=""></fDpoint2>
<fNoofPairs xmlns="">1</fNoofPairs>
<fTechnology xmlns="">MSAN</fTechnology>
<fExcB xmlns="">AKO2</fExcB>
<fCabinetB xmlns="">002</fCabinetB>
<fDpointB xmlns="">0002</fDpointB>
<fDpoint2B xmlns=""></fDpoint2B>
<fNoofPairsB xmlns=""></fNoofPairsB>
<fTechnologyB xmlns="">MSAN</fTechnologyB>
<fService xmlns="">P2P</fService>
<fSubno xmlns="">9995095</fSubno>
<fSubscr_Type xmlns="">L</fSubscr_Type>
<fWOID xmlns="">510930155</fWOID>
<fUsage_Type xmlns="">I</fUsage_Type>
<fOrder_Type xmlns="">INSD</fOrder_Type>
<fUserID xmlns="">m9714587</fUserID>
<fRemarks xmlns=""></fRemarks>
</arborP2PLL_fCNA>
</soapenv:Body>
</soapenv:Envelope>

<soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/>
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>org.springframework.transaction.UnexpectedRollbackException: Transaction silently rolled back because it has been marked as rollback-only</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>

checkNewActivationP2PFeasibility:
Request:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<ns3:checkNewActivationP2PFeasibility xmlns:ns3="http://server.api.nep.mobinets.com/">
<exchange>KWR1</exchange>
<cab>001</cab>
<dp>0001</dp>
<dp2 />
<nbOfPairs>1</nbOfPairs>
<exchangeB>AKO2</exchangeB>
<cabB>002</cabB>
<dpB>0002</dpB>
<dp2B />
<serviceTypeName>Digital data circuit with N/W</serviceTypeName>
<serviceTechnology>Copper</serviceTechnology>
<activeNeType>Multi Technology Access</activeNeType>
<activeNeCategory>MSAN</activeNeCategory>
<activeNeTypeB>Multi Technology Access</activeNeTypeB>
<activeNeCategoryB>MSAN</activeNeCategoryB>
</ns3:checkNewActivationP2PFeasibility>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:checkNewActivationP2PFeasibilityResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
<return>
<responseCode>10016</responseCode>
<responseMessage>Cabinet1: 001 Not Found</responseMessage>
</return>
</ns2:checkNewActivationP2PFeasibilityResponse>
</soap:Body>
</soap:Envelope>

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

added a comment - 07/Jul/25 9:26 AM

Cabinet 001 sent in the request is not found.

Show

added a comment - 07/Jul/25 9:26 AM Cabinet 001 sent in the request is not found.

Hide

Permalink

Abir Messaikeh added a comment - 09/Jul/25 7:42 AM

From: Shamim Ahmed <Shamim.Ahmed@mobinets.com>
Sent: Monday, July 7, 2025 11:49 AM
To: Zein Trabelsi <Zein.Trabelsi@nuiva.com>; Salem Dannawi <Salem.Dannawi@mobinets.com>; Abir Messaikeh <Abir.Messaikeh@nuiva.com>; integration <integration@mobinets.com>
Cc: Khaled Khalil <Khaled.Khalil@nuiva.com>; Khaled Ayoubi <khaled.ayoubi@omantel.om>
Subject: RE: P2P order Feasibility failure || Staging --~~Urgent~~--

Dear @Zein Trabelsi,

In below API NEP is passing exchange as KWR1 instead of QUR2 as per arbor API.So KWR1 cabinet 001 doestnt exist but QUR2 its exits.
This is only issue we have to resolve,had to parse correct Exc value which we are receiving from arbor under API:: arborP2PLL_fCNA

As per attached process table Exchange value under checkNewActivationP2PFeasibility API should be fExc which is QUR2.

<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:ser=http://server.api.nep.mobinets.com/>
<soapenv:Header/>
<soapenv:Body>
<arborP2PLL_fCNA xmlns=http://server.api.nep.mobinets.com/>
<fAppType xmlns="">I</fAppType>
<fExc xmlns="">QUR2</fExc>
<fCabinet xmlns="">001</fCabinet>
<fDpoint xmlns="">0001</fDpoint>
<fDpoint2 xmlns=""></fDpoint2>
<fNoofPairs xmlns="">1</fNoofPairs>
<fTechnology xmlns="">MSAN</fTechnology>
<fExcB xmlns="">AKO2</fExcB>
<fCabinetB xmlns="">002</fCabinetB>
<fDpointB xmlns="">0002</fDpointB>
<fDpoint2B xmlns=""></fDpoint2B>
<fNoofPairsB xmlns=""></fNoofPairsB>
<fTechnologyB xmlns="">MSAN</fTechnologyB>
<fService xmlns="">P2P</fService>
<fSubno xmlns="">9995095</fSubno>
<fSubscr_Type xmlns="">L</fSubscr_Type>
<fWOID xmlns="">510930155</fWOID>
<fUsage_Type xmlns="">I</fUsage_Type>
<fOrder_Type xmlns="">INSD</fOrder_Type>
<fUserID xmlns="">m9714587</fUserID>
<fRemarks xmlns=""></fRemarks>
</arborP2PLL_fCNA>
</soapenv:Body>
</soapenv:Envelope>

checkNewActivationP2PFeasibility:
Request:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<ns3:checkNewActivationP2PFeasibility xmlns:ns3="http://server.api.nep.mobinets.com/">
<exchange>KWR1</exchange>
<cab>001</cab>
<dp>0001</dp>
<dp2 />
<nbOfPairs>1</nbOfPairs>
<exchangeB>AKO2</exchangeB>
<cabB>002</cabB>
<dpB>0002</dpB>
<dp2B />
<serviceTypeName>Digital data circuit with N/W</serviceTypeName>
<serviceTechnology>Copper</serviceTechnology>
<activeNeType>Multi Technology Access</activeNeType>
<activeNeCategory>MSAN</activeNeCategory>
<activeNeTypeB>Multi Technology Access</activeNeTypeB>
<activeNeCategoryB>MSAN</activeNeCategoryB>
</ns3:checkNewActivationP2PFeasibility>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Thank U!!!!

Show

Abir Messaikeh added a comment - 09/Jul/25 7:42 AM From: Shamim Ahmed <Shamim.Ahmed@mobinets.com> Sent: Monday, July 7, 2025 11:49 AM To: Zein Trabelsi <Zein.Trabelsi@nuiva.com>; Salem Dannawi <Salem.Dannawi@mobinets.com>; Abir Messaikeh <Abir.Messaikeh@nuiva.com>; integration <integration@mobinets.com> Cc: Khaled Khalil <Khaled.Khalil@nuiva.com>; Khaled Ayoubi <khaled.ayoubi@omantel.om> Subject: RE: P2P order Feasibility failure || Staging -- Urgent -- Dear @Zein Trabelsi, In below API NEP is passing exchange as KWR1 instead of QUR2 as per arbor API.So KWR1 cabinet 001 doestnt exist but QUR2 its exits. This is only issue we have to resolve,had to parse correct Exc value which we are receiving from arbor under API:: arborP2PLL_fCNA As per attached process table Exchange value under checkNewActivationP2PFeasibility API should be fExc which is QUR2. <soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/ xmlns:ser= http://server.api.nep.mobinets.com/ > <soapenv:Header/> <soapenv:Body> <arborP2PLL_fCNA xmlns= http://server.api.nep.mobinets.com/ > <fAppType xmlns="">I</fAppType> <fExc xmlns="">QUR2</fExc> <fCabinet xmlns="">001</fCabinet> <fDpoint xmlns="">0001</fDpoint> <fDpoint2 xmlns=""></fDpoint2> <fNoofPairs xmlns="">1</fNoofPairs> <fTechnology xmlns="">MSAN</fTechnology> <fExcB xmlns="">AKO2</fExcB> <fCabinetB xmlns="">002</fCabinetB> <fDpointB xmlns="">0002</fDpointB> <fDpoint2B xmlns=""></fDpoint2B> <fNoofPairsB xmlns=""></fNoofPairsB> <fTechnologyB xmlns="">MSAN</fTechnologyB> <fService xmlns="">P2P</fService> <fSubno xmlns="">9995095</fSubno> <fSubscr_Type xmlns="">L</fSubscr_Type> <fWOID xmlns="">510930155</fWOID> <fUsage_Type xmlns="">I</fUsage_Type> <fOrder_Type xmlns="">INSD</fOrder_Type> <fUserID xmlns="">m9714587</fUserID> <fRemarks xmlns=""></fRemarks> </arborP2PLL_fCNA> </soapenv:Body> </soapenv:Envelope> checkNewActivationP2PFeasibility: Request: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header /> <SOAP-ENV:Body> <ns3:checkNewActivationP2PFeasibility xmlns:ns3="http://server.api.nep.mobinets.com/"> <exchange>KWR1</exchange> <cab>001</cab> <dp>0001</dp> <dp2 /> <nbOfPairs>1</nbOfPairs> <exchangeB>AKO2</exchangeB> <cabB>002</cabB> <dpB>0002</dpB> <dp2B /> <serviceTypeName>Digital data circuit with N/W</serviceTypeName> <serviceTechnology>Copper</serviceTechnology> <activeNeType>Multi Technology Access</activeNeType> <activeNeCategory>MSAN</activeNeCategory> <activeNeTypeB>Multi Technology Access</activeNeTypeB> <activeNeCategoryB>MSAN</activeNeCategoryB> </ns3:checkNewActivationP2PFeasibility> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Thank U!!!!

Hide

Permalink

Abir Messaikeh added a comment - 09/Jul/25 7:42 AM

Dear @Shamim Ahmed there is a pre defined rule in the process as below :

That means if the input exchange = QUR2 + cabinet = 001 , the exchange value should be overridden by KWR1 .
Name of Decision table = Exchange Cabinet Mapping
This is a business rule that has been pre-defined for more than 4 years.

Show

Abir Messaikeh added a comment - 09/Jul/25 7:42 AM Dear @Shamim Ahmed there is a pre defined rule in the process as below : <rule> <inputEntry id="inputEntry_InputExpression254807149_1062"> <text><![CDATA [== "QUR2"] ]></text> </inputEntry> <inputEntry id="inputEntry_InputExpression2076548139_1062"> <text><![CDATA [== "001"] ]></text> </inputEntry> <outputEntry id="outputEntry_fExc_1062"> <text><![CDATA ["KWR1"] ]></text> </outputEntry> <outputEntry id="outputEntry_fCabinet_1062"> <text><![CDATA ["001"] ]></text> </outputEntry> </rule> That means if the input exchange = QUR2 + cabinet = 001 , the exchange value should be overridden by KWR1 . Name of Decision table = Exchange Cabinet Mapping This is a business rule that has been pre-defined for more than 4 years.

P2P order Feasibility failure || Staging ---Urgent---

Details

Description

Activity

People

Dates

Agile

Drag and Drop