CustomerSequenceSchedules TG v2012EE PDF

QAD Enterprise Applications
Enterprise Edition
Training Guide
Customer Sequence
Schedules
70-3206-2012EE
QAD 2012 Enterprise Edition
Lab: Enterprise Edition 2011.1 r01 - Training
Workspace: 10USA > 10USACO
March 2012
This document contains proprietary information that is protected by copyright and other intellectual
property laws. No part of this document may be reproduced, translated, or modified without the
prior written consent of QAD Inc. The information contained in this document is subject to change
without notice.
QAD Inc. provides this material as is and makes no warranty of any kind, expressed or implied,
including, but not limited to, the implied warranties of merchantability and fitness for a particular
purpose. QAD Inc. shall not be liable for errors contained herein or for incidental or consequential
damages (including lost profits) in connection with the furnishing, performance, or use of this
material whether based on warranty, contract, or other legal theory.
QAD and MFG/PRO are registered trademarks of QAD Inc. The QAD logo is a trademark of QAD
Inc.
Designations used by other companies to distinguish their products are often claimed as
trademarks. In this document, the product names appear in initial capital or all capital letters.
Contact the appropriate companies for more information regarding trademarks and registration.
Copyright © 2012 by QAD Inc.
CustomerSequenceSchedules_TG_v2012EE.pdf/qad/mat
QAD Inc.
100 Innovation Place
Santa Barbara, California 93108
Phone (805) 566-6000
http://www.qad.com
Contents
Change Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
About This Course . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Course Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Course Credit and Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Virtual Environment Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
QAD Web Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 1 Introduction to QCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Customer Sequence Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
What Customer Sequence Schedules Do . . . . . . . . . . . . . . . . . . . . . . . . . 6
Where Are You? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
QCS Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
QCS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
QCS Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Processing QCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Schedule Processing Menu (7.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Sequence Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Review Questions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2 Business Considerations . . . . . . . . . . . . . . . . . . . . . . . . .17

EDI eCommerce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
EDI Business Value and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Netting Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Scheduled and Sequence Scheduled Order Precedence . . . . . . . . . . . . . 23
Sequence Scheduled Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Sequenced Scheduled Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Short Term Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Long-term Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Replace Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
iv Training Guide — Customer Sequence Schedules
Consume Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 3 Customer Sequence Schedules Setup . . . . . . . . . . . . . .31

QCS Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Item Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
QCS Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Exercise: Add Item Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Exercise: Create Remaining Item Numbers . . . . . . . . . . . . . . . . . . . . . . 36
Customer Item Maintenance (1.16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Exercise: Create Customer Items for Each Part . . . . . . . . . . . . . . . . . . . 38
Exercise: Add Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Customer Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Customer Maintenance (2.1.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Customer Data Maintenance (2.1.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Ship-To Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Exercise: Create Ship-To Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Customer Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Customer Calendar Maintenance (7.3.1) . . . . . . . . . . . . . . . . . . . . . . . . 46
Exercise: Customer Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
QCS Control Program Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Sequence Schedule Control (7.5.4.24) . . . . . . . . . . . . . . . . . . . . . . . . . . 49
QCS Control Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Sequences Per Container Option: Example . . . . . . . . . . . . . . . . . . . . . . 51
Tolerance Checking: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Print Sequence Range on Pre-Shipper: Example . . . . . . . . . . . . . . . . . . 53
Print Sequence Range on Invoice: Example . . . . . . . . . . . . . . . . . . . . . 54
Exercise: Enable Customer Sequence Schedules . . . . . . . . . . . . . . . . . 55
Customer Controls Maintenance (7.5.4.1) . . . . . . . . . . . . . . . . . . . . . . . 56
Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Generalized Codes Maintenance (36.2.13) . . . . . . . . . . . . . . . . . . . . . . 58
Exercise: Create Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
EDI eCommerce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Set Up EDI eCommerce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Exchange Definition Maintenance (35.15.6) . . . . . . . . . . . . . . . . . . . . . 62
Exchange Definition Maintenance (35.15.8) . . . . . . . . . . . . . . . . . . . . . 63
Application Definition Maintenance (35.15.10) . . . . . . . . . . . . . . . . . . 64
Implementation Definition Maintenance (35.15.13) . . . . . . . . . . . . . . . 65
Transformation Definition Maintenance (35.15.17) . . . . . . . . . . . . . . . 66
Trading Partner Maintenance (35.13.7) . . . . . . . . . . . . . . . . . . . . . . . . . 67
Trading Partner Parameter Maintenance (35.13.10) . . . . . . . . . . . . . . . 68
Sequence Scheduled Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Create a Sequenced Scheduled Order . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Contents v
Customer Scheduled Order Maintenance (7.3.13) . . . . . . . . . . . . . . . . . 71

Tax Data Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Line Item Data Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Order Line Item Data: First Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Order Line Item Data: Second Frame . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Exercise: Create Scheduled Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
QCS Setup Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 4 Loading Sequence Schedule Release. . . . . . . . . . . . . . .79

Load QCS Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Receive Schedule Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Exercise: Planning Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Exercise: Shipping Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Load Sequence Schedule Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Import Sequence Schedule Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Document Import (35.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Shipper Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Exercise: Import Sequence Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Create Sequence Schedule Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Sequence Schedule Maintenance (7.5.4.5) . . . . . . . . . . . . . . . . . . . . . . 95
Daily Shipping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Review Schedule Release Information . . . . . . . . . . . . . . . . . . . . . . . . . 98
Sequence Schedule Inquiry (7.5.4.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Sequence Schedule Report (7.5.4.7) . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Sample Detail Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Sample Report with Sub-Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Exercise: Print Sequence Schedule Report . . . . . . . . . . . . . . . . . . . . . 103
Sequence Schedule Variance Report (7.5.4.16) . . . . . . . . . . . . . . . . . . 104
Plan/Ship Sequence Variance Report (7.5.4.17) . . . . . . . . . . . . . . . . . 105
Chapter 5 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Plan QCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Generate RSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Required Ship Schedule Update (7.5.5) . . . . . . . . . . . . . . . . . . . . . . . . 111
Required Ship Schedule Update Report: Sequence Schedule . . . . . . . 113
Required Ship Schedule Update Report: Shipping Schedule . . . . . . . 114
Required Ship Schedule Update Report: Planning Schedule . . . . . . . 115
Required Ship Schedule Update Report: Netting Options Section . . . 116
Required Ship Schedule Update Report: RSS Schedule . . . . . . . . . . . 117
Selective Req Ship Sched Update (7.5.6) . . . . . . . . . . . . . . . . . . . . . . 118
Exercise: Required Ship Schedule Update . . . . . . . . . . . . . . . . . . . . . 119
Run MRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
vi Training Guide — Customer Sequence Schedules
MRP - Calculating Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

MRP Detail Inquiry (23.16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
MRP Detail Inquiry: Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Plan QCS Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Chapter 6 Shipping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Shipping QCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Create Pre-Shipper/Shipper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Shipping QCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Sequence Pre- Shipper - Automatic (7.5.4.10) . . . . . . . . . . . . . . . . . . 132
Picklist/Pre-Shipper: Sample Report . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Sequence Pack List: Sample Report . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Picklist/Pre-Shipper - Automatic (7.9.1) . . . . . . . . . . . . . . . . . . . . . . . 135
Shipper Gateway (7.9.22) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Shipper Gateway: Sample Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Pre-Shipper/Shipper Workbench (7.9.2) . . . . . . . . . . . . . . . . . . . . . . . 138
Carrier Detail Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Shipper Workbench Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Display Sequences Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Adding Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Display Sequence Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Trailer Information Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Print Shipper Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Exercise: Create Daily Pre-Shipper . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Exercise: Change Status to Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Exercise: Change Status and Shipping Date . . . . . . . . . . . . . . . . . . . . 147
Exercise: Print Pre-Shipper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Confirm Shipper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Confirm Shipper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Pre-Shipper/Shipper Confirm (7.9.5) . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Pre Shipper/Shipper Confirm: Invoice Options . . . . . . . . . . . . . . . . . . 153
Pre-Shipper/Shipper Confirm: Print Options . . . . . . . . . . . . . . . . . . . . 154
Exercise: Confirm the Shipper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Exercise: Change Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Send Shipper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Send Shipper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Pre-Shipper/Shipper Print (7.9.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Send ASN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Shipment ASN Export (35.4.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Sequence Shipper Report (7.5.4.11) . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Invoicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Invoicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Invoicing Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Contents vii
Shipping QCS Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Chapter 7 Features and Options . . . . . . . . . . . . . . . . . . . . . . . . . . .167

Multi-Item Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Multiple Delivery Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Multiple Delivery Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Deleting Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Sequence Schedule Maintenance (7.5.4.5) . . . . . . . . . . . . . . . . . . . . . 174
Sequence Schedule Detail Delete (7.5.4.22) . . . . . . . . . . . . . . . . . . . . 175
Schedule Delete/Archive (7.5.23) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Sequence Cross References\ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Sequence Cross-Ref Maintenance (7.5.4.13) . . . . . . . . . . . . . . . . . . . . 179
Linked Sequence Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Sequence Cross-Ref Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Sequence Cross-Ref Report: Sample Report . . . . . . . . . . . . . . . . . . . . 182
Cumulative Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Manually Create Sequence Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Print Sequence Schedule Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Set Up Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Scheduled Order - Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Current Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
New Schedule Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Design Alternative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Selected Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
E-R Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Schema Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Programming Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Required Ship Schedule Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Picklist/Pre-Shipper- Automatic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
eCommerce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
viii Training Guide — Customer Sequence Schedules
Change Summary
The following table summarizes significant differences between this document and the last
published version.
Date/Version Description Reference
September 2011.1 EE Rebranded for QAD 2011.1 EE ---
March 2012 EE Rebranded for QAD 2012 EE ---
x Training Guide — Customer Schedules
About This Course
Course Description
QAD designed this course to cover the basics of preparing to implement the Customer Sequence
Schedules (QCS) module of QAD Enterprise Applications. The course includes:
• An introduction to the QCS module
• An overview of key business considerations
• Setting up the QCS module
• Operating the QCS module
• Activities and exercises throughout the course
• Students practice key concepts and processes in the QCS module
Course Objectives
By the end of this class, students will:
• Analyze some key business decisions before setting up the QCS module
• Set up and operate the QCS module
Audience
• Implementation consultants
• Members of implementation teams
• Key users
Prerequisites
• Initial QAD Enterprise Applications Setup training course
• Customer Schedules training course
• Basic knowledge of how QAD Enterprise Applications is used in the business
• Working knowledge of the manufacturing industry in general
Note It is recommended that students unfamiliar with QAD Enterprise Applications work
through the User Interface Guide before attending this class.
Course Credit and Scheduling

This course is designed to be taught in a day
2 Training Guide — Customer Sequence Schedules
Virtual Environment Information

The hands-on exercises in this book should be used with the Enterprise Edition 2011.1 r01 -
Training environment, in the 10USA > 10USACO workspace.
QAD Web Resources

From QAD’s main site, you can access QAD’s Learning or Support sites.
http://www.qad.com/
Chapter 1
Introduction to QCS
Introduction to Customer Sequence Schedules

• Course Overview
• What are Customer Sequence Schedules
• What Does It Do
• Where is QCS in the System
• QCS Work Flow
• QCS Example
• Terminology
• QCS Life Cycle
• Processing QCS
• Customer Sequence Schedules Menu
- Sequence Schedules Menu
• Related Sources
• Summary
CSS-IN-040
Introduction to QCS 5
What Sequence Schedules Do

• QCS allows you to ship products in a particular,
customer specified, sequence by letting you add
sequence delivery information to a customer
schedule order. Using QCS you can:
- Set up default sequence schedule details
- Manage short term requirements that include the
sequence in which those requirements will be consumed
- Use the sequence schedule data to plan your production
and shipping of the customer’s requirements
- Receive incoming customer sequence schedules using EDI
eCommerce
- Selectively include sequence requirement information
CSS-IN-050
Customer Sequence Schedules
Sequence Schedule Documents and Variances

• View variances between shipping or
planning schedules and sequence
schedules or between different releases of a
sequence schedule
- Generate sequence packing lists automatically
when creating pre-shippers and shippers
- Print sequence packing lists in forward or reverse
order
- Maintain detailed picking records for all
sequenced requirements
- Maintain multiple sequence schedule releases
CSS-IN-060
The Customer Sequence Schedules (QCS) functionality enhances the current Customer Schedules
module.
• Allows you to receive and process shorter term, detailed customer sequence schedules
• Sent by an Electronic Data Interchange (EDI) or EDI eCommerce
• Document type 866
What Customer Sequence Schedules Do

QCS allows you to ship products in a particular, customer specified, sequence by letting you add
sequence delivery information to a customer schedule order. Using QCS you can:
• Set up default sequence schedule details
• Customize the default sequence schedule information for individual customer/ship-to
• Dates, times, items, quantities
• Destination information
• Desired packing order
• Manage short term requirements that include the sequence in which those requirements will be
consumed
• Use the sequence schedule data to plan your production and shipping of the customer’s
requirements
Where Are You?
Where Are You?

You are here
Planning
Shipping Customer
Customers
Sequence Schedules
QAD
Enterprise
Applications
Planning
Supplier
Shipments Schedules Shipping
Suppliers
Shipments
CSS-IN-090
Receive incoming customer sequence schedules using EDI eCommerce.

Selectively include sequence requirement information on:
• Picklist/Pre-Shipper
• Shipper
• Invoice
• Advanced Ship Notice (ASN)
• Required Ship Schedule (RSS)
View variances between shipping or planning schedules and sequence schedules or between
different releases of a sequence schedule.
• Generate sequence packing lists automatically when creating pre-shippers and shippers
• Print sequence packing lists in forward or reverse order
• Maintain detailed picking records for all sequenced requirements
• Maintain multiple sequence schedule releases
Customer sequence schedules is part of the customer schedules functionality found in QAD
Release Management.
QCS Workflow
QCS Work Flow
Seq Qty Item VIN Line Feed
1 1 Dashboard, Red ABC123 LF210
2 1 Dashboard, Green DEF435 LF210
3 1 Dashboard, Blue XYZ789 LF210
4 1 Dashboard, Green AEG434 LF210
5 1 Dashboard, Blue JWZ551 LF210

...
30 1 Dashboard, Blue UIV331 LF210
CSS-IN-100
Some customers need a particular delivery sequence in order to facilitate the consumption of the
parts by their own assembly process.
• Existing Customer Schedules functionality did not meet this requirement
This type of shipping is becoming increasing popular with customers requiring larger
subassemblies that are similar, but differ in color, size, or other optional features.
• Sun Roofs
• Dashboards
• Seats
Many companies that operate in just-in-time (JIT) environments regularly provide detailed
customer sequence schedules to their key suppliers.
These sequence schedules:
• List requirements in the order needed by the customer to build their products
• Can specify a delivery date and time
• Can specify a dock and assembly line-feed delivery location
For example, in a JIT manufacturing environment such as automotive manufacturing, the supplier
would provide subassemblies that are similar, but different in color, size, or other optional features
(e.g., seating, sun roofs) directly to the original equipment manufacturer (OEM). The OEM
schedules the production of the vehicles, including colors and options. These requirements, as well
as the order (i.e., sequence) in which they are required, are sent to the supplier in a production
sequence schedule or 866 document.
Suppliers receiving these customer sequence schedules need accurate and timely visibility into
customer production line activity. They use the sequence schedule requirements to plan the
manufacturing and delivery of the correct parts, in the correct sequence, to their customers. The
sequence information also alerts them to any fluctuations in customer production.
QCS Example
QCS Example
Sequence
Delivery
Order
Location
Needed Seq Qty Item VIN LineFeed

LF210
2 1 Dashboard, Grn DEF435 LF210

LF210
3 1 Dashboard, Blue XYZ789 LF210

LF210
4 1 Dashboard, Grn AEG434 LF210

LF210
5 1 Dashboard, Blue JWZ551 LF210

LF210

LF210
...
30 1 Dashboard, Blue UIV331 LF210
LF210
CSS-IN-110
Terminology
Terminology
• Customer Dock
• Customer Job
• Customer Reference
• Customer Sequence
• Line Feed
• Packing Order
• Sequence Pack List
CSS-IN-120
Customer Dock
Identifies dock location within the customer’s site for material to be delivered
Customer Job
Customer supplied ID
• Identifies customer’s production process
• Can contain alphanumeric values
• For example, date – 02/07/2009
Customer Reference
Identifies the customer’s end item

• VIN (automotive)
• Serial Number
• Used as an ID to track sequences
• Must be unique
Customer Sequence
Customer supplied ID
• Identifies order of assemblies in their production process
• Can contain alphanumeric values
• For example, A001, A002, B001
Line Feed
Identifies location within customer’s site for material to be delivered.
Packing Order
Indicates how the material is to be packed according to the customer’s preference.

• Two types:
• Forward
• Reverse (i.e., first on top)
Sequence Pack List
New document that accompanies pre-shipper (total quantity)

• Displays items in sequence
• Facilitates material handling
• Staging
• Shipping
QCS Life Cycle
QCS Life Cycle
CSS-IN-130
Processing QCS
Processing QCS
CSS-IN-140
The typical procedure for processing a customer’s sequence scheduled order is:
1 Create a sequence scheduled order for a customer.
2 Import the sequence schedule release from the customer.
• Long term planning schedule outlining the customer’s requirements (e.g., dates, quantities)
• Short term shipping schedule outlining what to ship day-to-day (optional)
3 Create the RSS to determine the required quantities for the customer’s sequenced scheduled
order.
4 Using information from the RSS, determine the planning requirements for the sequence
scheduled order.
5 Pick items being shipped.
6 Ship the ordered items.
Schedule Processing Menu (7.5)
Schedule Processing Menu
CSS-IN-150
Access to the QCS functions.

Sequence Schedules
Sequence Schedules
CSS-IN-160
Use the Sequence Schedules menu to access the QCS functions.
Review Questions:
1 What kinds of shipments demand Sequence Schedules? (Large subassemblies with optional
features)
2 What are the advantages of QCS over standard Customer Schedules? (shorter lead times,
greater detail)
3 What technology is required to transmit Sequence Schedules? (EDI)
4 What document type is transmitted? (866)
5 Can picklists include Sequence Schedules? (Y)
Chapter 2
Business Considerations
In this section you learn how to:
• Identify key business considerations before
setting up QCS in QAD Enterprise
Applications
• Set up QCS in QAD Enterprise Applications
• Loading QCS in QAD Enterprise Applications
• Planning QCS in QAD Enterprise Applications
• Shipping QCS in QAD Enterprise Applications
• QCS Features and Options
CSS-BU-010
Business Considerations 19
• EDI/EDI eCommerce
• Netting Logic
CSS-BU-020
There are several business considerations to look at before setting up QCS in QAD Enterprise
Applications. This section does not discuss all potential considerations, but presents some to
generate thought and discussion.
EDI eCommerce
EDI eCommerce
• Definition of EDI
- An international protocol defining the means
and methods for electronic transmission of
documents between trading partners (i.e.,
companies). Documents are transmitted in a
highly structured format that can be processed
by computer software.
• Definition of EDI eCommerce
- EDI eCommerce is the interface between QAD
Enterprise Applications and third-party EDI
communications or translator products called EC
subsystems. The eCommerce enhances the
system’s ability to manipulate, analyze, edit, and
reprocess EDI data.
CSS-BU-021
EDI Business Value and Features
EDI Business Value and Features

• Time saving
- Information processed faster
- Shortened response times
• Reduced data input
- Reduces errors
• Saves labor costs
- Reduces/eliminates paperwork, fewer people are needed
• Lower inventory levels
• Functionality in QAD Enterprise Applications
- Support import of customer sequence schedules
- Support export of invoices and ASNs
• Setup Implications
- EDI/eCommerce software, files, etc., need to be setup
• Discussed in the following Training Guide: EDI/eCommerce
CSS-BU-022
Netting Logic
Netting Logic
Definition
• Netting logic determines how Required Ship Schedule Update
(7.5.5) calculates a new release of the RSS. It uses netting logic
to interpret quantities from the planning, shipping, and
sequence schedules to arrive at the correct input for MRP
(Material Requirements Planning).
• Why Consider
- Customer sends sequence, planning, and shipping schedules
• Need to tell system how to handle the schedules when calculating
the RSS
• Functionality in QAD Enterprise Applications
• There are four options. The system uses the one you select to
determine:
- Which schedule to use to calculate the RSS
- How to handle overlap in planning, shipping, and sequence
schedules
• Netting logic works differently when sequences are associated
with a scheduled order line item.
CSS-BU-023
Scheduled and Sequence Scheduled Order Precedence
Scheduled and Sequence Scheduled Order

Precedence
• For scheduled orders without sequence schedules:
- Option 1 – uses only the shipping schedule
- Option 2 – uses only the planning schedule
- Option 3 – combines planning and shipping schedule, with
the shipping schedule taking precedence in the interval
the schedules overlap
- Option 4 – combines the planning and shipping schedules,
with the greater of the shipping or planning schedule
taking precedence in the interval of the schedule overlaps
• For scheduled orders with sequence schedules:
- Option 1 – uses sequence and shipping schedule
- Option 2 – uses sequence and planning schedule
- Option 3 – combines sequence, planning, and shipping
schedule, with the sequence schedule taking precedence
over the shipping schedule, then the shipping schedule
taking precedence in the interval the shipping and
planning schedules overlap
CSS-BU-024
For scheduled orders without sequence schedules:

• Option 1 – uses only the shipping schedule
• Short-term planning
• Option 2 – uses only the planning schedule
• Long-term planning
• Option 3 – combines planning and shipping schedule, with the shipping schedule taking
precedence in the interval the schedules overlap
• Replace logic
• Option 4 – combines the planning and shipping schedules, with the greater of the shipping or
planning schedule taking precedence in the interval of the schedule overlaps
• Consume logic
Note Discussed in the following Training Guide: Customer Schedules.
Sequence Scheduled Orders

For scheduled orders with sequence schedules:
• Option 1 – uses sequence and shipping schedule
• Short-term planning
• Option 2 – uses sequence and planning schedule

• Long-term planning
• Option 3 – combines sequence, planning, and shipping schedule, with the sequence schedule
taking precedence over the shipping schedule, then the shipping schedule taking precedence in
the interval the shipping and planning schedules overlap
• Replace logic
• Option 4 – combines sequence, planning, and shipping schedules, with the greater of the
shipping or planning schedule taking precedence in the interval of the schedule overlaps
• Consume logic
Setup Implications
• Customer Scheduled Order Maintenance (7.3.13) needs to reflect the netting logic used for
this customer’s sequence scheduled order
• Each sequence scheduled order can have a different netting logic
Note See in this training guide: Create Sequence Schedule Order (under Set Up Customer
Sequence Schedules).
Sequenced Scheduled Orders
Sequenced Scheduled Orders

Short Term Netting Sequence Schedules Shipping Schedules Planning schedules
Scheduled Orders 1
Sequences 1 2
Long Term Netting
Scheduled Orders 1
Sequences 1 2
Replace Logic
Scheduled Orders 1 2
Sequences 1 2 3
Consume Logic
Scheduled Orders 2 1
Sequences 1 3 2
CSS-BU-025
Short Term Planning
Netting Logic – Short-term Planning
Firm
Days
Sequence
Ship
Without Sequences
RSS
With Sequences
RSS
Shipping
CSS-BU-030
System uses the sequence and the shipping schedule to calculate the RSS.
• To determine the number of sequence schedule days, the system uses the number of Firm Days
specified in the sequence scheduled order
• Specified in Customer Scheduled Order Maintenance, Sequence Delivery Data frame
• Shipping schedule is appended to the end of the sequence schedule days
• In other words, the beginning of the shipping schedule is replaced by the number of days
specified by the Firm Days in the sequenced scheduled order
Using the above graphic as an example, the Firm Days are six.
• When calculating the RSS with sequences, the calculation starts with the sequence schedule
for the first six days
• After six days, the calculation goes to the shipping schedule
Long-term Planning
Netting Logic – Long-term Planning
Firm
Days
Sequence
Plan
w/o Sequences
RSS
w/ Sequences
RSS
CSS-BU-040
The system uses the sequence and planning schedule to calculate the RSS.
• To determine the number of sequence schedule days, the system uses the number of Firm Days
specified in the sequence scheduled order
• Specified in Customer Scheduled Order Maintenance, Sequence Delivery Data frame
• Planning schedule is appended to the end of the sequence schedule days
• In other words, the beginning of the planning schedule is replaced by the number of days
specified by the Firm Days in the sequenced scheduled order
• After six days, the calculation uses the planning schedule
Replace Logic
Netting Logic – Replace Logic
Firm
Days
Sequence
Ship
Plan
w/o Sequences
RSS
w/ Sequences
RSS
CSS-BU-050
System combines the sequence, planning, and shipping schedules. Calculation starts with the
specified sequence schedule days, followed by the shipping schedule, then the planning schedule.
• Sequence schedule days takes precedence over the shipping and planning schedule
• Shipping schedule takes precedence over the planning schedule
• After six days, the calculation goes to the shipping schedule
• If the planning schedule extends beyond the shipping schedule, that is used after the shipping
schedule
Consume Logic
Netting Logic – Consume Logic

Firm
Days
Sequence
Ship
Plan
w/o Sequences
RSS
w/ Sequences
Shipping
RSS
CSS-BU-060
The system uses the sequence, shipping, and planning schedules to calculate the RSS.
• The sequence schedule is processed first
• The shipping schedule is processed after the sequence schedule
• The planning schedule is processed last
The schedule consumes the shipping schedule. The shipping schedule consumes the planning
schedule. Any discrepancy is reconciled in the last daily bucket.
Review Questions
1 In what instances would you choose Replace Logic?
2 What events occur if a customer sends you a revised sequence schedule one day prior to
shipment? One hour?
3 How does MRP impact schedules?
Chapter 3
Customer Sequence Schedules

Setup
QCS Setup
• Item Records *
• Customer Records *
• Customer Calendars
• QCS Control Programs
• Status Codes
• EDI eCommerce *
• Sequence Scheduled Order
* Optional
CSS-SU-020
Customer Sequence Schedules Setup 33
QCS Setup
Setting Up QCS Involves the Following

• Review and update item records.
• Review and update customer records.
• Set up customer calendars.
• Set up QCS control programs.
- Enable QCS.
- Define system-wide control parameters.
- If desired, define customer control parameters.
• Define parameters for EDI eCommerce.
• Create sequence scheduled order.
CSS-SU-030
This illustration is a suggested setup sequence of master records for the QCS module which is
based on information that flows from one master record to another and prerequisites that need to
be accomplished before setting up records.
Item Records
QCS Setup
• Item Records *
• Status Codes
• EDI eCommerce *
* Optional
CSS-SU-040
Before creating a sequence scheduled order, item records must exist for all items and products
stored in inventory that you will be shipping. The Item Master table contains records for all items,
regardless of site. Item records hold the default information about items.
• If you are using shipping containers, you must set up container item numbers
To add item records, use one of the following:

• Item Master Maintenance (1.4.1)
• Item Data Maintenance (1.4.3)
QCS Exercises
You have just been awarded a huge contract with Namaka Motor Company. You are the sole
supplier to two Namaka plants, supplying five styles of sunroof from your finished goods
inventory. Namaka is a JIT automotive assembler who does not want to have a huge investment of
your parts in inventory so they require you to deliver sunroofs at the time they are needed and in
the order of their assembly line process. Namaka will be sending you a daily schedule from each
plant containing the requirements for the next three days in the order of consumption. You are
going to use Customer Sequence Schedules to support your Namaka account.
The data used in these exercises may not be the same as the data shown in the screen captures in
this lesson. In an exercise, if a field is not listed, you can accept the default value or leave it blank.
Exercise: Add Item Record

Create first new item record for the new Namaka contract.
Use Item Master Maintenance (1.4.1).
1 Create an item record for the sunroof by entering the following:
Field Data
Item Number: part1
UM: EA
Description: sunroof, red
2 Advance to the Item Data frame and enter:

Field Data
Prod Line: 10
Promo Group: IND
Status: ACTIVE
3 Advance to the Item Inventory Data frame and enter:

Field Data
Site: 10-200
Location: 100
4 Advance to the Item Shipping Data frame and enter:

Field Data
Ship Weight: 5 LB
Net Weight: 3 LB
5 Advance to the Item Planning Data frame and enter:

Field Data
Pur/Mfg: M
Mfg LT: 1
6 Advance to the Item Price Data frame and enter:

Field Data
Price: 100.00
Exercise: Create Remaining Item Numbers

Since you have already created one item number, you can now use that as the basis for the
remaining four sunroofs. This is done by copying the data from the first item record (part).
Use Item Master Copy (1.4.12).
1 To create the second item record using the data from the first enter:
Field Data
Copy Item Number: part1
To: part2
Description: sunroof, green
2 Create the third item record by entering:

Field Data
To: part3
Description: sunroof, blue
3 Create the fourth item record by entering:

Field Data
To: part4
Description: sunroof, black
4 Create the fifth item record by entering:

Field Data
To: part5
Description: sunroof, clear
Customer Item Maintenance (1.16)
Customer Item Maintenance
Must exist in
Item Master File
Prints on
Shipper & ASNs
CSS-SU-060
Use Customer Item Maintenance (1.16) to set up cross-references between:

• Your internal item numbers and your customer’s item numbers
• You can choose to have one or both item numbers appear on all sales and shipping
paperwork
On sales quotes and sales orders the item number can only be 18 characters long.
• Internal numbering systems, industry standard (UPC), or marketing catalog numbers
• By leaving the Customer field blank, the cross-reference will apply to all customers
Exercise: Create Customer Items for Each Part

Namaka uses their own customer item numbers for each part and wants to have that item number
referenced on the sequence scheduled order.
Use Customer Item Maintenance (1.16).
1 To create a customer item for the first part, enter:
Field Data
Customer /Ship-to: <blank>
Customer Item: sunroof, red
Item Number part1
2 Create a customer item for the second part by entering:

Field Data
Customer Item: sunroof, green
Item Number part2
3 Create a customer item for the third part by entering:

Field Data
Customer Item: sunroof, blue
Item Number part3
4 Create a customer item for the fourth part by entering:

Field Data
Customer Item: sunroof, black
Item Number part4
5 Create a customer item for the fifth part by entering:

Field Data
Customer Item: sunroof, clear
Item Number part5
Exercise: Add Inventory

Each part needs to be added to inventory.
Use Receipts - Unplanned (3.9).
1 To add inventory for the first part, enter:
Field Data
Item Number: part1
Quantity: 1000
Field Data
Site: 10-200
Location: 100
2 Add inventory for the second part by entering:

Field Data
Item Number: part2
Quantity: 1000
Site: 10-200
Location: 100
3 Add inventory for the third part by entering:

Field Data
Item Number: part3
Quantity: 1000
Site: 10-200
Location: 100
4 Add inventory for the fourth part by entering:

Field Data
Item Number: part4
Quantity: 1000
Site: 10-200
Location: 100
5 Add inventory for the fifth part by entering:

Field Data
Item Number: part5
Quantity: 1000
Site: 10-200
Location: 100
Customer Records
QCS Setup
• Item Records *
• Status Codes
• EDI eCommerce *
• * Optional
CSS-SU-080
A customer record must exist for each of your customers. The system uses this information to
identify the customer and to determine how to process the customer’s order.
Customer Maintenance (2.1.1)
Customer Create
Customer Create (27.20.1.1)

CSS-SU-090
Use Customer Create (27.10.1.1) to set up and maintain customer records. Customer records
contain information about the customer such as:
• Address (from the associated Business Relation)
• Bill-To Address
• Payment Information
• Defaults
• Credit Data
• Bank Information
• Tax Information
• Comments
Customer Data Maintenance (2.1.1)
Customer Data Maintenance
Customer Data Maintenance (2.1.1)

CSS-SU-120
• Must be completed before you can use new customer record defined in Customer Create.
• Provides additional operational values, such as:
• Site
• Shipping information
Ship-To Address
Customer Ship-to Create
Select customer,
enter Ship-To Code.
Click Create to display
Address Info frame.
CSS-SU-140
• Sold-to customer receives order by default, unless you assign a different ship-to
• Can set up alternate ship-to addresses in Customer Ship-to Create (27.20.2.1)
Exercise: Create Ship-To Address

Namaka want to receive the shipments at a location different from the corporate offices.
Since Nakama is an existing customer, the customer address has already been defined as part of
AR setup. However, you do need to set up a ship-to address.
Use Customer Ship-to Create (27.20.2.1).
1 Create the Ship-To Addresses for the Namaka plant.
Field Data
Customer Code: 30C1002
Ship-to Code: f001
2 Click Create.
3 Enter the following values in required fields in the Address Information frame:
Field Data
Zip/City: 90024 Los Angeles
State: CA
Country Code: USA
4 Click Save.
Customer Calendars
QCS Setup
• Item Records *
• Status Codes
• EDI eCommerce *
* Optional
CSS-SU-160
QAD Enterprise Applications allows you to define calendars matching your customer’s work
schedule (for the ship-to location). The system uses this calendar when calculating shipments for
the customer. This calendar:
• Identifies the customer’s holidays, shutdowns, hours, etc.
• Allows you to calculate a ship date acceptable to you and your customer
Customer Calendar Maintenance (7.3.1)
Customer Calendar Maintenance
Defaults to 8 hours per

day,
Monday through Friday
CSS-SU-170
Use Customer Calendar Maintenance (7.3.1) to set up a customer calendar.

• Useful when a customer has a work schedule different from your company’s work schedule
• Specify your customer’s work days and their hours of operation
• Can specify exceptions to the customer’s calendar
System checks the calendar when calculating the required ship schedule for the customer so
releases do not occur on the customer’s non-working days.
• If you do not set up a customer calendar, system uses your shop calendar (set up in Calendar
Maintenance (36.2.5))
Two additional frames let you specify exceptions to your customer’s regular work week:
• Operating Day Hour Exceptions
• Specify exceptions to the regular work week (e.g., shutdown periods)
• Specify a start and end date
• Reference only, not used in schedule calculations
• Non-Operating Days
• Specify a date
Exercise: Customer Calendar

Create a calendar for the ship-to location.
Use Customer Calendar Maintenance (7.3.1).
1 Create a calendar for the ship-to plant by entering:
Field Data
Customer Ship-To: f001
2 Accept the default values.

QCS Control Program Setup
QCS Control Program Setup

• Sequence Schedule Control (7.5.4.24)
• Customer Controls Maintenance (7.5.4.1)
CSS-SU-190
Control programs contain parameters which tell the system how processing takes place and what
defaults to use. Two control programs are available to use when setting QCS control parameters.
• Sequence Schedule Control (7.5.4.24)
• Required
• Enables QCS
• System-wide, affecting all sequence schedules
• Customer Controls Maintenance (7.5.4.1)
• Optional
• Use to set custom control parameters for an individual customer
• Overrides the settings in Sequence Schedule Control for the individual customer
Sequence Schedule Control (7.5.4.24)
Sequence Schedule Control
Set to Yes to
Activate Sequence
Schedules
CSS-SU-210
Use Sequence Schedule Control (7.5.4.24) to enable QCS functionality and to set the system-wide
defaults.
QCS Control Programs
QCS Setup
• Item Records *
• Status Codes
• EDI eCommerce *
• * Optional
CSS-SU-200
Note When you initially enable QCS, certain programs are automatically updated to be used with
QCS. If you deactivate QCS after enabling it, the modified programs function as they did before
they were updated.
Sequences Per Container Option: Example
Sequences Per Container Option: Example

Ship To: 01000036 S I M U L A T I O N
P I C K L I S T / P R E - S H I P P E R
Northwest Reliable S E Q U E N C E P A C K L I S T
1000 B Street Pre-Shipper: P00000289
Page: 2
Print Date: 02/01/00

Coos Bay
United States of America Container Parameter
Packing Order: forward Customer Dock:

Sequences Per Container: 2 Line Feed:
Customer Job
Pack Customer Sequence
Seq Customer Reference Item Number Quantity UM Status
---- ------------------------------ ------------------ ------------ -- --------
1 20000131 88-100 1.0 EA
001
1R1234XYZ006
Separator
2 20000131 88-100 1.0 EA
002
1R1234XYZ007
Container ( )
3 20000131 88-100 1.0 EA

003
1R1234XYZ008
4 20000131 88-100 1.0 EA
004
1R1234XYZ009
Container ( )
CSS-SU-220
The above shows an example of a Sequence Pack List and the number of sequences per container
for a shipment.
• Sequences Per Container field set to 2 in the control file
• Two sequences are to be packed in each container
Tolerance Checking: Example
Tolerance Checking: Example
System displays
a warning message
WARNING: SEQUENCE TOLERANCE EXCEEDED. PRIOR SEQUENCE:006
CSS-SU-230
The above shows an example of tolerance checking in effect when adding a sequence record in
Sequence Schedule Maintenance (7.5.4.5).
• Check Sequence Tolerance option is turned on
• Specified Maximum Tolerance value exceeded
Print Sequence Range on Pre-Shipper: Example
Print Sequence Range on Pre-Shipper: Example

Quality Products Inc. P R E - S H I P P E R
Div/Consolidated Corporation
Suite 1, Consolidated Bldg. Pre-Shipper ID: P00000288
One Consolidated Plaza Ship Date: 02/01/00
San Diego, CA 92130 Print Date: 02/01/00
Page: 1
United States of America
Sold To: 01000036 Ship To: 01000036
Northwest Reliable Northwest Reliable

1000 B Street 1000 B Street
Coos Bay Coos Bay
United States of America United States of America
Ship Via: Mode of Transport:

FOB Point: ESCONDIDO Carrier Shipment Ref: P00000288
Vehicle ID:
Sequence Ranges
Cumulative
Item Number PO Number Qty Shipped Qty Shipped UM
-------------------------- ---------------------- ----------- -------------- --
88-100 5.00 5.00 EA
Sequence Ranges
Customer Job: 20000128
Customer Sequence To
------------------------------ ------------------------------
001 005
CSS-SU-240
Sequence Range on Pre-Shipper

The above shows an example of a sequence range printed on a pre-shipper.
Set the Print Sequence Range on Shipper field to Yes in the control program.
Print Sequence Range on Invoice: Example
Print Sequence Range on Invoice: Example
Quality Products Inc. I N V O I C E

Div/Consolidated Corporation
Suite 1, Consolidated Bldg. Invoice: IV645 Revision: 0
One Consolidated Plaza Invoice Date: 02/01/00 Page: 1
San Diego, CA 92130 Print Date: 02/01/00
Bill To: 01000036 Sold To: 01000036
Sequence
. Ranges
.
Item Number UM Shipped Backorder Tax Price Ext Price

------------------ -- ---------- ---------- --- --------------- ----------------
88-100 EA 5.0 0.0 no 100.00 500.00
CASE,AUTO-UNIT
Customer Job: 20000128
Sequence Ranges
Customer Sequence To
------------------------------ ------------------------------
001 005
CSS-SU-250
Sequence Range on Invoice

The above shows an example of a sequence range printed on an invoice.
• Print Sequence Range on Invoice field set to Yes in control program
Including sequence information on the invoice gives the supplier and the customer better visibility
of the items being shipped and received.
• Sequence information on the invoice can be used for self-billing
Exercise: Enable Customer Sequence Schedules

Before you can create a sequence scheduled order, you must enable sequence schedules.
Use Sequence Schedule Control (7.5.4.24).
1 Turn on the Customer Sequence Schedules module if it is not already enabled and define other
parameters. Use the values from the following table.
Field Data
Enable Sequence Schedules: Yes
Schedule Order Default: Yes
Include Seq in Req Ship Sched: Yes
Firm Days: 0
Packing Order: Forward
Sequences Per Container: 0
Merge Schedules: No
Check Sequence Tolerance: No
Maximum Tolerance: 0
Print Sequence Range on Shipper: Yes
Print Sequence Range on Invoice: Yes
Send Sequence with ASN: Yes
Send Sequence with Invoice: Yes
Customer Controls Maintenance (7.5.4.1)
Customer Controls Maintenance
Settings Only Apply To This

Customer/Ship-To Address
CSS-SU-270
Use Customer Controls Maintenance (7.5.4.1) to create customer control records. These are
customer specific default values that are different from the system wide default values specified in
Sequence Schedule Control (7.5.4.24). This gives you the ability to set up customize parameters
for an individual customer or ship-to address.
• Except for the Ship-To, all values default from Sequence Schedule Control
• Settings entered here default to sequence schedules created for the ship-to address
• These settings override the corresponding Sequence Schedule Control settings for the
individual customer/ship-to address
Note Customer control settings are optional.
Status Codes
QCS Setup
• Item Records *
• Status Codes
• EDI eCommerce *
• * Optional
CSS-SU-280
Generalized Codes Maintenance (36.2.13)
Generalized Codes Maintenance
CSS-SU-290
Use Generalized Codes Maintenance (36.2.13) to set up status codes for field rcsd_status.
• Status codes are used in the Status field of Sequence Schedule Maintenance (7.5.4.5)
• Allow you to create user-defined entries (e.g., Offline)
• Can use to create a Blank status code
• Value field would be <blank>
• Creating status codes is optional
Exercise: Create Status Codes

In the following exercises you need to use status codes.
Use Generalized Codes Maintenance (36.2.13).
1 Create three status codes entries. Enter the following:
Field Data
Field Name: rcsd_status
2 Create a second status code by entering:

Field Data
Value: 9000
Comments: 9000-series part - special build
3 Create a third status code by entering:

Field Data
Value: offline
Comments: Vehicle is offline
EDI eCommerce
QCS Setup
• Item Records *
• Status Codes
• EDI eCommerce *
* Optional
CSS-SU-310
Set Up EDI eCommerce
Set up EDI
Trading Partner
Trading Partner
CSS-SU-320
You use the following functions to set up EDI eCommerce data:

• Exchange Definition Maintenance (35.15.6)
• Application Definition Maintenance (35.15.10)
• Transformation Definition Maintenance (35.15.17)
• Trading Partner Maintenance (35.13.7)
• Trading Partner Parameter Maintenance (35.13.10)
Exchange Definition Maintenance (35.15.6)
Exchange Definition Maintenance
CSS-SU-430
Use Exchange Definition Maintenance (35.15.6) to define the layout and content of exchange file
documents.
Note An exchange file defines documents communicated between EC subsystems and QAD
Enterprise Applications.
Exchange Definition Maintenance (35.15.8)
Exchange Definition Maintenance
CSS-SU-440
In this frame you identify the document for which you are creating an exchange file definition.
• Cust-Seq-Sched
Exchange File Field Record: Header Frame

This frame displays only if Fields is set to Yes for the selected record.
Application Definition Maintenance (35.15.10)
Application Definition Maintenance
CSS-SU-450
Use Application Definition Maintenance (35.15.10) to set up individual application template

document definition.
Implementation Definition Maintenance (35.15.13)
Implementation Definition Maintenance
CSS-SU-460
Use Implementation Definition Maintenance (35.15.13) to define the data exchange requirements
for a specific trading partner implementation.
Transformation Definition Maintenance (35.15.17)
Transformation Definition Maintenance
CSS-SU-470
Use Transformation Definition Maintenance (35.15.17) to define the maps needed to convert
between exchange file data and QAD Enterprise Applications data.
• Inbound map representing customer’s sequenced schedule
Trading Partner Maintenance (35.13.7)
Trading Partner Maintenance
CSS-SU-480
Use Trading Partner Maintenance (35.13.7) to:

• Identify the document types that are exchanged with each trading partner
• Set up cross-references between trading partner documents and QAD Enterprise Applications
• Cross-reference the trading partner’s site and address codes to the codes used in QAD
Enterprise Applications
Trading Partner Parameter Maintenance (35.13.10)
Trading Partner Parameter Maintenance
CSS-SU-490
Use Trading Partner Parameter Maint (35.13.10) to assign parameters and values to a variety of
trading partner-specific processing actions, such as setting a logical flag.
Sequence Scheduled Order
QCS Setup
• Item Records *
• Status Codes
• EDI eCommerce *
* Optional
CSS-SU-510
Create a Sequenced Scheduled Order
Create a Sequenced Scheduled Order
Supplier Creates a Sequenced

Scheduled Order
Customer Sends
an Order
CSS-SU-500
You are now ready to create a sequenced scheduled order for your customer. To do this, you do
would use Customer Scheduled Order Maintenance (7.3.13).
• A scheduled order contains the quantities the customer needs and the dates they are needed by
• A sequenced scheduled order tells the supplier’s system that the customer will be sending
sequence schedule releases
Customer Scheduled Order Maintenance (7.3.13)
Customer Scheduled Order Maintenance
Determines the
Transport Lead Time
Yes Indicates This is a

Sequence Scheduled
Order
CSS-SU-520
Use Customer Scheduled Order Maintenance (7.3.13) to create a sequenced scheduled order.
Order Data Frame
In the Order Data frame you set up the scheduled order parameters.
• Setting the Sequenced field to Yes makes this scheduled order a sequenced scheduled order
Tax Data Frame
Tax Data Frame
CSS-SU-540
The order tax data frame displays for the input of Global Tax Management data.
Line Item Data Frame
Line Item Data Frame
CSS-SU-550
In the line item data frame you identify the item being shipped and the line number.
• Item number
• Customer purchase order number (optional)
• Unit of measure (UM)
• Sequence scheduled order line number
• Sequential number
• Can be system assigned or user assignee
Note If your customer has multiple docks, with requirements coming on the same sequence
scheduled order, you should create a line for each dock, with the same item number and different
purchase orders.
The system asks you if you want to copy order details from another purchase order for the same
item.
• If Yes, the system prompts you through the copy
• You need the purchase order number and the sequential line number you are copying from
Order Line Item Data: First Frame
Order Line Item Data: First Frame
CSS-SU-560
There are two Order Line Item Data frames. The first frame contains pricing and inventory
information.
Order Line Item Data: Second Frame
Order Line Item Data: Second Frame
1/3 - Mon/Wed/Fri
Connection with Firm Days
CSS-SU-570
Exercise: Create Scheduled Order
SUV Assembly Plant
You are now ready to create a Scheduled Order

Use Customer Scheduled Order Maintenance 7.3.13
1 Create a scheduled order.
Field Data
Ship-From: 10-200
Ship-To: f001
Order: SO100
2 Advance to the Order Data frame and enter:

Field Data
Sequenced: Yes
3 Advance to the Sequenced Delivery Data frame and enter:

Field Data
Incl Seq in Req Ship Sched: Yes
Firm Days: 0
4 Advance to the line item frame and enter:

Field Data
Item: part1
Line: 1
5 Advance to the second Order Line Item Data frame and enter:
Field Data
Req Sched Days: 5
Req Sched Weeks: 3
Req Sched Months: 1
Netting Logic: 1
6 Return to the line item frame. You are going to create a second line, for part2.
Advance to the line item frame and enter:
Field Data
Item: part2
Line: 2
7 Advance to the second Order Line Item Data Frame and enter:
Field Data
Req Sched Days: 5
Req Sched Weeks: 3
Req Sched Months: 1
Netting Logic: 2
8 Return to the line item frame. You are going to create a third line, for part3.
Field Data
Item: part3
Line: 3
Field Data
Req Sched Days: 5
Req Sched Weeks: 3
Req Sched Months: 1
Netting Logic: 3
10 Return to the line item frame. You are going to create a fourth line, for part4.
Field Data
Item: part4
Line: 4
Field Data
Req Sched Days: 5
Req Sched Weeks: 3
Req Sched Months: 1
Netting Logic: 4
12 Return to the line item frame. You are going to create a fifth line, for part5.
Field Data
Item: part5
Line: 5
Field Data
Req Sched Days: 5
Req Sched Weeks: 3
Req Sched Months: 1
Plan SDP Code: 20 (1/5 Monday through Friday)
Netting Logic: 3
QCS Setup Summary
QCS Setup Summary

• Item Records *
• Status Codes
• EDI eCommerce *
* Optional
CSS-SU-590
Chapter 4
Loading Sequence Schedule

Release
Load QCS Release

Applications
CSS-LD-010
Loading Sequence Schedule Release 81
Load QCS Release
Load QCS Release

• Receive Schedule Release
• Review Schedule release Info
CSS-LD-020
be accomplished before setting up records.
Receive Schedule Release
Load QCS Release

• Receive Schedule Release
• Review Schedule release Info
CSS-LD-030
Once you have set up a customer’s sequence scheduled order, you are ready to start receiving their
schedule releases.
• Sequence schedule releases contain the customer’s demand requirements
• Dates, times, and quantities
• The most recently received schedule release normally supersedes all previous schedule
releases
• Raw and fabrication authorization are an exception to this
• The longest authorizations, calculated by end date, are the valid ones
There are two types of schedule releases supported by QAD Enterprise Applications. Each states
how much of a certain item a customer expects to need and when. The primarily difference
between the two is the planning horizon. The two types of schedule releases are:
• Planning Schedule (830, Delfor)
• Shows long-term planning (e.g., weekly, monthly buckets)
• Shipping Schedule (862, Deljit)
• Shows short-term planning (e.g., daily buckets)
• Usually the more accurate
If there are two schedules, the scheduled order’s netting logic (set up in Scheduled Order
Maintenance (7.3.13)) determines how to combine the schedules to obtain a RSS.
QAD Enterprise Applications retains every schedule the customer sends until you delete them
from the system using Schedule Delete/Archive (7.5.23).
Exercise: Planning Schedule

Note The data used in these exercises may not be the same as the data shown in the screen
captures in this lesson. In an exercise, if a field is not listed, you can accept the default value or
leave it blank.
Note No Planning Schedule needed for Line 1.
Use Customer Plan Schedule Maintenance (7.5.1)

1 Create a planning schedule for line 2 by entering the following:
Field Data
Order: so100
Line: 2
Release ID: 1
2 Advance to the lower frame and enter:

Field Data
Comments: No
Prior Cum Date: <Yesterday’s Date>
Schedule Data Type: Ship
3 Advance to the Schedule Detail Data frame and enter the following:
Date Time Int Reference Quantity Q Cmt Rqm Det
Next Monday W 20 F No No
Monday Week +1 W 25 F No No
Monday Week +2 M 100 F No No
4 Enter Yes when the system prompts you to make this schedule active.
5 Repeat the process, creating a planning schedule for line 3 by entering:
Field Data
Order: so100
Line: 3
Release ID: 1
Note Delete the Ship-From, Ship-To, and Item fields.

Field Data
Comments: No
Field Data
Order: so100
Line: 4
Release ID: 1
Note Delete the Ship-From, Ship-To, and Item Number fields.

Field Data
Comments: No

Field Data
Order: so100
Line: 5
Release ID: 1

Field Data
Comments: No
Exercise: Shipping Schedule

1 Create a shipping schedule for line 1 by entering the following:
Use Customer Ship Schedule Maintenance (7.5.2)
Field Data
Order: so100
Line: 1
Release ID: 1
2 Advance to the lower frame and enter.

Field Data
Comments: No
Next Monday D 5 F No No
Tuesday D 5 F No No
Wednesday D 5 F No No
Thursday D 5 F No No
Friday D 5 F No No
Monday Week +1 D 5 F No No
Tuesday D 5 F No No
Note No Shipping Schedule needed for line 2.
5 Repeat the process, creating a shipping schedule for line 3 by entering:

Field Data
Order: so100
Line: 3
Release ID: 1

Field Data
Comments: No

Tuesday D 5 F No No
Friday D 5 F No No
Tuesday D 5 F No No
Field Data
Order: so100
Line: 4
Release ID: 1

Field Data
Comments: No
Tuesday D 5 F No No

Field Data
Order: so100
Line: 5
Release ID: 1

Field Data
Comments: No
Tuesday D 5 F No No
Friday D 5 F No No
Tuesday D 5 F No No
Load Sequence Schedule Release
Import Sequence Create Sequence

Schedule Release OR Schedule Release
Generate
Run MRP
RSS
Create Pre- Confirm

Invoicing
Shipper/Shipper Shipper
Print Pre- Send

Print Sequence
Pack List
CSS-LD-050
There are two ways to load a schedule release onto the system so you can begin processing the
customer’s order:
• Electronically
• Document Import (35.1) (EDI eCommerce)
• Shipper Gateway (7.9.22) (ASCII file)
• Manually
• Sequence Schedule Maintenance (7.5.4.5)
Import Sequence Schedule Release

OR
Schedule Release Schedule Release
Generate
Run MRP
RSS
Create Pre- Confirm

Invoicing
Print Pre- Send

Print Sequence
Pack List
CSS-LD-060
There are two ways to import a sequence schedule release:

• Import using eCommerce
• Use Document Import (35.1) (EDI eCommerce)
• Import from an ASCII formatted file from an external system
• Use Shipper Gateway (7.9.22)
Document Import (35.1)
Document Import
CSS-LD-070
Use Document Import to start the process of loading standards neutral format (SNF) files from the
eCommerce subsystem, transforming them into formats usable by QAD Enterprise Applications,
and transferring them into the QAD Enterprise Applications database using a gateway program.
The system generates a report on the import process.
Note Import directory specified in Inbound Directory field in eCommerce Control (35.21.13.24).
• If Error, system displays only files containing documents that encountered load errors during
previous imports
Note Stored in the error file directory specified in the Error File Directory field set in eCommerce
Control.
Shipper Gateway
Shipper Gateway
CSS-LD-080
Use Shipper Gateway import an ASCII formatted file.

• Contains fields for customer sequence information
When you import a shipper gateway file from an external system, the system looks for the
corresponding sequence to pick from the sequenced scheduled order. If the corresponding
sequence is not found, the system picks the next available sequence.
Exercise: Import Sequence Schedule

Note You can load the schedule electronically via EDI/eCommerce or load the sequence schedule
manually. Electronically is the preferable method, but if problems occur then load the sequence
schedule manually as described in Appendix B and continue with the exercises.
Use Document Import (35.1)
1 To import the detail sequence schedule enter the following:
Field Data
Import from File/Process: File
Import File/Process Name: train1.886
Report Detail/Summary: Detail
Update: No
Note There should be one warning message, and no error messages.
2 Verify the schedule with the table entries found in Manually Create Sequence Schedule on
page 315.
3 To import the summary sequence schedule enter the following:
Field Data
Import from File/Process: File
Import File/Process Name: train1.886
Report Detail/Summary: Summary
Update: No
Create Sequence Schedule Release

Generate
Run MRP
RSS
Create Pre- Confirm

Invoicing
Print Pre- Send

Print Sequence
Pack List
CSS-LD-090
You can manually enter a sequence schedule release by using Sequence Schedule Maintenance
(7.5.4.5).
Sequence Schedule Maintenance (7.5.4.5)
Sequence Schedule Maintenance
CSS-LD-100
Use Sequence Schedule Maintenance (7.5.4.5) to:

• Manually enter (i.e., create) a sequenced schedule release
• Modify existing sequence schedule releases
• Imported
• Manually created
• Logically delete sequence records
Creating a New Release

When creating a new release, the system gives you the option of copying all non-deleted sequence
records from the current active release to the new release.
If you choose to copy the data from the active release, the system checks to see if any sequences
from the active release have been picked. If sequences have been picked, the system asks if you
want to create cross-references between the sequences on the new release and the corresponding
references on the active release.
• If you choose Yes, the system creates cross-references between the sequences on the new
release and the corresponding references on the active release
You cannot pick sequences from the new release that are cross-referenced to sequences on the
active release. These cross-referenced sequences have already consumed their requirements.
If you choose No, then the system:
• Copies all sequences from the active schedule to the new schedule
• Resets any sequence records previously marked as picked or cross-referenced
Note By resetting the sequences, the system considers them as open requirements.
When you finish creating the new schedule release, the system prompts you to make the new
release the active release.
Header Frame
In the header frame you identify the sequence schedule.
• A scheduled order must already exist for the ship-from/ship-to combination
Sequence Schedule Maintenance (7.5.4.5) Detail Data Frame
Use the Sequence Detail Data frame to:

• Create new sequence records
• Edit existing sequence records
• Mark existing sequence records as deleted
• System makes record inactive for the schedule release
• Sequence record is marked as deleted, but is not physically removed from the database
• To permanently delete the record, use Sequence Schedule Detail Delete 7.5.4.22
Note Deleted sequences remain on the schedule, but are not considered for picking or planning.
Once deleted, sequences are no longer active and cannot be re-activated.
Daily Shipping
Daily Shipping
Each Day Customer

Sends Sequenced
Schedule Release
Supplier Imports
(or Manually Creates)
Sequence Schedule
Release
Supplier Fills and

Ships Order
on Same Day
CSS-LD-110
Some suppliers receive sequence schedule releases every morning for that day’s deliveries.
Basically they ship the same day they receive the schedule release from their customers.
• Supplier ships directly off the sequence schedule release
• No need to create a RSS
• No need to run MRP
• MRP looks out to the future to plan replenishments
• Since sequence schedule release is used for the current day, running MRP is not necessary
Review Schedule Release Information
Reviewing Schedule Release Information

You can use any of the following to review and/or
compare sequence schedule information. This is
particularly useful if you have imported the
sequence schedule information.
• Sequence Schedule Maintenance (7.5.4.5)
• Sequence Schedule Inquiry (7.5.4.6)
- Displays all sequences on a sequence schedule release
• Sequence Schedule Report (7.5.4.7)
- Prints a report showing a complete sequence schedule
release
• Sequence Schedule Variance Report (7.5.4.16)
- Compares two sequence schedule releases
• Plan/Ship Sequence Variance Report (7.5.4.17)
- Compares specific item requirements on the active
sequence schedule to those on the active shipping or
planning schedule release
CSS-LD-120
Sequence Schedule Inquiry (7.5.4.6)
Sequence Schedule Inquiry
Starting Points Allow You

to Determine Where to
Start Looking
CSS-LD-140
Use Sequence Schedule Inquiry (7.5.4.6) to view sequences on a sequence schedule release.
Can view all or all from a specified starting point
Sequence Schedule Report (7.5.4.7)
Sequence Schedule Report
Sequences Marked
as Deleted Not
Included in the Report
CSS-LD-150
Use Sequence Schedule Report (7.5.4.7) to print a report which shows you the complete sequence
schedule release.
• Gives you a snapshot of what is going on
The report criteria gives you the option of:

• Including active or history data
• Including:
• Picked and unpicked sequences
• Only picked sequences
• Only unpicked sequences
• Including sequence records marked as deleted
• If Yes, only sequence records logically deleted will be included in the report
• If No, only sequence records not marked as deleted will be included in the report
Sample Detail Report
Sample Detail Report

rcrp05.p 7.5.4.7 Sequence Schedule Report Date: 01/28/00
Page: 1 Public Test Progress 91 Time: 11:29:02
Ship-From: 10000 nj plant

Customer: GM General Motors
Ship-To: orion Lake Orion Assembly Plant
Release ID: 991210-22 Active: yes
Schedule Date Type: Delivery Create Date: 12/10/99 11:54

Active Start: 12/09/99 Active End: Packing Order: forward
Cumulative: no Sequences Per Container: 0
Check Sequence Tolerance: yes Maximum Tolerance: 2
Date: 12/08/99
Customer Job Item Order Customer Ref Customer Dock Quantity

Customer Sequence Status UM Line PO Line Feed Cum Quantity Delete
------------------------------ ------------------ -- -------- -------------------- -------------------- ------------ ------
100-1 EA ori-test vin9110 1.0 no
9110 1 ori-99
Picked: yes Pre-Shipper/Shipper: shp99087 Confirmed: yes

9111 1 ori-99

9112 1 ori-99

9113 1 ori-99
CSS-LD-160
The above shows an example of a Sequence Schedule Report using the Detail report option.
Sample Report with Sub-Totals
Sample Report with Sub-Totals
rcrp05.p 7.5.4.7 Sequence Schedule Report Date: 01/28/00

Item Sub-Totals By Date
Sub-Total
Date Item Number Description Qty UM
-------- ------------------ ------------------------ ------------ --
12/08/99 100-1 Blue Overhead Interior 5.0 EA
100-2 Gray Overhead Interior 7.0 EA
100-3 Red Overhead Interior 4.0 EA
100-4 Sand Overhead Interior 1.0 EA
CSS-LD-170
The above graphic shows an example of the report with sub-totals broken out by date.
Exercise: Print Sequence Schedule Report

Use Sequence Schedule Report (7.5.4.7)
1 To generate the Sequence Schedule Report enter the following:
Field Data
Ship-To: f001
To: f001
Sub-Totals: Yes
2 Verify all sequences are displayed and the sub-totals are correct for each day.
Sequence Schedule Variance Report (7.5.4.16)
Sequence Schedule Variance Report
Use to Specify the

Sequence Schedules
You Want to Compare
CSS-LD-190
Use Sequence Schedule Variance Report to generate a report that compares sequence schedules of
different releases.
• Variance percentage reported
• Useful when looking for extremes
Plan/Ship Sequence Variance Report (7.5.4.17)
Plan/Ship Sequence Schedule Variance Report
Use to Specify
Percentage Reported
CSS-LD-200
Use Plan/Ship Sequence Variance Report to generate a report comparing sequence schedule to the
shipping or planning schedule.
• Variance percentage reported
Chapter 5
Planning
Plan QCS
Applications
• Plan QCS in QAD Enterprise Applications
CSS-PL-010
Planning 109
Plan QCS
Plan QCS
• Generate RSS
• Run MRP
CSS-PL-020
be accomplished before setting up a record.
Generate RSS
Create Sequence Import Sequence

Generate
Run MRP
RSS
Create Pre- Confirm

Invoicing
Print Pre- Send

Print Sequence
Pack List
CSS-PL-030
The RSS identifies for a particular customer and sequenced scheduled order, what they need you to
ship, on what dates, and by what time.
Basically the RSS has two purposes:
• It supplies MRP with the dates, times, and quantities of the customer’s demands
• Provides the information used to instruct the shipping dock what to ship
You create a new version of the RSS using one of the following:
• Required Ship Schedule Update (7.5.5)
• Selective Req Ship Sched Update (7.5.6)
Planning 111
Required Ship Schedule Update (7.5.5)
Required Ship Schedule Update
Determines if
RSS is created
Required Ship Schedule Update (7.5.5)

CSS-PL-050
Use Required Ship Schedule Update to generate a new RSS.

The RSS:
• Turns customer demand from the schedule release into dates, times, and quantities which you
can then use for planning and production
• Information used to supply MRP allowing it to plan future replenishment orders
• Instructs the shipping dock what needs to be shipped
• Information used to generate the picklist/pre-shipper
Note It is a good idea when first running this process to set Update to No. This gives you the
ability to review the new schedule release prior to actually creating it.
Creating the RSS
When creating the RSS, the system first selects the active schedule release for each schedule type
(e.g., sequence, shipping, planning). Then the system uses the customer requirement information
from active schedule release(s) and the following information to generate the RSS:
• Sequence scheduled order data (e.g., Week Offset, Cumulative, Transport Days, Req Sched
Days, Weeks, Months, standard pack quantity, Netting Logic, and SDP codes)
• Your calendar
• Your customer’s calendar, if necessary
• System uses this to adjust dates or quantities if your customer does not schedule their
requirements to coordinate with your open days, ship schedule, or shipment multiples
• QAD Enterprise Applications back-schedules all date adjustments
If Sequenced is set to Yes in Customer Scheduled Order Maintenance (7.3.13), the system knows
this is a sequence scheduled order and updates the RSS with sequence schedule data. When
sequences are involved:
• Netting logic works differently
• Netting logic is set up in the Netting Logic field of Customer Scheduled Order
Maintenance
• If Include Seq in Req Ship Sched is set to Yes in Customer Scheduled Order Maintenance then
the system includes the number of firm days from the sequence scheduled order
• Defined in the Firm Days field of Customer Scheduled Order Maintenance
Planning 113
Required Ship Schedule Update Report: Sequence Schedule
Required Ship Schedule Update Report: Sequence

Schedule
rcrsup.p 7.5.5 Required Ship Schedule Update Date: 02/03/00

Using ship-to calendar 01000036 Sequence Schedule

Customer Sequence Schedule- Required Quantities
Ship-From: 10000 Order: so2077 Line: 1

Ship-To: 01000036 Northwest Reliable
Item: 88-100 CASE,AUTO-UNIT UM: EA
PO Number:
Release ID: 1
Schedule Date Type: Delivery Create Date: 01/28/00 10:54

Active Start: 01/28/00 Cumulative: noxx
Active End:
Schedule Detail Data

Summarized Quantities
Date Time Reference Quantity
-------- ----- ------------------------ ------------
01/31/00 10:00 4.0
02/01/00 10:00 6.0ccx
CSS-PL-060
The image above shows an example of a Required Ship Schedule Update report using a sequence
schedule.
Required Ship Schedule Update Report: Shipping Schedule
Required Ship Schedule Update Report: Shipping

Schedule
Customer Ship Schedule- Required Quantities

PO Number:
Shipping Schedule
Release ID: 1
Comments: no Create Date: 01/31/00 15:08:02

SDP Code: Cumulative: no
SDT Code:
Int Purpose Code:
Ext Purpose Code: Schedule Date Type: Delivery
Prior Cum Req: 0.0 Active Start: 01/31/00
Prior Cum Date: 01/01/00 Active End:

Rqm
Date Time Int Reference Quantity Q Cmt Det
-------- ----- --- ------------------------ ------------ - --- ---
01/28/00 10:00 d 9.0 F no no
01/31/00 10:00 d 2.0 F no no
02/01/00 10:00 d 5.0 F no no
02/02/00 10:00 d 6.0 F no no
02/03/00 10:00 d 4.0 F no no
02/04/00 10:00 d 9.0 F no no
02/07/00 10:00 d 2.0 F no no
02/08/00 10:00 d 5.0 F no no
CSS-PL-070
The image above shows an example of a Required Ship Schedule Update report using a shipping
schedule.
Planning 115
Required Ship Schedule Update Report: Planning Schedule
Required Ship Schedule Update Report: Planning

Schedule
Customer Plan Schedule- Required Quantities

PO Number:
Release ID: 1
Planning
Schedule
SDP Code: Cumulative: no
SDT Code:
Int Purpose Code:
Ext Purpose Code: Schedule Date Type: Delivery

Rqm
-------- ----- --- ------------------------ ------------ - --- ---
01/24/00 10:00 w 20.0 F no no
01/31/00 10:00 w 15.0 F no no
02/07/00 10:00 w 25.0 F no no
Resource Authorization Data

Fab Qty: 0.0 Fab Start: 01/28/00 Fab End:
Raw Qty: 0.0 Raw Start: 01/28/00 Raw End:
CSS-PL-080
The image above shows an example of a Required Ship Schedule Update report using a planning
schedule.
Required Ship Schedule Update Report: Netting Options Section
Required Ship Schedule Update Report: Netting

Options Section
New Section
Netting Options
Netting Logic: 3 Use Plan & Ship schedules for Req Sched
Use Ship/Plan PCR: no
Plan Schedule Adjustment For Ship Schedule Overlap

Date Time Reference Quantity Adjustment Qty
New Date New Qty
------------------------------------------------------------------------------
02/07/00 10:00 25.0 -7.0
02/09/00 18.0
Combined Schedule
Date Time Reference Quantity From
-------- ----- ------------------------ ------------ ---------------
01/31/00 10:00 4.0 Seq Schedule
02/01/00 Adjustment for Weekly
10:00 6.0 Seq Schedule
Schedule
02/02/00 10:00 6.0 Ship Schedule
02/03/00 10:00 Plan Quantity 4.0 Ship Schedule
Used
02/04/00 10:00 9.0 Ship Schedule
02/07/00 10:00 2.0 Ship Schedule
02/08/00 10:00 5.0 Ship Schedule
02/09/00 10:00 18.0 Plan Schedule
CSS-PL-090
The image above shows an example of a report containing the new section, Netting Options.
Planning 117
Required Ship Schedule Update Report: RSS Schedule
Required Ship Schedule Update Report: RSS

Schedule
New RSS Schedule
Required Ship Schedule- Required Quantities

PO Number:
Release ID: 000002

Cumulative: no
From Plan Id: 1
From Ship Id: 1

Rqm
-------- ----- --- ------------------------ ------------ - --- ---
01/31/00 10:00 D 4.0 4 no no
02/01/00 10:00 D 6.0 4 no no
02/02/00 10:00 D 6.0 2 no no
02/03/00 10:00 D 4.0 2 no no
02/04/00 10:00 D 9.0 2 no no
02/07/00 10:00 D 2.0 2 no no
02/08/00 10:00 D 5.0 2 no no
02/09/00 10:00 D 18.0 1 no no
CSS-PL-100
The image above shows an example of the new Required Ship Schedule.
Selective Req Ship Sched Update (7.5.6)
Selective Req Ship Sched Update
Leave unchecked to
Preview Changes
CSS-PL-110
Use Selective Req Ship Sched Update to determine the sequence schedule requirements using a
specific release.
• You do not necessarily have to use the active release
• System uses the sequence schedule release ID to select the sequence schedule
• Only sequence lines associated with the specified schedule order lines are used
The method for calculating the RSS is the same as used in Required Ship Schedule Update.
Planning 119
Exercise: Required Ship Schedule Update

Important The data used in these exercises may not be the same as the data shown in the screen
leave it blank.
The required ship schedule function identifies what needs to be shipped and when. In this exercise
you are going to see the results of the Netting Logic used when setting up the scheduled order.
Use Required Ship Schedule Update (7.5.5) to run a preview of the required ship schedule by
entering the following:
Field Data
Ship-To: f001
To f001
Update: No
3 Use the following information to verify all of the required ship schedules are correct, based on
the Netting Logic.
Line 1:
Field Data
M-W Requirements from sequence schedule
Th-F Requirements from sequence schedule
Week 2+: Requirements from sequence schedule
Line2:
Field Data
Th Adjustment from weekly planning schedule
Week 2+: Requirements from sequence schedule
Line 3:
Field Data
Th Adjustment from weekly planning schedule
Week 3+ Requirements from sequence schedule
Line 4.
Field Data
F Adjustment from weekly planning schedule if
planning requirements NOT consumed
W Adjustment from weekly planning schedule if

planning requirements NOT consumed
Line 5:
Field Data
M-F Requirements from sequence schedule
Th-F Requirements from shipping schedule
Note The weekly intervals of the planning schedule of Line 5 are distributed according to the
SDP before the requirements are combined.
4 To generate the RSS, enter the following:
Use Required Ship Schedule Update (7.5.5)
Field Data
Ship-To: f001
To f001
Update: Yes
Note If the output report from the Required Ship Schedule Update fails to display, check the
result with Required Ship Schedule Detail Report (7.5.14).
Planning 121
Run MRP
Plan QCS
• Generate RSS
• Run MRP
CSS-PL-140
Once you have the new RSS, you are ready to run MRP. Running MRP determines the planning
requirements for the customer’s demands.
Note MRP only looks at the active RSS.
QAD Enterprise Applications offer you three ways to run MRP.

• Net Change Materials Plan (23.1)
• Calculates requirements only for those items that have changed since the last update
• Many companies use this option for their normal MRP runs
• Regenerate Materials Plan (23.2)
• Generates a plan for all items, not just those that have changed since the last run
• Recalculates demand and plans supply for all items in the site
• Selective Materials Update (23.3)
• Updates only the items and sites you select
MRP - Calculating Requirements
MRP – Calculating Requirements

• Net Change Materials Plan (23.1)
• Regenerate Materials Plan (23.2)
• Selective Materials Plan (23.3)
CSS-PL-150
Planning 123
MRP Detail Inquiry (23.16)
MRP Detail Inquiry
CSS-PL-160
Use MRP Detail Inquiry to see a detailed look at MRP for specified date buckets.
Selection Criteria
Item Number/Site/Start Date

Use one or more of the above criteria to select MRP detail information. To select all, leave the field
blank.
MRP Detail Inquiry: Display
MRP Detail Inquiry: Display
CSS-PL-170
Using your selection criteria, the system shows you the order information from the RSS.
Planning 125
Plan QCS Summary
Plan QCS Summary

• Generate RSS
• Run MRP
CSS-PL-180
Chapter 6
Shipping
Shipping QCS
Applications
CSS-SH-010
Shipping 129
Shipping QCS
Shipping QCS
• Pre-Shipper/Shipper
• Confirm Shipper
• Send Shipper
• Invoicing
CSS-SH-020
be accomplished before setting up a record.
Create Pre-Shipper/Shipper

OR
Generate
Run MRP
RSS
Create Pre- Confirm

Invoicing
Print Pre- Send

Print Sequence
Pack List
CSS-SH-030
The first step in the shipping process is to create a pre-shipper/shipper. The system uses the pre-
shipper/shipper to select and ship inventory. (QAD Enterprise Applications converts pre-shippers
to shippers before shipping.) Use one of the following to create the pre-shipper/shipper:
• Picklist/Pre-Shipper - Automatic (7.9.1)
• Creates pre-shippers for both sequenced and non-sequenced schedules
• Sequence Pre-Shipper - Automatic (7.5.4.10)
• Creates pre-shippers for sequenced schedules
• Shipper Gateway (7.9.22)
• Creates shippers for external systems using an ASCII file
The terms picklist and pre-shipper are synonymous. A pre-shipper describes which items and/or
containers need to be picked for the shipment.
Shipping 131
Shipping QCS
Shipping QCS
• Pre-Shipper/ Shipper
• Confirm Shipper
• Send Shipper
• Invoicing
CSS-SH-040
Sequence Pre- Shipper - Automatic (7.5.4.10)
Sequence Pre-Shipper Automatic
CSS-SH-050
Use Sequence Pre-Shipper - Automatic to create a pre-shipper for sequence schedules.

• Can be for one or a range of sequence schedules
• Only applies to sequence schedules
• Use Picklist/Pre-Shipper - Automatic 7.9.1 to create pre-shippers for non-sequenced and
sequenced schedules
• Only selects unpicked sequences from active schedules
• Selected sequences cannot be marked as deleted, picked, or cross-referenced
• Contains sequence specific criteria
• Job
• Sequence
• Dock
• Line Feed
• Status
• Break on Max Sequence (e.g., truck can hold so many items)
Note You can also use Pre-Shipper/Shipper Print (7.9.4) to print the Picklist/Pre-Shipper report.
Shipping 133
Picklist/Pre-Shipper: Sample Report
Picklist/Pre-Shipper: Sample Report

Ship To: 01000036
Northwest Reliable
Page: 1
Print Date: 02/01/00

Coos Bay
Customer Dock:
Line Feed:
Sales Order: so2077 Order Date: Ship To PO:
Site Lot/Serial Qty Open Due

Ln Item Number T Location Ref Qty to Ship UM Shipped
--- ------------------------------ - -------- ------------------ ----------- -- --------
1 88-100 10000
Revision: AA
CASE,AUTO-UNIT
1R1234XYZ001 1.0 EA 01/28/00
1R1234XYZ002 1.0 EA 01/28/00
1R1234XYZ003 1.0 EA 01/28/00
1R1234XYZ004 1.0 EA 01/28/00
1R1234XYZ005 1.0 EA 01/28/00
100 5.0 ( )
PO Nbr:
CSS-SH-060
The above shows an example of the first page of the Picklist/Pre-Shipper.

Sequence Pack List: Sample Report
Sequence Pack List: Sample Report

Ship To: 01000036
Northwest Reliable S E Q U E N C E P A C K L I S T
Page: 2
Sequence Print Date: 02/01/00
Coos Bay
Packing Order: forward Customer Dock: Second Page of

Sequences Per Container: 0 Line Feed:
Pre-Shipper
Customer Job
Pack Customer Sequence
Seq Customer Reference Item Number Quantity UM Status
---- ------------------------------ ------------------ ------------ -- --------
1 20000128 88-100 1.0 EA
001
1R1234XYZ001
2 20000128 88-100 1.0 EA
002
1R1234XYZ002
3 20000128 88-100 1.0 EA
003
1R1234XYZ003
4 20000128 88-100 1.0 EA
004
1R1234XYZ004
5 20000128 88-100 1.0 EA
005
1R1234XYZ005
CSS-SH-070
If the scheduled order contains sequences, the Sequence Pack List prints after the pre-shipper. It
contains:
• Instructions for dock personnel
• Sequential order of every item in the shipment
• Forward or Reverse (i.e., reverse load packing)
Shipping 135
Picklist/Pre-Shipper - Automatic (7.9.1)
Picklist/Pre-Shipper - Automatic
Selection
Criteria
Creation and
Print Options
CSS-SH-080
Use Picklist/Pre-Shipper - Automatic to generate a pre-shipper for sequenced and non-sequenced

scheduled orders.
• Recognizes sequenced items
• Reads sequence schedule for the requirements
• Creates separate pre-shippers for sequence items and non-sequenced items by Ship-To
Shipper Gateway (7.9.22)
Shipper Gateway
CSS-SH-090
Use Shipper Gateway to build shippers containing sequences.

• Uses an external ASCII file in the designated format to create shippers
• Accepts status codes
You have the option of including sequence values (from customer) or having the system select
available sequences.
Shipping 137
Shipper Gateway: Sample Report
Shipper Gateway: Sample Report

rcshgw.p 99 7.9.22 Shipper Gateway Date: 02/01/00
Page: 1 Your Name Here Time: 17:22:39
Type: s Site: Location:

Ship From: 17500 Number: ESHP000
Part: Lot/Serial: Reference:
Qty: 0 Ship To: 001 Order:
........
Kanban:
Shipper created ESHP000.
Type: i Site: 17500 Location:

Ship From: 17500 Number:
Part: item y Lot/Serial: Reference:
Qty: 10 Ship To: Order: so10063
Line: 1 Parent: sESHP000
Customer PO: po100 Qty UM: EA Ship Weight: 0
Weight UM: Volume: 0 Volume UM:
Net Weight: 0 Ship Via: Fob:
Carrier Ref: Trans Mode:
Vehicle Ref: vin100 Tare Weight:
Customer Job: job1
Customer Seq: seq1
Customer Doc: dock1 Sequence Data
Line Feed: line1 Status: stat1
Kanban:
Item added to shipper item y.
Shipper Gateway: Sample Report (7.9.22)

CSS-SH-100
The above graphic shows an example of a Shipper Gateway report containing sequence
information.
Pre-Shipper/Shipper Workbench (7.9.2)
Pre-Shipper/Shipper Workbench
Leave blank to
have system assign
number
CSS-SH-110
Use Pre-Shipper/Shipper Workbench for the manual maintenance of pre-shippers or shippers.

• Add, view, or delete sequences
• Validates number of sequences on pre-shipper or shipper
Header Frame
In the header frame you identify the pre-shipper or shipper that you want to see. You do this by
specifying:
• Ship-From
• Pre-shipper/shipper number, if existing
• Ship-To
Shipping 139
Carrier Detail Frame
Pre-Shipper/Shipper Workbench: Carrier Detail

Frame
Set to Yes if there is

more than one carrier
CSS-SH-120
Use the Carrier Detail frame to enter carrier data for this shipment (Ship Via, FOB Point, Mode of
Transport).
Shipper Workbench Frame
Pre-Shipper/Shipper Workbench: Shipper

Workbench Frame
1. Select item
2. Modify/view item information
CSS-SH-130
The Shipper Workbench frame shows what items and containers are included in this shipment. The
lower frame shows the shipper detail for individual items or containers.
Shipping 141
Display Sequences Frame
Pre-Shipper/Shipper Workbench: Display Sequences

Frame
CSS-SH-140
You can use the Display Sequences frame to:

• Track quantities on the sequence schedule
• Shows all the sequences on the pre-shipper/shipper
• Displays only if pre-shipper/shipper contains sequences
• Delete sequences
• Access the Add Sequences frame
• Access the Display Sequences frame
Deleting Sequences
The Display Sequences frame can be used to delete sequences.
• Move your cursor to the sequence you want to delete, then select Delete
• System removes the sequence from the pre-shipper/shipper and marks it as an open
requirement
Note Deleting the sequence in Pre-Shipper/Shipper Workbench does not delete the sequence
from the database. It deletes/removes the sequence from the pre-shipper/shipper.
Adding Sequences
Pre-Shipper/Shipper Workbench: Add Sequences

Frame
CSS-SH-150
The Display Sequences frame can be used to access the Add Sequences frame.
• Press the Insert key; the Add Sequences frame displays
Shipping 143
Display Sequence Detail
Pre-Shipper/Shipper Workbench: Display Sequence

Detail Frame
CSS-SH-160
The Display Sequences frame can be used to display sequence detail.

• To see details for an individual sequence, move your cursor to the sequence and press Enter
• The Display Sequence Detail frame displays
Trailer Information Frame
Pre-Shipper/Shipper Workbench: Trailer Information

Frame
CSS-SH-170
Status. Specifies if the shipper is active or cancelled.

• If blank, the shipper is active
• Newly created shipper
• If X, the shipper is cancelled
• You cannot cancel a confirmed shipper
• Cancelled shippers are ignored by the system, except for deleting or archiving
• If C, the shipper is confirmed
• Confirmed in Pre-Shipper/Shipper Confirm (7.9.5)
Shipping 145
Print Shipper Frame
Pre-Shipper/Shipper Workbench: Print Shipper

Frame
CSS-SH-180
In this frame you determine how your pre-shipper/shipper will print.

Exercise: Create Daily Pre-Shipper

Note The data used in these exercises may not be the same as the data shown in the screen
leave it blank.
The pre-shipper describes the items and/or containers that need to be picked for shipment.
Use Sequence Pre-Shipper - Automatic (7.5.4.10).
1 Create pre-shipper for the day by entering:
Field Data
Due Date: <next Monday>
To: <next Monday>
Ship-To: f001
To: f001
Status: 9000
Auto Allocation: Yes
Update: No
2 Verify the Pre-Shipper and Sequence Pack List.

3 Run again with Update set to Yes to generate pre-shipper.
Note If you receive Processing Errors stating: “INVALID SEQUENCE. SEQUENCE HAS
INCORRECT DATASET” refer to the Set Up Sequence Numbers topic of this training guide to
define the correct sequence numbers for pre-shippers and shippers.
4 To generate the Sequence Schedule Report enter the following:
Use Sequence Schedule Report (7.5.4.7)
Field Data
Ship-To: f001
To: f001
Details: Yes
5 Verify all sequences for Monday are associated with pre-shipper number.
6 To check the sequence schedule enter the following:
Use Sequence Schedule Maintenance (7.5.4.5)
Field Data
Ship-From: 10-200
Ship-To: f001
Release ID: 1
7 Verify all sequences picked cannot be edited.

Shipping 147
Exercise: Change Status to Offline

You receive notification from Namaka. Vehicle 1R004 is offline due to a bad paint-job. Please do
not ship the sunroof for sequence 004 until the vehicle is back online. Namaka will notify you at
that time.
Use Pre-Shipper/Shipper Workbench (7.9.2)
1 To edit the pre-shipper enter:
Field Data
Ship-From: 10-200
Pre-Shipper/Shipper: Pre-Shipper
Number: <pre-shipper #>
Ship-To /Dock: f001
2 Advance to the Shipper Workbench frame. Select part3. In the lower frame, reduce shipper
line quantity (Quantity) and quantity picked (Qty Picked) by 1 for part3.
3 The system advises you the quantity has changed, and asks if you want to recalculate the
weight and volume. Select Yes.
4 When the Display Sequences frame appears, remove the sequence for Customer Sequence
004.
5 Verify the Pre-Shipper and Sequence Pack List are correct by printing the Pre-Shipper.
6 Edit the sequence and mark it offline:
Field Data
Ship-From: 10-200
Ship-To: f001
Release ID: 001
7 Advance to the Sequence Detail Data frame and enter:

Field Data
Date: <next Monday>
Customer Sequence: 003
Item Number: part3
Customer Reference: 1R004
Status: offline
Exercise: Change Status and Shipping Date

You receive another notification from Namaka. All of the blue vehicles have bad paint-jobs. Don’t
send any blue sunroofs for Monday until Namaka notifies you.
1 Delete the pre-shipper by entering:
Field Data
Ship-From: 10-200
2 Advance to the Shipper Workbench. From the Actions menu, select Delete. An options frame
displays.
3 Select 1 - Delete Pre-Shipper/Shipper.
4 Edit the sequence and mark it offline by entering:
Field Data
Ship-From: 10-200
Ship-To: f001
Release ID: 1
5 Advance to the Sequence Detail Data frame and enter.

Field Data
Date: <next Monday>
Item Number: part3
Status: offline
6 Set the next sequence offline by entering:

Field Data
Status: offline
7 Create pre-shipper for the day:

Use Sequence Pre-Shipper - Automatic (7.5.4.10).
Field Data
To: <next Monday>
Ship-To: f001
To: f001
Status: 9000
Update: Yes

9 Verify the offline sequences are NOT included.
Write pre-shipper number here:______________________________________
Shipping 149
Exercise: Print Pre-Shipper

1 Print the pre-shipper and convert to shipper.
Use Pre-Shipper/Shipper Print (7.9.4), direct output to Page.
Field Data
To: <pre-shipper #>
2 Verify the shipper contains the range of sequences.

Write shipper number here:______________________________________
Confirm Shipper

OR
Generate
Run MRP
RSS
Create Pre- Confirm

Invoicing
Print Pre- Send

Print Sequence
Pack List
CSS-SH-200
Use Pre-Shipper/Shipper Confirm (7.9.5) to confirm the pre-shipper or shipper. During the
confirmation process, the system:
• Changes the pre-shipper to a shipper
• Decreases finished goods inventory
• Uses the requirement quantity to increase the cumulative shipped quantity
• Decreases the net requirement for the order line item
• Updates general ledger (GL) accounts
• Marks sequences as shipped
• Performs the first step in invoicing, creates the invoice
• Gives you the option of posting and printing the invoice
Shipping 151
Confirm Shipper
Shipping QCS
• Confirm Shipper
• Send Shipper
• Invoicing
CSS-SH-210
Pre-Shipper/Shipper Confirm (7.9.5)
Pre-Shipper/Shipper Confirm
Defaults to
system date
CSS-SH-220
Use Pre-Shipper/Shipper Confirm to:

• Record the shipments
• Convert pre-shipper to shipper
• System displays a message advising you it is converting the pre-shipper to shipper and
displays the shipper number
Requirement quantities are considered open until you confirm the shipper. Once a shipper is
confirmed:
• Pegged quantities are transferred to shipped quantities
• Shipped quantities are incremented by the ship line quantities
• Pegged quantities are decremented by the ship line quantities
Shipping 153
Pre Shipper/Shipper Confirm: Invoice Options
Pre-Shipper/Shipper Confirm: Invoice Options
CSS-SH-230
You use the fields in this frame to determine how the system processes the invoices generated by
the shipment.
Pre-Shipper/Shipper Confirm: Print Options
Pre-Shipper/Shipper Confirm: Print Options
CSS-SH-240
If you want to print the invoice, a frame displays asking for invoice printing information.
Note If printing a Brazilian Nota Fiscal, enter 11. The Invoice Number must contain a value.
Shipping 155
Exercise: Confirm the Shipper

Use Pre-Shipper/Shipper Confirm (7.9.5)
1 Confirm the shipper by entering:
Field Data
Ship-From: 10-200
Pre-Shipper/Shipper: Shipper
Number: <shipper #>
2 Advance to the next frame and enter the following:

Field Data
Post Invoice: Yes
3 Choose Yes at the system prompt asking if you want to print the invoice.
4 Verify the invoice contains the range of sequences.
Write invoice number here:______________________________________
Exercise: Change Status

It’s now later in the day and you receive the notification from Namaka that they corrected the cars
and you should send the blue sunroofs now.
1 Create pre-shipper for the day by entering:
Use Sequence Pre-Shipper - Automatic (7.5.4.10)
Field Data
To: <next Monday>
Ship-To: f001
To: f001
Status: offline
Update: Yes

3 Verify the offline sequences are included.
4 Delete the pre-shipper and build it again by entering:
Field Data
Ship-From: 10-200

Note If the output report from the Pre-Shipper/Shipper Print function fails to display check the
result with Pre-Shipper/Shipper Report 7.9.6.
Shipping 157
Send Shipper

OR
Generate
Run MRP
RSS
Create Pre- Confirm

Invoicing
Print Pre- Send

Print Sequence
Pack List
CSS-SH-260
QAD Enterprise Applications gives you two options to send the shipper to your customer:
• Print it and include with the shipment, like a packing list
• Electronically as an ASN when the shipment leaves your shipping area
Send Shipper
Shipping QCS
• Confirm Shipper
• Send Shipper
• Invoicing
CSS-SH-270
Shipping 159
Pre-Shipper/Shipper Print (7.9.4)
Pre-Shipper/Shipper Print
CSS-SH-280
Use Pre-Shipper/Shipper Print to create and print a shipper record.

• Prints separate packing list
• Can include sequence numbers
The system updates:

• The item quantity picked for this order
• Sequences on the shipper with the shipper number
Send ASN
Send ASN
Supplier Sends
an ASN at
Shipment
CSS-SH-290
An ASN is an electronic document derived from the shipper document and electronically sent (i.e.,
exported) by a supplier to a customer when a shipment leaves the supplier site. It informs the
customer that a shipment is on the way for purposes of in-transit advice and automated receiving.
The shipper number becomes the ASN number.
The ASN includes sequence information if the Send Sequences with ASN field is set to Yes in the:
• Sequence Schedule Control (7.5.4.24), or
• Customer Controls Maintenance (7.5.4.1), if used
The ASN is also called an 856 transaction set per the ANSI ASC X12 standard. The ASN takes the
place of an invoice in some supplier-customer arrangements. Export an ASN using EDI
eCommerce, Shipment ASN Export (35.4.1).
Note Whether or not an ASN is electronically transmitted using EDI to the customer depends on
the setting of the EDI ASN flag in Trading Partner Parameters Maintenance (35.13.10). If Yes,
then the ASN can be transmitted by EDI.
Shipping 161
Shipment ASN Export (35.4.1)
Shipment ASN Export
CSS-SH-310
In Shipment ASN Export, enter selection criteria to indicate which shipments should have ASNs
sent. The system uses these criteria to:
• Execute the appropriate gateway program
• Select the appropriate trading partner information
• Transform outbound QAD Enterprise Applications data to the format required by receiving
party’s EC subsystem
Sequence Shipper Report (7.5.4.11)
Sequence Shipper Report
CSS-SH-330
Use Sequence Shipper Report to print a report showing sequences contained within shippers.
• Allows you to see the shipper’s contents
Shipping 163
Invoicing

OR
Generate
Run MRP
RSS
Create Pre- Confirm

Invoicing
Print Pre- Send

Print Sequence
Pack List
CSS-SH-350
Confirming the shipper flags the order as ready for invoicing.

QAD Enterprise Applications gives you two options for sending the invoice your customer.
• Print an invoice and send the printed invoice to the customer
• Electronically transmit the invoice to the customer
Invoicing
Shipping QCS
• Confirm Shipper
• Send Shipper
• Invoicing
CSS-SH-360
Shipping 165
Invoicing Procedure
Invoicing Procedure
• Post Invoice
• Print Invoice
• Export Invoice
CSS-SH-370
The typical scenario for invoicing is:

• Post invoice
• Automatically at the time of confirmation
• Manually using Invoice Post and Print (7.13.4)
• Print invoice
• At the time of confirmation
• Manually, either during post or later using Invoice Print or Reprint (7.13.12)
• Send invoice
• Export
• Manually
Shipping QCS Summary
Shipping QCS Summary

• Confirm Shipper
• Send Shipper
• Invoicing
CSS-SH-380
Chapter 7
Features and Options

QCS Features and Options

In this section you learn how to use:
Applications
CSS-FE-010
In this chapter we are going to discuss different features and options available to you when using
QCS.
Features and Options 169
Multi-Item Sequences

• Multi-Item Sequences
• Multiple Delivery Locations
• Deleting Sequences
• Sequence Cross-Reference
• Cumulative Quantities
CSS-FE-020
QCS allows you to have multi-item sequences. Multi-item sequences simply means there is more
than one item (i.e., part) per sequence.
Using the above example for seat sets in a single vehicle:
• Two red front bucket
• Driver (D)
• Passenger (P)
• One red rear bench
Each item is a separate sequence scheduled order line item record.

• Three sequence scheduled order line item records
• Three different item numbers (driver red bucket, passenger red bucket, and red rear seat)
• One sequence number
Multiple Delivery Locations

CSS-FE-040

LF210
1 1
Seq Qty Item VIN Line Feed 2 2
3 3
1 1 (D) red bucket seat ABC123 LF210
1 1 (P) red bucket seat ABC123 LF210 4 4
1 1 red rear seat ABC123 LF211
5 5
2 1 (D) green bucket seat DEF435 LF210
2 1 (P) green bucket seat DEF435 LF210
2 1 green rear seat DEF435 LF211
30 30
3 1 blue bench seat XYZ789 LF210
3 1 blue rear seat XYZ789 LF211
4 1 green bench seat AEG434 LF210 LF211
4 1 green rear seat AEG434 LF211 1
5 1 (D) blue bucket seat JWZ551 LF210
5 1 (P) blue bucket seat JWZ551 LF210 2
5 1 blue rear seat JWZ551 LF211
3
...
30 1 (D) blue bucket seat UIV331 LF210 4
30 1 (P) blue bucket seat UIV331 LF210
5
30 1 blue rear seat UIV331 LF211
30
CSS-FE-050
For each item, there can be multiple delivery locations. These are customer defined and are
specified on the sequence schedule release as one of the following:
• Customer dock
• Line feed
It is important to understand the customer dock specified on the sequence schedule release is not
the same as a customer dock (i.e., dock address) specified on the scheduled order in Customer
Scheduled Order Maintenance (7.3.13). The dock address specified on the scheduled order is set
up in Dock Maintenance (7.3.6). Then on the pre-shipper/shipper, that dock address is used as the
ship-to address. The entire scheduled order is shipped to that dock address.
QCS allows the customer to specify a dock (or a line feed location) for each part (item). In QCS
the purpose of specifying a customer dock (or a line feed location) is to allow a sequence to be
delivered to more than one delivery location at the same customer ship-to address. A customer
dock (or a line feed location) is used to direct the items once they arrive at the customer site.
Note A customer would not use a dock address (set up in Dock Maintenance) and a dock location
(specified in the sequence schedule release) at the same time.
When a dock or line feed location is designated in QCS, it tells QAD Enterprise Applications two
things:
• The sequence is made up of multiple items
• The sequence items are going to different delivery locations
• Items being shipped should not be packed together because they are going to different
delivery locations at the customer site (ship-to)
• Shipper needs to be created for each delivery location, even if the ship-to address is the
same for each delivery location
Note In QCS these delivery locations (i.e., dock and line feed) are strictly customer internal
locations. QAD Enterprise Applications does not validate them.
Using the above graphic as an example, there are three items in the same sequence being shipped.
System detects that the sequence contains two different line feed locations. It puts each sequence
item on a shipper specific for the designated line feed.
• Driver red bucket seat and the passenger red bucket seat are to be delivered to line feed 210
• Grouped on the same shipper
• Red rear seat is to be delivered to line feed 211
• Separate shipper
Deleting Sequences

CSS-FE-060
QAD Enterprise Applications gives you two options for deleting sequences:
• Logical delete
• Use Sequence Schedule Maintenance (7.5.4.5)
• Does not physically remove (i.e., delete) the record from the database
• Physical delete
• Use Sequence Schedule Detail Delete (7.5.4.22)
• Selected sequence records are physically removed from the database
You also have the option of deleting/archiving inactive sequence schedules.

• Use Schedule Delete/Archive (7.9.23)
CSS-FE-070
Use Sequence Schedule Maintenance to do a logical delete by setting the Delete flag to Yes.
• Marks the sequence record as deleted
• Sequence record is inactive for this schedule release
• Sequence record is not removed/deleted from the database
You can mark for deletion any sequence record that is not picked or that is cross-referenced to a
picked sequence on another sequence release.
• Once marked as deleted, the sequence record is frozen and is not included in normal
processing
• Cannot be modified
• Not copied to next release
• Not included in planning or shipping
• Allows an audit of system
• Allows you to keep information in sync with your customer
Sequence Schedule Detail Delete (7.5.4.22)
Sequence Schedule Detail Delete
CSS-FE-080
Use Sequence Schedule Detail Delete to specify which sequence records are to be deleted.
• Selected sequence records are permanently removed from the database
• System allows you to delete any sequence record that is not picked or that is cross-referenced
to a picked sequence record on another schedule release
Schedule Delete/Archive (7.5.23)
Schedule Delete/Archive
Determines if
Sequences are
Included
CSS-FE-090
Use Schedule Delete/Archive to delete or archive all inactive sequence schedules with one
transaction.
All associated inactive detail and cross-reference sequence records are deleted or archived.
Sequence Cross References\

CSS-FE-100
You use sequence cross references to handle duplicate sequence requirements.

• Same sequence is on separate schedule releases
For example:
Day 1
• Supplier receives sequence requirement from customer
• Supplier ships sequence on day 1
• Shipment does not reach the customer on day 1
Day 2
• Customer sends new sequence schedule release to supplier
• Contains sequence requirement from day 1
• Supplier shows the sequence requirement as already fulfilled
CSS-FE-110
In Sequence Schedule Maintenance when you are adding a new sequence schedule release for an
existing ship-from/ship-to combination, the system gives you the option of copying data from the
active schedule release.
• If you say Yes, the system then checks to see if there are any sequences on the active schedule
release which have been flagged as picked. If there are, you are given the option of creating
cross-references between the sequences on the new sequence schedule release and the active
sequence schedule release
• If you say No, then the system copies all sequences from the active sequence schedule release
to the new sequence schedule release
• System resets any sequence records that were previously marked as picked or cross-
referenced
• Resetting these sequence records makes them open requirements
Sequence Cross-Ref Maintenance (7.5.4.13)
Sequence Cross-Ref Maintenance
CSS-FE-120
Use Sequence Cross-Ref Maintenance to manually create individual sequence cross-references

and to maintain information on sequence cross-references.
Cross-referenced sequences can be:
• Marked as deleted
• Already cross-referenced
• Maintain information on sequence cross-references
There are three frames:

• Header Frame
• Picked/Shipped Sequence
• Linked Sequence
Header Frame
In the header frame you identify the ship-from ship-to combination on the existing sequence
schedule release.
Picked/Shipped Sequence Frame
The Picked/Shipped Sequence frame shows information on picked/shipped sequences. You can
use this frame to select a previously picked or shipped sequence for the specified ship-from/ship-to
combination.
Linked Sequence Frame
Sequence Cross-Ref Maintenance: Linked

Sequence Frame
CSS-FE-130
The Linked Sequence frame shows information on the linked or related sequence in the new
sequence schedule release.
• System creates a cross-reference link between the picked/shipped sequence and this sequence
• The new cross-referenced sequenced (i.e., linked sequence) cannot be picked
• System considers this sequence to be a closed requirement
Sequence Cross-Ref Report
Sequence Cross-Ref Report
CSS-FE-140
Use Sequence Cross-Ref Report to generate a report showing information on the shipped
sequences and linked sequences. Shows cross-references created:
• Manually
• Automatically when sequences are imported using:
• eCommerce
• Shipper Gateway
The image above shows a sample Sequence Cross-Ref Report.

Sequence Cross-Ref Report: Sample Report
Sequence Cross-Ref Report: Sample Report
rcsqsxrp.p 7.5.4.14 Sequence Cross-Ref Report Date: 02/01/00

Ship-From: 10000 nj plant
Ship-To: 866-1 Customer
Shipped Sequence Linked Sequence

---------------- ---------------
Shipped Release ID: 1 Release ID: 2
Shipped Job: job1 Customer Job: job1
Shipped Sequence: seq1 Customer Sequence: seq1
Shipped Item Number: 866-item1 Item Number: 866-item1
Scheduled Date: 12/07/99 Date: 12/07/99
Scheduled Time: 08:00 Time: 09:00
Shipped Reference: vin100 Customer Reference: vin400
Shipped Dock: dock1 Customer Dock: dock1
Shipped Line Feed: line1 Line Feed: line1
Picked: yes
Shipped: yes
Shipper ID: shp99070
CSS-FE-150
The image above shows a sample Sequence Cross-Ref Report.

Cumulative Quantities

CSS-FE-160
Cumulative (cum) sequence schedules are rare.

• Currently found in one Ford plant
• Items are cumulative based
• Quantities are based on the cumulative amount shipped
• Discrete quantities are calculated
Cumulative Quantities
Cum Quantity Cum Quantity

Indicator
CSS-FE-170
When you set the Cumulative flag in Sequence Schedule Maintenance to Yes, it flags the sequence
schedule as cumulative. The cumulative quantity for the sequence schedule is shown in the
Sequence Detail Data frame, the Cum Quantity field.
Appendix A
Manually Create Sequence

Scheduler
Manually Create Sequence Schedule
SUV Assembly Plant
1 Use Sequence Schedule Maintenance (7.5.4.5) to create a sequence schedule:

Field Data
Ship-From: 10-200
Ship-To: f001
Release ID: 001
2 Advance to the next frame and enter:

Field Data
Cumulative: No
Schedule Date Type: Ship
3 Advance to the Sequence Detail Data frame and enter:

Field Data
Date: <next Monday>
Customer Job: <Julian Date for next Monday Ex. 20080305
Item Number: part1
Customer Ref: 1R001
Quantity: 1
Status: 9000
Note Use Status 9000 for all sequences.
Note Remember to clear the Order and Line fields with each entry. They will fill in automatically.
Date Time Job Seq Order Line Part PO Ref Qty
Next Monday <Julian Date> (Ex: 20080306) 002 part2 1R008 1
“ “ 003 part1 1R011 1
“ “ 004 part3 1R013 1
“ “ 005 part4 1R014 1
“ “ 006 part1 1R015 1
“ “ 007 part4 1R016 1
“ “ 008 part3 1R017 1
“ “ 009 part4 1R018 1
“ “ 010 part2 1R019 1
“ “ 011 part3 1R020 1
“ “ 012 part2 1R021 1
Tuesday <Julian Date> (Ex:20080307) 001 part1 1R022 1
“ “ 002 part2 1R023 1
“ “ 003 part3 1R024 1
Manually Create Sequence Scheduler 187
Date Time Job Seq Order Line Part PO Ref Qty

“ “ 004 part1 1R025 1
“ “ 005 part4 1R026 1
“ “ 006 part2 1R027 1
“ “ 007 part3 1R028 1
“ “ 008 part4 1R029 1
Wednesday <Jullian Date (Ex: 20080308) 001 part2 1R030 1
“ “ 002 part3 1R031 1
“ “ 003 part2 1R032 1
“ “ 004 part4 1R033 1
“ “ 005 part3 1R034 1
“ “ 006 part4 1R035 1
“ “ 007 part1 1R036 1
“ “ 008 part4 1R037 1
“ “ 009 part3 1R038 1
“ “ 010 part1 1R039 1
“ “ 011 part2 1R040 1
“ “ 012 part1 1R041 1
Print Sequence Schedule Report

1 Use Sequence Schedule Report (7.5.4.7) to generate the Sequence Schedule Report. Enter the
following:
Field Data
Ship-To: f001
To: f001
Sub-Totals: Yes
2 Verify all sequences are displayed and the sub-totals are correct for each day.
Appendix B
Set Up Sequence Numbers

Set Up Sequence Numbers

1 To set up the first sequence number code enter:
Field Data
Sequence ID: Ship
Target Dataset: abs_id.shipper
Internal: Yes
Use Number Range Management (36.2.21.1)

2 Advance to the Segment List frame. You are going to define the format and parameters for the
first segment number by entering:
Field Data
Nbr: 1
Type: Fixed
New Segment Number: 1
Fixed Value: SH
3 Add a second segment number by entering:

Field Data
Nbr: 2
Type: Int
Minimum Value: 0
Maximum Value: 999999
Initial Value: 1
Reset Value: 0
4 Add a new sequence number code by entering:

Field Data
Sequence ID: pre-ship
Target Dataset: abs_id_preship
Internal: Yes
5 Advance to the Segment List frame and enter:

Field Data
Nbr: 1
Type: Fixed
Fixed Value: PRE

Field Data
Nbr: 2
Type: Int
Set Up Sequence Numbers 191
Field Data
Minimum Value: 0
Initial Value: 1
Reset Value: 0
7 Add a new sequence number code by entering:

Field Data
Sequence ID: mbol
Target Dataset: abs_id_mbol
Internal: Yes
8 Advance to the Segment List frame and enter:

Field Data
Nbr: 1
Type: Fixed
Fixed Value: MB

Field Data
Nbr: 2
Type: Int
Minimum Value: 0
Initial Value: 1
Reset Value: 0
10 Update Container/Shipper Control to use the new sequence number codes.

Field Data
Pre-Shipper Sequence ID: preship
Shipper Sequence ID: ship
Master Bill Sequence ID: mbol
Use Container/Shipper Control (7.9.24)

Appendix C
Design and Architecture

Design Considerations

• Design Considerations
- Scheduled Order - Data View
- Current Architecture
- New Schedule Type
- Design Alternatives
- Design Requirements
- Selected Architecture
- E-R (Entity-Relationships) Diagram
- Schema Diagram
• Programming Considerations
CSS-DE-010
Design and Architecture 195
Scheduled Order - Data View
Scheduled Order - Data View
Customer Schedules
Data View
for Processing & Reporting
Customer
Line(s) Schedule
Data View
Sales ...
Order
Schedule(s)
Date, Time, Qty

Sequence
Schedule
Data View
CSS-DE-020
Current Architecture
Customer Schedules
Planning Shipping Req. Ship
Line(s)
Sales
Order Planning Shipping Req. Ship
Schedule(s)
Active Schedule
Date/Time,
Ref, Qty
Requirement
Pegging
(CSN)
CSS-DE-030
New Schedule Type
New Schedule Type

• Design Alternatives
- Type 7
- Type 4
• Design Requirements
- Physical Requirements
• New Fields
• New Indexes
CSS-DE-040
Existing schedule types:

• Customer Planning – Type 1
• Customer Shipper – Type 2
• Customer Required Ship – Type 3
• Supplier Schedule – Type 4
• Supplier Planning – Type 5
• Supplier Shipping – Type 6
Design Alternative
New Type 7
• Creates gap between schedule types
New Type 4
• Move supplier schedules to 5, 6, and 7
• Large invasive code change
New Data Structure

Design Requirements
Physical requirements:
• New fields
• Job
• Sequence
• Dock
• Line Feed
• New indexes
• By date/sequence for maintenance
• By date/item for planning (required ship schedule [RSS])
• By date/destination/sequence for shipping
Selected Architecture
Selected Architecture
Customer Schedules
with Sequence Schedule
as New Planning Shipping Req. Ship
Table
Line(s)
Sales Planning Shipping Req. Ship
Order
Schedule(s)
Active Schedule
Sequence Requirement
Schedule(s) Date/Time, Pegging
Ref, Qty (CSN)
Date, Seq, Part, Qty, etc.
CSS-DE-050
E-R Diagram
E-R Diagram New Entity-Relationships

cm_mstr
Customer
Customer
qad_wkfl rcf_ctrl
Customer
Customer/Ship-to Sequence
(extension of cm_mstr) Schedule
so_mstr Control File
Sales Order
Customer
rcs_mstr
Order
Sequence rcsx_ref
Schedule
sod_det Master Sequence
Order/Line X-Reference
Sales Order Lines
Sequences
Release ID /
Sequence
rcsd_det abss_det
Schedules
[ 1, 2, 3 ] Sequence Sequences Shipment
Schedule Sequence
Detail Detail
sch_mstr
Shipper
Scheduled Order
Order/Line/Qty
Authorization sbid_det
Self-Bill
Date/Time/Qty Detail
schd_det abs_mstr Shipper

Scheduled Order Picklist -
Detail Pre-Shippers - Shipper ih_hist
Shippers
Invoice History
Requirements
rqm_det absr_det
Shipper
Requirement Shipment
Detail Requirement
Date/Time/Qty Detail
CSS-DE-060
Schema Diagram
Customer Sequenced Schedules
Schema Diagram
System Architect
Fri Jan 21, 2000 15:42
cm_mstr rcc_mstr rcs_mstr

Customer Customer
Customer Sequence Sequence

rcc_addr = rcs_shipto
cm_addr = rcc_addr Customer Master Schedule Master
Linked Sequences
rcsd_shipfrom = rcsx_shipfrom Sequences
rcsd_shipto = rcsx_shipto
rcs_shipfrom = rcsd_shipfrom
rcsd_rlse_id = rcsx_rlse_id
rcs_shipto = rcsdshipti
rcsd_cust_job = rcsx_cust_job
Sales order/line rcs_rlse_id = rcsd_rlse-id
rcsd_cust_seq = rcsx_cust_seq
cm_addr = so_nbr rcsd_part = rcsx_part
rcsd_date = rcsx_date
rcsd_time = rcsx_time
rcsd_cust_ref = csx_cust_ref
rcsx_ref rcsd_dock = rcsx_dock rcsd_det
rcsd_line_feed = rcsx_line_feed
Sequence Cross- Sequence Detail

Reference Shipped Sequences Schedule
rcsd_shipfrom = rcsx_shipped_shipfrom
rcsd_shipto = rcsx_shipped_shipto
rcsd_rlse_id = rcsx_shipped_rlse_id
rcsd_cust_job = rcsx_shipped_cust_job
rcsd_cust_seq = rcsx_shipped_cust_seq Delivery Schedule Order/Line
rcsd_part = rcsx_shi pped_part sod_nbr = rcsd_order
rcsd_date = rcsx_shipped_date sod_line = rcsd_line
rcsd_time = rcsx_shipped_time
rcsd_cust_ref = rcsx_shipped_cust_ref Sequences Shipped
rcsd_dock = rcsx_shipped_dock rcsd_shipfrom = abss_shipfrom
rcsd_line_feed = rcsx_shipped_line_feed rcsd_shipto = abss_shipto
rcsd_rlse_id = abss_rlse_id
rcsd_cust_job = abss_cust_job
so_mstr
rcsd_cust_seq = abss_cust_seq
Sales Order/Line rcsd_part = abss_part
sod_det
Sales Order so_nbr = sod_nbr rcsd_date = abss_date
rcsd_time = abss_time
Sales Order Lines rcsd_cust_ref = abss_cust_ref
Shipper rcsd_dock = abss_dock
abs_order = sod_nbr rcsd_line_feed = abss_line_feed
abs_line = sod_line
abs_mstr abss_det
Shipper
Picklist - Pre- abs_id = abss_abs_id Shipment
Shippers - Shippers abs_shipfrom = abss_shipfrom Sequence Detail
CSS-DE-070
Programming Considerations

• Design Considerations
• Programming Considerations
- Required Ship Schedule Update
- Picklist/Pre-Shipper - Automatic
- ECommerce
CSS-DE-080
• Required Ship Schedule Update (7.5.5)

• Picklist/Pre-Shipper - Automatic (7.9.1)
• eCommerce

Netting Logic
• Keep existing 1–4 options
New Workfile Created

• Contains sequence schedule requirements
RSS Begins with Sequence Schedule

• Replace logic
• Consume logic – updates running CUM (cumulative)
SDT (Ship/Delivery Time) Code vs. Weekly Interval Problem

• With SDT weekly requirements distributed
• For example, 20 – (1/4 Monday through Friday)
• Without SDT weekly requirements dropped
• Ship Schedule
• 1,000 for Monday

• 1,500 for Tuesday
• Plan Schedule
• 10,000 for week
• RSS
• 1,000 for Monday
• 1,500 for Tuesday
• Now RSS
• 7,500 for Wednesday

• Netting Logic
• New Workfile Created
• RSS Begins with Sequence Schedule
• SDT Code vs Weekly Interval Problem
CSS-DE-090
Netting Logic
• Keep existing 1–4 options
New Workfile Created

• Contains sequence schedule requirements
RSS Begins with Sequence Schedule

• Replace logic
• Consume logic – updates running CUM (cumulative)
SDT (Ship/Delivery Time) Code vs. Weekly Interval Problem

• With SDT weekly requirements distributed
• For example, 20 – (1/4 Monday through Friday)
• Without SDT weekly requirements dropped
• Ship Schedule 1,000 for Monday1,500 for Tuesday
• Plan Schedule 10,000 for week
• RSS 1,000 for Monday 1,500 for Tuesday
• Now RSS 7,500 for Wednesday
Picklist/Pre-Shipper- Automatic
Picklist/Pre-Shipper - Automatic
• Handles Sequenced and Non-Sequenced
Items
• Reads Sequence Schedule
• Recalculates Pre-Shipper Quantity
CSS-DE-100
Handles sequenced and non-sequenced items:

• One transaction to create pre-shippers
• Segregates sequenced and non-sequenced items into separate pre-shippers by Ship-To
• Eliminates cloning of code
• Needs selection criteria for sequences
Reads sequence schedule:

• Open quantity
• RSS contains gross quantities
• Sequence schedule contains detail
Recalculates pre-shipper quantity:

• Existing calculation:
• Total item quantity
• New sequence calculation:
• Order material
• Summarize item quantity
eCommerce
eCommerce
• Transformation Files Example
• Gateway is Part of PRO/PLUS
CSS-DE-110

CustomerSequenceSchedules TG v2012EE PDF

Uploaded by

Copyright:

Available Formats

CustomerSequenceSchedules TG v2012EE PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CustomerSequenceSchedules TG v2012EE PDF

Uploaded by

Copyright:

Available Formats

QAD Enterprise Applications

Copyright © 2012 by QAD Inc.

About This Course . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Chapter 1 Introduction to QCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Chapter 2 Business Considerations . . . . . . . . . . . . . . . . . . . . . . . . .17

Chapter 3 Customer Sequence Schedules Setup . . . . . . . . . . . . . .31

Customer Scheduled Order Maintenance (7.3.13) . . . . . . . . . . . . . . . . . 71

Chapter 4 Loading Sequence Schedule Release. . . . . . . . . . . . . . .79

Chapter 5 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

MRP - Calculating Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Chapter 6 Shipping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Shipping QCS Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Chapter 7 Features and Options . . . . . . . . . . . . . . . . . . . . . . . . . . .167

Course Credit and Scheduling

Virtual Environment Information

QAD Web Resources

Introduction to Customer Sequence Schedules

What Sequence Schedules Do

Customer Sequence Schedules

Sequence Schedule Documents and Variances

What Customer Sequence Schedules Do

Where Are You?

Where Are You?

Receive incoming customer sequence schedules using EDI eCommerce.

QCS Work Flow

Seq Qty Item VIN Line Feed

1 1 Dashboard, Red ABC123 LF210

2 1 Dashboard, Green DEF435 LF210

3 1 Dashboard, Blue XYZ789 LF210

4 1 Dashboard, Green AEG434 LF210

5 1 Dashboard, Blue JWZ551 LF210

6 1 Dashboard, Red ABC124 LF210

1 1 Dashboard, Red ABC123 LF210

2 1 Dashboard, Grn DEF435 LF210

3 1 Dashboard, Blue XYZ789 LF210

4 1 Dashboard, Grn AEG434 LF210

5 1 Dashboard, Blue JWZ551 LF210

6 1 Dashboard, Red ABC124 LF210

Identifies the customer’s end item

Identifies location within customer’s site for material to be delivered.

Indicates how the material is to be packed according to the customer’s preference.

Sequence Pack List

New document that accompanies pre-shipper (total quantity)

QCS Life Cycle

QCS Life Cycle

Schedule Processing Menu (7.5)

Schedule Processing Menu

Access to the QCS functions.

Use the Sequence Schedules menu to access the QCS functions.

EDI Business Value and Features

EDI Business Value and Features

Scheduled and Sequence Scheduled Order Precedence

Scheduled and Sequence Scheduled Order

For scheduled orders without sequence schedules:

Note Discussed in the following Training Guide: Customer Schedules.

Sequence Scheduled Orders

• Option 2 – uses sequence and planning schedule

Sequenced Scheduled Orders

Sequenced Scheduled Orders