FACTS 7.8.2 Application Changes

System-Wide Changes

Disable condition for line detail in 3L is not disabling the button (Defect 389303)

Previously, the 3-Level Entry driver did not disable the line detail button when the line detail disable condition was true. This has been corrected in FACTS version 7.8.2.

Enhancements by Module

Accounts Payable

Noninvoice Check Entry (APE330)—Message "Goods Authorized but not yet received" displays when updating Non Invoice Checks. Can't run update. (Defect 404639)

The absence of a default branch specified in the user profile caused APCMIL.BRANCH$ to be null during Non Invoice Check Entry (APE330) processing and fired the incorrect message during AP Payment Register processing. In FACTS 7.8.2, the Noninvoice Check Entry program was modified to allow the user to enter a branch when necessary. The new Branch field in Noninvoice Check Entry displays only if the user does not have a Branch value entered in User Preferences F/M. If you have "No Priority" set in User Preferences F/M for "Branch", this field behaves as follows: during line entry, Branch, is a display-only field and is populated with the branch coming from the GL number you enter. However, if the branch is not part of the GL number (as determined in Company Control F/M) then the Branch field will be enabled and you must enter a valid branch to save the line entry.

General Ledger

Journal Inquiry (GLI620)—Cost Discrepancy GL breakdown & S/L handling (Updated from Defect 408119)

The posting of the GL will now include all the document line level information to allow more detail in the GL Journal Inquiry program. This change will allow the user to drill back to a source document that was updated by the cost discrepancy register if the inquiry view is available. Both the receipt and disbursement (usage) documents can be viewed from the Cost Discrepancy journal inquiry.

Journal Inquiry (GLI620)—GL Journal Inquiry defaults to last closed period instead of current period (Defect 370709)

The Journal Inquiry (GLI620) was modified. When the screen is initially displayed, the Period field now defaults to the current period instead of the most recently closed period.

Inventory Control

Cost Discrepancy Entry (ICE610)—Cost Discrepancy - For factored cost – allow user to enter the offset GL account (Defect 389585)

Cost Discrepancy Entry (ICE610) was updated to include a new field, Offset GL Acct. You can optionally specify the Offset GL account to use an alternate GL Offset account (offset to Inventory) for factored cost.

Usage Review (ICE555)—In Usage Review, the “Recalculate Usage” button currently takes the icwhse.last_disb_date$ and passes it to the recalc routine, but if last_disb_date$ is null, nothing happens (Defect 404726)

The Usage Review (ICE555) program was enhanced to allow the entry of a ‘date from’ to use in recalculating usage. Now, selecting the Recalculate Usage button will display a window with a date entry field. That value will default to the last distribution date in the ICWHSE file if that date exists. If one does not exist, the program will check to see if a line is selected in the list box and if a line is/was selected then that date will be the default date displayed - if no line selected then the default date will be 'today'. A date greater than 'today' is not allowed. The entered date will be the date from which usage will be recalculated. Previously in Usage Review, the “Recalculate Usage” button used the icwhse.last_disb_date$ and passed it to the recalculation routine, but if last_disb_date$ was null, nothing happened.

Usage Review (ICE555) / Usage Review Detail (ICE556)—Usage review and detail usage - allow F2 for end of IC period button on date range entry (Defect 404536)

In the Usage Review (ICE555) and Usage Review Detail (ICE556) programs, the Beginning Date field functionality was expanded. Now you can press F2 or click IC Period End icon to automatically enter the 'end of current IC period' or you can enter the date to be the end of the current IC period (even if that date is in the "future"). This allows you to view all the dates of the current period.

Actual and Qualified Usage System Processing Programs—Record actual usage for non-replenished items and exceptional sales (Defect 415138)

In FACTS, the actual usage was not being recorded for non-replenished or Exceptional Sale items. Usage could also be incorrectly recorded based on the Initiating and Shipping warehouses and the Replenish flag set in Warehouse/Item F/M (ICF920). In FACTS 7.8.2, the nightly system process to record the actual and qualified usage was modified to record the proper usage for non-replenish and exceptional sale transactions. For Sales Orders, the Advanced Inventory Management methodology for identifying the usage warehouse has been applied to all lines as needed. Now, the ICWHSE file will have the last disbursement date set to allow the system to rebuild the usage after the incremental has been applied. The Actual usage can be viewed in Inventory Control> File Maintenance> Usage Review after the nightly rebuild has been performed.

