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: GRINYA

GRINYA is one of the more complex issues in ERP Finance. GRINYA is the tracking via ledger account of the value of items received on a purchase order that have not been matched to a supplier invoice.

Baan solutions for Baan IV and V were incomplete. To take full advantage of the current GRINYA reconciliation process, check Infor solution #107147, which contains the GRINYA user manual and a link to download the software for your version of Baan. For ERP LN, look at Document Code U8942C US.

It is called User Guide for Reconciliation and Analysis. If you are not running the latest GRINYA solutions, patching will require a good amount of time in filling the Interim tables this solution runs from. Infor has posted several procedural write ups, so check the Support Site and read up before tackling this for the first time.
Previous Article Managing Customer Supplier Relationship in Discrete Manufacturing
Next Article BPCS/LX Tip of the Week: Cycle Counting Part 1
Print
60689 Rate this article:
3.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

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.

In addition to assigning lot numbers in Shop Order Entry/Maintenance (SFC500) after the shop orders have been released, users can now pre-assign lot numbers during the Multi-level Shop Order Release process (SFC530) and the Multi-Level Backflush process (LMP600) for sub-assemblies that are lot controlled items. The user has the choice of using the parent lot ID, the next sequential generated lot ID, or not pre-assigning lot IDs. Multiple items per lot must be installed to use the parent lot number option.

First6263646567697071Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories