The credit crunch and recovery have exposed manufacturers to volatile demand. The earthquake in Japan has exposed manufacturers to volatile supply. The key to effective management of supply and demand lies in a manufacturer's planning activities.
In this series of bi-weekly tips, we break down the secrets to effective replenishment planning and shop scheduling. Pemeco Consulting is a leading vendor-agnostic provider of Supply Chain and ERP services to companies running Infor LN and Baan ERP systems. Learn about our niche speciality Infor LN and Baan ERP services and our Planning Dashboard for ERP LN and Baan.
A planning engine is a lot like a high-performance athlete. It can only perform if it’s well-trained, in shape and well-prepared. Like an athlete, if it’s only fed a steady diet of junk food, it’s simply not going to perform optimally.
Pemeco provides implementation, optimization and supply chain services to companies running Infor's ERP LN, Baan IV and Baan V systems. Our firm is vendor-agnostic and has no affiliations with Infor. Learn about our Infor services and review our Infor clients.
In my February article, ERP Buyer’s Corner: Making 2011 the Year of Success, I predicted that “some of the bigger ERP vendors [would] go acquisition hunting to quickly fill strategic gaps in their product repertoires.” This prediction has come true in spades.
A few days ago, GC Software Holdings, Inc. – an affiliate of Golden Gate Capital and Infor – agreed to acquire Lawson, another Tier II ERP vendor for about $2 billion (U.S.). The intention is to integrate the Lawson ERP suite (M3 and S3) into Infor's software suite. This acquisition follows Infor's recent integration of SunSystems, financial management software.
This recent M&A activity is likely to have both positive and negative effects on Infor's ERP LN and Baan users.
In terms of the positive – and assuming that Infor/GC Software can successfully pull off the integration – Infor's ERP LN and Baan users could achieve the following benefits:
We are using Exchange Schemes for updating a customized table in our production environment. In the table there's a enumerated field which contains a status for each record, this field help us to control other processes so is not required to be updated by the exchange. The Exchange scheme has been configurated for no updating, no deleting, no overwriting records only adding in the session tuxch0121m000.
If a new record validated by the primary key in the table (a field with a consecutive number) doesn't exist the Exchange works fine, quickly inserts the record in the table with the session tuxch0223m000 (Import data no regularly), but if a second execution for the same flat file with the same data in the record is carried out it lasts a lot. Before it didn't work in this way, the session also worked quickly for a second try with the same flat file.