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 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.

Previous Article Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Update User Security in IDF
Next Article Tick-Tock... It's time to get more out of your ERP
Print
6650 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

12345678910Last

Theme picker

Tips: LN | Baan

Project templates are useful because you can specify all of the information that you would normally want to include when creating a new project such as project structure, budget, and so on.

In Baan IV/V, project templates do not exist, but you can set up a project template by creating a regular project, and setting the status to simulated or free. This is done so that the project does not create plans. Under this scenario, you can easily copy one project to another.

In LN, when you create a new project, a template can be used as the starting point. This is similar to copying a normal project, but unlike normal projects, no costs or revenues can be posted on a template.


In ERP LN, users can define a distributed business partner organization by defining parent business partners to link the business partners with different roles.

In Baan IV, users can define a distributed business partner organization in the Maintain Concern Structure of Trade Relations (tccom3101m000) session.

First154155156157159161162163Last

Theme picker

Categories