Resources for Sage X3 Users

Did you know that filtering with reporting trees can be more flexible with the use of wildcard characters? Reporting trees can already save you time but being able to use special characters in your search can further simplify the process. CREATING A REPORTING TREE In the Administration section, click on Reporting Trees in the left pane. In the left-hand corner, click on Add New Reporting Tree. In the Reporting Tree field, enter a name for the Reporting Tree. In the Filter drop-down lists, select the Global Parameters you want to use as Filters. Note: The Global Parameters you define here will be used as values when you add a Root Level Filter. Click on Confirm to finish. Note: Click on the pencil icon to edit an existing Reporting Tree or on the cross icon to delete one. ADDING A ROOT LEVEL GROUP AND A ROOT LEVEL FILTER At the group level, the filters you define are gathered on each level from the Root (Root Level Filter) into a group so that the hierarchy stays organized and easy to navigate. It is here that you create the Nodes that will compose your Reporting Tree.   In the Reporting Tree list, click on the wrench icon of the Reporting Tree you want to apply Filters to. Click on Add Root Level Group to start defining the hierarchy of your Filters: In the Description field, enter a name for this group. In the second field, click on the paste icon to retrieve the value from the Description field or enter the name you want displayed in the tab of your Excel file. Tick the Distributable checkbox to make this Node and the Filters within this group available for the Distribution. Click on Save to finish the creation of your group. Note: If needed, you can add a Group inside a Root Level Group by clicking on Add Group. Click on Add filter to add Filters to the Group you have just created: In the Description field, enter a name for this Filter. In the second field, click on the paste icon to retrieve the value from the Description field or enter the name you want to be displayed in the tab of your Excel file. Use the prompt to select a value in the Global Parameters or enter your values. You can use wildcards to filter your values. Select the Distributable option to make this Node and the Filters within this group available for the Distribution. Click on Save to finish creating your Filter. Click on Confirm to create your structure. Example: FILTERING VALUES WITH WILDCARDS Wildcards can only be used on text strings (not on numbers). Only one logic must be used at a time; for example, you cannot use 4???;[4000:4999]. ? replaces one character * replaces multiple characters ! excludes characters ; defines a list [ ] defines a range Filtering Examples: Example of filtering values Description 4000 Single value 4000;5000;6000 Single list 4* Must starts with 4 4??? Must start with 4 and have a length of 4 characters [4000:4999] Range between 4000 and 4999 !4000 Must not be 4000 !4* Must not start with 4 !4??? Must not start with 4 and must not be 4 characters long ![4000:4999] Must not be between 4000 and 4999 4???-???-10 Must start with 4, followed by – and any 3 characters, followed by – and any 3 characters, must finish with 10, and must be 11 characters long !1000;2000;7000 Must not be in the list: 1000;2000;7000 EDITING REPORTING TREE FILTER NODES In the Reporting Tree window, click on Edit: If needed, change the name of the Filter in the Description field. In the second field, change the name that will be displayed in the tab (sheet) of your Excel file. If needed, use the Prompt to select another value in the Global Parameters for the Filters. If needed, tick or untick the Distributable checkbox to make this Filter Node available or unavailable to Distribution. Click on Save to finish editing this Filter. Click on Confirm to save your changes on the server. Note: If you choose to edit a Reporting Tree Group Node, you will only be able to change the Description name and the one used in the tab (sheet) of your Excel file. Tip: You can restructure Reporting Treefilters and groups in the Manage Nodes menu by simply dragging and dropping them in the desired location. Both filters and groups can be re-ordered within their current structure level or moved to a parent or child level using this method. However, please note that a group cannot be placed within itself. For more information about creating reporting trees in Sage Enterprise Intelligence, or for any other questions about SEI, please reach out to your Account Manager or Vijay Kothari, our BI leader. Note: Content for this blog post was originally posted in the Nectari Online Help Center.

