SA Administrator Options - System - General field descriptions

Contact and Activity Manager

Create CAM Activities (Instead of CM Activities)

Use this operation with Corporate Assistant. If you create Customer Marketing activities for Corporate Assistant events, select this option for Corporate Assistant to create activities in Contact and Activity Manager instead of Customer Marketing.

Interface to Customers from CM Prospects

Select this option to link a prospect record to a customer record. Sales Prospect Setup updates the customer address information in Customer Setup when changes are made to the corresponding prospect record. Each prospect record may contain a company number and customer number linking it directly to a customer. If a link is established, any changes to the prospect’s address or other fields automatically update the customer’s record and vice versa.

For example, if a change is made to the Prospect Name on the Sales Prospect Setup record, and no Lookup Name is defined in the associated Customer Setup record, the Lookup Name is updated with the first 15 characters of the Prospect Name.

Lookups

Disable Auto Wildcard Usage for Keyword Lookup Keys Field and Search Fields

Select this option to disable wildcard usage for all free-form filters and the keyword search fields. For example, select this option if you do not want to use automated wildcards in any keyword lookup. Automated wildcards are also called masking lookups. These are wildcard characters that are substituted for actual characters in a lookup on product records. You can also use an asterisk at the end of a lookup word. If you disable automated wildcards, asterisks that you specify in any key lookup fields are not modified.

For example, if this option is selected, when you specify ta ex in a Product field with a lookup, records are returned that begin with ta and ex, such as tap extension or tap brass extension.

Note: In the Keyword field in a product look up, the order does not matter. You can specify ex ta and tap extension would be a valid value.

If you clear this option, the search is for an exact match.

Disable Auto Wildcard Usage for Keyword Lookup Search Fields With a Lookup Button

Keyword lookup functionality for the primary master data lookups uses wildcards on all search criteria filters. This occurs even when the filter should be an exact match. This is because the value is known value or there are lookup capabilities. Due to the wildcard usage, a query can take several seconds, instead of milliseconds, depending on the size of the database. Use this option to disable the automatic wild card creation for these lookups to improve performance. The option is selected by default.

Maximum Record Count for Keyword Lookups

Specify the number of records to return as a result of a keyword search. The higher the number of records, the longer the search may take.

Commerce Catalog / Storefront

Interface To Commerce Catalog: Select this option if you are integrating Distribution SX.e to Infor Storefront and are using the Commerce Catalog. This option indicates that recordsync records should be created for the data load.
Interface ICSC Records: Select this option to send existing catalog records from Product Catalog Setup to the Storefront Commerce Catalog during the data load.
Note: This option is available only in your first operating company in Distribution SX.e. This setting is applied to the same Administrator Option setting for all other companies.
URL: Specify the URL to your Storefront instance.

Dropbox

Interface To Dropbox: Select this option to enable users to send reports that are processed through Report Scheduler to Dropbox, a secure file hosting service that users install on their personal computers.

System

Use Advanced Polling Interface Logic for Designated Service Interface Calls

Select this option to implement batch call processing in functions that process large transaction sets. Batch call processing allows Service Interface calls to complete and return data outside of the 1-minute system constraint time frame.

As the batch process runs, a poller is initiated that tracks the status of the batch call using a database table that is updated as the batch process progresses. This status can be requested, in process,completed successfully, or completed with errors. If there are errors, a message is displayed to the screen with the specific error. When the status is completed successfully or completed with errors, the poller stops for that specific call and processing continues as normal.

After you select the Use Advanced Polling Interface Logic for Designated Service Interface Calls option, you can choose the service calls to activate for the advanced polling batch process in the Available Advanced Polling Calls list. Services calls are available for Customer Cash Receipt Entry, PD Mass Maintenance Entry, Sales Order Inquiry, Sales Order Entry, Purchase Receipt of Inventory Entry, Transfer Receipt of Inventory Entry, and Transfer Shipping Entry.

If the Use Advanced Polling Interface Logic for Designated Service Interface Calls option is selected, and no calls are selected in the Available Advanced Polling Calls list, batch processing is enabled for all calls in the list. If the option is selected, and you select any calls in the list, batch processing is enabled for the selected calls only.

If the option is not selected, batch call processing is not enabled for any service calls. If you uncheck the option after selecting service calls in the list, those calls remain selected. This is useful for disabling advanced polling/batch processing temporarily. The selected calls remain selected if you enable the option at a later date.

Other functions' transaction processing Service Interface calls are being reviewed by Infor to determine where this batch call process can be enabled. We recommend you review the Available Advanced Polling Calls list periodically or as part of troubleshooting transaction set timeout errors.

The Rdclean utility reviews any orphaned batch process records that remain in the database more than two days after the process is completed. Log records are written to the rptsch.mmddyyy.log file as batchcallprocess records, and can be used for debugging, if necessary.

You can configure a business rule, RequestPollingInterval, in SA Business Rule Setup to override the 5-second interval between polling the batch process. You can set a shorter interval to require the poller to check the batch process sooner than 5 seconds. This is useful if a service call normally can complete in a short amount of time, under the 5-second polling time. If the business rule is enabled for a time under 5 seconds, and you run a process where a large set of data is processed, the batch process is run more frequently, but you do not experience timeout issues.

Use Client Time Zone to Load Date/Time on System Records

Select this option to create system records during report processing using the local date and time of the user's client system, rather than the server date and time.

When selected, the time zone is obtained from the user's Windows' session Time Zone. This Time Zone is stored as an offset of Universal Time Coordinated (UTC) time, and factors in Daylight Savings Time. For example, a user working in Denver, CO has a Windows Time Zone offset for Mountain Standard Time, or -7:00 hours. If UTC time is 17:00, MST time is 10:00. (You can select a setting in the Windows Date/Time Settings to automatically adjust for daylight savings time.)

Using the Windows Time Zone, the user’s SA Operator Setup record is updated with their Client Time Zone Offset. This is updated each time they sign in to their client system. If Daylight Savings Time (DST) applies in the user's locality, the DST offset is recorded on the user's SA Operator Setup record so that the correct date and time is used. When the user runs a report that creates transactions in Distribution SX.e that store a date and time, the Client Time Zone Offset is included on the transaction record.

Transactions created before you select the new option are not changed to reflect the client date and time zone.

Note: This time zone offset relies upon your Windows system time zone. TWL RF functions running on handheld devices do not use a Windows-based client and always record the date and time as the server time.