Versions Compared

Old Version 198

changes.mady.by.user Lise Berntsen

Saved on

compared with

New Version 199

changes.mady.by.user Lise Berntsen

Saved on

Key

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

...

AreaDescription
API

Export of ordered quantity (RTC-38244)

Ordered quantity is exported to a Procurement.OrderedQuantity.Export blob with file format as in Swagger. It contains identifier of store and item, ordered quantity and date when this value has last been updated. This is same value as 'In order' field in Procurement Management. This is a sum of remaining quantities in orders with status submitted/edited/confirmed. Value is exported after each time when this sum can change.

System

Import of assortment codes (RTC-38694)

Assortment codes are imported on item level from Item Service if assortment code is added to item or edited. Not existing assortment codes are pushed into table with assortment codes.

Validation error messages (RTC-38924)

There is a validation message saved in the database and shown in Integration Platform, when the user tries to import file through 3rd party to Procurement module with field with spaces/enters at the beginning or at the end.


...

Release 18.03.2024

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).

...