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
As organizations migrate to the cloud, cybersecurity threats have grown, making security a top priority. This shift is driven by the realization that data breaches can have devastating financial and reputational impacts. Businesses are now prioritizing the protection of sensitive data, often opting to invest more in security measures despite potentially higher costs. David S.Linthicum, industry expert and thought leader, shares an article on Infoworld.com on why cloud security typically prioritizes and outranks cost and scalability for some companies. Linthicum explains how the shift in prioritizing cloud security over cost and scalability is a significant trend driven by several factors. Some include: rising cyberthreats, complex cloud environments, compliance and regulatory pressures, reputation, long-term cost implications, innovation and agility. “This landscape is driving businesses to adopt a ‘security-first’ mindset,” he notes.” Although this can be a platitude, we must recognize that other benefits of cloud computing—cost savings and scalability—can be undermined without good security planning and mechanisms. This shift mirrors a broader global movement toward valuing resilience and reliability alongside traditional operational metrics.”
How can companies keep security and cloud costs within a reasonable budget? Balancing cloud costs with security involves strategic approaches to optimize resources while safeguarding systems and data, Linthicum explains. “This directly correlates with the price of the cloud versus the value of security, and they are not often that easy to connect. Many assume that the more security you’ll need, the higher the cost of the cloud services.” However, he has found that in many instances that the opposite is true.
Below are Linthicum’s words of advice to help you find value in security and move away from the accepted mentality that more security always means more money.
Build security into the architecture from the start to avoid expensive fixes later. This seems obvious but it’s often not done. Security is an afterthought about half the time, and companies then are forced to toss money at the problem.
Automate compliance and management to reduce manual efforts and costs. Automation means repeating good processes without depending on humans; security is no different.
Use strong access controls to ensure only authorized users access critical data. Identity management is the most used approach here, and for good reason.
Regularly audit cloud usage to eliminate wasteful spending and optimize resource allocation. Also, train teams to efficiently manage cloud resources and security.
If you’re in Lawson on PO20 and you’re trying to delete a PO, you may sometimes come across the following error message, “Cannot delete, line ###### has been issued”.
There is a reason why you cannot delete and a workaround for it. The reason for it not being able to be deleted is that unfortunately, since the PO has been issued, the vendor has a copy of that PO. This means that it is a binding document. It cannot be deleted. It needs to be kept in the system so that it can be referenced if the vendor should call about it. The only action you can take is that the PO can be canceled instead.
https://www.nogalis.com/wp-content/uploads/2024/10/Lawson-PO20-Error-Cannot-delete-line-has-been-issued.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2024-10-08 09:13:382024-10-07 15:18:11Lawson PO20 Error – Cannot delete line ###### has been issued
