Caliach Vision Feature Enhancements up to V1.1000

F0059 - Parts cost record system

Date: 18 Apr 2001, version: 1.1000, rating: 20, platforms: All

Description: Parts master current costs do not show how it has been arrived at. Current cost log feature controlled by a system preference with listing, reporting and delete, archive and snapshot features. {Previously: R0026}

Get around: None

Caliach response: PTCFILE, MCDPTC, rCompany, rPtcList, wPtcList, wPtcPrint wPtmEdit, wSystemPrefs

F0060 - Mac OSX and Linux operating system variants and new environment features

Date: 29 Jan 2002, version: 1.1000, rating: 50, platforms: All

Description: Re-design the environment arrangements to accomodate Studio V3.1 fieldstyle improvements and provide for bother Mac OSX and Linux operating system versions of Caliach Vision. {Previously: R0015}

Get around: None

Caliach response: All classes to V1.100, wEnvironmentDesigner, tbEnvironment, wFixStylesV110

F0061 - Incorporate additional standard reports

Date: 25 Aug 2001, version: 1.1000, rating: 50, platforms: All

Description: Incorporate additional standard reports for SO and PO dates, costed stock movements and other submitted custom reports. NOTE: All submissions of custom reports for incorporation as standard and therefore subsequently supported will be considered. 9 reports added. Note: rDispatchAll and rInvoiceAll are alternative custom Dispatch Note and Invoice report classes. {Previously: R0063}

Get around: None

Caliach response: rDispatchNoteAll, rInvoiceAll, rPolDates, rPuhUnverified, rPuhVerified, rSolDates, rSthCostCur, rSthCostStd, rWohEfficiency

F0062 - Workflow Alerts Checking - automatic scanning of business condtions

Date: 29 Jan 2002, version: 1.1000, rating: 50, platforms: All

Description: A system is proposed whereby a series of pre-defined checks are run at defined points (perhaps on first log-in of the day for certain key users), and a report generated of items that require action / urgent action. The report could optionally be emailed to a defined person. The idea is to move from a passive system to a more active tool. One way to set up the alerts would be to create a matrix of users / alerts applicable. These checks could include the following: - WOs late for kitting WO's late for completion WO ops late for completion Overdue PO items Overdue credit control memos (on next action date) Out of date production plan items Overdue SO items Payments overdue for A/P & A/R Recent QA data outside limits Overdue MRP recommendations WO & O/W PO shortages Goods received but not invoiced (after defined period) New unapproved parts, customers, suppliers (do not use flag?) An initial set of triggers could be introduced, and users could request additional ones. {Original customer reference: R0001} {Previously: R0114}

Get around: Run regular check reports manually

Caliach response: cFile, mFile, oAlertChecks, rAlertReport, wAlertReportMaint, wAlertReportSelect, wAlertResult, mPrefs, wPrivileges, wNavigator, USPFILE

F0063 - Workflow Alert Triggers - automatic notification of business condtions

Date: 29 Jan 2002, version: 1.1000, rating: 50, platforms: All

Description: This feature would notify pre-defined individuals on certain system data criteria as it actually occurred, in a similar way to the existing notification of items short on sales / works / O/W PO orders when booked in. The difference would be that a message would be sent to key users / user, by email and/or system message box, and a method would have to be included to set up the criteria / users. These triggers could include the following: - Items due on SO / WO / PO when stock received (not just shortages) Stock going below re-order, min. stock, going -ve Bank accounts going -ve Accounts below budget at period-end WO scrap quantity Stock items quarantined QA data entered out of spec. New SO items where stock / projected stock not available New PO items and/or receipts where stock to exceed re-order level (future surplus) PO, SO, credit / on-order value limits exceeded An initial set of triggers could be introduced, and users could request additional ones. {Original customer reference: R0002} {Previously: R0115}

Get around: Run regular check reports manually

Caliach response: wTriggerMaint, wTriggerSend, MCDFILE, MEMORY

F0064 - Export and import of part, customer, supplier and all related master data

