Resources for Sage X3 Users

A feature of fixed assets that is not used often is the Fixed Asset Group.  Setting up and managing fixed assets by group will ease data entry and provide more granular financial tracking by asset type.  Read this blog post to learn how to configure fixed asset groups and assign them to your fixed assets. STEP 1 Create a new GL account for Fixed Assets, mark the checkboxes ‘Fixed Assets Tracking’ and ‘Expense Creation’. STEP 2 Create the FA Accounting code accordingly. It is not necessary to give these new codes names similar to the GL account’s name, but it helps. To use these FA Group Accounting Codes, X3 FA must have a ‘FA Group’ associated. This is what we’ll do in the next step.   STEP 3 Go to Setup > Fixed assets > Associations.   There are two main groups in these associations—Assets or Expenses. We’ll use Assets. Then click on Enter Values: STEP 4 Here we’ll create the Value 15220. Click on ‘New’: In the Value field, enter the 15220 Acc Code just created, or look it up from the list with the magnifying glass: STEP 5 The next step is to choose the depreciation method, along with the duration in years. After that, you’ll be all set to create a new asset or to capitalize an expense going to this asset group, which in turn is associated with the 15220 account: For more information on creating a Fixed Asset Group Association in Sage X3, please contact us.

When entering a transaction in Sage X3, you may occasionally receive the message “indefinite period or processing prohibited on this date”. PROBLEM This error message is displayed when the record allocation date is within an accounting period or stock status that has already been closed. Note: The screenshots in the example are from an NT Quality Control Record but the approach applies to all inventory allocation transactions where this message may appear.   RESOLUTION If you encounter this error, exit out of the transaction (in this case, the Quality Control Record) and then re-enter. There are two possible solutions to resolve the error: Solution Option 1 – if you need to edit a field (see screenshot below) In a field on the line, access a field that allows entry.  In this case, we use the Status field. Enter a value.  In this case, we have entered value “A” but you should enter whatever Status you are trying to change the stock to. Press the TAB key. This will automatically update the Allocation date to today’s date. Proceed with the transaction as normal, it will now work correctly. Solution Option 2 – if you do not need to edit a field (see screenshot below) Double click in in the Allocation date field and it will change to today’s date. Proceed with the transaction as normal, it will now work correctly. Should you have any additional questions about how to resolve the “indefinite period or process prohibited” message in Sage X3, please contact us.

Effective July 1, 2022, Colorado imposed a retail delivery fee on deliveries made by motor vehicle to locations in Colorado. The fee applies to all deliveries with at least one item of tangible personal property subject to state sales or use tax. The retailer or marketplace facilitator that collects the sales or use tax on the tangible personal property sold and delivered, including delivery by a third party, is liable to collect and remit the retail delivery fee. In this blog post, we will explain how to set up a Colorado Retail Delivery Fee calculation with Avalara for Sage X3. Setup Miscellaneous Table 203 Go to Setup > General Parameters > Miscellaneous tables Search for table 203 in the left list Add Code OF400000 and description Save Non-Stock Product Setup Set up a non-stock product for this fee, with the OF40000 tax code: Navigate to Common Data > Products > Products Press New Select category for non-stock product Enter Product code (optional if product sequence exists) Enter Description Stock Management set to No Management Scroll to Financials Enter Accounting code Select Tax level 1 applicable Enter the SST tax code (OF400000)   Sales Price List Setup To allow automatic insertion of the Colorado Delivery Fee product on the sales order lines we will set up a price list with free product on the match of State. Additional conditions can be applied based on the company’s needs. Navigate to Setup > Sales > Price List > Setup Press New Enter T60 or any other code desired Set CO Delivery Fee as description and check active Set priority to 35 (or other as needed) Under Price list type select grouped Under Customers select Outside group Under reason select 5 Enter criteria as follows on the screenshot below Click into the Price/Free tab under Sales Pricing Setup Under Price Processing select no Price – / + tax select exclude and under Price/Quantity select Net Price bands Under conversion – / + tax select no, under Unit conversion select Yes, under Currency conversion select No Under Free products select the Order total option, select Threshold under Free type Create and validate Create a Sales Price list Navigate to Sales > Price list > Price list entry Select price list entry T60: CO Delivery Fee Press New + Set Subdivision (State) to CO in the table below For Tax level select the TAX (this will depend on the tax setup of the company) Set currency to USD Set SAL to EA (same as the Colorado Fee Product created) Set Max amt to 1,000,000 Set Minimum free to 1.00 Enter code CORDF (Colorado Fee Product created) under Free product Create Price List: When entering a sales order Sage X3 automatically adds the Colorado Retail Delivery Fee product to any order shipping to Colorado state and Avalara calculates the Retail Delivery Fee accordingly. If you have additional questions about how to set up the Colorado Delivery Fee calculation, please contact us. For more information about the Retail Delivery Fee, please visit the Colorado Department of Revenue.

