EDI Schedules

EDI schedules for a part/delivery location are transmitted by messages that are contained in a file.  Depending on the flag that is set on Reference File category G52, Firm Horizon, EDI schedules support the firm horizon.  If the flag is set to Yes, (the firm horizon is handled by Repetitive Supply), the first period transmitted for schedules is equal to the greater of either today’s date + 1 or the last firm horizon + 1.

A new firm horizon is calculated whenever a firm schedule is sent; it is also updated on the Part Master File (DE100M).  It is calculated as follows:

Firm Horizon Date = Date of the Schedule Confirmation + Total Fixed Lead Time Days

Note the following about firm horizons:

·     The firm horizon date may be adjusted to the last day of the week based on the PO generation mode.

·     This firm horizon date is then stored on the Part Master File (regardless of the vendor) for purposes of Repetitive Supply firm horizon processing.  Releases after the previous firm horizon will be included on the schedule.

Up to 32 periods and release natures can be transmitted on DELINS schedules.  The periods and release natures are defined on Reference File category G54, EDI Schedule Periods.  For RS VDA parts, this information is taken from the appropriate fields on the effective endorsement, overriding Reference File category G54.  You may define the periods to represent either days or weeks.  PO releases are accumulated into weekly periods.  Note that you must not intersperse daily and weekly periods.  You must define all daily periods before you define any weekly periods. 

EDI Schedule Example

Assume that Reference File category G54 has been set up as follows:

If the EDI schedule is transmitted on Tuesday, April 5, it will appear as follows:

For EDI schedules, weekly natures that run for the duration of a week can only begin on a Monday.  (See the last line in the above table.)  Although Friday, Saturday, and Sunday in the above example were assigned weekly natures, you can see that they are for daily periods only.  

Planners can request draft paper schedules that show both scheduled quantities and variances.  This allows planners to monitor what has been sent to the vendor.

A control report is generated along with messages that indicate either a valid schedule or invalid data.  The control report specifies:

·     The transmission date and time

·     The vendor

·     The message number (date, time, and sequence number)

·     The number of records

·     The number of ARD segments of the message (This is formatted for ODETTE schedules only)

·     Error messages

Purging Records from Files

The RS ANSI Schedule File Translation Update Program (RS040E) updates the individual ANSI schedule file records, marking the Translation Status field with a “P” (processed) and stamping the date and time the record was updated.  All records that have a blank status field are updated with a status of “P” indicating that the records have been processed by the transmitter and have been sent via EDI.  This program should be used once the schedules have been successfully translated using a third party translation software package.  If these programs are run before the schedules have been translated, the record(s) will not be transmitted to the vendor.  

Once the translation program has been run, the transaction file can be purged.  The RS ANSI Schedule Purge Program (RS050E), which can be accessed through the File Support Menu, purges records from the ANSI Schedule File (RS645AP).  The purge program will only purge records that have a translation date prior to the horizon date and have a “P” in the Translation Status field.  If you leave the horizon date blank, all processed records will be purged.

Note:    You must manually purge records from the RS ODETTE Message Work file (RS640AP) and the RS VDA Message file (RS640M).