My Oracle Support Banner

Timestamp Fields Are Assigned With The Current System Time / Pin_virtual_time By Default (Doc ID 760753.1)

Last updated on MARCH 20, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 6.7.0.0.0 and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

When calling a PCM_OP_CREATE_OBJ to create a custom object with a timestamp fields, timestamp fields are automatically assigned with system time if the field is not specified in the input flist.

-- Steps To Reproduce:
1. Define a custom object class with a timestamp field
2. Use testnap to call PCM_OP_CREATE_OBJ to create an instance of the custom object
3. Do not specify the timestamp field in the input flist

The expected result is the timestamp field being set to 0.
The actual result is the timestamp field being set to pin_virtual_time.

Solution

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
Goal
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.