Do you want your Sage X3 ERP to better represent your brand? Would you like to see your company logo or change the background color your users see when logging in to Sage X3? Before we begin, it’s important that we backup the files we intend to modify. If you make an error while editing the files, you could make it impossible for users to access the system. You should always avoid making changes to a live environment. For this example, we’re assuming you’re logged on to the Syracuse Server. The background image is located in directory “SYRACUSE_HOMEsyracusebinnode_modules@sagesyracuse-libpublicauthimages” and is named “background.jpg”.  To change the background image, simply replace the “background.jpg” file with your own file. For best results, try to keep the new image similar in size. The original image size is 1080 x 608 pixels. In addition to changing the background image, you can also change the color property of the background element. If you look at “Syracuse_HOMEsyracusebinnode_modules@sagesyracuse-libpublicauthlogin.css”, you can change the background color in the .container section: Alternatively you can comment out the background-color section with the usual css /* */ format: Notes: Whenever you patch or upgrade the Syracuse Server it is highly likely that the CSS files you edited above will be overwritten. Therefore, it’s important to add a step to the end of your process documentation to remind yourself (and others) to replace the CSS file with the revised version. You may need to force a full-cache refresh by pressing CTRL + F5 (most browsers) for these changes to show up. Just to be clear, the steps described in this blog post are not officially supported by Sage. If you have any questions about customizing the login page for Sage X3, or any other questions, please contact us. Portions of this blog post come from a discussion on Sage City from July 2022.

3Gtms and FreightWaves discuss complexities facing 3PLs and explore today’s toughest 3PL and supply chain challenges. To support the increase in demand and ensure customer satisfaction, 3PLs need fast, reliable, and highly advanced systems to allow for shipping high volume at a rapid pace without driving up costs. A recent survey by 3PL Central found that 85% of third-party logistics (3PL) warehouses experienced volume growth in 2021. 3PLs rose to the occasion, demonstrating agility, adaptability, and flexibility while maneuvering endless obstacles – operating above capacity, supply chain latency, and labor shortages. To discuss the complexities facing 3PLs, 3Gtms hosted a webinar featuring Mark Southey, Managing Partner at Traffix, Ron Lee, Chief Product Officer at 3Gtms and FreightWaves expert, Zach Strickland, Director of Freight Market Intelligence. They explored today’s toughest 3PLs and supply chain challenges, and generously shared real-life experiences and valuable advice. The panel of experts dove into the quick and expansive pivot to eCommerce and how it has created a high demand for experts in shipping, logistics, and inventory management. 3PLs, in particular, are under tremendous pressure to perform at breakneck speed while exponentially increasing capacity and maintaining customer satisfaction. When asked about the top challenges facing 3PLs today, the panel covered everything from capacity to visibility and control, the difficulty forecasting demand, and disruptions that are causing an already volatile industry to become even more unpredictable. These complexities require 3PLs to be more agile than ever before because they need to respond to market shifts quickly. Additionally, contingency plans must be developed to deal with disruptions wherever they may occur. Echoed throughout the panel were tips and opportunities for 3PLs. Traffix’ Mark Southey stressed the importance of listening to customers and understanding their pains. “Our purpose as a 3PL is to help our customers solve problems,” shared Southey. He continued by sharing a customer story about how they successfully used live data displays to help manage and improve operations. “One of the things 3PLs need to do now, more than ever, is to manage expectations…make sure customers understand the situation you are dealing with,” shared FrieghtWaves Zach Strickland. He stressed that no one can control the market changes, but helping customers understand the situation will help avoid knee-jerk reactions. Ron Lee of 3GTMS shared the importance of iterative improvements to help everyone get to some level of predictability. When asked about opportunities for 3PLs, the panel of experts shared their experiences with modern shipping requirements. 3PLs have a chance to solve problems that their competitors are not solving, such as the intricacies of transporting “a wood stove into the Ozarks.” You can watch the webcast replay for the complete discussion here: Every Season is Peak Season: How 3PLs Meet Customers’ Growing Demands. For additional information, please contact us. NOTE: Content for this blog post was originally posted by 3Gtms, Mar 22, 2022.

