The Sage ERP X3 Fiscal Year End function closes out the current fiscal year by rolling Balance Sheet account balances forward and posting the Net Income/Loss to the New Period Suspense account, then clearing the New Period Suspense account and debiting or crediting the Retained Earnings account. Because most organizations are not ready to close the fiscal year before posting transactions in the new year, Sage ERP X3 provides a Year End Simulation function. In this post we include an outline the processes for both Year End Simulation and Fiscal Year End.
Related Posts
ERP
03 Jul 2018
How to Test a Sage X3 Web Service of Type Subprogram Using SOAPUI
You have a web service (WS) working as expected then you make a minor change and all of the sudden the WS is not working anymore. What do you do? You could try troubleshooting using Sage X3 Classic SOAP web services but in our experience, it is much better to use SOAPUI instead. This is an open source software designed to manage WS calls. It is easy to set up and use and allows you to reuse your test code.
Steps to set up and use SOAPUI for X3 subprogram web services
Download software from https://www.soapui.org/downloads/latest-release.html
Open SOAPUI
Select Switch the Workspace from File menu. Enter a name for a file that will contain the entire workspace. The workspace can have multiple projects pointing to different Sage X3 installations and folders. Make sure you add .xml extension to the file name. Click Open.
You will get a confirmation message, click Yes.
Create a new SOAP project by right clicking on Projects (1) and selecting New SOAP Project. The Initial WSDL URL (2) contains the Sage X3 web server and port. The entire URL is http://YOUR_X3_SERVER:YOUR_X3_PORT/soap-wsdl/syracuse/collaboration/syracuse/CAdxWebServiceXmlCC?wsdl
Specify Sage X3 credentials to connect to the folder. Double click on CAdxWebServiceXmlCCSoapBinding (1), then click on Service Endpoints tab (2) and enter your username (3) and password (4).
To setup a request that executes the Sage X3 subprogram WS, select run method (1) and click on Request 1 (2). You could change the name to a more meaningful name (3) .
Double click on the new Request (1) and set up the authentication as Basic authentication. To do so, click on Auth (2) and select Basic on the Authorization drop down (3). If Basic doesn’t exist already, select Add New Authorization from the drop down (4) and create it by selecting Basic Type (5).
Enter the Sage X3 credentials to connect to the folder. They don’t have to be the same as the credentials used to connect to the WS Pool. Make sure Authenticate pre-emptively is selected.
Fill in SOAP XML parameters with the appropriate information:
1. codeLang: Sage X3 language
2. poolAlias: Sage X3 Pool name
3. requestConfig: adxwss.trace.on=on&adxwss.beautify=true&adxwss.optreturn=XML
4. publicName: Web service name
5. inputXml: Web service input parameters (make sure the parameters are enclosed on … tags) Submit the request by clicking on the green arrow in the toolbar and get your results. Save your project and reuse it every time you want. Right click on the project (1) and select Save Project. Now you know how to use this program. Give it a try next time you have issues with web services.
1. codeLang: Sage X3 language
2. poolAlias: Sage X3 Pool name
3. requestConfig: adxwss.trace.on=on&adxwss.beautify=true&adxwss.optreturn=XML
4. publicName: Web service name
5. inputXml: Web service input parameters (make sure the parameters are enclosed on … tags) Submit the request by clicking on the green arrow in the toolbar and get your results. Save your project and reuse it every time you want. Right click on the project (1) and select Save Project. Now you know how to use this program. Give it a try next time you have issues with web services.
Read more
Distribution / Manufacturing
ERP
13 Nov 2017
Wholesale and Distribution: Leveraging ERP to Stay Ahead
Over the last several years leaders in the wholesale distribution space have discovered that the secret to managing customers’ demands is to take advantage of the most up-to-date, emerging capabilities that ERP and related digital technologies can offer.
In addition to the pressure to lower costs, improve margins and grow the business, wholesalers and distributors today are faced with a competitive market filled with demanding customers. How are top performing wholesalers and distributors differentiating themselves from the competition? By getting the right products, at the right price, to the right customers at the right time, and industry leaders are doing this by leveraging modernized technology, and specifically Enterprise Resource Planning (ERP).
New Channels
Thanks to eCommerce and online sales, customers have new channels to get their products, enabling competitors to enter new markets they were once unable to service. To stay ahead of competition, smart wholesalers and distributors are looking to streamline processes and optimize their supply chains. This will not only accomplish more with fewer resources, but will also allow companies to more effectively manage inventory and keep prices low.
For many wholesalers and distributors who struggle to implement new delivery methods and interoperability, modernization of the technology used to support operations have proven to be a good strategy. But industry leaders truly succeed by leveraging the capabilities of an integrated ERP solution.
Integrated Technologies
To succeed, it is crucial to have an ERP that integrates with technologies that support distribution and supply chain goals. Here are a number of ways leaders manage to stay ahead, while dealing with customers’ demands at the same time:
Top industry performers combine Customer Relationship Management (CRM) with ERP to create a centralized portal for customer data that interacts with supply chain functionality.
They implement eCommerce and customer self-service portals that facilitates communication with customers, making it easier for them to order from the company, thereby increasing sales.
They implement a series of capabilities that improve their ability to make decisions as well as work with customers and suppliers.
Leading wholesalers and distributors utilize the data contained within ERP to make better decisions and become more agile.
Research notes that top performers are 72% more likely to have business analytics integrated into ERP, enabling them to make informed decisions, such as more accurate demand planning (Source: Aberdeen Group, February 2017).
Having real time visibility into the status of business processes and data is essential to wholesalers and distributors with a lot of moving parts. Utilizing data in conjunction with analytic capabilities allows organizations to better plan, forecast demand, improve customer service, reduce costs, as well as inform changes in workflows. Therefore, leaders understand that combining capabilities in their ERP systems is key to meeting customers’ demands. A modern ERP implementation facilitates customer service and help meet customer expectations in a competitive environment for wholesalers and distributors.
For more on this topic browse our learning center or speak to one of our expert ERP consultants.
Read more
ERP
01 Nov 2023
How to Eliminate the Need for Similar Requesters in Sage X3
We all know that we can put a requester on a landing page in Sage X3. But not a lot people know that you can filter the requester on the menu item by using the “where” parameter. Since a landing page query cannot be filtered on the front end, often times we need to create multiple variations of the same query pre-filtered with different criteria. The ability to filter the requester on the menu item level would eliminate need to create multiple similar requesters. We can have multiple menu items referencing the same query, but each with a different filter.
The screenshot below shows that I have a requestor under YKAL039. However, I need a landing page for each shared routing. So I would create YKAL39-01, YKAL39-02, and YKAL39-03 all referencing the same YKAL039 requestor, but each would have a different “where” parameter filtering by different routing codes.
A couple notes:
The filtering field needs to be a filter criteria on the requestor itself.
The “where” parameter value does not support any “or” operation.
For more information about how you can use filters to eliminate the need for multiple requesters, please contact your Net at Work Account Manager.
For more information about how you can use filters to eliminate the need for multiple requesters, please contact your Net at Work Account Manager.
Read more
0 Comments