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

Infor LN & Baan Tip: Backflushing of Materials & Hours

Why do I sometimes see small decimal quantities remaining after backflush?

This behavior is largely caused by differences in decimal quantities allowed in inventory units versus the display format of the data. Having different display formats with different rounding for material quantities and warehouse line quantities means that since these quantities interact, if one is rounded more strictly and the other is not, then the rounded quantity is being propagated to the other quantity, thus resulting in a loss of decimals. As a result, it is advised to not use different formats and rounding settings for material quantities and warehouse line quantities.

Previous Article Infor LN & Baan: BIG DATA - Keeping Track of Key Metrics
Next Article Infor LX & BPCS Tip: Vendor Terms Maintenance, ACP160D1
Print
63185 Rate this article:
5.0

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

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.

Categories