...
No data is uploaded for now. Request only checks whether file contains valid columns.
...
Improvements
Area | Description |
---|---|
Deliveries | Goods receipt from InStore App (RTC-33711) When the user performs a manual goods receipt in the InStore App and receiving items from different suppliers, a separate package and a separate purchase order is created in Procurement for each supplier.
In case of receiving order which has no order despatch advice, after clicking 'Receive goods', but then receiving order through InStore App, remaining values are properly updated. Numbers counted but not submitted in user interface are cleared. After clicking 'Receive goods' again in user interface, remaining values are correct. Order with goods receipt (first done or just started) in user interface but then done in InStore App is possible to set to done. |
Deliveries lines and order lines | Fix: Total price (RTC-33465) Values in side panel updates properly when user navigates through received delivery lines. 'Total price' and other values updates properly after editing delivery lines or order lines. |
Import | Fix: Creating packages when importing order despatch advice (RTC-34078) If the user re-imports order despatch advice line but does not enter a package number, the line will be updated and a new package will not be created. |
Purchase order lines | Fix: 'Line no' column (RTC-33825) Line no column can be moved/resized/sorted for 'cancelled' and 'done' order statuses in the order lines grid. |
...
In addition, the 'SKU' column is visible in all views in the Procurement module where items appear (delivery lines, order lines, goods receipt lines).
Improvements
Area | Description |
---|---|
Deliveries | Received date (RTC-33843) Date of first submitted goods receipt of order or package is properly saved on order and package levels in database. Values are visible in Deliveries grid. Date is not updated after next goods receipts of same package or order. When receiving goods with InStore app, this date is the date when goods receipt was submitted in app.
If the order has status draft, edited, submitted or cancelled, editing and submitting delivery is not possible. The user sees the information: 'Unable to edit/submit delivery. This order is missing information for supplier or items, and order can not change status until this information is updated.' |
Import | Import file with thousands of rows (RTC-34237) StagingImport job does not fail when one imported file contains over 4000 of JSON rows. |
Procurement API | Order number in 'Packages per store' response RTC-33988 "Packages per store" endpoint is extended with orderNumber value on orderLine level, so it is known which order the line from the package belongs to.
API for requesting packages per store does not return packages containing draft, edited, submitted or cancelled orders, but if there are multiple orders in the package and at least one of them has a confirmed status, the package will be returned. |
Purchase order | Dates (RTC-27773) The following dates are visible at order level:
For draft, submitted and edited statuses, only requested time of delivery/delivery date and estimated time of arrival are displayed. For the other statuses, all dates are visible (if defined). Order lines: Export to Excel (RTC-33758) Order lines can be export to Excel by 'Export to Excel' button. 'View purchase orders' permission is needed. User can narrow results by applying filters in columns in the grid. Exported fields are:
|
System | Database compatibility level (RTC-32039) Compatibility level on databases is set to 150. Import of currency rates (RTC-30891) Currency cost and sales rates are imported from Item Service. There is a 'ProcurementServiceJanitor' job in ProcurementServiceintegration package. By default, in runs once every night. If there were any changes in data, it rebuilds index on updated table in database. This results in a reduction of the database size and improves performance. |
...
Import of suppliers from Item Service works properly when GLN is changed between two suppliers within one import.
Improvements
Module | Description |
---|---|
Deliveries | Fix: Order dispatch advice import and purchase order validation (RTC-33997) 'Received' and 'Deviation' is properly displayed after creating or editing quantity of order dispatch advice line. |
Delivery and Purchase order | Pcs unit (RTC-31023) Import of items from ItemService is extended by unit. For 'pcs' unit only whole numbers are allowed when adding and editing order lines or delivery lines. The same for panels in receive goods view and delivery view. |
Internal transfer | Create 'internal transfer' purchase order in user interface (RTC-32775) 'Internal transfer' order type is available when creating new purchase order in user interface. When this type of order is selected, supplier dropdown shows only suppliers which GLN is the same as GLN of any store in Store Management. Any item can be added to this order - supplier-item relation is not needed and its placeholder is not created. Goods receipt for such order works same as for other order types. Purchase order is exported with 'InternalTransfer' order type. GLN of store must be unique. It is not possible to create order for store and supplier with same GLN.
'Internal transfer' order type is available when creating new manual delivery. Same as in purchase orders, when this type of order is selected, supplier dropdown shows only suppliers which GLN is the same as GLN of any store in Store Management. Any item can be added to this delivery - supplier-item relation is not needed and its placeholder is not created. It is not possible to create delivery for store and supplier with same GLN. Additionally, 'Preorder' order type can be selected for manual delivery.
Purchase order and order despatch advice imports from 3rd party are extended with 'internal transfer' order type and 'GLN' as store identifier. |
Purchase order | Status done (RTC-31607) It is possible to change status of the order from confirmed to done after receiving all expected deliveries. The set to done dialogues are different based on whether or not there is a remaining value. If remaining value, user is asked what to do with this value (add as deviation or edit order quantity to match what is delivered). If there is no remaining value, dialogue will show just the summary of the order. If there are active deliveries, dialogue that all deliveries must be processed before order can be set to done is shown. When the 'Set to done' button is clicked, the purchase order is exported. If the order has no deliveries, setting to done is not possible. Importing order despatch advice into an order with a done or cancelled status is blocked.
Supplier order number value is properly saved when confirming order.
Browser focus is on store dropdown when creating purchase order. Focus is on item input while entering purchase order. Supplier discount is always prefilled with '0' in panel for adding item to order. After adding item to order, focus on back to item search input. Only the just created order line row is expanded in order lines grid (other expanded lines are closed without saving changes). After saving changes in order line in submitted order, status 'Edited' and 'Resubmit' button are properly displayed. Order line note is wrapped when too long in read-only expanded order line (on statuses confirmed, cancelled, done).
Order lines that were created via manual delivery are visible in the user interface. Delivery date (RTC-30947) It is possible to set past delivery date when creating or editing order or order line. |
System | External store number (RTC-31281) StagingMerger in ProcurementServiceIntegration works properly when store has external number according to new rules (unique in company, not unique globally). StoreIdentifier used in imports has no longer externalStoreNo field. Field StoreNo is now required. New stores created through import have externalStoreNo set to null. |
...
It is possible to generate PDF file by 'print order' button with order confirmation when status of order is submitted. The file contains the following information: purchase order number, order date, customer number, vendor, to which shop the order is sent ('Ship to' field), e-mail address ('Billing'), order note, GTIN (Item number), item name ('Description'), quantity of product ('Qty'), total price for each item and price for whole order.
Improvements
Module | Description |
---|---|
Deliveries | Receive goods with deviation (RTC-28803) Side panel in delivery view shows quantity of sent items and input for received quantity (max 3 decimals). After save, deviation is calculated, grid is updated and order despatch advice line has status 'Counted'. Focus is automatically set to the received field in the panel after opening panel or changing selected delivery row, so value can be entered directly. Keyboard can be used to undo changes (Ctrl+Z), save (Enter), save and move to next line (Shift+Enter). Arrow keys can be used to change line selection. Panel can be closed and opened using button in its corner or 'Space' and 'Esc'. Manual delivery (RTC-29687) It is possible to create a new delivery manually – delivery for which there was no purchase order. It can be created using button in Deliveries page and is displayed as package and order delivery in status 'Draft'. It is created alongside with new purchase order in state 'Confirmed', so all changes on manual delivery cause export of order. Such order cannot be edited through 'Purchase order' view. A package code is created for all order despatch advice lines in manual delivery when adding the first line. New despatch cannot be created for order created through manual delivery. If any line selected when creating new manual delivery, then field in form for store is filled with value from selected line. 'View deliveries' permission is needed to view manual deliveries. 'Manage purchase orders' permission is needed to create and edit manual delivery. Submit delivery (RTC-30255) It is possible to submit delivery which was created through 3rd party import. This can be done using 'Submit delivery' button in delivery page. Before submitting delivery, there is a modal with information about delivery (submitted quantity, amount, deviation). It is possible to add a receive note. After submitting, counted lines (in displayed package or order) status changes to 'Received'. Submission does not affect the 'not counted' lines. If all lines are 'Not counted', submit isn't possible. Received line cannot be edited and resubmitted. When submitting, statuses of relevant orders and packages change either to 'partially received' or 'done' depending on other delivery lines in order/package. Delivery status is added on purchase order level. Whether a purchase order can be edited depends on the 'delivery status'. Status 'Done': only new lines can be added. After this process, the delivery status changes to 'Partially received'. Status 'Partially received' and 'Not received': new lines can be added. Delivery status does not change. Handling of delivery status 'In progress' (counted, not submitted) or 'Draft' (manual delivery) - not in scope. Removal of order lines is only possible if the purchase order does not have any order despatch advice lines and delivery status is 'Partially received' or 'Not received'. Editing order line - not in scope. Goods receipt from purchase order (RTC-25796) There is 'Receive goods' button in purchase order with status 'Confirmed'. It opens order deliveries page if there is order despatch advice imported from 3rd party. Button is hidden when all purchase order lines are delivered. |
Export | Goods receipt (RTC-30254) Goods receipts are exported to blob as JSON, with content as specified in Swagger. Goods receipt is created after submit of delivery. |
Order lines | 'In order' column (RTC-26264) 'In order' column in order lines tab in purchase order indicates quantity of items in all purchase orders that are not deleted and have status submitted, edited or confirmed and are from the same store as the purchase order. Filtering and delete button (RTC-31614) |
Procurement API | Use order line delivery date in API for order info for item for given store (RTC-30953) Order lines in API response are grouped by delivery date on order line level instead of date on order level. |
Purchase order | Decimal quantity (RTC-26261) It is possible to enter, import and export decimal quantity of item in purchase order. Quantity can have 4 decimals and be between 0.0001 and 999999999.9999. Edit delivery date of item in confirmed purchase order (RTC-30708) Delivery date can be edited when purchase order has status 'Confirmed'. Line number (RTC-28425) Line no. is identifier of order line unique within each purchase order. Column is added to purchase order lines grid. When adding items to purchase order, it is automatically generated as a next available number, starting from 1. One item can be added to purchase order multiple times, as another order line with other line number (in user interface and import). Change status of purchase order when changing delivery date (RTC-30955) After changing delivery date of 'Submitted' order or order line, the status of purchase order changes to 'Edited'. |
System | Migration to .NET 6 (RTC-28897) Procurement Service module is migrated to .NET 6. Item name and item group name (RTC-31164) Item names with up to 255 characters can be stored in the Promotion and Procurement databases. The same applies to item groups stored only in the Promotion database. When the item names are too long when importing OrderDespatchAdvice or PurchaseOrder via a third party, a validation error will appear. Suppliers export/import (RTC-30619) Export of suppliers from Item Service and import to Procurement is extended by 'VAT number', 'Lead time', 'Reference' and 'EDI' fields. Import of items performance (RTC-28310) Performance of import of items and supplier-items is improved. |
...
Package details view is opened after clicking package number in "Packages" tab in "Deliveries". Page shows contents of the package. Each line has its order number (package can contain items from multiple purchase orders). "Order no" links to order delivery details page.
Order delivery details view is opened after clicking order number in "Order" tab in Deliveries. Page shows contents of the order that is being delivered. Each line has its package number (order can be delivered in multiple packages). "Package no" links to package details page.
Both pages breadcrumbs show package or order number, supplier name, number of lines and quantity of items in this package or order delivery.
Improvements
Module | Description |
---|---|
Deliveries | Mark items as counted without setting deviation (RTC-28850) It is possible to mark item lines as counted using 'Confirm items' button on bottom of the delivery details page. Item lines can be selected by using mouse, Control and Shift buttons. There is also a 'Select all' button. After clicking 'Confirm items' button, selected lines have status 'Counted', and 'Received' column has the same value as 'Order'. Deviation equals zero. |
Import | Order status (RTC-27171) "Order Status" is optional field in purchase order import from file. Value can be set to 'Draft' (default) or 'Submitted'. "Submitted" orders import fails when order uses placeholder store/supplier/item/supplier-item. Draft orders can be submitted, but submitted order cannot be set as draft. Other statuses are not supported. Purchase order export is triggered after creating/updating submitted order or submitting draft order through import. |
Procurement | Supplier model/Item number: (RTC-26263) Supplier number and Supplier Model number imported from Items to Procurement. Purchase orders and deliveries: (RTC-26263) Columns added to Procurement module, displayed in Purchase Orders and Deliveries. |
Purchase order | Order type (RTC-26548) "Order type" must be set when creating new purchase order: "Replenishment" or "Preorder". Value is displayed in column in "Purchase orders" grid. Order type of existing purchase order cannot be changed (in user interface and import API). Confirm (RTC-25795) 'Edited' and 'Submitted' orders can be confirmed using 'Mark as confirmed' button on bottom of purchase order page. To be confirmed, order must have at least one order line, and store/supplier/item/supplier-item cannot be placeholder. After clicking button, 'Confirm order' modal appears, where 'Supplier order no.' can be defined (not required, unique within supplier). Delivery date on purchase order line level (RTC-25710) Delivery date can be set for each order line. Existing order lines have delivery date same as delivery date of order. Order level value is also used for newly created order lines. Delivery date of order line can be changed in 'Edit row' modal or by selecting multiple rows and using 'Edit date' button on bottom of page. Multi-select of order lines (RTC-25710) Order lines can be selected by using mouse, Control (Ctrl) and Shift buttons. There is also a 'Select all' button. Cancel (RTC-28234) Purchase order can be cancelled using button in three dots menu on bottom of page. Pressing cancel order button opens modal with description and buttons to close modal or cancel order. When cancelling order with submitted, edited or confirmed status, order is exported with status "Cancelled". Supplier order number (RTC-30018) Supplier order number is pre-filled with value in database, allowing order confirmation without change of this value. |
System | Import of store groups (RTC-28768) Profiles and teams and its assignment to stores is imported from Store Service. |
...