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 What are the differences between INV810 and INV015 for Cycle Counting updates?

INV810 only deletes the sequence number from the ILI of the item so it is not selected again for counting and does not delete the ICY record.

The ICY Cycle Count sequential history file increases in size with each new cycle count session. Running INV015 will purge all the old ICY records up to the date entered on the set-up screen ‘Enter Cycle Count Ending Date’ field. Physically deleting the old ICY files.

In most cases, when you complete the cycle count posting and run the reports, you can reconcile the data as required. After you reconcile the data for a specific day (or group of days), you can run INV015 to purge the data for that day (or group of days).

Previous Article Infor LN & Baan Tip: When is backflushing disabled in LN?
Next Article Infor LN & Baan Year-End Processing Checklist for Period and Fiscal Year Closure
Print
6200 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

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.

Determining whether to use Master Production Schedule (MPS) planning or Material Requirements Planning (MRP) planning for items in Infor LX and BPCS involves understanding the nature of the items and their demand characteristics.

Master Scheduled Items typically encompass finished goods or service items. These items receive their requirements either from Independent demand, Dependent demand, or a combination of both...

12345678910Last

Theme picker

Tips: LN | Baan

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

First144145146147149151152153Last

Theme picker

Categories