We have heard from many of our clients that you want to get together in person to talk all things Sage X3! After the great success of our New Jersey event in the Spring, Net at Work is happy to announce two more end-user groups across the US: Salt Lake City – Thursday, October 12 | 8:00AM – 6:00PM Chicago – Thursday, October 19 | 8:00AM – 6:00PM Join other Sage X3 users to share experiences and learn from each other in these in-person gatherings. ATTENDING FROM NET AT WORK Samantha Marshall, Sage Enterprise Practice Director Val Domange, Sage Enterprise Consulting Manager Juliet Lorii, Sage X3 Solutions Architect Tom Dieterle, Sr. Account Manager Pat Russo, Sr. Account Manager Jaleidy Tannenbaum, Sr. Account Manager Vijay Kothari, Sage X3 Team Manager – BI, Data Migration & Reporting Cyril Laik Chapier, Sage X3 Solution Architect  Vanessa Munoz, Sage X3 Project Manager TOPIC HIGHLIGHTS Net at Work Modules and ISVs Sage X3 Roadmap Finance Tips and Tricks Data Import/Export Tools Dashboards and Data BI Tools FULL AGENDA 8:00 to 9:00 Registration, Breakfast & Networking 9:00 to 10:30 Net at Work Modules and ISVs Review extensions and modules that Net at Work has built to deliver more value from Sage X3! Give your feedback on other modules you would like to see us develop. Sam Marshall will also present and gather feedback on what ISVs you would most like to see integrated with Sage X3. 10:00 to 10:30 Sage X3 Roadmap Join us to review the Sage X3 roadmap and provide feedback to help direct the future of X3. 10:30 to 10:45 Break 10:45 to 12:00 Finance Tips and Tricks Presented by Juliet Iorii and Vanessa Munoz, two of our X3 whisperers, learn tips and tricks for daily operations, month end, and beyond. 12:00 to 1:30 Lunch & Networking 1:30 to 2:30 Data Import/Export Tools Presented by Vijay Kothari, our BI and Data Leader, learn about the new Sage X3 Data Migration Tool options from Sage and Net at Work. 2:30 to 3:15 License Plate Numbers (LPN) in Sage X3 One of our top consultants, Cyril Laik-Chapier, will dive into the native LPN functionality and show how you can manage pallets via mobile and web functionality native to Sage X3. 3:15 to 3:30 Break 3:30 to 4:00 Dashboards and Data Juliet and Vanessa return to present dashboard personalization to help you optimize Sage X3 landing pages. 4:00 to 5:00 BI Tools Vijay returns for tips and tricks for Sage Enterprise Intelligence and Sage Data & Analytics.  Pick our brains about the best tools for your BI goals. 5:00 to 6:00 Happy Hour and Q&A MEETING LOCATIONS DoubleTree Suites by Hilton SLC Downtown 110 West 600 South Salt Lake City, Utah, 84101, USA Hilton Garden Inn Chicago OHare Airport 2930 South River Road Des Plaines, Illinois, 60018, USA REGISTER HERE: Sage X3 User Groups in Chicago & Salt Lake City Download Brochure For more information about attending an upcoming End User Group Meeting, please reach out to your Account Manager directly or contact us.