Item Inquiry (ICI610)—Clicking OK in Alt Look for catalog items - 'invalid data' msg (Defect 387530)

The Alternate Lookup feature in the Item Inquiry (ICI610) program has had the Catalog Item search option removed. Previously, selecting Alt Look button and choosing the Catalog Item search option returned an 'invalid data error' to the Item Inquiry screen.

Transaction Cost Processing Program (ICI663)—Ability to see the cost layer consumed by a transaction (Defect 402934)

In this release a Cost Layers tab has been added to the programs which currently support a Line Detail option to allow viewing of the Receipts used to fill the disbursement for documents. The source document information in the Cost Layer view allows an individual to research the source document and cost information allowing any corrective actions necessary. The user must have the Cost Security Code set in the Inventory Control Static F/M in order to view the new tab folder and list view. The Cost Layers tab is visible from the Line Detail screen from the following modules/programs:

Sales Orders

Order Confirmation (SOE320)

Direct Invoice Entry (SOE510)

Document Inquiry (SOI620) for Past Documents and Past Invoices

Purchase Orders

PO Receipt Entry (POE210) for negative quantities on received lines

Inventory Control

Transfer Inquiry (ICI640) for shipments

Transfer Entry (ICE320)—Header Detail Screen Update the Emergency Buy methodology to use the days remaining in the Review Cycle (Defect 411469)

An additional field, Replenishment, was added to the Header Detail screen of Transfer Document Entry (ICE320). The Replenishment field indicates whether the transfer is a normal replenishment document (Y) or the PO is an Emergency Transfer (N) for the item highlighted in the line item browser. A Transfer is considered to be a normal replenishment document if the flag for “Replenishment Transfer” is checked within the Transfer Entry. If the user / buyer choose to flag the Transfer as an Emergency Buy, this option will be unchecked. When selecting an Emergency Buy scenario for an ARP in the Buyers Control Center, the API will set the option to No for the transfer.

Transfer Document Inquiry (ICI640)

The new field is also visible from Transfer Document Inquiry (ICI640) program in the Inventory Control module.

Alerts Replenishment Parameters—PO and Transfer Early alerts not firing / clearing properly (Defect 414520)

The Alert on Product Arriving Too Early for Demand was not firing and clearing properly because calculations for transfers were not including incoming quantities to the proper warehouse and item combination. To correct this, the BKC100 check_timeline routine was updated to use the correct incoming transfers and add the incoming quantity for Purchase Orders and Transfers when checking the Early alerts in the calculations and when raising the alert.

Alerts Replenishment Parameters—Calculated Variance Alert (Defect 414057)

The Alert on Calculated VS. Frozen Order Point / Line Point / Order Quantity Variance was implemented in the FCATS 7.8.2 release. A warehouse/item can have its Order Point, Line Point and/or Order Quantity set and frozen with an expiration date for the freeze. You can raise an alert when the warehouse/item’s calculated order point, line point or order quantity differ from the frozen order point, line point or order quantity values set here. The values defined in this section indicate under what circumstances alerts will be generated for this scenario.

Alerts Replenishment Parameters—Abnormal Usage Alert (Defect 414056)

The Alert on Usage was implemented in the FACTS 7.8.2 release. When determining abnormal usage for a warehouse/item, you can specify whether to be notified when a value falls outside a high and low usage amount. Then an alert can be generated to review the usage.

Alerts Replenishment Parameters—Non-Replenishment Items with Hits Alert (Defect 414970)

The Alert on Non-Replenishment Items with Hits was implemented in the FACTS 7.8.2 release. The alert allows you to flag an item that is not being replenished and has been experiencing an increased level of activity. Proper responses to this alert could include evaluating the item for what is driving the increased activity, changing the item to a replenished item, or simply making a mental note and deleting the alert.

Cost Discrepancy Entry (ICE610)/ Cost Discrepancy Register (ICR610)—Cost Discrepancy GL breakdown & S/L handling (Defect 408119)

