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 Reconciliation – What Could Go Wrong?

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or 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.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Optimize Your Manufacturing Today!

Previous Article 10 Ways to Reduce Inventory in Your Supply Chain
Next Article BPCS/LX Tip of the Week: 6 Powerful Steps to Win With Automation
Print
40431 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Enterprise General Ledger (EGL) provides audit attributes to track journal entry changes and approvals.

To implement this enhancement, you can request and apply MR 81026.

This enhancement provides audit attributes for the last maintained user, date, time, and approval user, and date, and time on the Financial Journal Entry and Financial Journal Entry Lines. This audit function provides visibility to who and when the journal was last maintained and to who and when the journal was approved.

The programs or areas impacted include:

  • Financial Event
  • Financial Journal Entry
  • Financial Journal Entry Line
  • Financial Journal Entry Detail Line
  • Post Multiple Events

Did you know CLD provides you with the following benefits?

▪ You can journalize and post-transaction data from any third-party application or Infor LX subsystem to the Configurable Ledger (CLD).

▪ You can generate multiple journal entries across different charts of accounts, ledgers, and books within the CLD from one transaction line.

▪ You can automatically post transaction amounts across different books using an appropriate exchange rate between the batch transaction currency and target book currency.

▪ You can use validation reports to identify validation errors within the files that contain batch transaction data and then you can make any necessary corrections before resubmission.

▪ You can use standard CEA grouping and summarization options for journals created during Batch Transaction Processing.

▪ You can interface GLD journal entries into CEA for the BPCD version of Infor LX. This allows data to be interfaced into CEA without changing the way data is processed through Infor LX subsystems.

First2021222325272829Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories