OPSM Audit Functionality For Some PLSQL Services added
(Doc ID 2197393.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Pedigree and Serialization Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Performance
Find problem with the audit trail functionality since when using PLSQL transactions.
With the non PLSQL transactions, find both the old and the new values when changing data of serial (ie : Serial status) manually.
However with the “Import serial” transaction, the “insert” of new serials is not audited. Then after changing the serial status, the old value doesn’t appear. Only the new value appears.
It is necessary every time a change is done, to record both the old and the new values. **
The issue can be reproduced at will with the following steps:
1. Serials > Maintain Serials
Product : 08699001870205
Serial : 999552
Unique Check String:08699001870205999552
2. “Import serial” transaction > “insert”
3. Audit Trail > Audit Trail History
Find that the new serial is not audited, after changing the serial, the old value does not occur.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|