Difference between revisions of "Information Systems:Sending Weekly Pfizer Files"
| (24 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Weekly Pfizer File== |
==Weekly Pfizer File== |
||
| − | Although this is a basic file and a very simple process, it is nonetheless quite important. If we don't send this file every Monday morning then Pfizer will actually stop processing our orders. So you may find calendar reminders very helpful as it's easy to forget this crucial step. Jeremy sends this file regularly and John is the backup incase Jeremy forgets or is unavailable. For the future we can keep this process in the Information Systems department and the I.S. staff can provide the backup. |
+ | Although this is a basic file and a very simple process, it is nonetheless quite important. If we don't send this file every Monday morning then Pfizer will actually stop processing our orders. So you may find calendar reminders very helpful as it's easy to forget this crucial step. Jeremy sends this file regularly and John is the backup incase Jeremy forgets or is unavailable. For the future we can keep this process in the Information Systems department and the I.S. staff can provide the backup. John can continue to be a third or fourth level backup. |
===Background=== |
===Background=== |
||
| − | Pfizer Canada (#22337) wants to manually verify that the weekly dollar amount of product that we are selling to our stores does not exceed a threshold of $15,000 per week per store. To Pfizer Canada, anything above this amount would warrant further investigation and is a red flag for potential abuse. We negotiated with Pfizer and they have allowed us to police this weekly purchase threshold ourselves. However, to satisfy Pfizer's internal requirements we still need to send |
+ | Pfizer Canada (#22337) wants to manually verify that the weekly dollar amount of product that we are selling to our stores does not exceed a threshold of $15,000 per week per store. To Pfizer Canada, anything above this amount would warrant further investigation and is a red flag for potential abuse. We negotiated with Pfizer and they have allowed us to police this weekly purchase threshold ourselves. We do this through a monthly report that we pull off and check. However, to satisfy Pfizer's internal requirements we still need to send the text file every week. And since we are managing the weekly purchase amounts per store ourselves, the file we are sending is actually blank and just contains the mapped field names. The only thing that really changes with the submitted file week to week is the name of the file, as it has a date in it. |
===Process=== |
===Process=== |
||
| − | Every Monday morning first thing |
+ | Every Monday morning first thing go to: \\Superserver\BI\Common\Pfizer to find the latest Pfizer report. Open up last weeks report by double clicking on the filename, select Save As... from the File menu in Notepad and then name the file with the appropriate date according to the file naming convention. I also save a second copy on my desktop just to make it easier to attach it to an e-mail but this isn't necessary. The naming convention is: |
| − | + | unipharm.com-yyyymmdd.txt |
|
The date is always the previous Saturday. For example, the latest report at the time of writing this article is: unipharm.com-20171104.txt and the following weeks file will be named unipharm.com-20171111.txt. It's important to note that if there is a holiday on the Monday and we're not open you would send the file on the very next business day. This would not change the naming convention. |
The date is always the previous Saturday. For example, the latest report at the time of writing this article is: unipharm.com-20171104.txt and the following weeks file will be named unipharm.com-20171111.txt. It's important to note that if there is a holiday on the Monday and we're not open you would send the file on the very next business day. This would not change the naming convention. |
||
| + | Send the file via e-mail to: WeeklySalesReport@pfizer.com and cc: johnt@unipharm.com and jeremym@unipharm.com. For the subject line put: Weekly Pfizer Sales Report and make sure that you remove any signatures from the body of the email as they may cause the e-mail to be quarantined by Pfizer's e-mail security measures. This means that the body of the e-mail is completely blank and all that is included is a subject line and the attached file. That's basically it! Just hit send and you should receive an e-mail back from Pfizer shortly with the subject line that says: THIS IS AN AUTOMATED REPLY./CECI EST UN MESSAGE AUTOMATISÉ. The body of the e-mail reply looks like this: |
||
| − | Send the file via e-mail to: WeeklySalesReport@pfizer.com and cc: johnt@unipharm.com and jeremym@unipharm.com |
||
| − | |||
| − | For the subject line put: Weekly Pfizer Sales Report |
||
| − | |||
| − | Also make sure that if you are using a jpg uniPHARM issued signature you need to delete it as it will cause the e-mail to be quarantined by Pfizer's e-mail security measures. |
||
| − | |||
| − | That's it! Just hit send and you should receive an e-mail back from Pfizer shortly with the subject line that says: THIS IS AN AUTOMATED REPLY./CECI EST UN MESSAGE AUTOMATISÉ. The body of the e-mail looks like this: |
||
THIS IS AN AUTOMATED REPLY. |
THIS IS AN AUTOMATED REPLY. |
||
| Line 28: | Line 22: | ||
----------------------------------------------------------------------------------------------------------- |
----------------------------------------------------------------------------------------------------------- |
||
| − | Simply forward the automated reply e-mail to jeremym@unipharm.com and the process is complete. If you don't receive the automated reply check your spam filter as it could get stuck there. Pfizer usually sends the reply within 30 minutes. If you don't receive it keep your |
+ | Simply forward the automated reply e-mail to jeremym@unipharm.com and the process is complete. If you don't receive the automated reply check your spam filter as it could get stuck there. Pfizer usually sends the reply within 30 minutes. If you don't receive it keep watching for it and checking your e-mail spam filter and if it's been a couple of hours perhaps let the pharmaceutical buyer know that the file was sent but you're unsure if Pfizer received it. The pharmaceutical buyer should be able to verify that it was received by reaching out to their contacts. |
Latest revision as of 08:01, 2 August 2022
Weekly Pfizer File
Although this is a basic file and a very simple process, it is nonetheless quite important. If we don't send this file every Monday morning then Pfizer will actually stop processing our orders. So you may find calendar reminders very helpful as it's easy to forget this crucial step. Jeremy sends this file regularly and John is the backup incase Jeremy forgets or is unavailable. For the future we can keep this process in the Information Systems department and the I.S. staff can provide the backup. John can continue to be a third or fourth level backup.
Background
Pfizer Canada (#22337) wants to manually verify that the weekly dollar amount of product that we are selling to our stores does not exceed a threshold of $15,000 per week per store. To Pfizer Canada, anything above this amount would warrant further investigation and is a red flag for potential abuse. We negotiated with Pfizer and they have allowed us to police this weekly purchase threshold ourselves. We do this through a monthly report that we pull off and check. However, to satisfy Pfizer's internal requirements we still need to send the text file every week. And since we are managing the weekly purchase amounts per store ourselves, the file we are sending is actually blank and just contains the mapped field names. The only thing that really changes with the submitted file week to week is the name of the file, as it has a date in it.
Process
Every Monday morning first thing go to: \\Superserver\BI\Common\Pfizer to find the latest Pfizer report. Open up last weeks report by double clicking on the filename, select Save As... from the File menu in Notepad and then name the file with the appropriate date according to the file naming convention. I also save a second copy on my desktop just to make it easier to attach it to an e-mail but this isn't necessary. The naming convention is:
unipharm.com-yyyymmdd.txt
The date is always the previous Saturday. For example, the latest report at the time of writing this article is: unipharm.com-20171104.txt and the following weeks file will be named unipharm.com-20171111.txt. It's important to note that if there is a holiday on the Monday and we're not open you would send the file on the very next business day. This would not change the naming convention.
Send the file via e-mail to: WeeklySalesReport@pfizer.com and cc: johnt@unipharm.com and jeremym@unipharm.com. For the subject line put: Weekly Pfizer Sales Report and make sure that you remove any signatures from the body of the email as they may cause the e-mail to be quarantined by Pfizer's e-mail security measures. This means that the body of the e-mail is completely blank and all that is included is a subject line and the attached file. That's basically it! Just hit send and you should receive an e-mail back from Pfizer shortly with the subject line that says: THIS IS AN AUTOMATED REPLY./CECI EST UN MESSAGE AUTOMATISÉ. The body of the e-mail reply looks like this:
THIS IS AN AUTOMATED REPLY. We acknowledge receipt of your email, however its content has not yet been verified. Pfizer Canada Inc. -----------------------------------------------------------------------------------------------------------
Simply forward the automated reply e-mail to jeremym@unipharm.com and the process is complete. If you don't receive the automated reply check your spam filter as it could get stuck there. Pfizer usually sends the reply within 30 minutes. If you don't receive it keep watching for it and checking your e-mail spam filter and if it's been a couple of hours perhaps let the pharmaceutical buyer know that the file was sent but you're unsure if Pfizer received it. The pharmaceutical buyer should be able to verify that it was received by reaching out to their contacts.