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
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip of the Week: Control Number, POCNO, added to CEA502B1

This enhancement makes the control number field in the purchase order file available for macros. Previously, the POCNO field (control number) in the purchase order was not available for macros. This enhancement allows the user to create macros that use this field. This enhancement provides the user with the ability to keep track of control numbers in their journal entries.

The programs impacted include:

  • CEA502B1, ACP Engine Resolution Program
  • CGL091B, ERPLX ACP File I/O Program
Previous Article Infor LN Extensibility Methodology for Cloud and On Premise
Next Article Consulting News: Planning for your LX Upgrade
Print
33501 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

In LX 8.4, an enhancement has been included to allow for the expanded Company fields to have the leading zero truncated.

To trim leading zeros, CEA515B is called during macro resolution to trim the leading zero based on the position in the Zero Trim file (GZT). The Zero Trim file contains all the company number fields currently defined in the CEA Cross Reference fie (GXM).

This enhancement provides year over year comparison in financial reports and eliminates the need to setup new companies in programs such as Alias Definition. Financial programs trim the leading zero on Company fields, such as Company 010, on subsystem transactions to process as Company 10 during CEA macro resolution. Clients who prefer to retain the Company value as 010 on financial reports can clear the GZT file.

First5859606163656667Last

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