| Version/Build |
Date |
Reference |
Module |
Program |
Description |
| V3.100.33 |
14 Oct 2004 |
ARA |
POP |
D4-POP |
I have reviewd and re-vamped the purchase analysis calculations, which must be run on a weekly basis. When the option is selected the system asks for the date of the Sunday at the end of the week in question. The program then goes through the POP files and takes into account all delivered orders which fall within a 13 week retrospective period. |
|
| V3.100.32 |
12 Oct 2004 |
ARA |
D4-POP |
D4-POP-PROCS |
Changed the naming of the original text file generated at the end of a purchase order to have a .ARA extension. This is designed to stop the IDX system deleting the file after it has been completed. Using the EXECUTE command at the end of the order entry to rename the file to .TXT |
|
| V2.100.30 |
13 Aug 2004 |
Bug |
D4-POP |
D4-POP-PROCS |
Discovered that neither the stock header record or the depot record were being correctly update with the QTY-ON-ORDER during the generation of a purchase order in Delta 4. This has now been corrected in this build. |
|
| V3.100.29 |
10 Aug 2004 |
|
D4-IDX |
D4-POP |
Noticed that the D4-POP programs were not reflecting recent changes to the D4-IDX-PARAM file structure changes. Corrected this. Uploaded this complete build. |
|
| V2.100.28 |
06 Aug 2004 |
NC |
D4-RECIPES |
D4-RECIPES |
Recompiled the recipes program to out put to the S drive |
|
| V2.100.27 |
06 Aug 2004 |
IDX |
D4-IDX |
D4-IDX and D4-IDX-EXPORT |
Added a user table and associated maintenance and then included the users in D4USERS.TXT, the IDX export programs. Various emails to Ian and Nicola. |
|
| V2.100.26 |
05 Aug 2004 |
ARA |
D4-IDX |
All Programs |
This is the start of the IDX implementation. So far the parameter maintenance programs have been implemented along with the stock and purchase order exporting. This means that the D4-IDX programs are continuously exporting stock information to the appropriate lookup files. Also, all purchase order generated are being exported for display and processing on the hand helds. In theory it will be possible to start evaluating the Stock Take, Stock Transfer and Goods Received programs on the hand helds. No processing back to Delta 4 or Line 100 is happening in this build. |
|
| V3.100.25 |
27 Jul 2004 |
NC |
D4-POP-PROCS |
D4-POP |
As a request from Brian Young a facility has been provided to allow a delivery address to be added to each purchase order. The memory restrictions of this program were such that the procedure could not be done conventionally (i.e. a lookup on the standard delivery address file in Line 100). So 2 delivery addresses have been hard coded into the program and these can be accessed at the end of a purchase order by keying the appropriate code (a help panel has been provided). |
|
| V3.100.24 |
21 Jul 2004 |
NC |
D4-UTILITIES |
D4-PROD-DESCRIPTIONS |
Added the D4-RECIPE file to the list of files which can, optionally, have their product descritpions changed during the running of this procedure. |
|
| V3.100.23 |
09 Jul 2004 |
|
D4-WAREHOUSE |
D4-BIZERBA |
1. The labelling program now correctly updates the D4-PRODUCTION-PLAN 'Made' column.
2. The Print Additional Labels option no longer updates stock and decrements the quantity still to make. |
|
| V3.100.22 |
07 Jul 2004 |
|
D4-WAREHOUSE |
D4-BIZERBA/D4-MADE |
Changed the item number source from LT-ITEM-NUMBER to RC-ITEM-NUMBER |
|
| V3.100.21 |
30 Jun 2004 |
Update |
All Modules |
All Programs |
New version installed on CF server. |
|
| V3.100.21 |
16 Jun 2004 |
|
D4-WAREHOUSE |
D4-BIZERBA/D4-MADE |
A new faciltiy has been added which will allow the keying of either a sales batch code or a supplier's batch code and the screen will display the associated products. This is as close to full traceability as can be achieved at present. To test this select Delta 4 Warehouse/Enquiries/Trace by Batch Number. You can trace the products made from an entered suppliers batch number, or you can trace the ingredients used to make a selected sales batch number. |
|
| V3.100.21 |
15 Jun 2004 |
|
DELTA4 |
D4-BIZERBA/D4-MADE |
A INGREDIENTS table has been added to the D4-MADE header table. When the header record is written, so also are the ingredients. So, in Check Todays Production, if an item is selected the name of the ingredient and the supplier batch number is displayed (this is only useful if a single supplier batch number has been used in the manufacturing process). This is the first stage of total traceability. |
|
| V3.100.21 |
15 Jun 2004 |
|
DELTA4 |
D4-BIZERBA/D4-MADE |
Changed the method of recording the items labelled in the factory. Previously the Check Todays Production display used the STO-SERIAL-NUMBERS file for data. The data contained in this file is limited. I have therefore used the table D4-MADE to store product information, quantity, batch, date and time. Then, in Check Todays Production, the screen displays the product made on a selected date (or range) and displays in time order. So, from this screen, it is easy to see the pattern of manufacture throughout the day - when marinades etc. come on stream, it will be possible to track the workings of the factory on a day-by-day basis. |
|
| V4.100.06 |
08 Jun 2004 |
|
DELTA 4 PRODUCTION |
D4-PRODUCTION-PLAN |
The preparation side of the new Production Plan is now complete. This program will do the following:
1. Prepare a weekly production plan - e.g. run on a Friday for all of the following week.
2. Allow amendments to each product in the plan for any of the planned days.
3. Print a manufacturing production plan (can be re-printed any time).
4. Print a stock production plan - this is an attempt to show that stock requirements for each day of the plan.
5. Calculates the ingredient requirements for any day of the plan.
The next stage of this is to incorporate the plan into the warehouse programs so that the plan can be displayed in the warehouse or in the factory, thus monitoring production. |
|
| V3.100.20 |
27 May 2004 |
|
D4-RECIPES |
AMEND RECIPE PROCEDURE |
The bug which has been reported in the ingredient amend procedure when the ingredient is packaging whereby the cost price is not divided by the correct unit, has been fixed (testing required). It is essential that the Stock Extra STOCKED-IN-TO-EACH field is correctly populated. For example, if labels come in packs of 1000, then this field MUST hold the value of 1000, otherwise the ingredient amend will divide the cost price (in units of 1000) by 1! |
|
| V1.3 |
27 May 2004 |
UPLOAD |
IDX LABEL CONTROL PROGRAM |
CaldersLabels.exe |
A bug was found in this program yesterday caused by the EAN13 bar code check digit going to 10 instead of 0. This check digit can only be a single digit. Fixed by Andrew Thompson and sent to me overnight. Uploaded and tested OK by Di at 6.30am |
|
| V3.100.19 |
26 May 2004 |
UPLOAD |
DELTA 4 / DELTA 4 PRODUCTION |
|
7.00am - uploaded this build and re-built data dictionary. Also spent quite a bit of time on the system looking at the results of the labelling on stock. Stock movement (transaction) reports for fillers for 24th and 25th May look very interesting. Why are we selling more than we are making? |
|
| V3.100.19 |
25 May 2004 |
pamela |
DELTA 4 |
D4-REP-PICK-TIME |
I may well have found the secret of the time calculation (at least it is now within a few minutes). However, the enlarged print issue remains a complete mystery (OK on Epson printers). This report was put together in exactly the same way as all other reports (also, the printer target is confirmed as 0). There is absolutely nothing in the code which would cause the ASCII value to change at the end of file. Suggestion: set the End of File value in the control strings (Manager/Printers) to 27 70 and the Start File settings to 27 15. There is no guarantee that this will have any bearing whatsoever. Also, while this report is printing observe the beheavour of the font size settings (if they can be observed), and especially when it reached the end - do the values change? |
|
| V4.100.05 |
25 May 2004 |
NC |
DELTA 4 PRODUCTION |
D4-PROD-CPP-CONSOL |
As expected the error was in the D4-STOCK-EXTRA file (item number 5234 - SE-STOCKED-IN-TO-EACH = 0) causing a division by zero error. I have now tested for this possibility and if a 0 value is present this item will be ignored. |
|
| V4.100.04 |
24 May 2004 |
Nicola Chandler |
DELTA 4 PRODUCTION |
D4-PROD-CPP-CONSOL |
In response to a reported error at line 1129 some division by zero checking code has been added. This requires testing. Program re-compiled and up-loaded. |
|
|
24 May 2004 |
Nicola |
SVNUTILS |
STOCK UTILITIES |
A modification has been made to the Zero Depot Stock facility which will allow the by-passing of the Product Group request. It is now possible to zero the quantity of the entire stocks in a selected depot. This has been up-loaded and installed and so is ready to use. |
|
| V3.100.18 |
22 May 2004 |
|
D4-WAREHOUSE |
D4-BIZERBA |
Added new LABELS ABORTED screen message to remove any confusion when a user requests a print quantity greater than the available amount. The strict control here is intended to reduce the number of wasted labels. |
|
| General |
22 May 2004 |
|
DELTA4 |
ALL MODULES |
NB: when a new build number is applied, this number will only be displayed correctly at the top of the screen AFTER the DELTA 4 splash screen has been loaded at least once. |
|
| V3.100.17 |
22 May 2004 |
|
D4-WAREHOUSE |
D4-BIZERBA |
Having noticed that the updates to Line 100 stock control from the Bizerba labelling were incorrect changed the update field from LT-PACK-SIZE to LT-LABELS-TO-PRINT in the programs which update STOMAST and STOSNO respectively. |
|
| V3.100.16 |
21 May 2004 |
|
D4-WAREHOUSE |
D4-MADE |
This program was reading the STO-SERIAL-NUMBERS file to return the quantity of each individual item made on any given day. It would appear that the update to STO-SERIAL-NUMBERS might be flawed and required to be carefully checked. I have resorted to reading the data direct from D4-BIZERBA-CONTROL, but this does not hold the individual product quantity. |
|
| V3.100.15 |
20 May 2004 |
Nigel Amendments |
D4-WAREHOUSE |
D4-REP-PICK-TIME |
A number of amendments have been made to this program, primarily to change the ELAPSED-TIME calculation to use the ACTUAL-CALL-TIME generated at the time the order was created and incorporate the number of units to be picked for each order (with a total at the bottom).
WARNING: There are some issues relating to time manipulation in Retrieve, namely that all calculations have to be made in 100ths of a second! Therefore, if the order is very old (not really sure how old) then there is a chance that the elapsed time will be so large as to cause an overflow error. The reason why this has become apparent is that I have tried to calculate a true elapsed time, if the order is more than a day old. |
|
| V3.100.15 |
20 May 2004 |
Nigel Harrison |
D4-WAREHOUSE |
D4-REP-PICK-TIME |
This is a new program designed to report the elapsed time between the printing of a pick list and a start reference time for the date (e.g. 06:00) for any given order delivery due date. The user is required to confirm the 'Date For Pick List Print' (this would normally be today's date, but any historical date would do if historical analysis is required) and the 'Reference Time' (this being the time against which the elapsed time of the print is to be calculated).
The report does not appear in any module report list. Instead it should be set-up to run from specified users own menus (e.g. NH). The Retrieve program name is D4-REP-PICK-TIME (no parameters should be set). |
|
| V3.100.14 |
19 May 2004 |
|
Stock Extra Changes |
D4-SE-FILE |
Fixed a problem which was causing one of the recipe updates to run even if the 'Continue Without Check' option was selected. If this option is now selected, then the update procedure will be missed out. |
|
| V3.100.13 |
19 May 2004 |
|
DELTA 4 RECIPES |
D4-RECIPES |
Added a new report to enable the listing of all recipes containing a selected ingredient. This can be run by selecting Recipes/Recipe Reports/Find Ingredient. |
|
| V3.100.12 |
19 May 2004 |
|
D4-POP |
PURCHASE ANALYSIS |
Checked this to ensure that the report is in fact using the quantity delivered. |
|