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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Back Dating Cycling Counting Orders

Cycle Count Orders cannot be directly “back dated” in Baan IV, Baan V or LN, however, there are some work-arounds.

In Baan IV you can do an inventory adjustment and back date. Just set all dates on the adjustment to the date you want and Baan will post the adjustment in that period.

In LN you can do a Cycle Count/ Adjustment and again back date and Baan will post to that period.

 

Unfortunately, there is no work-around for Baan V.

Previous Article BPCS/LX Tip of the Day: Inventory Management
Next Article BPCS/LX Tip of the Week: Top Down Shop Order Schedule
Print
57713 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

When an attempt is made to change an item’s type to a non-inventory item from any other value, a new validation is performed to determine if the item has any inventory on hand and, if so, prevents changing the item’s type.

This enhancement available in LX 8.4 prevents LX from showing an on-hand inventory balance for a non-inventory item.

The programs or areas impacted include:

  • Facility/Planning Data Maintenance, MRP140D2
  • IDF Enterprise Item

To get this enhancement, request and apply MR 80120.

An 8.4.1 EGL audit enhancement now provides visibility to who and when a financial journal was last maintained and to who and when the journal was approved. The enhancement provides audit attributes for last maintain user, date, time and approval user, date time on the Financial Journal Entry and Financial Journal Entry Lines.  

The programs or areas impacted include:

First1718192022242526Last

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