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

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

What would you say to someone if they never went to a doctor for a check-up, or never took their car in for regular maintenance, like an oil change?

You might say that they were asking for problems, right? The point of those check-ups is to catch a problem early, or better yet before it occurs. Going for check-ups gives you the peace of mind that things are running well and if an issue is identified early enough you can reduce overall risk. Regular check-ups can help reduce out-of-pocket expenses over time.

What about Finance, Manufacturing, Supply Chain, and Company-wide Check-Ups for your Infor ERP system? What will happen if you NEVER hit pause?

Here are some questions by department to consider.

Finance:...

There are two options for rework of serialized items. One is to define the serial numbers upfront by defining the as-built serial header before releasing the rework order. The second option is to not define serials in the as-built header and instead, the serials are defined through issuing the material to the rework order. Manually entering the serial number after release of the rework order is not supported.

First3233343537394041Last

Theme picker

Categories