What are the changes in Web services in Sage X3 Product Update 9 and later?

Sage X3 Business Cloud product update brought 9 with it significant changes to web services, here is an overview

  • Generic SOAP web services are based on classic clients and act exactly like it did previously

  • The license now controls the data volume consumed through web service and there is no control on the count of clients defined in the pool

  • Web services are managed within the Syracuse administration, there is no more Console configuration

  • All setups and tests of web services will now be carried out in the new Sage X3 Web methodology (You can no longer use the “old” web tester)

Entities

  • hosts (Administration, ADMINISTRATION, Servers, Hosts): Defines the number of Web Service child processes. By default this is set to 0, so it must be configured. This allows you to work with the Sage X3 web load balancer mode

  • soapClassicPools (Administration>ADMINISTRATION, Web Services, Classic SOAP pools configuration): : Defines pools, count of clients to be initialized during pool setup, maximum count of clients allowed by pool (to avoid overload)
    Note: If you set two child processes and two clients per pool, you will have four clients started. (Nb of clients=Nb of child processes*Nb of clients per child processes)

  • soapGenerics (Administration, ADMINISTRATION, Web Services, Classic SOAP Web services): Retrieve WSDL description and is the internal tester for every operation (save, read, query, delete…)

  • restWebServices (Administration, ADMINISTRATION, Web Services, Rest web services):Declares outgoing rest web services to be used from the SAFE X3 dedicated API.

  • licenseViews: (Administration, USAGE, Session management, License follow up) Allows view into Web services consumption

License Parameters

  • WSGRACELIMIT: (%) defines the oversize percentage allowed (typically 10%) if the maximum size is fixed at 1MB / day, this means that:

    • 1 MB per DAY without speed limitation

    • The next 10% (100Kb) at a lower speed

    • The web service does not respond when the 1.1 MB limit is reached

  • WSGRACESLOWDOWN: indicates the rate used to decrease the speed of the Web services when the grace limit is reached

  • WSPERIOD: determines the period on which the size limitation applies (DAY/MONTH/YEAR)

  • WSSIZELIMIT: size, in MB, of the license for the web services

Sage X3 V11 Architecture and System Requirements Guide

Hardware specifications for Sage X3 V11 and Architecture / Architectural and System Requirements Guide

Once an architecture guide is released there is no further testing to certify any updates beyond that point. The architecture guides do not get updated. To see updated information, refer to online help, preferably from the latest version of Sage X3 available.

For example, under v12, this is found by going into Technical help, Upgrade, public technical help, and Prerequisites overview. This will show updated information for v12, as well as prior versions. If you have access to other lower versions of Sage EM, the information may not be up to date, and will be titled differently, but can generally be found under the Technical help area.

v12 example screenshot (up to date as of January 9, 2019)






















Click here for downloading the Architecture guide for Sage X3 V11

What’s new in Sage 300c 2021 Product Update 3

General improvements

This product update includes the following new features and improvements in both Sage 300cloud web screens and Sage 300 classic desktop screens:

  • Improvements to bank feeds. On the Reconcile E-Statements screen:
    • When automatically reconciling transactions from a bank feed, the system now tries to match transactions in more ways than it did previously. Transactions will now match if certain information in Sage 300 is in the Comment 2field in the e-statement, even if the Comment 2 field includes additional information (for example, if the payment description in Sage 300 is Check 900 and the Comment 2 field in the e-statement is Invoice 2286 Goods – Check 900).
    • Transactions downloaded using a bank feed have a Bank Cleared Date based on your local time.

Note: In web screens, the “local” time comes from the system where Sage 300 is running, which may be different from the time on your system.

Microsoft 365 integration with Sage 300

The Sage Contact app (for viewing and managing Sage 300 customer information within Microsoft Outlook) is no longer supported.

Posted Originally on: https://www.sagecity.com/za/sage-300-south-africa/f/sage-300-south-africa-announcements-news-and-alerts/175776/what-s-new-in-sage-300c-2021-product-update-3

What to do when BI Generator is missing in excel (Terminal Server environment)

Steps to follow when the BI generator or BI tool cannot be accessed in Excel terminal server environment even though a licensed version is installed. This generally happens when the registry entry for the BI generator in Excel has not been created properly, or not present altogether.








Before you begin

This solution requires advanced knowledge of your computer’s operating system. Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Evomatiq Business Solutions LLC and Sage Software PLC are not responsible for operation issues caused by incorrectly modifying your Windows Registry.

