Versions Compared

Old Version 193

changes.mady.by.user Lise Berntsen

Saved on

compared with

New Version 194

changes.mady.by.user Lise Berntsen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Coming next release

AreaDescription
Import

Fix: deleted order points (RTC-39007)

Order points are properly deleted from Procurement databased after import caused by deleting order point from item in Item Management.

Planned assortment

Import of assortment codes (RTC-38670)

Assortment codes are imported from register in Item Management. Values are imported based on unique code. If code in assortment register will be changed, in Procurement it is imported as a new assortment code. Statuses of assortment codes such as: active, default are imported and correctly assigned as well.

Purchase order

Order delivery date based on lead time and transport time of supplier (RTC-38621)

Delivery date of order is properly set to 'now' + 'supplier lead time' + 'supplier transport time' when creating purchase order in user interface (prefilled date), new orders created from 3rd party (when delivery date not defined in imported file), import from InStore app. Feature already existed for Excel import and order proposals.

Receive goods in InStore App

Fix: Scanning items with tandem GTIN (RTC-38887)

Items are properly matched in Procurement when scanning items with tandem GTIN during receiving goods manually in InStore App.

Suppliers in Procurement

Item suppliers on store group scope (RTC-36665)

Import of item suppliers is extended with store/team/profile scope. Import of stores from Store Service is extended by creation of 'Private' store group.
Item can be ordered only if it is delivered by selected supplier to selected store (store, store team, store profile or common supplier):

  • When adding line in user interface, item search result is filtered by that (item is visible in search only if can be ordered from supplier to store). Order lines grid show supplier model/item number of correct supplier.
  • When importing order by Excel file, supplier from file is used if correct link exists. If not, line not created and warning in notification. If no supplier in file, order is created for lowest level main supplier (found for store, team, profile, common).
  • When generating order proposal, order is created for lowest level main supplier (found for store, team, profile, common).
  • In imports from 3rd party, item-supplier are never created anymore. If link does not exist:
    • purchase order imported but cannot submit it
    • order despatch advice does not auto confirm order if such line is being added
    • order despatch advice not imported if such line is tried to be added to confirmed order
    • no validation in goods receipt imports.

Detailed validation message appears in 'submit/confirm order' modal, if there are no order lines, item is inactive, item, store, supplier is placeholder or one of the ordered items is not delivered by the supplier to store (instead of generic server side error).


...

Release 05.03.2024 

AreaDescription
Import

API contract for Order Confirmation from 3rd party (RTC-38745)

Business rules and file contract for import of order confirmation are available in Swagger. There is also example of files. Business rules for each import are in separate expandable section of Swagger.

Use price from database for order lines from InStore app (RTC-38901)

Wholesale price and discount are taken from Procurement database when creating purchase orders or receive goods manually through InStore App. That is the price that was imported to Procurement directly from Item Service. When price does not exist in Procurement database, then price and discount are equal to 0.

Order proposal

Fix: Max order point reached (RTC-39038)

When max order point is reached, what means difference between max order point and available quantity (+remaining) is equal to 0, and min order qty is defined and is more than 1, order proposal should not be created if it doesn't exist or is updated/removed if it exists.

Management

Fix: user interface bugs in purchase orders and order lines (RTC-38567)

In purchase orders grid:

  • Un 'Supplier No.' column, correct supplier number is displayed.
  • Default sorting of the grid is by order number descending.
  • 'Total' column show price in store currency. There is hidden by default column ' Total suppl. curr.'

In order lines grid and line panel:

  • Columns in grid are properly displayed after adding columns that are hidden by default (SKU and prices in supplier currency).
  • Changed translations of validation messages: 'Quantity must be a multiple of', 'Minimum order quantity is'.
  • Changed translation of field 'Sales next 30 days last year'.

It is possible to create manual delivery when user has permission to only one store. Store selection dropdown is hidden in such case.

...