Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

Infor LX / BPCS Tip of the Week: Pre-assigned lot numbers for multi-level SO release

In addition to assigning lot numbers in Shop Order Entry/Maintenance (SFC500) after the shop orders have been released, users can now pre-assign lot numbers during the Multi-level Shop Order Release process (SFC530) and the Multi-Level Back-flush process (LMP600) for sub-assemblies that are lot controlled items. The user has the choice of using the parent lot ID, using the next sequential generated lot ID, or not pre-assigning lot IDs. Multiple items per lot must be installed to use the parent lot number option.
Previous Article How Are Your 2019 Goals? Get More Out of Your ERP!
Next Article Infor LN & Baan Tip of the Week: The RFQ Comparison Workbench in LN 10.7
Print
30485 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

If you opt to summarize transactions, do so after a period of testing so that you can be certain that all models and aliases are working to your satisfaction. When you summarize, consider ‘Summary with Detail’ because this retains the detail transactions in GLH.

Are you still using handwritten tickets for your inventory?  This method of inventory tracking is slow and prone to human error.

Putting a simple barcode system in place speeds up the process of tracking inventory movements, reduces the likelihood of mistakes, and creates a recorded history of the who/what/where that can provide valuable insight to those who make critical business decisions for your business.

Not sure where to start? Contact us and we’d be happy to help you take the first step.

First96979899101103104105Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories