Information Systems:Health Canada Monthly Activities Report (MAR)

Overview

This page aims to document the business logic and processes around the MAR, a report automatically generated and sent to Health Canada each month

Report Business Logic

Transaction and Stock sections

1. For the domestic contacts, it's been determined that we will populate the report with only those contacts that have transactions in the reported month.
2. Internal replenishments (907 transaction type) are to be ignored as movements between MAI & RET are irrelevant. Only stock coming in or out of the building needs to be reported on.
3. Store inventory returns are triggered by Sales Order, Credits (800 transaction type). The MAR reference guide is limited in how these are handled and must be listed using the Transaction code of PURCHASED and a Transaction Reason of either RETURNED TO BE CONSUMED or RETURNED TO BE DESTROYED. Because we do not know the reason for the return or if the item will be put back into stock or destroyed at the time of the return we will assume that all returned inventory will have a reason code of RETURNED TO BE CONSUMED.
4. Stock returns to the vendor are triggered by Purchase Order, Credit (931 transaction type). The MAR reference guide is limited in how these are handled and must be listed using the Transaction code of SOLD and a Transaction Reason of either TO BE DESTROYED FROM STOCK TO BE CONSUMED or TO BE DESTROYED FROM STOCK TO BE DESTROYED. Because all of our inventory is determined to be stock to be consumed we will always choose TO BE DESTROYED FROM STOCK TO BE CONSUMED as the transaction reason.
5. There are other transaction types where we send product out to get destroyed (1002, 1010, 1020 and 1030) and where we destroy product ourselves on site (1000). These will also be handled the same as in point 4 with a Transaction code of SOLD and a Transaction Reason of TO BE DESTROYED FROM STOCK TO BE CONSUMED.
6. Transaction type 1001 is for a missing item. Any of these transaction types can be used for a positive or negative value. For simplicity sake if it's a negative or reduction of inventory then we would capture this on the transaction worksheet with a Transaction code of SOLD and a reason of RETAIL DISTRIBUTION as if it was sold to a store. If it's a positive or increase to inventory then we would use the Transaction code of PURCHASED and a reason of RETAIL DISTRIBUTION. NOTE: It is expected that a transaction type of 1001 would be a reduction to inventory so if that's not the case it might be worth somehow making this visible, like on an exception report or something so it can be looked at and investigated before submitting the report.
7. Transaction 1040 - Cycle Count Adjustment and 1043 - Unit of Measure Adjustment should be handled the same way as point 6. If the adjustment reduces inventory then we would capture this on the transaction worksheet with a Transaction code of SOLD and a reason of RETAIL DISTRIBUTION as if it was sold to a store. If it's a positive or increase to inventory then we would use the Transaction code of PURCHASED and a reason of RETAIL DISTRIBUTION. It is expected that adjustments could be positive or negative so accounting for both scenarios is all we would need to do.
8. The Destruction or Loss at the Site worksheet is mainly for manufacturing but there are two codes that apply to us. The first is you must report all destroyed substance / drug products by your company at your site. This is covered by transaction type 1000 and 1002 as these are both internal destruction types. It's possible that a wrong transaction type could be used when entering this data and that an internal destruction was actually an external and vice versa. Since these destruction transaction types are not very common it would be ideal if we could somehow provide visibility to any transactions that are reported using transaction type 1000, 1002, 1010, 1020 and 1030, like on an exception report or something like that so they can be looked at and investigated before submitting the report.
9. The other reason code that applies to us on the Destruction of Loss at the Site worksheet is Accidental Loss. These would include any negative inventory reduction transaction from type 1001, 1040 and 1043. I think it would also be useful to include these transaction types on an exception report as well as they would likely be rare and should be looked at.

Running the MAR manually

Sometimes the MAR has to be run manually if the report produced by the automated monthly run contains errors.

• Log in to Integrator Admin Portal (username admin).
• Navigate to Class runner via the top menu.

• Hit start beside the existing Class runner with the description HC MAR Test (or some variation)

• The job takes a few minutes at most and wil be listed under Active class runners, during which the running log can be viewed. If the job finishes too quickly, view the log under Completed class runners and investigate any errors.

Changelog

• Version?