This enhancement provides search capabilities on segment value description in Segment Value List window (WINGSVD).

Segment Value List (WINGSVD):

• Converted to a standard subfile
• New action code 10=Search

This makes it easier to locate segment values when defining segment values in Model Account Builder or Alias definition. In addition, WINGSVD has been redesigned as a subfile to enable WebTop grid capabilities.

This enhancement allows reconciled payables and payments to be retained in the system for over 200 years. It extends the retention period in A/P Application Control Maintenance (ACP180) to support up to five digits. This gives LX customers the ability to retain data online for significantly longer durations.

FINANCE: Increase A/P Retention Day

TECHNOLOGY: Search by Description in Segment Value List

OPERATIONS: IDF Customer Order Inquiry Enhancements

We’re standing in the middle of the Fourth Industrial Revolution—Industry 4.0—a transformation that’s redefining how products are made, moved, and managed. But many companies are still operating with Industry 3.0 systems: digitized, yes, but not yet intelligent, connected, or adaptive.

So, what makes Industry 4.0 different? And more importantly—where does your company stand in this transformation?

Automation to Intelligence: The Shift from Industry 3.0 to 4.0
Industry 3.0 introduced computers, electronics, and early automation into manufacturing. It marked the beginning of digital systems and the rise of Manufacturing Execution Systems (MES) as a bridge between planning and the shop floor. Industry 4.0 takes it further: it brings interconnectivity, real-time data, and AI-powered intelligence into every corner of the industrial environment. It’s about smart factories, self-optimizing systems, and predictive capabilities that weren’t possible before.

8 Pillars of Industry 4.0:

1...

Learn all this and more in our webinar -Thursday, March 20th at 1:00 PM Eastern / noon Central.

Presenter: Nick Olson, Crossroads RMC Solutions Consultant

In this session, we will explore customizing the User Interface:

• Want to see only the objects you need?
  • Build a Card!  
• Constantly recreating the same filter row criteria?
  • Build it into a Subset!  
• Too many irrelevant or not enough pertinent columns of data?
  • Build a custom View!  
• Need to draw attention to a particular piece of information?
  • Build a Presentation Scheme!  
• Tired of scrolling back and forth to see key data?
  • Freeze columns!  
• Need to add and view attachments?
  • Build an Attachment Viewer Card!

Register TODAY: https://ibmi.workoutloud.com/Event/dive-into-idf-for-lx-part-2

FINANCE Tip: Remap Posted Integration Transactions (tfgld4282m100)-

OPERATIONS Tip: Using Country of Origin for Purchase Orders-

TECHNOLOGY Tip: Impact of Configuration Changes on Audit Trails-

Impact of Configuration Changes on Audit Trails

The impact of changes in the audit settings varies depending on the specific circumstances. The issues typically arise when changes made to audit settings are implemented at runtime without requiring all users to exit the system (LN). As a result, some users may continue to generate audit trails using the old configuration, while those who log in after the changes take effect will create audit trails based on the new configuration.

Changes in User Profiles

Below is a summary table that illustrates the effects of these changes for a specific table within a company:

For purchase orders, information about the COO allows you to track the related import duties, tariffs, and compliance with sourcing requirements. You can maintain the COO of an item when creating an order or the release level of a purchase order.

When you create a purchase order line in the Purchase Order Lines (tdpur4101m000) session, the COO related details are defaulted based on the item-purchase data defined in the Items - Purchase (tdipu0101m000) session. To view this data, you can use the Country of Origin option from the References menu in the Purchase Order Lines (tdpur4101m000) session.

After the order line is released to Warehousing, an inbound line is created in the Inbound Order Lines (whinh2110m000) session with the COO information. A receipt line is created in the Warehouse Receipt Lines (whinh3512m100) session when the inbound order line is received. To view the actual COO for the item specified on the receipt line, you can use the Country of Origin option from the References menu in this session.

You can view the country of origin (COO) data for the inventory received in a warehouse in the Item - Country of Origin Inventory (tcitu6600m000) session based on the data specified in the header section such as, warehouse, item, and so on.

In the Inventory Tracking Receipt (tcitu2610m000) session, you can view the information related to the purchase order, inventory quantity, and actual COO of the item. You can use the Intrastat Transactions (tccom7171m000) session to view the COO that is reported for an order line and is used for the Intrastat declaration.