ACK Not Getting Mapped In SAFETYREPORT Table
(Doc ID 2055646.1)
Last updated on MAY 16, 2023
Applies to:Oracle Argus Safety - Version 7.0.4 and later
Information in this document applies to any platform.
On Applications Oracle Argus Safety : Version 7.0.4 (and earlier versions)
If more than one versions of a particular report are destined to same authority, and are also transmitted in one message, then the ACK is being updated in ACKNOWLEDGMENT table for
both reports but in safetyreport table only one is getting mapped.
This results in the other report (for which the ACK is not mapped in safetyreport table) remaining as waiting for ACK and its not getting marked as submitted.
Ideally both should be acknowledged in Safetyreport, currently only one is linked to acknowledgement
The issue can be reproduced at will with the following steps.
1. Submit two versions of report simultaneously to same authority, so that both are transmitted in one message.
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