The functionality of the Cost Discrepancy Entry (ICE610) and Cost Discrepancy Register (ICR610) was enhanced to allow entry of WH type receipts, entering of a correction without GL Accounts for the receipt, and provide better handling for over shipment cost discrepancy entries. Additionally, the ability to begin a Cost Discrepancy Entry from Item Inquiry Receipts and LIFO/FIFO views was added.

The program change details are described as follows:

Cost Discrepancy Entry (ICE610)

A new Warehouse (WH) document type was added to the Cost Discrepancy Entry program. The WH document type behaves similarly to when an Adjustment (AD) type is used. The user will be able to enter an item and date to populate the Cost Discrepancy Entry screen. Individual lines can have an updated unit cost entered and processed. Cost Factoring cannot be applied to WH or AD document type entries. Additionally, document types that do not have GL and GL offset accounts on the receipt are now allowed in Cost Discrepancy Entry.

If the filling of an over-shipment (OS) has a different cost than what was used on the usage document, a cost discrepancy record will be automatically created during the receipt process and flagged as User Entered =”N”. Cost discrepancy records for over-shipments are display-only and cannot be edited or deleted in this program. You must run the Cost Discrepancy Register (ICR610) to process cost discrepancy records for over-shipments to allow additional edits to be performed.

A Disbursements button was added to Cost Discrepancy Entry. Highlighting a line and then clicking the Disbursements button will allow the user to drill down to the source document if the appropriate inquiry program is available. If the inquiry program is not available, the user will receive the corresponding message for view not available.

Cost Discrepancy Register (ICR610)

The Cost Discrepancy Register (ICR610) program will only update the receipt and disbursement costs since the GL accounts are not known. Previously the Cost Discrepancy Register would assign default GL account numbers.

Serial / Lot item register processing was also enhanced to adjust the line level cost of the usage documents (if used) and the receipt layer cost(s). Prior to this, only the Item Level (not serial / lot level) costs were being updated. The cost update will be performed at the lowest level first, and then applied back up the document lines. An example is SORSOL versus SOLOTS. In previous versions, SOLOTS was not being updated, only the line level cost was being updated. The issue was the resulting line level cost was not the “true” average of the serial / lot item layer cost. In the 7.8.2 release, processing changes now update the SOLOTS data table, and then update the cost of SORSOL based on the setting for Sales Order Static > Serial / Lot Cost method. If the Averaged Actual cost method is used, the SOLOTS costs will be averaged and applied to the SORSOL cost.

The Cost Discrepancy Register GL Summary now includes the following line level information: document type, document number, Receipt / Invoice / Shipment number, Line Number, Component Line, Item and a flag indicating if the item is a Serial / Lot item. This information will be posted through to the GL Journal and allow drill back from the GL Journal Inquiry.

Item Inquiry (ICI610)

The Item Inquiry Receipt and LIFO/FIFO Cost views have been enhanced to allow the ability to enter a cost discrepancy. A new Cost Disc Entry button will access the Cost Discrepancy Entry screen populated with the selected item information. Any of the corresponding lines, cost factor, and so on can be entered as if the user performed a search / load manually.

A Disbursements View was also added to Item Inquiry for both the LIFO/FIFO Cost and Receipts views. Highlighting a line and then clicking the Disbursements button will allow the user to drill down to the source document if the appropriate inquiry program is available. If the inquiry program is not available, the user will receive the corresponding message for view not available.

Replenishment Parameter Maintenance (ICF990)—RPM Detail view for OQ Rounding not showing UM for selected row (Defect 389107)

In the Replenishment Parameter Maintenance (ICF990) program, the UM box for Order Quantity rounding by Vendor/Transfer was not populating when viewing in Detail (Overrides) mode. The issue has been resolved, and now allows the UM drop box to display the proper value and have the appropriate UMs available if editing/viewing records in Detail (overrides) mode.

Replenishment Parameter Maintenance (ICF990)—Saving of Review Cycle changes in ICF990 while in Detail view won't save (Defect 390340)

When viewing records in the detail view of Replenishment Parameter Maintenance (ICF990), the edit ability was not available, or when available, would not allow saving of changes. In the FACTS 7.8.2 release, the edit ability was restored in the Detail view Replenishment Parameter Maintenance and user changes are now saved.

Replenishment Parameter Maintenance (ICF990)—"Cannot Delete Line" in Replenishment Parameter Maintenance (Defect 415127)

In Replenishment Parameter Maintenance (ICF990) users were unable to delete lines when using Detail (overrides) view. The delete confirmation was presented, but when the user selected Yes, the record was not removed. The ability to delete the selected line in Replenishment Parameter Maintenance was restored in the FACTS 7.8.2 release.

Manufacturing Control

Production Entry Programs (MCE140 and MCE240), Production Registers (MCR110 and MCR210), Formula Entry (MCE210)—(Manufacturing Control Bill of Materials and Formulation Serial / Lot disbursement issues (Defect 408746)

The Manufacturing Control entry programs (MCE140 and MCE240) and registers (MCR110 and MCR210) for Production and Formulation have been updated with the proper variable assignments. Additionally, the Production Registers (MCR210 and MCR110) are now returning the Averaged Actual cost and assigning it properly to the GL Distribution when the Serial/Lot Cost selected in Manufacturing Control Static F/M is set to Averaged Actual.

Previously, when using a serial/lot component for Production or Formulation, the Averaged Actual cost was not being returned properly in the Production Registers. In addition, based on the usage of the serial/lot item as an Ingredient or Packaging component for Formulation, the verification of the disbursement could fail and cause an over-shipment to be created.

Payroll

941 Print (PRP810)—941 Medicare Wages not going beyond FCA bracket 2 limit (Defect 396855)

The PR 941 Print (PRP810) program was not using values beyond the FCA bracket 2 limit for reporting wages. If there was an employee who has exceeded the second bracket (200,000.00) in wages, the 941 Medicare column was not reporting any wages above the FCA second bracket limit.

In FACTS 7.8.2 the 941 Print processing routines, PRP811 and PRP812, were updated to use the total taxable wages for the reporting period. Since Medicare currently does not have a cutoff for the total taxable wage amount, the logic to use a bracket limit was removed.

Tax Recap (PRR211) processing program after Check Register (PRR210)—Reports not balancing after recent changes for Medicare (Defect 395480)

The Tax Recap (PRR211) processing program was updated to correct a rounding issue for FICA for those employees going over 200K in earnings. A new routine, PRC210;FICA_SPLIT, now allows the FICA split during the Payroll Check Register (PRR210) processing for Social Security/Medicare. The new routine will return the Employee and Employer Social Security and Medicare split from the supplied FICA amount based on the current check.

Purchase Orders

Buyers Control Center Detail Screen (POE405)—Duplicate lines in the BCC in ICBCCL (Defect 406464)

An issue with special order items caused the Approve Replenishment Path (ARP) lines in the Buyers Control Center Screen (POE400) to show achieved amounts that did not have a matching detail item in the Buyers Control Center Detail Screen (POE405). This issue has been corrected so that only the applicable ARP will show the achieved amount for special order items.

Buyers Control Center Detail Screen (POE405)—Error 11 line 235 in POE405 (Defect 401552)

An error in the Buyers Control Center Detail (POE405) screen was corrected. Previously when processing transfers and the user recalculated the line, an error occurred if the recalculation did not return at least one item for the selected ARP. Now, when the ICBCCH record does not exist for the Approved Replenishment Path (ARP) passed in, the detail screen cannot load and the program automatically closes.

Buyers Control Center Detail Screen (POE405)—Error 11 in program POE405 line 22145 when BCC grid is empty (Defect 404564)

When accessing Replenishment Parameter Maintenance (ICF990) from the Buyers Control Detail Screen (POE405) for an Approved Replenishment Path without items in the grid, an error occurred. The following was modified to correct this: The LINE_KEY$ from the ICBCCL (detail) file is not required to be present. The setting of the variables based on the LINE_KEY$ to call Replenishment Parameter Maintenance can be empty. The correction eliminates the error for selecting View>Replenishment Parameter Maintenance without items in the grid.

Buyers Control Center Detail Screen (POE405)—Non-replenishment items do not appear in BCC when on backorder (Defect 413344)

An item flagged as non-replenish in Warehouse Item F/M (ICF920) that is replenishing for another warehouse was not being added to the Buyers Control Center Detail (POE405) screen when on backorder. The Buyers Control Center Detail (POE405) screen processing was modified, and the program now checks for non-replenish items during the calculation if the Include Non-Replenish Items option is selected in Warehouse Item F/M.

PO Receipt Entry (POE210)—(Updated from Defect 402934)

In the PO Receipt Entry (POE210) program for negative quantities on received lines, a Cost Layers tab has been added to the Line Detail option to allow viewing of the Receipts used to fill the disbursement for documents. The source document information in the Cost Layer view allows an individual to research the source document and cost information allowing any corrective actions necessary. The user must have the Cost Security Code set in the Inventory Control Static F/M in order to view the new tab folder and list view.

Buyers Control Center (POE400)—With PO Static flag “allow nonstock w/o SO” = No, don't allow add to BCC unless it's a special order (Defect 407393)

The Buyers Control Center (POE400) was allowing a non-stock item to be added on the Detail screen when the Allow Purchase Without SO option was not checked in Warehouse Item F/M (ICF820). The Buyers Control Center item validation now checks the setting of the Allow Purchase Without SO option in Warehouse Item F/M and issues the appropriate message. The item will not be added to the Buyers Control Center if the item is non-stock and the Allow Purchase Without SO option is set to "N".

Buyers Control Center Screens (POE400)—Update the Emergency Buy methodology to use the days remaining in the Review Cycle (Defect 411469)

The functionality of the Emergency Buy option in the Buyers Control Center was modified. The change updates the Temporary Review Cycle to the Days Remaining in the Review Cycle versus previously only showing products below Line Point that are also below Order Point. The Temporary Review Cycle will be stored in the ICBCCH record and used to calculate the items for replenishment.

The program change details are as follows:

Buyers Control Center (POE400)

In the Buyers Control Center (POE400) screen, the “Emergency Buy” checkbox was removed from the Calculation Options section. A Display drop down list that allows the toggling of the Actual versus Percentage values was also added.

Buyers Control Center Detail (POE405)

In the Buyers Control Center Detail (POE405) screen the emergency buy option was replaced with a Replenish Action drop down box that allows you to determine the type of buy to perform:

Line Buy--Normal replenishment based on the current system values / settings for an ARP. A line buy is the default type of buy. When it is determined that it is time to place a PO (because there are worthy items below Order Point), the Line Buy option will select all items that are below line point and recommend an order to bring them all back to line point. The Line Buy concept is that since a PO is being placed anyway, you should go ahead and order any items you know will be needed for the review cycle.

Emergency Line Buy--A purchase / transfer that is based on the remaining days in the review cycle to fill an urgent need. The Emergency Buy option is used to bring in only those items and quantities you need before it’s time to place the next regular PO with this vendor. If the ARP’s review cycle is 14 days, and it has been 10 days since the last PO, the Emergency Buy option will calculate the PO for the remaining 4 days – i.e. what you need to buy to cover the next 4 days. The Emergency Buy concept is used to avoid interrupting the review cycle by placing a small PO to take care of any current crises. Buying for the remaining time in the review cycle hopefully prevents having to do another emergency buy in a couple of days.

Below Order Point Buy--The items within an ARP that are below the Order Point will be included in the buy / transfer. All other items for the selected ARP will be excluded. This can be used for daily purchasing / transfers.

The Emergency Buy option now establishes a Temporary Review Cycle value, which is the Days Remaining in the Review Cycle versus only showing products below Line Point that are also below Order Point. If the date difference in days on the past PO record is greater than the number of days in the Review Cycle, then calculated Temporary Review Cycle value is greater than the Review Cycle value for the ARP, and the Emergency Buy option is disabled.

A new Last Replenishment Doc field displays the last PO Number and Order Date for the document. You can use the drill down icon for quick access to the source document.

The target and current information in dollars, weight, and cubes, variances, was enhanced to include the percentage of the target that has been achieved.

Header Detail screen for Purchase Order Entry (POE120) and Non-PO Receipt Entry (POE220)

An additional field, Replenishment PO, was added to the Header Detail screen for Purchase Order Entry and Non-PO Receipt Entry. A Purchase Order is considered to be a normal replenishment document if the flag for “Replenishment PO” is checked in Purchase Order Entry. If the user / buyer choose to flag the PO as an Emergency Buy, this option will be unchecked. When selecting an Emergency Buy scenario for an ARP in the Buyers Control Center, the API will set the option to No for the purchase order.

The Replenishment PO field indicates whether the purchase order is a normal replenishment document (Y) or the PO is an Emergency Buy (N) for the item highlighted in the line item browser.

The new field is also visible from the following programs in the Purchase Orders module:

On Order View (POC411)

The view is accessible from the Buyers Control Center Detail screen by selecting the icon in the On Order field in the browser.

Purchase Order History View (POC414)

The view is accessible from the Buyers Control Center Detail screen by selecting the icon in the Lead Time field in the browser.

Transfer History (POC415)

The view is accessible from the Buyers Control Center Detail screen by selecting the icon in the Lead Time field in the browser.

Suggested PO Inquiry

The program is accessible from Suggested PO Entry POE110>Suggested PO Inquiry >Inquiry>Receipts List.

Sales Analysis

Commission Entry/Correction (SAE310)—Error 11 line 5525 program SME997 (Defect 374965)

The Commission Entry/Correction (SAE310) program was modified so that an error no longer results when a salesperson/territory has been removed from the system. Now when using the Next Record function and a salesperson/territory has been removed from the system but SA commission records are still on file, an alert will display next to that salesperson/territory name that reads:).

"****** Salesperson/Territory No Longer On File ******"

When this is the case, the existing record cannot be added-to, edited, or lines deleted—it is view only. The entire record can be deleted, if desired.

If the user tries to manually enter a salesperson/territory that is no longer on file, the standard 'Not on File' text will display and the user must enter a valid salesperson/territory to continue, even if SA commission records are still on file for the entered salesperson/territory. This prevents the user from manually entering more commission records for a no longer on file salesperson/territory.

Sales Orders

SO Entry Options F/M (SOF915)—Unused checkboxes on Line Options tab (Defect 259886)

On the Line Options tab in SO Entry Options F/M (SOF915), the Options section was modified. The following checkboxes are not used and were removed: Committed, On Order, and Warehouse options. The Substitutes checkbox determines whether the Substitutes menu option is available. The Quotes checkbox determines whether the Quote menu option is available. The Direct checkbox determines whether the "Direct Ship" checkbox on sales order/quote line is enabled.

Daily Sales Register (SOR310)—Usage not getting updated for transactions after the DSR has been run (Defect 404659)

The background process used to recalculate usage was resetting the last disbursement date for a warehouse + item combination when the transaction was still "open". If an invoice was printed and the Daily Sales Register had not been run, the background process would reset the Last_Disb_Date$ in ICWHSE to NULL. After running the Daily Sales Register, the last disbursement date was still NULL and the background process would omit the usage. The code was modified to leave the oldest disbursement date in the ICWHSE file for any transaction that is outstanding. This allows usage to be properly maintained regardless of the Daily Sales Register and other register run times.

