Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Cash Flow Functionality and Setup

A cash flow statement provides a historical view of the movement of cash within a company. This statement offers an overview of both the origins and destinations of cash, aiding management in evaluating the company's ability to fulfill short-term financial obligations. To differentiate between various sources and uses of cash, reason codes can be utilized. When interacting with cash transactions in relevant sessions, users have the option to input or review the corresponding cash flow reason. The cash flow statement organizes cash transactions based on these reasons. LN software system maintains year-specific opening balances for cash flow transactions. Should the need arise, users can manually input opening balances in the Opening Balance Cash Flow (tfgld2118m000) session.

To set up the cash flow statement, use the following sequence of sessions:

  1. Group Company Parameters (tfgld0101s000): If you want to generate cash flow statements in any of the financial companies of the group, you must select the Cash Flow Statement check box.
  2. Reasons (tcmcs0105m000): Define reason codes for the sources and uses for cash that you want to distinguish. The Reason Type must be Cash Flow.
  3. Purchase Types (tcmcs2101m000): For the purchase types related to cash transactions, select the default cash flow reasons.
  4. Sales Types (tcmcs2102m000): For the sales types related to cash transactions, select the default cash flow reasons.
  5. Chart of Accounts (tfgld0108s000): For ledger accounts used for cash transactions, select the default cash flow reason in the Cash Flow Reason field. The ledger accounts must have level zero and must not be a text account, an intercompany account, or an integration account.


To enter and view cash flow transactions: Transactions that must be included in the cash flow statement must have a cash flow reason linked to them. For most transactions, ERP LN derives the default cash flow reason from the sales type, the purchase type, or the ledger account.

If you manually enter cash transactions, you can enter a cash flow reason. You can view cash flow transactions in the following sessions:

  1. Cash Flow History (tfgld2519m000): This session displays, for one cash flow reason, the opening balance, the closing balance, and the movement during one financial period.
  2. Cash Flow Transactions (tfgld1523m000): This session lists the transactions by cash flow reason.

In both sessions, on the Specific menu you can click Opening Balance to start the Opening Balance Cash Flow (tfgld2118m000) session. Use this session to view the calculated opening balances for a cash flow reason or to enter manually an opening balance, if necessary.


To print the cash flow statement: Use the Print Cash Flow Transactions (tfgld1419m000) to print the cash flow statement. You can print the report for one financial company and one fiscal year, and for a range of financial periods and cash transaction reasons.

To print the cash flow statement, use the following sequence of sessions:

  1. Cash Flow History (tfgld2519m000): On the Specific menu, click Cash Flow Transactions. The Cash Flow Transactions (tfgld1523m000) session starts.
  2. Cash Flow Transactions (tfgld1523m000): Click Print. The Print Cash Flow Transactions (tfgld1419m000) session starts.
  3. Print Cash Flow Transactions (tfgld1419m000): To print the cash flow statement, in the Report field, select Cash Flow Reason Transactions.


Other related KBs which would be helpful in Cash Flow process queries:
1998168 How to link child Cash Flow Reason Group to Cash Flow Reason

Previous Article Infor LX & BPCS Tip: What prevents tax from being calculated on a purchase order?
Next Article Planning for Growth – What you need to do first to be successful
Print
40438 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

Read more

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Read more
Last

Tips: LN | Baan

Users can personalize sessions and apply special formatting to the data displayed in sessions. The personalizations and formatting settings that are specified by the users are stored on the LN server. Administrators can maintain these settings.

  • Session personalizations

    Users can personalize sessions in various ways. users can, for example, hide fields, change labels, customize the toolbar, and move fields to another tab. Administrators can maintain the personalizations defined by the users. For example, an administrator can export personalizations to an XML file, import personalizations from an XML file, and copy personalizations to another user, to a DEM role, or to a company number.

  • Report personalizations

    You can use the Report Designer (ttstppersrep) to personalize the layouts and style of reports, without modifying the standard reports or using an external reporting solution. The changes are stored as personalizations.

    You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer (ttstppersrep), or modify them in Infor LN Studio.

    For details, see the Infor LN Report Designer Development Guide
     

  • Conditional formatting

    users can define conditions to apply special formatting to the data displayed in LN sessions. The users can define multiple conditions per session and different types of formatting, such as a specific color for particular fields or rows, and a warning symbol for particular rows. Administrators can maintain the formatting settings specified by the users and can define system-wide formatting settings.

Read more
  • If Finances is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that is linked to the purchase order line, and for which an internal invoice must be sent from the purchase office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.
Read more

Categories