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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: GRINYA Reconciliation – What Could Go Wrong?

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Optimize Your Manufacturing Today!

Previous Article 10 Ways to Reduce Inventory in Your Supply Chain
Next Article BPCS/LX Tip of the Week: 6 Powerful Steps to Win With Automation
Print
40540 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This enhancement allows users to update Reason Code Maintenance, INV140D1, for Transaction Effects that they are not authorized to in any other programs. A new system parameter was added to Inventory Parameters, INV820D. The enhancement allows users who do not actually perform transactions in Infor LX to maintain the reason codes for the transactions.

This enhancement provides clients the ability to store the opening/ending on hand balance for each Inventory period at the Item (IIM), Warehouse/Item (IWI) and Lot/Location (ILI) levels. Infor LX clients can back date inventory transactions into the immediate previously closed period, and thus update what was saved as the opening/ending balance throughout the current open period. 

Tracking the opening/ending/period balance for each inventory period can give users insights into the levels of inventory for each item, item/warehouse and item/warehouse/lot/location combination.

First6465666769717273Last

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