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: Event / News, Consulting

A/P Payment Update in LX 8.3.4

A/P Payment Update in LX 8.3.4. ACP660B creates a file using a layout required by the bank; the file informs the bank to pay invoices. These conditions must be met to create the file:

  • FIM is an installed product in SYS821  ­
  • The user is authorized to FIM in SYS600 ­
  • The company is active in FIMCOMIT in SYS105  ­
  • The payment type is in BONPAYTP (SYS105)
Previous Article Infor LX & BPCS Tip of the Week: LX 8.4 Database
Next Article Infor LN & Baan Tip of the Week: Job Groups in LN
Print
35256 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This is a simple way to go from the customer order to making the order and shipping the order. It involves a few simple steps:

  1. Receive and enter the customer order
  2. Automatic credit review
  3. Automatic release of the shop order tied to the customer order
  4. Issue material, report labor to the production order receipt
  5. Pick the order, ship the order, invoice the customer

 

With lean, you can skip processing the demand through MRP. You can go directly from the customer order to the shop order creation.

In ERP LX, this function is called Backward Scheduling. This is a simple, easy way to create and release shop orders associated with the end item.

The result is a shop calendar with the associated order start dates. Setting up ERP LX properly with correct Queue Times, Setup and Run Times, along with Move Times, will result in accurate shop order start dates.

First143144145146148150151152Last

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