Always create a backup of your data before proceeding with advanced solutions.

Resolution

We will have to create a registry entry manually





















  1. Create a .txt file on the desktop.
  2. Add the information below to it exactly how it is
  3. Save and change the extension to .reg
  4. Close and double click on the file to open
  5. Click yes to change the registry.

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\BIGenerator]
“Description”=”BI Generator”
“LoadBehavior”=dword:00000003
“FriendlyName”=”BI Generator”
“CommandLineSafe”=dword:00000001
“Manifest”=”C:\\Program Files (x86)\\Common Files\\\\BIGenerator\\AlchemexWizard.vsto|vstolocal”



 

Things to know before using REST APIs with Sage X3 Business Cloud

Starting in version 7 here are some things that dev teams need to keep in mind if they are going to use REST APIs to work with Sage X3 Business Cloud:

  • The Web API (REST)

    • Can be used to read elements from all modules, as Sage X3 is already providing read-only representations on most resources. Basically, if there is a representation in the Read Only Pages section, REST can be used to read the data.

    • Should be used to update data from modules that have been upgraded. Resources that you can access with the mobile client can be read and modified through the Web API.

  • For the others REST web services currently is only available for READs (i.e. the Read Only Pages).

  • Create, Update and Delete are not currently supported.

Sage X3 Life-cycle Policy

The Sage X3 Life-cycle Policy is designed to provide consistent and predictable guidelines on the availability of maintenance of Sage X3 versions. This policy document outlines how long each version of Sage X3 will be covered by maintenance support, allowing you to effectively plan your software investment and avoid any gaps in support.

  • This policy applies globally to Sage X3.
  • This policy applies to all Sage X3 versions up to and including Version 11, and Sage X3 Version 12 on wards.
  • This policy excludes solutions that are supplementary to Sage X3 such as third-party products and services, or embedded components.

What is a life-cycle policy?

A life-cycle policy formalizes a software vendors procedure of withdrawing maintenance support for software versions that are behind the latest release.

The Sage X3 life-cycle policy specifies how long maintenance support will be available for a release of Sage X3, from when the product is available for purchase to when it reaches the end of maintenance date. It is designed to provide consistent and predictable guidelines on maintenance support of Sage X3 versions throughout the life of the product. Click Sage X3 Lifecycle Policy for downloading the detailed Sage X3 product policy by Sage.

10 common supply chain challenges and ways to resolve them

As we navigate through the COVID 19 pandemic, companies have had to take a hard look at their inventory management systems. Timelines, trimming costs and smart inventory control are the hallmarks of a business with remarkable profit margins in the post COVID world.

Here are 10 most common inventory management problems that a business may face and tips on how you can solve them

  1. Need for supply chain transparency: End-to-end supply chain visibility is key to maximizing efficiencies and your future risk management efforts. Businesses must map their business processes, from concept to customer, to be in control of timelines and make more educated situational pivots.

  2. Missing the bigger picture: Data intelligence is important at every stage of your business. From marketing analytics to inventory quantities to profit margins, all information is important. Supply chain data and context is most of the times ignored as insignificant, but overlooking supply chain data is a big mistake. Make sure you’re utilizing supply chain data appropriately to make wiser business decisions.

  3. Not accounting for business disruptions: Not having pivot plans in place is a sizable risk towards running a smooth business. When the inevitable happens, you will be prepared to keep your customers from being affected. Pandemics like COVID 19 are an eventuality and as much must be factored into processes as much as possible.

  4. Choosing too many partners: Although you want to be prepared, there is such a thing as having “too many cooks in the kitchen.” Too many vendors introduce more complexities to processes. Investigate and find your right balance. Data is going to be your savior in finding the sweet spot and choosing the right partners.

  5. Going lean without supporting infrastructure: COVID 19 has forced businesses to go lean. Here is the dichotomy, lean is good, but being too lean can cause issues. Granted, going lean is desirable to save costs, however going lean without the right systems in place can cause disruptions and bottlenecks to an otherwise smooth operation. Make sure you have the right processes and systems in place to support going lean.

  6. Lack of proper security protocols: In 2021, ransom-ware & phishing attacks are an eventuality. You must have proper processes and systems in place for a) avoiding getting infections in the first place b) recover with minimum disruptions in the event of an infection. The number of businesses that we see without a coherent strategy in this department is too () high.

  7. Lack of optimized business processes: Understanding what comes before AND after your business is crucial to optimizing your supply chain and business plan. (After all, loss of revenue can occur when a customer returns a product.) Prepare for this with a supply chain that is optimized from concept to customer, and beyond.

  8. Not aligning application design to a business strategy: If your supply chain is only aligned with one specific type of business, it will be difficult for you to acquire or change to other products or businesses in the future. Understand your long-term growth plan, and align your supply chain for now and the future.

  9. Not creating effective vendor relationships: Yes, price is definitely important when choosing a supplier. However, employee relations and customer service also are important. Finding someone who is willing to be a partner is much more beneficial to your overall business than a few pennies saved.

  10. Operating in silos: Organizations that operate as networks operate much more efficiently than organizations that operate in silos. Make sure your teams are collaborating with one another and are customer-centric in their approach. The right combination of business suites will make all the difference.

