38

Intrastat information at variant level

It should be possible to setup Commodity codes, Country of origin, etc. at variant level.

Read more...

1 Comments

Read more... 1 Comments

Category: Product Information Management (366)

STATUS DETAILS
Needs Votes
3

Check EAN can only linked to one product

Adding a check that a barcode (EAN) cannot be linked to two different products to avoid scanning issues (and other) in the logistic and warehouse processes. This could, for example, be set via a parameter in the Product information management parameters.

Read more...

0 Comments

Read more... 0 Comments

Category: Product Information Management (366)

STATUS DETAILS
Needs Votes
2

Validation of Categorie names placed on Hierarchy

Currently the check of uniqueness of a category name is done disregarding the place within the hierarchy. Example: Level 1 Level 2 value 1 Level 3 value 1 Level 2 value 2 Level 3 value 1 As in this case Level 3 value 1 is created on two different places within the hierarchy they are unique how...

Read more...

1 Comments

Read more... 1 Comments

Category: Product Information Management (366)

STATUS DETAILS
Declined
0

Change the dimension defaults

In many screens in the system where items have to be entered (Item inventory adjustment, Item allocation key, many more) the user faces a time consuming clicking process because the item dimension display by default displays Size Color Style and Configuration. Every time the user gets to that ...

Read more...

0 Comments

Read more... 0 Comments

Category: Product Information Management (366)

STATUS DETAILS
Needs Votes
63

Possibility to update Product Item Number when there are transactions

Since the platform 27 update the possibility to update product item numbers has been depreciated. Product numbers can still be updated however. As advised by Microsoft we want to keep our product numbers alligned with the item number of a product over all our entities. We have cases where we n...

Read more...

3 Comments

Read more... 3 Comments

Category: Product Information Management (366)

STATUS DETAILS
Needs Votes
6

Not possible to release several time the same product

Releasing several times the same item into the same company raises an error message in the log of product releases, which is not properly handled through the application : Cannot create a record in Item table (RetailInventTable). Item number: XXX. The record already exists. This is not user-fr...

Read more...

0 Comments

Read more... 0 Comments

Category: Product Information Management (366)

STATUS DETAILS
Completed
0

Add current fields to Entities

Add all product fields to entities - Counting Groups for example as theses are required to be uploaded

Read more...

0 Comments

Read more... 0 Comments

Category: Product Information Management (366)

STATUS DETAILS
Needs Votes
1

Create a periodic job to cascade unit conversion changes for catchweight items

Catchweight products have a conversion between the inventory unit (eg Kilograms) and the catchweight (eg each). In some industries this unit conversion changes regularly, such as seasonally. Changing the unit conversion updates the released product, but doesn't cascade to open orders or formul...

Read more...

0 Comments

Read more... 0 Comments

Category: Product Information Management (366)

STATUS DETAILS
Needs Votes
0

Product physiologic requirements setup by date

It would be nice to future be able to easily maintain setup of item product physiologic requirements per item group. Not having this option, the user may maintain these product physiologic requirement elements outside the system. Having the option to maintain the product physiologic requiremen...

Read more...

0 Comments

Read more... 0 Comments

Category: Product Information Management (366)

STATUS DETAILS
Needs Votes
0

Do not allow purchased items to be phantoms

The system allows to make items with default order type PUR to be phantoms. The slider on the item does let you say "YES" to phantom and the line type on the BOM line lets you make it Phantom for a purchased part . No warning. but serious MRP consequences. MRP will not recognize existing Purch...

Read more...

0 Comments

Read more... 0 Comments

Category: Product Information Management (366)

STATUS DETAILS
Needs Votes