You can use a problem code to indicate that a problem exists for a sales invoice. If the invoice-to business partner notifies you about a problem with the invoice and does not pay it, you can link a problem code to the invoice.

In the direct debits procedure, problem invoices are automatically discarded. For each problem code, you can set an option to prevent linked invoices from being selected on reminder letters.

The audit server logs all database actions that change the contents of a table in so-called audit files. The Exchange module can use these audit files, which are useful in a multisite environment because the databases on all sites must have identical data. These audit files can also be used in data conversions.

Only the updates in a specific period are exchanged, which leads to an improvement in performance. Specify this period in the Export Data (Non-Regular) (daxch0233m000) and Export Data (on a Regular Basis) (daxch0234m000) sessions. Changes such as insert, update, and delete are processed and written into the ASCII files. Actions such as drop, clear, and create tables are ignored.

Audit control data is added to the resulting ASCII file. This data consists of a batchline ID, transaction ID, sequence ID, and an indicator. The control data is added at the beginning of each line and is formatted like other data fields such as the enclosing and separator characters.

An update writes two lines to the ASCII file. One line contains the key fields and old values of the updated fields. The other line contains the new values of the key fields and updated fields, even if a key field does not change.

The batchline ID is used for recognition when processing the ASCII files. The transaction and sequence IDs are used to ensure that the transactions are replayed in the same order as on the exporting site. The indicator defines the type of action that is executed on the table. Use the letter I to insert; use the letter D to delete; use the letter U to update with old values; and use the letter N to update with new values.

To determine which copying method you must use, answer question 1 and follow the instructions.

Question 1: Is the source component a project item (that is, is a project defined in the first segment of the item code)?

• If the answer is yes, proceed with question 3.
• If the answer is no, proceed with question 2.

Question 2: Is the target component a project item?

• If the answer is yes, select copy method NonProj Item to Proj Item.
• If the answer is no, proceed with question 4.

Question 3: Is there a relationship with the same project?

• If the answer is yes, select copy method EBOM to Production BOM Only.
• If the answer is no, proceed with question 4.

Question 4: Is there a relationship with the target item?

• If the answer is yes, proceed with question 5.
• If the answer is no, select copy method No Copy Action.

Question 5: Does the item exist already?

• If the answer is yes, select copy method EBOM to Production BOM Only.
• If the answer is no, select copy method Copy E-Item to Item.

Operations: Copying EBOMs - Which copying method should I use?

Technology: Using audit files in the Exchange module

Finance: Problem Invoices

In April 2025, Infor LN Cloud Edition release 2025.04 will introduce the deprecation of Windows® fonts in LN report design and output. This means that Windows fonts will need to be replaced by Google fonts.

Actions Required:

• All LN Cloud Edition customers must identify all reports modified with the LN report designer and update them by replacing the Windows fonts with Google fonts.
• Completed before the 2025.04 Maintenance Window.
• Please see Knowledge Base (KB) article 3523663 for more information, details and FAQs.

FINANCE: Use of Electronic Bank Statements

OPERATIONS: What is Statistical Inventory Control (SIC) and How Does It Work?

TECHNOLOGY: Archiving Data from tipcs300 and ticst300 Tables

1. Archiving tipcs300

• Using Session tipcs2260m000:
  • When archiving PCS projects, selecting the "Archive Financial data" option ensures that:
    • Records in tipcs300 are archived to the archiving company.
    • Records are deleted from the original company.
  • If records remain in tipcs300:
    • They may belong to projects that have not been archived.
    • The project may have been archived without selecting "Archive Financial data."
  • Verify there are no errors during the archiving process.
• Using Session tipcs3500m001:
  • The session "Delete Financial Transactions by Project" can delete records from tipcs300.
  • Note: This session is not for archiving; it removes records without copying them to the archiving company.

2. Archiving ticst300

• Using Session ticst0250m000:
  • The session "Archive Production Orders" allows:
    • Archiving and deleting records from the original company.
    • Only deleting records from the original company.
  • When executed:
    • Records in ticst300 associated with archived orders are removed.
    • Remaining records belong to unarchived orders.