Date: 18 Apr 2001, version: 1.1000, rating: 30, platforms: All

Description: Export/Import a Part with all its associated structures: BoM, Route, Eng Data, Serial Number Structure, Quality, etc. {Previously: R0023}

Get around: None

Caliach response: wCusEdit, wPtmCusSupExpImp, wPtmEdit, wSupEdit

F0065 - Return to Supplier Back Order by Default option

Date: 6 Sep 2001, version: 1.1000, rating: 20, platforms: All

Description: I would like to request that, when returning goods to supplier, it would be a good idea to default the 'Back Order' tickbox to being on back order. This is because this is nearly always the case and even if it is not (and you don't untick it) then the worst that you have to do is delete it from the order. At the moment, if you forget you have to recreate the order which is much more work. {Original customer reference: R0019} {Previously: R0087} Introduced option optPOReturnBackorder.

Get around: None

Caliach response: oTerminal, wPuhReturn, optPOReturnBackorder

F0066 - Multi-company licenced names implementation

Date: 29 Jan 2002, version: 1.1000, rating: 50, platforms: All

Description: Currently the Caliach Vision licence has the provision for multiple company names. However, the program does not implement this provision. {Previously: R0014}

Get around: None

Caliach response: cPrefs, mPrefs, cStartup, wCompanySelect wDataFileCompany, wLicense, wMcdEdit, wMcdCoNames

F0067 - User settings to be added

Date: 24 Aug 2001, version: 1.1000, rating: 20, platforms: All

Description: Add user settings for: Navigator Header (on shutdown), Tooltips On (on shutdown), Print GRN on Goods Receipt (on window close), Print Distatch Note on dispatch (on window close), Print Invoice on dispatch (on window close). {Previously: R0040}

Get around: None

Caliach response: oEnvironment, USPFILE.oSettings.iOthers: NavHeaderNotVisible, WindowHelp, PoRecPrintGRN, DispatchPrintDN, DispatchPrintInv, DispInvPrintInv, SahRetBackorder, PORetPrintReturnN, JobPrintInvoice

F0068 - Duplicate Part QA Regime and Serial Number structure

Date: 24 Aug 2001, version: 1.1000, rating: 60, platforms: All

Description: When duplicating a part offer the option to duplicate any QA Regime and Serial Number structure. Also to be included when creating a part in SO configuration. {Previously: R0054}

Get around: None

Caliach response: wPtmEdit

F0069 - Drill down to outwork operation purchase orders from work windows

Date: 11 Oct 2001, version: 1.1000, rating: 20, platforms: All

Description: It has been suggested that with the wonderful drill down capabilities of the system it would be nice to drill down on the operation in WO maintenance and WO review to check there is / has been a PO for it and check the status of the related PO or PO history. {Previously: R0067}

Get around: None

Caliach response: wPartAssySub

F0070 - Active Production Plan update on dispatch option

Date: 9 Nov 2001, version: 1.1000, rating: 20, platforms: All

Description: As agreed with Paul Wilson we are using a production plan to drive our manufacturing, which works well. However, we find it a burdensome overhead to have to maintain the plan at the same time as dispatches and work ordering. We feel that the production plan would benefit greatly from an option that automatically reduced the active production plan on despatch of a product from the product family as determined by the planning alias system. It could quite simply review the plan and decrement quantities from the earliest date forward. Caliach Note: This comes up a lot in pre-sales work as well as on-site consultancy, people often express surprise that it is not a standard option as the rest of forecasting and production planning is so comprehensive. {Original customer reference: R0011} {Previously: R0096}

Get around: None

Caliach response: MCDPRDA, oProcessJobs, oProcessSales, wSystemPrefs

F0071 - Provide for special currency cent character that suppresses cents

Date: 28 Jan 2002, version: 1.1000, rating: 20, platforms: All

Description: Currently a currency (including system currency) must have a cent character. It would be useful to provide for the ability to suppress the cents when the words are printed on a document. In the case of Yen, Rupees etc. {Previously: R0099} The # character supresses the cents text.

Get around: None

Caliach response: cReportDest

F0072 - Goods Inwards History - require facility to change receipt date

Date: 25 Oct 2001, version: 1.1000, rating: 30, platforms: All

Description: Confirm PO prices / invoice verification allows certain changes to Goods Inwards history, along with PUHREF edit. We also require the ability to override the receipt date on the Goods Inwards window, and/or edit it retrospectively. It would also be useful to be able to edit the purchase history reference retrospectively (the reference that is used to record suppliers advice notes) as it can be entered incorrectly on occasion. {Original customer reference: R0002} Edifis Ltd also requested: We cannot always book goods in on the day they arrive, so we need the facility to enter a different receipt date on the goods receipt window, and / or the ability to edit the date on the Amend purchase history references window. On this window, it would also be useful to edit the purchase history reference (the one entered at the time of receipt, not the one taken from the PO - PUHREF as well as PUHUSER. {Previously: R0091}

Get around: None

Caliach response: wPuhRefEdit

F0073 - Additional items on PO receipt

Date: 18 Apr 2001, version: 1.1000, rating: 30, platforms: All

Description: PO Receipt: Would it be possible on this screen to allow for the receipt of additional items, not specified in the PO. It would be very helpful in our operations to be able to do this, where the packing (drum, tank, etc) are an integral part of the PO item, but can become a separate part of inventory once they are received. {Previously: R0016} Controlled by the system-level option optPOReceiptAddUsers that must list users permitted to add extra items from the Scratchpad, separated and followed by a comma.

Get around: None

Caliach response: oProcessPurch, wPolReceive, optPOReceiptAddUsers

F0074 - Customers and Suppliers to have Trade Description field

Date: 31 Jan 2002, version: 1.1000, rating: 20, platforms: All

Description: Add a Trade Description field to each of Customers and Suppliers. This would enable a brief product range for each company to help satisfy ISO9000 requirements without using the comments field. {Previously: R0116} Caliach Comment: This has not been implemented as a simple field addition to Customers and Suppliers. An improved linking environment to Marketing records has been provided with a button on both Customer and Supplier Maintenance and drag and drop in Marketing Maintenance. This is to provide for comprehensive Customer Relationship Management and Supplier Relationship Management.

Get around: Use comments.

Caliach response: cMarketing, taMarketing, wMarketMaint, wCusEdit, wSupEdit

F0075 - PO Receive Window does not show stock location

Date: 3 Jan 2002, version: 1.1000, rating: 20, platforms: All

Description: PO Receive Window does not show stock location. I believe it did in CaliachMRP - could it do so again? {Original customer reference: R0001} {Previously: R0104}

Get around: None

Caliach response: wPolReceive

F0076 - Exclude empty accounts from standard financial reports

Date: 18 Jan 2002, version: 1.1000, rating: 30, platforms: All

Description: When printing standard financial reports with the "Show Individual Account Lines" box checked it would be highly desirable to be able to exclude from the report any empty accounts for the period being reported, to avoid empty spaces on the printed report {Original customer reference: R0068} {Previously: R0105}

Get around: None

Caliach response: wAcGlResultPrint

F0077 - Auto-generate Batch of Work Orders from Sales Orders

Date: 10 Aug 2001, version: 1.1000, rating: 50, platforms: All

Description: Some operations operate a system of back-to-back work orders for each sales order line item. It would be useful to be able to do this from the sales order itself, where the part number, due date, start date (from lead time), quantity etc. are entered automatically - perhaps resulting in the batch work order creation window used in MRP results to actually confirm, consolidate and set the options for the work orders. It is probably not necessary to take into account existing stock etc., because it is expected that the feature would be used where work orders are strictly back-to-back with sales order items (ie. make/assemble to order). Stock information is available anyway from the planning tab of the sales order. {Original customer reference: R0040} {Previously: R0052}

Get around: Use MRP.

Caliach response: cSalesOrders, mSalesOrders, taSalesOrders, wMrpWoList, wSoMaint

F0078 - Work Order scrap reason when using work order tracking input

Date: 17 Aug 2001, version: 1.1000, rating: 30, platforms: All

Description: When entering WO trackingand selecting quantity the system allows the input of a scrap quantity but does not offer the oopportunity to record a scrap reason code for that operation {Original customer reference: R1000} {Previously: R0050}

Get around: None

Caliach response: wWtkInput

F0079 - Part number search in stocktake entry

Date: 8 Oct 2001, version: 1.1000, rating: 20, platforms: All

Description: There needs to be a part number search option in the stocktake entry window. Our stock sheets and freeze were done in location order to make the physical count easier. But it can be very difficult to find a particular part number in the freeze set, especially if there is no prefered location. {Original customer reference: R0037} {Previously: R0089}

Get around: None

Caliach response: wSttEntry

F0080 - Sales and Purchase Order Maintenance - parts for customer / supplier

Date: 26 Oct 2001, version: 1.1000, rating: 10, platforms: All

Description: On the item details tab for a sales order or purchase order, we find the customer / supplier part details button useful - the only problem is that it is not accessible until a part is selected. It would be even more useful if the button was active before a part was entered, on the basis of the customer or supplier selected for the order. {Original customer reference: R0003} {Previously: R0093}

Get around: None

Caliach response: wPolMaintSub, wPptEdit, wSolMaintSub, wCptEdit

F0081 - Option to print multi-location comments with batch id on picking lists and dispatch notes

Date: 18 Oct 2001, version: 1.1000, rating: 20, platforms: All

Description: Provide option to print the first 20 characters of the multi-location comments field when ever the batch number is printed on a picking list. And also provide option to print the first 20 characters of the multi-location comments field when ever the batch number is printed on a dispatch note {Original customer reference: R0000} {Previously: R0090}

Get around: None

Caliach response: oProcessSales, rSalesSuper, rWoSuper, optSOBatchComments, optSOPickStoComments, optWOPickStoComments

F0082 - Delivery Note Ref on Goods Receipt

Date: 3 Sep 2001, version: 1.1000, rating: 10, platforms: All

Description: On "Receive Goods" window the new feature that duplicates the delivery note number to all blank lines is good. One thing - if the ref is not put in the top box then it is not duplicated. This happens a lot on part receipts. Could it be any line? {Original customer reference: R0001} {Previously: R0068}

Get around: None

Caliach response: wPolReceive

F0083 - Shortage reports - show WO's due for made parts

Date: 27 Nov 2001, version: 1.1000, rating: 30, platforms: All

Description: The current W/O shortage report lists shortages of both bought and made parts but only gives details of the purchased parts. Is it possible to have this report modified to show W/O ref, qty due and date due of the made parts. {Original customer reference: R0008} {Previously: R0098}

Get around: None

Caliach response: rWosPurch, wWosPrint

F0084 - Annual Budget import/export for GL accounts

Date: 5 Oct 2001, version: 1.1000, rating: 20, platforms: All

Description: The ability to export into a spreadsheet all the accounts and future budget periods in order to create all the proposed budgets for the same range in the spreadsheet and then to import them. Either for all accounts or a discrete set say for a project. Particlarly useful for companies that require each department to present their estimated budgets for consolidation before being approved for the year. Equally useful for the quarterly or half year review when there might be a number of changes. {Original customer reference: R0025} {Previously: R0088}

Get around: None

Caliach response: wAcGlExport, wAcGlaMaint

F0085 - Provision to control printed flag on POs and SOs

Date: 18 Apr 2001, version: 1.1000, rating: 10, platforms: All

Description: Print PO & Print SO dialogues: No option to reverse printed flag.This is a great new feature on Print Invoice/Dispatch note, would be really useful here because most people print to screen first, and the system does not recognise when subsequently printed to printer. {Previously: R0030}

Get around: None

Caliach response: wPurchOrderno, wSalesOrderno

F0086 - WO Available-to-kit from Capacity Planning change WO date window

Date: 25 Jun 2001, version: 1.1000, rating: 20, platforms: All

Description: On the Work Centre loading Chart, we double click to open the window called 'Work Orders', to which you kindly added the Part Numbers. Then by double clicking on one of the lines another window called 'WO Completion Date Change' is opened. Would it be possible to do a shortage check here, as only one WO would be involved at a time, and so the performance penalty would be modest? {Previously: R0037}

Get around: None

Caliach response: taCapacity

F0087 - Part Lead-Time Changes Report

Date: 22 Aug 2001, version: 1.1000, rating: 40, platforms: All

Description: There is no report for part lead time changes anymore - a simple one that just tells you what changed. It is possible to run an anaylasis of all parts first but this is far too complicated. {Original customer reference: R0008} {Previously: R0045}

Get around: None

Caliach response: rPtmLeadResults, wPtmGloblead

F0088 - GL bank account report for auditors

Date: 18 Apr 2001, version: 1.1000, rating: 20, platforms: All

Description: To be able to print bank account review for a particular point in time - status at month end even though further transactions have been processed. {Previously: R0021} Print G/L Review now has transaction date selection.

Get around: None

Caliach response: rAcGlRev, wAcGlPrint

F0089 - Serial Number Structure design maintenance

Date: 5 Sep 2001, version: 1.1000, rating: 20, platforms: All

Description: When describing the Serial Number Structure you give the ideal (from the BOMs), which is fine. I then drag over the serial numbers that I wish to include in the SN structure. After this point there is no association between the SN structure and the BOM structure, correct? What would be the practicality of dragging in other serial numbered parts (perhaps parts not in the BOM). This would allow us to make a serial number association between parts that are related in practice but not in production. For example I would be able to have a photocopier with child SN records that tell me all its options and the kits that are with it. These items are never in a BOM together although they are put on the same sales order and sold together. The BOM structure and the SN structure are not necessarily the same. {Original customer reference: R0018} {Previously: R0085}

Get around: None

Caliach response: wSnsBom

F0090 - Delete non-conformance report records function

Date: 18 Apr 2001, version: 1.1000, rating: 25, platforms: All

Description: Provide delete or clear non-conformance report records. {Previously: R0029}

Get around: None

Caliach response: wReorganize

F0091 - Serial Numbers fully implement the Bar flag

Date: 24 Aug 2001, version: 1.1000, rating: 40, platforms: All

Description: The Serial number obsolete/do not use flag is not currently maintainable. It should be implemented in the maintenance window. {Previously: R0056}

Get around: None

Caliach response: wSnoEdit, wSnoList

F0092 - Add day literals to day fields on parts maintenance

Date: 24 Aug 2001, version: 1.1000, rating: 10, platforms: All

Description: Add 'days' to the parts maintenance window for shelf life and 'buy or make days' to lead time. {Previously: R0058}

Get around: None

Caliach response: wPtmEdit, wPtmGlobal

F0093 - Serial Number on Goods-in

Date: 3 Sep 2001, version: 1.1000, rating: 10, platforms: All

Description: On the "Enter SN on goods arrival" window it is possible to leave the window (and therefore commit the receipt) without entering all (or any serial numbers). This sort of latitude is fine but perhaps a message should appear to indicate that you are going to do this giving you the option to return and enter the numbers. {Original customer reference: R0003} {Previously: R0070}

Get around: None

Caliach response: wSnoPoCreate

F0094 - Work Order Kitting Window Enhancements

Date: 6 Sep 2001, version: 1.1000, rating: 20, platforms: All

Description: I would like to make two suggestions regarding the 'WO kitting window' and the 'Outwork kitting window'. 1) could you add projected stock (perhaps after the description) so that it is easy to discover what is preventing you from kitting by double-clicking it (like in parts) and getting the projected stock analysis. 2) could you highlight when available stock is less than required (could make the available numbers red or put an icon on the left). These enhancements would make it much easier to see a problem with WO kitting at a glance. {Original customer reference: R0020} {Previously: R0086}

