Anda di halaman 1dari 38

Epicor ERP

Demand Management Course


10.0.700.2

Disclaimer
This document is for informational purposes only and is subject to change without notice. This document and its
contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its
date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with
regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a
particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is
likely to be unique in their requirements in the use of such software and their business processes, users of this document
are always advised to discuss the content of this document with their Epicor account manager. All information contained
herein is subject to change without notice and changes to this document since printing and other important information
about the software product are made or published in release notes, and you are urged to obtain the current release
notes for the software product. We welcome user comments and reserve the right to revise this publication and/or
make improvements or changes to the products or programs described in this publication at any time, without notice.
The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of
any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage
of the solution(s) described in this document with other Epicor software or third party products may require the purchase
of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements
in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws
and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly
Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of
platform and product compatibility in this document shall be considered individually in relation to the products referred
to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also
stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible
with both of the products running at the same time on the same platform or environment. Additionally platform or
product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and
Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs
released by third parties after the date of publication of this document. Epicor is a registered trademark and/or
trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other
trademarks mentioned are the property of their respective owners. Copyright Epicor Software Corporation 2014.
All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of
Epicor Software Corporation.

ED838905
90521-10-9234-58310702
10.0.700.2
Revision: July 25, 2014 2:03 a.m.
Total pages: 38
course.ditaval

Demand Management Course

Contents

Contents
Demand Management Course...............................................................................................5
Before You Begin....................................................................................................................6
Audience.........................................................................................................................................................6
Prerequisites....................................................................................................................................................6
Environment Setup..........................................................................................................................................7

Demand Management Overview..........................................................................................8


Application Setup...................................................................................................................9
Company Configuration..................................................................................................................................9
Maintenance Programs..................................................................................................................................10
Customer Periodicity Maintenance..........................................................................................................10
Terms Maintenance................................................................................................................................11
Customer Maintenance..........................................................................................................................12
Demand..........................................................................................................................................13
Documents......................................................................................................................................13
Demand..........................................................................................................................................14
Part Maintenance...................................................................................................................................14
Workshop - Create a Customer Part................................................................................................16
Carrier Maintenance...............................................................................................................................16
Ship Via Maintenance.............................................................................................................................17
FOB Maintenance...................................................................................................................................17

Daily Demand Processing.....................................................................................................18


Demand Contract Entry.................................................................................................................................18
Workshop - Enter a Demand Contract....................................................................................................19
Create a Demand Contract..............................................................................................................19
Enter Contract Lines........................................................................................................................19
Demand Entry................................................................................................................................................20
Workshop - Create and Define the Demand Schedule.............................................................................22
Establish Begin and End Dates.........................................................................................................22
Create Demand Lines......................................................................................................................23
Create and Define a Demand Schedule............................................................................................23
Create an Unfirm Demand Schedule................................................................................................24
Generate the Schedules...................................................................................................................25
Review the Sales Order....................................................................................................................25
Review the Sales Forecast................................................................................................................25
Create a Firm Demand Schedule......................................................................................................25
Compare New Releases with Previous Releases Generated...............................................................26
Demand Net Change Report...................................................................................................................26

Specialized Demand Processing...........................................................................................28


Demand Mass Review....................................................................................................................................28
Workshop - Mass Review Multiple Demand Records...............................................................................28

Epicor ERP | 10.0.700.2

Contents

Demand Management Course

Create Unfirm Demand Schedule.....................................................................................................28


Create Firm Demand Schedule.........................................................................................................29
Review Demand Schedules in Demand Mass Review........................................................................29
Review Available Actions.................................................................................................................29
Review Releases in Sales Order Entry................................................................................................31
Demand Review Report..........................................................................................................................31
Demand Reconciliation..................................................................................................................................32
Workshop - Run Demand Reconciliation.................................................................................................32
Workshop - Close a Demand Contract....................................................................................................33
Cumulative Quantities Variances Report..................................................................................................33

Additional Information - EDI................................................................................................34


EDI Installation...............................................................................................................................................34
EDI File Format...............................................................................................................................................35
Supported EDI Transaction Types...................................................................................................................35

Conclusion.............................................................................................................................36

Epicor ERP | 10.0.700.2

Demand Management Course

Demand Management Course

Demand Management Course


This course discusses how the Demand Management module handles the creation, analysis, editing, and
reconciliation of cumulative records for order releases from your customers.
This course is designed to review the concepts, processes, and reporting of the Demand Management (DM)
module. Discussions introduce you to the fundamental setup of master files, information impacting Demand
Management processes, the programs for Demand Contract Entry and Demand Entry used to define and manage
contracts as well as release schedules. This course also looks at Demand Mass Review used to evaluate the impact
of demand lines and shipping schedules as well as Demand Reconciliation used to update releases to reflect
changes that occurred during shipping.
Throughout the course, hands-on workshops guide you through these topics.
Upon successful completion of this course, you will be able to:
Analyze the features and functionality available in the Demand Management module.
Configure the related file setup.
Identify additional demand parameters in the Customer Maintenance program.
Define Periodicity and the impact of the available options.
Specify customer contracted parts in Contract Entry.
Retrieve demand lines from the contract to generate demand.
Generate a shipping schedule for current demand.
Use additional functions used to review demand and match new and existing releases.
Reconcile quantity variances on demand contracts.
Enter demand information through Electronic Data Interchange (EDI).

Epicor ERP | 10.0.700.2

Before You Begin

Demand Management Course

Before You Begin


Read this topic for information you should know in order to successfully complete this course.

Audience
Specific audiences will benefit from this course.
COO/Operations Manager
Production Manager
Sales Manager
Sales Engineer/Pre-Sales
Account Manager
Sales Representative

Prerequisites
To complete the workshops in this course, the necessary modules must be licensed and operating in your training
environment. For more information on the modules available, contact your Epicor Customer Account Manager
at EpicorCAM@epicor.com. It is also important you understand the prerequisite knowledge contained in other
valuable courses.
Navigation Course - This course introduces navigational aspects of the Epicor application's user interface.
Designed for a hands-on environment, general navigation principles and techniques available in two user
interface modes - Classic Menu and Modern Shell Menu. Workshops focus on each of these modes and
guide you through each navigational principle introduced.
Customers Course - This course introduces fundamental concepts pertaining to the creation of customer
records. This course also covers various maintenance programs necessary to define a customer in the Epicor
application.
Order Management Course - This course discusses the Order Management module and how it facilitates
the flow of manufactured items from inventory or jobs to the customer. A shipping transaction is performed
whether items are shipped from stock or from work in process (WIP). Shipping transactions are captured
during invoicing in the Accounts Receivable (AR) module, creating financial transactions that post to the
general ledger (GL). Order entry and shipping are directly affected by the nature of the product and the
process, specifically whether the items are built-to-order or shipped from stock.
Methods of Manufacturing Course - This course defines the role of a method of manufacturing (MOM),
its composition, and the impact it has on scheduling and costing outputs.
Parts Course - This course introduces the building blocks that make up Part Maintenance. It focuses on the
importance of Part Maintenance, required maintenance program setup, key fields, manufactured and purchased
part setup, and commonly used reports and trackers.
Manufacturing Foundations Course - The Manufacturing Foundations course introduces you to the principal
building blocks in establishing a strong manufacturing environment. This course discusses the necessary
prerequisites involved with efficient production floor configuration.

Epicor ERP | 10.0.700.2

Demand Management Course

Before You Begin

Environment Setup
The environment setup steps and potential workshop constraints must be reviewed in order to successfully
complete the workshops in this course.
Your Epicor training environment, in which the Epicor demonstration database is found, enables you to experience
Epicor functionality in action but does not affect data in your live, production environment.
The following steps must be taken to successfully complete the workshops in this course.
1.

