My Oracle Support Banner

Profile Tag Dates Earlier than January 1st 1970 Do Not Display in the SMS Screens (Doc ID 1591360.1)

Last updated on MARCH 06, 2019

Applies to:

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

Symptoms

Profile Tag date fields stored with a value earlier than the UNIX epoch 0 start date (January 1st, 1970) will not display in the Service Management System (SMS) screens, as defined by Subscriber Profile Manager (SPM) configuration.  When attempting to modify and save the same date via the SMS screens, the Profile Tag is deleted.

Other methods of saving, modifying or displaying a Profile Tag date work fine though.  For example, the Provisioning Interface (PI) can store a date earlier than January 1st 1970 correctly:

CCSCD9=CHG:TAG=Update Date,MSISDN=<MSISDN>,VALUE=19020101000000;
CCSCD9=CHG:ACK,SYNSTAMP=2013100112165459;

And the correct vlue is returned when queried:

CCSCD9=QRY:MSISDN=<MSISDN>,TAG=Update Date;
CCSCD9=QRY:ACK:Update Date=19020101000000,SYNSTAMP=2013100112165460;

A look at the subscriber's stored profile also shows the date is saved correctly:

/<DIR>/bin$ ./acsProfile -u / -z <MSISDN>
...snip...
0x01e240 Update Date 4 80 17 e8 80
  01 January 1902 00:00:00 (2149050496)

The acsProfile tool also allows saving these dates via manual commands, such as:

/<DIR>/bin$ ./acsProfile -u / -z <MSISDN> -W 294e47 -H 83AA7E80

Cause

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
Symptoms
Cause
Solution
References


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