Get around: None

Caliach response: wPoOutkit, wWoBackflush, wWoKitIssue

F0095 - Outwork purchase order - structure comments on component list

Date: 26 Oct 2001, version: 1.1000, rating: 30, platforms: All

Description: We would like any associated structure comments to be shown on the component list on an outwork PO. {Original customer reference: R0002} {Previously: R0092}

Get around: None

Caliach response: rPurchSuper, optPOBomComments

F0096 - Provide for change of dispatch and invoice date

Date: 30 Mar 2002, version: 1.1000, rating: 10, platforms: All

Description: It has been previously requested to allow the backdating of goods receipt. We would also like to be able to allow the controlled backdating of customer despatches and invoices, as a number of our contracts require this. This capability should not be made available system-wide, but allowed only for specific users. {Previously: R0118}

Get around: None

Caliach response: wInvNoSelect

F0097 - Work order option to prevent part number change

Date: 28 Jan 2002, version: 1.1000, rating: 20, platforms: All

Description: Provide an option to prevent part number change to a work order once it exists. {Previously: R0107}

Get around: None

Caliach response: wWkoMaint, optWoNoPartChange

F0098 - G/L Journal - cannot save (or post) without values

Date: 27 Feb 2002, version: 1.1000, rating: 10, platforms: All

