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

Infor LX & BPCS Tip of the Week: Additional Selection Criteria for Cycle Count Purge Enhancement – 8.4

The final step in Cycle Count processing is to maintain the (ICY) Cycle Count file. This history file increases in size with each posting session. It is up to users to purge the historical data that you no longer need. Previously, INV015 Cycle Count Purge by date only allowed users to purge the cycle count file by date. Now, additional selection criteria have been added that allows users improved ways to control records they may want to purge.
Previous Article Infor LN & Baan Data Collection News: Crossroads RMC Cycle Counting Application
Next Article Consulting: Methodology for Infor LX & BPCS Upgrades
Print
33989 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

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

In LN, the configuration of a generic item not always results into a customized item. Configured items can now be customized items as well as standard items. If users configure items without PCS projects, standard items are generated instead of customized items.

 

The sessions for generating product variant structures for sales quotations and sales orders are moved from the Product Configuration module in Manufacturing to the Sales Control module in LN. The following new sessions are available in Sales Control:

▪ Generate (Budget) Structure for Sales Quotations (tdsls1201m100).

▪ Generate (Project) Structure for Sales Orders (tdsls4244m000)

Service departments and warehouses that contain spare parts and components used for service and maintenance belong to enterprise units. To perform separate financial accounting for the service departments and their warehouses, you can assign service departments and warehouses to enterprise units that are linked to different financial companies.

 

If material, labor, or other costs are transferred between service departments and warehouses, or from one service department to another (in the case of internal subcontracting for depot repair), LN can perform the invoicing between these departments and warehouses. In the Enterprise Modeling Management module, you can define internal trade relationships with invoicing between various entities.

 

You can also record and process service operations in a multi-logistic company environment.

First139140141142144146147148Last

Theme picker

Categories