Have you faced any challenge from this list?

Do you think we missed something?

Want some guidance on how to solve any of these challenges?

Drop us a line, we’d like to help.

Employee Management – Historical Payslip Print

Here are the steps you need to take to print history payslips on Sage 300 People for an employee.

Expand Employee Management Double-click History Payslips > Select History Period for the relevant Company Rule > Click Search > Click on the employee > Click Payslip Detail

 

 

 

 

 

 

To print the payslip for the specific employee for the selected period

Click Print Payslip button

 

 

 

 

 

 

 

 

 

Printing a History Payslip of all employees

Expand Reports > Double-click All Reports > Expand Payroll > Expand Payslip > Select Payslip > Click Open Print Form

 

 

 

 

 

 

 

 

Report Selection screen > Click Custom Period > Add Filter on the Company Rule if needed > Add Filter on Pay > Period and select the relevant Pay Period for the selected Company Rule > Click Preview

How to resolve “Due date being paid INVXXX” error while using the manual matching function

Described further are the steps that you need to take to resolve the “Due date being paid INVXXX” error message when using the manual matching function

Some important pointers

Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst. Before you undertake any of the following steps please make sure you have all the necessary back ups in place. Make a list before you start, if there is anything that you aren’t sure of, please contact us.

Please take a note, steps listed ahead require knowledge of database engines and application databases (DBs) such as Microsoft/Transact SQL, Pervasive SQL, or MySQL, etc. Incorrect application of these steps may result in system breakages and Evomatiq Business Solutions assumes no responsibility for errors resulting from changes to the database engine or DBs. Before making changes, backup all system and application DBs required for a full restore.

If you are unsure of anything, contact support for assistance

Resolution

  1. Go to DEVELOPMENT, UTILITIES, MAINTENANCE, IN LINES (GMAINT)

  2. When prompted for table, type GACCDUDATE in the table field and click on OK.

  3. From the right menu, CLICK on SELECTION.

  4. Enter NUM=’XXXXX’ (where xxxx is the invoice number, payment/receipt number)

  5. Verify you are on the correct line by comparing the value. If you are not on the correct line, use the arrows at the top left to change

  6. Delete the values in the fields TMPCUR, TMPLOC, and If using v1.4 or v5, TMPRPT
    Note: Do this for each of the lines of the NUM the by clicking on the Next radio button at the top of the screen.

  7. Verify that the FLGCLE field has a 1 in it. If not, change it to a 1.

  8. Try again, the issue should now be resolved.

Sage X3 “Unable to get the Add property of Workbooks class”

While trying to run any Sage Intelligence standard reports in Microsoft Excel 2007 you might come across this error: “Unable to get the Add property of Workbooks class”

The issue is caused when Excel 2007 fails to recognizing the XLTM template. Before you move ahead with the steps mentioned below, please ensure that you have the appropriate backups in place.

Follow the steps mentioned below to resolve this error

1. Navigate to the Sage Intelligence templates folder. You will find the location in the Report Manager under the Template Storage Location field.

2. Open the Dashboard Analysis AR 3-8 Report in Excel.

3. Click on Save.

4. Click on the drop down option under Save as Type.

5. Select Excel Macro-Enabled Template (*.xltm).

6. Click on Yes.

7. Click on Save.

8. Select the location, you can save it on your desktop for the time being. Ensure that it’ s the same name as the original report.

9. Copy the report from your desktop and paste it to the original location found in step 1. Replace the current report.

10. Rerun the report from the Report Manager.