Verify the following or ask your system administrator to verify for you:
Your Epicor training icon (or web address if you are using Epicor Web Access) points to your
Epicor training environment with the Epicor demonstration database installed. Do not complete
the course workshops in your live, production environment.
Note It is recommended that multiple Epicor demonstration databases are installed. Contact
Support or Systems Consulting for billable assistance.
The Epicor demonstration database is at the same service pack and patch as the Epicor
application. Epicor's education team updates the Epicor demonstration database for each service pack
and patch. If your system administrator upgrades your Epicor application to a new service pack or patch,
he or she must also download the corresponding Epicor demonstration database from EPICweb > Support
> Epicor > Downloads and install it. If this is not performed, unexpected results can occur when completing
the course workshops.
Your system administrator restored (refreshed) the Epicor demonstration database prior to
starting this course. The Epicor demonstration database comes standard with parts, customers, sales
orders, and so on, already defined. If the Epicor demonstration database is shared with multiple users
(that is, the database is located on a server and users access the same data, much like your live, production
environment) and is not periodically refreshed, unexpected results can occur. For example, if a course
workshop requires you to ship a sales order that came standard in the Epicor demonstration database,
but a different user already completed this workshop and the Epicor demonstration database was not
restored (refreshed), then you will not be able to ship the sales order. Epicor's education team has written
the course workshops to minimize situations like this from occurring, but Epicor cannot prevent users
from manipulating the data in your installation of the Epicor demonstration database.

2.

Log in to the training environment using the credentials manager/manager. If you are logged in to your
training environment as a different user, from the Options menu, select Change User.

3.

From the Main menu, select the company Epicor Education (EPIC06).

4.

From the Main menu, select the Main Plant.

Epicor ERP | 10.0.700.2

Demand Management Overview

Demand Management Course

Demand Management Overview


Use Demand Management in Epicor ERP more efficiently manage short and long term contracts, turning the
demand from these contracts into sales orders and Material Requirements Planning (MRP) forecasts.
Demand Management incorporates the framework and business logic necessary to efficiently manage long term
contracts. These contracts encompass forecasts, sales orders, changes to sales orders, and shipping schedules.
You can enter demand information manually, electronically through Electronic Data Interchange (EDI), or both.
The EDI feature suite generates electronic information that passes both to and from your customers.
Demand Management handles creation, analysis, editing, and reconciliation of cumulative records for releases
from your customers. Demand Management includes the following functionality to support long term contracts:
Provides the ability to have several sales orders or lines attached or subordinate to the contract.
Creates the ability to review contracted values and quantities with actual incoming quantities and values.
Delivers an efficient interface and process to manage the volume of data possible with long term contracts.
Includes the capability to view the impact of incoming contract changes before accepting, while allowing
them to be accepted, revised, or rejected and provides the appropriate response to trading partners.
Provides access to both forecasts and sales orders from one point of entry.
Allows the management and reconciliation of cumulative shipping quantities.
Allows the acceptance of incoming information to be handled individually, in mass, or in auto-accept mode
at the trading partner or document level.
Business Scenario
Dalton Manufacturing is a large manufacturer of consumer goods for leading big-box retailers throughout North
America, South America and Europe. Dalton is responsible for managing and immediately fulfilling demand from
these large and geographically dispersed customer trading partners. The tasks involved to do this typically include
initial negotiation of the demand contracts, through the creation of orders and outbound documents (such as
Advanced Shipping Notices, sales order acknowledgments, packing slips and invoices). Efficient planning of their
own internal production activities is based on properly managing the time-sequenced demand contracts they
sign with each of their retailer customers.
Dalton Manufacturing has chosen to manage these tasks on an automated basis in the Epicor application; this
involves highly efficient processing of Electronic Data Interchange (EDI) transactions received from, and transmitted
to their customer trading partners. Personnel in the Dalton Manufacturing Information Technology department
actively work with these trading partners to properly manage inbound and outbound data interchange transactions.
This includes mapping the data formats required for demand management processing in their Epicor application
to their customer trading partner's EDI processing formats.

Epicor ERP | 10.0.700.2

Demand Management Course

Application Setup

Application Setup
This section reviews common company configuration and maintenance program factors related to Demand
Management.
In order to more efficiently manage short and long term contracts in Demand Management and turn demand
from contracts into sales orders and Material Requirements Planning (MRP) forecasts, certain master file definitions
are required.
Note Many of the master files are established during implementation of other modules. A brief review of
selected master files are included along with discussions on the importance of specific parameters for
Demand Management.

Company Configuration
Company Configuration defines options for companies in the Epicor application. Use these options to customize
the application to best fit each company within your organization. This section reviews configurations and tables
specific to Demand Management.
Only the Company Configuration fields specific to the Demand Management process are covered in this course.
Refer to the Application Help to define any other fields of interest.
Modules > Sales > Demand
Use the Modules > Sales > Demand sheet to define the Demand Management module configuration settings.
This includes specifying if unfirm and forecast schedules should be included in demand management lead time
checking logic for the specified company, and if scheduled matching should automatically be performed for all
orders.
Settings defined on this sheet are as follows:
Select the Check Unfirm Schedules check box to include unfirm schedules in the demand management lead
time checking logic for this company.
Select the Check Forecast Schedules check box to include forecast schedules in the demand management
lead time checking logic for this company.
Select the Automatically Match All check box if the Demand Matching selection should automatically match
all new demand schedules and candidates. In this case, the application runs matching in the background as
a continuing process and automatically matches new demand schedules.
Select a Cancel Schedules Action to specify what the Epicor application should do when you run the Demand
Schedule > Close command on the Demand Entry Actions menu for a demand contract - automatically cancel
or delete sales order releases for closed demand schedules.
Cancel Releases - The Epicor application automatically cancels sales order releases for closed demand
schedules received from customer trading partners in this company.
Delete Releases - The Epicor application automatically deletes sales order releases for closed demand
schedules received from customer trading partners in this company.

Epicor ERP | 10.0.700.2

Application Setup

Demand Management Course

Menu Path
Navigate to this program from the Main Menu:
System Setup > Company/Site Maintenance > Company Configuration

Maintenance Programs
This section of the course discusses common maintenance programs that influence the Demand Management
process.
In many cases, not all fields within the following master files are discussed in this course. For a full description of
all available fields, refer to the Application Help.

Customer Periodicity Maintenance


Use Customer Periodicity Maintenance to define valid periodicity rules (if any) for a specific customer or ship
to customer trading partner.
Periodicity rules define the regular intervals at which deliveries to the customer or ship to location take place
(daily, specific day of the week, weekly or monthly).
When you define periodicity intervals, first create the periodicity rules by selecting the customer (and optionally
Ship To identifier), then define the delivery interval rules used for the specified customer.
You select a periodicity rule on the customer record in Customer Maintenance on the Customer > Demand
sheet. There is also a Demand sheet available at the Ship To level, so you can select different periodicity rules
for the same customer.
By selecting different periodicity rules, you can schedule releases and forecasts based on the requirements of the
specific customer and/or ship-to locations. These periodicity values are used during Demand Processing to calculate
the Ship By dates that are required for each order release or forecast.
To calculate the demand schedule, the demand process first looks for a periodicity linked to a customer or ship-to
location. It uses the selected rule to calculate the Ship By Date on each demand record. If a periodicity is not
defined on the customer location or ship-to location, the application's default periodicity values are used to
determine the demand schedule.
Two ways of handling periodicity are:
Electronically - EDI will use the periodicity rule designated on the customer record to define the interval for
customer deliveries. The periodicity rule is available at the main customer level as well as the Ship-To level, so
different rules can be selected for individual customer ship-to's. By selecting different periodicity rules, order
releases and forecasts can be scheduled based on the requirements of a specific customer or ship-to location.
To calculate the demand schedule, the demand process first looks for a periodicity linked to a customer or
ship-to location. It will use the selected rule to calculate the Ship By Date on each demand record. If a periodicity
is not defined on the customer location or ship-to location the application's default periodicity values will be
used to determine the demand schedule.
Manually Entered - The Create Demand Schedule option in Demand Entry allows any of the values defined
in the periodicity table for that customer to be selected to generate schedules and calculate the Ship By dates
required for each order release or forecast. If no periodicity codes are defined for the customer, any of the
application's default periodicity values can be used to define the demand schedule.
Available periodicity options are:
Daily - When selected, this Rules check box indicates that deliveries are made every day - Monday through
Friday.

