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: 15 Reconciliation Steps for GRNI Transactions

How many are you missing in your process?

The reconciliation process of the Goods Received Not Invoiced (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.
Previous Article Optimize with Infor Development Framework: IDF
Next Article Is Your ERP System Hurting Your Business?
Print
14190 Rate this article:
3.3
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This enhancement provides the ability to copy order lines, quote lines, and RMA lines. During Order Entry, action 3=Copy is available to copy regular lines and special lines. The new line displays in the next available line number.  This enhancement reduces manual key entry and speeds up Order Entry. 

The programs or areas impacted include ORD700D2, Order Line Entry, Quote Line Entry, and RMA Line Entry.

This enhancement prevents over-allocations and resulting overshipments to customers. Attempted over-shipments can present an error message to the user, or there is an option to automatically adjust the user’s request to the allowed quantity.

Since over-shipments result from over-allocations, Infor LX provides an optional validation during the four processes where a user can attempt to over-allocate. Note: Infor LX never over-allocates or over-ships; this always results from a user’s action. This enhancement provides three options regarding over-allocations and over-shipments:

  • Continue current process with warning message.
  • Show error message.
  • Automatically change allocation quantity to match quantity available for shipment.

If the over-ship quantity change is acceptable, internal procedures may require that the order quantity be revised so that pricing, promotions, credit checking, load planning, and other processes reflect the actual quantity.

The programs or areas impacted include:

  • ORD820D, Order Entry System Parameters
  • ORD720D2, Order Allocations
  • ORD725D, Order Entry Allocations
  • ORD570D5, Pick Confirm Inventory Confirmation
  • ORD700D2 / ORD700DA / ORD710B, Order Line Validation
First5556575860626364Last

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