Introduction

Grouping is a crucial feature when importing data with one-to-many relationships into Infor M3. This feature is particularly useful for managing orders and order lines, or items and item warehouse records. While Infor M3 typically stores such data across different tables, Excel represents this data in rows and columns. By applying grouping effectively, we can ensure accurate and efficient data import processes.

Importance of Grouping

When preparing data in Excel, many rows will share common data such as requested delivery date, warehouse and supplier etc... When we enable grouping on the columns, the VXL will look for identical data in each row for the columns where grouping is applied. This identical data will be considered as the order header, and the rows that belong to that particular order header will be considered as order lines and linked to the order header.

In below above example when grouping is applied on Batch, Supplier number, order type, Facility warehouse, Buyer, requested delivery date, the data is organized into groups that correspond to unique combinations of these fields.

For example:

• Group 1:
  • THB, SUPL001, M10, A01, 001, JANKIN84, 20240710
• Group 2:
  • THB, SUPL001, M10, A01, 001, JANKIN84, 20240717
  • THB, SUPL001, M10, A01, 001, JANKIN84, 20240717

We have faced an issue when Grouping is applied on DO order creation, and below is the solution to resolve the issue.

Problem

When creating DO orders, if the line items have an item status that prevents them from being purchasable, an error message is displayed for each line. If the "End Run" option is enabled, the last transaction executes only for the unique records count, resulting in misleading error messages.

For example:

• Consider two unique headers with different item statuses.
• If item1 is not purchasable, the error message appears for both lines even if only one has an issue.

Solution

To avoid this issue:

• Disable the "End Run" option on the last transaction.
• Pass each message line number to the last transaction.

This ensures each line is validated individually, displaying error messages only for the problematic items.