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

Infor LN & Baan Tip: What is the GRNI Reconciliation Process?

What is the GRNI (Goods Received Not Invoiced) Reconciliation Process?

The reconciliation process of the GRNI transactions consists of the following steps:

  1. Close the financial period so that no new transactions can be entered.
  2. Print the trial balance.
  3. Print a report of the invoices to be received.
  4. Compare the reports.
  5. Print the reconciliation data.
  6. Examine the reports.
  7. Rebuild the History.
  8. Print the trial balance and the reconciliation report again.
  9. Print the GRNI reconciliation checklist.
  10. Check the balances on the GRNI reconciliation checklist.
  11. Analyze the reconciliation data.
  12. Make corrections.
  13. Print the GRNI reconciliation checklist again.
  14. Post the reconciliation correction transactions.
  15. Accept the reconciliation data.


Have questions on this process or need some help? Contact us! Our experienced Finance consultants will be glad to assist you.

800.762.2077

Previous Article Infor LX & BPCS Tip: Capacity Planning – Resource Requirements Reports
Next Article By 2026, 75% of organizations will base their digital transformation model on the CLOUD!
Print
12665 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

One way to save space in your general ledger is to compress integration transactions. The transactions are combined into one ledger account number, and the detail is still available in the integration transactions sessions.

The compression is seen after the transactions are finalized. 

Compression is established in the mapping scheme by checking the box under the columns “Compression of Debit/Credit Transactions. This can only be done in a mapping scheme that is not activated. 

There has been a recent porting set change due to Infor’s Product Life Cycle Policy.  

How to determine the maintenance stage of an Infor LN product version and release

Before a customer starts deploying Porting Set 9.4a or a later release, they must determine the actual maintenance stage of their Baan / Infor LN product. The definition of the maintenance stages for the product versions and releases of all versions of Baan and Infor LN are outlined in the Product Support schedule as published in the PLC policy. The maintenance stage of the ERP version is either “Mainstream Maintenance”, “Extended Maintenance” or “Sustaining Maintenance”.

How to manage Porting Set updates

The following conditions apply to customers who intend to upgrade to Porting Set 9.4a or later Porting Set releases:

First2930313234363738Last

Theme picker

Categories