ACK Import Issue
(Doc ID 2851443.1)
Last updated on DECEMBER 04, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 8.1.2 and laterInformation in this document applies to any platform.
Symptoms
User has an Agency for which two reporting destinations (Inbound and Outbound) are configured using the same Agency Identifier.
When a report is Generated with a specified Outbound Reporting destination, say {BP} SEAXXX (SEA) E2B, for which “Primary Receive Agency” is not checked,
when the ACK is received, Argus tries to import the ACK with Incoming Agency {BP} SEAXXX INCOMING E2B (SEA) with Profile (EMA 3.0) for which “Primary Receive Agency” is checked.
User expected that Argus would use the ACK profile defined in the Reporting Destination from which the report has been generated.
ERROR MESSAGES:
REPLICATION STEPS:
1) Create 2 Reporting destinations with same same Agency Identifier and different ACK Profile.
Reporting Destination 1 - “Primary Receive Agency” checked
Reporting Destination 2 - “Primary Receive Agency” not checked
2) Create report using "Reporting Destination 2" and get the ACK generated for the report.
3) Try to import the ACK back
Result: Argus Safety tries to import back using the Reporting Destination 1 for which “Primary Receive Agency” checked.
OCCURRENCE PATTERN: consistent, all users or any user who follows steps
Cause
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
Symptoms |
Cause |
Solution |
References |