10

Epicor ERP | 10.0.700.2

Demand Management Course

Application Setup

If you need, you can also select the Include Saturday and Sunday Shipments check box. This indicates
that deliveries are required on Saturdays and Sundays.
Monthly Forward - When selected, this Rules check box indicates that all deliveries to this customer are
sent once per month.
You can then use the First Ship Day field to define the day of the week this shipment must arrive.
To further define this shipment interval, use the Week Number in the Month value to indicate which week
during the month (1-5) this shipment needs to be sent.
Weekly Forward - When selected, this Rules check box indicates that all deliveries are sent to this customer
once per week.
Optionally, you can then use the Ship Day field to define the day of the week this shipment must arrive.
Nth Day of the Week - When selected, this Rules check box indicates that shipments arrive on this specific
work day.
You then use the Day of the Week Shipment field to define the specific day of the week (Monday through
Sunday) on which this shipment arrives.
Menu Path
Navigate to this program from the Main Menu:
Sales Management > Demand Management > Setup > Customer Periodicity

Terms Maintenance
Use Terms Maintenance to establish conditions that define how customers pay their invoices (for example,
discounts, number of payments, and payment frequency).
Terms define the due dates, payment frequency, applicable discounts, and number of payment installments.
Each accounts receivable (AR) code defines a time period and a discount percentage period schedule.
To begin setting up the selling terms, select one of the following term code types:
Days
Day Of Month
End of X Month(s) On Y Day(s)
Determine whether the discount percentages for a term code calculate against partial or full payments.
Each terms code can have either one discount period or multiple discount periods. Each discount period has a
specific percentage which is valid for a specific period. Together, the discounts gradually reduce the percentages
based on the passed period (months, days) within the overall terms period.
Enter as many discount percentage periods as you need.
Note that the discounts have the same types as the term codes:
Days
Day Of Month
End of X Month(s) On Y Day(s)
You do not need to select the same type for a term code and a discount assigned to this term code.
When a payment is received, the percentage active on the payment date is used to calculate the discount amount.
AR terms display on sales orders and AR invoices. Select default payment terms for customers and on AR invoices.

Epicor ERP | 10.0.700.2

11

Application Setup

Demand Management Course

A terms record is required for each customer. When creating a customer record, a default terms record displays
in the new record, but you can override this selection.
Menu Path
Navigate to this program from the Main Menu:
Financial Management > Accounts Receivable > Setup > Terms
Sales Management > Demand Management > Setup > Terms
Sales Management > Order Management > Setup > Terms
For CRM users, the Main Menu appears as:
Customer Relationship Management > Order Management > Setup > Terms

Customer Maintenance
Customer trading partners are businesses to whom you sell products and services. Use Customer Maintenance
to enter customer records. Customer records are primarily used to create quotes, sales orders, and accounts
receivable (AR) invoices. Customer records are also used during the Customer Relationship Management (CRM)
process.
Create Demand Entries
Use Actions > Create Demand Entries to select existing sales orders for a specific customer and to enable the
sales order for processing in Demand Management. This functionality allows you to enable existing sales orders
for update in the future based on the demand records you receive from your trading partner via EDI and Service
Connect. This selection is only available if the specific customer record is designated as a trading partner in
Customer Maintenance.
Menu Path
Navigate to this program from the Main Menu:
Financial Management > Accounts Receivable > Setup > Customer
Financial Management > Deferred Revenue Accounting > Setup > Customer
Financial Management > Multi-Site > Setup > Customer
Production Management > Material Requirements Planning > Setup > Customer
Sales Management > Customer Relationship Management > Setup > Customer
Sales Management > EDI > Setup > Customer
Sales Management > Order Management > Setup > Customer
Sales Management > Quote Management > Setup > Customer
Service Management > Field Service > Setup > Customer
For CRM users, the Main Menu appears as:
Customer Relationship Management > Sales and Marketing Management > Setup > Customer
Customer Relationship Management > EDI > Setup > Customer
Customer Relationship Management > Order Management > Setup > Customer
Customer Relationship Management > Quote Management > Setup > Customer

12

Epicor ERP | 10.0.700.2

Demand Management Course

Application Setup

Demand
Use the Demand sheet to assign a trading partner identification number and define demand processing
parameters. The parameters defined specify how the Epicor application evaluates incoming Electronic Data
Interchange (EDI) shipping schedules from your customer.
The parameters you define for your customer trading partner in this sheet include the following:
Assign a Trading Partner an identification number. A trading partner is the Epicor Service Connect identifier
for the customer. Epicor Service Connect uses this identifier to send and receive EDI documents between your
company and a specific customer.
Define demand processing parameters for a specific customer. This includes assigning Periodicity, Delivery
Days, and Date Type parameters used by the Epicor application to calculate the Ship By or Need By dates for
the demand schedules.
Indicate how differences in unit price and part records should be evaluated by the application during demand
processing.
Specify the lead time required to evaluate and process certain types of action requests, for example, add new
demand schedule lines, change or cancel existing demand schedule lines, on incoming EDI transactions received
from this customer trading partner. For each type of action request, specify the actions that should take place
in the Epicor application (stop transaction or process transaction and display a warning message) when
incoming EDI transactions are received with insufficient lead times with respect to the parameters you have
specified for the type of transaction.
Enter lead time values used with firm shipping schedules. Each lead time value defines a date range during
which the Epicor application notifies you when various actions occur on a firm shipping schedule currently
linked to this customer record.
Important This sheet is only available if you use the Demand Management module. For more information,
refer to the Demand Management Overview topic in the Demand Management module help.

Documents
Use the Documents sheets to define the processing parameters for inbound documents you accept from a
customer trading partner when sent to you as well as the outbound documents you generate and send to the
customer trading partner through Epicor Service Connect.
The Demand Management functionality uses these definitions to recognize the specific Electronic Data Interchange
(EDI) documents, such as advanced shipping notices, sales order acknowledgments, and invoices, that are
generated in the Epicor application.
The document processing parameters you define for your customer trading partner in this sheet include the
following:
Assign a unique document identification number.
Specify the type of document being defined, for example, forecast, unfirm release, ASN, and invoice.
Specify the map ID number and whether this is an inbound document you receive from this customer trading
partner, or an outbound document you send to this customer trading partner. If it is an outbound document,
you can specify if the Epicor application should automatically generate a document record deposited in a
destination folder, for transmission to the customer trading partner via EDI, with no manual intervention
required on the part of a user.
Specify the part number processing hierarchy the Epicor application must use to validate internal part, customer
part, manufacturer part, EAN, GTIN, or UPC codes on the inbound demand document when received from
this customer trading partner.
Specify how incoming demand transactions for the document will be processed - Always Accept, Accept If
No Errors, Manually Accept.

Epicor ERP | 10.0.700.2

13

Application Setup

Demand Management Course

Identify an Alternate Trading Partner ID (if any) being used for the document.
Important This sheet is only available if the Demand Management module is licensed. For more information,
refer to the Demand Management Overview topic in the Demand Management module help.

