Release 4.27
New deal log facility When a user adds a new deal, makes certain changes to a deal, or deletes a deal, the system will now capture who made the change, when it took place (time stamp), and what action took place. To access the new screens associated with this information, the user will see a new function key ‘F18=Deal log’ on the K3S_5040 ‘Deals by Buy Group’ screen.
Customer Usage enhancement for multi-level processing in a Hub Transfer environment
The system will now take adjustments to the product average, and look upstream to see if it is being sourced from a Hub Transfer Supplier. If so, the corresponding product will also be adjusted, and then the system will check his upstream source. Up to 9 levels of hierarchy can be checked for adjustment.
Hold Out Quantity records can now be maintained by group When multiple product Hold Out Quantity records all have the same Location, Reason code, Begin date and End date, then the user will be able to work with this group of records as a set, to make certain changes. The user can perform a 3=Copy to the group of records, and then change the Reason code globally, change the Begin and/or End date globally, change the Location (for multi-location environments), and optionally delete the group being copied. The user can easily 4=Delete an entire group of related Hold Out Quantity records. The user can also list (7=Products) the products in a group, so that individual quantity changes can be made, or the individual product hold out record can be deleted. To access the new Product Hold Out Groups screens, the user would press ‘F19=Groups’ from the K3S_3050 ‘Product hold out quantities’ screen.
The management reports have been adjusted to provide feedback to the user when ‘no records’ have matched the criteria for running the report - Instead of not having the report to print, because ‘no records’ could be found that match the criteria requested, the user will now get the cover page which shows what criteria was requested, and then the ‘no records’ label.
The management reports now provide a method for the user to specify that ALL supplier sub components be rolled up into the totals for that supplier - By entering an ‘*’ into the supplier sub code field for the report request criteria, the user will now see these values summarized by supplier, versus having each individual supplier sub code printed.
‘Path of Replenishment’ view For customers who have multiple locations, and use the Hub Transfer facility, this new program will provide a way for you to visualize the ‘Path of Replenishment’ for your multi-level hierarchy. From the K3S_8000 ‘All locations for a product’ screen, the user will see a new ‘F5=Path of Replenishment’ option. Level 1 would be from your regular supplier source to your facility(s), while levels 2,3,4… would display the rest of your internal distribution structure. This is a valuable tool for users who need to view their internal distribution network.
Manual Minimum/Maximum enhancements.
A) The manual minimum/maximum in days capability is now functional. The user may enter the manual minimum and/or maximum in days to be used for calculating the suggested order quantity. The same rule applies for using the manual minimum and/or maximum in days, as we use when processing the manual minimum and/or maximum in units. That rule is: the system will use the larger of the minimums, and the smaller of the maximums (system generated min/max versus manually entered min/max).
B) The user now has the ability to enter just one value for the manual minimum/maximum in either days or units. Previously the system required for the user to enter a manual maximum value, if a manual minimum value was entered. Now the user can enter a manual minimum value without entering a manual maximum value, or the user can enter a manual maximum value without entering a manual minimum value. The system will understand how to process this information for either days or units.
C) The system will now allow a company to use a straight manual minimum and/or maximum in either days or units, without using the normal rule. The normal run is that the system will use the larger of the minimums, and the smaller of the maximums (system generated min/max versus manually entered min/max). Usually a company would prefer to use the normal rule. However this new capability “straight rule” will allow companies to migrate over from other buying systems where they used the straight min/max approach.
Service Levels by Product Groups This new program series will provide customers with a method for setting service level targets by Product Group 1, and also by Product Group 1 and Group 2.
The system now provides a choice for having the values from linked products either to be used, or not to be used, in different calculations - Product links can be established from the K3S_1040 ‘Orders - Product detail’ screen using ‘F13=Links’. Previously the system would also use the values from both the ‘From’ and ‘To’ product in report calculations, and Order Cycle Analysis. The default being set for this release is to not use the values that come from the ‘From’ product, but only use the values from the ‘To’ product in these calculations.
The supplier maintenance program would at times generate invalid Supplier Lead Time audit trail transaction records. During the install of this new release, these records will be fixed.
Product Hold Out Quantity records will now automatically be changed during the night job, if a supplier switch has taken place.
There were several screens in the system, where the user can perform an ‘F20=Toggle’ action, yet the screen did not show a ‘1 of X’, ‘2 of X’, etc. label. These screens have now been changed. An example of a screen that did already contain these labels would be the Products screen, which contains 5 separate screens of data. The user can view the ‘1 of 5’, ‘2 of 5’, etc. by looking on the 2nd line, just under the title of the screen. An example of a screen that did not previously contain these labels would be the K3S_3040 ‘Product Forecast Changes Log’, which actually does have 3 different screens.
Product Hold Out Quantity records will now be displayed with a ‘-‘ sign, if a negative value has been entered. At least one customer does actually key in negative Hold Out Quantity values into the system, and now they will display correctly.
Several fixes were made to the program that will allow you to add new products to the system during the day, and not wait until a night job.
Several new programs were developed, and adjustments were made to several existing programs, that will enable the system to in beta form for ‘external inventory processing’. The new areas include Vendor Managed Inventory, and Store Level Replenishment.
For weekly forecasted products, both the last week of a year, and the first week of the new year, would not always display the past few weeks of history correctly. This has been fixed.
Additional edits were placed into the maintenance programs for Hub Transfer Suppliers, to keep users from the following problems:
Trying to add a regular product to a Hub Transfer Supplier, when his regular source supplier is already set up for that Hub.
Trying to add a regular supplier to a Hub Transfer Supplier, when products under that regular supplier are already set up. The system will now provide a warning, and allow global deletion of these products, so that the regular source supplier can be added.
Trying to add a regular product, or a regular supplier, to a Hub Transfer Supplier which would cause a double point (pointing in both directions). This condition would be like having two Hub Transfer Suppliers trying to feed each other for the same product.
18) Deal System fixes. There were many fixes made to the deal system, which became visible with the new deal log facility mention in #1 above.
When a product had two deals back to back (one ending 12/31/2000 and the next deal starting 1/1/2001), but the system was not scheduled for night job processing until AFTER the start of the new deal (1/2/2001 or greater), then the system would miss attaching the new deal to the product. That happened this past year end for some customers, where a deal ended on a Sunday (12/31/2000) and the next deal for that product started on New Years (1/1/2001), but they didn’t perform night job processing for 3 days (Saturday, Sunday or Monday). So the next time they performed night job processing was on Tuesday (1/2/2001) and therefore the new deal did not get attached. During the install of this new release, a program will fix any broken links from deals to products.
When a customer uses the Hub Transfer System, then deals should become disconnected from a product when they move over to a Hub. When a product moves from a Hub back to a regular source supplier, and if a deal is active for that product at another division, then it should be activated for the product that has moved back to its regular source.
