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

Get ahead of the curve with a seamless, comprehensive integration strategy that surpasses other competitive solutions. In part two of this webinar, join our discussion of best practice integration tricks and solutions from a fellow customer’s office of finance. Understand what makes their integration approach effective and review best practices in integrating your IBM i solution to other office of finance solutions (F9/EPM/Birst/GRC).

Hosted by Peg Tuttle from the IBM i podcast, “The Incredible i Show”. 

  • How version upgrades have tightened internal control loopholes.
  • Structural IBM i advancements designed to safeguard your organization.
  • IBM i ecosystem solutions that strengthen both data and access vulnerabilities.

Don't miss this fourth fireside chat, Eight Ways to Modernize your IBM i product – Topic #3 of 8: Best practices in integration for the office of finance (Part 2). Register today!

Register today!

Did you know that you can set up one-time vendors in LX? One Time Vendor (1,A): Specify Y to indicate that this vendor is a one-time vendor. Otherwise, could you specify N. The system removes a one-time vendor's information from the Vendor Master file after all transactions are reconciled. If this vendor already exists as a one-time vendor, you can specify N to change the vendor to a regular vendor.

First678911131415Last

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.

123456789Last

Theme picker

Categories