Utilizing the TRG EDI Connector Net Change Report

 

If you are receiving 830 forecasts/schedules from your trading partners, you know how daunting it can be to figure out what has actually changed since the last time they sent you an update. If they are sending you updates multiple times per week (some send multiple times per day), it can be nearly impossible to keep up with the change activity to keep your system in sync.

In a traditional EDI integration/ERP setting, you bring in the new 830 schedule and wait for the next MRP run to tell you what actions, if any, need to be taken to handle any changes the customer has made to their schedule.

We have found that most of our clients wanted to know immediately what the impact of schedule changes will be even before the customer’s EDI is processed into their system. They can then be proactive with the customer and with their internal material planning well before the next MRP run.

The TRG EDI Connector includes a “Net Change Analysis Report” that is emailed every time an 830 is processed for one of your customers. This report analyzes the incoming 830 schedule, comparing it to the last time an EDI 830 was received for the combination of Customer, Purchase Order, Item and provides a succinct breakdown of net changes.

There are 5 exceptions reported on the Net Change Report:

  • Date Changes – these are determined by looking at the current release and comparing to prior releases within 6 days and noting the exception if just the date has changed.
  • Quantity Changes – these are determined by linking up to the prior release by date – if the quantity is different, an exception is reported.
  • Date and Quantity both Changed – if a date change is encountered, the report also checks if the quantity is the same or different – if both date and quantity have changed, this exception will be reported
  • New Release – if a new release is not matched up to any prior releases, this exception is reported
  • Dropped Release – if the release existed before, but is not in the current 830, this exception is reported

We have had customers request changes to the report to include:

  • Only report changes within the item’s lead time (lead time pulled from the ERP system); only Net Changes that occur within the part’s lead time are reported – changes outside lead time are ignored. If you are not concerned if the customer makes changes outside your standard lead time, this is a good way to eliminate a lot of “noise” on the report.
  • Dollarized impact of Net Changes – look up the selling price of the item and include unit and extended price as well as totals of the net changes.

The TRG EDI Connector Net Change report is a powerful tool to help you leverage your EDI integration investment and streamline how you manage customer change activity.

Below is an example of the TRG EDI Connector Net Change Report including an example of each type of exception:

temp