Description: It does not seem possible in Vision to save a Journal without values - a feature in CaliachMRP that was useful for setting up "template" journals for re-use. It used to work when posted, but now you are told that there is nothing to post, and the journal lines are not saved. Perhaps the "save" button on the Journal Details tab could be enabled once zero value lines have been entered to allow the saving of the journal. {Original customer reference: R0001} {Previously: R0117}

Get around: Save Journals with values, and change the values after copying.

Caliach response: wAcGlJournal

F0099 - Creating a Serial Number sequence in Maintenance

Date: 5 Sep 2001, version: 1.1000, rating: 20, platforms: All

Description: When you create a new sequence from the SN maintenance window, its fields are initially populated from the record that you were on in the main window. I would argue that there is little practical value to this and that most times you have to delete all the fields before you start. You are creating a new sequence - it has nothing to do with the record you were looking at. {Original customer reference: R0005} {Previously: R0072}

Get around: None

Caliach response: wSnoSequ

F0100 - Creating a Serial Number sequence in WO or SO processing

Date: 5 Sep 2001, version: 1.1000, rating: 30, platforms: All

Description: When you do this from WO Receive window (or dispatch) the despatch date defaults to today with no ability to change it. This is undesirable in all cases, but especially in the case of WOs, it is extremely unlikely that you are dispatching today. This should be blank so that a lot of records are not created incorrectly. {Original customer reference: R0006} {Previously: R0073}