Demand
Use the Demand sheet as needed to assign a trading partner identification number and define demand processing
parameters that specify how the Epicor application should evaluate incoming Electronic Data Interchange (EDI)
shipping schedules received from your ship to customer trading partner.
This sheet is similar in function to the Customer > Demand sheet, but allows you to define override demand
processing parameters for specific ship to locations for a customer trading partner. For example, the trading
partner may have West Coast, East Coast and off-shore ship to locations, each with their own lead time and
shipping requirements.
The demand processing parameters you define for your ship to customer trading partner in this sheet include
the following:
Assign a trading partner identification number and define demand processing parameters for a specific ship
to customer. This includes assigning periodicity, delivery days and date type parameters used by the application
to calculate Ship By or Need By dates for the demand schedules.
Indicate how differences in unit price, part records, and revision levels are evaluated by the application during
demand processing.
Specify the lead times required to evaluate and process certain types of action requests (for example, adding
new demand schedule lines, changing or cancelling existing demand schedule lines) on incoming EDI
transactions received from this ship to customer trading partner. For each type of action request, you specify
the actions that should take place in the application (stop transaction or process transaction and display a
warning message) when incoming EDI transactions are received with insufficient lead times with respect to
the parameters you have specified for that type of action request.
Additionally, this sheet allows you to enter Lead Time values that you use with firm shipping schedules. Each
lead time value defines a date range during which the application notifies you when various actions occur on
a firm shipping schedule that is currently linked to this ship to location.
Important The Ship To > Demand sheet is only available if you use the Demand Management module.
For more information, refer to the Demand Management Overview topic in the Demand Management
module help.

Part Maintenance
Use Part Maintenance to establish or update part information. Parts are items purchased or manufactured for
use as raw material, made to use as subassemblies, or built as finished items to fill orders.
Note Typically, parts have been established in the application when Demand Management is implemented.
Therefore, the creation of parts is not covered in this course. Refer to the Inventory or Parts courses for
more information regarding defining and entering parts.
Menu Path
Navigate to this program from the Main Menu:
Material Management > Inventory Management > Setup > Part
Material Management > Purchase Contracts Management > Setup > Part
Material Management > Purchase Management > Setup > Part

14

Epicor ERP | 10.0.700.2

Demand Management Course

Application Setup

Material Management > Supplier Relationship Management > Setup > Part
Production Management > Engineering > Setup > Part
Production Management > Job Management > Setup > Part
Production Management > Material Requirements Planning > Setup > Part
Production Management > Quality Assurance > Setup > Part
Sales Management > Configurator Management > Setup > Part
Sales Management > Demand Management > Setup > Part
Sales Management > Order Management > Setup > Part
Service Management > Field Service > Setup > Part
For CRM users, the Main Menu appears as:
Customer Relationship Management > Configurator Management > Setup > Part
Customer Relationship Management > Order Management > Setup > Part

Epicor ERP | 10.0.700.2

15

Application Setup

Demand Management Course

Workshop - Create a Customer Part


In this workshop create a customer part reference for an existing part in the database.
Navigate to Customer Part Cross Reference.
Menu Path: Sales Management > Order Management > Setup > Customer Part Cross Reference
Tip The CRM menu path is: Customer Relationship Management > Order Management > Setup > Customer
Part Cross Reference
Important In order for multiple people to perform this workshop, different customers and parts must be
selected. Note the customers and parts selected or created to be used throughout the remaining workshops
in this course.
1. In the Customer field, search for and select Addison and press Tab.
2. Click New.
3. In the Part Number field, search for and select DSS-1010 and press Tab.
4. In the Customer Part Number field, enter XXXX (where XXXX are the last four digits of your phone
number).
5. In the Description field, enter XXXX (where XXXX are the last four digits of your phone number) and click
Save.
6. Exit Customer Part Cross Reference.

Carrier Maintenance
Use Carrier Maintenance to define valid carriers in the Epicor application.
Carrier Maintenance is tied to Ship Via in order to accurately define the specific carrier used for shipping (for
example, FedEx Next Day and FedEx Two Day). The Ship Via field found in many of the Epicor application
programs is also linked to the carriers defined in this program.
You can associate a Standard Carrier Alpha Code (SCAC) code with each carrier. It is an internationally accepted
two-to-four digit number used in the transportation industry to identify freight carriers used in Electronic Data
Interchange (EDI) transactions and shipping documents (such as Bill of Lading, Freight Bill, Packing List, and
Purchase Order). These codes are commonly used by the automobile, petroleum, forest products, and chemical
industries, as well as suppliers to retail businesses, carriers engaged in railroad piggyback trailers, and ocean
container drayage.
The following are key fields:
Carrier - Use this field to define the unique identifier for the carrier.
Description - Use this field to define the carrier.
SCAC - Use this field to define the Standard Carrier Alpha Code (SCAC) to identify the carrier.
Inactive / Active - Use this check box to define the status of the carrier.
Menu Path
Navigate to this program from the Main Menu:
Material Management > Shipping / Receiving > Setup > Carrier

16

Epicor ERP | 10.0.700.2

Demand Management Course

Application Setup

Sales Management > Demand Management > Setup > Carrier


Sales Management > Order Management > Setup > Carrier
For CRM users, the Main Menu appears as:
Customer Relationship Management > Order Management > Setup > Carrier

Ship Via Maintenance


Use Ship Via Maintenance to identify the different methods you use to ship products to subcontractors or
customers. These shipping methods are known as Ship Via Codes.
Note Ship Via Codes are mandatory at the point of sales order entry.

Menu Path
Navigate to this program from the Main Menu:
Financial Management > Accounts Payable > Setup > Ship Via
Financial Management > Accounts Receivable > Setup > Ship Via
Material Management > Purchase Management > Setup > Ship Via
Material Management > Shipping / Receiving > Setup > Ship Via
Sales Management > Customer Relationship Management > Setup > Ship Via
Sales Management > Demand Management > Setup > Ship Via
Sales Management > Order Management > Setup > Ship Via
For CRM users, the Main Menu appears as:
Customer Relationship Management > Sales and Marketing Management > Setup > Ship Via
Customer Relationship Management > Order Management > Setup > Ship Via

FOB Maintenance
Use FOB Maintenance to set up FOB term descriptions and delivery term codes. Free-on-board (FOB) is the point
where legal title of goods passes from your company to a customer or from a supplier to your company.
Use Customer Maintenance, Supplier Maintenance, Sales Order Entry, and Purchase Order Entry to select FOB
codes. The selected FOB code defaults in AP Invoice Entry and AR Invoice Entry.
Use the FOB table to validate descriptions and delivery term codes.
Delivery terms can be associated with an FOB code only if Internationalization is set up in Company Configuration.
Non-Intrastat Customers
Important Free-on-board (FOB) codes are not required in the United States but can still be useful. FOB is
required setup for European countries.
Common practice in the United States is to interpret FOB as the point where legal title passes from you to the
customer or from the supplier to you. You can enter a generic FOB description such as My Sites City, Origin,
or Destination. Select this description during a transaction. Since the term FOB prints on Epicor application
forms, including FOB in the description can be redundant.
FOB codes have a different and more restrictive meaning in Europe than in the United States. European countries
use this program to organize delivery terms data used for Intrastat declaration.

Epicor ERP | 10.0.700.2

17

Daily Demand Processing

Demand Management Course

Tip Note that if you use Intrastat, the FOB description and corresponding delivery code is not required for
legal reporting. Because of this, you can leave the FOB value blank.
External Coding System
If your industry has a recognized external coding system, enter these external codes in FOB Maintenance. Use
these codes for your reference only; they do not activate additional functionality in the Epicor application.
Menu Path
Navigate to this program from the Main Menu:
Financial Management > Accounts Payable > Setup > FOB
Financial Management > Accounts Receivable > Setup > FOB
Material Management > Purchase Management > Setup > FOB
Sales Management > Demand Management > Setup > FOB
Sales Management > Order Management > Setup > FOB
For CRM users, the Main Menu appears as:
Customer Relationship Management > Order Management > Setup > FOB

