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
56149 Rate this article:
3.3
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

BPCS/LX Tip of the Week: SFC600

In addition to SFC650, this ERPLX program is also used to capture and post shop floor information.

The key difference between the two is that SFC600 only captures Labor (run time) reporting, machine time, downtime and indirect time.

If you use SFC600, then all shop order material receipts and issues would be captured using INV500.

Both Inventory and Shop Floor Transaction entry is keyboard dependent, unless you incorporate an automated method like an MES solution to capture the data.

Using SFC600 to enter downtime.

You are tracking downtime and using SFC600 to enter the downtime, but you don’t know where to go to setup downtime reasons. You can set up the downtime reason codes in the INV application by selecting the reason code maintenance program INV140D1.

Once you are in the reason code maintenance program, position to the transaction effect code “D”. Using the transaction effect code “D” you can now setup as many downtime reason codes as needed. The reason code field is alpha numeric, so be creative with your reason code assignments.

FirstLast

Tips: LN | Baan

Categories