Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Current »

Issue Prompt

The hospital notifies the development team of a missing CUBEX transaction.

Needed Input

You will need the following to properly handle these requests.

Input Needed

Required

Example

Reason / Purpose

CUBEX Transaction ID

Yes

123132

Needed to track down in the CUBEX logs. Two-part key with Database.

CUBEX Database

Yes

small animal

Needed to track down in the CUBEX logs. Two-part key with Transaction ID.

Resolving the Issue

Different actions are required based on where you find the transaction if at all. Below goes over where you should start looking and what needs to be done if found there.

1st Search In cubex_billing_log_transaction

DECLARE @transactionId as varchar(max) = '00000'
DECLARE @databaseNumber as int = 1 -- 1 = small animal; 2 = large animal; 3 = tomo

select * 
from [cubex_billing_log_transaction] l
WHERE	l.cubex_transaction_id = @transactionId
	AND l.vmis_database_number = @databaseNumber

Has Null Date Processed

If date_processed is null the CUBEX Billing Sync command process-transactions failed. Fix the issue and the system will automatically run this.

Has a Date Processed but no Foreign Keys

This is a valid response based on the transaction itself. To investigate further look into sp_cubex_transaction stored procedure.

Has a Date Processed with Foreign Keys

The data looks correct. Send the requesting user the keys for validation.

2nd Search In cubex_billing_log

DECLARE @transactionId as varchar(max) = '00000'
DECLARE @databaseNumber as int = 1 -- 1 = small animal; 2 = large animal; 3 = tomo

SELECT *
FROM cubex_billing_log l
LEFT JOIN cubex_billing_log_transaction t ON t.cubex_billing_log_id = l.id
WHERE	l.database_no = @databaseNumber
	AND CAST(l.raw_data as varchar(max)) LIKE '%>' + @transactionId + '<%'

Has a record in cubex_billing_log but not cubex_billing_log_transaction

If true, the CUBEX Billing Sync command sa-process | lg-process | tomo-process has failed to properly upload. Log onto eadu.cvm.tamu.edu and check the C:/Cubex_Billing_Sink/retry-log/ /|C:/Cubex_Billing_Sink/failed-log/ for a file with the transaction id. There may also be an email sent to help desk with the issue specified.

Once the issue is fixed move the retry log file from failed-log to retry-log and it will automatically reprocess the file.

3rd Search in eadu.cvm.tamu.edu Log Folders

Log onto eadu.cvm.tamu.edu and check the logs files under:

  • C:/Cubex_Billing_Sync/unprocessed-files/ - If you find it here the Cubex Billing Sync is not currently running.

  • C:/Cubex_Billing_Sync/retry-logs/ - The system is trying to upload but is failing. Check the log file for what is going on.

  • C:/Cubex_Billing_Sync/failed-logs/ - The system tried 10 times and failed. Check help desk for the work item and / or open the log file and see what is going on.

  • C:/Cubex_Billing_Sync/resolved-retry-logs/ - The system successfully uploaded. Restart from search 1.

  • No labels