The calendar is fresh, the resolutions are set, and the opportunities are endless!

But before you dive headfirst into tackling your to-do list, take a moment.

Pause.

Now is the perfect time to reflect and plan your ERP strategy.

What’s an ERP Strategy?

An ERP strategy is a roadmap for the steps you should take before, during, and after implementing an ERP system. It’s designed to ensure your ERP delivers on its promise of functionality and success—the backbone of running your business effectively.

Think of it like planning a road trip:

• Which cities will you visit?
• Where will you stay?
• What landmarks do you want to explore?

Without a plan, you’re winging it. While spontaneity might work for a vacation, it’s risky when it comes to your ERP system.

A poorly executed road trip might waste time or cause frustration, but a poorly executed ERP strategy? That can hinder your business growth, create inefficiencies, and lead to costly mistakes.

What if:

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

Users can now freeze period-end balances at the end of a fiscal period. You can now store the opening/ending on hand balance for each Inventory period at the Item (IIM), Warehouse/Item (IWI) and Lot/Location (ILI) levels. This information can then be used for inventory tracking and valuation purposes, as well as other ad hoc financial and audit reporting requirements. Infor LX clients can backdate inventory transactions into the immediate previously closed period, and thus update what was saved as the opening/ending balance throughout the current open period.