Daily Demand Processing


This section of the course reviews the demand processing that occurs throughout the day. These processes include
creating a demand contract, generating demand, process multiple demand records, and update demand records
to reflect changes that occurred during shipping.
After primary information is defined, demand contracts are created for customers along with defining demand
lines and shipping schedules. This functionality includes the ability to reject or select schedules and process
demand. Additional processing options include the ability to mass review demand records and perform
reconciliation with customer receipts.
Demand Contracts
The demand contract is the instrument against which the Epicor application receives and processes inbound EDI
files received from your customer trading partners. The demand contract structure lets you attach multiple sales
order releases to a single demand contract, providing the ability to review the contract quantities with the actual
incoming quantities.
Generating Demand
Although the demand for each contract can be imported into the application electronically through Service
Connect and Electronic Data Interchange (EDI), the information is entered manually for the exercises in this
section. For additional information, refer to the Service Connect course and the EDI - Demand Management
Technical Reference Guide.

Demand Contract Entry


Use Demand Contract Entry to enter customer contracts. These contracts are the overall documents that define
the contracted parts as well as the dates during which each contract is active. The contract records are used to

18

Epicor ERP | 10.0.700.2

Demand Management Course

Daily Demand Processing

generate demand for your parts, allowing you to set up a shipping schedule for order releases or forecasts for
Material Requirements Planning (MRP) processing.
Through this program, you can set up several default values for the sales orders and/or forecasts that are generated
through the contract. You can indicate the discounting method that is used on this contract's part quantities,
and whether or not each sales order is shipped complete.
Each contract can be set up for multiple parts, so one contract can be used to generate multiple shipping schedules
for each part detailed on the contract.
Menu Path
Navigate to this program from the Main Menu:
Sales Management > Demand Management > General Operations > Demand Contract Entry

Workshop - Enter a Demand Contract


Dalton Manufacturing has just entered into a negotiated demand contract with one of their customer trading
partners. In this workshop, create a demand contract using Demand Contract Entry, and enter a demand line
item using the customer part number cross reference you set up in the Workshop - Create a Customer Part.

Create a Demand Contract


Navigate to Demand Contract Entry.
Menu Path: Sales Management > Demand Management > General Operations > Demand Contract Entry
1. From the New menu, select New Contract Header.
2. In the Contract field, enter XXXX (where XXXX are the last four digits of your phone number).
3. In the ID field, search for and select Addison.
4. Navigate to the Header > Detail sheet.
5. In the Cumulative Setting field, select By Part/PO.
6. In the Start field, select today's date.
7. In the End field, enter the date two years from today's date.
8. Click Save.

Enter Contract Lines


1. From the New menu, select New Contract Detail.
The Line > Detail sheet displays.
2. In the Part field, search for and select DSS-1010 and press Tab.
3. In the Total Contract Quantity field, enter 50000.
4. In the Unit Price field, notice the unit price pulled in from the part record and click Save.
The unit price can be modified if necessary.

Epicor ERP | 10.0.700.2

19

Daily Demand Processing

Demand Management Course

5. From the New menu, select New Contract Detail to enter the second line in the Demand Contract.
6. In the Part field, enter ML-1698-A36 and press Tab.
7. In the Total Contract Quantity field, enter 50000.
8. In the Unit Price field, notice the unit price pulled in from the part record.
The unit price can be modified if necessary.
9. Click Save.
10. Exit Demand Contract Entry.

Demand Entry
Demand Entry is the central processing program for Demand Management. Use this program to generate
demand from either manually entered contracts or imported customer Electronic Data Interchange (EDI) documents
sent to you through Service Connect.
Use Demand Entry to accept or reject a demand, providing control over what demand is used. When you are
satisfied with the demand, use this program to generate a shipping schedule.
Once a demand is accepted, the next step is to select the Ready To Process check box on the Header > Detail
sheet. The purpose of this check box is to ensure all demands listed are processed.
This process affects not only Demand Entry but also Demand Mass Review and the automated process of loading
demands. The demand does not process unless this check box is selected.
Finally, process the demand. Depending on the demand type, the Demand Entry process creates unfirm order
releases, firm order releases, or Material Requirements Planning (MRP) forecasts. You can use either Sales Order
Entry or Forecast Entry to further refine the resulting data.
Demand Entry has additional functionality that helps analyze the incoming demand. The additional functionality
includes the following:
Schedule Review - Allows you to examine the shipping schedule that results.
Delete By Schedule Number - Allows you to remove all demand schedule lines contained within a selected
demand schedule. Several demand schedules can be removed through this program at the same time.
Match - Allows you to combine a new release with any previous releases generated through this demand
record.
Demand lines are added manually or from the Actions > Demand Line > Get Demand Lines From Contract
option. Once you are satisfied with the demand, use the Actions > Demand Schedule > Create Demand
Schedule option to automatically generate a shipping schedule for the current demand line. This utility converts
part quantities ordered through a demand line from a contract or from a customer's imported EDI document
into a shipping schedule.
Once the demand (shipping) schedule has been generated, individual entries of the shipping schedule are examined
further by selecting the Schedule > List sheet. Individual schedules can be changed and deleted or dates and
quantities corrected. The Actions > Demand Header > Process generates sales order releases or forecasts once
the review of the detail shipping schedule is complete.
Errors that occur are written to a log file when running the process (posting) option. You can review the errors
by selecting Actions > Demand Header > Log.

20

Epicor ERP | 10.0.700.2

Demand Management Course

Daily Demand Processing

Depending on the demand type, the Process option in Demand Entry creates unfirm order releases, firm order
releases, or MRP forecasts. Use either Order Entry or Forecast Entry to further refine the resulting data after
processing is complete.
Matching
Use the Actions > Demand Schedule > Match option to pair similar sales releases together to create a more
efficient release schedule and to ensure that changes to schedules are accurately reflected.
This program allows you to match the new shipping schedule against the previous schedule. It allows linking, or
matching, similar demands together on the same sales order release. This ensures a more accurate shipping
schedule.
This functionality uses a best guess method of comparing releases that first share the same date, same release
quantity, and so on. Matching functionality is described below.
The following options are available:
Match - Initially this functionality matches the incoming demand releases with existing sales orders. After
allowing you to decide whether or not to combine these releases. Releases are combined by manually selecting
specific sales order releases and clicking the Match button. The application automatically creates a new release
for those that were not selected for matching.
Match All - As an alternative to the manual process of matching sales order releases, you can review potential
matches and then click the Match All button to automatically match all sales orders displayed. This process
is done by setting the release number on the incoming demand, and sets the release number to zero for any
releases that cannot be matched.
Automatically Match All - The demand matching process can also be performed automatically. To set the
matching process to automatic, the Automatically Match All check box must be selected for a specific
company on the Company Configuration > Modules > Sales > Demand sheet. In this case, the matching
process happens in the background.
Unmatch All - Yo can use this button as needed to unmatch all currently matched entries and perform the
matching process again manually.
Besides matching demand schedules, Demand Schedule Matching also allows you to reject specific schedules or
an entire shipping schedule. You can launch Demand Reconciliation directly from this program. Demand
Reconciliation allows you to enter quantity adjustments that are electronically sent to you by customers on each
shipping line. The logic used for this matching is as follows:
Schedule records are looped through by the Required Date.
The Demand Reference field is the first criteria checked. The first Order Release found that has not been
matched with the same demand reference value as the schedule is matched. (Order Release records are also
sorted by Required Date.)
If a match cannot be found, the next criteria is the Required Date. If an Order Release can be found with the
same required date as the schedule, a match occurs.
If a match cannot be found with either criteria, the schedule matches with the first order release that has not
been matched yet. For example:
Schedule

