When an ARCUST record was removed, the corresponding Corporate Group customer was not removed. In IO.ARCUST, changes were added to DO for ARCUST for "pre remove code" and "post remove code".
A new background process, System Data Updater (S3 – BKC609), was added to FACTS 9.1.0. The purpose of this background process is to make various direct updates to the FACTS data. Initially, the program updates the status of expired quotes once they are expired, though other data will be added in the future. By default, S3 is run at daily 12:30 AM.
The PriceAvailability extended output xml was enhanced to include the next PO date and the next PO quantity when sending to Storefront.
A new API was created for item interchanges.
The request looks like this:
<RequestBatch ConsumerKey="{value}" DateTime="" Language="" Password="{value}" SerialID="">
<Request Company="{value}" RequestID="ItemInterchanges" SerialID="">
<ItemNum>{value}</ItemNum>
</Request>
</RequestBatch>
ItemNum can be left blank or excluded to retrieve all item interchanges for all item.
If ItemNum is included, only the item interchanges for that specific item will be included.
The response looks like this:
<ResponseBatch ConsumerKey="{value}" Language="en" DateTime="{value}" SerialID="">
<Response RequestID="ItemInterchanges" Company="{value}" SerialID="">
<ItemInterchange>
<Interchange>100 </Interchange>
<ItemNum>I100 </ItemNum>
</ItemInterchange>
<ItemInterchange>
<Interchange>12345 </Interchange>
<ItemNum>I100 </ItemNum>
</ItemInterchange>
</Response>
</ResponseBatch>
Where <ItemInterchange> will be repeated for each interchange. If no interchanges exist, there will be no <ItemInterchange> nodes.
The X in the top right corner of the FACTS program windows now acts as a program close in most programs. When clicked, the X acts as a cancel/backup/Done/Exit/Close/F4, where those functions are available. If a cancel or backup or Done/Exit/Close is not available, clicking the X will not do anything.
In the 9.1 release FACTS has a new main menu design and launcher process. All programs are launched. This minimizes the impact on global variable usage.
In SMU200, the entire user interface is now metadata and the code is not protected. The launch program, SMU201, is the argument while CS-LAUNCH is actually the initial program.
The new FACTS menu system contains these components.
A header ribbon containing the system date and time and three drop-downs: Communication, which contains Message and Phone Message programs to check email and phone messages,
My Alerts which accesses the Alert Control Center (ACC) to review, respond to, or dismiss (delete) alerts specifically tied to a user,
and User name, which contains a menu with these options.
|
Option |
Action |
|---|---|
|
User Preferences
|
Accesses User Preferences F/M (SMF440) to specify user preferences for each system user. These settings are derived from User Code F/M and other FACTS programs that provide default information for FACTS companies, users, and locations. Each user can modify their own settings using this program. |
|
Change Active Profile
|
Use this screen to select a different user profile. You can set up multiple profiles with different defaults for warehouse, printer, etc. Then, if you need to change from working in warehouse 01 to warehouse 02, you can change the active profile and all of the default values will change. You do not need to have multiple logins to get different default values. The active profile is displayed when you enter this program. Whenever you change your active profile, all of the global default variables will be reset. If no default warehouse, department or branch is set in your active profile then it will be taken from the location record, if one is set up.
|
|
Profile Maintenance
|
Accesses User Profile F/M where you can add, edit and delete profile records. Upon returning, the last profile that was edited will be compared to the active profile and if different, FACTS displays a message so you can indicate if the active profile should be changed to this one.
|
|
Set FACTS Date
|
Accesses Set FACTS Date (SMU120) to set the system date for your FACTS' terminal. Usually, the system date is already set when you start up the system. If for some reason the date is incorrect, or for example, you need to set the date back a day to finish up yesterday’s work, the date can be changed. To set the date, specify the New Date. If the day is set more than three days from the current date a warning is given, but the day is still set to its new value. The current system date and time are displayed. Check the Use This Date check box to set the FACTS system time to the value you specified. Click OK for the new date to take effect. When the date is changed, it will be displayed in the upper left portion of the FACTS Main screen and surrounded by asterisks (***). The date change lasts only for the session the FACTS user is logged into. |
|
Change FACTS Company
|
Accesses Change Company (SMU200) to change from working in one company to working in another. The Change Company (SMU200) program search now only shows the ones the user can access. Multiple companies can be set up in the FACTS system. However, you can work only in one specific company at a time. To switch from working in one company to another, the Change Company can be used at any time as long as you are authorized to work in the new company. To change companies, specify the company code to begin working in. The current company number and name appear at the top of the screen. Specify Yes or No to indicate whether to change companies (from current company to new). If you specify Yes (and you have proper authorization), the company is changed and the program returns to the menu. This option is only available if the FACTS Date Change check box is checked in User Code F/M (SMF410). |
|
Help
|
Displays options for the About menu for FACTS and the Infor Copyright message. Click Help>About Infor ERP FACTS to see the FACTS version you are running as well as support, licensing, and workstation information. |
|
Sign Off
|
Logs you out of the system. |
Below the header ribbon is the start-up menu location, the Main menu tab if the Allow Main Menu check box is checked, and an optional Primary menu tab if the Primary Menu prompt is specified on the Menu Setup tab of User Code F/M (SMF410).
Modules and drop-down menus are displayed on the main screen. The menu contains is drop-down modules on left side. The right side of the menu has drag and drop capability to place frequently used programs directly on the front of the main menu panel.
The panel and main screen enable you to open and close the FACTS module menu trees that contain sub menus for each module.
When you first log into FACTS, the navigation panel displays the master menu or, if your System Administrator created one, a customized start-up menu
Double click on a plus-sign (+) menu selection in the panel to see any available sub-menus. If the selection links to another menu, that sub-menu displays to the right in the main screen. However, if the menu selection links to a program (entry, file maintenance, report or inquiry), nothing appears in the main screen.
If you double click on a selection in the navigation panel, two things can occur:
If the selection links to a program, the program opens.
If the selection links to another menu, the menu appears in the navigation panel, taking the place of the previous menu. Depending on which selection is highlighted, another menu can appear in the main screen or the screen can remain blank.
Programs and sub-menus can be deleted from the Main menu by highlighting the program or submenu and pressing the Delete key. Those programs and submenus can be restored by right-clicking from the Main program menu and clicking Hidden Menu Items. On the Hidden Menu Items (SMS200) screen, highlight the lines containing the programs you want to restore to the Main menu and click Delete. At the message: Delete this line? Specify Yes and click OK. The program or submenu will be removed from the Hidden menu and returned to the Main menu.
Use the Access prompt to specify a module code or program code to display the module menu dialog box or program. For example, if you specify SME, the System Management End of Period menu dialog is displayed.
Since the FACTS menu now runs as a launcher, the system cannot handle cash drawer sign-in the same way. In FACTS 9.1.0, users should “sign-in” from the menu. The path is Sales Orders>Invoices>Counter Sales>Cash Drawer Sign-On. For users that access this program regularly, it is suggested you drag and drop it to the FACTS custom menu tab.
In Company F/M, a new setting, Color Scheme, is available to allow you to select the color scheme for FACTS. There are 11 color schemes to select from. Using the color scheme enhancement allows users to visually differentiate between FACTS companies in a system or the training company.
The FACTS/CenPOS crecit card processing integration was enhanced in the 9.1.0 release to include these features.
For CenPOS credit card processing, multi-merchant is available. In Credit Card Control (SME957), the merchant ID can be set at the company level and overridden by warehouse locations that have individual merchant ids for processing credit card transactions by warehouse.
Tokenization provides a way to securely store customer credit cards for future/repeated use. You create the token in CenPOS, and when completing card transactions, you use the token. Tokens are only valid with CenPOS, and only for the customer’s merchant account, eliminating them are targets for potential hackers.
A web services call has been implemented to retrieve all tokens for a given client ID. A list of tokens is displayed in FACTS Order Entry programs. Using a new transaction type, users can add, change or delete a token. The CenPOS integration includes multi-merchant capability. The merchant ID is at the company level but can be overridden by using a merchant ID at the warehouse level.
Users with proper authorization set on the Security tab of User Code F/M (SMF410), can manage credit card tokens for use with CenPOS credit card processing. Credit card tokens can be created for the specified customer or by ship-to location for the customer. To access the new CC Token Management (SME958) screen, the CC Token Management prompt in Customer F/M (ARF910) must be set to Customer or Ship-to, and CenPOS must be selected as the credit card processor.
The CenPOS integration uses only CenPOS-approved card readers.
Some FACTS workstation must have an active VT Bridge connection to an approved card reader. Any FACTS workstation that will be utilizing the card reader thru the VT Bridge connection of another workstation does not require the reader drivers or the CenPOS VT Bridge software. Each card reader is either connected to a workstation via USB or direct connected to your intranet via an Ethernet cable but only one workstation can establish a CenPOS VT Bridge connection with that card reader.
Set up EMV (chip) terminals in EMV Terminal FM to use EMV (chip reader) credit card terminals in FACTS. For each terminal specify the terminal ID, description and associated IP address of the FACTS workstation that controls the reader via the VT Bridge software. The IP address for the workstation is passed to the CenPOS credit card integration. When you process a credit card transaction, the EMV Terminal Search dialog box is displayed so you can select which terminal to use during credit card processing. You can also click EMV Terminal on the CenPOS Credit Card Entry screen to display the terminals for selection.
Level-3 processing provides more detailed information about the transaction, which is sent back to the buying organization via the issuing bank. By supplying this information, the transaction may qualify for significantly lower merchant transaction fee rates. In addition, a special interchange category called ‘Large Ticket Interchange,” (LTI) requires Level-3 processing.
To implement level III payment processing for CenPOS, complete this information:
Working with CenPOS and your bank, determine whether you need to use alternate unit of measure codes, then if necessary enter the required units in Unit of Measure Code F/M (ICF965) in the Alternate Unit of Measure Code. Then indicate the appropriate UM to use in Credit Card Control F/M for Level III summary data processing.
In Credit Card Control, ensure the Transmit Level III Data checkbox is selected and the Level III UOM, AR and SO Level III Summary descriptions are completed.’
A pre-authorization is a non-financial transaction that essentially reserves credit line against a credit card. This is done at order entry to verify that the card is good for the amount of the order. Pre-authorizations are usually only valid for 7 days.
When the order ships, the pre-authorization is then converted to a sale for the invoice amount. Typically a pre-authorization can be converted to a sale of up to 20% over the pre-authorization amount.
To initiate a preauthorization, from order entry Depost/Payment Entry screen, add a line and select the Pre-Auth type. Enter the estimated amount of the final invoice.
To convert a pre-authorization to a sale (force capture), from order confirmation or invoice entry payment entry, double click a preauthorization line the CenPOS ForceCapture CC Transaction screen is displayed. The Amount prompt defaults to the balance on the invoice; you can change this amount.
If any Credit Card pre-authorizations exist, an ‘alert’ message, Note: PreAuths Exist, is displayed at the bottom/left of the Footer screens of Order Entry (SOE210), Direct Invoice Entry (SOE320) and Order Confirmation (SOE310).
When running the Daily Sales Register (SOR315), if a document is converted to a back order, any existing pre-authorizations for that document are retained.
If a document is completed and deleted when the Daily Sales Register (SOR315) is run, all existing pre-authorizations for that document are deleted and the preauthorization is voided via a Web Service Call to CenPOS.
Note: The “Payments” buttons on the main screen of the SO Entry Suite programs has been removed, and it is only available now from the “Footer” screen.
Refer to the Accounts Receivable, Inventory Control, Sales Orders and System Management module sections of the release notes for program change details.
Access to Command mode has been restricted in FACTS. A new check box, Allow Command Mode, was added to the Security tab of User Code F/M (SMF410) and all setesc commands in FACTS were eliminated unless directed to a specific unique location. Check the Allow Command Mode check box to allow the user to use the 'break' key to access command mode to clear FACTS program or system errors. Infor recommends this check box is unchecked (not selected) for all users as the default. If a situation arises where the user needs to access command mode, you can temporarily change the flag, allowing the user to get to command mode, then change the setting back when they are finished.
Note: custom code should have all SETESC and SETERR commands removed unless they serve a purpose specific to that particular code.
SMC091 is the new escape handler.
SMC090 remains the error handler.
Also, the option to access BASIC from the sign-on screen has been permanently removed. Access to BASIC remains on the system install menu, and it is recommended that you apply a password to the system install menu.
Because the escape handler is always active, it will be triggered from all running code, including “Q&D” utilities, etc.
A new metadata File, SMPGMB – Program Break Options, and an entry program to populate it, Program Break Options Setup (SME022) were added to FACTS 9.1.0. The program is located on the META menu. This controls how the interrupt and error handling functions work in 9.1.
There are two options you can set in this program.
Option A only impacts the escape handler. It indicates this is a report/print/update program that should allow the use of the break key to cancel the report/print entirely at any time during that program’s execution. This is similar to allowing the old “F4-END” from the 9710 block. This is exclusive, meaning no program allows this unless it is setup here with the A option.
Typically reports have a main “0” overlay and sequential overlays following them. The typical implementation would be that the “0” overlay not be entered in SME022 unless it also does report processing. This is because the user can always just return to the menu from the “0” overlay, so there’s no need for the Break/Cancel option.
Some reports also have optional updates. Traditionally the print and update portions are done in different overlay programs. The first sequential overlay that has any update code, and all subsequent overlays should NOT be included in Option A. This is a change because if a single overlay has both a print loop and an update loop, you could previously control the SETESC such that the user could stop the report during the print loop, but not during the update loop. Now the entire program either allows abort or doesn’t.
Option X only impacts the error handler. It indicates this is a program that should disallow the user from canceling out of an error within this program. This is similar to the old functionality of setting Z8$=”**” in the 9810 routine. All programs allow canceling from an error unless it is setup here with the X option.
Typically this applies to the update portions of reports and to critical programs that users should not be able easily to stop if an error is encountered.
Only programs that need to have one of these options set should be added to Program Break Options Setup.
The error handler has been improved substantially at 9.1. It uses a new graphical user interface.
SMERRS now includes the full program stack at the time of the error.
SMERRI is a new file that holds a screen shot of the user’s screen when the error occurred. Note that the screen image could potentially include sensitive information, so only authorized users should be given access to the System Error Inquiry (SMI650) program, described later.
A new alert, Error Alert (Alert Code: ERROR), is called/recorded when an error occurs in FACTS. You can access the Alert Control Center to view and optionally dismiss this alert. The Error alert is sent to provide visibility that an error occurred and the error can be viewed in System Error Inquiry, provided the user has security to access this program.
To support IP v6 addresses, several changes were made, including:
All files that hold IP addresses were expanded for a maximum field size of 75. This includes SMIMIN and others.
Fields that previously combined an IP address and a port address in the same field have had the field split into a field for the IP address and a field for the port address.
Two new procedures were added:
- SMF950;expand_ipv6 – expands the IP address to the full address
- SMF950;compress_ipv6 – reduces the IP address to appropriate short notation
When a user types in an IP address, it can be first sent through the expand process, then through the compress process to arrive at the proper representation of the IP address.