JDE ITEM MASTER - ITEM BRANCH MASS DATA UPDATE FUNCTIONALITY REQUIRED
JD Edwards requires a lot of Product Data (e.g. Item Master, Item Branch fields) to be populated when a product is created to allow the system to operate.
However, the developers of JDE have not provided for the fact that in a real business many of these fields need to be updated en-mass. For example, the Item Branch may include a Category Code for Master Planning Family - and due to a factory re-structure a list of 5,000 items may need to change F4102.PRP4 from 'M01' to M99'. There is no end-user way of doing this, and any database manipulation carries a sever risk of data corruption.
Given that any fields related to Product information (especially F4101 Item Master and F4102 Item Branch) may need to be updated en-mass for a specific list of items (usually prepared on a spreadsheet), I believe that JDE should have a feature developed which allows users to extract all Item Master/Item Branch table values they choose to a spreadsheet, make changes and re-load back into JDE. When this is reloaded from the grid, it should validate row-by-row using the same validations as if the data was being manually keyed.
Whilst there is a Z Table upload process, this is not usable for the end-user. Also, having this feature would be beneficial for new JDE implementations for initial data uploads and the subsequent corrections and refinements required.
Points
Category: JD Edwards EnterpriseOne
JDE ITEM MASTER - ITEM BRANCH MASS DATA UPDATE FUNCTIONALITY REQUIRED
JD Edwards requires a lot of Product Data (e.g. Item Master, Item Branch fields) to be populated when a product is created to allow the system to operate.
However, the developers of JDE have not provided for the fact that in a real business many of these fields need to be updated en-mass. For example, the Item Branch may include a Category Code for Master Planning Family - and due to a factory re-structure a list of 5,000 items may need to change F4102.PRP4 from 'M01' to M99'. There is no end-user way of doing this, and any database manipulation carries a sever risk of data corruption.
Given that any fields related to Product information (especially F4101 Item Master and F4102 Item Branch) may need to be updated en-mass for a specific list of items (usually prepared on a spreadsheet), I believe that JDE should have a feature developed which allows users to extract all Item Master/Item Branch table values they choose to a spreadsheet, make changes and re-load back into JDE. When this is reloaded from the grid, it should validate row-by-row using the same validations as if the data was being manually keyed.
Whilst there is a Z Table upload process, this is not usable for the end-user. Also, having this feature would be beneficial for new JDE implementations for initial data uploads and the subsequent corrections and refinements required.
3 Comments ›