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

George Moroses

Infor LX / BPCS Tips & Tricks for EXECUTIVES

FINANCE: Prevent Voiding of Selected Invoices
This enhancement prevents users from voiding invoices after they have been selected for payment. If a user selects an invoice for payment and another user voids the invoice during the payment process, it can produce erroneous and duplicate records. The ACP500 programs were modified to check the status of an invoice before it can be voided. If the invoice has been selected for payment, a message is generated, and the invoice cannot be voided.

OPERATIONS: Copy Shop Order
In the Shop Order Selection program, action 3=Copy is available. This action allows copying any shop order except for flow orders or campaign orders. Instead of copying from the parent item's bill of material and routing, the new shop order’s materials and operations will be copied from the selected shop order. Note that if the existing shop order is linked to a customer order or line, this linkage will not be copied to the new shop order.

TECHNOLOGY: Group Security for ILM501 Inbound Delivery Maintenance
Add function key / action code security to control who is authorized to create/revise/delete functions in ILM501 Inbound Delivery Maintenance.  With added Group Security, managers can control which users are authorized to create, change and delete deliveries in ILM501 Inbound Delivery Maintenance.

Previous Article Infor LN & Baan OPERATIONS Tip: MPS Planned vs. MRP Planned
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
11950 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

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