Audit Trail for Discount Object Is Ignored by Batch Pipeline (Doc ID 2346403.1)

Last updated on SEPTEMBER 12, 2023

Applies to:

Goal

On : 7.5.0.16.0 version, Pipeline Manager

Batch Pipeline does not seem to use correctly the audit trail for pricing data like /discount.

It is correctly using the /au_purchased_discount, selected based on the effective time of the usage. But then it always seems to use the current version of the /discount, rather than referring to the valid /au_discount object based on the effective time of the usage being loaded.

Steps to reproduce:

1. Set Pin Virtual Time (PVT) = pvt1
2. Configure a /discount and point to discount model A
3. Move PVT to pvt2 = pvt1 + 3 days (for example)
4. Change the /discount by pointing it to discount model B (for example, from Pricing Center, edit the discount)
5. Restart the Batch Pipeline
6. Load a usage having date = pvt1 (or pvt1 + 1 day), anything BEFORE pvt2

Expected behavior:

The expectation is to see discount model A been used.

Actual behavior:

One can see that discount model B (the most recent one) is used which is incorrect.

What is the reason of this wrong behavior and how to overcome it?
 

Solution

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