Wireless usage records require a valid Serving PMN.
Common Cause
This GSM usage record requires a serving PMN, but it is either not specified or is incorrect in the usage record.
Common Resolution(s)
Actions you can take to resolve the problem:
If the serving PMN in the usage record is correct but is not in the PMN table, use Applications/ Backoffice Management/ PMN Management to add it to the PMN table.
The CDR may be bad or malformed (i.e. it may contain a bad Serving PMN). If so, it can be left alone (it will eventually age and no longer be visible) - or it can be purged immediately if desired.
If the usage record should be billed anyway, choose Override Rule on the usage record. If this is done frequently, consider a change to Unbillable Rules for this Unbillable Code. Note that ignoring lookup failures can have undesirable downstream repercussions – although some event type processing doesn’t care about Serving PMN, in others the Serving PMN is fundamental to determining the correct roaming agreement.
Details
Certain GSM-specific usage records require a Serving PMN in the usage record in order to rate and discount correctly. The Serving PMN in each such record must be known to CostGuard. In this case, this is a GSM-network specific CDR and one of the following occurred:
The Serving PMN cannot be determined: it is not in the original CDR and a default setting isn’t specified in Admin Console/ Business Rules/ Backoffice Settings/ Rating/ Usage/ Default Serving PMN.
The Serving PMN in the usage record could not be found in the PMN table.