List of selected release notes Sector : 01- Purchases ................................................................................................................. 2

Sector : 02- Sales ......................................................................................................................... 5

Sector : 03- Statistics ................................................................................................................. 13

Sector : 04- Price Structure ....................................................................................................... 14

Sector : 05- Finances ................................................................................................................. 16

Sector : 06- Warehouse ............................................................................................................. 21

Sector : 07- Administrator ......................................................................................................... 32

Sector : 08- Invisible to users .................................................................................................... 34

List of selected release notes

Sector : 01- Purchases

BEA419 - Phenix - Include the Interco in the average sales in CAPS multi-warehouses. Objective of change: We need to be able to define by vendor if the purchases done in CAPS multi-warehouse are consolidated without creating Interco. If the option is unchecked for the vendor, an Interco transfer will be created. How to observe the change: 1-Go in Phenix / Utilities / System Parameters (Purchase tab) : the option "Include the Interco in the sales stats" has been removed (will not be necessary anymore). 2-Always in System Parameters (Purchase tab) :the option " Interco Transfers in CAPS" is still a valid option. You just need to take note that this option is only for CAPS regular (and not for CAPS multi-warehouse). 3-Go in Phenix / Purchases / Maintenances / Vendors (Purchase Detail / Performance tab): a new option "Interco Consolidated" has been added. By default, the check box will not be checked. This option allows to merge the destination warehouses to the source warehouse in CAPS multi-warehouse and to order only for the source warehouse without sending immediately inventory to other warehouses. This option has not effect in CAPS regular. 4- The report RAP_MODIF_MAINT_VENDOR has been modified to trace the new option in the vendor's maintenance. You will know which employee made the modification on this option (who has checked or unchecked the option!). 5-Go in Phenix / Purchases / Orders / Assisted Purchase Order Entry (CAPS) (regular): You must order products with and without Intercos and make sure CAPS is working as before. Create purchase order with and without Intercos. For those who have not multi-warehouses, simply create purchase orders to see that everything is working as before (validate the sales and purchases historic, the inventory, all buttons, etc...). 6-Go in Phenix / Purchases / Orders / Multi-Warehouse Purchase Order Entry: In the main screen, a new column has been added, for informational purposes, to indicate if the vendor is with Interco Consolidated or not. (Note: This option of consolidation works also for Broker purchases.) In the detail screen of the purchase order, you will notice that the bottom section has a little bit change (the column "Sugg. Qty" has been renamed with "Total Sugg.Qty", a new column "Whs Sugg. Qty" has been added and the column representing the quantity is automatically changing to "Weight" if the product must be order by weight). It is still possible to press the function keys Ctrl + Shift + F2 to see the information of "Outgoing Interco (on PO)" and "Incoming Interco (on PO)" A) Vendor not checked for the option "Interco Consolidated": the purchases made for this vendor will generate Interco's transfer (as before). The new column "Whs. Sugg. Qty" allows to see more easily from which warehouse the suggested quantity comes from. So if you have 2 warehouses (#99-source and #91-destination) and you purchase a product that can transfer Interco: if the suggested quantity is 100 cases for the source warehouse and 25 cases for the destination warehouse, the column Total Sugg. Qty will display 125 cases. In the Summary section, it will be possible to see the ordered quantity (as before), but the column "Qty /Weight Interco" has been renamed with "Warehouse Qty / Weight". When you will be on the source warehouse information’s, you will be able to see the quantity that is for the source warehouse (in this new column). Example: If you ordered a total of 100 cases, and 40 cases if for the destination warehouse (#91), you will see that for the source warehouse (#99), the "ordered qty" will be 100cs and the "warehouse Qty" will be at 60cs. When you will be on the destination warehouse information’s (#91), the "Ordered Qty" will be empty (as before) and the "Warehouse Qty" will be at 40cs. When you will complete the order with an Interco product, make sure that an Interco Transfer has been created (In Interco Transfer / Transfer Entry. B) Vendor checked for the option "Interco Consolidated": The purchases done for this vendor will not be generating Interco Transfers. It will be an order done by the source warehouse and which will stay in the source warehouse until you decide to transfer some inventory in the other warehouse. With this option, the destination warehouse will not be displayed in CAPS multi-warehouse. However, the information’s of the destination warehouse will be included with the information’s of the source warehouse. Example, the average sales by week, the sales historic, the product's inventory, the field "Week/Inv", the suggested quantities will include the destination warehouse inside the source warehouse information’s (on one line). Some buttons in CAPS Multi-Warehouse screen will displayed all warehouses when the vendor will be "consolidated" as the customer's prebooks and customer's regular orders button. 7- The reports that considers the average sales have not been modified, but you must generate these reports to make sure they work as before: -RAP_INVENTAIRE_DETAILLE -RAP_ACHATS_SANS_PROMOTION -RAP_VIEILLISSEMENT_INVENTAIRE -RAP_PRODUITS_RECOMMANDER

BER10279 - Phenix - Do not include the 'No reply' message to the email when the sender address is not the one from the System parameters. Objective of change: Do not include the 'No reply' message to the email when the sender address is not the one from the System parameters. The correction has been made mostly for the purchase order report that should be send to the vendor and come from the buyer (replenisher). The vendor should not ask himself if he can answer the email (to the buyer) or not. So, the message of "No reply to this email" should be removed when the buyer is the email sender. How to observe the change: Go in System parameters and validate the email address that is defined in first tab (Identification). For example, for the test, we will have noreply@colabor.com define in this field. Go in the job schedule and select any report, but make sure to fill the bottom section to send the report by email to your attention. In the email you will receive, you will see that the email comes from the address noreply@colabor.com and that a message in bold is displayed " Please note: This e-mail was sent from a notification...". Select any vendor and go in Purchases / Maintenances / Vendors, in the Address tab to indicate an email address to who send the report of purchase order (in the field "Email" at the bottom of the screen). For this example, indicate your email address. ATTENTION: take note of the replenisher code for this vendor and go in Utilities / Security / Users to see if an email address is defined for the replenisher. If not, you must define one, if not, the test wont work, since the system will automatically take the email address from the system parameters and it will be normal that the message of no reply will be displayed. Go in Purchases / Orders / Direct Purchase Orders (or in CAPS) and create a new purchase order and send the order. ATTENTION: in the field "Replenisher", you must confirm the buyer's (replenisher) code so his email address will be defined as the sender. A blue pop-up will be display and you must check the check box " Send by email" to receive the purchase order report by email! Result in the email: The buyer (replenisher) is the sender of the email, your email address is the address of the vendor (recipient address) and the message in bold won’t be displayed " Please note: This e-mail was sent from a notification...".

BER10284 - Phenix (report) - Adjust the total cost in the purchase order report when the product is from definition type 'D' Objective of change: Adjust the total cost in the purchase order report (RAP_BON_DE COMMANDE) when the product is from definition type 'D'. How to observe the change: Create a purchase order for a product to buy in solid format and to invoice by weight. Display the report of the purchase order and look at the cost column. The price that was displayed was the cost for one kilo and it should be the ordered quantity multiplied by the product's weight and by the kilo cost. Note: At Colabor Boucherville and AOF, this report is personalized and no modification has been done for these customers.

CSC9712 - Phenix - Display in CAPS the Exhibition participating products (from SG2A system) and the total bought during the Exhibition

FOR COLABOR BOUCHERVILLE ONLY Objective of change: Display in CAPS the Exhibition participating products (from SG2A system) and the total bought during the Exhibition How to observe the change: N/A

CSC9810 - Phenix (report) - Modify the report to display the sales and purchases according to a promotion

Objective of change: Modify the report to display the sales and purchases according to a promotion. This report (RAP_VENTE_ACHAT_PAR_PROMOTION) will allow to the comparison of the purchases done versus the sales done for a specific promotion and will allow to know if you lose some opportunities. How to observe the change: Go in job schedule and generate the new report RAP_VENTE_ACHAT_PAR_PROMOTION for a specific promotion type and for the exact beginning and ending date of the promotion selected.

CSC9866 - Phenix - Create a procedure (.csv file) that display the last promotion and the next promotion of active products

Objective of change: Create a procedure (.csv file) that display the last promotion and the next promotion of active products. How to observe the change: Go in job schedule and select the new procedure LIST_NEXT_AND_LAST_PROMOTIONS. It is possible to select which character you wish to separate the information in the .csv file. If you do not specify any character, the file will be separate with a semicolon. You must indicate an email address in the bottom section to receive the file.

CSC9896 - Phenix - Produce in Phenix, the product's catalogue that was done in Access for Colabor Boucherville. FOR COLABOR BOUCHEVILLE ONLY Objective of change: Produce in Phenix, the product's catalogue that was done in Access for Colabor Boucherville. How to observe the change: N/A

CSC9907 - Phenix - Display the volume that is found in the Purchase order inquiry in the EDI file sent to the vendor. Objective of change: Display the volume that is found in the Purchase order inquiry in the EDI file sent to the vendor. How to observe the change: Go in the Vendor's maintenance and select a vendor for which the EDI purchase order file must be sent (Go in the EDI/Communication type. The EDI transaction type "Purchase order" must be there). Create a new purchase order for this vendor with many products. Once the purchase order is sent, go in Purchases / Orders / Purchase Order Inquiry and note the information of the "Volume m3" (at the bottom of the screen). Go in the file directory bck_out / EDI / 875 or 850 and open the EDI file of the purchase order. In the last line of the .ord file (line SUM, position 4), you must see the same volume as the one from the Purchase Order Inquiry Phenix option.

CSC9933 - Phenix (report) - Modify a report to compare the vendor promotion ending date with the customer promotion beginning date

Objective of change: Modify the report RAP_VENTE_ACHAT_PAR_PROMOTION to compare the vendor promotion ending date with the customer promotion beginning date. The vendor promotion ending date must now be 30 days or less than the customer promotion beginning date. We consider that the buyer had the time to replenish the quantities in inventory before the promotion begins and the report will no longer display the comment "To claim". How to observe the change: Try to find a vendor promotion with an ending date with a difference of less than 30 days than the customer promotion beginning date. Go in job schedule and select the report RAP_VENTE_ACHAT_PAR_PROMOTION for the customer promotion dates. The report should display the vendor promotion and the comment "To claim" should not be displayed.

FRE4808 - Phenix (report) - Add a page break by route for the report RAP_ACHATS_A_RAMASSER

Objective of change: Add a page break by route for the report RAP_ACHATS_A_RAMASSER. How to observe the change: Go in job schedule and select the report RAP_ACHATS_A_RAMASSER and make sure there is now a page break after each route.

GCL11096 - Phenix - Calculate the average costs when the inventory is zero

Objective of change: Calculate the average costs when the inventory is zero. Be able to update the product's average costs, even if the current inventory is zero. (We must take the cost from the last reception that was higher than zero.) How to observe the change: Select a product in the product's maintenance and take note the "Last Average Cost Calculation" date in the Price Tab. Create a purchase order and at the reception with the gun, receive zero quantity (example: ordered 5cs, received 0cs). Make sure the product has zero in inventory (0). To be sure the inventory is zero, go in Warehouse System / Inquiries / Inventory Inquiry and do a search for the product code you have chosen. If there is still inventory for the selected product, place a customer order for the total quantities in inventory and make sure (after invoiced the customer), that the inventory is now at zero. For your purchase order, complete all operations and invoice the PO in invoice matching (the PO must be closed). Go in job schedule and generate the task GET_AVERAGE_COSTS_PROC. When you will return in the product's maintenance, Price tab, you will notice the date has been updated in the "Last Average Cost Calculation" field. Before, the date was not updated, since the task was not re-calculating the average costs.

MTP628 - Phenix (report) - New report to list the purchases by vendors and by product's group

Objective of change: New report to list the purchases by vendors and by product's group How to observe the change: Go in job schedule and select the new report RAP_ACHATS_FACTURE_PAR_GROUPE. You will be able to precise your search with these 6 parameters: -From date -To date -Product Group: if nothing is in this parameter, all products will be in the report (same thing if you write group 0) -Payable Vendor -Purchase Vendor -Warehouse Code

Sector : 02- Sales

ARM716 - Phenix - Create a credit card charge notion

Objective of change: Create a new type of charge for the credit card payment. This new type will be named "Processing Charges". The idea is to invoice the customer when he paid by credit card. A new menu will be created to specify the percentage to invoice to the customer. This percentage will be calculated on the order's total before taxes. This processing charge will be taxable according to the customer and the province. How to observe the change: Go in General / Maintenances / Warehouses, GL tab and you will notice a new type "Processing Charges" to identify its GL account. Go in Sales / Maintenances / Account Processing Charges Types and create a new processing charge type with a percentage to invoice to a customer that you will link to it. It is possible to assign a customer from this menu or in the customer's maintenance, Invoicing tab. Create customer orders and complete all the steps until invoicing. Also create credits link or not to existing invoices. Go in Sales / Billing/ Invoice Inquiries and you will notice in the header a new field named "Process. Charges ($)". As soon as a customer order is invoiced and the customer should be invoice for processing charges, an amount will be displayed in this field. Some reports / procedure have been adjusted to include the processing charges: 1-GEN_COKE_STATS_PROC 2-EXTRACT_GOUVERNEMENT 3-RAP_MODIF_MAINT_CUSTOMER 4-RAP_BALANCEMENT_A_RECEVOIR 5-RAP_BALANCEMENT_COMM_COMPTOIR 6-SOMMAIRE DES VENTES 7-RAP_DES_VENTES_PAR_VENDEUR 8-RAP_PROFIT_SIX_WEEKS 9-RAP_TENDANCE_VENTE 10-File EDI .inv, crd and .sta (in newout / EDI) 11-File ACC_AR (in newout / financial) 12-Customer invoice (personalized ARM0237) 13-Customer invoice for the credit note (personalized ARM0237) 14-RAP_ROUTE_CLIENT (personalized ARM0237) 15-RAP_SOMMAIRE_ROUTE_2 (personalized ARM0237) 16-RAP_SOMMAIRE_ROUTE (personalized ARM0237) 17-RAP_ANALYSE_PROFIT 18-RAP_VALIDATIONS_DES_REPORTS Note: The processing charges are not calculated for the orders from the Cash and Carry.

BEA411 - Phenix - Do not invoice delivery freight for the orders done with RBH products. FOR BEAUDRY-CADRIN ONLY Objective of change: Do not invoice delivery freight for the orders done with RBH products. How to observe the change: N/A

BEA473 - Phenix - Warn a user when an EDI order is rejected because the customer has no DUNS number

Objective of change: Warn a user when an EDI order is rejected because the customer has no DUNS number. We need an option to indicate an email address to warn us that a customer order is rejected because of a non-existing DUNS number. For now, since the system don't find a customer linked to the order, neither the customer or we are receiving the warning. How to observe the change: Go in Utilities / Projects and Parameters Definition. A new project named EDI for the context 875 has been added. You will be able to configure the email address to who the reject report of the EDI orders must be send. Take a customer order file and, in Phenix / customer maintenance, delete his DUNS number. Put the customer order file in NEWIN/EDI directory and generate the procedure EXTRACT_ORDERS_PROC. You must receive the reject email (if you indicate your email address!) Possible reasons to receive this email: • The customer code is empty • The customer code doesn’t match any customer • The DUNS number is empty • The DUNS number doesn’t match any customer • The same DUNS number is matching with more than one customer

BEA475 - Phenix - Forbid to modify the customer reference number in Telemarketing if the order is a KC order (RBH) FOR BEAUDRY-CADRIN ONLY Objective of change: Forbid to modify the customer reference number in Telemarketing if the order is a KC order (RBH) How to observe the change: N/A

BEA480 - Phenix- Optimize the Partnership program report

FOR BEAUDRY-CADRIN ONLY Objective of change: Optimize the Partnership program report How to observe the change: N/A

BEA481 - Phenix - Display the credit authorizations for the regular order in the report RAP_CREDIT_AUTHORIZATION (perso CVI0078)

FOR BEAUDRY-CADRIN ONLY Objective of change: Display the credit authorizations for the regular order in the report RAP_CREDIT_AUTHORIZATION (perso CVI0078). How to observe the change: N/A

BEA496 - Phenix (report) - Do not display the tobacco promotion in the customer personalized catalogue (Perso CVI0078) FOR BEAUDRY-CADRIN ONLY Objective of change: Do not display the tobacco promotion in the customer personalized catalogue (Perso CVI0078) How to observe the change: N/A

BEA499 - Phenix - Send only the last account statement when the customer has many account statements not sent yet. FOR THOSE WHO ARE USING THE ACCOUNT STATEMENTS. Objective of change: Send only the last account statement when the customer has many account statements not sent yet. How to observe the change: If a customer has more than one account statement without any "Communication date" in Sales / Billing / Account Statement Inquiry, only the last account statement must be send and a communication date for all previous account statements must be updated. The idea is to not send many account statements to the same customer (by email, by fax or by route). The customer will have all updated information’s on the last account statement. To test, you must find a customer that has many account statements not sent (without communication date). Make sure the report of account statement will be send to you by email (EMA type, in the customer's maintenance, EDI/Communication tab, and/or by ROU type). Regenerate the customer's account statement, either by generate one of his routes or go in job schedule and generate the procedure GEN_ACCOUNT_STATEMENT_PROC. You must receive only the last account statement. This account statement AND the previous account statements must now have a communication date.

BER10041 - Phenix - Calculate the prebooks profitability on the current day costs in Telemarketing menu

Objective of change: When you pick quantities for a prebook in Telemarketing (fix or declining method), the average costs must be calculated based on the System parameters switches instead of considering the average costs calculated at the time of the prebook reservation (including vendor's agreements, after sale volume rebates, etc..) This modification will allow to get the right calculated profit in Telemarketing menu (to avoid the thought there is a loss of money) and also allow to calculate correctly the transport additional fees. How to observe the change: Select a customer that has left quantities for some prebooks (the prebook reservation alreadry done). Go in Telemarketing menu and pick some quantities for the prebook found. Validate the product's profit % and the different information’s affecting the cost in the optional footing options of Telemarketing (after sale volume rebate, vendor agreement, cost 4, etc...). Then, add (create) a vendor agreement and/or an after-sale volume rebates grid and return in Telemarketing menu. Validate one more time the product's profit % and the different information’s affecting the cost in the optional footing options of Telemarketing (after sale volume rebate, vendor agreement, cost 4, etc...). You must notice the product profit % has been recalculated. Before, the calculation of the average cost was done with the amount of the prebook reservation and not with the current prices. To help you, you can generate the report of the questionable orders "RAP_COMM_DOUTEUSES". Before, the prebooks were on this report since the costs were not calculated with the current price, it was calculated with the price at the moment of the prebook reservation.

BER10140 - Phenix (report) - Standardize the extensions calculation of some sales reports and include the mail products

Objective of change: Standardize the extensions calculation of some sales reports and include the mail products. Report's list of the reports that must have the exact same totals (for the same period): -RAP_VENTE_PAR_GROUPE_MAJEUR -RAP_VENTE_GROUPE_MAJEUR_TELEVENDEUR -RAP_SOMMAIRE_DES_VENDEURS -RAP_SOMMAIRE_DES_VENDEURS_DETAIL -RAP_ANALYSE_PROFIT How to observe the change: Generate the 5 reports for the same period and the same parameters and make sure the totals are the same.

BER10192 - Phenix - Modifications in the report RAP_LIGNE_COMM_PAR_TELEVENDEUR

Objective of change: Modifications in the report RAP_LIGNE_COMM_PAR_TELEVENDEUR. 1-Add new parameters as: From Telemaketer, To Telemarketer, From User, To User, Display (Telemarketer or User) and Cost Used. 2-In the report, add new colums to display the sales, the costs, the profit ($) and the profit (%). 3-In the report, display on one separate line the total of PCI orders. How to observe the change: This report is used to display the total orders no matter if it is invoiced or not. Go in Job schedule and select the report RAP_LIGNE_COMM_PAR_TELEVENDEUR. You will notice the 6 new parameters. Note 1: The telemarketer is the one who has entered the order. To find this information, go in Sales / Orders / Customer orders inquiry, in the bottom section "Additional Information" and note the telemarketer that is display in this section. (The telemarketer will be empty if it is a PCI order.) Note 2: The user is also the one who has entered the order. To find this information, go in Sales / Orders / Customer orders inquiry, in the bottom section "Additional Information" and note the user that is display in this section. Note 3: When you chose a specific warehouse in the report's parameter "Warehouse Code", the user or the telemarketer of this warehouse will be displayed, and this, even if the customer is from another warehouse. The warehouse code validation is on the user or the telemarketer and not on the customer.

BER10205 - Phenix (report) - In the report RAP_COMPTEURS_TELEVENTE_A_PAYER, assign the credits to the salesman that took the order

Objective of change: In the report RAP_COMPTEURS_TELEVENTE_A_PAYER, assign the credits to the salesman that took the order instead of the person that created the credit. Also, add a column that will display the initial amount of the counter (total counter amount before it is split between the salesman, the telemarketer and the administrator). How to observe the change: Go in job schedule and generate the report RAP_COMPTEURS_TELEVENTE_A_PAYER. See that the new column has been added and find a credit note to see that the salesman is the one assigned to the invoice instead of the person that created the credit note.

BER10254 - Phenix (report) - Modify the sales reports to calculate the cost on a forced sale at zero dollars. Objective of change: Modify the sales reports to calculate the cost on a forced sale at zero dollars. In Telemarketing, when you create a real freegood with the button "Freegood", a charge is done to the vendor and the selling prices as the cost prices become at zero. However, when in Telemarketing the user forces the selling price at zero to simulate a freegood, there will be no charge created for the vendor and the product's cost still exists. So, the sales reports must calculate the product's cost even if the selling price is at 0.00$ (for force selling price). How to observe the change: The five reports that you need to test are: 1-RAP_VENTE_GROUPE_MAJEUR_TELEVENDEUR 2-RAP_VENTE_PAR_GROUPE_MAJEUR 3-RAP_SOMMAIRE_DES_VENDEURS_DETAIL 4-RAP_SOMMAIRE_DES_VENDEURS 5-RAP_ANALYSE_PROFIT Go in Telemarketing and create an order for a product with a real freegood by clicking on the Freegood button. Then, order in the same order another product. However, you will have to modify the price of the second product at zero $. Complete all operations until the order is invoiced. Go in job schedule to generate the procedure PROCESS_INVOICES_AND_UPDATE_CUSTOMER_PROFILES so the statistics table will be updates. Then, always in job schedule, generate the 5 reports to see that the "Selling price" column will be at zero $ for the two products, but for the "Cost price" column, the first product will be at zero $ and the second product will have its cost displayed.

BER10275 - Phenix (report) - Creation of a new report for the invoiced delivery charges versus the proposed charges in Telemarketing

Objective of change: Creation of a new report for the invoiced delivery charges versus the proposed charges in Telemarketing. How to observe the change: Go in job schedule and select the new procedure GEN_CHARGE_PROPOSED_DELIV_PROC. You must configure the bottom section to receive the report by email. The parameters "Year" and "Period" are mandatory. The report displays in a .csv file the list of IN invoices for the selected period.

BER10282 - Phenix (report) - If the period is not defined, consider the current period in the two profit 's reports. FOR CDA ONLY. Objective of change: If the period is not defined, consider the current period in the two profit 's reports. The 2 reports modified are: -RAP_VENTE_PROFIT_VENDEUR (personalized BER0191) -RAP_VENTE_PROFIT_TELEVENDEUR (personalized BER0191) How to observe the change: N/A

BER10301 - Phenix (report) - Indicates the product is a transit product on the report BOTTIN_PERSONNALISE (perso CORPO). FOR CDA ONLY Objective of change: Indicates the product is a transit product on the report BOTTIN_PERSONNALISE (perso CORPO). How to observe the change: N/A

BER10305 - Investigation of sales and profits(Drilldown) - Add PRICE SOURCE types in the legend

Objective of change: Add PRICE SOURCE types in the legend How to observe the change: Go in Phenix / Sales / Billing / Sales and Profits Inquiry. In the titles, when you pass the cursor on the title "Source", the legend must be displayed. Here are the new sources that have been added: DG: Discount by Grid DP: Personalized Discount FP: Floor Price QP: Personalized Quotation QN: Quotation by NAC QT: Quotation by Type

BER10315 - Phenix - Add the possibility to send by FTP the Direct Link statistics file

Objective of change: Add the possibility to send by FTP the Direct Link statistics file. How to observe the change: To be able to send the Direct Link file by FTP, the FTP account must be configured in Phenix / General / Job Section / FTP Accounts. The FTP account code must be DL (for Direct Link). Go in Job Schedule to generate the procedure GEN_DIRECT_LINK_STATS_PROC. Make sure that in the bottom section, you have defined a recipient with the sending type "FTP Account" and that you will identify "DL" in the FTP Account field. When the procedure will be activated, the Direct Link file will be place in the FTP Account directory and in the Newout/Listing directory (as before). Also, if you have defined your email address in the bottom section, you will still receive the Direct Link file by email (as before).

BER9897 - Phenix - Exhibition Reception section: validate if the customer is deleted and change the position of the catalog printing with the badges printing

Objective of change: Exhibition Reception section: validate if the customer is deleted and change the position of the catalog printing with the badges printing. How to observe the change: Go in Phenix / Exhibition / Reception and select a customer that is deleted. A message in red will be displayed to inform the user. Also, the 2 printing buttons have been interchanged for having the badges printing button first and the catalog printing at the bottom of the screen.

BER9899 - PCI - Modify the message that is explaining the cut off time has exceeded. Objective of change: Modify the message that is explaining the cut off time has exceeded. (For a cutoff time due to a transit or of "just in time" product). How to observe the change: In the PCI, we need to change the message when the cut off time has exceeded for: "Cut off time exceeded (12h30) " (HH:MM) When the cut off time has not passed, it will be as before, the time count down will be displayed: "Cut off time in 00hour 7minutes ..."

BER9926 - Phenix (report) - Standardize the Account statement screen and the report RAP_VISITES

Objective of change: Standardize the Account statement screen and the report RAP_VISITES How to observe the change: Go in Phenix / Sales / Billing / Account Statements Inquiry and make sure the screen works as before. Go in Job schedule and select the report RAP_VISITES. Generate the report in English to make sure all the traduction is ok.

CLC1808 - Phenix (report) - Add the promo type for the 2 consumption reports (CL_PR and PR_CL)

Objective of change: Add the promo type for the 2 consumption reports (CL_PR and PR_CL) How to observe the change: Go in job schedule and generate the 2 reports for which a new parameter has been added (PROMOTION TYPE). RAP_CONSOMMATION_PR_CL RAP_CONSOMMATION_CL_PR

CLC1819 - Phenix (report) - New sales report with the sales in $ and the quantities for current year comparing with last year

Objective of change: New sales report with the sales in $ and the quantities for current year comparing with last year. (This report is based on the consumption reports). How to observe the change: Go in job schedule and select the new report named RAP_CONSOMMATION_COMPARATIF. Note: it is preferable to specify a restricted customer interval, since the report can be long to generate for all customers at the same time.

CSC9597 - StatsNAC - National Accounts - Create a csv file for the data of all reports in Stats NAC

FOR COLABOR BOUCHERVILLE ONLY Objective of change: Create a csv file for the data of all reports in Stats NAC How to observe the change: N/A

CSC9837 - Global Portal Services - Accept the hyphen in the manufacturer product's code in the 810 forms and change a title. Objective of change: In the Colabor PGS, rename the field for the Minimum selling price to Floor price. How to observe the change: Connect in the Colabor PGS and see that instead of "Minimum selling price", it is "Floor price".

CSC9841 - Phenix - Add a total invoice surcharge of 2% for some customers that are buying at Boucherville

This modification is mostly for Colabor Boucherville, but it can affect your business too. Objective of change: Add a total invoice surcharge of 2% for some customers that are buying at Boucherville. To do so, a discount grid will be created and a total invoice surcharge of 2% will be define in the appropriate field (Total Invoice Surcharge (%)). A new button "Exceptions" has been added to be able to exclude a promotion type from the invoice surcharge (so with this button, you will be able to exempt the products for the Colabor Exhibition). To manage all the new charges, a new GL account has been created to separate the Total invoice surcharge from the Minimum order charge (0.40$ for purchase of less than 5 cases) How to observe the change: Go in General / Maintenances / Warehouses, in the GL tab and you will notice a new field has been added to specify a GL account for the "Charges on Minimum Quantity". So, to specify a GL account for the Total invoice surcharge, you must put it in the field "Administration" and for the freight of 0.40$, you must put it in the field "Charges on Minimum Quantity". Go in Products / Cost / Rebate / Per grid and see that the new button "Exceptions" has been added beside the Total Invoice Surcharge field. Create a new discount for the group 0 and link a customer to this grid. Create orders for this customer in Telemarketing and invoice the transactions. Go in the Invoice Inquiry to see that the 2% and the 0.40$ has been calculated correctly (2% on the total before taxes and 0.40$ per case for products ordered with less than 5 cases). Create credits for existing invoices and credits for products that are not related to an invoice (always for the same customer that is linked to the discount grid of 2%). The amounts of surcharge will not be credited for the products not linked to an invoice. However, the debit note will always invoice the total invoice surcharge. Different reports have been modified to separate the Charges on minimum quantities (0.40$) from the Total invoice surcharge (2%). 1-The file .INV for EDI (in newout / EDI) 2-The file .CRD for EDI (in newout /EDI) 3-The file ACC_AR.dat (in newout / financial) 4-The report RAP_TENDANCE_VENTE 5-The invoice IN personalized Colabor (CSC0000) 6-The invoice CN credit personalized Colabor (CSC0000) 7-The report RAP_VALIDATION_DES_REPORTS The PGS has also been modified to display the Handling feed (2%) and the Minimum quantity charge (0.40$) on the invoice from the section Web EDI. Attention: The Minimum order charges (0.40$) has change of field in the table. Note: For those who are using the Cash and Carry, the Total invoice surcharge are now calculated in the total. Note 2: For the customers (other than Colabor Boucherville), when you will be using Invoice matching for the Colabor vendor, the freight of 2% and 0.40$ will be merged in the field "Taxable Charges".

CSC9867 - Phenix - Modify the report RAP_TRANS_DOUTEUSES to add a parameter to select the customer and remove the maximum of one week for the date interval. Objective of change: Modify the report RAP_TRANS_DOUTEUSES to add a parameter to select the customer and remove the maximum of one week for the date interval. How to observe the change: Go in job schedule and select the report to view the questionable transactions (RAP_TRANS_DOUTEUSES). A new parameter to select the customer has been added. Also, it is now possible to generate the report for more than one week of interval (for a period and even for a year). However, if you generate the report for more than one period, you must select a customer. If not, the report's time generation will be very long.

FRE4775 - Phenix (report) - The report RAP_PROD_SOUM_DORMANTS is too long to generate. Objective of change: The report RAP_PROD_SOUM_DORMANTS is too long to generate. How to observe the change: Go in job schedule and generate the report.

FRE4812 - Phenix - Add customers begin and end dates for the statistics files (QUASEP)

FOR CUSTOMERS THAT SEND STATISTICS FILES TO QUASEP. Objective of change: Add customers begin and end dates for the statistics files (QUASEP). How to observe the change: Go in Products / Statistics / File Types, in the bottom section "Statistic File Customers". Two new columns have been added to define the customer's beginning and ending date. These parameters are used only for QUASEP code. If the dates are empty, that means the customer is active and should be include in the report. If a beginning and ending date is define, only customer's statistics between these dates will be in the report.

GCL10982 - Phenix - Cleaning in Phenix for some fields that are not used anymore. Objective of change: Cleaning in Phenix for some fields that are not used anymore. How to observe the change: The cleaning must be invisible for the user since the fields that have been removed were fields not used since a long time. To do the tests, make sure that the following actions work as before: 1-Go in Sales / Orders / Customer Orders Entry (Telemarketing) and create a regular order. Go in Sales / Orders / Customer Orders Inquiry and make sure your order is there. Go in Sales / Picking / Generate Picklists and generate the picklist for this order. Go in Sales / Picking /Picklists Inquiry to see that the picklist has been created for your order. 2-Go in job schedule and generate the procedure CUSTOMER_INVOICING_PROC so the customer's invoice will be created. Go in Sales / Billing / Invoice Inquiry and make sure your invoice has been created for your order. Click on the REPORT button to display your invoice. 3-For those that are using the Cash and Carry option, you must create a new order in the Cash and Carry and invoice the customer. Go then in Sales / Billing / Invoice Inquiry and make sure your invoice has been created for your order. Click on the REPORT button to display your invoice. 4-For those that are using Counter orders, make all the steps of # 1 and #2 (instead of creating a regular order, create a counter order). 5-For those that using the BF invoice, make sure the invoice is displayed on the screen when you go in Sales / Billing / Invoice Inquiry and click on the REPORT's button. Also try to find a vendor that is asking for the Shipping note instead of the invoice to see that if you click on the REPORT's button, the report RAP_BON_DE_LIVRAISON_BF is displayed. 6-Go in job schedule and generate the report RAP_FEUILLE_DE_CHARGEMENT. Just make sure the report is displayed with the right information’s. 7-Go in Sales / Billing / Invoice Cancellation and make sure you can cancel any invoice as before. 8-Go in Purchases / Billing / Vendor Invoice Inquiry and make sure the screen is working as before. Click on the REPORT's button to display some invoices. 9-Go in Purchases / Indirect Shipment and select an order with the ALL button. Generate the indirect order. Go in Sales / Orders / Customer Orders Inquiry to see that the customer order has been created. Go in Purchases / Orders / Invoice Matching to invoice (close) the vendor's indirect order. Go in job schedule and generate the procedure CUSTOMER_INVOICING_PROC so the customer's invoice will be created and go in Sales / Billing / Invoice Inquiry to see it. 10-Go in Purchases / Maintenances / Vendors, in the Warehouse tab. A field in the bottom section has been removed (this field was named "Extra (%)" and was at the right of the Cut-off time column). This option has also been removed from the blue pop-up of additional search. In the bottom section, in the Warehouse tab of the vendor's maintenance, add, modify and delete some information from the bottom section (Product Groups Properties) and save between each modification. Go then in job schedule and generate the report RAP_MODIF_MAINT_VENDOR to see the trace of your modifications. 11-For Beaudry-Cadrin only: Select an RBH "NI" type file and make sure the order and the invoice has been created in your system.

GCL11084 - Phenix - Add on the questionable transactions report a note to display this invoice is coming from an Indirect delivery

Objective of change: Add on the questionable transactions report a note to display this invoice is coming from an Indirect delivery. Two new parameters have been added in the report RAP_TRANS_DOUTEUSES. (DISPLAY INDIRECT DELIVERY and PO COST USED). How to observe the change: Generate the report in job schedule and notice the 2 new parameters. Note: the parameter PO COST USED is linked to the indirect delivery invoice.

GCL11106 - Phenix - Standardization of the taxes in Telemarketing menu. Objective of change: How to observe the change: Go in Telemarketing and make sure that the taxable products are identified in the column "TX" (P for provincial, F for federal or T for provincial + federal). You also need to make sure the taxe calculation is correct in Telemarketing screen. For those who has a multi-warehouse environment: a correction has been made when you are a user from the warehouse 99 and you decide to order for a customer from another warehouse (#91 for example). When you order for the customer from the warehouse #91, the warehouse code is highlighted in orange. If you modified the customer number for a customer from your warehouse (#99), the color was staying there. Now, the orange will be gone is the customer is from the same warehouse as the connected user.

USG1282 - PCI - Get a list of the prebooks and be able to order from this list. Objective of change: Get a list of the prebooks and be able to order from this list. How to observe the change: A new list has been added in the PCI to display the products with left quantities of prebooks. You must connect to PCI application and begin an order for a customer that has left quantities of prebooks with declining method. You must click on the dropdown list that begins with "Your profile" and select the new option "Prebook". Notes: -Only active and pre-deleted products will be displayed. -Only prebooks that have the prebook delivery date equal or inferior than the one chosen for the PCI order will be displayed. -Even the products that are not in the customer profile will be displayed in the prebooks' list, . -The sort and the search functions will work as for the other filter (lists).

USG1310 - PCI - Be able to search by UPC code on non-sellable format. Objective of change: Be able to search by UPC code on non-sellable format. How to observe the change: Go in the PCI application and everywhere you can do a search, make a search of a UPC code that is on a non-sellable format in Phenix. The product should be found if the product is available for the customer (either in his profile or in the general product's catalogue). Example: A wine case is sellable by case and a UPC code is on the case and a different code is on the unit. The customer should be able to find the product even if he is searching by the UPC code from the bottle of wine (unit).

USG1326 - PCI - To personalize the catalogue, the retailer must be able to remove products from his profile with the PCI application

Objective of change: To personalize the catalogue, the retailer must be able to remove products from his profile with the PCI application. How to observe the change: Go in the PCI for one of your customers. When an order begins in the PCI application, it is the products list of the customer profile that is displayed. If this customer would like to remove a product from his profile, he can now click on the product code (in blue) and then click on the button "More details". At the right top of the screen, there is the button "Back". A new icon will be displayed beside if the product is included in the customer profile. If the customer clicks on it, he will be able to remove the product from his profile. Note: If a telemarketer is in Phenix Telemarketing option, in the same customer profile and this telemarketer is ordering the same product as the customer is trying to remove from his profile from the PCI, the customer will get a message in the PCI to indicate that the record could not be saved (the product will not be removed from his profile in this case). Note 2: A vendor representative will not be able to use this function.

USG1340 - Phenix - Remove all existing Phenix tables, Phenix Packages concerning the old PCI Objective of change: Remove all existing Phenix tables, Phenix Packages concerning the old PCI to stop the maintenance of tables that are not useful anymore. How to observe the change: 1- Go in the new PCI application and make sure it works as before. Nothing should have change. (Create an order, create a new user, generate reports). 2- Go in Phenix / Utilities / Project and Parameters Definition. (Only the project of the new PCI (PCI5) should stay). The projects named « PCI_FTP » / « PCI.GICNET.CA » / « PCI2.GICNET.CA » have been removed.

Sector : 03- Statistics

ARM715 - Phenix - Create a new statistics file for Compass group

FOR OH ARMSTRONG ONLY Objective of change: Create a new statistics file for Compass group How to observe the change: In Phenix / Products / Statistics / File Types, create a new file type code with COMP for Compass. Here are the fields that are mandatory for the generation of these statistics: 1-Enter the Warehouse (or warehouses) code (s) that needs to be sent to Compass. The field "Identification" must be filled to be displayed as "Distributor Center ID" for Compass. 2-In the section "Customers Groups of the Statistic file": you must create 2 groups "Y or 1" for yes, this customer is a Compass Canada customer or "N or 0" if no, this customer isn't a Compass Canada customer. 3-In the section "Statistic File Customers": you must define all the customer you want to include in the statistic file for Compass. You also must define the Group ("Y or 1" or "N or 0") for each customer. When the configuration of the COMP file type is completed, go in job schedule to generate the new procedure GEN_COMPASS_STATS_PROC. The statistics file will be place in the directory NEWOUT/LISTING. If you generate the procedure more than one time in a day, the file will be override and only the last generation will be kept.

ARM735 - Phenix - Change the field delimiter to use the character | instead of the coma (COMPASS)

FOR OH ARMSTRONG ONLY Objective of change: Change the field delimiter to use the character | instead of the coma (COMPASS) How to observe the change: Generate the procedure to receive the Compass file GEN_COMPASS_STATS_PROC and see the modification.

ARM736 - Phenix - Change the file extension for Compass (from .dat to .txt)

FOR OH ARMSTRONG ONLY Objective of change: Change the file extension for Compass (from .dat to .txt) How to observe the change: Generate the procedure GEN_COMPASS_STATS_PROC and see that the file is now with the extension .txt instead of .dat

BEA497 - Phenix - Inventory file WC_INV, replace the value with 99999 when the inventory has more than 5 digits

FOR BEAUDRY-CADRIN ONLY Objective of change: Inventory file WC_INV, replace the value with 99999 when the inventory has more than 5 digits How to observe the change: N/A

BEA498 - Phenix - Modify some information in the statistic's file for Lesters and Slush Puppies

FOR BEAUDRY-CADRIN ONLY Objective of change: Modify some information in the statistic's file for Lesters and Slush Puppies How to observe the change: N/A

BEA516 - Phenix -Display only active products when we do a search by manufaturer in Products - Statistics - Product Categories

Objective of change: Display only active products when we do a search by manufacturer in Products - Statistics - Product Categories How to observe the change: Go in Products / Statistics / Product Categories, in the section "Additional Criteria’s for Research Among the Details", for the field "Manuf.". When you will do a search by manufacturer with this field, only the Active products will be displayed. Attention: If you do a search by Manufacturer in the top section (just under the description), the system will search all products from this manufacturer whatever they are active or not.

FRE4796 - Phenix - Modifications in the files for Greenbridge (GEN_GREENBRIDGE_STATS_PROC)

FOR AOF ONLY. Objective of change: Modifications in the files for Greenbridge (GEN_GREENBRIDGE_STATS_PROC) How to observe the change: N/A

Sector : 04- Price Structure

BER9910 - Phenix - Define a price floor by product for the sale (to not be able to go under this price) Objective of change: Define a price floor by product for the sale (to not be able to go under this price). If a price is in the field "Price floor" in the product's maintenance, the salesmen and telemarketers should not be able to give a price lower than this price (whether in the quotations, the promotions, during the order taking or all other ways to give (change) a price). Note: The field "Minimum selling price" in the product's maintenance, Format tab, has been renamed "Floor Price". How to observe the change: 1-Go in Products / Maintenance / Products, Format tab and validate that the field "Minimum selling price ($)" has been modified by "Floor Price ($)". It is in this field that you will be able to define the floor price for a product - format. 2-Go in Sales / Maintenance / Customers, Price tab and validate that the option "Apply Floor Price" has been added. This option allows to define if the customer should not be invoice under the floor price (checked) or if he can obtain a better price than the floor price (unchecked). 3-The report RAP_MODIF_CUSTOMER has been modified to display the customers that the switch "Apply Floor Price", has been checked or unchecked. 4-To test, select some products and define a floor price in the products maintenance. Select also some customers with the switch "Apply floor price" checked and other customer with the switch unchecked. If you go in Telemarketing option, for a customer that should respect the floor price and you try to modify the price under the floor price, you will get a message forbidding it. Try all options of modifying the price in Telemarketing menu (in the order main screen, in the buttons complete or light profiles, in the buttons of prebooks (Fast prebook order / Reservation pbk / Pbk without promo / Show). 5-A new price source has been created when the price routine is equal to the floor price. The price source will be then FP in Telemarketing menu, in the Customers invoice inquiry or in the option "Sales and Profits Inquiry". In the Price inquiry menu, the price source "Floor price" will also be displayed and can be combined with a promotion code if that is the case. 6-In the Cash and Carry, the floor price is also validated if the customer should respect it. 7-In the customer's maintenance, there is an option in the Invoicing tab allowing to "Recalculate Selling Price when Invoicing". If the switch is checked for a customer and in the order, the customer had a selling price or 20.00$ for example, and then, a floor price has been added for the product (example, a floor price of 22.00$), the customer will be invoiced with the floor price of 22.00$. Note: during the customer invoicing, if the price routine was already returning a floor price, the recalculation will not be done with the new price (if the price source is FP, we do not recalculate). 8-For the prebooks orders that the reservations have been done to X price and a floor price is added after, the prebook prices will stay even if the prebook price is under the floor price since the idea of the prebooks is to reserve quantities with a price that will not change! Also, a prebook price cannot be override. A button "Changes" exists in the Prebooks Maintenance / Inquiry and allows to override the prebook price. It will be impossible to go under the floor price with this option (a security has been added for this button so it won't be everybody that can change the prebooks prices! 9-In the Price Change Entry, the field Minimum Selling Price has been renamed by Floor Price ($). When a floor price exists for a product and you want to create a new price change, a calculation of the new floor price is calculated with the prorata as follows: ((New selling price / Old selling price) * by the old floor price). Same thing if the price change is coming from the Colabor price synchronization. For the Colabor price synchronization, even if Colabor puts a floor price from his side, the synchronization will not transmit it to you. Note: A new report has been created to give you the product's list that have changed of prices at Colabor (by the synchro) and that has a floor price in your system. That way, you will be able to decide if you need to change the price or not (RAP_CHANGEMENTS_DE_PRIX_MIN). 10-For the order files that come from outside (MSI, PCI, etc...): if the confirmed price in the file is lower than the floor price, we will recalculate with the good price. 11-Different reports have been modified to consider the new price source (FP- floor price). Here is the report's list: BOTTIN_PERSONNALISE, RAP_COMM_DOUTEUSES, RAP_TRANS_DOUTEUSES, RAP_TRANS_DOUTEUSES_PAR_PROD, RAP_SOMMAIRE_DES_VENDEURS_DETAIL, RAP_COMMANDE_SANS_PROMOTIONS(TEMP), RAP_SOMMAIRE_DES_GROUPES_CLIENTS_DETAIL

CSC9805 - Phenix - Add a message if the counter's vendor is not a vendor associated to the product (during a customer promotion creation). Objective of change: Add a message if the counter's vendor is not a vendor associated to the product (during a customer promotion creation). How to observe the change: Go in Products / Price / Promotions / Customers and create a new promotion for a product. If you have to claim an amount to a vendor in the "Counter" section, a new message will be displayed if you do not enter a vendor code associated to the product. For example, if for a Nestle product, you confirm a vendor code like Olymel, the message "This product (xxx) is not sellable by the vendor (yyy). Do you really want this vendor as counter?" will be displayed. You will have to answer yes or no to continue. If you answer no, the vendor code that you entered will be highlighted so you will be able to enter another one right away.

CSC9927 - Phenix - Add a button in the customers promotions entry to allow the copy of a promotion to another one

Objective of change: Add a button in the customers promotions entry to allow the copy of a promotion to another one. With this button in addition of being able to copy 2 promotions, you will be able to add an administration rate percentage on the prebooks (a little bit like the customers discounts). How to observe the change: The promotions copy will be possible if the two promotion's types have the same following configurations (checked or unchecked): -Guaranteed Price -Special Order Products -Show Promotion -Guaranteed Allocation for Prebook -Cumulative Promotion -Excluded Cumulative Promotions When you will click on the "Promotion copy with admin", you will have to define ALL the fields. If you do not wish to put an administration rate %, you must put zero (0). The beginning and end date must be the same promotion's dates as the original promo to copy. If you add an administration rate %, the calculation percentage method will be done according to the configuration in System Parameters, Sales tab (Purchase (divided) or Sales (multiplied). Once the promotion copied, you can press the keys Ctrl + Shift + F2 to see the price that has been calculated. The field "Prebook Price ($)" will be the price invoiced to the customer. You can press the same keys in the screen "Customers Promotions Inquiry".

Sector : 05- Finances

BEA464 - Phenix (report) - Modify the drop reject report to be more precise for a message that validates the retailer 's active dates. FOR BEAUDRY-CADRIN ONLY Objective of change: Modify the drop reject report to be more precise for a message that validates the retailer 's active dates. How to observe the change: N/A

BEA483 - Phenix - Allow to check the check box 'already printed' for the credit invoices when they are created in Credit/debit Entry

Objective of change: Allow to check the check box 'already printed' for the credit invoices when they are created in Credit/debit Entry. (Either it is created in Credit/debit Entry, Invoice Cancellation or the Credits button in the Cash and Carry menu). How to observe the change: When you enter a credit or a debit without have a merchandise return to do, you will get a new option in the blue pop-up that is asking if you wish to display the credit note or not on your screen. This option is named "display and update credit note" and prevent the printing of the document in the next customer route (the check box "already printed" will be checked automatically). To test, you must create credit notes in Sales / Billing / Credit - Debit Entry, in Sales / Billing / Invoice Cancellation and with the CREDITS button from the Cash and carry menu (Sales / Orders / Cash and Carry orders entry.

BEA524 - Phenix (report) - Vendor charge send 2 times the same copy (refund request) for the RMA and for the refund request. Objective of change: Vendor charge send 2 times the same copy (refund request) for the RMA and for the refund request. There must be a difference between the two sending copies to not get the impression we receive 2 times the same report. How to observe the change: Go in the vendor's maintenance and in the Purchase Detail / Performance, check the options "Authorization Required for Ven. Returns" and "Authorization Required for Ven. Billing". With these options, you will be able to receive the 2 necessary emails to see the difference of the modification. In addition to these two options, go in the EDI/Communication tab of the vendor's maintenance and add your email address for the transaction type CN. Create a charge request in Purchases / Billing / Vendor Billing for the vendor you have selected. For the Billing type, select a type that need a picking. When you will click on the button "Generate vendor billings", you will receive by email the refund request, but the report will be named RAP_RMA_POUR_CHARGES. Before, you would receive the same report, but with the same title of the refund request report. Go in Purchases / Billing / Vendor Returns Approval to approve the RMA and click on GENERATE. The picking request will be created and you will be able to go in WMS or Phenix to pick the product. The mission will be invoiced with the procedure VENDOR_RETURNS_PC_PROC. Then, when the invoice will be created, you will receive by email the report RAP_DEMANDE_DE_CHARGES with the same report's title (refund request), just as before.

BER10142 - Phenix - Validate the vendor sales agreements to include the credits even if the ending date agreement is ended

Objective of change: Validate the vendor sales agreements to include the credits even if the ending date agreement is ended. How to observe the change: 1-I have a vendor agreement in Sales / Agreements / Vendors for the product X, that the switch credit is checked with the customer #14 linked to this vendor agreement. Note: to make the test easier, this agreement has no beginning date and no ending date at this moment. 2-I create an order for the customer #14 for the product X and I invoice the customer. 3-I return in the vendor sales agreement and I add a beginning and ending date, but with an ending date in the past (like the agreement is finished). 4-I go in the Invoice cancellation to create a credit for the same invoice that I just have created. 5-Generate the procedure INVOICE_AGREEMENT_PROC to invoice the vendor. The 2 invoices (invoice and credit) must be included for the vendor.

BER10175 - Phenix - Separate the invoices sent to Accpac from the invoices sent by email FOR CDA ONLY Objective of change: Separate the invoices sent to Accpac from the invoices sent by email for the transports invoices. How to observe the change: Before, when a transport invoice needed to be sent by email and the email could not be sent because of a server problem for example, the transport invoice was not transferred in ACCPAC. Now, even if a transport invoice cannot be sent by email, the invoice will be transfer in ACCPAC, since the two actions have been separated.

BER10185 - Phenix (report) - Modify the procedure that invoices the Telemarketer counters to keep the orders not yet invoiced during the period

Objective of change: Modify the procedure that invoices the Telemarketer counters to keep the orders not yet invoiced during the period. How to observe the change: Create a customer order for a product linked to a Telemarketing counter and complete the picking of the order, but do not invoice the customer. Generate the procedure that invoices the telemarketing counters (TELEMARK_COUNTER_INVOICE_PROC) and make sure no VT invoices have been created. Generate the procedure to invoice the customer CUSTOMER_INVOICING_PROC and then re-generate the procedure that invoices the telemarketing counter. The VT invoice must be created. (Note: make sure to change the "Last Date" of invoicing in Sales / Counters / Counters Types the second time you will generate the procedure TELEMARK_COUNTER_INVOICE_PROC with a date in the past. If you do not change the Last Date, you will have to wait the day after to complete the test!).

BER10191 - Phenix (report) - Modification of the report Rap_Rentabilite_Route_Detail Objective of change: Modification of the report RAP_RENTABILITE_ROUTE_DETAIL How to observe the change: Before, the report was not balancing for the profit ($ et %) information. Now it is balancing.

BER10252 - Phenix - Add a function key in the customer's invoice inquiry to be able to modify the invoiced customer

Objective of change: Add a function key in the customer's invoice inquiry to be able to modify the invoiced customer How to observe the change: In Utilities / Security / Security, search the menu option that is named CUSTOMER_INVOICE_INQUIRY. If for the security group desired (example Finance), the column U (for update) is checked, you will be able to modify the "invoiced customer" in Sales / Billing / Invoice Inquiry. To modify this value, you must press the function keys Shift + Ctrl + F3 and a pop-up will open to select the right invoiced customer.

BER10255 - Phenix (report) - The freegood claim should not convert the kilo price when the ordered format is unit Objective of change: The freegood claim should not convert the kilo price when the ordered format is unit. How to observe the change: Go in Telemarketing and for a product invoiced by weight (Product's definition = D), order for the case format and the unit format (find a product that is sellable on 2 different formats). For the 2 product's lines you ordered, click on the button FREEGOOD so the product will be invoice to the customer. Go in job schedule and generate the procedure FREEGOOD_INVOICING_PROC to invoice the vendor. Go in Purchase / Billing / Vendor Invoice Inquiry and see that the claim has been created and the calculation is as follows: Weight for the case line x kilo price (example: 2 cases for a total of 11.5kg x 11.99$/kg = 137.89$ Weight for the unit line x kilo price (example: 2 units for a total of 4.3kg x11.99$/kg = 51.56$ (Before, the kilo price of 11.99$/kg was divided by the number of unit in a case for the unit format line)

BER10283 - Phenix - Calculate the volume rebate on the debit line for the credit types with 'Same format' and 'Same product' Objective of change: Calculate the volume rebate on the debit line for the credit types with 'Same format' and 'Same product'. Before, when the customer was assigned to a volume rebate grid and a credit/debit was done for the same product and same format, the volume rebate was calculated only on the credit amount and the debit line was ignored. With this modification, the debit line volume rebate is also calculated. How to observe the change: Select a customer and take note his off-invoice volume rebate grid (Sales / Maintenances / Customers (Price tab). Example, a customer has a volume rebate of 0.5% if he purchases 500.00$ and more. Go in Sales / Billing / Invoice Inquiry and find an invoice for this customer and make sure that the off-invoice volume rebate has been calculated (that there is an amount). Go in Sales / Billing / Credit-Debit Entry and create a credit with credit-debit type. Attention, the credit-debit type must be linked to an invoice and should be for the same product, same format type. Example of the calculation: 1-Initial customer invoice = 1000.00$, so a volume rebate amount of 5.00$ was applied. 2- For the credit/debit, I credit 2 cases of ketchup (12x500ml) at 25.00$ each and I debit the 2 same cases (ketchup 12x500ml), but at 24.00$. 3-The volume rebate on the credit line will be at -0.25$ 4-The volume rebate on the debit line will be at 0.24$ (Before, nothing was calculated on the debit line) 5-The volume rebate is now of -0.01$ for the credit note

BER10296 - Phenix (report) - Creation of a new report of credit validation

Objective of change: Creation of a new report of credit validation. This report will display the person who approved the customer's credit and for which order. How to observe the change: Go in job schedule et select the new report named "RAP_VALIDATE_CREDIT_ORDERS". The parameters "From date", "To date", allow to define the date interval when a user approved a credit. The parameters "From user", "To user", allow to define the user interval that approved the credit. Note: To have results in the report, you must have approved credits in Phenix / Sales / Billing / Credit Validation.

BER10304 - Phenix (report) - Display the number of products (SKU) in the inventory report RAP_SOMMAIRE_INVENTAIRE

Objective of change: Display the number of products (SKU) in the inventory report RAP_SOMMAIRE_INVENTAIRE. How to observe the change: Go in job schedule and generate the report RAP_SOMMAIRE_INVENTAIRE. You will notice a new column that displays the total number of products by vendor.

BER10317 - Phenix - Add the product's original amount on the CN invoice (before the service charges) FOR CDA ONLY (the report has been modified only for the personalization CORPO) Objective of change: Add the product's original amount on the CN invoice (before the service charges) How to observe the change: N/A

BER9863 - Phenix - New report that displays in which account go all vendor charges (account payable or account recevable)

Objective of change: New report that displays in which account go all vendor charges (account payable or account recevable). To be able to create this report, it was necessary to standardize the GL account rules (AR/AP). How to observe the change: 1-Go in job schedule and generate the new report RAP_GL_POUR_FOURNISSEUR for the vendor you want. In this report, you will see for each charge type, in which account it will goes (To pay or To Receive). At the beginning of the report, you will also see if the vendor you chose is the payable vendor for another vendor and you will see in which GL division this vendor is. 2-The following charges type have been standardized for the GL account rules. In resume, we consider the GL account of the manufacturer, but we consider the account (To pay or To receive) of the payable vendor. This modification has been done for the following invoice types: VR (Count and recount), VC/VI (vendor charge/invoice matching charge), BF/CF (billed for), VG (free goods), VS (incentive sales), VA (vendor agreement), OA (Trade program RBH), VT (Telemarketing counter, Power Colabor), RC (reception charge) et VM (miscellaneous charge). 3- Some screens in Phenix have been modified to display the payable vendor -Products / Price / Rebate / Discount Types -Sales / Agreements / Vendors Note for the vendor agreements: we also add an option "according to GL Division". Do now you can specify for a vendor if the account is To be paid, To be received or According to GL Division (configured in Utilities / Maintenances / GL Divisions. 4-In Utilities / Maintenances / GL Divisions / Rebates tab: we add a possibility to configure if the "Vendor agreement" charge should be in the Payable or Receivable account and we add the charge "Miscellaneous charges" to be able to configure if the charge should be in the Payable or Receivable account. 5-In Purchases / Maintenances / Vendors / Purchase detail / Performance tab, we add the possibility to chose the account for the reception charges between the Payable or Receivable account. (This option indicates if the account to use will be Payable or Receivable if the current vendor is charged for receipt charges).

CSC9870 - Phenix - Modification in the remittance table (RRT) for the DR (drop) invoices with retailers. FOR COLABOR BOUCHERVILLE ONLY Objective of change: Modification in the remittance table (RRT) for the DR (drop) invoices with retailers. How to observe the change: N/A

FRE4800 - Phenix - Do not be able to delete an erroneous ASN completely if a part of the lines have already been transferred. Objective of change: Do not be able to delete an erroneous ASN completely if a part of the lines have already been transferred. To do so, we had a new information to indicate if the ASN has been partially transferred. This way, if you try to delete an ASN partially transferred, the system will forbid you. How to observe the change: Go in Purchases / Orders / Erroneous Receipt Notice Maintenance and for an ASN with many products in error, "Validate" and "Transferred" a product without error (or correct the product so it will be without error). Exit and re-enter in the screen to see that the check box "Partially Transferred" has been checked and try to delete this ASN. You must be blocked and you won't be able to delete it.

GCL11012 - Phenix - Create a new procedure to print the customer's invoices in batch. Objective of change: Create a new procedure to print the customer's invoices in batch. (BATCH_PRINT_CUS_INVOICES_PROC). We need a new procedure to send in one email all the invoices for a customer for a date interval. How to observe the change: Go in job schedule and select the new procedure BATCH_PRINT_CUS_INVOICES_PROC. You must define a date interval and a customer. You can also fill the bottom section to indicate the person to send the invoices (email address). The invoice types that will be send by email through this procedure are: IN, CN, DR, TR, TC, PT and CM.

GCL11105 - Phenix - Add the validation if the vendor already exists in ACCPAC customers when a new vendor is created in Phenix. Objective of change: Add the validation if the vendor already exists in ACCPAC customers when a new vendor is created in Phenix. How to observe the change: In Phenix / Purchases / Maintenances / Vendors, when a new vendor is created, a validation already exists to validate if the vendor code already exists in ACCPAC at the vendor level (APVEN) and a message is displayed to know if you want to continue or not with this code. The same validation has been added for the customer level (ARCUS). So, if the vendor code you are trying to create already exists in ACCPAC / ARCUS, the same message will be displayed but will be specify in parenthesis if it is for the vendor (APVEN) or the customer (ARCUS). To test, try to create a new vendor with a vendor code that already exist in APVEN and ARCUS.

GCL11156 - Phenix - Do not be able to delete a PO if the purchase order is waiting to be received, but already invoiced

Objective of change: Do not be able to delete a PO if the purchase order is waiting to be received, but already invoiced. How to observe the change: Go in Purchases / Orders / Receipt Notice Inquiry-Correction and find a purchase order that has "Open" status and "System" source. For this purchase order (PO), create a file that represents the EDI invoice for this PO and place the file .inv in the directory NEWin/EDI (for help, as the TI department). Generate the procedure EXTRACT_880_810_856_JOB_PROC. If the invoice contains errors and can be found in Purchases / Orders / Erroneous Invoice Maintenance, do all the corrections so the invoice will be transfered. Then, go in Purchases / Orders / Direct Purchase Order and try to delete the PO you have selected. You should get the message "Impossible to delete this purchase order since its invoice already exists in the system".

GCL11163 - Phenix - Allow to use the 'Shift + Tab' in the field Payable Vendor in the invoice generation (Invoice matching)

Objective of change: Allow to use the 'Shift + Tab' in the field Payable Vendor in the invoice generation (Invoice matching). In an environment with more than one warehouse, we must be able to get back on the field "Warehouse" with the keys Shift + tab when we are on search mode. How to observe the change: Go in Purchases / Orders / Invoice Matching and click on the GENERATION button. In search mode, if you are in the field Payable vendor, you will now be able to use the keys Shift + tab to get back on the field Warehouse.

GCL11193 - Phenix - Do not display the closed line by the system (received at zero, but without invoice) in the report RAP_RECUES_NON_FACTUREES

Objective of change: Do not display the closed line by the system (received at zero, but without invoice) in the report RAP_RECUES_NON_FACTUREES. Another correction has been made to not create a new line in the ASN when the EDI invoice sends a quantity (invoiced) at zero. The existing line should be updated, not doubled. How to observe the change: Go in Purchases / Orders / Receipt Notice Inquiry-Correction and search for a line that has zero for quantity received and the order line status is "paid" and the line is "closed". The section "Invoice's Information" should also be empty. Once this line is found, go in job schedule to generate the report RAP_RECUES_NON_FACTUREES. This purchase order line should not be displayed in the report. For the second correction, follow the following steps: 1-Select a vendor and make sure the invoices should be sent by EDI, but not the ASN (so it will be an ASN system). To know this, go in vendor's maintenance, in the EDI/Communication tab and make sure the transaction type "Invoice" is there, but not the transaction type "Shipment notification". 2-Create a purchase order for the selected vendor. 3-Go in Purchases / Orders / Receipt Notice Inquiry-Correction to see that your ASN system is really there with all the products you have ordered. 4-Ask the EDI responsible to send you an . inv file for your purchase order invoice (arrange the file so it will pass through your system, but you must change one line to put a quantity at zero). Place the file in Newin /EDI and go in job schedule to generate the procedure EXTRACT_880_810_856_JOB_PROC. If the file contains errors, you will find the erroneous invoice in Purchases / Orders / Erroneous Invoice Maintenance and you must correct the errors to be able to transfer the transaction. If you do not have any errors or if you have corrected the errors and transferred it, go in Purchases / Orders / Receipt Notice Inquiry-Correction to see that the line with the quantity at zero is still there with the invoice number entered. Before, the same product was displayed twice for the same line (was doubled), one with the invoice number entered and the other empty.

GCL11219 - Phenix - Send a reject email to the user even if the file is empty (for 2 procedures)

Objective of change: Send a reject email to the user even if the file is empty (for 2 procedures). -EXTRACT_VB_INFO_PROC (importation of a file to create automatically the vendor charges) -PURCHASE_GROUP_IMPORT_PROC (importation of price changes for purchasing groups) How to observe the change: Go in job schedule and generate the 2 procedures. Do not forget to configure your email address in the bottom section so you will receive the reject file. Either if the reject file is empty or not, you must receive the reject file by email.

Sector : 06- Warehouse

BEA366 - WMS Phenix - Allowing the creation of replenishments by targeting the Interco only and be able to replenish by Interco in WMS

Objective of change: Allowing the creation of replenishments by targeting the Interco only and be able to replenish by Interco in WMS. How to observe the change: For the customers with a multi-warehouse environment: 1-Go in Phenix / Warehouse system / Replenishments / Generate Replenishments and see that the screen has been modified. A new option has been added to generate replenishments based on Interco. You must also test the 2 other options (based on Min/Max and based on Sales) to make sure everything is working as before. 2-To generate a replenishment based on Interco, you must create an Interco with Transfer Entry menu for a product that has quantities in one or more overstock location and in a picking location. It is important to create a Transfer entry with a quantity higher that the quantity left in the picking location! Than, the Interco transfer must be validated with the Transfer Console (it is at this moment the replenishment based on Interco will be visible in the replenishment generation). Note: The Interco from CAPS are not considered in the replenishment based on Interco, since the locations used are always linked to a dock. 3-Go back in System Warehouse / Replenishments / Generate Replenishments and select the new option based on Interco and click on Generate. Your product must be displayed and you can now activate the replenishment. 4-Go in Cancel Replenishments. You will see the replenishment you just activate and you will notice the replenishment's type will be: "Interco". By default, the other existing replenishments already in the system will be tagged with the "Min/Max" type. 5-Test the procedure that generates automatically replenishments (GENERATE_AND_ACTIVATE_REPLENISHMENT_PROC), since the parameter "BASED ON SALES", has been modified for "REPLENISH. BASED ON". This will allow selecting between SAL (sales), MIN (Min/Max) or INT (Interco). Before, you were able to chose between YES or NO for the parameter "Based on Sales". If the procedure already existing was having the parameter at YES, a default value for SAL has been made. 6-Go in WMS (gun) to test the new replenishment option "by Interco". You also need to test all other options of replenishments to make sure everything is working as before (Without route, by route/zone, by min-max/zone, by zone, by product and by dock) 7-Go in Inventory Movements Inquiry to notice that the replenishment type is displayed with the "Replenishment by Interco" type (same thing in Products/Locations Inquiry and Product's Movement Inquiry) 8-The 2 following reports have been modified to include the replenishments by Interco: (RAP_PRODUCT_MOVEMENTS, RAP_REAPPROVISIONNEMENT_EXCESSIF) 9-Note: a new option has been created in System Parameters, WMS tab, to prioritize the picking location when an Interco is generated. This option is named "Prioritize Picking Locations for Interco". By default, this option will be unchecked so the inventory check order will be: perfect match with the overstock qty, picking location, overstock location. If the option is checked, the inventory check order will be: picking location, overstock location, perfect match with the overstock qty. For the customers with only one warehouse: 1-Go in Phenix / Warehouse system / Replenishments / Generate Replenishments and see that the screen has been modified. You must test the replenishments (based on Min/Max and based on Sales) to make sure everything is working as before and activate a replenishment. 2-Go in Cancel Replenishments. You will see the replenishment you just activate and you will notice a new column displaying the replenishment's type. By default, the other existing replenishments already in the system will be tagged with the "Min/Max" type. 3-Test the procedure that generates automatically replenishments (GENERATE_AND_ACTIVATE_REPLENISHMENT_PROC), since the parameter "BASED ON SALES", has been modified for "REPLENISH. BASED ON". This will allow selecting between SAL (sales), MIN (Min/Max) or INT (Interco). Before, you were able to chose between YES or NO for the parameter "Based on Sales". If the procedure already existing was having the parameter at YES, a default value for SAL has been made. 4-Go in WMS (gun) to test all options of replenishments to make sure everything is working as before (Without route, by route/zone, by min-max/zone, by zone, by product and by dock). 5-Go in Inventory Movements Inquiry to notice that the replenishment type is displayed with the right one (example: Replenishment by products"). (Same thing in Products/Locations Inquiry and Product's Movement Inquiry) 6-The 2 following reports have been modified to include the replenishments by Interco, so you just need to generate them to make sure they are as before: (RAP_PRODUCT_MOVEMENTS, RAP_REAPPROVISIONNEMENT_EXCESSIF 7-Note: a new option has been created in System Parameters, WMS tab, to prioritize the picking location when an Interco is generated. This option is named "Prioritize Picking Locations for Interco". By default, this option will be unchecked and will not be used by you, since you have only one warehouse.

BEA413 - Phenix - Modify the pallet section on the customer route sheet (perso CVI0078)

FOR BEAUDRY-CADRIN ONLY Objective of change: Modify the pallet section on the customer route sheet (perso CVI0078). How to observe the change: N/A

BER10005 - Intersection(Roadnet) - Manage the service hours from Phenix to Roadnet

FOR THE CUSTOMERS USING ROADNET APPLICATION ONLY. IMPORTANT: THE CHECK BOX "ROADNET INTERFACE" MUST BE CHECKED. Objective of change: Manage the service hours from Phenix to Roadnet How to observe the change: Because of this modification, we had to make a modification on the PM orders. This should be invisible for you. So, you just need to create a customer order (PM) in Phenix / Telemarketing with today's date. The picking generation must be done automatically. For the service hours: You must go in the customer's maintenance, in Expedition tab and add/modify/delete some service hours so the modification will be tag and sent to Roadnet with the help of Intersection application. Go then in Intersection application for the service hours to be updated in Roadnet and go in Roadnet to validate the customers were really updated (in Location / Time Window Overrides). Another modification has been done to send the message that can be write in the customer order in Telemarketing menu and in the transport transaction entry to Roadnet. This message will be displayed in Roadnet, in the Special Instructions column, for the customer order.

BER10006 - Intersection(Roadnet) - Send the order details (SKU) to Roadnet

FOR THE CUSTOMERS USING ROADNET APPLICATION ONLY. IMPORTANT: THE CHECK BOX "ROADNET INTERFACE" MUST BE CHECKED. Objective of change: Send the order details (SKU) to Roadnet. How to observe the change: Go in Phenix and create a customer order with more than one products. Go then in Intersection to export the orders in Roadnet. The UPC codes (products) are now sent Roadnet. If the product has no UPC code configured, it will be the manufacturer product code that will be sent to Roadnet. Note: When a UPC code or manufacturer code is already in the same order (example, a product ordered 2 times on 2 separate lines), a sum is calculated for the quantities (so in Roadnet, the same SKU won't be displayed 2 times). Note 2: In Roadnet, the Case total column will not necessary be the same for the order and for the order details. In the order total case, it is the total of formats checked for the "Pick to count" switch and consider the volume calculation. In the order details total case, it is the total elements that are displayed, whatever the format should be counted or not. Note 3: The order SKUs are not deleted when they are deleted in Phenix / Telemarketing. The quantities can be updated, but Roadnet do not allow to erase a complete line. So, if a product is remove from an order and re-send to Roadnet with the same session, the line will still be displayed. However, to avoid this situation, you can create a new session, so you will get all the modifications. Note 4: A modification has been made for the transport transactions sent to Roadnet to also send the weight that was entered in the Transport transaction entry. Before, the weight information was not sent to Roadnet, so it was always at zero in Roadnet.

BER10008 - Intersection(Roadnet) - Display the order's exportation and importation date with Roadnet application (Intersection)

FOR THE CUSTOMER USING ROADNET (INTERSECTION) ONLY Objective of change: Display the order's exportation and importation date with Roadnet application (Intersection). How to observe the change: 1-Create a customer order in Phenix by going in the Telemarketing menu. 2-Go in Intersection and send your order from Phenix to Roadnet. 3-Go in Phenix / Sales / Orders / Customer orders inquiry and search for your order. At the right top of the screen, a new field has been added to display the exportation date from Phenix to Roadnet. By double-clicking on the date, you will get a pop-up to also see the time of the exportation. 4-Go in Roadnet to place your order on a route. 5-Go in Intersection, in the Route menu to be able to import the route in Phenix. 6-Go in Phenix / Sales / Orders / Customer orders inquiry and search for your order. At the right top of the screen, a new field has been added to display the importation date from Roadnet to Phenix. By double-clicking on the date, you will get a pop-up to also see the time of the importation. You also need to test an order of Indirect delivery (in Phenix / Purchases / Indirect Deliveries to make sure everything is working as before in Phenix. Another correction has been made to be able to transform a regular order into a counter order in Telemarketing, even if there is a transit product in the order. Before, there was an error in this situation. Now, if you want to transform a regular order with transit products into a counter order, the order will be divided in two. One counter with the products for the same warehouse and another one that will stay a regular order for the transit product.

BER10033 - Phenix - Interco to close when the authorized quantity is at 0 for a purchase order from CAPS

FOR THE CUSTOMERS WITH MULTI-WAREHOUSE ONLY Objective of change: Interco to close when the authorized quantity is at 0 for a purchase order from CAPS. In the Interco Transfer Entry, it is impossible to delete an Interco if the authorized quantity is at zero (if the Interco is from a CAPS purchase order). Also, these Interco cannot be generated with the Interco Transfers Console and so are kept for nothing! How to observe the change: Go in CAPS multi-warehouse to order a product for the source warehouse and give some quantities to another warehouse (destination). Example, order 15 cases of product X for the source warehouse, with 7 cases for the warehouse 91 (destination warehouse). Go then in WMS (gun), and complete the product's reception. Attention, when you will begin the reception, select the source warehouse at first and even if WMS will indicate to receive 8 cases, confirm the reception of 15 cases and nothing for the destination warehouse. Close the reception. Since all the quantity was confirmed for the source warehouse, the Interco transfers will now have an authorized quantity at zero since the PO reception is now closed. Go in Phenix / Transfer Interco / Transfers Entry and search for your PO number to make sure that the authorized quantity for the destination warehouse is at zero. In this screen, it is now possible to delete these lines with authorized quantities at zero. Also try to delete an Interco transfer linked to a purchase order (CAPS) with an authorized quantity more than zero. You should not be able to delete this line. Same thing for an Interco transfer linked to a PO and nothing yet confirmed for the authorized quantity. You should not be able to delete this line.

BER10086 - WMS Phenix - Optimize the WMS operations for any inventory movements. Objective of change: Optimize the WMS operations for any inventory movements. How to observe the change: To test, you must go in all options mentioned above in WMS (gun) and complete each of them until the end. Also, before and after completing an inventory movement, go in Phenix, Inventory Inquiry and Inventory Movements Inquiry to make sure every quantities are good. -Product movement (screen 2-1) -Product movement with a product that the format needs to be broken (from case to unit) (screen 2-1) -Movement by Dedicated location (screen 2-4) -Replenishment (screen 3-5) -Replenishment with a product that the format needs to be broken (from case to unit) (screen 3-5) -Replenishment with a product transformation (screen 3-5 with a transformation product) -Product transformation (screen 2-5) -Inventory transfer in the Supervision menu (and then complete the movement) (screen 9-3) -Replenishment transfer in the Supervision menu(and then complete the replenishment) (screen 9-5)

BER10098 - Phenix - Do not create new replenishments for a product when a user is in the process of completing one. Objective of change: When a PLANNED replenishment is created, (and the option "To allow already existing replenishments to be increased" is checked), and a replenishment for this product / Warehouse is already existing, a new replenishment should not be created. (Anyway, it will be created later with the next replenishment generation, if the initial replenishment did not put enough quantity in the location.) How to observe the change: Go in Phenix / Warehouse System / Replenishments / Cancel Replenishments and select a product with an existing Planned replenishment. Create a customer order in Telemarketing for the same product with tomorrow's date to cause a second replenishment. To check if you configure correctly your test, you must go in Warehouse System / Replenishments / Generate Replenishments and check the option "Based on Sales" and then click on Generate button. The product you have selected previously must be there. Do not activate this replenishment, you must exit the screen without saving. Go in WMS (gun) and begin the product's replenishment. However, you should not complete it, you just have to make sure the replenishment status is "In Use", in Warehouse System / Replenishments / Cancel Replenishments. Go in Generate replenishments in Phenix and check the option "Based on Sales" and also the option "To allow already existing replenishments to be increased", and generate the replenishment. No new replenishment must be created for the product you have selected previously since its status is "In use". The same thing is happening when the task GENERATE_AND_ACTIVATE_REPLENISHMENT_PROC is generated at the same time. If the user exits the replenishment in WMS, the replenishment will be created the next time the task will be generated or if you generate it manually in the Generate Replenishment Phenix menu.

BER10108 - Intersection(Roadnet) - Be able to synchronize the routes from Phenix into Roadnet

FOR THE CUSTOMERS USING ROADNET APPLICATION ONLY. IMPORTANT: THE CHECK BOX "ROADNET INTERFACE" MUST BE CHECKED. Objective of change: Be able to synchronize the routes from Phenix into Roadnet. This will allow to maintain only one data base instead of two. Following are the fields that will now be updated in Roadnet each time you will export the customer orders from Phenix to Roadnet: 1- Start time 2- Route code (only the regular active routes) 3- Route day (Monday, Tuesday, Wednesday, Thursday, Friday, Saturnday or Sunday) 4- The delivery warehouse linked to the route 5- Route description (the base description) 6- The truck code linked to the route 7- The driver linked to the truck 8- The route stops (each position that was define for the route in the customer's maintenance or routes) How to observe the change: Go in Intersection application to export orders from Phenix to Roadnet. You will notice that the pop-up with the confirmation of what have been exported has been modified. All the fields mentionned above will now be exported to Roadnet. To test, you should create a new route to realize the difference. Note: if the driver and the truck do not exist in Roadnet, the fields will be empty and this, even if you have data in Phenix for these fields. You must create the driver and the truck in Roadnet for matching with Phenix.

BER10135 - Phenix (report) - Display the UPC in the bar code for the report RAP_ETIQUETTE_COMM_SPEC (perso BER0191) FOR CDA ONLY Objective of change: Display the UPC in the bar code for the report RAP_ETIQUETTE_COMM_SPEC (perso BER0191) How to observe the change: N/A

BER10136 - Phenix (report) - Modify the report rap_etiquette_identification to add a parameter for the UPC code. Objective of change: Modify the report RAP_ETIQUETTE_IDENTIFICATION to add a parameter to display the UPC code on the label. Remove the Warehouse code parameter. How to observe the change: Go in job schedule and select the report RAP_ETIQUETTE_IDENTIFICATION. You will notice the parameter "Warehouse code" has been removed and a new parameter named "UPC Code" has been added. The bar code that is displayed on the label is the one of the UPC code (if the parameter UPC code has been filled and the product code parameter is empty). If the product code is specified in the "Product Code" parameter, it will be the bar code of the product code that will be displayed (the product code has priority). If the UPC code specified is corresponding to 2 different products for the same format, the report will be empty.

BER10152 - Intersection(Roadnet) - Transfer the salesman code from Phenix in Roadnet

Objective of change: Transfer the salesman code from Phenix in Roadnet How to observe the change: In Phenix, customer's maintenance, when there is a modification on the customer (business name, address, service hours, salesman code), the "salesman code" will be sent to Roadnet. The salesman code will be place in Roadnet, under the locations (field Alias #6).

BER10194 - Phenix - Validate the volume of the order transfered from Phenix to Roadnet

FOR CUSTOMERS USING ROADNET ONLY Objective of change: Validate the volume of the order transfered from Phenix to Roadnet How to observe the change: Create a regular customer order with many products. Note the volume of the products you have included in your order. Go in Intersection to send the order to Roadnet. Go in Roadnet to validate if the volume is corresponding to the volume you have calculated.

BER10202 - Phenix - Documents maintenance

Objective of change: When we go in Sales / Maintenances / Documents and a territory interval is saved, it is not displayed correctly. It is displayed, for exampe : from territory 13, to territory 13 even if we saved from territory 13 to territory 15. How to observe the change: Go in Sales / Maintenances / Documents and create a new document to be sent by Territory interval. Define an interval of Territories and saved. Even if you get out of the screen and come back, the territory interval must be displayed with the good territories codes. (Before, if we entered from territory 13 to 15 and we get out of the screen, it was displayed 13 to 13. Now, it is display Territory 13 to 15).

BER10278 - Intersection(Roadnet) - Keep some configurations in the standard routes in Roadnet

Objective of change: Keep some configurations in the standard routes in Roadnet. When the standard routes were updated by Phenix (Intersection), some information’s were lost and should not. A modification has been made to update only the necessary fields without changing other configurations done in Roadnet. How to observe the change: Chose a route in Phenix and go see how it is configured in Roadnet, in the Standard routes section. The following fields are fields that will no longer be lost when the routes are updated: 1- Pre-route Time 2- Post-route Time 3- Driver #2 code 4- The check box for the helper 5- Origin and destination ID 6- Equipment’s (the truck assigned to the route can be updated, but all other equipment’s defined manually will stay there (wont be deleted). 7- Regular Time / Max Time 8- Route color 9- Breaks and layover of the drivers Do a print screen and see how the route was configured before in Roadnet. If all fields are empty or at zero, fill it with different information’s before doing your print screen. Go in Phenix and make some modification in the route like change the start time, the truck code, etc. and go in Intersection to update Roadnet. Return in Roadnet to see that the modifications were updated in Roadnet, and the other information’s are not lost. **MODIFICATIONS DONE ON NOVEMBER 14 2017 AS FOR THE CUSTOMER'S NEEDS. To help you test these modifications, here are the resume: 1- The drivers will not be updated (from Phenix to Roadnet) 2- The trucks will not be updated (from Phenix to Roadnet) 3- The Original "DPT" will not be updated (from Phenix to Roadnet) Note: When a new route is created (or changed from the Inactive status to the Active), the 3 values will be sent and updated in Roadnet. Please take note that if you De-activate a route, it will be deleted in Roadnet... So, if you re-activate the same route, it will be consider as a new route and the 3 values (Drivers, Trucks and Origin DPT) will be updated in Roadnet with the Phenix data. Note 2: These 3 values are configurable, so if you decide one day to update all these values from Phenix, you will be able, but you will have to ask the IT department!

BER10309 - Phenix (report) - Add a sort on the positions (desc) for the pallet labels (when the product is ordered 2 times by 2 customers)

FOR THE CUSTOMER USING THE ENVIRONMENT WITH PALLET CONSOLIDATION (AND USING THE REPORT RAP_ETIQUETTE_PALETTE). Objective of change: Add a sort on the positions (desc) for the pallet labels (when the product is ordered 2 times by 2 customers) How to observe the change : Generate the report of the pallet label (RAP_ETIQUETTE_PALETTE ) for a pallet that contains the same products ordered by more than one customer. The higher customer route position must be the first one.

BER10312 - Phenix (report) - Add the transport customer on the report RAP_PREP_BON_TRANSPORT

Objective of change: Add the transport customer on the report RAP_PREP_BON_TRANSPORT. How to observe the change: Go in job schedule and generate the report RAP_PREP_BON_TRANSPORT. You will notice the transport customer number above the field "Assembler".

CHA2177 - Phenix- Delivery routes generation

Objective of change: In an environment without pallet consolidation and without identifier, we improved the speed to pass from the main screen to the second screen in the option Generate Delivery Routes. How to observe the change: Go generate a delivery route and make sure everything is working normally.

CSC9726 - WMS Phenix - Add an inventory count when a movement to a picking location

Objective of change: Add an inventory count when a movement to a picking location. How to observe the change: For the moment, the modification is just for Colabor Boucherville, but just take note that a new option is in Phenix / Utilities / System Parameters, WMS tab and is named " Validate the inventory if the destination is for picking". This option cannot be use by others for the moment.

CSC9750 - SRV (Voice) - Verify the diction of the location when a user skip an element (Zone/ Alley/ Bay/ Position)

Objective of change: Verify the diction of the location when a user skip an element (Zone/ Alley/ Bay/ Position). How to observe the change: Take the SRV device and connect to begin a picking. The problem before this modification was that the SRV device was telling the complete location instead of telling only the part of the location that was different from the previous location when the user was saying "Skip". Example: Loc of first element = 60280036AA02 Loc of second element = 60280040BB03 Loc of third element = 60280040CC03 The SRV device should say this: Zone 60 , Alley 28, Bay 36, Level alpha, Position 2 If you say "skip", the SRV device should tell the next location that way: Bay 40, Level bravo, Position 2 If you say again "skip", the SRV device should tell the next location that way: Level Charlie, Position 3 In summary, the SRV device must avoid to say the complete location number to shorten the picking time (when the user is picking the product or even when he skip the product).

CSC9817 - Phenix - In the Potential picklists inquiry, the quantity to deliver and suggested is always at zero. FOR COLABOR BOUCHERVILLE ONLY Objective of change: In the Potential picklists inquiry, the quantity to deliver and suggested is always at zero. How to observe the change: Go in the potential picklists inquiry, in the "Selection" button and see that the quantities suggested and to deliver are now displayed.

CSC9838 - WMS Phenix - Allow to continue a PO reception that was paired with other PO's and one of the PO's is already closed! Objective of change: Allow to continue a PO reception that was paired with other PO's and one of the PO's is already closed! This modification is mostly for an environment with identifier (Colabor Boucherville). However, the other customers must also test the reception menu in WMS to make sure everything is working as before. How to observe the change: Connect in WMS. In the "Receiving" menu, select 2 PO (purchase order) to receive. Press *9 to close one of the PO. It is not necessary to received some products or nothing on the PO that will be closed. Close the first PO that will be displayed on the screen and then, without exit or close the second PO, go see the products included in the reception and select one of them. Receive this product and stop at the page that asking for the location confirmation. Close WMS with the X (to simulate a lost connection) and re-connect in WMS. It will not react the same way as Colabor Boucherville, since the inventory will not stay on your user, so the user will not be obliged to complete the reception if the session is lost. The user will be able to select a new reception or to select the same one and complete it. Also test the RMA reception to make sure you are able to receive products with this option as before.

CSC9843 - Phenix (report) - Modification for the report RAP_ECARTS_INVENTAIRE

Objective of change: Modification for the report RAP_ECARTS_INVENTAIRE to display the quantities with whole numbers (instead of 11.00, display 11) (keep the decimals only for products with weight). Also, add a new column to display the location where the count has been done. How to observe the change: Go in Job schedule to generate the report RAP_ECARTS_INVENTAIRE and see the modications.

CSC9864 - Cubi Scan - Do not limit the Cubiscan to the purchase format. Display all 'Multiplied' format (not only the sellable formats). FOR COLABOR BOUCHERVILLE ONLY Objective of change: Do not limit the Cubiscan to the purchase format. Display all 'Multiplied' format (not only the sellable formats). How to observe the change: N/A

FRE4609 - WMS Phenix - Display the format in the message of a WMS screen

Objective of change: In the WMS device, at the end of a replenishment, the system is asking the user if the location inventory is good. However, the format is not specified in the screen and where the locations have many formats of the same product in the location, it is confusing and sometimes, the user is causing an imbalance and creates useless counts. The message will be improved to display the format. How to observe the change: Go in WMS (Gun) and begin a replenishment. For a replenishment that should validate the inventory, the format has been added just under the product's description (screen #35048).

GCL10634 - WMS Phenix - Forbid to place a product in a picking location that comes from a RMA with a different format (smaller format)

Objective of change: Forbid to place a product in a picking location that comes from a RMA with a different format (smaller format). Example, put a box of juice (non-sellable format) in a location that contains case of juice. How to observe the change: Create a RMA for a product that is sellable on the case format (the RMA must be for a unit (or a smaller format than the sellable format). Connect in WMS (gun) and begin to receive the RMA. The proposed location must be a damaged location or a transit location. Try to change the proposed location for the picking location or an overstock location. You should not be able to put the product with a smaller format in a picking or overstock location (only in a damaged of transit location). Create another RMA but for a product with the same format as the sellable format. You must be able to put the product in the picking location or an overstock location.

GCL10670 - WMS Phenix - Standardize the access to the Phenix package for the pallets shipments. FOR AN ENVIRONMENT WITH PALLET CONSOLIDATION ONLY. Objective of change: Standardize the access to the Phenix package for the pallets shipments. How to observe the change: The modification should be invisible for the user. You must test with the WMS (gun) and test the option # 6 (Shipping), #6 (Loading pallet) and all options under. Make sure everything is working as before.

GCL10738 - WMS Phenix - Standardize the security configurations in Phenix + change the security name of the menu INFO BALANCE

Objective of change: Standardize the security configurations in Phenix + change the security name of the menu INFO BALANCE. How to observe the change: Go in Utilities / Security / Security. The securities have been standardized for WMS (gun) as follows: All WMS securities have not the switch "Phenix Form" checked and are checked for the switch "Sub Menu". The options C-R-U-D should not be available. Only the check box "Visible" should be available to check or not for each security group. To test, you must be an "administrator" so you will be able to do all the tests alone. You must uncheck the option "Visible" and connect in WMS (gun) to make sure you cannot see the menu in the gun. If the option "Visible" is checked and you reconnect in WMS, you will now be able to access the option. Try all securities by checking and unchecking the option "Visible".

GCL10850 - WMS Phenix - Code standardization used during an inventory movement

Objective of change: Code standardization used during an inventory movement. All operations touching the inventory in WMS must be tested. How to observe the change: 1-Do product's reception (of a PO) in WMS (gun) and verify that the inventory is added in the location where the reception is completed (Phenix). Make sure the inventory inquiry in Phenix is balancing. 2-Do RMA's reception in WMS and make sure the inventory is added in the location where the reception is completed (Phenix). For the RMA, place the product in the proposed location and do also another test to put the product in a damaged location. 3-Do movements in WMS (try all movement types) and go in Phenix (Inventory movement inquiry) to see that the inventory is correctly moved and that the traces are there. Also go in Inventory inquiry to see that the inventory is balancing. 4-Do replenishments in WMS (try all replenishment types) and go in Phenix (Inventory movement inquiry) to see that the inventory is correctly moved and that the traces are there. Also go in Inventory inquiry to see that the inventory is balancing. 5-Do inventory counts in WMS (try all inventory counts types) and go in Phenix (counts inquiry) to see that the traces are there. Also go in Inventory inquiry to see that the inventory is balancing. 6-Do some picking operations to see that in the inventory inquiry, the quantity decreases and go in the Picking transactions inquiry to see all the details of the picking are ok. For all customers except Colabor Boucherville: Test in the WMS Supervision menu, the 2 options (Inventory transfer and Replenishment transfer). The movement type that will be in Phenix / Inventory Movement Inquiry will be "User change".

GCL10871 - Phenix - Validate the customers coming from Roadnet and that are already on pallets that have been generated. FOR THOSE WHO ARE USING ROADNET APPLICATION ONLY. Objective of change: Add a message in Intersection to advise the user that he cannot separate customers on 2 different routes when the pallet is already generated (waved). Two more modifications have been added in Intersection: 1-Block the double-clicking on the menu "Updates" 2-Improve how a too long cross-dock name is displayed (before, it was displayed on 2 lines, now, it is displayed on one line and it displays a maximum of characters (the rest is replaced by "..."). How to observe the change: -Create 2 orders in Phenix for 2 different customers but for the same delivery date and the same warehouse (and for the same product). -Go in Intersection application and send the orders to Roadnet. In Roadnet, select the 2 customers orders and put it on the same route (on a built route). Save and return the route to Phenix. -Go in Phenix / Sales / Picking / Generate Picklists and generate the picklist for the route of your two customers. -Go in Phenix / Warehouse System / Picking / Mission Console and wave the pallet. If you go in Pick Transactions by Pallet Inquiry, you will see your 2 customers on the same route for the same pallet. -Return in Roadnet and change the built route you just created to separate the 2 customers on 2 different routes. -When you will go in Intersection application to send the routes in Phenix, you will get the new message indicating that the pallet #... is separated between many routes... 1-Test for the double-click: Go in Intersection application and click on the menu Updates. Once the updates are beginning, try to double-click on the menu Updates. No problem should happen. 2-Test for the cross-dock name display: Go in Phenix / General / Maintenances / Cross-docks and modifiy a cross-dock name to have the maximum allowed number of characters. Go then in Intersection application and notice that there will be 3 points at the end of the cross-dock name (it should not be displayed on two lines).

GCL11066 - Phenix - Standardize the number of elements displayed for the products with unique picking weight in the mission console

Objective of change: Standardize the number of elements displayed for the products with unique picking weight in the mission console. How to observe the change: Select a product with Definition Type D (solid purchases, invoiced by weight) and with the check box "Unique Weight Picking" checked in the product's maintenance, Format tab, for the sellable format. Create a customer order for this product with more than 1 for quantity (example: 7 units). A product that should be weighed for the total weight of the 7 units must be considered as 1 element to pick and not 7. Generate the picklist generation for your order so you will be able to see the results in the mission console. In the mission console, a product with unique weight to pick must be considered as 1 element. Same thing when you will go in the pop-up to wave the missions or the pallets. Example: If my customer ordered 7 units of a product with unique weight to pick and 3 cases of chocolate (not weighed product), you must see in the mission console: 4 elements.

GCL11104 - WMS Phenix - Validation added for the number of identifier to create in a location

FOR COLABOR BOUCHERVILLE ONLY Objective of change: Validation added for the number of identifier to create in a location How to observe the change: N/A

GCL11124 - Phenix - Adjust the picking automatic generation to cohabit with the job schedule option. Objective of change: Adjust the picking automatic generation to cohabit with the job schedule option. For the moment, the procedure GENERATE_PICK_MISSION_PROC (PHENIX SGE) is running for all customers each minute. Instead of having this procedure running, we created an automatic picking generation that is running only when a new mission is created. A problem has been caused when the automatic picking generation was running at the same time as other procedures in Job schedule. A correction has been made to cohabit the two functions and no longer overload the database. How to observe the change: You must be sure that the option of automatic picking generation is activated for your system and you must deactivate the old procedure (GENERATE_PICK_MISSION_PROC (PHENIX SGE)). Create many orders in Phenix and go then in Sales / Picking / Generate picklists and generate your missions. When you will go in Warehouse system / Picking / Missions console, you must see your missions and they should be ready to wave. If the missions are not ready yet to wave, click on the Refresh button, since sometimes, there is a little delay of 2-3 seconds! Also create counter orders, PM orders, go through the Credit validation screen and in the Generate special orders picklists. Also try the second wave (when a product is back order and you get a second chance to pick it). Note that if a product needed some replenishment, these lines will be in the section “Waiting Lines” and you will need to complete the replenishment for then see that the mission is automatically generated.

GCL11166 - Phenix - Validate the email sending in the RMA closure treatment (task RMA_FINAL_CHECK_PROC (PHENIX SGE))

Objective of change: In the customer's maintenance, EDI/Communication tab, there is the transaction type CRE with the transmission type ROU, there is an error in the task that invoices the merchandise return, since there is no email address defined. A correction must be done so the task RMA_FINAL_CHECK_PROC (PHENIX SGE) will work without error even if you choose the ROU transmission method. How to observe the change: Go in the customer's maintenance, EDI/Communication tab and add in the bottom section the transaction type CRE and the transmission method ROU. Go in the Credit/Debit Entry option to create a credit with a merchandise return (RMA) and complete the reception of this RMA with the gun (WMS). Generate the task RMA_FINAL_CHECK_PROC (PHENIX SGE) and go then in General / Job Section / Logs Maintenance and make sure there is no error (like Oracle error) and that the invoice (CN) has been created.

GCL9664 - SGE Phenix - In WMS, do not send the parameter (0 or 1) in a Phenix function. Objective of change: This modification is really technical and should be invisible for the user. This modification must be tested by making sure nothing has changed. How to observe the change: -Go in WMS (gun) and complete an inventory count by location empty. Make sure everything is working as before and that nothing has changed.

GCL9774 - Phenix - Correction of the weight displayed for bacon type product (picked form WMS or SRV) in the picking transaction inquiry

Objective of change: Correction of the weight displayed for bacon type product (picked form WMS or SRV) in the picking transaction inquiry. How to observe the change: 1-Find a product with the definition type B (bacon - purchase case - invoiced by weight, not scaled (assumed weight)). If you don't have any product with this definition type in the product's maintenance, Classification tab, do the same tests but with a product with D for definition type (purchasae case - invoiced by weight). Make sure everything is working as before. 2-Create a customer order for the product you found and take WMS (Gun) and pick the product. Make sure that in the Phenix screen "Pick Transaction Inquiry", the weight has been added automatically (since the weight is assumed (known) from the start). For the environments with Pallet consolidation, also validate the "Pick Transactions by Pallet Inquiry" is displaying the product's weight. 3-Create another order with the same product and do all the same tests, but with the SRV device. 4-If you are using one of the 3 following reports, validate it work correctly (rap_cueillette_douteuse, rap_poids_cueilli_a_zero, rap_transit_warehouses).

LAU801 - Lauzon inventory - Add a default location (CHIP) when a new pallet is created with the option Pallet Consolidation

FOR LAUZON ONLY Objective of change: Add a default location (CHIP) when a new pallet is created with the option Pallet Consolidation How to observe the change: N/A

ROL5100 - WMS Phenix - Reception vs stock in an overstock location

Objective of change: When a product reception is done in WMS, we do not see if there is inventory in an overstock location. The system sends us to place products automatically in the picking location, even if the overstock inventory should be emptied first (because of the expiry dates). How to observe the change: Go in WMS (gun) and begin a reception (until the screen #11110 where you must confirm the location). You must validate that: -If the location is damaged or transit type, you must continue -If not, WMS validate if an overstock location exists for the product and if yes, a pop-up asking is there is inventory in overstock. Accept? (Y/N) is displayed... This pop-up has disappeared with another modification from the past. To get this message, make sure you have inventory in overstock for the product and also a picking location.

ROL5108 - WMS Phenix - Allow to credit the weighed products and to complete the reception in WMS

Objective of change: Allow to credit the weighed products and to complete the reception in WMS. In Phenix, we must have a function that will receive the information of the product reception (Product code, #RMA, Qty to receive). The function will validate if an invoice is linked to this RMA. 1-If there is no invoice linked to the RMA: the function will retrieve the differential weight of today and will add the tolerance %. 2-If there is an invoice linked to the RMA and the weight is by ITEM (not by unique weight picking) : the function will retrieve the MAXIMAL weight for this product, without validate the tolerance 3-If there is an invoice linked to the RMA and the weight is "unique weight picking" : the function will extract the fraction to credit and will add the tolerance %. (Example: total weight in the invoice =100kg. The customer wants to return 3 cases from total of 10 cases (so 3/10). There will be 30kg to credit and we will add 20% of tolerance). How to observe the change: 1-RMA not linked to an invoice: Create an RMA in Phenix for a product to weigh. Since the credit is not linked to an invoice, the system will consider the differential weight of the product (example, a RMA of 3 cases of a product with differential weight of 2.5kg). Go in WMS (gun) and complete the RMA reception. The calculation will be done as follows to determine the maximum allowed weight: (Qty received of the RMA in WMS x differential weight of the product format) x (1 + (tolerance /100)) Example: if I receive the 3 cases of the RMA (3x2.5kg) x (1+(20/100)) = 9kg (so you won't be able to exceed 9kg in WMS (in the case that the product is by "unique weight picking". If not, it will be 3kg maximum by case). 2-RMA linked to an invoice with weight by item (not by unique weight picking): Create an RMA in Phenix for a product to weigh and that is linked to an invoice. The system will search for the weight of each cases of the product on the initial customer invoice (example, a RMA of 3 cases linked to an invoice of 3 cases (weight of each case: 1.5kg - 1.6kg - 1.7kg). Go in WMS (gun) and complete the RMA reception. The calculation will be done as follows to determine the maximum allowed weight: (Qty received of the RMA in WMS x maximum weight of the invoice line) Example: if I receive the 3 cases of the RMA (1x1.7kg) (the higher weight of the 3 cases) = 1.7kg / case (so you won't be able to exceed 1.7kg per case in WMS. 3-RMA linked to an invoice with unique weight picking: Create an RMA in Phenix for a product to weigh and that is linked to an invoice. The system will search for the total weight of the initial customer invoice (example, a RMA of 3 cases linked to an invoice of 3 cases (total weight on the invoice = 5kg). Go in WMS (gun) and complete the RMA reception. The calculation will be done as follows to determine the maximum allowed weight: (Qty received of the RMA in WMS x weight of the invoice line (unique weight divide by the number of cases invoiced) x (1 + tolerance /100)). Example: if I receive the 3 cases of the RMA (3x1.667kg) (1.667kg calculation = 5kg/3cs) x (1+(20/100)) = 6.001kg / case (so you won't be able to exceed 6.001kg per case in WMS.

ROL5192 - Phenix - Sales / Maintenance/Documents: the documents are printed even if the date is before today

Objective of change: Sales / Maintenance/Documents: the documents are printed even if the date is before today How to observe the change: In Sales / Maintenance / Documents, if a document was supposed to be print because of the customer group, the route interval or by region and the ending date was in the past, the document was printed anyway. To test, you must create documents to print with an ending date in the past and try all the customers association criteria.

USG1366 - Intersection(Roadnet) - Send one record at a time according to the modification's order to synchronize Roadnet (instead of sending it in batch)

FOR THE CUSTOMERS USING ROADNET ONLY Objective of change: Send one record at a time according to the modification's order to synchronize Roadnet (instead of sending it in batch). Example to understand the modification : 1- if one customer is modified (=record of modification (M) in the table to synchronize) 2- the same customer is deleted (second record (D) to synchronise) 3- once the synchronization is beginning... the delete records (D) are done first and then... the updates (M)... so the customer is not deleted in Roadnet! How to observe the change: Go in Phenix, in the customer's maintenance and create a new customer (it will be easier for the rest of the test!). Go in Intersection application to update Roadnet (Updates menu) and then go in Roadnet to make sure your new customer is the "location" section. Then, go in Phenix, in the customer's maintenance and make a modification in the address for example (and save!). A record to synchronise to Roadnet will be created in the table. Then, delete the customer by clicking the option "Deleted" and save. You now have 2 records to be synchronize in Roadnet. The fisrt one is a modification (M) and the second one is a delete (D). Return in Intersection application to update the 2 records in Roadnet and then go in Roadnet to see that the customer is really deleted. Before, the customer still be in Roadnet, since the synchronization would have erased the customer first and then re-created the customer!

Sector : 07- Administrator

CSC9775 - Phenix - Display the available information’s from the order file (.ord) in the file .ack even if there is an error for one product

Objective of change: Display the available information’s from the order file (.ord) in the file .ack even if there is an error for one product How to observe the change: N/A (only the EDI responsible can test this modification. The file .ack has been created for a specific customer.)

GCL10813 - Phenix - Modify the function that creates a .zip file when the file is really big (so the emails won't be rejected (SPAM))

Objective of change: Modify the function that creates a .zip file when the file is really big (so the emails won't be rejected (SPAM)). Explanation: The chosen method that creates ZIP files when the reports were too big ensured that some SMTP software was rejected the attached files since the files were not contain the "Meta Tag" that identifies the file as an approved .zip file. By using the actual method of "gzip", this constraint does not exist and the email is rejected for some customers. How to observe the change: Go in job schedule and select a report that will have many pages (for example, generate the report RAP_VENTE_PROFIT_VENDEUR for one period, for all salesmen or telemarketers). Identify your email address at the bottom of the screen so you will receive the report by email. If the file is really too big (over 8Mo), the report that will be included in your email will be zipped. In the email, open the report and make sure the file run correctly. Also try a small report (Example, the report PRODUCT_GROUPS). This report should not need to be zipped and you should receive the report by email in a PDF file (not a .ZIP file)

GCL10977 - Phenix - Creation of a new purge for the product's statistics (product_stat_summaries) Objective of change: Creation of a new purge for the product's statistics (product_stat_summaries) in order to delete the old statistics which are used by purchases. How to observe the change: Go in job schedule and select the procedure PURGE_FACTURES. This procedure already exists and was purging different data. We add the product's statistics to purge in this procedure. So, generate the procedure and then go in General / Job Section / Logs Maintenance and do a search in the "Module name" field with "PSS_OPERATION_PACK.PURGE_PROC". You must see the log in the screen and see how many products statistics have been purged.

GCL11088 - Phenix - Allow to finish an Oracle session by the screens of unlock in Phenix

Objective of change: To be able to use the temporary tables in the Picklists generation and in Telemarketing, we must be sure that the Oracle user's session is finish. To avoid locks situation, we must be able to "kill" the Oracle session if a user is in Telemarketing screen and his supervisor decide to liberate this user for a customer. If not, a second user is able to enter in Telemarketing and get problems with the previous session of himself or another user (if the electricity has stopped, for example). How to observe the change: You must be two users to be able to do the tests... 1-Ask one of your colleague to connect in Phenix and enter in the Picklists generation (Sales / Picking / Generate picklists for a customer or for a route). This user must be in the second screen. Since you are the administrator, you, you will go in Utilities / Unlock / General Options and you will unlock your colleague. Your colleague won’t be able to continue when he will click everywhere in the screen and he must get the message "You are no longer connected to the database. Please close this window.". The only way for him to get out of Phenix is to click on the X at the right top of the screen (he will have to re-connect to Phenix). If he re-connects in Phenix, he should be able to do everything he wants (he should not be locked). 2-Do the same test as number 1, but ask your colleague to enter in Sales / Orders / Customer order entry (Telemarketing). After he will select a customer, you, you must go in Utilities / Unlock / Customers and liberate him. Your colleague won’t be able to continue when he will click everywhere in the screen and he must get the message "You are no longer connected to the database. Please close this window.". The only way for him to get out of Phenix is to click on the X at the right top of the screen (he will have to re-connect to Phenix). If he re-connects in Phenix, he should be able to do everything he wants (he should not be locked).

GCL11108 - Phenix - Allow to search by email address in Job Schedule Inquiry

Objective of change: Allow to search by email address in Job Schedule Inquiry. How to observe the change: Go in General / Job Section / Job Schedule Inquiry. In the middle of the screen, it is now possible to search by email address so you will now which task you must modify to correct an email address.

GCL11171 - Phenix - Be able to delete a user in Phenix when all references link to this user are deleted (purged)

Objective of change: Be able to delete a user in Phenix when all references link to this user are deleted (purged). How to observe the change: Only an administrator that is responsible of the users in Phenix can do this test. Go in Utilities / Security / Users and delete users (the older user who are not working anymore for your company!) 5 tables have been modified so their property will be in "cascade" mode. If you have a message that tells you "you cannot delete this user", it should not be one of these 5 reasons: -USER_LOGIN_ATTEMPS (ULA) -USER_PICKING_TIMES (UPT_ -USER_REMOTE_APPLICATIONS (URA) -USER_SESSION_TRANSACTIONS (UST) -USER_SKIPPED_MISSIONS (USM)

USG1357 - Phenix - Add a message in the emails that indicates that they are from a broadcast address. Objective of change: Add a message in the emails that indicates that they are from a broadcast address. The message will indicate that the user should not answer the email. How to observe the change: Go in Job schedule and select whatever report to generate it. Attention, make sure that your email address is in the bottom section so you will be able to receive the email with the report! Open your email to see the following message: Ce courriel a été envoyé depuis une adresse de notification seulement qui ne peut accepter de courriels entrants. Veuillez ne pas répondre à ce message. / Please note: This e-mail was sent from a notification-only address that cannot accept incoming e-mail. Please do not reply to this message. Note: The message is always sent with the 2 languages and can be removed if needed.

Sector : 08- Invisible to users

BER10288 - Phenix - Validate the treatment of MODULE_RESTRICTION_PACK (add some trace) Objective of change: Validate the treatment of MODULE_RESTRICTION_PACK (add some trace) How to observe the change: N/A (cannot be tested (invisible for the user)

CSC9777 - Global Portal Services - (V3) Creation of a new package in Phenix that is necessary for the new PGS. Objective of change: (V3) Creation of a new package in Phenix that is necessary for the new PGS. How to observe the change: N/A