Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Billing and Revenue Management (MOSC)

POID generation for Realtime and Delayed Events

May 5, 2016 4:35AM edited Jun 3, 2016 5:04AM in Billing and Revenue Management (MOSC) 1 commentAnswered

Hi Experts,

As of now for generating POID below logic is followed.

POID = 2^44 * num_days (for realtime partitions)

POID = 2^60 + num_days * 2^44 for delayed partitions.

Why the logic / formula is different for generating POID_ID for realtime and pipeline events ? Any technical reason behind this ?

Tagged:

FM/Custom Opcodes

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

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

Category Leaderboard

Top contributors this month