Required Date

Quantity

12/01/13

25

12/08/13

25

12/15/13

25

12/22/13

25

Epicor ERP | 10.0.700.2

Demand Ref.

78457

21

Daily Demand Processing

Demand Management Course

Release

Required Date

Quantity

11/30/13

20

12/07/13

20

12/14/13

20

Demand Ref.

78457

The Results of the Automatic Match


Schedule 1 is matched with release 1. The references do not match, and the dates do not match. Release 1
is the first that has not been matched yet.
Schedule 2 is matched with release 2 because the demand reference values match.
Schedule 3 is matched with release 3 because the release has not been matched yet.
Schedule 4 is not matched because all the releases already have a match. A new order release record is created
when the Processing option is selected.
One Time Ship To
Use the Schedule > One time Ship To sheet to create one time ship to address information for the demand
order. This function is beneficial if you are shipping to a ship to address that does not display in the Ship To field
selection list.
Note The One Time Ship To sheet can only be accessed when the Allow One Time Ship To check box
is selected for the specific sold to or ship to customer in Customer Maintenance on the Customer > Detail
sheet.

Workshop - Create and Define the Demand Schedule


Dalton Manufacturing has just negotiated and signed a long-term demand contract with a new big box retailer.
While the Dalton Information Services (IS) department collaborates with the retailer's own IS department to
finalize EDI transaction maps, Dalton uses Demand Entry to create and define demand records in their Epicor
application.
In this workshop, perform the following tasks using Demand Entry:
Create and define demand records in the Epicor application and designate the beginning and ending dates
for the demand schedule.
Create an unfirm demand schedule, and generate schedules. Overlapping time periods are intentionally used
to provide an opportunity to work with additional functions to help analyze demand. A time bar is included
to assist with entering the appropriate dates to achieve overlap. Use today's date as the current date (sample
dates are included as a reference).
Review sales orders and sales forecasts related to the demand schedule.
Compare new and previous releases against the demand schedule.

Establish Begin and End Dates


Use the time line below to assist with defining appropriate dates for the workshop example.
1. Enter today's date for the time line's first Your Date value.
2. Fill in each of the remaining dates in relation to the time line, referring to the example dates provided.
3. Enter the Your Date values for each of the spaces provided on the time line before continuing.

22

Epicor ERP | 10.0.700.2

Demand Management Course

Daily Demand Processing

Create Demand Lines


Navigate to Demand Entry.
Menu Path: Sales Management > Demand Management > General Operations > Demand Entry
1. From the New menu, select New Demand.
2. In the Contract field, enter XXXX (where XXXX are the last four digits of your phone number) and press
Tab.
3. In the PO field, enter POXXXX (where XXXX are the last four digits of your phone number).
4. Click Save.
5. From the Actions menu, select Demand Line > Get Demand Lines From Contract.
The Create Demand Lines From Demand Contract Lines window displays.
6. Select the Selected check box on Line 1 and click OK.
7. Navigate to the Line > Detail sheet to review the demand line.

Create and Define a Demand Schedule


1. From the Actions menu, select Demand Schedule > Create Demand Schedule.
The Create Demand Schedule window displays.
2. In the Begin and End date fields, enter the dates you defined in Step A of the time line.
3. In the Quantity Per Schedule field, enter 200 and press Tab.
4. In the Schedule Options section, in the Create field, select Monthly.

Epicor ERP | 10.0.700.2

23

Daily Demand Processing

Demand Management Course

5. In the Create As section, verify Forecasts is selected and click OK.


6. Click OK to the schedules created message.
7. Navigate to the Schedule > List sheet to review the demand schedule.
Individual schedules can be deleted and rejected, or specific schedule parameters can be manually changed
here, for example, the Ship By dates.
8. Review the date of the entries for reference later.
Note The output of the generated schedule is related to the calendar of the plant in which you are
currently working.

Create an Unfirm Demand Schedule


1. From the Actions menu, select Demand Schedule > Create Demand Schedule.
2. In the Begin and End date fields, enter the dates from Step B of the time line.
3. In the Quantity Per Schedule field, enter 50.
4. In the Schedule Options section, in the Create field, accept the default of Daily.
5. From the Create As options, select Unfirm Releases and click OK.
6. Click OK to the schedules created message.
7. Navigate to the Schedule > List sheet to review the demand schedule.
8. Review the entry dates for reference later.
The list is cumulative.

24

Epicor ERP | 10.0.700.2

Demand Management Course

Daily Demand Processing

Generate the Schedules


1. From the Actions menu, select Demand Header > Process.
2. Click OK to the Processing Complete message.
3. Navigate to the Header > Detail sheet.
4. In the Header > Detail > Lines sheet, in the Order field, record the sales order number ___________.
5. Minimize Demand Entry.

Review the Sales Order


Navigate to Sales Order Entry.
Menu Path: Sales Management > Order Management > General Operations > Order Entry
Tip The CRM menu path is: Customer Relationship Management > Order Management > General
Operations > Order Entry
1. In the Sales Order field, enter the sales order number created in the previous section and press Tab.
2. In the tree view, expand all of the nodes to view the demand releases for the part.
3. From the tree view, select various releases and navigate to the Lines > Detail sheet and Releases > Detail
sheet to review the status of each release.
Each of the sales order line releases have the Not Firm (unfirm) status.
4. Exit Sales Order Entry.

Review the Sales Forecast


Navigate to Forecast Entry.
Menu Path: Production Management > Material Requirements Planning > General Operations > Forecast Entry
1. In the Part field, search for and select DSS-1010 and press Tab.
2. Navigate to the List sheet.
3. Review the forecast list created.
4. Exit Forecast Entry.

Create a Firm Demand Schedule


Maximize Demand Entry..
1. From the Actions menu, select Demand Schedule > Create Demand Schedule.
2. Enter the Begin and End dates you defined for Step C of the time line.

Epicor ERP | 10.0.700.2

25

Daily Demand Processing

Demand Management Course

3. In the Quantity Per Schedule field, enter 10 and press Tab.


4. In the Schedule Options section, in the Create field, select Weekly.
5. In the Create As section, select Firm Releases and click OK.
6. Click OK to the schedules created message.
7. Navigate to the Schedule > List sheet to review the demand schedule.
8. From the Actions menu, select Demand Schedule > Review.
The Schedule Review window displays.
9. Review the entries. Note the columns of information related to the current and proposed data.
10. Click OK to close the Schedule Review window.

Compare New Releases with Previous Releases Generated


1. From the Actions menu, select Demand Schedule > Match.
The Demand Schedule Matching window displays.
2. Review the Demand Schedule and the Current Schedule.
In the Demand Schedule grid, entries with a release of 0 (zero) indicate that a match was not found. These
entries create new schedules. Entries with the same release number indicate an auto-match. The current
schedule is replaced with the demand schedule match.
3. Highlight both entries of a match that do not have the same date or quantity values.
Note The first entries that match (Release 1) have the same date but different quantities. The new
daily releases update (replace) their matching current weekly scheduled entries. Notice that the last
entries (auto matched) do not have the same date or quantity. In this situation, these entries are
outside the firm daily releases range we want to add. You need to unmatch these entries in order to
leave the unfirm weekly schedule (beyond the firm daily schedule range) as is.

4. Click Unmatch to remove the tie between the current schedule and the demand schedule.
5. Repeat the unmatch process for each entry where the date and quantity do not match and click OK.
6. From the Actions menu, select Demand Header > Process.
7. Click OK to the Processing complete message.
8. Exit Demand Entry.

Demand Net Change Report


