Unable To Trace The Intake Ack File
(Doc ID 2861449.1)
Last updated on DECEMBER 04, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 8.1.3 and laterInformation in this document applies to any platform.
Symptoms
After accepting the Local Event intake file from Worklist Intake screen, LAM Intake Service creates an ACK File but the ACK file name in not recorded in any logs or tables.
Steps to Repeat:
1) Drop in a local event XML file into LAM Intake Folder
2) Login to Argus Safety as a LAM user
3) Click on Worklist and go to Intake Worklist screen
4) Search for the Intake record that was dropped in step 1
5) Click on Create Local Event button
6) Select Report Type
7) Click on Create Local Event button
8) Save the Local Event
9) Go to Intake Out folder and observe that it created the ACK file
Example ACK File Name:
10) Go to INTAKE_CASES table, find the local event and check the status
11) Observe that it updated the status to 2 but there is no ACK file name mentioned in the table
When Axway completes the unsuccessful processing of a new ACK file, it is difficult to verify that the file was ever created.
This makes it difficult to diagnose or troubleshoot where the failure occurs.
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 |