Get around: None

Caliach response: wSnoSequ

F0101 - Serial Number record Despatch Date value

Date: 5 Sep 2001, version: 1.1000, rating: 30, platforms: All

Description: I assume that the original intention of this field was to indicate the date that the serial numbered item is used (shipped). Given the new SN functionality, perhaps you should rename it "Date Used" and set it when either it is dispatched or it is assigned to another parent serial number (i.e. when it is consumed). Most child SN items will never be dispatched but they are used when they are put into a higher order assembly. {Original customer reference: R0007} {Previously: R0074}

Get around: None

Caliach response: wSnoEdit, wSnoList, wSnoSelect, wSnoSequ

F0102 - Cannot assign serial numbers to multi level structure on maintenance window

Date: 5 Sep 2001, version: 1.1000, rating: 20, platforms: All

Description: In the SN Maintenance window it does not seem to be possible to assign child serial numbers to the a structure with more than two levels (a simple parent/children one is OK). {Original customer reference: R0009} {Previously: R0076}

Get around: None

Caliach response: wSnoEdit

F0103 - Cannot put assigned Serial Numbers into structure in maintenance window

Date: 5 Sep 2001, version: 1.1000, rating: 20, platforms: All

Description: The Serial Number listing tab (in maintenance) only shows unassigned SNs (not assigned to SO etc.) so it is not possible to make structure assignments. SO assignments have little to do with adding to a structure. Could you put a checkbox on the left that would either show SNs that have no parent (the default) or all SNs (to allow reassignment). {Original customer reference: R0010} {Previously: R0077}