Use the Demand Net Change Report to display demand records that have been converted into sales orders.
You first define the date from which you want the report to begin; all demand records transformed into sales
orders on or after this date display on the report. You can further limit the information displayed on this report
by sales orders, customers, parts, and trading partners.

26

Epicor ERP | 10.0.700.2

Demand Management Course

Daily Demand Processing

Important This report only prints if the Book Sales Order check box is selected in Company Configuration.
This check box is available on the Orders Configuration sheet.
Menu Path
Navigate to this program from the Main Menu:
Sales Management > Demand Management > Reports > Demand Net Change Report

Epicor ERP | 10.0.700.2

27

Specialized Demand Processing

Demand Management Course

Specialized Demand Processing


This section of the course discusses special Demand Management capabilities of the Epicor application.

Demand Mass Review


Demand Mass Review is designed to quickly review, reject, delete, and process multiple demand records at
the same time.
Use this program to evaluate and process either the current demand for a specific part or all the current demand
in your database. This program is designed for companies that work with a large volume of data, allowing these
organizations to quickly evaluate the demand that needs to be turned into firm sales order releases. The program
contains a Group sheet that you use to individually select and identify groups of demand records for processing.
This allows multiple users to mass-process different groups of demand records independently of each other.
Demand Mass Review operates in two modes. You can review the demand by part or by demand. Depending
upon the review mode you use, different fields are available to help you accept, reject, or delete the displayed
demand record.
Menu Path
Navigate to this program from the Main Menu:
Sales Management > Demand Management > General Operations > Demand Mass Review

Workshop - Mass Review Multiple Demand Records


After signing a demand contract with their trading partner, Dalton used Demand Entry to generate demand
schedules. These schedules can be reviewed in Demand Mass Review. Although this program is most beneficial
when processing large volumes of data, you can use it to review demand schedules for a single demand record.

Create Unfirm Demand Schedule


Navigate to Demand Entry.
Menu Path: Sales Management > Demand Management > General Operations > Demand Entry
1. In the Contract field, enter XXXX (where XXXX are the last four digits or your phone number) and press
Tab.
2. In the PO field, enter POXXXX (where XXXX are the last four digits of your phone number) and press Tab.
3. From the Actions menu, select Demand Schedule > Create Demand Schedule.
4. In the Begin field, enter today's date.
5. In the End field, enter the date one month from today.
6. In the Quantity Per Schedule field, enter 100.
7. In the Schedule Options section, in the Create field, select Monthly.

28

Epicor ERP | 10.0.700.2

Demand Management Course

Specialized Demand Processing

8. In the Create As section, select Unfirm Releases and click OK.


9. Click OK to the schedules created message.
10. Click Save.

Create Firm Demand Schedule


1. From the Actions menu, select Demand Schedule > Create Demand Schedule.
2. In the Begin field, enter today's date.
3. In the End field, enter the date one month from today.
4. In the Quantity Per Schedule field, enter 14.
5. In the Schedule Options section, in the Create field, accept the default.
6. In the Create As section, select Firm Releases and click OK.
7. Click OK to the schedules created message.
8. Navigate to the Schedule > List sheet to review the demand schedule.
9. Click Save.
10. Exit Demand Entry.
Note You will not process the demand from Demand Entry in this workshop. Once the demand is
processed, it is no longer available for review in Demand Entry or Demand Mass Entry.

Review Demand Schedules in Demand Mass Review


Navigate to Demand Mass Review.
Menu Path: Sales Management > Demand Management > General Operations > Demand Mass Review
1. Navigate to the Demand Mass Review sheet.
2. In the Review By section, verify Part is selected.
3. Click the Part button, search for and select DSS-1010.
4. Review the Part Demands entries.
Only the firm demand created in the previous workshop is included in the entries. You will see the Current
Quantity from the previous exercise and the Proposed Quantity from the new demand.

Review Available Actions


1. Click the Actions menu. The menu displays the following options:
Process Group

Epicor ERP | 10.0.700.2

29

Specialized Demand Processing

Demand Management Course

Select for Group


Unselect for Group
Matching
Reject
Unreject
Close
2. From the Actions menu, select Matching > Match All for Part.
Note Notice the columns of related and comparison information for Current and Proposed data.

3. Click OK to the Demand Matching for Part DSS-1010 complete message.


4. Click the Demand Entry button.
Note Demand Entry can be accessed to review the detail of the releases and the auto-matching
performed. Individual changes can be made in Demand Entry.

5. Navigate to the Schedule > List sheet.


6. From the Actions menu, select Demand Schedule > Match option to review or change individual entries.
Each of the Current Schedules (of 10 in the Selling Requested Qty column) will be replaced with the new
demand in the Demand Schedule schedule for 14 (Order Quantity column).
7. Click the Cancel button to exit the Demand Schedule Matching window.
8. Exit Demand Entry.
9. In Demand Mass Review, from the Actions menu, select Select for Group > Select All for Part.
10. From the Actions menu, select Process Group.
11. In the Demand Mass Process window, click Submit.
Note Review the path in the Log Filename field.

12. Close the Demand Mass Process window and exit Demand Mass Review.

30

Epicor ERP | 10.0.700.2

Demand Management Course

Specialized Demand Processing

Review Releases in Sales Order Entry


Navigate to Sales Order Entry.
Menu Path: Sales Management > Order Management > General Operations > Order Entry
Tip The CRM menu path is: Customer Relationship Management > Order Management > General
Operations > Order Entry
1. In the Sales Order field, enter the order number created in the Workshop - Create and define the
Demand Schedule.
2. In the tree view, expand all nodes to view all the part releases in the sales order.
3. Navigate to the Releases > List sheet and verify the scheduled releases.
The quantity for each of the daily releases was changed from 10 to 14.
4. Exit Sales Order Entry.

Demand Review Report


Use the Demand Review Report to analyze EDI / Demand Management information, including what demand
has been processed in Demand Entry or Demand Mass Review, what orders were updated, and what demand
was rejected or remains as unprocessed.
The Demand Review Report collects demand information that has been manually entered, or created from EDI
transactions that have been imported via Service Connect, into the Epicor application. It can be run for specified
customers, parts and customer purchase orders for a specified date range. Based on the selection and filter criteria
entered, it selects and sorts data stored in the DemandSchedule table by customer number, contract number,
contract line, schedule sequence and schedule number.
Menu Path
Navigate to this program from the Main Menu:
Sales Management > Demand Management > Reports > Demand Review

Epicor ERP | 10.0.700.2

31

Specialized Demand Processing

Demand Management Course

Demand Reconciliation
Use Demand Reconciliation to update demand records to reflect changes that occurred during shipping. It
displays cumulative quantity amounts according to your company's records, and your customer trading partner's
records.
The Epicor application tracks and displays cumulative quantity information by part number, or by part/purchase
order number, depending on the option selected in the Cumulative Setting field (in the Demand Contract Entry
> Header sheet) for the associated demand contract. The Epicor application tracks these changes based on
shipments you make to the customer, and by using the EDI documents received from your customer trading
partner; the calculated cumulative values display in this program.
The Company Information section displays cumulative quantity and last shipment information, according
to your company. The Epicor application automatically updates this information each time it generates a
shipment record in Customer Shipment Entry or Master Pack Shipment Entry.
The Trading Partner Information section displays cumulative quantity and last shipment information,
according to your trading partner.The Epicor application automatically updates these fields each time it
processes incoming EDI transactions that contain cumulative quantity information reported by your customer
trading partner.
Based on the difference between the reported shipment quantities, you can manually enter an adjustment quantity
as needed that creates an invoice charge, or a chargeback credit memo, depending on if the adjustment quantity
is entered as a positive or negative.
Menu Path
Navigate to this program from the Main Menu:
Sales Management > Demand Management > General Operations > Demand Reconciliation

Workshop - Run Demand Reconciliation


Dalton Manufacturing shipped a quantity of 100 to their trading partner according to the demand schedule.
However, the trading partner claimed they only received 50 units. In this workshop, run Demand Reconciliation
to record this quantity variance and generate a chargeback memo.
Navigate to Demand Reconciliation.
Menu Path: Sales Management > Demand Management > General Operations > Demand Reconciliation
1. Click the Demand Reconciliation button to search for and select the demand contract you created in the
Workshop - Enter a Demand Contract.
2. In the Adjustment field, enter -50 to indicate the customer received 50 units less than you shipped.
A chargeback memo is generated for the customer for this quantity.
3. Click Save.
The Variance field displays the cumulative variance quantity. This value is the difference between your
company's reported cumulative quantity and that reported by your customer trading partner.
4. Navigate to the Detail > Adjustment sheet and review the reconciliation line you created.
5. Exit Demand Reconciliation.

32

Epicor ERP | 10.0.700.2

Demand Management Course

Specialized Demand Processing

Workshop - Close a Demand Contract


The demand contract Dalton Manufacturing entered for their customer has not yet expired, but they agreed to
cancel the contract. In this workshop, close the demand contract so no new demand entries can be made against
this contract.
Navigate to Demand Contract Entry.
Menu Path: Sales Management > Demand Management > General Operations > Demand Contract Entry
1. In the Contract field, search for and select the demand contract you created in the Workshop - Enter a
Demand Contract.
2. From the Actions menu, select Close Contract.
The red Closed flag displays on this contract.
3. Exit Demand Contract Entry.

Cumulative Quantities Variances Report


Use the Cumulative Quantities Variance Report to review cumulative quantities and variances calculated for
demand entries. It reports differences between shipment quantity records maintained by your company, and
those maintained by your trading partner.
This report displays information regarding purchase order(s), sales order number(s), trading partner(s), and contract
number(s).
Menu Path
Navigate to this program from the Main Menu:
Sales Management > Demand Management > Reports > Cumulative Variances

Epicor ERP | 10.0.700.2

33

Additional Information - EDI

Demand Management Course

Additional Information - EDI


Electronic Data Interchange (EDI) is the traditional form of exchanging information electronically and is utilized
by many mid- to large-sized suppliers to manage their supply chains more efficiently. Epicor EDI provides an
interface for managing and exchanging electronic documents with your trading partners. It offers direct integration
with your Epicor data, reducing the turnaround time on schedule changes, additions and eliminating potential
data entry errors.
Electronic Data Interchange (EDI) is the traditional form of exchanging information electronically and is utilized
by many mid- to large-sized suppliers to manage their supply chains more efficiently.
Epicor EDI provides an interface for managing and exchanging electronic documents with your trading partners.
It offers direct integration with your Epicor data, reducing the turnaround time on schedule changes, additions
and eliminating potential data entry errors.
The Epicor solution development team is experienced in making EDI work in various environments and offer
enhanced functionality that is tailored to the EDI needs of your business.
Note EDI only supports two-character UOM (unit of measure) codes. If using EDI Import or EDI Export,
limit the length of the UOM codes created in UOM Maintenance to a maximum length of two characters.
Creation of UOM codes in excess of two characters requires customization.

EDI Installation
Inbound text-based EDI transactions received from your customer trading partners and passed by the TIE KINETIX
eVision third-party application directly link to the Epicor application using the Import EDI Demand Process or
through the use of Epicor Service Connect.
Users are on 9.05.607 or above are strongly encouraged to use the Import EDI Demand Process (direct EDI import),
however, you can (optionally) import EDI documents using Epicor Service Connect. The Import EDI Demand
Process runs on a server code; this significantly improves EDI transaction import performance.
Users manage the whole process using the Import EDI Demand Process, located on the Demand Management
General Operations Menu. When the Import EDI Demand process attempts to import EDI transactions, it
performs a series of data validations. You can view and correct data errors using Demand Workbench, which
has the same concept as the Integration Workbench for Multi-Company, and then cancel or resubmit it to
continue the import process.
Service Connect is an optional method that can be used for processing inbound EDI transactions passed by
the eVision third-party application. It generates records in the Epicor application (for further processing by
the Demand Management module) through the use of several pre-defined processing workflows.
The following applications and procedures must be installed and working before utilizing the EDI functionality.
The tasks you perform with guidance from the EDI TIE KINETIX Integration Guide include:
1.

Verifying prerequisite installations, including:


Verifying you have completed the TIE KINETIX Planning Documentation.
Verifying that the TIE KINETIX consultant has properly configured and tested your system. Configurations
include:
Microsoft Internet Information Service (IIS)
ODBC Drivers

34

Epicor ERP | 10.0.700.2

Demand Management Course

Additional Information - EDI

eVision server
communication interface
eVision client / Integrator Translation software

2.

Configuring your Epicor application server.

3.

Configuring Demand Management for EDI inbound and outbound processing.

4.

Performing post- installation steps, including reviewing EDI file layouts, configuring outbound EDI automatic
generation.

If you are using Service Connect in place of the direct EDI import process (Import EDI Demand), you must perform
additional installation and setup tasks. These tasks are similar to those outlined above, but require that you
perform additional setup tasks. Refer to the EDI / Demand Management Technical Reference Guide for
complete details.

EDI File Format


This topic details system requirements for EDI input files. Input files must follow this format exactly, or the EDI
functionality will not run properly.
File format requirements:
Boolean values must be true or false. This must be in all lower case.
Times must be expressed in one of these formats: 15:25:05, 15:25, 152505, 1525
Dates must be in this format: CCYY-MM-DD
The file formats must exactly match the sample file Sample.txt, included as part of your Epicor application
installation. On a standard installation, the file is located in the
\\<server>\Epicor\MfgsysXXX\ESC\EDI\Demand directory, where XXX is the release version, such as 905.
Note For specific information on the EDI Input File Table Hierarchy, refer to the EDI / Demand
Management Technical Reference Guide.

Supported EDI Transaction Types


The Epicor application supports processing of the following types of inbound and outbound EDI ANSI X20 and
AIAG documents, including:
Transaction Type

Description

810/INVOIC

Outbound AR Invoice

830/DELFOR

Inbound Planning Schedule

850/ORDERS

Inbound Purchase Order (PO)

855/ORDRSP, 865/ORDRSP

Outbound PO Acknowledgement

856/DESADV

Outbound Advanced Shipment Notification (ASN)

860/ORDCHG

Inbound Purchase Order Change

Epicor ERP | 10.0.700.2

35

Conclusion

Demand Management Course

Transaction Type

Description

862/DELJIT

Inbound Shipping Schedule

Features of EDI
Additional EDI features include:
Feature

Description

Trading Partners

Set up any number of trading partners for both incoming and outgoing
documents.

Documents

Review incoming documents (830 and 850) online and compare to any current
open orders.

Updates

Ignore, add new or replace imported information into current application sites.

Implementation

Implement EDI at any point in the application implementation site.

Audit

Edit and print incoming and outgoing transactions.

Net Change

Maintain an audit before and after transaction data with the EDI net change
report.

History

Maintain a complete history of all transactions indefinitely.

Third-Party Suppliers

Map data to ASCII files through the Epicor relationship with EDI application
suppliers.

Note Refer to the EDI / Demand Management Technical Reference Guide for detailed information
on the installation and use of EDI in conjunction with the Demand Management module.

Conclusion
Congratulations! You have completed the Demand Management with EDI course.

36

Epicor ERP | 10.0.700.2

Demand Management Course

Index

Index
T
terms maintenance 11

Epicor ERP | 10.0.700.2

37

Additional information is available at the Education and


Documentation areas of the EPICweb Customer Portal. To access
this site, you need a Site ID and an EPICweb account. To create an
account, go to http://support.epicor.com.