Today, we’ll be clarifying a common licensing scenario where a user requires cross-functional access in Sage X3. For example, a user requires access to standard Sage X3 functions (i.e., GESPOH) and also access to the ADC Handheld (Mobile Automation – X3 Services). Therefore, the user role will require an ERPFULL badge and an ADCDIS badge. We will log into the standard Sage X3 interface with user FU05. In another browser, we’ll log in as the admin user then navigate to Administration > Usage > Session management > License usage information. As we can see, both badges are consumed. This is the intended behavior for badge consumption. Which is also referenced here: Online Help: X3 Licensing Information – badge consumption. To remedy this issue with badge consumption, being that the user is consuming both badges, our recommendation is to assign one role for ADC Mobile Automation and a separate role for the standard Sage X3 interface.  When our test user FU05 logs into the Sage X3 interface, only the badge associated with the selected role is consumed.  Also, keep in mind that Syracuse remembers the last role used for the user session. As of 2022R2 (12.0.30), if the user intends to access ADC Mobile, our recommendation would be to switch to a role that contains the ADC badge (e.g., ADCDIS) BEFORE disconnecting or logging out of the standard Sage X3 interface.  Note: The mechanism in which Syracuse stores and manages the last role used is currently under review. To avoid errors related to ADC mobile and badge consumption (KB 115500) please reference the workaround above until further notice. If you have additional questions regarding badge consumption, please visit the Sage X3 Online Help Center or contact us. NOTE: The content in this blog post was originally posted on Sage City by Darius Arnold on June 29, 2022.

For automatic deliveries, meaning deliveries being generated from a Sales Order, simply setup the SDHTYPNOR value parameter as to the desired value (i.e., SDH). Automatic Delivery Open Setup > General parameters > parameter values Expand VEN Chapter, and use the action button and click on Details, for SSD group (Shipment management rules) Set the parameter SDHTYPNOR (Standard delivery type) to your desired default delivery type Note: This parameter is used to default the delivery type and it can be set per folder, company, and site. Manual Delivery For manual deliveries (deliveries created directly from Sales > Delivery), a screen adjustment is required: Navigate to: Development > Script dictionary > Screens Open the SDH0 (Invoice management) screen and look for this field: SDHTYP Enter *”SDH” as a default value on this field Make sure to protect your change with an activity code Save and validate screen For these changes to take effect, you also need to re-validate your sales delivery entry transaction: Navigate to Setup > Sales > Entry transactions > Delivery Select your transaction from the left menu and validate Automatic Invoice For automatic invoices, meaning invoices being generated from a sales delivery, simply setup the SIVTYP value parameter as to the desired value (i.e., INV). Open Setup > General parameters > parameter values Expand VEN Chapter, and use the action button and click on Details, for INV group (Invoicing rules) Set the parameter SIVTYP to your desired default invoice type Note: This parameter is used to default the invoice type and it can be set per folder, company and site. Manual Invoice For manual invoices, invoices created directly from Sales > Invoices, a screen adjustment is required: Navigate to: Development > Script dictionary > Screens Open SIH0 (Invoice management) screen and look for this field: SIVTYP Enter *”INV” as a default value on this field Make sure to protect your change with an activity code Save and validate screen For these changes to take effect, you also need to re-validate your sales invoice entry transaction: Navigate to Setup > Sales > Entry transactions > Invoices Select your transaction from the left menu and validate For more information on setting default sales delivery and sales invoice types in Sage X3, please contact us

