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 Focusing on Productivity: Analyzing Pick-to-Pallet Selection
Next Article Baan/LN Tip of the Week: Printing Pick Lists
Print
42964 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

The LMP module (Lean Manufacturing Process) uses work centers but refers to them as production cells.

A cell is one or more work centers that produces an end item. So when a company decides to adopt the lean manufacturing philosophy, the concept of work centers takes on a new meaning.

In lean terms, the work center, or group of work centers, becomes a production cell. In other words, a mini-factory producing end items with similar characteristics.
Understanding:

The Machine Master File

Do your machines have a fixed asset tag? The machine master file has a field called Fixed Asset.

BPCS does not use this field, so you can use this field for anything. You can record your fixed asset tag in this field and use the effective date. You can create a custom fixed asset list by using a DFU or Query program.

First150151152153155157158159Last

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