Get around: None

Caliach response: wSnoEdit

F0104 - Cannot remove serial numbers from structure in maintenance

Date: 5 Sep 2001, version: 1.1000, rating: 20, platforms: All

Description: There is no apparent way to remove Serial Number Structure assignments. They can be re-assigned but not de-assigned. {Original customer reference: R0011} {Previously: R0078} You can now use the Delete key in the tree list to remove pre-assignment.

Get around: None

Caliach response: wSnoEdit

F0105 - Serial Number Structure Maintenance window

Date: 5 Sep 2001, version: 1.1000, rating: 40, platforms: All

Description: It is VERY easy (no warnings) to delete or modify a BOM SN structure when you have already made SN structure assignments. You could potentially loose the entire set of SN structure records. Should you be able to do this if structures exist? {Original customer reference: R0012} {Previously: R0079}. The structure is not tested but a warning is now provided on deletes.

Get around: None

Caliach response: wSnsBom

F0106 - Not Possible to de-assign Serial Numbers on WO receive

Date: 5 Sep 2001, version: 1.1000, rating: 30, platforms: All

Description: When assigning Serial Numbers on WO receive. If it is a second receive for the WO or serial numbers already exist that are assigned to the WO then the SN list on the left defaults to using the existing assignments. This behaviour is fine (desired) for despatch because you may have previously assigned them. However, on WO receive what you need to do is create a new sequence but you can't because there is no way to change serial numbers other than assigning them a new number. In order to create a new sequence you have to be on an unassigned serial number, but you can't. I would propose that you do not change the default behaviour, as it is useful most times. You could add the ability to de-assign the selected items (a button perhaps) then all would be well. {Original customer reference: R0013} {Previously: R0080} You can now use the Delete key to remove selected serial number assignment.

Get around: Edit list line and blank serial number.

Caliach response: wSnoSoSetup

F0107 - Provide an additional field on quotation prepeparation for quotation validity

Date: 26 Mar 2002, version: 1.1000, rating: 10, platforms: All

Description: All quotations should have a finite validity. We currently express this in one of the text fields, but it would be preferable to provide an additional field in SOHFILE to record the validity date. This field should be included immediately on the quotation report, and may be used in future enhancements to issue reminders or alarms. {Original customer reference: R0072} {Previously: R0120}

Get around: Use Special Header Text

Caliach response: MCDQVAD, SOHQVAD, oAlertChecks, wAlertReportMaint, rSolDates, rSalesQuote, rSalesQuoteLand, wMcdEdit, wSalesOrderno, wSoMaint

F0108 - Part Default Sales / Purchase Accounts - won't take Asset Account

Date: 10 Apr 2002, version: 1.1000, rating: 20, platforms: All

Description: The facility to sell and buy items directly to an asset account is very useful to those accustomed to this method of accounting, but it is not currently possible to enter asset accounts as default purchase and sales accounts for parts in part maintenance, global changes and manager controls. If this was possible it would complete the picture. {Previously: R0121}

Get around: Change accounts in SO and PO maintenance.

Caliach response: oLedgers, wPtmEdit

F0109 - Sales Order Shipping Load management system

Date: 11 Apr 2002, version: 1.1000, rating: 25, platforms: All

Description: The ability to group separate sales order line items into shipping loads. Requires a sequence load number. Assignement and de-assignment of line items to a load. The ability to dispatch a load in one operation and print all the subsequent dispatch notes. Requires an indexed field SOLLOAD and SAHLOAD. {Previously: R0122}

Get around: Manually handle shipping loads with individual dispatches.

Caliach response: MCNLOAD, SAHLOAD, SOLLOAD, cSerial, cDispatch, mDispatch, taDispatch, wMcdEdit, wSolLoadAssign, wSolLoadShip, wSolLoadShipList, wSolPrint, wSolSelect, wSolSelectSimple

Back to Program Changes Contents