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:...

When there are two Cost Items, one with Release to Warehousing applied and the other with Release to Warehousing not applied, upon approval of the Sales Order, the Cost Item that is released to Warehousing will go straight to Staged status, pending Shipment confirmation, while the Cost Item that is not released to Warehousing will be up for Sales Deliveries.

Apart from this main difference in functionality between having and not having this option to release to Warehousing checked, there are other impacts to consider...

Is there a procedure for changing an item’s inventory unit? What conditions must exist before it can be done?

Once inventory transactions (receipts or issues) have occurred for an item, the inventory unit cannot be changed. If only orders have been placed against the item (sales or purchase), the inventory unit can be changed if these...

Changing an item from serialized to not serialized can only be done by unchecking the Serialized flag in session Item - General (tcibd0101s000). 
The conditions for this are:

• On Hand inventory is...

When a sales order is canceled, the outbound order line/advice cannot always be deleted because of the status. In that case...

How do I assign an unallocated payment to a purchase invoice when the document dates are not the same?

When trying to assign an unallocated payment, it is possible that the purchase invoice is not displayed in session Assign Unallocated / Advance Payments to Invoices (tfcmg2106s000), even though it is showing in the open entries. This can happen when the document date of the unallocated payment lies before the document date of the purchase invoice you want to assign it to. There are 2 ways to handle this...

You may be wondering if it's necessary to have separate item codes for incoming and outgoing subassemblies.

No, it is not necessary to have separate item codes for incoming and outgoing subassemblies, but it is recommended. In theory, you could have only one item code with the description subassembly and use the same item code for the outgoing subassembly and for the incoming subassembly. However, when monitoring inventory movements and financial integration transactions, it will be difficult to understand the process. Also, the costing logic is much clearer when different item codes for the incoming and outgoing subassemblies are used. Because of this, it is advised to use a different item code for the outgoing subassembly and a different item code for the incoming subassembly.

The porting set consists of the executables, located in the $BSE/bin directory, and shared libraries located in the $BSE/shlib. Apart from bug fixes, performance enhancements are...