dynamics nav schedule release forecast
Post on 31-Dec-2021
2 Views
Preview:
TRANSCRIPT
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
1
SIKICH, LLP
EDI SCHEDULE-RELEASE-FORECAST MICROSOFT DYNAMICS NAV 2015
Setup and Processing Guide
Note: This Add-on is available in English (United States) only. Please contact Sikich if you are interested in
localizing the solution to your region.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
2
TABLE OF CONTENTS
TABLE OF CONTENTS ................................................................................................................................... 2
INTRODUCTION ............................................................................................................................................. 3
SETUP AND ADMINISTRATION .................................................................................................................... 5
E.D.I. 830 Setup .............................................................................................................................. 6
E.D.I. Packaging Codes ................................................................................................................. 10
E.D.I. Supplier Cross References .................................................................................................. 11
E.D.I Cust. Cross References ........................................................................................................ 13
E.D.I. Trade Partner 830 and 862 Document Setup ................................................................... 14
Mapping the E.D.I 830 & 862 Documents .................................................................................. 16
PROCESSING OF 830 AND 862 ................................................................................................................. 18
Schedule Release Forecast .......................................................................................................... 25
E.D.I. 830 Schedule Releases ...................................................................................................... 32
E.D.I. 830 Schedule Release Card ............................................................................................... 33
Schedule Event Log ....................................................................................................................... 34
SCHEDULE-RELEASE-FORECAST EDI 830 PROCESS FLOW DIAGRAM ................................................ 35
SCHEDULE-RELEASE-FORECAST EDI 830-862 PROCESS FLOW DIAGRAM ........................................ 36
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
3
INTRODUCTION
The Schedule-Release-Forecast (SRF) functionality provides the capability to import customer product demand
forecasting and release schedules in Microsoft Dynamics NAV. In simple terms, this is accomplished by capturing
and tying the Forecasts and Shipments from the EDI 830s and 862s to Dynamics NAV Production Forecasts and
Planning Engine.
The SRF process imports an EDI 830 document sent by a Trade Partner and creates a Production forecast that
can be used by Dynamics NAV MRP-MPS to create production orders on items that are built. When a ‘Firm’
release is given (either on the 830 itself with a ‘Firm’ indicator or on a separate EDI Document – 862), the
demand is moved from production forecast to true orders.
On items that are manufactured, SRF also calculates the demand of the components and generates the
outbound EDI 830 Schedule to the component vendor. For vendors that are not EDI, SRF provides the ability to
generate the Vendor Forecast as an Excel export from NAV.
A special menu called ‘E.D.I. Forecasting’ provides access to the SRF Administration, Processing and Reporting
functions. One of the very helpful pages in the E.D.I. Forecasting menu is the ‘Schedule Release Forecast’ Page
which provides users the ability to review the detailed schedule of Planned and Firm requests by the customer.
The SRF interface provides easy navigation and quick references to all the key information related to Sales, Item
and Forecasts. It also keeps track of shipments to the customer and outstanding quantities. The page also allows
the users to make modifications/tweaks to the delivery quantities if needed to handle exceptions.
The SRF engine also has the ability to calculate and track Accumulated Release-Shipment quantities sent by
large scale Trade Partners such as FORD and GM.
Quick background on EDI documents
(850) Purchase Order: Inbound Purchase Order creates Sales Order.
(856) Advanced Ship Notice: Outbound Advanced Ship Notice mapped from the Bill of Lading and package
detail.
(830) Forecast: Inbound Planning Schedule creates Sales Order, Blanket Order, or Quote.
(862) Release: Inbound Shipment Schedule creates a Sales Order for items that are to be shipped.
Relation between 850-830-862
The cycle typically starts with the company receiving a Purchase Order from the Trade Partner. This is document
850 - Sales Order for the company.
In a basic EDI setup, the 850 is brought into Dynamics NAV as a sales order. This means that in terms of EDI
mapping, the 850 document is mapped directly to the Sales Header and Line tables.
In more advanced scenarios, the company receives either 830 (with both Firm Releases and Forecasts) or a
separate 830 (with just the Forecasts) and 862 (with Firm Shipment Releases) from their Trade partner in
addition to the initial 850. When the company receives an 830, the 850 usually just denotes start of the contract
and no documents are created in NAV based on 850. When the 830 is received, the forecast schedule is created
in NAV. Many times the 830 functions as both the Forecast and the Release document in which case the Blanket
Sales Orders and Sales Orders are also created based on the Firm Releases on the 830. For example, Caterpillar
(CAT) sends a firm indicator on the 830 (“F”). That is what marks the schedule line to create a sales order.
If the company receives separate documents for Forecast (DELFOR, 830) and Shipment Releases (DELJIT, 862),
The Release (DELJIT, 862) creates a sales order or updates existing sales order(s). The details of 830 & 862 set
up and processing are covered in the ‘Setup and Administration’ and ‘Processing of EDI 830 & 862’ chapters.
E.D.I Cycle
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
4
The processing is of EDI 850, 830, 862 and 856 is as follows:
1. EDI 850 is received from the Customer (Trading partner)
If the company directly receives 850 from the customer with no Forecast or Release documents, the
processing of 850 creates the Sales orders in NAV.
If the company receives 830 or both 830 and 862, the processing of these documents creates the
sales documents in NAV. If the 850 is currently mapped to create sales orders, the ‘Navision
Document’ field for the 850 Document needs to be changed to ‘I_SLSGEN’ to make the 850 a generic
Sales document that does not create Sales Orders.
2. EDI 830 is received from the Customer
EDI 830 updates the Schedule Release Header and Schedule Release Lines in Dynamics NAV. If Firm
demand is received on 830 as a ‘Firm’ indication, then Blanket Sales Orders and Sales Orders are
created in NAV. The Schedule Release Forecast (SRF) Page in NAV provides a detailed view of the
Forecasts and Releases along with the calculation of component forecasts.
3. EDI 862 is received from the Customer
If Firm demand for the releases is received on separate 862 Release document, then Blanket Sales
Orders and Sales Orders are created in NAV based on the 862.
4. Regular Manufacturing, Warehousing, Pack Line Scanning & Shipping processes are performed in NAV
These are performed according to the company’s regular business workflow.
5. EDI 856 is sent to Trading Partner upon Shipment
Once the Sales Order is shipped, the regular 856-ASN process is performed from the Bill of Lading in
NAV which generates and sends the EDI 856 to the Customer.
6. EDI 810 is sent to Trading Partner upon Invoicing
Once the Sales Order is invoiced in NAV, the EDI 810 – Sales Invoice is sent to the Customer.
Please refer to ‘Schedule-Release-Forecast EDI 830 Process Flow’ and ‘Schedule-Release-Forecast EDI 830
862 Process Flow’ diagrams at the end of this document.
The objective of this document is to explain the Setup and Processing of EDI 830 and 862 in the context of
Schedule Release Forecast. It is assumed that the user-reader has good understanding of the basic Lanham
NAV EDI functionality.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
5
SETUP AND ADMINISTRATION
A new Menu titled ‘E.D.I. Forecasting’ has been added to the Navigation Pane. This menu contains the SRF
specific Setup, Processing and Reporting functions.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
6
E.D.I. 830 SETUP
In the E.D.I. 830 Setup Page, we define the key settings for the SRF 830 process.
EDI 830 No. Series
Create a No. Series in NAV for EDI 830 and select that No. Series in this field.
Current Forecast
This field ties the 830 forecasts to the Production forecast in NAV. Once tied to the NAV Production forecast,
the forecasts get taken into account in NAV’s planning engine when calculating MRP and MPS.
Component Forecast
This field is primarily for supporting outbound Component forecasts to vendors. This can be done via Outbound
E.D.I. 830 or Excel output.
Please Note: As standard Best Practice, the Component Forecast should be different from the Current
Forecast. The MRP function in NAV only looks at one Forecast so component demand will come from NAV’s
standard process of ‘blowing out’ the components in the BOMs of the Finished Good forecast.
Location Code
Select the default Location Code. The Sales Orders and Schedule Release Forecasts will get created with this
location code.
Please Note: SRF also creates a special field called ‘Default Location’ on the Item card under the Forecast fast
tab. A default location can be assigned here for the Item. If the Default Location is not set at the Item level,
then the process will use the Location Code on the E.D.I. 830 Setup card.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
7
Auto Create Sales Blanket
Placing a check-mark on this field triggers automatic creation of Blanket Sales Orders for Firm Releases on the
830 or 862.
Auto Create Purchase Blanket
Placing a check-mark on this field triggers automatic creation of Blanket Purchase Orders for
items/components based on the demand requirement on the 830s if a Vendor No. is assigned on the Item
card of the component items.
Maintain Blanket Order
If this field is check-marked, the system validates if a Blanket Sales Order already exists for the associated
Schedule Release Header for the Customer No., PO No., Ship-To Code, Item No. and Location Code during the
Forecast and Shipment Import process.
Vendor Forecast Export Path
Specify the file path for creation of Excel File of Vendor Forecasts. This is not a mandatory field for SRF 830
Import. It is only used if the Vendor Forecasting granule has been purchased.
Use Buyer Part as Item No.
Place a check-mark if the Item No. (Part No.) in NAV matches the Trade Partner’s Part No. If NAV Item No. does
not match the Trade Partner’s Part No., then the 830 Item/Part No.s are handled by SRF in the following ways:
The 830 Item is identified based on the ‘Vendor Part No.’ if sent by the Trade Partner on the
830.
The Trade Partner’s Part No. for the 830 Item is specified on the ‘No. 2’ field on the Item
Master Table in NAV. Below is an example of the Item setup with the Trade Partner Part No.
specified in the No.2 field.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
8
The logic behind SRF’s specific Item Cross Referencing design is based on the fact that when a company
receives forecast schedules for an Item from a customer, typically these items are very specific/custom builds
for that customer. So in most scenarios, the Item in NAV is directly linked to Trade Partner’s Item No. either by
having the same Item No. as the Customer’s or through the No.2 field.
Append Engineer Change No.
A check-mark in this field will automatically append the EC No. on the 830 to the Item No. So if the Item No. on
830 is ABC001 and the EC No. on the 830 is 02, then with this option check-marked, the system adds ‘/02’ or
‘-02’ to the Item No. which makes the Item No. ABC001/02 or ABC001-02. The extension character is based
on the setting in the ‘Engineer Change Extension Char.’ Field. The forecast import process looks for an exact
match of the ‘Item No.-EC No.’ combination in NAV Item Master table. If the ‘Item No.-EC No.’ does not exist in
NAV, the 830 import process will display an error. The process follows the same logic with looking for the ‘Item
No.-EC No.’ combination based on the ‘No.’ field first and then the ‘No. 2’ field on the Item Master table.
Engineer Change Extension Char
Used when ‘Append Engineer Change No.’ field is check-marked. The two options are ‘/’ and ‘-‘. By default, the
system uses ‘/’ as the extension character.
Forecast Quantity Change Notification
This is a notification function that uses the settings in the “Warning Notification Email” and “Date Notification
Window”. SRF sends an email if an email address is entered in the “Warning Notification email” AND the SMTP
email is setup in standard NAV. As Best practice, it is recommended to create an email group to send the
notification to.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
9
If a change in quantity between the current work date and the “Date Notification Window” is identified, the
system will create a notification email as shown below. The email content will be structured according to the
data. For example, the following fields are only in the email if they are not blank - “Engineering Change No.”,
“Ship-to Code”, “Supplier Code”, “ASN Facility”, “Sales Order No.”
Forecast Threshold Deviation % and Forecast Deviation period
These fields highlight changes between schedule receipts.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
10
E.D.I. PACKAGING CODES
If specific Packaging Codes need to be sent on the 856 (typically on the TD1 and CLD Segments), SRF provides
an option for selecting the E.D.I. Packaging Code during Pack Line Scanning when //cp or //cpp commands are
issued. This page is used to set up all the applicable Packaging Codes. To enable the functionality for selecting
the Packaging Code on Close, place a check-mark on the ‘Enter Packaging Code on Close’ option under the E.D.I.
Forecasting fast tab on the Packing Rule Card.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
11
E.D.I. SUPPLIER CROSS REFERENCES
This is a special Cross Reference table in SRF designed to handle 830s for multiple facilities (set up as Ship-To
Addresses in NAV) coming under one ‘Umbrella’ Facility code where the ASN needs to be sent to the respective
individual Facility code.
Departments>> Electronic Data Interchange>> Administration>> E.D.I. Trade Partner. Click Supplier Cross
References on the Ribbon.
Some Trading Partners such as Caterpillar (CAT) send 830s for multiple facilities under one umbrella Facility
code. The Facility code is identified in the ISA & GS envelope segments of the 830. When the order for each
individual facility is shipped, the ASN (& subsequently the 810) has to be sent to the respective facility with its
Envelope identification although it may have come under a different (Umbrella) facility code on the 830. The
E.D.I. Supplier Cross Reference table effectively handles this scenario by providing the ability to set up the
individual ASN facilities under the Umbrella Facility Trade Partner.
In the example below, CAT sends 830 for multiple facility codes – 11, 12, 13, 92 under one Umbrella Facility 39.
An E.D.I. Trade Partner card is created for the Umbrella Facility 39 and all the individual ASN facilities that come
under 39 are listed along with their respective envelope addresses in the EDI Supplier Cross Reference Page.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
12
With this setup, when the orders are shipped to each individual facility, the 856 (ASN) is generated and sent to
the individual facility - 11, 12, 13 and 92.
Note: If the Trading Partner does not use Umbrella Facility codes, only one record needs to be created in the
E.D.I. Supplier Cross Reference table to identify the envelope address for the Customer (E.D.I. Trade Partner)
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
13
E.D.I CUST. CROSS REFERENCES
Set up the Customer Cross references to identify the Customer No. and Ship-To codes for the Trade Partner. As
best practice, the ‘Navision Shp To Code’ should match the ‘EDI Ship To Code’.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
14
E.D.I. TRADE PARTNER 830 AND 862 DOCUMENT SETUP
As the first step, the Inbound 830 and 862 documents need to be created for the E.D.I. Trade Partner.
Departments >> Electronic Data Interchange >> Administration >> E.D.I. Trade Partners. Select the E.D.I.
Trade Partner card and click ‘Documents’ on the Ribbon. Click New.
830: Navision Document: ‘I-FORECAST’
EDI Document No.: 830
Version: Match with other EDI Documents for the Trade Partner
Interface File: Specify a Unique identifier for the Trade Partner & Document
EDI Template Code: Select the appropriate template for the Trade Partner
862: Navision Document: ‘I_SLSSHSCH’
EDI Document No.: 862
Version: Match with other EDI Documents for the Trade Partner
Interface File: Specify a Unique identifier for the Trade Partner & Document
EDI Template Code: Select the appropriate template for the Trade Partner
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
15
Shown below are the E.D.I. 830 and 862 documents in the Trade Partner E.D.I Documents List.
Additional Note: With SRF, there isn’t a need to have any of the options check-marked under the ‘Forecast
Release’ Fast tab of the 830 and 862 documents. The logic for tying and matching Releases and forecasts is
already built into the functionality.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
16
MAPPING THE E.D.I 830 & 862 DOCUMENTS
As with other E.D.I. Documents, the mapping for 830 and 862 is done according to each Trade Partner’s
specifications. A sample 830 and 862 document is provided with SRF as reference. The important aspects of
SRF 830 mapping are explained below:
SRF functionality brings the Forecast and Release schedules into the Schedule Release Header (SRH)
and Schedule Release Lines (SRL) tables in NAV. So the E.D.I. Elements and Conditionals mapping will
be to the SRH and SRL tables. As example, the screenshots below show the E.D.I Element mapping of
the BFR Segment, the E.D.I. Conditional mapping for the LIN-03 element and the E.D.I Element
mapping for FST segment in the 830.
E.D.I Element mapping for BFR Segment of the 830
E.D.I. Conditional mapping for LIN-03 Element of the 830
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
17
E.D.I Element mapping for FST segment of the 830
SRF has logic built in to identify the Firm lines on 830 (DELFOR) and trigger the creation of Sales
Orders and Blanket Sales Orders. If the company receives 862 (DELJIT) for Shipment Releases, the
Sales Order creation is triggered on the processing of 862.
The ‘Trigger’ for Sales Order creation is in the FST Segment of the 830 and 862. The ‘Trigger’ needs
to be on the last element where all of the fields that make up the line record have been mapped and
accounted for. This rule applies to other E.D.I Document mappings as well.
If a separate Shipment Release – 862 (DELJIT) is received, SRF ties the shipment to the forecast
based on a match of the Date. The Release Date is assumed to be a release between two Schedule
dates on the Forecast. The Sales Order is created based on the Release Date on the 862 and the EDI
830 schedule release lines are adjusted to connect the two documents.
For the 830, the Quantity field on the FST segment is mapped to the ‘Source_Outstanding_Qty’ field of
the Schedule Release Line Table. For the 862, the Quantity field on the FST segment is mapped to the
‘Release_Quantity’ field of the Schedule Release Line Table.
E.D.I. Element mapping for FST Segment of the 862
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
18
PROCESSING OF 830 AND 862
The initial processing of 830s and 862s is done the same way as with other E.D.I. Documents.
1. Go to EDI>> Processing>> File Cabinet or type ‘File Cabinet’ on the Search box on the top right-hand
side and select the page.
2. Click ‘View Common Rec. Files’. All incoming EDI files will first reside in the Common Receive folder.
You will see the files waiting to be processed. The example below shows the processing of a sample
830 from Caterpillar (CAT)
3. Click ‘Process All Common Rec. Files’.
4. Once the files are processed from the Common Receive folder, the system creates the necessary files
in the Inbox.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
19
5. Next, click ‘View Inbox Docs’.
Please Note: Multiple Inbox files may be created for one EDI 830 file in the Common Receive folder
depending on the number of Ship-To addresses in the file. The example below shows the list of files that
were created in the Inbox after processing the single Common Receive file shown above.
E.D.I. Inbox Files
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
20
6. Click ‘Process Single Inbox File’ or ‘Process All Inbox Files’
Note: You have the option ‘Process Single Inbox file’ if you want to select a specific file to process. In
general, it is best to select ‘Process ALL Inbox files’ to be sure all incoming files get processed into NAV.
Click Yes on the Confirmation window.
You will see the progress window importing and creating the forecast lines for each Inbox file.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
21
After the Inbox file/files are processed, the Inbox Files window will be empty. The system will also
automatically generate and send a functional acknowledgment for the 830 (if it is set up to automatically
send functional Acknowledgement)
7. The imported 830s and 862s are listed in the Receive Documents Page. (Departments >> Electronic
Data Interchange >> Processing >> Receive Documents) To get a quick snapshot of the Sales Orders
created for an 830 or 862, select the Receive Document on the list and view the ‘Sales Document
Created’ Factbox on the right-hand side. It shows the Sales documents that were created in NAV based
on the processing of the Forecast-Release document. You can click on the ‘No.’ field to open the Sales
Document.
For an incoming EDI 830 forecast file, the following documents/records are created in NAV:
1. Blanket Sales Orders for ‘Firm’ lines
2. Individual Sales Order for ‘Firm’ lines for each Shipment Date.
3. Schedule Release Forecast
8. View the sales documents and Schedule Release Forecast lines records:
Blanket SO: Departments >> Sales & Marketing >> Order Processing >> Blanket Sales Orders OR
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
22
Click the ‘No.’ field on the Receive Documents Factbox as shown above.
Sales Orders: Departments >> Sales & Marketing >> Order Processing >> Sales Orders OR
Click the ‘No.’ field on the Receive Documents Factbox as shown above.
Schedule Release Forecast: Departments >> E.D.I. Forecasting >> E.D.I 830 Schedule Releases
Note: You can always find & navigate to these Pages using the NAV Search box.
Please Note:
In this example, the Item No. is identified based on the value in the ‘No.2’ field of the Item Card which
matches the Trade Partner’s Part No.
Below is Blanket Sales Order 1002 created from the above 830 document.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
23
Below is the Sales Order created from the 830.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
24
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
25
SCHEDULE RELEASE FORECAST
The Schedule Release Forecast page is a very helpful and powerful interface to view the Schedule Releases
and Forecasts from the Incoming 830s and 862s.
It is located under the E.D.I. Forecasting Menu - Departments >> E.D.I. Forecasting >> Schedule Release
Forecast or search and navigate through the NAV Search Box
The Schedule Release Forecast (SRF) Page provides both a High level Summary View of the Schedule Releases
and Forecasts as well as the detailed line level visibility to each Item.
At the Summary level, the SRFs are grouped based on Source Type.
The SRFs for the main Sale Items/Parts are grouped by Customer
The SRFs for the components are grouped by the Vendors (if Vendor No. is assigned on the
component Item card).
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
26
Vendor assignment on the Item card is shown below
The Customer and Vendor Source Types can be expanded to view the individual Items. Click the Expand button
located on the left of each Source Type or click ‘Expand All’ on the SRF Ribbon.
Schedule Release Forecast Header
The Header shows the Item No., Release No., Location Code, Forecast Generation Date, Forecast Horizon Start
and End Dates for each Customer/Vendor and Ship-To Code.
Select the individual Item row to view the detailed Scheduled Release and Forecast lines for that Item. The
Schedule Release Lines for the item are displayed on the Schedule Release Lines section of the Page.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
27
Schedule Release Lines
The Lines contain the details of the Schedule – the Shipment Dates, Quantity, Firm or Planned, Quantity
Shipped, Outstanding Quantity, Accumulated Quantities (where applicable). The Schedule Release lines can
track many quantity related fields depending on the nature and complexity of the Trade Partner’s Schedule
Releases and Forecasts.
The Schedule lines for the Main Sale item shows the actual quantities from the 830. The SRF for components
are calculated based on the BOM and the settings under ‘Planning’ and ‘Replenishment’ tab of the component
Item card.
Schedule Release Accums FactBox
The Factbox on the right hand side of the Schedule Release Forecast Page
shows key information about the SRF record as calculated in the Schedule
Release Lines.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
28
Schedule Release Forecast Ribbon
Expand All and Collapse All: Use to Expand or Collapse all the SRF Source Types.
Item Unit of Measure: Opens the Items Unit of Measure for the selected Item.
Show Component Prod. Forecast: Shows the Production Forecast Matrix for Items
Send Vendor Forecast: Generates and Sends Vendor Forecast for the selected Vendor on the SRF Page. To
enable this functionality, the ‘Maintain Outbound Forecast’ field needs to be check-marked on the Vendor card.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
29
Export
Vendor
Forecast:
Generates and exports Vendor Forecast for the
selected Vendor on the SRF Page as an Excel file.
Export ALL Vendor Forecasts: Generates and exports
Forecast for all the Vendors on the Schedule
Release Forecast as an Excel file.
Reset Vendor Allocation: This function takes the
vendor schedule and updates the schedule dates
with any receiving activity that has happened since
the schedule was created. If the schedule is
updated nightly due to frequent customer forecasts
coming in then this function doesn’t need to be used
as much. But in a scenario where a vendor schedule
only gets updated monthly when a monthly inbound
customer schedule is updated, this routine keeps
the vendor side updated with current activity from
PO receipts.
Cancel Latest Release: Finds the 830 Schedule Release Header that is marked as current, delete it, mark the
most recent prior to that as current, and run the update routines to make the production forecast match that
document. This is not a function that would be run as part of daily activity but is a helpful tool for adjusting and
re-aligning forecasts in case of exceptions.
Create Expedite Lines: Creates manual entries for delivery. It adds a new shipment date entry to the Schedule.
This is to handle scenarios where a customer makes a call for a rush delivery and want the shipment before
the next EDI might be processed.
Delete Schedule: This function is used to reset/clear the schedules.
Update Accums: ‘Accums’ stands for Accumulated Quantities. This window displays a snapshot of the Schedule
Release Accums for Trade Partners who send Accumulated Quantities on the 830. For example, FORD, GM etc.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
30
Process and interface for Shipment Releases – (862, DELJIT)
All of the above steps apply to 862 as well. On the Receive Documents Page, the 862 is listed as EDI
Document = 862 and Navision Document = I_SLSSHSCH with links to the corresponding Sales Documents.
On the Schedule Release Forecast Lines, the ‘Release’ field is automatically check-marked for the 862.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
31
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
32
E.D.I. 830 SCHEDULE RELEASES
This is a history screen to review the Schedule Release Header and Lines information. It is similar to the
Schedule Release Forecast Page but created primarily for Inquiry and History review. It is accessed from the
E.D.I. Forecasting Menu. Departments >> E.D.I. Forecasting >> E.D.I. 830 Schedule Releases or search and
navigate through the Search Box
The E.D.I. 830 Schedule Release List shows the Release Schedule for the Primary Sale Item as well as its
components.
Select the individual record and click ‘Card’ on the Ribbon to open the E.D.I. 830 Schedule Release Card.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
33
E.D.I. 830 SCHEDULE RELEASE CARD
The E.D.I. 830 Schedule Release Card consists of Schedule Release Header and Schedule Release Lines
associated with it.
Schedule Release Header
The Header contains the Item No., Release No., Location Code, Forecast Generation Date, Forecast Horizon
Start and End Dates. The Current Release field is automatically check-marked if the document contains a
current Firm release.
Schedule Release Lines
The Lines contain the details of the Schedule – the Shipment Dates, Quantity, Firm or Planned, Quantity
Shipped, Outstanding Quantity, Accumulated Quantities (where applicable). The Schedule Release lines can
track many quantity related fields depending on the nature and complexity of the Trade Partner’s Schedule
Releases and Forecasts.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
34
SCHEDULE EVENT LOG
The Schedule Event Log records the main Events along with the Creation Date and Key information such as the
Purchase Order No. and Item No. It provides a quick and convenient snapshot of the Forecasts and Releases
that have been processed in the system.
Conclusion
The objective of the Schedule Release Forecast functionality is to provide enhanced Manufacturing and Supply
Chain Planning capabilities by integrating the data contained in our Customers’ Forecasts and Shipment
Releases with the Dynamics NAV Production Forecasting and Planning Engine. It effectively leverages and
smoothly integrates with standard Dynamics NAV as well as Lanham E.D.I & ESHIP functionalities.
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
35
SCHEDULE-RELEASE-FORECAST EDI 830 PROCESS FLOW DIAGRAM
Sikich, LLP Schedule Release Forecast
Dynamics NAV 2015
36
SCHEDULE-RELEASE-FORECAST EDI 830-862 PROCESS FLOW DIAGRAM
top related