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

George Moroses

Infor LX & BPCS Tip: Tracking Financial Journal Entries

An 8.4.1 EGL audit enhancement now provides visibility to who and when a financial journal was last maintained and to who and when the journal was approved. The enhancement provides audit attributes for last maintain user, date, time and approval user, date time on the Financial Journal Entry and Financial Journal Entry Lines.  

The programs or areas impacted include:

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

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

Previous Article Infor LN & Baan Tip: Payment Terms on a Purchase Invoice
Next Article DATA: See it. Understand it. Discuss it.
Print
13938 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

12345678910Last

Theme picker

Tips: LN | Baan

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

Pros
Each legal entity can have its own general ledger and balance sheet.
Income statements can be generated for the different logistics companies.
Accounting user must go in and out of companies if there is a need to view or create transactions in more than one company.  However, if all companies are tied to the same financial group company, centralized payments, cash receipt application, and display and printing of ledger transactions and trial balances are possible for both companies from within the financial group company.

Cons
First126127128129131133134135Last

Theme picker

Categories