When it is time to close the period, what is the fastest way to ensure that you have posted everything and are ready to close? The Cloper Report! The Cloper Report is the pre-closing verification report. It will point out potential issues stopping you from closing such as unposted transactions,  simulated entries that need resolution, and general ledger account balances that are showing the opposite sign of what you expect. The Online Help Center’s definition of the report reads: “The CLOPER report presents in the form of a log file the list of pre-closing anomalies recorded for a legal company. This report can be printed for one or several non-closed accounting periods defined at folder level. This report can be accessed from the report menu of the group General accounting. It is also called by default from the following function: Common data > G/L accounting tables > Periods” TYPICAL ANOMALIES ON THE CLOPER REPORT & HOW TO FIX THEM All those pages!!! First Step:  1 $VERF_HAE Temporary Journal The Cloper report results can be pretty daunting when you aren’t closing periods on a regular basis (Hint! Hint!) Where to start when there is so much to clear up? Usually, the most entries on the Cloper log will start with this: “1 $VERF_HAE Temporary Journal” followed by details of the associated temporary journal. This message means that you have journals that aren’t in Final Status. You can’t close until all journals for the period are in final status. Here is an example from the Cloper log: You can go into each Journal entry under Financials, Journals and change the status there. If you have a number of entries and don’t need to review each one first, use Final validation under Financials, Current processings to move the journals to final status. You have the option to run this by period, company, journal code or document type. Once you have moved the journals to final, they will drop off of the Cloper log. 1 $VERF_SIH Customer Invoice not posted followed by the invoice number. These are Sales or BP Customer invoices that haven’t been posted. They can be posted individually from their respective entry screens or in mass. Sales invoices can be posted from Invoice/Credit memo validation under Sales, Invoices. For BP customer invoices in mass, post under A/P-A/R accounting, Invoicing, Customer BP invoice posting. After you are finished,. the journals generated will have to be moved to Final Status. 1 $VERF_PIH Invalid Supplier Invoice followed by the invoice number. This one confuses everyone with the “invalid.” This only means that the Purchase or BP Supplier invoice has not been posted. Like the customer invoices they can be posted from their data entry screens or in a batch. BP Supplier invoices can be posted in mass under A/P-A/R accounting, Invoicing, Supplier BP invoice posting. Purchase invoices can be posted in mass from Invoice validation under Purchasing, Invoices. Again, once these are posted, journals are generated which will require final validation. 1 $VERF_TMP SPDIR PI#### Entry pending validation means your invoice has been posted, but the entry hasn’t made it to the GL. Check to make sure your Accounting Tasks function is running. This is found under Usage, Batch, Server. 1 $VERF_HAE Temporary Journal: GENSM ##### On the Journal: GENSM Active simulation means its time to decide what to do with those simulated entries. In my example, I had simulated entries for a recurring transaction. Under Financials, Current processings, Recurring entries, Recurring entries, I generated Actual entries. There is an entry to have the journal created in Final or Temporary status. 1 $VERF_GAF XXXXXX Recurring journal not generated indicates there is a recurring transaction that has to be generated. Head back to Financials, Current processings, Recurring entries, Recurring entries to generate that entry for the period(s). -1 $VERF_SVC NA0111705INVBC000002 Revenue with apportionment not posted means that an invoice with apportioned revenue such as a subscription invoice has not been posted. It is posted the same way other Sales invoices are. $SLD 12100 NA008 Sign by Default Debit – Balance total Credit balance or $SLD 20100 NA056 Sign by Default Credit – Balance total Debit balance these messages indicate the balance signs on the account aren’t what is expected. If we look at the Management tab under Common data, G/L accounting tables, General, Accounts, for 12100 AR, we’ll see that Balance sign was set to Debit because we expected the accounts receivable, an asset account, to have a debit balance. This won’t stop us from closing the period, but it is probably something we want to research. 1 Error USD SITE# Balance unbalanced typically shows up on the Cloper log when the prior year has not been closed. To clear this, either go to Financials, Closing processing, Fiscal year end and perform a “hard close” or to Financials, Utilities, Closing, Year end simulation, and run the simulated close. For more information about using the Cloper report, or for any other questions about Sage X3, please contact us. NOTE: Some of the content for this blog post was originally posted on Sage City.

Sage Enterprise Intelligence is one of the most popular and well-used Business Intelligence tools for Sage X3 and related applications.  Here are their latest quarterly release notes to ensure you keep up to date with the latest features.  If you have any questions about this content or SEI generally, please reach out to your Account Manager or Vijay Kothari, our BI leader. NECTARI/SEI JULY 2023 RELEASE IS HERE In this release, we’ve added more functionality to the Formula Wizard and Drill Down Wizard in the Web Workbook. We also continue to increase customization when sharing reports and have improved how quickly users can sync large amounts of data to Nectari. Name your formula. For a quick understanding of cells that contain multiple formulas, users can customize the name of each formula using the Formula Wizard in the Web Workbook. Drill down updates. Easily remove multiple field aggregations set in your drill down profiles to view your results in a flat list without any grouping applied. Drill down to more data in the Web Workbook using fields that are Hyperlinks. Customize shared reports. To improve readability when saving or sharing individual reports sent by the scheduler, you can now customize the name of the saved or shared file. We could always customize the name for consolidated reports, but now we can also use the global and special variables for this. Better syncing. We have improved the performance when synching large amounts of data using Nectari DataSync. New AutoSimply reports. Some of the new reports include the BOM Aging Report Materials (Issuance & Returns), Manufacturing Quotations, and Transaction History. For further details, please read the full release notes or contact us.

In this blog post, we’ll show you how to implement several high-contrast filters, making Sage X3 (and any other web applications) more readable for certain users. STEPS TO IMPLEMENT HIGH CONTRAST FILTERS Open your Chrome browser. Click the vertical three dots in the upper right-hand corner and select Extensions > Visit Chrome Web Store. (Tip: you do not need to be signed in to a Google account) Search for “Contrast” Select the “High Contrast” extension Select “Add to Chrome” The “High Contrast” extension is now available in your toolbar. Click on the extension’s icon. (Tip: You may need to click on extensions (puzzle piece) in the upper right-hand corner and “pin” the extension so that it is visible in the toolbar) Choose your desired color scheme Click on “Disable” or select Shift+F11 to disable the high contrast settings EXAMPLES OF THE VARIOUS SETTINGS EXAMPLE 1: SAGE X3 PAGE BEFORE USING HIGH CONTRAST SETTINGS EXAMPLE 2: SAGE X3 PAGE AFTER USING THE “INCREASED CONTRAST” SETTING EXAMPLE 3: SAGE  X3 PAGE AFTER USING THE “GRAYSCALE” SETTING For more information about implementing high contrast filters in Sage X3, or for any other Sage X3 questions, please contact us.

You were in the middle of doing your Bank Reconciliation (BANREC) and you got up to answer the door. You return to your computer and panic sets in because in those brief seconds you were gone, your cat walked across the keyboard making random transactions cleared and closing the bank reconciliation. Unfortunately, the cat didn’t clear the correct transactions and you were left with a Variance. The Reopen option in the right box is grayed out. How are you going to reverse this mess? Relax and let’s see what we can do. The first temptation is to use Reconciliation Reversal (DEPOINTAGE). However, the DEPOINTAGE function only works with the functions RAPBAN (Bank Statement Reconciliation) and POINTAGE (Reconciliation). If you accidentally use DEPOINTAGE with BANREC, the Mark will be removed from the transaction line(s). However, if you attempt to clear the transaction in the future, you will receive a “Transaction already exists error,” referencing the Key which is the id number for the line and the Table BANKRECD. The scope of DEPOINTAGE is stated in the Online help center. If you did use DEPOINTAGE, you may have to contact your Net at Work Account Manager for assistance correcting this situation. The BANREC has to be manually reversed. To start the correction process, the statement must be reopened. If the Reopen option is grayed out, head over to Setup, Users, Users (GESAUS) and call up the User code for the person who will be authorized to reopen the BANREC statements. Under the Parameters tab, Chapter TRS/ Group AUZ, change the Value for Parameter REOPENREC to “Yes.” Click OK and Save. Logout of X3 before returning to the Bank Reconciliation. You might consider returning the parameter to “No” when you are finished for internal control purposes. Reopening prior statements will impact those statements which followed potentially changing balances and cleared items. The Reopen option in the right box will now be available. Click Reopen and the statement Status will be changed to “Open.” Now you can proceed to the Details grid to continue reconciling. There is no need to dread removing the Mark from each line. Instead. go to the Action icon (3 vertical dots) to the left of the Mark column. Once you click, note the drop down menu gives you the option of selecting “Yes to all the rest” or “No to all the rest.” This allows you to clear large chunks of transactions or all of them depending on where you start. Hopefully with this information, you will be able to forgive your cat for her journey across your keyboard and finish your bank reconciliation. Trivia: The Bank Reconciliation (BANREC) function was introduced in v6p17.             If this blog has sparked your interest in learning more about the different ways to perform a bank reconciliation, check out the Sage University instructor led session: X3 – Sage X3 – Introduction to Bank Reconciliation.  After taking the class, you will: Understand the different options available for performing a bank reconciliation. Understand how to clear transactions and manually enter missing transactions. Understand how to import bank transactions as well as match and reconcile the imported transactions. Understand bank formats and segments with a focus on the BAI2 format. For more information about reversing the bank reconciliation in Sage X3, or for any other Sage X3 questions, please contact us. NOTE: Content for this blog post was originally posted on Sage City, July 31, 2023.

