Overview
The System Defaults module maintains system-level configuration options that impact the system's function. The settings within this module are applied at the Org Level and will, therefore, apply to all Company structures defined within Rootstock.
IMPORTANT Settings within the module should not be changed without a complete understanding of the impact. Before making any changes to this record you should consult Rootstock support and conduct thorough testing of the change in your Sandbox environment before deploying to production.
Navigation
System Defaults
Your Rootstock Consultant will create and configure the System Default record as part of the initial implementation process. Should changes be required to the configuration, click Edit and process the changes. Once the changes are processed, click Save for them to take effect. Users may be required to log out and log back in before the changes are visible in the User Interface. Below is the list of configuration options by page section with a brief explanation of the functionality.
SYDEFAULT Detail
Fields
Sydefault Name: Name of Sydefault record - usually created by the Rootstock Support Team.
Default Printed Image Row Size: Used as the default row size for printing images.
Number of lines on fulfillment page: The maximum number of lines to show on the Sales Order Fulfillment and Sales Order Fulfillment Pre-Selection pages. The Maximum the UI supports is 150.
Auto Run Fulfillment Search: When checked, it will automatically run an SO Fulfillment search when entering the Sales Order Fulfillment page if there are saved user criteria available (System Option by User – SYREG object).
Sync Item and Product Descriptions: When checked, the description of an item will be synchronized between all Item Masters, Product Masters, and SF Products tied directly to the given Inventory Item. The Engineering Item Master record is the controlling record for maintaining descriptions.
Control Item Description Access by User: When checked, only users authorized to change item descriptions may do so.
Auto Create RMA When SIW on a Case: When checked, when creating an RMA for a Shipped Serial Item under Warranty (aka Covered Item) from a Case, the RMA is added for that Covered Item Product Number.
Item Features Active: When checked, Item Features functionality within the Engineering Item Master is enabled. Item Features functionality facilitates the adding of attributes to the Engineering Item Master record, i.e., Color or Make.
Selective Issue by Location and Lot: When checked, this changes the Sales Order Fulfillment page to be more oriented for issuing Lot Items, particularly when many Lots are involved.
Use Lightning Style Sheets: Certain Rootstock Visualforce pages have been enhanced with the Salesforce Lightning Experience (LEX) Style Sheets, giving them the look of LEX when run in a Lighting environment when this feature is activated. When unchecked, the Rootstock Classic style sheets will be used when in a Lightning-enabled environment.
Workday - Auto Approve Vendor Invoices: This Workday integration - controls if the Supplier Invoice is sent as approved or not.
VAT Recognition Option: Defines the point/stage where VAT will be recognized/accounted for. Options are Upon Delivery, Upon Invoice, and Upon Payment.
NOTE When changing the VAT Recognition Option from Upon Delivery / Upon Invoice to Upon Payment, ensure that all the VAT Classes have a 'VAT Clearing Account' defined.
SYDATA Processor Start Time: Start time of SYDATA Processor.
SYDATA Processor Finish Time: Finish time of SYDATA Processor.
SOAPI Processor Start Time: Start time of SOAPI Processor.
SOAPI Processor Finish Time: Finish time of SOAPI Processor.
Use PLM Item Name as Description: If this field is checked, Rootstock ERP will populate the item description (Description on the Engineering Item and also all Inventory Items, Purchase Items, and Products associated with this Engineering Item) with the PLM Item Name during the processing of Scheduled Arena Interface. Else it will be populated with the PLM Item Description.
Schedule Date Type: Defines the Date Type for Scheduling. Options are: a) Calendar, 7-day; b) Shop Calendar.
Allow COGS Acct on Indirect/Service Item: When checked, Cost of Goods Sold Accounts may be used to procure Indirect or Service Items.
VAT Active: When checked, VAT Tax/Classification is active in this organization.
IMPORTANT Do not activate this field until Divisions and VAT Classes have been added.
Allow Turning Off FIFO: When checked, the FIFO flag may be unset on the Engineering Item Master record.
Use High Volume SO Entry UI: When checked, the SO Entry page will be used (for Add, Edit, and View modes) that supports a high volume of SO Lines.
Create Dimension Only JE for Proj-2-Proj: When checked, dimension-only Journal Entries will be created for Inventory Project Transfers (transferring from one Project to another).
Replace Mfg User Job In Use: When checked, the process is checked when the background task Replace Manufacturing User is in progress.
Default Item Unit Of Measure: When adding new Items, the predefined value (defined using the Unit of Measure program) used here will be used as the default, which can be overridden or changed.
Product Add option: This picklist field contains values S, R, and B.
Zip/Postal Code Are Not Required: When checked, Zip Codes fields are optional for all addresses throughout Rootstock objects.
Derive PO Receipt Number from Record ID: When checked, this causes the Receipt Number associated with each Purchase Order Receipt to be derived from the Salesforce assigned Record ID.
Allow Sales Order Line Tax Loc Overrides: This field activates a feature that allows a Tax Location to be specified directly on a Sales Order Line which will override the Tax Location on the Ship To Address associated with the line.
Use the Lighting POAP Headers Workbench: When checked, PO-AP Match can only be completed in the Lighting POAP Headers workbench, and access to the previous PO-AP Match Lighting and Visualforce pages will be disabled along with the SYDATA Transaction Types 'PO AP Match Using Detail', 'Close PO AP Batch', and 'Reopen PO AP Batch'. When unchecked, the Lightning POAP Headers Workbench cannot be used.
IMPORTANT User cannot uncheck this flag 'Use the Lighting POAP Headers Workbench' if one or more PO-AP Match Batches exists with the status 'Closed'.
Customers and Vendors
Fields
Allow Add of SF Acct from RS Cust & Vend: When checked, Salesforce Accounts may be auto-created as the result of creating a new Rootstock Customer/Vendor Master record if 'Salesforce Account' field is left empty. When unchecked, the field 'Salesforce Account' is required when creating new Rootstock Customer/Vendor records.
Only Use Salesforce Address on Customers: When checked, designates that addresses for Rootstock Customers are maintained on the associated Salesforce Account and not on the RS Customer Master record. Note that this feature should be used if multiple addresses are required for a given Address Type.
Only Use Salesforce Address on Vendors: When checked, designates that addresses for Rootstock Vendors are maintained on the associated Salesforce Account and not on the RS Vendor Master record. Note that this feature should be used if multiple addresses are required for a given Address Type.
Auto Create RS Customer Contact From SF: When checked, the system automatically creates a Rootstock Contact when a Salesforce Contact is created.
Auto Create SF Customer Contact From RS: When checked, the system automatically creates a Salesforce Contact when a Rootstock Contact is created.
Update RS Customer Contact From SF: When checked, the system will update the Rootstock Contact when the Salesforce Contact is updated.
Update SF Customer Contact From RS: When checked, the system will update the Salesforce Contact when the Rootstock Contact is updated.
Suppress Auto-Default of Cust Contact: When checked, rather than defaulting the Customer Contact from the Customer Master, the Contact will need to be manually selected.
Allow Customers from Accts with no Addr: When checked, the standard Customer Master 'address is mandatory' validation between the Salesforce Account and the Customer Master is disabled, and Customer Master records can be created without addresses.
Sync Terms from Rootstock to SF Account: When checked, Credit Terms will be synchronized between Rootstock Customers and Salesforce Accounts. This feature is only available for FinancialForce users.
Customer Auto-Numbering Active: When checked, when creating SF Accounts and checking the 'Rootstock Customer' checkbox, or when adding the Customer directly in Rootstock, the required Customer Number will be automatically assigned.
Last Customer Number: When 'Customer Auto Numbering Active' is checked, this field represents the last Customer Number auto-assigned. The value must be initialized when setting Customer Auto-Numbering to active.
Default Customer Class: Enter a valid Customer Class, which will be used to set various defaults when adding a new Rootstock Customer, including Customer discounts, shipping info, and credit terms. These default values can be modified on the Rootstock Customer record as necessary.
Vendor Auto-Numbering Active: When checked, the auto-numbering feature for setting the Vendor Number is active.
Last Vendor Number: When Vendor Auto-Numbering is active, this reflects the last Vendor Number assigned. The value must be initialized when setting Vendor Auto-Numbering to active.
Default Vendor Class: Enter a valid Vendor Class, which will be used to set various defaults when adding a new Rootstock Vendor, including Buyer, payment terms, freight/carrier info, and lead times. These default values can be modified on the Rootstock Vendor record as necessary.
Auto Create RS Vendor Contact From SF: When checked, the system automatically creates a Rootstock Contact when a Salesforce Contact is created.
Auto Create SF Vendor Contact From RS: When checked, the system automatically creates a Salesforce Contact when a Rootstock Contact is created.
Update SF Vendor Contact From RS: When checked, the system will update the Salesforce Contact when the Rootstock Contact is updated.
Update RS Vendor Contact From SF: When checked, the system will update the Rootstock Contact when the Salesforce Contact is updated.
Integration - General
Fields
Zenkraft Active: When checked, Zenkraft functionality is active.
Zenkraft Multi-Carrier: This setting is enabled if the Zenkraft Multi-Carrier app is installed and integrated with Rootstock.
Zenkraft MC with Custom Address Source: When interfacing Rootstock with the Zenkraft Multi-Carrier app, this field activates the Zenkraft Customer Address Source object to do the mappings between Rootstock and Zenkraft.
Payment Gateway – Order Comment 1 Source: Used when mapping Rootstock fields to Payment Gateway integrations. This will be copied from COMMENT1 in the Sales Order Header (SOHDR).
Payment Gateway – Order Comment 2 Source: Used when mapping Rootstock fields to Payment Gateway integrations. This will be copied from COMMENT2 in the Sales Order Header (SOHDR).
Payment Gateway – Inv Comment 1 Source: Used when mapping Rootstock fields to Payment Gateway integrations. This will be copied from COMMENT1 in the Sales Invoice Header (SOINV).
Payment Gateway – Inv Comment 2 Source: Used when mapping Rootstock fields to Payment Gateway integrations. This will be copied from COMMENT2 in the Sales Invoice Header (SOINV).
Run Principal API in Test Mode: When checked, will run Principal API in Test Mode.
WMS API User ID: Used when integrating WMS and to record API User ID.
WMS API Pass Phrase: Used when integrating WMS and to record API Pass Phrase.
Last PLM Import Request: When interfacing with a supported PLM product, this is the date and time of the last import requested.
Quality Interface: Identifies the integrated Quality Control system in use.
Custom PLM Field for Commodity Code: Used when integrating PLM software and mapping to Commodity Codes.
Custom PLM Field for Product Group: Used when integrating PLM software and mapping to Product Groups.
Arena User ID (Email): User ID used to access the Arena API.
Arena Access Value: Password used to access the Arena API.
Arena - Qualifying Lifecycle Phases: This field is used to identify the set of Arena Lifecycle Phases that qualify for transfer from Arena to Rootstock (listed out one per line). Leave the field blank when all Lifecycle Phases qualify to transfer from Arena to Rootstock.
QuickBooks Integration
Fields
QuickBooks Online Multi-Company Active: When checked, multiple Companies can be supported using QuickBooks Online. Otherwise, only one is supported, and the Quickbooks Online Named Credential should be configured on the System Defaults record.
QuickBooks Online Company: QuickBooks Company ID.
QuickBooks Online Token: This Token is combined with the Token Secret to validate integration from the QuickBooks website back to the Rootstock Org. This combination is required when making HTTP requests to Data Services for QuickBooks.
QuickBooks Online Token Secret: This Token Secret is combined with the Token to validate integration from the QuickBooks website back to the Rootstock Org. This combination is required when making HTTP requests to Data Services for QuickBooks.
QuickBooks Online Consumer Key: This Consumer Key is combined with the Consumer Secret to validate integration between the Rootstock Org and the QuickBooks website. This combination is required when making HTTP requests to Data Services for QuickBooks.
QuickBooks Online Consumer Key Secret: This Consumer Key Secret is combined with the Consumer Key to validate integration between the Rootstock Org and the QuickBooks website. This combination is required when making HTTP requests to Data Services for QuickBooks.
QuickBooks Timeout: The number in seconds before QuickBooks export will time out.
Quickbooks Online Named Credential: Set to the Named Credential used for connecting to the Quickbooks Online server when configured as a single Company.
QuickBooks Online Auto-Add Products: When checked, Products will be auto-added into QuickBooks.
QuickBooks Online - Send Email on Errors: When checked, emails will be sent (to the user who launched the export) when errors occur.
QuickBooks Online-Abort Export on Error: If an error is encountered during export and if this flag is TRUE then the errors will be shown in the job email. Otherwise, they will be shown in the Processing Results (SYRESULT). In either case, the export will fail if an error is encountered.
Sales Invoice Export In Use: The Accounting export process marks this checkbox when it starts. If the job is manually aborted, the check box can be unchecked to continue the export process. Otherwise, the process will uncheck the box when it has been completed.
Payables Invoice Export In Use: The Accounting export process marks this checkbox when it starts. If the job is manually aborted, the checkbox can be unchecked to continue the export process. Otherwise, the process will uncheck the box when it has been completed.
Journal Batch Export In Use: The Accounting export process marks this checkbox when it starts. If the job is manually aborted, the checkbox can be unchecked to continue the export process. Otherwise, the process will uncheck the box when it has been completed.
Suppress Cost Txn Record ID on QB Export: When checked, the Inventory Cost Transaction ID is not passed when doing a QB Export.
QB Desktop 2019 ACCNT Option: This field controls the value placed in the ACCNT column of QuickBooks 2019 export files. Account Description is the default when no value is specified.
QuickBooks Desktop 2019: This field indicates that the 2019 version of QuickBooks Desktop is active.
Plaid Integration
Fields
Plaid Client User ID: This field will store the Plaid User ID for the Org. This will be encrypted/masked data.
Plaid Client User Name: This field will store the Plaid User Name for the Org. This will be encrypted/masked data.
Plaid Create Token URL: This field will store the URL to create a plaid token.
Plaid Exchange Token URL: This field will store the URL to exchange the plaid public token.
Plaid Supported Languages: This field will store the list of languages Rootstock supports for the Org.
Supported languages: Danish ('da'),Dutch ('nl'), English ('en'), Estonian ('et'), French ('fr'), German ('de'), Italian ('it'), Latvian ('lv'), Lithuanian ('lt'), Norwegian ('no'), Polish ('pl'), Portuguese ('pt'), Romanian ('ro'), Spanish ('es'), Swedish ('sv').
Plaid Get Transactions URL: This field will store the URL needed to retrieve transactions from Plaid.
Plaid Production URL: This field will store the URL to access the Plaid Production instance.
Plaid Products: This field will store the list of Plaid products Rootstock supports. Supported Products: Auth, Transactions.
Plaid Sandbox URL: This field will store the URL to access the Plaid Sandbox instance.
Plaid Supported Country Codes: This field will store the list of countries Rootstock supports for the Org. Possible values: US, GB, ES, NL, FR, IE, CA, DE, IT, PL, DK, NO, SE, EE, LT, LV, PT, BE.
NOTE These fields will be updated by the system when the Bank Integration is activated.
Intacct Integration
Fields
Intacct User ID: The User ID for access to Intacct when exporting accounting data.
Intacct Company: Identifies the Intacct Company.
Intacct Dimension for Class: Numerical value 1-8.
Intacct Dimension for Customer: Numerical value 1-8.
Intacct Dimension for Department: Numerical value 1-8.
Intacct Dimension for Employee: Numerical value 1-8.
Export Intacct Sales Invoices as SO: When checked, Intacct Sales Invoices will be exported as Sales Orders.
Intacct Warehouse Feature Active: When checked, it indicates Intacct Warehouse Management is in use.
Intacct - Pass Company as Entity: When checked, the Rootstock Company ID will be used as an Entity (aka Dimension) in Intacct.
Intacct SO Inv Freight/Tax as Subtotals: When checked, any Freight or Tax from Rootstock SO Invoice records will be passed as a Subtotal to the Intacct SO Invoice record.
Intacct - GL Transaction Symbol: This field allows the user to override the default value of 'GJ' used in the creation of new Intacct GL Transactions created from Rootstock Cost Transactions.
Intacct User Password: Used to record the Intacct User Password.
Intacct Timeout: Intacct API call timeout in seconds. Minimum value 1, Maximum value of 120.
Intacct Dimension for Item: Numerical value 1-8.
Intacct Dimension for Location: Numerical value 1-8.
Intacct Dimension for Project: Numerical value 1-8.
Intacct Dimension for Vendor: Numerical value 1-8.
Intacct - Pass Item Number as Item in PO: When checked, the Item Number passed will be the Item on the Purchase Order.
Intacct Sales Order Transaction Type: Used to define the Intacct Sales Order Transaction Type that will be used in the integration mapping process.
Intacct Freight/PPY UOM: The Intacct interface can be given a single header level Unit of Measure when it’s the target of an invoice exported. This field holds that value. It will be something defined in Intacct (e.g., “EA”, “DZ”) – It can be left blank, and Intacct will work out the units for itself (from the line product).
Intacct Purchase Order Transaction Type: Used to define the Intacct Purchase Order Transaction Type that will be used in the integration mapping process.
Intacct PO Freight Subtotal Description: Used to define the Intacct PO Freight Description that will be used in the integration mapping process.
Intacct PO Tax Subtotal Description: Used to define the Intacct PO Tax Description that will be used in the integration mapping process.
Workday Integration
Fields
Workday User ID: The User ID for access to Workday.
Workday User Password: The user Password for access to Workday.
Workday - Export By Company: Typically set to false. Set to true if a specific batch should be scheduled independently for every Company.
Workday - Address Sync Include Email: Typically set to false. Set to true if an email should be included as part of the Customer Address.
Workday Financial Management Endpoint: Used to record the Workday Endpoint URL for Financial Management.
Workday Resource Management Endpoint: Used to record the Workday Endpoint URL for Resource Management.
Workday Revenue Management Endpoint: Used to record the Workday Endpoint URL for Revenue Management.
Accounting Seed Integration
Fields
Auto-Post AS Journal Batches: When checked, Journal batches will be automatically posted in the Accounting Seed.
Auto-Post AS Sales Invoices: When checked, Sales Invoices will be automatically posted in the Accounting Seed.
Workday - Auto Approve Vendors: If set to true, suppliers integrated into Workday will be auto-approved when created.
Auto-Post AS Payables Invoices: When checked, Payables Invoices will be automatically posted in the Accounting Seed.
Bar Code
Fields
Barcode Printing Active: When checked, Barcode Printing is activated for this Rootstock installation. When Barcode Printing is active, there are a number of reports that have options for printing both text and barcode details.
Barcode Type: When Barcode Printing is active, this field defines the barcode type to be used for printed barcode values. The default value is Code 3 of 9 ("code39") but can be changed as necessary.
Barcode Width: When Barcode Printing is active, this field defines the default barcode width used to print barcode values. The default value is '1' and can be expanded for trial and error testing to accomplish optimal barcodes for your environment.
Barcode Height: When Barcode Printing is active, this field defines the default barcode height used to print barcode values. The default value is ‘40’ and can be modified for trial and error testing to accomplish optimal barcodes for your environment.
Barcode Text Size: When Barcode Printing is active, this field defines the default barcode text size used to print barcode values. The default value is ‘12’ and can be modified for trial and error testing to accomplish optimal barcodes for your environment.
Print Text Under Barcode: When Barcode Printing is active, and this field is checked, associated text values print under the barcode.
Intermec Location Transfer Defaults
Fields
From Division: When using a mobile scanning device (currently Intermec), this value is the division that will default as the From Division for all movement transactions. The default value can be modified by the user when processing the transaction.
From Site: When using a mobile scanning device (currently Intermec), this value is the site that will default as the From Site for all movement transactions. The default value can be modified by the user when processing the transaction.
From Location ID: When using a mobile scanning device (currently Intermec), this value is the Location ID that will default as the From Location ID for all movement transactions. The default value can be modified by the user when processing the transaction.
From Location Number: When using a mobile scanning device (currently Intermec), this value is the Location Number that will default as the From Location Number for all movement transactions. The default value can be modified by the user when processing the transaction.
From Project: When using a mobile scanning device (currently Intermec), this value is the Project that will default as the From Project for all movement transactions. The default value can be modified by the user when processing the transaction.
To Division: When using a mobile scanning device (currently Intermec), this value is the division that will default as the From Division for all movement transactions. The default value can be modified by the user when processing the transaction.
To Site: When using a mobile scanning device (currently Intermec), this value is the site that will default as the From Site for all movement transactions. The default value can be modified by the user when processing the transaction.
To Location ID: When using a mobile scanning device (currently Intermec), this value is the Location ID that will default as the From Location ID for all movement transactions. The default value can be modified by the user when processing the transaction.
To Location Number: When using a mobile scanning device (currently Intermec), this value is the Location Number that will default as the From Location Number for all movement transactions. The default value can be modified by the user when processing the transaction.
To Project: When using a mobile scanning device (currently Intermec), this value is the Project that will default as the From Project for all movement transactions. The default value can be modified by the user when processing the transaction.
Form Templates
Fields
SO Picklist Email Content Option: Defines how the SO Picklist form is delivered in email dispatch. Options are 'Embed in Body', 'Attachment' or 'Both'.
Sales Invoice Email Content Option: Defines how the Sales Invoice form is delivered in email dispatch. Options are 'Embed in Body', 'Attachment' or 'Both'.
Acknowledgment Email Content Option: Defines how the Acknowledgment form is delivered in email dispatch. Options are 'Embed in Body', 'Attachment' or 'Both'.
Bill of Lading Email Content Option: Defines how the Bill of Lading form is delivered in email dispatch. Options are 'Embed in Body', 'Attachment' or 'Both'.
RMA Email Content Option: Defines how the RMA form is delivered in email dispatch. Options are 'Embed in Body', 'Attachment' or 'Both'.
Purchase Order Email Content Option: Defines how the Purchase Order form is delivered in email dispatch. Options are 'Embed in Body', 'Attachment' or 'Both'.
Packing Slip Email Content Option: Defines how the Packing Slip form is delivered in email dispatch. Options are 'Embed in Body', 'Attachment' or 'Both'.
Email Template Document Audit Active: When checked, an audit record is kept of Email Templates despatched from Rootstock to Customers/Vendors. The audit records are in the ‘Email Template Document Audit’ object.
Form Overrides
Fields
Override Form Tool - BOL: Allows for individual override of the standard forms tool for the Bill of Lading.
Override Form Tool - Packing Slip: Allows for individual override of the standard forms tool for the Packing Slip.
Override Form Tool - Purchase Order: Allows for individual override of the standard forms tool for the Purchase Order Print.
Override Form Tool - Quotation: Allows for individual override of the standard forms tool for the Quotation Print.
Override Form Tool - RMA: Allows for individual override of the standard forms tool for the RMA Form.
Override Form Tool - Sales Invoice: Allows for individual override of the standard forms tool for the Sales Invoice.
Override Form Tool - SO Picklist: Allows for individual override of the standard forms tool for the Sales Order Picklist.
Override Form Tool - WO Picklist: Allows for individual override of the standard forms tool for the Work Order Picklist.
Override Form Tool - Sales Order Ack.: Allows for individual override of the standard forms tool for the Sales Order Acknowledgement.
Override Form Tool - Sales Credit Memo: Allows for individual override of the standard forms tool for the Sales Credit Memo.
Override Form Tool - WO Traveler: Allows for individual override of the standard forms tool for the WO Traveler.
