Infor ERP Tips and Infor ERP News for Infor LX, BPCS, Infor ERP LX, Infor LN, Infor ERP LN, Baan, Infor M3, and Movex

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

BPCS/LX Tip of the Week: The Item Master Requirements Code

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).


Other options for the field are:

1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.
Previous Article Hoffmaster Selects Crossroads MES for LX Implementation
Next Article Baan/LN Tip of the Week: Printing Pick Lists
Print
83312 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Why this matters

Inventory discrepancies are often identified, but not fully understood. Without clear visibility into where and why variances occur, teams are left reacting instead of improving processes.

What this solves

The Cycle Counting Variances session (whinh8352m000) provides a visual way to analyze inventory discrepancies, helping teams identify patterns and root causes across warehouses and counting activities.


How it works...

Categories