A new retail delivery fee is taking effect in Colorado on July 1, 2022. Retailers will have to collect the $0.27 fee every time they deliver taxable goods to a Colorado address. This will add a layer of compliance complexity for both in-state and out-of-state retailers. The $0.27 fee, which will be adjusted for inflation, applies to retailers selling taxable tangible goods for delivery by motor vehicle to Colorado consumers, no matter who owns or operates the vehicle used to make the delivery, and whether the delivery originates in Colorado or another state. Given the number of Prime (and other) delivery trucks zipping around neighborhoods daily, this could be quite lucrative for the state. In fact, it’s expected to generate $16.8 million during fiscal year 2022–23 and $18.8 million in FY 2023–24. Serious online shoppers may feel it the most; though collected and remitted by retailers, the fee is imposed on purchasers. Registration and filing requirements Businesses subject to the new retail delivery fee — i.e., any retailer registered to make taxable retail sales in Colorado that makes sales for delivery — must register to collect and remit the fee. If you don’t make any sales of taxable tangible property for delivery into Colorado, you’re not required to register. The Colorado Department of Revenue has confirmed that a person who does not have nexus and therefore does not meet the requirements to collect sales tax is also not required to collect the retail delivery fee. There’s no license or registration fee, but retailers will need to add a retail delivery fee account through the Colorado Department of Revenue. Every retailer with a retail delivery fee account will need to separately report the fee on a retail delivery fee return (form DR 1786). Returns are due every reporting period, at the same time as the state sales tax return, even if no deliveries into the state were made during that time. If there are any silver linings, it’s that only one return will be required for the entire state and electronic filing and payments options will be available. Fee must be separately stated Retailers must separately state the retail delivery fee on all customer invoices and receipts. Exceptions The fee doesn’t apply when otherwise taxable goods are delivered to a purchaser exempt from the state sales tax, such as a government or charitable organization. Likewise, the fee doesn’t apply to deliveries of nontaxable goods, including wholesale sales, so long as all the property delivered is exempt from the state sales tax. If a delivery includes both taxable and exempt goods, the delivery fee will apply. Colorado’s gone fee happy The retail delivery fee is just one of several new fees created by the enactment of Senate Bill 21-260. Others include: Electric motor vehicle registration fees Gasoline and diesel fuel fees Passenger ride fees Road usage fees Short-term vehicle rental fee “Funding highway and road construction and maintenance comes mostly from taxes on motor fuel and fees imposed on motor vehicle ownership,” says Scott Peterson, vice president of Government Relations at Avalara. “The tax on motor fuel isn’t a long-term option given the ever increasing use of electric vehicles and miles per gallon. Many states are studying and talking about how to solve the problem, but Colorado may be the first state to broaden the revenue mix to provide long-term funding. The challenge is the administrative cost it imposes on the businesses that must collect the fees.” Automating tax collection and remittance can help reduce the burden on business. If you would like to learn more about the Colorado Retail Delivery Fee (or about automating tax collection and remittance), please contact us or reach out to your Account Manager directly. You can also check out these additional resources: Colorado Retail Delivery Fee, Department of Revenue, Taxation Division Department of Revenue Colorado State Legislature NOTE: Content for this blog post was originally posted by our partners at Avalara on May 11, 2022.  

Hello readers, today’s blog post is about a sizing tool for endpoints, specifically when creating a new one. The tool will generate a “worst case scenario” for folder size based on the saved folder information in the general parameters, folder function. We are going to take a brief look at how it works and generally just bring attention to the tool in case anyone wants to figure out how many resources they might need for a specific endpoint. This information can also be used if you are asked by Sage or your partner for the size of your Sage X3 folder. Before we begin… Some quick contexts first. For this example. Let’s assume we are using an all-in-one (aka single tier) environment on AWS, and it has regulated resources. And that we are using Sage X3 2022R2 (aka 12.0.30). Remember, this tool is based on the options selected in the folder creation, so there is a good chance that your results will be different than ours. So, let’s get to it… To start, you will need to log into Sage X3 as the ADMIN account. This will ensure that we have all the proper access to take a look at the tool and associated functions. You will also need access to the X3 Reference folder. If you do not have access to the ADMIN account, any administrator account with access to Folder function (GESADS) would be preferred. First you will want to log, then change the endpoint folder to the X3 folder. Then navigate to Setup, General Parameters, Folders (GESADS). Once the function loads, you are going to want to click the New button (+ button) and start creating a new endpoint folder. Note that creating a new endpoint folder does not actually create any file folders or SQL tables until you click the Validation button. Second note, DO NOT click the Validation button after you create the endpoint folder. You have to fill out all the TABs as if you were going to create a brand-new endpoint folder. Another note: We are not going to go through creating a new folder, if you want to test and see (like we are about to) you can copy the SEED demo folder. Once you have the endpoint folder created, you want to refresh the left list and reselect the folder. Like so… If you look on the right list under OPTIONS, you will see an option called Size. Click on it. If all goes as planned, you should get a spinning wheel and a size simulation popup which will process. This may take some time depending on your current environments resources and utilization and folder creation selections. When it finishes, it will generate the following grid information. The important part of the popup is at the bottom where it shows you the total size of the calculated space (the Tables, Indexes, and Overall size appear in MB). The grid itself shows the table-by-table breakdown based on the folder options selected. Note that your numbers will most likely be different than what you see in our screenshots (unless you used the SEED folder for testing then is should be the same as above). So, based on the SEED folder (with average usage), we would expect it to be about 5GBs of space on the server (both in SQL and flat file). And that’s really it, pretty simple. Just remember, this is an estimated calculation and should not be used as exact values. Its more or less a way to have an idea of expected resource needs. If you have any additional questions about the using the folder sizing tool in Sage X3, please reach out to your Account Manager or contact us. NOTE: Content for this blog post was originally posted by Chris Hann on Sage City, June 13, 2022.