Incorrect 030 Record For Suspended CDRs (Doc ID 1339891.1)

Last updated on FEBRUARY 27, 2015

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 5-May-2013.

Goal

When a GPRS's CDR gets suspended for some reason in the pipeline process, the suspense out file contained an empty 030 record. This causes REL to fail.

See below snippet from the suspense out file where the record type 030 is coming empty, while this is supposed to represent xml details of the call in a blob format.

010 1 0 0 1309715107 1309715107 1309715107 0 0 00 966 SUSPENSE_CREATE 10000 /suspended_usage/telco SUSP_USAGE_TELCO_INFO_T{BYTES_IN:DECIMAL;BYTES_OUT:DECIMAL;CALLED_TO:STRING;
CALL_DURATION:DECIMAL;PRIMARY_MSID:STRING;SERVICE_TYPE:STRING;START_TIME:DATE;
USAGE_TYPE:STRING}
020 9 0 gprs_pipe 30007 gprs_pipe MARKUP_IN_XXX.edr GPRS 042 0 1 /account 1 0 0711G2002935 10800
030
040 49089 6211 00 10800 420032100891471 813 1309703647 913



Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms