In FACTS 9.1.1, these modules were entirely removed from the FACTS authorization code algorithm.
FA – Fixed Assets
ER – Equipment Rental
SC/TS – Tech Support
RQ
TF – TeleFACTS
CL – CodeLight
VF – Visual FACTS
DW – Data Warehouse
Spa – Spanish
SQL Server is also no longer an option.
For FACTS systems that had any of these modules enabled, when upgrading to 9.1.0 or higher, you will need an updated Authorization Code Sheet.
As part of this change, the Modules tabs of System Control F/M (SMF950) and Company Control F/M (SMF920) have been updated to present the valid modules in a more logical/organized presentation, with the 8-Pack modules listed together and separate sections for Optional Modules and Integrations. The SQL Server tab was also removed from Company Control F/M, and the Localization tab with the Spanish Language Pack setting was removed from System Control F/M.
Additionally, the Authorization Code Sheet has been reorganized to match the new display for simpler entry of the authorization codes.
In the FACTS/CenPOS integration, pre-authorization processing was fixed to include the ability to re-authorize a pre-authorization automatically and raise alerts when the pre-authorization is expiring or the automatic re-authorization failed.
These FACTS programs were updated to implement these changes:
In Credit Card Control F/M (SME957), these new prompts were added for reauthorization processing.
Auto Re-Auth # Days- the number of days old a pre-authorization is when the pre-auth is automatically reauthorized.
Existing Pre-Auth Alert # Days- the number of days old a pre-authorization is when the pre-auth expiring alert is raised.
In Customer F/M (ARF910), Quick Customer Add (ARF915), and Transfer / Change Customer Codes (ARU910), these two prompts were added for controlling the reauthorization of a pre-auth.
Auto Re-Auth -Indicate whether to automatically re-authorize this customer’s pre-authorization credit card transactions.
Hold Doc -Indicate whether to place the sales order on hold if the automatic re-authorization fails.
In Deposit/Payment Entry (SOC718), a new Re-Auth button was added to manually re-authorize a pre-authorization that is about to expire.
An alert is raised when a pre-auth transaction qualifies for automatic re-authorization based on the customer’s settings and the # days old setting in Credit Card Control but the attempt to re-authorize the transaction fails.
S3 Data Updater Background Process (BKC609) was updated to perform reauthorizations automatically if applicable and raise the new Auto Re-auth Failed alert.
For pre-auth transactions that do not qualify for automatic re-authorization based on the customer’s setting, the A1 Alert Minor (BKC100) background process will raise the Pre-auth Credit Card Transaction is Expiring alert when the pre-auth is old enough based on the CC Control setting.
You can access the Alert Control Center to view and re-authorize the pre-auth or optionally dismiss these alerts. From the alert, you can click Re-auth to access Deposit/Payment Entry to re-authorize the pre-auth. The Alert Control Center (POE400) was updated with a new Re-auth All button to re-authorize all pre-auth lines that have raised the PreAuthExp alert.
When adding/changing/deleting ShipVia records within FACTS (Ship Via F/M) these changes were not propagated correctly through StoreFront, leaving Carrier Code records in Storefront that do not exist in FACTS. This is a procedural issue where the Storefront Initialization (SMU 960) program from within FACTS was run at the wrong time and created orphaned records in StoreFront.
To correctly propagate ShipVia/Carrier code information to StoreFront:
1 Login to the Storefront Admin utility
2 From the Admin Utility menu, click RETRIEVE DATA
3 Check the Carrier Codes check box. (Select ALL if desired.)
4 Click RETRIEVE DATA.
5 When the SUCCESSFULLY RETRIEVED DATA message is displayed, Storefront Carrier codes have now been updated and match the Ship Via records in FACTS.
In FACTS 9.1.1, a new logging feature was added to the CSCPOSTKN processing program. When the new logging property is turned on in CSCPOSTKN, a TOKEN_REQUEST_LOG.txt file, which contains all of the components of a USETOKEN call to Cenpos, is created. Each transaction in the log file is wrapped between "--->TRANSACTION START:" and "--->TRANSACTION END:" comments to facilitate cutting/pasting specific transactions out of the log file as needed.
In FACTS 9.1.1 metadata changes were implemented to disable the "record navigation" arrow buttons when a new record is created. The result now allows the user to use the F4 key to traverse all fields and tab screens backwards when creating new records. This is similar to pressing the Tab or Enter key for a new record (like in a File Maintenance screen multiple tab screens) and "entry focus" moves forward through all fields and all program tab screens. Once the new record is saved/aborted the record navigation buttons are enabled again.
These changes were implemented in FACTS 9.1.1 APIs.
The QuoteLoad, OrderLoad, OrderTotal APIs now include support for component “on-the-fly” bill of material items. If an item is flagged as a BOM finished item and to create the bill of materials, the API will attempt to create the component lines, following the established rules for the customer and items. If anything fails, the API will be rejected with an appropriate message.
The display of the warehouse quantities window is now controlled by the same setting that controls the warehouse quantities window in the main entry screen.
The QuoteLoad, OrderTotal and OrderLoad APIs now have the ability to receive these new data tags in the OrderHeader nodes.
QuoteLoad API
FreightAmount and HandlingAmount
If either of these is included, they will be added together and calculates as freight for the Quote. Note however, that FACTS’ quote handling does not preserve freight with the quote or pass it on to the sales order, so these values are of limited use in QuoteLoad.
TermsCode
This forces the AR Terms Code on the quote to this value.
OrderTotal and OrderLoad APIs
FreightAmount and HandlingAmount
If either of these is included, the freight will be set to these amounts, and the freight method for the order will be forced to “C-Calculated”.
The freight and handling amounts will be stored in warehouse’s freight and handling fields and the override flags set.
TermsCode
This forces the AR Terms Code on the order to this value.
The QuoteLoad, OrderTotal and OrderLoad APIs now support loading temporary items. These data tags are new.
OrderDetail/LineItemInfo/TemporaryItem – set to either ‘Y’ or ‘true’ if the item is a temporary item
OrderDetail/LineItemInfo/ItemClass – required for temporary items, optional for non-temporary items
OrderDetail/LineItemInfo/CommissionPcnt – optional for all items (not available for QuoteLoad)
OrderDetail/LineItemInfo/TaxableFlag – set to either ‘Y’ or ‘true’ – optional
OrderDetail/LineItemInfo/UnitCost – optional for all items. for temporary items, if this is omitted, the cost will be 0
OrderDetail/LineItemInfo/VendorNum – required for temporary items, optional for non-temporary items
OrderDetail/LineItemInfo/UnitWeight – optional for all items; for temporary items, if this is omitted, the weight will be 0
The OrderLoad API was updated for the integration to Storefront 2.0.500. In versions of FACTS 9.1.0 and older the OrderLoad API processing would parse the OrderLoad.xml request and process the credit card information (if there was any included) as a CenPOS transaction when there was a “C” contained within the XMLTAG CCProcessorID (example: <CCProcessorID>C</CCProcessorID> ). If there was any other value contained within the XMLTAG CCProcessorID then the credit card information was processed as a non-CenPOS transaction.
In FACTS 9.1.1, the OrderLoad API now parses the OrderLoad.xml file and processes credit card information (if there is any included) as follows:
This change to the OrderLoad API was made to accommodate the integration between FACTS 9.1.1 and Storefront 2.0.50x but is applicable to any process utilizing the OrderLoad API for other purposes.
At the 9.1.1 release, these programs were entirely renumbered and had major code re-factoring: SOC112, SOC113, SOE113, SOE513, and SOC508.
Due to the new menu design/type, the “Caption” type entry on a menu is no longer supported starting in FACTS 9.1.
SOC112, SOC113, SOE113, SOE513, and SOC508.
For users running FACTS programs, the use of the PxPlus *control program has been eliminated, including access to the PxPlus utilities by using the F5 key. Access to the utilities is still available from a command prompt.
Additionally, while the use of hotkeys/$CTL- programs is preserved, those programs must now adhere to these new requirements:
These changes were implemented in Advanced Inventory Management.
In FACTS 9.1.1 WMS functionality was restored and enhanced in Adjustment Entry (ICE210). Now if you specify a WMS-controlled warehouse and you are not a WMS administrator, the message: WMS Warehouse – Adjustment must net zero is displayed at the top of the screen. The ability for WMS administrators to adjust quantities for items in a WMS-controlled warehouses was restored. Non-WMS administrators cannot exit Adjustment Entry (ICE210) for an item that is in a WMS-controlled warehouse if the adjusted quantity does not sum to zero.
When non-net-zero quantity exists and the user is not the WMS administrator, a dialog box is now displayed with the first item that is the problem and a login prompt for the WMS Admin user and password to override the net zero requirement. Once the WMS Admin user and password is entered, the non-wms-admin user will not be prompted again (while remaining in ICE210) if any line (for any warehouse) is not net zero.
Functional changes in the Suggested Cost/Price Entry (ICE410) program now cause the screen focus to land in the in the Effective Date field when creating a new suggested cost/price for an item. Additionally, the item navigation buttons to display the Previous Item, Previous Suggested Costing/Pricing Line, Next Suggested Costing/Pricing Line or Next Item suggested costing/pricing information were relocated to the upper right corner of the screen.
The Cost Discrepancy Register (ICR610) now displays the list of warehouses that have cost discrepancies, and the Warehouse field will default to the first warehouse in that list.
The IRS is rejecting the 1095-C forms originally coded to in ACA 1094/1095 Management. To correct this, a different form from Transform from the original one we recommended must be used. Instead of form number B95CFPREC, you must use form B1095C (and optionally B1095CCON, for employees that have more than 6 dependents). Also, the new 1095-C form requires landscape printing instead of portrait printing. The change to the 1095-B form was minor and does not require a different form.
Previously when an inactive item was entered in the Buyers Control Center Detail (POE401) screen, there was no message to indicate the item was inactive and processing resulted in a “deleted” purchased order. Now the user is alerted the item is inactive, and if the user enters an item that is already in the grid and it is an inactive item, the user is also alerted the attempted entry is inactive. The purchase quantity cell for the inactive item is shaded in light red so that all items in the grid that are inactive can easily be found.
When the Adjusted Review Cycle prompt was updated in the Buyers Control Center (BCC) Detail screen, the Replenishment Math window values were not updated. Code changes in the Buyers Control Center Detail screen have improved the calculations for review cycle and adjusted review cycle, as well as "adjusted" line point when the adjusted review cycle changes the line point, and the Replenishment Math values are updated. Note that lines in the BCC Detail screen with the Override check box checked, will still display the Replenishment Math screen calculations based on the review cycle in effect. For example if the line in the BCC Detail was frozen when the adjusted review cycle was 100 and then later the adjusted review cycle is changed, then the Replenishment Math screen displays the values using the 'current' adjusted review cycle (and not the 100 that was in effect when the Override check box was checked for line). When deselecting the Override check box, all values on that line are not updated until a recalculate occurs either by changing the adjusted review cycle on the BCC Detail screen or through normal Buyers Control Center (POE400) recalculation options.
These issues were corrected.
On the Suggested PO Report, items were not being relieved when initiating and shipping warehouses are different. Items on a sales order with different initiating and shipping warehouses remained on the suggested PO report after the PO is created (either thru Buyers Control Center (BCC) or manually).
Creating a tie to a special order did not check if it already was tied in the BCC and if a POSUGG record existed and the user entered/created the PO line via the F1 key in Order Entry, the POSUGG record was removed, but if that PO line was deleted, then the POSUGG record was not "recreated" and was lost.
In the BCC, item vendors and suggested special orders would become out of sync if the vendor was changed in Item F/M. The new vendor was not reflected in existing order lines (SORSOL) or in Buyers Control Center lines (ICBCCL) generated from a special order (suggested entry). The special order was "lost" if primary vendor changed after initial entry in Sales Order Entry.
The Commit Backorder Quantities (SOR210) program did not check if an order was a special order (suggested) which had been imported into the Buyers Control Center for procurement/transfer, and attempts to proceed in the BCC failed once the original order was no longer a special order/backorder.
The special order alerts, Stale Purchase Order (IC-STLPO) and Stale Transfer (IC-STLTR), which are raised if special order records remain in POSUGG or ICSTRN suggested files for too long, were expanded to also include checking the BCC for stale special order records. The record which generated the alert could be in the POSUGG file (for PO), the ICSTRN file (for TR) or now, the BCC (Procurements for stale PO, Transfers for stale TR).
The Commit Backorder (SOR210) program has been modified to check for conflicts with the BCC. If tied orders exist in the BCC or the Override check box is selected for the BCC line, the commit quantity will not be committed by running this report. At the end of the report, a new section lists all orders which would have been committed but had a conflict with the BCC. Detail information is provided so that the conflicting line(s) in the BCC can be addressed as needed.
On the Buyers Control Center (POE400) main screen, the Change ARP Filters button label was modified to Change ARP Buys. The change was to clarify the functionality of the button. Click Change ARP Buys to modify what is included (what to buy) in the Lines display for each individual line. On the Buyers Control Center Detail (POE405) screen, a frame title, Display Filters, was added to the check boxes to further clarify that the use of these check boxes does not change the "Buy" column values. These check boxes are filters only to refine which detail lines are visible.
An additional message was added to the window displayed when you click Create PO or Create Transfer. If you have filtered the visible lines (by changes in the Display Filters check boxes), an additional message is displayed alerting you that all detail lines marked 'buy' will be included, even if the line are not visible.
The Customer Price List was printing the Quantity Break pricing without the ‘Q’ indication that the quantity break applies. The Report Formatter and code were updated to correct the print out.
A new field, Allowance Return Code, was added to CRS F/M (SOF890). The Allowance Return Code is the value to use on the second allowance type credit memo that gives the credit for goods that were waiting for vendor approval.
When creating a CRS document, the replacement order cost was treated as a cost override when the sales order is created. Confirming the sales order did not pick up the current warehouse/item cost. The sales order should be defaulting to current warehouse cost unless the option to use past invoice cost was selected.
In FACTS 9.1.1, you can specify a replacement cost to use as a cost override when the sales order is created. In Customer Returns Line Entry (SOE811), the Customer Replacement section was now includes two new prompts. An Override Cost check box was added and when checked, a Replacement Cost prompt is available to specify the replacement cost to use when creating the sales order.
Note: Leaving the Override Cost check box "unchecked" allows the cost to be processed 'as normal' (including changing the cost during confirmation if set up to do so), and keeps the Replacement Cost prompt disabled.
Previously in Quote Entry, the credit check routine was using the quote total amount (the extended amount on the screen) for processing. Code changes in FACTS 9.1.1 now use the amount being converted to an order for the credit check routine. Additionally, the button labels were updated from "Orders" to "Toggle Orders Flag" and from "Contracts" to "Toggle Contracts Flag” to clarify their use.
To accommodate security limitations and requirements, specifically for applications that must prevent code injection threats, we have introduced the ability to limit the valid characters for specific fields in FACTS.
In System Control F/M (SMF950), a new Default Allowed Characters prompt is available to specify the default list of allowed characters for controlled fields, other than space, 0-9, A-Z, and a-z. The list applies to all data classes that are set using the new prompts to Limit Characters and Use Defaults in Data Class Control Setup (SME640). (Non-controlled fields and data classes allow all characters.) You can override this list using the new prompts in Data Class Control Setup.
These new prompts are available in Data Class Control Setup (SME640).
| Prompt | Definition |
|---|---|
| Limit Characters |
If checked, all places in FACTS that allow entry of this data class will verify that only the indicated allowed characters are entered. |
| Allow All Alpha/Num | Defaults to checked. This applies to the space, the digits from 0-9, and all upper-case and lower-case letters. When checked, all of those characters are allowed, and these values cannot be entered in the “Allowed” field because they are already known to be allowed. If Allow All Alpha/Num prompt is unchecked, you can enter any of these characters that are allowed in the “Allowed” field. For example, if you only want the digits 0-9 to be allowed, you can set Allow All Alpha/Num to unchecked (No), and enter ‘0123456789’ in the Allowed field. |
| Use Defaults |
The default list of allowed characters from System Control F/M is displayed next to this field. If that default list is adequate, check the box. The allowed characters will be that list in addition to all alpha/numeric characters if that option is selected. |
| Allowed |
If you are not using the default list from System Control F/M, this prompt is enabled. Specify the allowed characters for this data class. If Allow All Alpha/Num is checked, you cannot enter the standard alpha/numeric characters in this field because they are all allowed. If you leave this prompt blank, no special characters will be allowed in this data class. |
In Data Class Control Setup, when editing a record and Limit Characters is checked, if you change any of the settings related to which characters are allowed, FACTS checks all of the existing data to ensure that no existing data violates the new settings.
If violations are not found in existing data, the changes are saved, and you can continue. If there are violations, they will be displayed. You must use the Generic Data Changer (SMU940) to change the offending data before you can make the requested change.
To resolve special characters issues
1 Copy the contents of the Special Characters Issues list to a document editor of your choice, such as Notepad.
2 Click SM>File Maintenaces> Generic Data Changer (SMU940).
3 Follow the instructions for the Generic Data Changer to change all of the entries in the list to acceptable values.
4 Then return to Data Class Control Setup to make the changes to allowed characters.
Due to the menu architecture where programs are launched as "stand alone" screen, processing for the Data Dictionary Update encounters several busy files for SM because the menu from which it is launched persists as a separate process with open global channels. You must go back and close the Main Menu window to complete the update.
As of 9.1.1, the API Polling program, SMU954, may not be run more than one time. If it is started while another copy is already running, an entry will be made to the APIPOLL.LOG file indicating that it cannot be run more than once, and the PxPlus session will terminate.
Previously SMU954 was responsible for two major processing: handling incoming API Polling directory entries and launching background processes. This was problematic because if an API crashed, it would take SMU954 out with it. There was inefficiency as well, which could impact launching background processes. At 9.1.1, the monitoring of the API polling directory was offloaded to a new background process code, A, which is run in BKC101. SMU954 is now only responsible for launching background processes.
If BKC101 fails with an error processing an API, SMU954 will simply restart it, just like any other background process. Additionally, API polling directory entries will be much faster when processing multiple entries.
These hookpoints are impacted by this change:
SMU95E;create_global_objects is replaced by BKC10B;create_global_objects
SMU95E;pre_clean_up_channels is replaced by BKC10B;pre_clean_up_channels
Prior to FACTS 9.1.1, a recurring error in the API Polling processor, SMU954, generated a constant flow of RaiseAlerts API records that never stop and fill the API polling directories. This issue has been corrected.
The "Email Password" fields in the System Control F/M in Company Control F/M program were encrypted so that the user sees only asterisks during entry, and the value saved to the files will be encrypted/decrypted as needed.
After ten minutes of inactivity on the FACTS sign-in screen, the sign-in screen will terminate. There is no option to change the # of minutes or to turn off this feature.