Please Wait a Moment
X

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

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

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

Subscribe to newsletter

Crossroads MES Version 11 Released

Anthony Etzel 0 53519 Article rating: No rating

Crossroads MES Version 11 was rolled out in March, 2014. Some of the new features include a new GUI interface, improved End of Shift review functions, pre-formatted production label printing, and an electronic shop packet on the factory worker Job In screen.

Read more

Crossroads MES Released for Tablet

Anthony Etzel 0 49926 Article rating: 3.7

Crossroads RMC announces that the Crossroads MES solution is now compatible with tablet PCs running Windows 8.1. Tablet PCs are becoming the clipboard replacement for supervisors and managers to monitor what’s happening on the shop floor.

Read more
First126127128129130131132133135

Tips:  LX | BPCS | 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 BPCS/LX Tip of the Week: How To Capture Re-Work Time (Part 1)
Next Article BPCS/LX Tip of the Week: Work Center & Machine Locations
Print
77572 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel
Contact author

Contact author

x

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Read more

Categories