My Oracle Support Banner

Updated AlternateWalletDetails SDK Function Does Not Select Correct VWS Pair (Doc ID 2789700.1)

Last updated on JULY 20, 2021

Applies to:

Oracle Communications Network Charging and Control - Version and later
Information in this document applies to any platform.


On Oracle Communications Network Charging and Control (NCC) version,

Due to an issue with Ported-out subscribers looking like on-net subscribers, Customer required implementation of the Enhanced AlternateWalletDetails function mentioned on KM <Note 2749904.1>.

But when they deployed this on their production, it is observed that the Wallet Info (WI) Request for the AlternateWalletDetailsRequest was going to the wrong VWS  and beVWARS process reports the below errors during this:


This was because the specific <WALLET_ID> is on VWS2, but the logical subscriber is on VWS1.

Here they need this lookup to be more intelligent and go to the correct VWS. It is expected that this function will automatically determine the correct VWS pair and send the request - it shouldn't have to look it up as part of the node processing.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.