Information Systems:Health Canada Monthly Activities Report (MAR) - Revision history

Jeremym: /* Running the MAR manually */

2021-09-01T19:51:56Z

Running the MAR manually

Norwinu: Fixed formatting

2021-06-02T20:57:18Z

Fixed formatting

Jeremym: /* Ignored transaction types */

2021-06-01T23:23:15Z

Ignored transaction types

Jeremym: /* Ignored transaction types */

2021-06-01T23:22:37Z

Ignored transaction types

Norwinu at 23:18, 8 January 2021

2021-01-08T23:18:32Z

Norwinu: /* Ignored transaction types */

2021-01-08T23:10:44Z

Ignored transaction types

Norwinu at 23:07, 8 January 2021

2021-01-08T23:07:52Z

Norwinu at 23:07, 8 January 2021

2021-01-08T23:07:18Z

Norwinu: /* Running the MAR manually */

2021-01-08T22:59:12Z

Running the MAR manually

Norwinu: /* Running the MAR manually */

2021-01-08T22:58:18Z

Running the MAR manually

@@ Line 40: / Line 40: @@
  Note: This runs the MAR for the previous period, respective to the current date. This method cannot be used to run the report for another period. Oddly enough, the "class runner" in Integrator does not allow the user to specify runtime/program arguments (for which the report date is the first arg), despite this being the case for scheduled task runners.
-* Log in to [http://xtgui.unipharm.local Integrator Admin Portal] (username admin).
+* Log in to [http://xtgui.unipharm.local:16999/admin/servlet/admin.AdminStart Integrator Admin Portal] (username admin).
 * Navigate to Class runner via the top menu.
 :[[File:2021-01-08 14_39_28-Iptor XT Platform.png|500px]]

@@ Line 18: / Line 18: @@
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.

@@ Line 18: / Line 18: @@
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.
 ) 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.

@@ Line 19: / Line 19: @@
 ) 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.
 ) 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.
-) 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
+) 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.
 ) 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.
-) 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
+) 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.
-    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,
+) 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.
 ==Running the MAR manually==

@@ Line 3: / Line 3: @@
 ==Report Business Logic==
 ====Ignored transaction types====
 These transaction types are ignored:
@@ Line 42: / Line 46: @@
 :[[File:2021-01-08 14_50_48-Iptor XT Platform.png|400px]]
 * The job takes a few minutes at most and wil be listed under Active class runners while it is running, during which the runtime log can be viewed. If the job finishes too quickly, view the log under Completed class runners and investigate any errors.
 ==Changelog==

← Older revision		Revision as of 23:07, 8 January 2021
Line 3:		Line 3:

	==Report Business Logic==		==Report Business Logic==
−	===Transaction and Stock sections===

		+	===Transactions===
⚫	# 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.
		+
⚫	# 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.
		+	====Ignored transaction types====
⚫	# 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.
		+	These transaction types are ignored:
⚫	# 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.~~
		+	* 907 (location movements) - These are transactions within the warehouse (e.g between shelf locations), and therefore have net-zero effect on inventory.
⚫	# 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.
		+	* 1001 (loss) - Losses are done as stock/balance adjustments and therefore are not technically a transaction from one establishment to another. Therefore, any losses will be reported manually by JohnT (or designated).
⚫	# 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.
		+
⚫	# 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.
		+	Email excerpt (JeremyM and JohnT discussion regarding MAR business logic)
−	# 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.
		+
⚫	# 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.~~
		⚫	# 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.
		⚫	# 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.
		⚫	# 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.
		⚫	# 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.
		⚫	# 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.
		⚫	# 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.
		⚫	# 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.
		+	# 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.
		⚫	# 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==		==Running the MAR manually==