Sage product migration paths have been created as addons to the current Sage Data Migration Tool (Sage DMT). These product migration paths assist customers moving from Sage 500 and Sage 300 to Sage X3. The product migration paths give customers views to extract data eliminating the need to understand source data structures, and the need to create import files. With the click of a button, the tool enables automatic importing and mapping of data to the Sage X3 templates. To gain access to the templates you must complete both the Sage Data Migration Toolkit and the Sage 500 or Sage 300 Data Migration Toolkit eLearning courses. Once completed, you will receive access to the Sage Implementation Resources Sage City site which contains: The Sage Data Migration Tool A library of Sage X3 compatible import templates to be used throughout your implementation Documentation explaining the tool You’ll also have access to community forums to share, access, and discuss best practices and provide feedback with your peers. This feedback will contribute towards the continuous improvement of the toolkit and methodology. To learn more about the Sage Data Migration Tool click here. Or, for more information about this or any other Sage X3 question, please contact us. NOTE: This content was originally posted on Sage City July 7, 2023.

Did you know that you can open Sage X3 from external applications? In this blog post, we will show you how you can call Sage X3 (using the code below) and open the application to a specific record. The user doing the call will need Sage X3 security.  If the user is not currently logged in, they will be prompted to log in and a badge will be consumed. XXX = Your Sage X3 URL which may include the port Folder ID = Your specific folder, e.g., LIVE, PROD, etc. Function = Valid Sage X3 function such as: Sales Order (GESSOH) Purchase Order (GESPOH) Customer (GESBPC) Product (GESITM), etc. Object = The object that correlates to your function. For example: Sales Order (SOH) Purchase Order (POH) Customer (BPC) Product (ITM), etc. Record = The actual record you want to open such as: Sales Order number Purchase Order number Customer Code Product ID An alternate method for calling Sage X3 is to specify the entry transaction. This will avoid the entry transaction pop-up selection that you would receive in the above call. In this case you are not specifying the object but instead are using the entry transaction (ALL, STD, etc..) followed by a 2 instead of a 1. For more information on calling Sage X3 from external applications, or for any other Sage X3 questions, please contact us.

The 2023 R1 release of Sage X3 has been available since June 1, 2023 and today we’re sharing some of the enhancements made in Mobile Automation. Sage continues to invest heavily in the Mobile Automation modules of Sage X3 with loads of new features in the last several releases including: Container receipts LPNs on the fly Product pictures Sound options This feature in the Purchase receipt transaction definitely caught our eye.  It is now possible to read data contained in a GS1 composite barcode, QR code, or Datamatrix.  In one scan, several product data fields can be filled. The AI codes handled currently are: 01-Global Trade Item Number GTIN), 10-Batch or Lot Number, 17-Expiration Date, 21-Serial Number. In the purchase receipt, Sage X3 will manage: = GTIN (Global Trade Item Number) (10) = Lot/batch number (17) = Expiration date (21) = Serial number New field in Product to contain data: Now in the Mobile Automation Receipt, on the product field, the operator scanned the GS1.  The system retrieves all the contained data and populates only the product value on the field product. When the operator progresses to the next details page, the system populates automatically serial number and lot extracted from GS1.  The operator enters only the quantity and stock characteristics (status) to receive. The interface shows much more detail now than with the older technology. Here we see some other features of the new UI – some-easier-to-use Stock change enhancements: And, the product picture!  For now, showing in the view functions.  Might be nice to have this in other transactions too for the operators to feel more confident they are moving and working with the right products. For more information on Sage X3 2023 R1, or any other Sage X3 questions, please contact us.