Open APIs

Dear Community,

We have the scenario where the customer has placed a MNP order on day 1 with us. Now due to some reason while the order is still in-progress ( as MNP orders could take several days) he placed a second MNP order for the MSISDN on day2. The second order will fail from the carrier side as there is already one running order. What is the best way to handle such error cases.

• Could we use POQ to restrict the second order being placed ? But POQ mainly talks about offerings and not about orders
• Could we check for an in-progress MNP order inside COM based on MSISDN and fail the second order
• We do nothing in COM, and receive the rejection from carrier that it is not allowed to port the number twice.

is there any recommendation ? We would like to hear how industry has implemented such use case.  

Thanks,

Rosalin

Hi,

not sure what a MNP is, but I would see 2 separate scenarios:

1. Asset-Based Ordering, when the starting point of the order is an existing active product customer would like to alter (Modify, Change, Renew, move...)
2. new sale

for scenario 1:

1. Customers access their "my products" list. they pick one product to open the PDP (product details page)
2. POQ does pre-pick eligibility check:
   1. POST /CHECK... TMF679 with the product Id  and Action= Modify, Change, Renew...
      1. if you want to check multiple Action, repeat the product Id in the array
   2. POQ Service checks if there are any open order on that product Id or service identifier Id (MSISDN, fiber termination point...)
3. POQ returns qualificationItemResult and eligibilityResultReason for each action.

for scenario 2:

In a nutshell, you want to avoid that the 2nd order (or even a 1st order) uses a resource that is:

• already assigned to an active product
• already reserved

SQ (TMF645) can do that.

hope this helps.

Dear Community,

We have the scenario where the customer has placed a MNP order on day 1 with us. Now due to some reason while the order is still in-progress ( as MNP orders could take several days) he placed a second MNP order for the MSISDN on day2. The second order will fail from the carrier side as there is already one running order. What is the best way to handle such error cases.

• Could we use POQ to restrict the second order being placed ? But POQ mainly talks about offerings and not about orders
• Could we check for an in-progress MNP order inside COM based on MSISDN and fail the second order
• We do nothing in COM, and receive the rejection from carrier that it is not allowed to port the number twice.

is there any recommendation ? We would like to hear how industry has implemented such use case.  

Thanks,

Rosalin