End of mainstream maintenance for SAP Crystal Server 2016 and support plan for SAP Crystal Server 2020
We are on Crystal Server/Reports 2016. Do we need to upgrade to Crystal 2020? I only see the 2016 version on the download site.
Infor BI 10.6.30 for Lawson S3/M3 now supports SAP Crystal Reports Server 2020 as a report’s server. As such, this should be reflected accordingly on the LBI installer. Changes were made on the installer to include CRAS 2020.
CRAS 2020 is backwards compatible with reports created in 32-bit. Users just needs to recreate the data source connections in ODBC to ODBC 64-bit using the same Datasource Name. This also means that users will need to install the 64-bit drivers and configure the settings from 32-bit to 64-bit. For MSSQL, the 64-bit drivers are already available once you already have it installed. For other data source type, download the respective 64-bit driver. Same with Lawson OLEDB, Infor has released a 64-bit version, uninstall OLE DB 32-bit and install the 64-bit version.
Since CRAS2020 is a 64-bit application, the JVMMaxHeap value can now be set more than the 3GB limit in D:\BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\CRConfig.xml
Open the CRConfig.xml file. Look for the following lines:
<JVMMaxHeap>64000000</JVMMaxHeap>
<JVMMinHeap>32000000</JVMMinHeap>
Change the JVMMaxHeap value more than the 3GB limit. Save and Restart RAS.
Please note that Crystal Designer 2020 will no longer work when installed in the same server as CRAS 2020. In CRAS 4.3 (CR server 2020), it is not supported to install both server side and client side in the same machine. Registry keys may get corrupted.
If you’re interested in moving forward updating your Crystal software, Nogalis offers MSP support to assist with upgrades and migrations.
https://www.nogalis.com/wp-content/uploads/2024/10/PSA-SAP-Crystal-Server-2020-Support.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2024-11-01 08:04:112024-10-28 12:05:27PSA – SAP Crystal Server 2020 Support
If you are having issues loading your externally facing Lawson Portal, one way to troubleshoot is to set the logs to debug mode so that you can hopefully get more information about the errors.
In WebSphere Application Server admin on your internal server, click into the web server under Servers > Server Types > Web servers.
Click the web server name then Click “Plug-in properties”.
Change the “Plug-in logging” to Log Level “Debug”
Click “Apply” or “OK”. Go back to the web server list, and select your web server using the checkbox. Select “Generate Plug-in”. Since your web server is external, there is no need to Propagate the plug-ins (this is a manual process).
When you generate the plug-in, the location will be displayed at the top of the screen. Navigate to that location and copy the plugin-cfg.xml file.
Navigate to your external server and paste the plug-in file at <WebSphere Install Directory>/Plugins/config/<webserver name>
Perform an iisreset on the external web server.
Now your web server will be in debug mode, and you will get more detailed information in the plugin logs.
https://www.nogalis.com/wp-content/uploads/2024/10/Setting-External-Web-Server-to-Debug-Mode.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2024-10-29 08:12:212024-10-28 12:03:44Setting External Web Server to Debug Mode
This problem usually means that the shipments are not found on the handhelds – and it’s because of this error causing the missing information.
Resolution:
To simply amend this, you will need to ensure that the Access flag in Lawson Security is set to “Y” when the ‘lawson’ (this is referring to the lawson.username from the mscm.filter.properties file) user has a requester. Once the setting is changed or confirmed, you should not come across this error anymore.
https://www.nogalis.com/wp-content/uploads/2024/10/MSCM-No-Picking-Information-on-handheld.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2024-10-25 08:44:232024-10-21 10:52:39MSCM Not Picking Information on handheld
Is it by design that the Payroll ACH payments are automatically reconciled in PR85 (Bank Account Reconciliation)?
Why are the AP ACH not automatically reconciled in CB80 (Bank Transaction Adjustment)?
Answer:
There is a setting on the payment code that determines if the transactions are automatically reconciled. Inquire on CB00.4 (Bank Transaction Definition) for ACH and click on the Cash Payment button (CB00.7). Set Automatic Reconciliation to “Y”.
Then when you issue an ACH payment it will be automatically reconciled. Payments that already exist in the system will not be affected by this change and will still need to be reconciled.
https://www.nogalis.com/wp-content/uploads/2024/10/Lawson-PR-ACH-Auto-Recon-is-in-PR85-but-not-AP-ACH-payments.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2024-10-22 08:31:422024-10-21 10:43:58Lawson PR ACH Auto Recon is in PR85 but not AP ACH payments
Recent updates for Infor Lawson S3 mainly focus on cloud migration and release schedules for on-premises and single-tenant customers. Notably, starting in 2024, Lawson’s V10 products will follow a new release schedule, with updates in April and October instead of March and September as in previous years. Additionally, annual maintenance service packages (MSPs) will be aligned with the October release, ensuring consistent delivery of security patches, compliance updates, and bug fixes throughout the year.
For organizations still on the S3 platform, there is growing momentum towards cloud migration as Infor promotes its cloud-based ERP solutions, enhancing flexibility, scalability, and data management. Financial and other sector-specific modules for Infor Lawson S3 are increasingly being optimized for cloud use, encouraging businesses to explore cloud adoption for better integration and efficiency.
These changes reflect Infor’s commitment to modernizing its platforms and aligning with evolving cloud standards, improving both the user experience and system performance.
Migrating Lawson S3 to the Infor Cloud with Nogalis offers several advantages. Nogalis specializes in seamless migration processes, ensuring minimal downtime and operational disruptions while optimizing Lawson for the cloud environment. Our team of experts can handle complex integrations and customizations, allowing businesses to leverage Infor Cloud’s advanced features, scalability, and security. With ongoing support and proactive management, Nogalis helps organizations achieve cost savings by reducing the need for on-premise hardware and maintenance, while improving system performance and accessibility across various devices. And once the move to the cloud is complete, Nogalis can stay on board to provide managed services for all your Infor Cloud products. Here is some more information about our Managed Service and Project offerings.
When it is time to move to the cloud, Archiving Lawson data using APIX will be crucial. APIX offers a reliable and compliant data archiving solution, allowing businesses to securely store historical Lawson data without burdening the cloud environment. Additionally, APIX provides a sleek UI that puts historical data at users’ fingertips. Proper archiving helps maintain data integrity and ensures easy access to legacy information for auditing and reporting needs. By archiving Lawson data before migration, businesses can streamline the transition, reduce storage costs in the cloud, and comply with regulatory requirements, all while ensuring that critical data is preserved and accessible post-migration. Book a demo here!
https://www.nogalis.com/wp-content/uploads/2024/10/Summary-of-Infors-Q3-Lawson-Announcements.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2024-10-18 08:16:452024-10-17 16:19:03Summary of Infor’s Q3 Lawson Announcements
When installing Infor Process Designer, a new addition for install is that it is now asking for the Java 17 path. To complete the install, you will first have to download JDK 17 from Amazon Corretto and install it. Then verify that the install path is added to JAVA_HOME and Path environment variables.
Next, run the IPD installer and choose New Install. Select the directory to install IPD. Browse to the Java 17 location if it isn’t already populated.
The option to copy configuration information is now available. You can select “Yes” here and select the existing IPD configuration to copy.
Can you please open again program in Lawson Portal and once you open it, please do “CTRL+ALT+A” from your keyboard and send me the result it will show the XML file.
var vID = portalWnd.oUserProfile.getAttribute(“ID”);
var vNtID = portalWnd.oUserProfile.getAttribute(“lawsonuserlogin”);
var vMessage=”User Cannot Modify GL Entry”;
var vCompany=lawForm.getDataValue(“GLC-COMPANY”);
vCompany=portalWnd.strFillChar(vCompany,4,”left”,”0″);
var vFYear=lawForm.getDataValue(“GLC-FISCAL-YEAR”);
var vAPeriod=lawForm.getDataValue(“GLC-ACCT-PERIOD”);
var vSystem=lawForm.getDataValue(“GLC-SYSTEM”);
var vJeType=lawForm.getDataValue(“GLC-JE-TYPE”);
var vCountrolGrp=lawForm.getDataValue(“GLC-CONTROL-GROUP”);
var vJeSeq=lawForm.getDataValue(“GLC-JE-SEQUENCE”);
// build the DME call that will get the related asset number
var vDmeString = portalWnd.DMEPath;
vDmeString += “?PROD=DEVRY&FILE=GLCONTROL&FIELD=OPERATOR;&MAX=1&INDEX=GLCSET1”;
vDmeString += “&KEY=” + vCompany + “=” + vFYear + “=” + vAPeriod + “=” + vSystem + “=” + vJeType + “=” + vCountrolGrp + “=” + vJeSeq;
vDmeString += “&SELECT=OPERATOR=” + vNtID;
vDmeString += “&XCOLS=TRUE”;
vDmeString += “&OUT=XML”;
// send the DME call to the server
var vDMEInfo = portalWnd.httpRequest(vDmeString);
if (!vDMEInfo || vDMEInfo.status)
{
var msg=”Error calling DME, “;
msg += (vDMEInfo
? “(status code): “+vDMEInfo.status
: “bad server response.”);
lawForm.setMessage(msg);
alert(msg);
return false;
}
// create an XML object to contain the DME data
var vObjDMEXML = new portalWnd.DataStorage(vDMEInfo);
var vOpr=lawForm.getDataValue(“OPERATOR”);
// load a variable with the records returned by DME
var vRecords = vObjDMEXML.document.getElementsByTagName(“RECORD”);
if (vRecords.length != 1)
{
var vMsg = “Cannot Modify GL Entry”;
lawForm.setMessage(vMsg);
return false;
}
}
return true;
}
]]>
</XSCRIPT>
</form>
This shows the program is a Design Studio form formid=”GL40.2_CUSTOM”. The reason it didn’t show properly aligned to the Lawson Portal is because some of the size of the boxes did not match the Portal and DS form.
Resolution:
Run the analyzer tool from Lawson Portal.
Go to Portal > Migrate Custom Content > Migrate Custom Content > Migrate>Custom Form Nodes
You will get Pop ups for the custom form to migrate.
Click ok
And then go to Portal and try your screen again. It should not have the right size.
https://www.nogalis.com/wp-content/uploads/2024/10/Lawson-form-is-not-sized-right-in-Portal.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2024-10-11 08:20:212024-10-07 15:28:47Lawson form is not sized right in Portal