Order Entry (SOE210)—Deleting of a line in OE with SOBOMS Serial/Lot component for user created BOM is not removing the ICRDST record (Defect 410070)

In FACTS 7.8.1, the cost layers could become out of balance if a serial/lot component was used for an on-the-fly bill of materials item in Order Entry. When a line was entered and serial/lot numbers were assigned to the components, the cost layers would be out of balance if the user deleted the line during Order Entry.

The Order Entry line delete processing routine has been updated to use the proper document status and serial/lot quantities when removing an on-the-fly bill of material item. The SOC503 BOM_SL_DELETE routine now sets the quantity to de-allocate to the appropriate quantity (the shipped quantity or the committed quantity), based on the document status of the Credit Memo, Confirmation, Counter Sale or Invoice document.

Order Confirmation (SOE320), Direct Invoice Entry (SOE510), Document Inquiry (SOI620)—(Updated from Defect 402934)

In this release a Cost Layers tab has been added to the Line Detail screen for Order Confirmation (SOE320), Direct Invoice Entry (SOE510) and Document Inquiry (SOI620) for Past Documents and Past Invoices to allow viewing of the receipts used to fill the disbursement for documents. The source document information in the Cost Layer view allows an individual to research the source document and cost information allowing any corrective actions necessary. The user must have the Cost Security Code set in the Inventory Control Static F/M in order to view the new tab folder and list view.

Sales Order Entry (SOE210)—Update the Emergency Buy methodology to use the days remaining in the Review Cycle (Updated from Defect 411469)

Purchase orders created for sales orders are not considered a normal replenishment path and the Replenishment status setting is automatically set to No.