Aps Ig R9 1 022013

Infor XA – Advanced Planning and
Scheduling Integration Guide

Copyright © 2013 Infor
Important Notices
The material contained in this publication (including any supplementary information) constitutes and
contains confidential and proprietary information of Infor.
By gaining access to the attached, you acknowledge and agree that the material (including any
modification, translation or adaptation of the material) and all copyright, trade secrets and all other
right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or
interest in the material (including any modification, translation or adaptation of the material) by virtue
of your review thereof other than the non-exclusive right to use the material solely in connection with
and the furtherance of your license and use of software made available to your company from Infor
pursuant to a separate agreement, the terms of which separate agreement shall govern your use of
this material and all supplemental related materials ("Purpose").
In addition, by accessing the enclosed material, you acknowledge and agree that you are required to
maintain such material in strict confidence and that your use of such material is limited to the
Purpose described above. Although Infor has taken due care to ensure that the material included in
this publication is accurate and complete, Infor cannot warrant that the information contained in this
publication is complete, does not contain typographical or other errors, or will meet your specific
requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or
otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or
omissions in this publication (including any supplementary information), whether such errors or
omissions result from negligence, accident or any other cause.
Without limitation, U.S. export control laws and other applicable export and import laws govern your
use of this material and you will neither export or re-export, directly or indirectly, this material nor any
related materials or supplemental information in violation of such laws, or use such materials for any
purpose prohibited by such laws.
Trademark Acknowledgements
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor
and/or related affiliates and subsidiaries. All rights reserved. All other company, product, trade or
service names referenced may be registered trademarks or trademarks of their respective owners.
Publication Information
Release: Infor XA 9.1
Publication date: February 26, 2013
Page iii
To the reader
To the reader
This book contains the information you need to use APS Integration in conjunction with Release 6.1 of the Infor
Supply Chain Management (SCM) application, formerly known as Thru-Put Manfuacturing. SCM is
a stand-alone application to be installed on an NT server. The APS Integration provides a conduit for
transporting information to and from SCM, while SCM provides the engine and tools for developing
concurrent material and capacity plans. You will need to read the Supply Chain Management
Concepts Guide and Supply Chain Management User’s Guide to understand that application.
For a complete list of the books in the XA library, see the bibliography on the
documentation CD.
Before you begin

Complete the following training if you do not have equivalent knowledge:
• Education on how to use Windows NT and a Windows application
• System i education for the basic operating concepts of the IBM System i.
• Education classes for SCM.
What this book contains

This book guides you in using APS Integration with SCM Release 6.1.
Page iv
Summary of changes
Summary of changes
The book has been reformatted from the APS Bridge User’s Guide to match the new design of APS
Integration.
Page v
Contents
Contents
To the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i-iii

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i-iii
What this book contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i-iii
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i-iv
Chapter 1. Introducing APS Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What Supply Chain Management (SCM) does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What APS Integration does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Information Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Information used in SCM planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
The planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Implementing the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Capable To Promise (CTP) for Customer Orders . . . . . . . . . . . . . . . . . . . . . . . 1-4
Chapter 2. Installing SCM 6.1 and APS Integration . . . . . . . . . . . . . . . . . . . . . 2-1
Installing APS Integration on the System i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installing SCM 6.1 on the PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Creating an ODBC data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Integration Control – iSeriesIntegration.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Connecting SCM and Infor ERP XA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
CTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Enabling Capable To Promise (CTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Chapter 3. Managing APS Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Information used In SCM planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Production facility information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Item/product information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Demand and forecast consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Supply information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
MRP planning parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
The planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Activating APS Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Downloading to SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Planning and scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Uploading to ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Implementing the plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Customer order scheduling and CTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Handling purchased items in CTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
CTP for KBC items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Order board matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Updating customer orders from SCM planning . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Appendix A. Data downloaded to SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
Item (PPIPRT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2
Item Process (PPIPRC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-4
Bill of Material (PPIBOM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-5
Routing (PPIRTG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-6
Workcenter (PPIWKC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-8
Setup Sequence (PPISEQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-9
Forecast (PPIFCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10
Page vi
Contents
Sales (PPICOM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-11

Inventory (PPIINV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-13
Workorder Heading (PPIMOM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-14
Workorder Allocation (PPIMOD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-15
Workorder Routing (PPIMOR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16
Jobs in Progress (PPIJIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-18
Purchase (PPIPUR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-20
Warehouse Control (PPIPLN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-21
Appendix B. Data uploaded to ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
MRP Requirements (REQMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
MRP Planned orders (PLNORD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
MRP Demand reference (DMDREF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
MRP Reschedule activity work (RACWRK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2
Customer order update (PPCOWK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2
COM customer order line item release (MBADREP) . . . . . . . . . . . . . . . . . . . . . . . .B-3
User customer order (OLCSBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3
Manufacturing Order/REP Schedule Master (MOMAST) . . . . . . . . . . . . . . . . . . . .B-4
Manufacturing Order Routing (MOROUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4
Manufacturing Order Component (MODATA) . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5
Appendix C. Download error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Appendix D. Additional SCM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
User Customer Orders and Forecasts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
User Customer Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
User Forecasts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Processing maintenance transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
User-controlled files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
Item (PPITEM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
Routing operation (PPROUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6
Setup sequence (PPSEQS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6
Appendix E. If APS Bridge is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-1
Differences between APS Bridge and APS Integration . . . . . . . . . . . . . . . . . . . . . .E-1
User Interface Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-2
Actions you must take . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-3
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GL-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-1
Page 1-1
Introducing APS Integration
Chapter 1. Introducing APS Integration

What Supply Chain Management (SCM) does......................................................... 1-1
What APS Integration does ...................................................................................... 1-1
Information Flow ....................................................................................................... 1-2
Information used in SCM planning ........................................................................... 1-2
The planning process ............................................................................................... 1-4
Implementing the Plan.............................................................................................. 1-4
Capable To Promise (CTP) for Customer Orders ..................................................... 1-4
What Supply Chain Management (SCM) does

Supply Chain Management (SCM), formerly known as Thru-Put
Manufacturing (TPM), is an advanced planning and scheduling application that plans
capacity and material concurrently, based on the Theory of Constraints. The SCM
application, called the SCM Synchronization Engine, or SCM Synch Engine,
or SCM Engine, for short, resides on a PC and provides the tools to analyze
constraints and develop plans in recognition of those constraints. The general
processing steps within the SCM application are:
• Identify constraints for work center and materials
• Exploit these constraints using the Drum, Buffer, Rope technique
• Subordinate the system to these constraints
• Elevate constraints for priority processing
• Concurrently generate a production plan, material plan, and detailed schedules
• Use analysis tools to analyze plans in terms of quantities and monetary units
• Regenerate the plan
• Save the plan for further processing.
What APS Integration does

APS Integration provides a seamless connection between the planning and
scheduling in the SCM Synchronization Engine and the XA applications.
On the System i, APS Integration works primarily through the MRP application, and it
interfaces to all the applications that MRP does, except for MPSP and Cameleon.
The SCM Synchronization Engine functions replace the MRP planning run and the
PCC scheduler.
APS Integration includes the MRP application at no additional charge, and both
applications must be installed on the System i using the normal XA Cross
Application Support (CAS) process. XA CAS, IM, and either PDM or EPDM are
required. Either PCC or REP can provide the interface to the shop floor for plan
execution. And COM/CSM, EC, FCST, ISL/MISL, KBC, OBPM, and PUR/PM are all
supported as they interface to MRP.
APS Integration provides three basic connections between SCM and XA:
• The ERP information required for planning and scheduling is provided to SCM.
• The SCM planning and scheduling results are provided to ERP for
implementation.
• In COM customer order entry, a capacity and material tested delivery date is
provided by SCM (using the Capable To Promise [CTP] function) for reliable order
promising to customers.
Page 1-2
Information Flow
We will discuss the planning cycle in these three phases:
1. Preparation for Planning: Most information used in planning is maintained in XA
Production facility information, product definition and item
planning parameters, forecasted and/or actual demand, and current inventory
balances and supply orders are all managed on the System i. Planning calendars
and most planning control parameters are maintained on the SCM PC.
APS Integration allows you to define and maintain on the System i some data used
in SCM not currently maintained in other ERP for System i applications. It allows
you to maintain forecasts and customer orders from a source outside ERP for System i,
for use in SCM planning. And it allows you to maintain APS Integration
control parameters on the SCM PC.
2. Planning: Information from the System i is downloaded to the SCM database, and
the plan is generated. The plan includes changes to the scheduled delivery of
customer orders, planned production and purchase orders for release, exceptions
for action for open orders, and operation schedules for all planned and open
production orders. The plan is uploaded to theSystem i, and the ERP database is
updated based on the APS Integration control parameters. In all cases, the plan
is loaded into the MRP planning files, so that you can use all the ERP for System i
functions that work with the MRP plan.
APS Integration manages the download and upload of information, and the
processing done on the System i after planning, based on the settings of the
integration control parameters.
3. Implementing the Plan: As the SCM plan is in the MRP files, you can use all the
functions on the MRP Order/Schedule Release and Review menu to implement
the plan. You can also use Order Based Production Management (OBPM),
specifically the MRP Recommendations object.
APS Integration uses the SCM operation schedules for planned manufacturing orders
to schedule operations as manufacturing orders are released in MRP or OBPM.
Customer order delivery dates are determined in SCM planning, typically done daily,
and in most cases overnight. But if you have to quote a realistic delivery date before
your customer will place an order, you can use the Capable To Promise (CTP)
function in COM order entry to get an achievable date from SCM based on the current
plan, and the required capacity and materials. If the SCM promised date is accepted,
an order is reserved in SCM, to ensure accurate responses to future CTP requests.
APS Integration manages the connection between COM and SCM, to make the CTP
request of SCM, return the date to COM, and to reserve the order in SCM.
Information used in SCM planning

Information provided from Infor ERP XA
This section summarizes the XA information used in SCM planning, and

identifies the System i application that maintains or provides the information. Chapter 3
describes the key differences between MRP, Advanced Planner (AVP), and SCM.
Appendix A describes in detail the data downloaded to SCM. Appendix D describes
the information you maintain in APS Integration.
Page 1-3
Production facility information

Facilities and capacities from PDM/PDM+ or EPDM
Item/product information
Item warehouse/balance/plan data from IM/MM, PDM+ or EPDM
Additional item warehouse data for SCM from APS Integration (See Appendix D)
Item master/item revision data from PDM/PDM+ or EPDM and KBC
Bill of material and routing data from PDM/PDM+ or EPDM, KBC and REP
Additional routing operation and setup sequence data for SCM from APS
Integration (See Appendix D)
Forecast demand
Forecasts from FCST
Forecasts from MRP either propagated or entered manually
User forecasts entered via user program directly into the MRP REQMTS file
User forecasts entered in APS Integration (See Appendix D)
Planned and released intersite orders from ISL/MISL
Requirements from MRP, either propagated or entered manually
Customer sales demand
Customer orders from COM, CSM, COM_Net, EC, etc.
Expected customer orders from EC,
User customer orders entered via user program directly into the MRP REQMTS
file
User customer orders entered in APS Integration (See Appendix D)
Planned and released intersite orders from ISL/MISL
Requirements from MRP either propagated or entered manually
Supply information
On hand item balance from IM/MM,
Open production orders and component and operation status from IM, PCC/
OBPM, REP, and APS Integration
Open purchase orders from PUR/PM and ISL/MISL
MRP planning parameters
Warehouse-level control parameters from MRP
Information provided on the SCM PC
The following information used in planning is maintained on the SCM PC:

SCM planning control parameters
Config.ini: This file contains options available to all users of the SCM
synch engine. See the SCM documentation for further
information on this file.
iSeriesIntegration.ini: This file contains the options available to ERP for
iSeries (System i), for connecting the systems, downloading, uploading,
and capable to promise. Chapter 3 explains these options,
and how to maintain them.
SCM calendars SCM plans using calendars on the PC, and you must maintain those
calendars there. See the SCM documentation for further information.
Page 1-4
The planning process

You run SCM planning from the SCM PC. Planning consists of these three parts that
can all be run in one scheduled job:
Downloading to SCM The SCM PC connects to the System i, runs an APS Integration
job to build the ERP data used in planning, and SCM DBUtil downloads
the data to the SCM database.
Planning and scheduling The SCM synch engine loads the database into memory,
consumes forecast with customer orders, and develops the supply plan
and detailed schedule to address the net demand, and writes the
schedule to the database.
Uploading to ERP The SCM PC connects to the System i, uploads the planning results
to theSystem i, and runs an APS Integration job to load the MRP planning
files from the planning results, and update the System i database as
specified in the iSeriesIntegration.ini file. Options include updating the
scheduled delivery dates of customer orders, and operation schedules for
open manufacturing orders, and automatically creating manufacturing
orders, purchase orders, and intersite orders identified for release.
The following System i information is updated from planning:
MRP planning files

Requirements, demand reference, reschedule activity, planned order, and order
review, with the planning results
Customer orders (COM and user)
Promised date and manufacturing due date
Manufacturing order master and operation records
Priority and scheduled dates, per the plan
Implementing the Plan

You implement the plan on the System i, using MRP and all the applications that
interface to it. You can use the functions on the MRP Order/Schedule Release and
Review menu. You can also use the MRP Recommendations object in Order Based
Production Management (OBPM) to review and act on the plan, including its
interactive component availability checking.
As you release new manufacturing orders in MRP or OBPM, the SCM operation
schedules for planned manufacturing orders are used to schedule the operations.
Capable To Promise (CTP) for Customer Orders

Just as you can use Available To Promise (ATP) in COM order entry if you run MRP
and optionally MPSP, you can use the more powerful Capable To Promise (CTP) if
you run SCM, to give a realistic, capacity-tested promised delivery date based on the
current resource and material plan, and the required capacity and material to build the
product, if there is no currently scheduled production available to promise. The order
entry user interface is easy to use. And if the customer accepts the promised date,
and the order is entered, the capacity and material for the order is reserved in the
SCM engine, to ensure future CTP requests do not double-book capacity.
Page 2-1
Installing SCM 6.1 and APS Integration
Chapter 2. Installing SCM 6.1 and APS Integration

To run SCM release 6.1 with XA, you must install:
• APS Integration on the System i
• SCM 6.1 on the PC.
This chapter covers how to install each product on the respective system, and the
unique steps on the SCM PC required to manage the integration between the two
systems, namely:
• Creating an ODBC data source
• Setting the integration control parameters in the iSeriesIntegration.ini file
• Enabling Capable To Promise (CTP), for customer order promising during order
entry.
Note: System i connection software required. The PC running SCM must be
connected to the System i running APS Integration by an Open Database Connection
(ODBC) data source.
Use Client Access Express, Version 5, Release 1 or later to create this ODBC
connection on the PC.
Installing APS Integration on the System i

APS Integration for SCM 6.1 replaces APS Bridge, which runs with SCM 5.1 and 6.0.
If you are currently running SCM and APS Bridge, see Appendix E for conversion
information.
APS Integration requires MRP, and both applications must be installed on the System i
using the normal XA Cross Application Support (CAS) process. IM and either PDM or
EPDM are required for MRP. See the current XA CAS documentation.
Installing SCM 6.1 on the PC

This section gives an overview of installing SCM 6.1, as there is an SCM Installation
Guide with hardware and software requirements, and installation details for SCM. This
section identifies the topics unique to XA that are not covered in the SCM
document.
Installing SCM for use with XA includes the following steps:

1. Install the base SCM software components on the PC, either from a CD or from
the website.
In the Options list, select (at least) Synchronization Engine and ERP Integration.
On the XA iSeries (System i) Integration panel, select Use XA iSeries (System i)
Integration as default Integration to activate System i integration in the SCM config.ini
file if this is a new SCM installation, and to create an iSeriesIntegration.ini file in the
SCM install folder on the PC.
2. Create an ODBC data source on the PC to connect the PC to the iSeries (System i) with
APS integration installed, as explained below.
3. Set the parameters in the iSeriesIntegration.ini file to control the integration,
including connecting SCM to the iSeries (System i) environment and warehouse, and
Page 2-2
options for download, upload, Capable To Promise (CTP), and debugging. The
parameters, and options available for each, are explained below.
Note: If you are not using the SCM web components, your installation is
complete, and you are ready to test, or plan, using your iSeries (System i) warehouse.
4. Create an Application Server if you want to run Capable to Promise, or use other
SCM web components.
See “Enabling Capable To Promise (CTP)” for additional information on enabling
Capable To Promise.
5. If required, set up SCM for multiple plants (SCM term)/warehouses (System i term),
as described in the SCM documentation. This will result in a separate folder with a
separate config.ini file, SCM database, and iSeriesIntegration.ini file for each
warehouse, allowing you to control and run the warehouses separately, and with
different options if required.
6. Other steps, as required, depending on what additional features or components of
SCM you are using.
Page 2-3
Creating an ODBC data source

As mentioned earlier, Client Access Express, Version 5, Release 1 or later is required
to create an ODBC connection between the SCM PC and the System i with APS
integration installed. One ODBC data source can be used for multiple warehouses if
they are in the same XA environment on one System i, but if they are in different
environments, or on different System i, a separate ODBC data source is required for
each.
To create the data source on the SCM PC, select Start > Control Panel >
Administrative Tools > Data Sources (ODBC), to display the following ODBC Data
Source Administrator window:
Page 2-4
Select the System DSN tab, and click the Add button to display the Create New Data
Source window:
Page 2-5
Select Client Access ODBC Driver, and click Finish, to display the Client Express
ODBC Setup window.
On the General tab, enter a Data source name, and select the appropriate system
from the available System i systems.
Page 2-6
Select Connections Options to display the Connections options window:
In the Default user ID section, select Use the user ID specified below, and type in the
ID, and click OK.
Page 2-7
On the Server tab, select the System naming convention (*SYS), type AMALIBx in
SQL default library, where x is the first character of the ERP environment ID. Type
QGPL in Library list.
Page 2-8
On the Translation tab, select Convert binary data (CCSID 65535) to text.
Page 2-9
If you want to print a joblog of the System i download and upload jobs, on the
Diagnostic tab, select Print Joblog at disconnect.
Click OK to create an ODBC connection between the PC and the environment

serviced by the AMALIBx you entered on the Server tab.
Page 2-10
Integration Control – iSeriesIntegration.ini

This section describes the integration control parameters in the iSeriesIntegration.ini
file on the SCM PC. Navigate to the folder on the SCM PC containing this file, and edit
these parameters to control the integration for the warehouse.
Connecting SCM and Infor ERP XA

The parameters in the [ODBC] section link SCM to the iSeries (System i), environment,
and warehouse.
Parameter Options
ISeriesDataSourceName Name of the ODBC data source to the iSeries (System i)
ISeriesUserId A valid XA user ID
ISeriesPassword The password for the user ID
ISeriesEnv The two-character XA environment ID
ISeriesWarehouse The three-character warehouse ID
Download
The parameters in the [Download] section control, most importantly, whether APS /
SCM is active on the System i and planning the warehouse, and whether SCM runs
order board matching, and if not, what customer sales order date is downloaded to
planning. See The Planning Process in Chapter 3 for additional information on
activating APS Integration and downloading.
Parameter Options
APSActive 0 Default. APS Integration is not active in the warehouse.
1 Activate APS Integration in the warehouse (the next
download).
2 Deactivate APS Integration in the warehouse (the next
download).
DownloadMode 0 Default. Test: SCM can download and plan, but cannot
upload the plan to the System i. You can test download and
planning in this mode while planning the warehouse with
another technique.
1 Plan: Normal operation. APS must be active in the
warehouse.
LoadItemProcess 0 Default, and only option currently supported by the SCM
engine. If EPDM is active, download only the current
primary item process for an item.
PrintAuditReport 1 Default. Print download errors only.
0 Print no download audit reports.
2 Print complete download audit reports.
LongOperMinHours 0000008 Default (all seven digits are required). The
minimum number of hours for a long running operation. In
progress operations with setup or run time per batch equal to
or greater than this value will have Jobs In Progress (“JIP”)
records downloaded for more accurate scheduling. See Jobs
In Progress in Appendix A for more details.
Page 2-11
Parameter Options
OrderBoardMatch 1 Default. Yes, order board matching is done, to minimize
disruption between planning runs. See the SCM Concepts
book for additional information.
0 No, order board matching is not done.
IfNoMatchSendRequest If order board matching is not done, the date sent to SCM as
the customer order promise date. See Sales in Appendix A for
more details.
0 Default. No, send the date first promised by SCM:
For customer orders scheduled by SCM: original
manufacturing due date; For customer orders not yet
scheduled by SCM: (current request date minus ship lead
time).
1 Yes, send the date requested for all customer orders:
(current request date minus ship lead time).
CTP
The parameters in the [CTP] section control how purchased components are used in
CTP processing. See “Customer order scheduling and CTP” for more information.
Parameter Options
SCMCheckPurchaseMaterials 1 Default. Use minimum MRP lead time for all purchased
materials. See Item in Appendix A for more details.
0 Ignore purchased materials.
2 Use typical MRP lead time for all purchased materials.
SCMPlantName The name you gave the plant when you created the
SCM Application Server
SCMDaysToExpire When a customer order is CTPd and entered with the
CTP date, APS Integration enters a reserved order into
SCM, to reserve capacity against future CTP requests.
In the next planning run, SCM replaces the reserved
order with the actual customer order. If the customer
order is canceled before the next planning run, the
reserved order will not be replaced, as no customer
order is present. This parameter ensures that obsolete
reserved orders get deleted when they are not replaced
with a customer order.
5 Default. Number of days in which the reserved
order expires.
SCMCharacterSetId The coded character set identifier (“CCSID”) of the SCM PC,
used for data conversion in System i run remote command
processing in CTP. The value here is sent by the System i as a
parameter on run remote commands.
*CALC Default. The PC determines the CCSID to use.
1-65535 A valid CCSID value.
Page 2-12
Upload
The parameters in the [Upload] section control the processing done as the SCM plan
is uploaded to the System i.
Parameter Options
UpdateOpenWorkOrders 0 Default. No update of “work orders” (manufacturing orders
and REP schedules).
1 Update priorities and dates in open manufacturing orders
and REP schedules from the SCM schedule.
UpdateCOMCOPromiseDate 0 Default. No update of promise date in COM customer
orders.
1 Update the promise date only the first time it is planned by
SCM.
2 Update the promise date every time it changes.
UpdateCOMCODueDate 0 Default. No update of manufacturing due date in COM
customer orders.
1 Update the manufacturing due date only the first time it
is planned by SCM.
2 Update the manufacturing due date every time it changes.
UpdateUserCODates 0 Default. No update of user customer orders.
1 Update dates in the user customer orders per the options
above for COM customer orders
AutoCreateWorkOrders SCM checks component availability for planned orders during
planning, and planned orders with all components available
have 1 / Yes in the “Components available (SCM)” field in the
OBPM MRP Recommendations object. This field is used with
the two options below (1 if the item … code is 1, and 2) that
create orders only if all components are available.
0 Default. Create no “work orders” (manufacturing orders
and REP schedules).
1 Create work orders flagged for release based on the item
warehouse manufacture auto release code. The code has
the following options:
0 No auto release
1 Auto release if all components are available
2 Auto release.
2 Create work orders flagged for release if all components
are available.
3 Create all work orders flagged for release.
AutoCreateWOShopPacket 0 Default. Print no shop packets.
1 Print shop packets when creating manufacturing orders.
AutoCreatePurchaseOrders 0 Default. Create no purchase orders and requisitions.
1 Create purchase orders and requisitions flagged for
release based on the item warehouse purchase auto
release code. The code has options 0 through 7, and
processing is described in the MRP User’s Guide, Chapter
6, Option 7 Auto-Release Purchase Orders.
AutoCreateIntersiteOrders 0 Default. Create no intersite orders.
1 Create intersite orders flagged for release if the item
purchase auto release code is 2 or greater, or the item
manufacture auto release code is 1 or greater.
2 Create all intersite orders flagged for release.
Page 2-13
Parameter Options
AdjustOpStartForCurrentDate 1 Default. Ensure that no manufacturing operation start date
is before the MRP current date.
0 Use the SCM Don’t Do Before date as the manufacturing
operation start date.
AdjustOpStartForPrevOpStart 1 Default. Ensure that no manufacturing operation start date
is before the previous operation start date.
0 Use the SCM Don’t Do Before date as the manufacturing
operation start date.
AdjustOpComplForPrevOpCo 1 Default. Ensure that no manufacturing operation
mpl completion date is before the previous operation
completion date.
0 Use the SCM operation completion date as the
manufacturing operation completion date.
Debug
The parameters in the [Debug] section control whether data files are written on the
SCM PC.
Parameter Options
CreateDataFiles 0 Default. Do not create data files on the SCM PC.
1 Write download and upload data in files on the SCM PC.
Page 2-14
Enabling Capable To Promise (CTP)

Capable To Promise requests from the System i execute commands on the PC
“remotely”, that is, from the System i. To enable these commands to be run remotely,
you must set the Client Access Express Remote Command service to start
automatically, so that it will start when the PC is booted.
On the SCM PC, select Start > Control Panel > Administrative Tools > Services.
Double click on the Client Access Express Remote Command service, to see its
properties:
On the General tab, select Automatic for Startup type, click Start under Service status,
and click OK.
In order to make CTP requests while entering customer orders in COM, you must
also:
• Set the the user data default “Automatic available to promise” in COM
• Create an SCM server for the plant
• Enter the plant name into the SCMPlantName parameter in the CTP section of
ISeriesIntegration.ini
Page 2-15
• Load, or start, the SCM plant, per the SCM documentation, to handle the
requests.
Note that unattached job AXATGU runs on the System i to create the reserved orders.
Page 2-16
Page 3-1
Managing APS Integration
Chapter 3. Managing APS Integration

This chapter provides additional information to help you manage the major areas
identified in Chapter 1.
Information used In SCM planning ........................................................................... 3-1
The planning process ............................................................................................... 3-9
Implementing the plan ............................................................................................ 3-13
Customer order scheduling and CTP ..................................................................... 3-13
Information used In SCM planning

As APS Integration uses MRP as the primary user interface on the System i, the same
supply and demand information used in MRP is used in APS Integration with SCM
planning. This section reviews the information used in planning, and highlights the key
differences between MRP, Advanced Planner (AVP), and APS/SCM. The information
is discussed in the same sequence it is summarized in Chapter 1. Appendix A gives
all the details of the data downloaded to SCM.
Production facility information

Production facility information, including capacity, calendar used, utilization and
queue times, is used. MRP does not use this data, but AVP and SCM do. Other
differences and points to note are:
Calendars
Neither AVP nor SCM downloads calendars, so you must maintain calendar
information on the System i and the planning engine.
Capacity
AVP and SCM define only the capacity/units for the facility, not for each shift, so
the largest capacity/units is used.
Queue times
SCM defines three queue times a facility can have. If it is a drum, it can have a
typical queue time and a minimum queue time. If it is not a drum, it can have a
forced queue time. The standard queue time is downloaded into the typical queue
time and the forced queue time, so it is available whether the facility is a drum or
not. The input buffer hours is downloaded into the minimum queue time. AVP
does not define drums, and uses typical queue and minimum queue times.
Item/product information
Item definition is used, including the lead time code (make or buy), bill of material and
routing if make, and purchase lead times if buy. Item warehouse codes let you control
whether certain kinds of item demand are used in planning: Plan customer orders
code, for customer orders from COM, CSM, COM_Net, and so forth, Plan expected
customer orders, for expected customer orders from EC, and Forecast code, for
forecasts from FCST. You can also propagate either forecasts or requirements using
the Master level forecast code and three associated fields. Order planning
parameters, including number of days supply, and order minimum, multiple and
maximum quantity modifiers are used in planning order quantities. Key differences
between MRP, AVP and APS/SCM are:
Page 3-2
Combining requirements
AVP and SCM use the Combine customer orders option, specified for the
warehouse in MRP Planning Run Execution Options, but do not combine
requirements according to the item warehouse Combine requirements code.
Master level items:
Master level items
AVP and SCM honor the master level item code, but treat all non-blank master
level item codes as M (multiple source).
Order planning
SCM uses the same order planning parameters (days of supply, and order
minimum, multiple, and maximum quantity modifiers) as MRP does. As a result,
SCM plans order quantities almost exactly as MRP does for order policy codes A
– Discrete, D – Fixed quantity, G – Time periods of supply, and H – Discrete
above a minimum. Download sends the proper data in Aggregation period and
Minimum lot, based on the order policy code, to accomplish this.
The order maximum is used differently by SCM for manufactured and purchased
items. For manufactured items, if the quantity required exceeds the order
maximum, the order is planned for the order maximum, and order planning
restarts with the remaining quantity required. For purchased items, if the quantity
required exceeds the order maximum, the order is planned for the quantity
required, and an exception is issued.
Manufacturing order lead times
SCM does not use the item manufacturing lead time, but schedules work orders
dynamically, based on the quantity, resources and components required, and
whether any of the production resources is a drum. See the SCM documentation
for further information.
Purchase time fences
AVP and SCM do not use the Firm time fence or the Authorized time fence, but
flag purchase orders for release only if their start date is on or before the
(warehouse horizon) Release date.
Order rescheduling
SCM does not use the order, item or warehouse reschedule control information.
Work orders are scheduled when required, and appropriate exceptions are issued
for early or late purchase orders.
Schedule controlled (REP) items
SCM plans schedule controlled items using a single operation routing based on
the information in the item line (ITMLIN) record for the primary production line for
the item. The production line is the work center for the operation. So the schedule
is planned as one step. If an item has multiple item lines, and PDM is active, an
alternate routing operation is downloaded for each alternate item line. This helps
you see during planning when you can offload a planned REP schedule to
another production line. After planning, REP schedules can optionally be
automatically created (not released), and they can also be created and
maintained in Enter and Maintain Schedules, as they are with MRP.
KBC items
SCM identifies KBC-configured items using a unique item number composed of
the item number and a 7-digit sequence number for each configuration of the
item. Download uses this unique number to send all information for the
configuration: an item, bill and routing, the customer order line item, and, when
released, the open manufacturing order. Manufacturing orders for KBC items
must be released in Inventory Management Order Entry and Order Release, as
with MRP. The sequence number is visible only on the planning engine, not on the System i.
Page 3-3
Additional SCM item information (PPITEM file)

Three additional item fields dealing with SCM forecast consumption are provided
in a user-controlled PPITEM file. See “Forecast consumption” for more
information, and see Appendix D for the fields in the PPITEM file.
Additional SCM routing information (PPROUT and PPSEQS files)
These two files provide additional information used by SCM in scheduling
operations. The PPROUT file provides five additional routing operation attributes.
The PPSEQS file defines the desired scheduling sequence of operations within a
setup family, and associated setup times. See Appendix D for more information.
Demand and forecast consumption

All demand downloaded to SCM is planned, including forecasts, customer orders,
safety stock, expected customer orders from EC, intersite orders, and master level
requirements entered in MRP.
As APS Integration interfaces through MRP, it supports demand warehouses

associated with a planning warehouse just as MRP does, so forecasts, customer
orders and safety stocks from demand warehouses can be used in planning the
warehouse. See the MRP User’s Guide for additional information.
Forecast consumption
SCM consumes, or blends, forecast demand with customer sales demand, and plans
for the customer sales demand plus only the unconsumed forecast. It consumes
forecast on a monthly basis, and by smaller periods within a month if the forecast is in
smaller periods. Consider the example of a monthly forecast submitted as 25 per
week for four weeks. If a customer order is booked for 55 in the third week of the
month, SCM consumes the forecast of 25 for the third week, then goes toward the
beginning of the month, consuming the 25 for the second week, and finally consumes
5 of the 25 for the first week. As a result, it plans for 20 the first week, 55 on the date
of the customer order, and 25 the fourth week. If the order had been for 83, after the
entire forecast of 25 for the first week were consumed, SCM would then go towards
the end of the month to consume the remaining 8, and would plan for 83 for the
customer order and 17 the fourth week.
FCST stores forecasts by periods defined in the calendar for the warehouse, and
loads forecast to MRP (where they are used by APS Integration), on week-beginning
dates, either by week or by period, based on a FCST tailoring question. If your FCST
periods are not calendar months, the first week-beginning date in a FCST period may
not always be in a new calendar month. As SCM consumes forecast on a monthly
basis, if your FCST periods are not months, you should answer the FCST tailoring
question so that forecasts are converted to weekly forecasts at least through your
longest cumulative material lead time, and longer if desired, to ensure satisfactory
forecast consumption by month.
SCM can consume forecasts in three ways, and provides three additional item
attributes to control this. The three attributes are defined in the “Item (PPITEM)”.
The simplest forecast consumption is by individual item – the additional item

attributes are not required. The forecast for each item is consumed only by customer
sales orders for that item.
If there are many finished products, made from relatively few components that must
be forecast, you can forecast only the components. Enter forecasts only for the
Page 3-4
components, not finished products. Enter a Family ID (FMID in PPITEM) of FULL for
the components, to specify that the forecast for this item is to be consumed by any
customer order (CO) that requires that item, either directly or as a component. SCM
consumes a forecast by a CO only when there is a forecast, and the Family ID of the
forecast allows it. When a CO is entered for a parent item with no forecast, SCM
explodes the CO through the item BOM, until it finds an item with a forecast with a
Family ID that allows it, and the component quantity required consumes the
component forecast.
To enter and consume forecasts by product family, define a Planning bill item, a
special type of item that cannot be built, but can help you forecast components for a
family of products. Let’s say we define Planning bill item P, for family P of products.
Define a BOM for P, with the Components to be forecast, say items C, D and E with
the average quantity used in a Finished product in the P family, say items F, G and H.
Items F, G and H all are real items that are sold, built and shipped, and so have BOMs
and routings that use components C, D and/or E, in different quantities and
combinations. Note that the finished products F, G and H are not in the planning bill
for item P.
• For item P, type in 1 in Planning bill item (PLNB in PPITEM).
• For finished product items F, G and H, type in P in Forecast family ID (PRTF in
PPITEM: identify customer orders for this item with this forecast family, that is,
consume only forecasts for this family).
• Enter the forecast for item P, not for the specific products sold (F, G and H). As
item P is a planning bill item, its forecast, for Family P, is exploded through its
BOM until a (non-phantom) item (for example, C, D and E) is found, and a
forecast, for the exploded quantity, is entered for that item, and identified as for
Family P.
As customer orders are entered for products F, G or H, as they have no forecast,
SCM explodes the CO quantity, identified as Forecast family P, through the BOM,
and the component quantity required consumes the first forecast found for Family
P, in this case for components C, D and E.
Note that a second planning bill item, say item L, can be defined for a second
family L, say with finished products M, N and O, and those products could also
use components C, D or E.
- For item L, type in 1 in Planning bill item (PLNB in PPITEM).
- For finished product items M, N and O, type in L in Forecast family ID (PRTF
in PPITEM).
- Enter the forecast for item L, not for the specific products sold (M, N and O).
As item L is a planning bill item, its forecast, for Family L, is exploded through
its BOM until a non-phantom item (for example, C, D and E) is found, and a
forecast, for the exploded quantity, is entered for that item, and identified as
for Family L.
As customer orders are entered for products M, N or O, as they have no
forecast, SCM explodes the CO quantity, identified as Forecast family L,
through the BOM, and the component quantity required consumes the first
forecast found for Family L, in this case for components C, D and E – not the
forecast for those parts for Family P, which is only consumed by sales of
products in Family P.
Page 3-5
Forecast demand
APS Integration downloads forecast demand to SCM from:

• Forecasting, if the item Forecast code is 2 or 3, input forecast to MRP or MPS
• User-entered information in MRP Maintain Forecast
• User-propagated from fields in the Item Warehouse object and Item Balance file
• User-supplied information from a user program that loads the forecast to the MRP
Requirements (REQMTS) file with the following fields:
- Warehouse (RQPLWH)
- Item number (RQCOM)
- Forecast date (RQDUD)
- Forecast quantity (RQQTY)
- Sequence number of 50001 or greater, ensuring that no duplicate key of
warehouse/item number/date/sequence (RQSEQ) exists
- Source of 5 forecast (RQSOR)
- Origination of 20 or greater (RQORG)
- Blank customer order ID (RQCID).
The user program must build and maintain the forecast, but need not delete it
as time passes. Download deletes the forecast when it is for a previous
month.
• User-supplied in APS Integration (See Appendix D). Download loads these user-
supplied forecasts into the MRP REQMTS file, identified as described for user-
supplied forecasts just above, but with one difference: the Origination (RQORG)
is 10.
Customer sales demand
APS Integration downloads customer sales order demand to SCM from:

• Customer orders from Customer Order Management (COM), Customer Service
Management (CSM), Electronic Commerce (EC), and COM_Net if not filtered
from planning by a COM hold code specified in MRP Menu AMMM10, Option 8,
Maintain Customer Order Filters, and if the Planned customer orders code is 1,
2, 3 or 5
• Expected customer orders from Electronic Commerce (EC) based on the if the
expected customer order type, if the Plan expected orders code = A, B, C or D
• User-supplied information from a user program that loads the customer demand
to the MRP Requirements (REQMTS) file with the following fields:
- Warehouse (RQPLWH)
- Item number (RQCOM)
- Required date (RQDUD)
- Order quantity (RQQTY)
- Sequence number of 70001 or greater – ensuring that no duplicate key of
warehouse/item number/date/sequence (RQSEQ) exists
- Source of 6 or 7 (manual or held requirement) (RQSOR)
Page 3-6
- Origination of 20 or greater (RQORG)

- Non-blank customer order ID (RQCID).
The user program must build and maintain the customer demand entirely,
including deleting the demand when the order is shipped. Download deletes
the customer demand if the source (RQSOR) is 6 and is earlier than the MRP
current date, or if the source is 7 and is earlier than the MRP start date.
• User-supplied in APS Integration (See Appendix D). Download loads these user-
supplied customer orders into the MRP REQMTS file, identified as described for
user-supplied customer orders just above, but with two differences: the Source
(RQSOR) is 7, and the Origination (RQORG) is 10.
Both forecast and customer sales demand
APS Integration downloads two types of demand to SCM as both forecast demand
and customer demand. No forecast from the preceding sources is consumed by this
demand.
• Intersite orders, both planned and open. InterSite Logistics (ISL/MISL) records
intersite shipments as inventory transfers, not sales. Intersite demand is not
included in forecast (based on sales), so you must plan it in addition to forecast.
• User master level item requirements entered in MRP Maintain Master Level Item
Schedules or propagated from fields in the Item Warehouse object and Item
Balance file. You can enter special demand of any type and have it directly affect
the plan in addition to forecast, as requirements do in MRP.
SCM also plans safety stock in addition to any other forecast or customer demand,
just as it plans the preceding two types of demand.
Unconsumed forecast
MRP shows forecast demand two places:

• All forecasts appear in Forecast Demand and are used with customer orders to
compute Greater Demand in the following:
- Review Forecast/Orders display (AMM451)
- MLI Requirements vs. Forecast/Orders display (AMM351)
- MLI Requirements vs. Forecast/Orders report (AMM221).
• Forecast requirements, used in MRP planning, appear in Requirements or
Planner Requirements, in the following:
- MLI Requirements vs. Forecast/Orders display (AMM351)
- Item Requirements Inquiry display (AMM511)
- MLI Requirements vs. Forecast/Orders report (AMM221)
- Requirements Planning and Master Items Planning reports (AMM3A1).
APS Integration shows the total forecast in Forecast Demand, and after planning, it
shows only the unconsumed forecast in Requirements (identified as Forecast
Requirements – FCR or FCST REQ). Only the unconsumed forecast is used in
planning.
Page 3-7
The download and upload processes manage the MRP requirements (REQMTS) file,
so the MRP displays and reports show only unconsumed forecast as forecast
requirements. Download deletes all types of forecast requirements records:
• Source (RQSOR) is 6 or 7
• Origination (RQORG) is 1, 6, or 20 or greater
• Customer order ID (RQCID) is blank.
Upload builds forecast requirements records for the unconsumed forecast:

• Source (RQSOR) is 6
• Origination (RQORG) 6
• Customer order ID (RQCID) is blank.
Although APS Integration uses MRP to view forecasts, APS Integration handles
forecasts differently than MRP does. FCST loads the same forecasts to MRP files in
the FCST Forecast Load to Master Schedule, based on the frozen, firm, and free
period days you specified in FCST Forecast Control. APS integration treats the FCST
data differently in two ways:
• APS Integration uses the forecasts, not the forecast requirements. Download
deletes all forecast requirements and upload rebuilds them with only the
unconsumed forecast.
• APS Integration does not delete forecasts as they become past due, that is, prior
to the MRP Current Date. Forecasts are retained for the entire month, and used in
SCM forecast consumption.
As SCM consumes forecast on a monthly basis, forecast and customer sales data is
downloaded for the entire current month, even the part of the month that is past. So
the forecast for the entire month is always downloaded, as are customer orders
already shipped that were promised for delivery this month, along with all unshipped
customer orders and future forecasts.
APS Integration shows forecast similarly to the way MRP shows it. The total forecast
from all sources appears in Forecast Demand. Only the forecast used in planning
appears in Requirements. The difference is that SCM consumes forecast to
determine the forecast used in planning and APS Integration updates the MRP
requirements file with the results.
Supply information
APS Integration downloads the following data for the three types of supply accepted
by SCM:
• Inventory: On hand quantity for the warehouse and associated demand
warehouses, excluding inventory identified as non-nettable
• Workorders: Open manufacturing orders, and released and unreleased REP
schedules, with component and operation requirements and status
• Purchase orders: Open purchase order line items, line item blanket releases,
purchase requisitions, and intersite orders.
Page 3-8
MRP planning parameters

This section discusses all the planning parameters MRP uses at a warehouse level,
and describes whether those parameters are used in SCM planning.
The following MRP warehouse planning parameters are used just as they are in MRP:
• Planning Horizon Dates, to set the planning “base date” (Current Date), to
determine planning exceptions, and to define the supply order review horizon:
- Start Date
- Current Date
- Release Date
- Review Date.
• Planning Run Execution Options, to control combining of COM customer orders,
clearing of quantity sold, source of demand tracking, rescheduling of canceled
orders, contracts in purchase auto release, and safety stock timing:
- Combine customer backlog orders
- Clear quantity sold with extract
- Maximum demand sources to track
- Track demand sources for on hand quantity
- Cancel exception code
- Contract required for auto release
- Safety stock lead time.
Note: SCM plans as of the MRP Current Date, as the Planning Horizons, listed
above, are all based on that date. This allows you to build a plan today for tomorrow,
or the next working day if a weekend. Note, however, that the MRP Current Date
should be set to only the current date or the next working day, as the SCM assumes
that it is scheduling as of today.
SCM planning does not interface to MPSP, always plans all (planned) items in a
warehouse, extracts independent demand if COM is interfacing to MRP, always
extracts all requisitions, always reschedules open production orders as required by
demand, and never reschedules open purchase orders, so a number of MRP
planning parameters are not used:
• Planning Run Execution Options:
- Level to plan master level items
- Warehouse, item, and order reschedule codes
- Minimum days to reschedule orders
- Rescheduling frozen zone
- Due date in past automatic rescheduling options (3)
- Extract requisitions.
• Initiate Planning Run Options:

- Extract independent demand
- Transfer new master scheduled orders from MPSP
- Automatic reschedule options (3)
- Planning run type.
SCM does not combine requirements while planning, so the item warehouse combine
requirements code is not used. Requirements can be summarized for printing using
the MRP Period Intervals.
Page 3-9
SCM always plans all allocations to manufacturing orders and REP schedules as time
phased, based on the operation where used, and the planned production schedule for
that operation. The Time-phased allocations option in Planning Run Execution
Options, and the Allocation days in Maintain Horizon Values control whether
allocations are stored as requirements in the MRP REQMTS file (scheduled as they
are in MRP), and therefore how they appear on MRP displays and reports, and are
treated in component availability checking during manufacturing order release in MRP
and OBPM.
You control auto release of manufacturing, purchase and intersite orders after
planning via Upload options in the iSeriesIntegration.ini file on the SCM PC. See
“Implementing the plan”.
The planning process

As discussed in Chapter 1, planning has three parts: Downloading to SCM, Planning
and Scheduling, and Uploading to ERP. All three parts are initiated and controlled
from the SCM PC. This section will discuss each part so you can understand and
manage the process. But first let’s discuss what “Activating” APS Integration means,
and how to do it.
Activating APS Integration

Three planning applications interface to XA using the MRP
planning files: MRP itself, Advanced Planner (AVP), and SCM Release 6.1 with APS
Integration (APS). SCM Release 6.0 with APS Bridge also plans for XA,
although it does not use the MRP files.
To prevent one of these applications from damaging another application’s information,

AVP and APS must be Activated in a warehouse before they can update the MRP
planning information for that warehouse. You can download data to the planning
engine in test mode (vs. plan mode), and run the planning engine, but you cannot
save the plan (in AVP) or write schedule pass (in SCM) unless that planning
application (AVP or APS) is active in the warehouse. Only one planning application
can be active in a warehouse, and while it is, the other planning applications cannot
plan the warehouse.
You activate (and deactivate) both AVP and APS in a warehouse the same way:
1. Setting an option in a control file on the planning engine (for AVP, the
APDataLink.ini file; for APS, the iSeriesIntegration.ini file; see Chapter 2)
2. Planning the warehouse, to set on (or off) a flag in the AVP/APS control file on the
iSeries (System i), to establish that application as planning the warehouse.
Activating APS Integration in a warehouse (set APSActive to 1 and plan): prevents

MRP, AVP and APS Bridge from planning the warehouse (AVP is actually deactivated,
and cannot be activated while APS Integration is active); if AVP was not active in the
warehouse, saves (to allow restore, see below) and clears the MPSP item codes
(MSIC in ITMPLN) for items in the warehouse, to disable the interface between MRP
and MPSP, as neither AVP nor APS interfaces to MPSP (if AVP was active in the
warehouse, these codes were cleared when AVP was activated).
Page 3-10
Deactivating APS Integration in a warehouse (set APS Active to 2 and plan in test
mode):
• If AVP was not previously active in the warehouse, restores the MPSP item
codes, and sets off the flag in the APS control file, to permit MRP and APS Bridge
to plan the warehouse
• If AVP was previously active in the warehouse, “Re-Activates” AVP, permitting it to
plan the warehouse.
Note that forecast and forecast requirements are handled differently in MRP, AVP and
APS, so if you change from one to the other – or back – you should run FCST Load to
Master Schedule to refresh the MRP REQMTS file for the new application.
Ideally you should test APS/SCM in a separate environment before you activate it in
your operational environment, so you can activate it and save and upload the plan
and work with it in MRP or OBPM as you will in operation, before you go live.
Downloading to SCM
Planning must first download the information required from the System i. When you run
SCM DBUtil with System i Integration activated in SCM, it performs the following steps:
1. Opens an ODBC to the System i.
2. Runs a System i procedure to extract demand data into MRP work files, and
extract all the System i data required for SCM planning into ERP work files (see
Appendix A)
3. Loads the planning data to the SCM database.
Parameters in iSeriesIntegration.ini establish the connection to the System i and the

specific XA environment and warehouse, and help control the download,
planning and upload parts of the process. All the control parameters, and the options
for each, are defined in “Integration Control – iSeriesIntegration.ini”.
The parameters to connect the SCM PC to the XA system, environment,

and warehouse are defined in “Connecting SCM and XA”.
The download parameters are defined in “Download” in Chapter 2 and are discussed
here.
The APSActive and DownloadMode parameters, mentioned in the previous section,

control whether the planning run is only a test, or will upload the plan back to the System i
for implementation. You can run in test mode while any planning application is
planning the warehouse, as the download does not conflict with any other ERP jobs,
does not save data, and cannot upload. When getting ready to go live with APS / SCM
in a warehouse, you may want to run in test mode on the actual warehouse in the
operational environment, to ensure your ODBC connection and the parameters in the
iSeriesIntegration.ini match, and connect properly.
When APS Integration is active, and you run with DownloadMode set to 1-Plan, APS
Integration establishes job conflicts with the following ERP jobs from download start
until upload completion:
• MRP Maintain forecast
• MRP Maintain MLI requirements
• MRP Maintain horizon values
Page 3-11
• MRP Maintain period intervals

• MRP Planning run execution options
• MRP Order review and approve
• OBPM MRP recommendations.
The PrintAuditReport parameter allows you to see reports of errors that prevent data
from being downloaded to planning. See Appendix C for the possible error messages.
See “Customer order scheduling and CTP” to see how the download
OrderBoardMatch and IfNoMatchSendRequest parameters fit into SCM customer
order scheduling.
User exit
APS Integration provides a user exit UXADNL01, called if present on the System i,
in download after the PPI* files are built on the System i and before they are loaded
by DBUtil to the SCM database.
Planning and scheduling

Planning and scheduling can work a variety of ways in SCM, considering batch DDQ,
synch and resynch, order board matching, etc., and all of those options can be
automated, customized, scripted, run as scheduled jobs, and so forth. This document
does not address all the options. See the SCM documentation.
Once DBUtil has loaded the System i planning data to the SCM database, the SCM
synch engine, using the functions selected, loads the data into memory, consumes
forecast with customer orders, and builds the detailed plan and schedule to satisfy the
demand. When the plan is complete, and Write schedule pass is performed, it writes
the plan/schedule to the SCM database, and uploads the information required to
implement that plan to the System i.
Uploading to ERP
As the information is uploaded to the iSeries (System i), APS Integration:
1. Loads the planning results into the MRP planning work files, and runs the last
steps in MRP planning to:
• Load the MRP files from the work files
• Create the Order Review file for use in MRP/OBPM review and release of all
needed supply orders
• Print MRP reports as specified in the MRP Planning Run Report options.
2. If the iSeriesIntegration.ini upload parameter UpdateOpenWorkOrders is 1 -
Update, updates open manufacturing orders and REP schedules with scheduled
dates, priorities, and offloaded facilities for unstarted operations, from the SCM
schedule.
3. Updates COM and user customer orders as specified in the iSeriesIntegration.ini
upload parameters UpdateCOMCOPromiseDate, UpdateCOMCODueDate and
UpdateUserCODates. See “Customer order scheduling and CTP” for details.
Page 3-12
4. Automatically creates manufacturing orders and REP schedules as specified in

the iSeriesIntegration.ini upload parameter AutoCreateWorkOrders, and the item
warehouse Manufacture order release codes. Manufacturing orders are
released; REP schedules are created but not released. You can use a single
option whether to create manufacturing orders and REP schedules for all items:
0 No
1 You can set different options by items: If flagged for released, based
on the item warehouse Manufacture auto release code, which has
the following options:
0 No
1 If all components are available
2 Yes
2 If flagged for release (Start date is within MRP Release Horizon) and
SCM determined that all components are available
3 If flagged for release
The AutoCreateWOShopPacket parameter specifies whether shop packets are
printed for manufacturing orders released.
5. Automatically creates purchase orders, blanket releases and requisitions as
specified in the iSeriesIntegration.ini upload parameter
AutoCreatePurchaseOrders, and the item warehouse Purchase auto release
codes. This works just like MRP Auto Release Purchase Orders.
6. Automatically creates intersite orders as specified in the iSeriesIntegration.ini
upload parameter AutoCreateIntersiteOrders, and the item warehouse purchase
and/or manufacture auto release codes. The options are:
0 No
1 If flagged for release, and either the item warehouse manufacture
auto release code is 1 or 2 or the item warehouse purchase auto
release code is 2 or greater
2 If flagged for release
7. Gives you the option to either adjust the SCM dates for non-drum operations to
make them more reasonable, or to upload them as is from SCM. Basically, for
non-drum operations, or for drum operations that are split while scheduling, SCM
does not ensure that the Don’t Do Before dates make sense either relative to the
dates for the previous operation, or relative to the current planning date. So for
scheduled operation start dates and scheduled operation completion dates, APS
Integration by default adjusts the dates for reasonableness, but lets you also
upload the SCM dates as is, if you want. See the last three entries in the table in
“Upload” for details.
See the “Integration Control – iSeriesIntegration.ini” for all the parameters and
options.
See Appendix B for the details of the iSeries (System i) information updated from planning.
User exits
APS Integration provides two user exits in upload:
• UXAUPL01, called if present on theSystem i, when the SCM engine connects

to the System i and before any processing
Page 3-13
• UXAUPL02, called if present on the System i, after data is sent from SCM to
the System i and processed.
Implementing the plan

After the SCM plan is uploaded to the MRP files, and processed based on the upload
options you specified in the iSeriesIntegration.ini file, you can take the actions
required to implement the plan using all the functions available to implement an MRP
plan on the MRP Order/Schedule Release and Review menu.
You can use either MRP or Order Based Production Management (OBPM) to review
and create required manufacturing, purchase and intersite orders that were not
automatically created in upload.
You can use either MRP or OBPM to check component availability for manufacturing
orders being released. As discussed in the previous section, SCM performs a
component availability check during planning, and the Components available (SCM)
field in the MRP Recommendations object in OBPM shows the results, and is
available to you while creating manufacturing orders in OBPM.
You can use either MRP or OBPM to create, expedite, or defer purchase and intersite
orders as required.
You can enter and maintain REP schedules as you do with MRP.
You can define and send purchase planning schedules to suppliers, either printed,
faxed, or via EDI if you have Electronic Commerce (EC).
Notes:
1. SCM does not support firm planned orders, so firming a planned order in MRP
or OBPM has no effect, as firm planned orders are discarded during the next
planning run.
2. SCM schedules the operations for all open and planned manufacturing orders,
and for planned orders, APS Integration updates the manufacturing orders with
that schedule data as the order is released. So if you change the quantity, date, or
if EPDM is active the item process as you release the manufacturing order, the
order is updated with SCM data previously determined in planning, so can be
incorrect until the next plan. The order will be rescheduled as required in the next
SCM plan, and updated along with other open orders from that plan.
Customer order scheduling and CTP

When a customer order is entered in XA, SCM determines the earliest
date it can build (and ship) the order the next time it plans, either by consuming
available forecast or by scheduling available capacity. The SCM scheduled date is
loaded into the original manufacturing due date in the order line item release record
during upload after planning, and a Scheduled by APS flag is set in the record.
If an order is entered interactively in COM, and you use Capable to Promise (CTP)
against the current memory-resident SCM plan, you can have SCM determine the
Page 3-14
earliest ship date, as above, while you are entering the order. In fact, when you make
the CTP request, APS Integration adds the order shipment lead time to the SCM
scheduled build date, and displays the promised delivery date. If the order is entered
with the CTP date, the SCM scheduled build date is loaded into both the original and
the current manufacturing due date, and the scheduled delivery date is loaded into
both the original and the current promise date in the order line item release record,
and a Promised using CTP with APS flag is set in the record (as is the Scheduled by
APS flag). A reserved order is also entered into the SCM plan to prevent double
booking of forecast or capacity by future CTP requests.
If the ordering customer does not need the item until a specific date, that date can be
entered into the CTP request, and SCM will determine the earliest date it can build the
item on or after the requested date.
CTP requests will be rejected if the order has a COM hold code that is filtered from
planning using the MRP Maintain Customer Order Filters function.
Handling purchased items in CTP

There are three ways that you can have SCM treat purchased items in a CTP request,
by setting the CheckPurchaseMaterials parameter in iSeriesIntegration.ini:
0 Ignore purchased items: assume they can be obtained as needed

1 (default) Use the minimum lead time for purchased items required (purchase
vendor: LTVEN)
2 Use the normal lead time for purchased items required (purchase vendor
plus safety: LTVEN + LTSAF)
CTP for KBC items

Each order for a KBC item generates a new configuration of the item, with a bill and
routing, and possibly lower level bills and routings if some components are also
configured. APS Integration defines each configuration as a new item to SCM, by
appending a sequence number to the base item number. When a CTP request is
made for a KBC item, APS Integration sends the configured items, bills, and routings
to SCM and loads them into the SCM database, so the request can be accurately
answered. CTP requests for KBC items therefore take longer than CTP requests for
standard items
Order board matching

During normal planning, SCM uses order board matching to give priority to orders
previously scheduled, to minimize the chances that their promise dates are affected
by newly entered orders. APS Integration ensures that orders previously sent to SCM
are sent with the same date – providing the requested delivery date hasn’t changed,
or the order quantity hasn’t increased.
For orders entered without using CTP, APS Integration always downloads (latest
requested date minus ship lead time) as the order date, so that SCM can match the
order if it was previously planned.
When an order is entered in COM with the CTP date, the Promised using CTP flag is
set in the order, and a reserved order is created in SCM. In this case, APS Integration
Page 3-15
downloads the original manufacturing due date for the order, which matches the date
in the reserved order. If the customer changes his requested date, or increases the
order quantity, COM/CSM sets off the CTP flag, and APS Integration downloads
(latest requested date minus ship lead time) as the order date, to have SCM
reschedule the changed order.
Order board matching = no
For a variety of reasons, you can have SCM reschedule all orders by not using order
board matching. You select whether to use order board matching by setting the
download OrderBoardMatch parameter (1 = Yes [default], 0 = No). Depending on the
reasons for this, you may want SCM to schedule using:
• The SCM previously scheduled dates
• The current requested dates.
You select this by setting the download IfNoMatchSendRequest parameter:

0 (default) No. For previously scheduled orders (Scheduled by APS flag is on), send
the date SCM first promised, or scheduled, so SCM plans previously
scheduled orders using their scheduled date (original manufactured due
date) to try to preserve it. For these orders, set on the Promised using
CTP flag, so order board matching works properly in later planning. For
orders not previously scheduled, send the requested date (latest
requested date minus ship lead time).
1 Yes. Send the requested date (latest requested date minus ship lead
time), for all orders, and set off the Promised using CTP flag, so order
board matching works properly in later planning.
Updating customer orders from SCM planning

As conditions of all types change with your plan, you may determine that you cannot
meet all the currently scheduled dates and you can have SCM schedule revised dates
for some customer orders.
Whenever SCM plans a date that does not match the currently scheduled date in the
order, APS Integration writes a record in the Customer order upload file (see
Appendix B).
You can also have APS Integration upload the revised dates directly back into the
customer order records after SCM planning, by setting two parameters in
iSeriesIntegration.ini:
• UpdateCOMCOPromiseDate: controls whether the current promise (delivery)
date is updated from planning;
0 (default) No update
1 Updates the date only the first time SCM plans the order
2 Updates the date every time the SCM plan date changes
• UpdateCOMCODueDate: controls whether the current manufacturing due (ship)
date is updated from planning;
1 Updates the date only the first time SCM plans the order
2 Updates the date every time the SCM plan date changes.
Page 3-16
User customer orders
User customer orders, that you maintain (see Appendix D), are planned by SCM just
like orders in the COM files. APS Integration tracks whether the user order was
scheduled, and you control whether promise dates or manufacturing due dates are
updated from planning by the UpdateUserCODates parameter in
iSeriesIntegration.ini:
1 Update user customer order dates using the two parameters for COM
orders.
Page A-1
Data downloaded to SCM
Appendix A. Data downloaded to SCM

This table lists the data files sent to SCM. Each file is further described on the
following pages in this appendix.
Download file (ERP workfile

name) Contents/Purpose/Source See page ...
Item (PPIPRT) Items planned, from IM, KBC and A-2
APS
Item Process (PPIPRC) (for future Item processes sent from EPDM A-4
use)
Bill Of Material (PPIBOM) From PDM, EPDM, and KBC A-5
Routing (PPIRTG) From PDM, EPDM, KBC, and A-6
APS
Workcenter (PPIWKC) From PDM and EPDM A-8
Setup Sequence (PPISEQ) Operation sequencing and setup
times from APS
Forecast (PPFCS) From FCST, MRP, ISL/MISL, and A-10
APS
Sales (PPICOM) Customer orders from COM/CSM, A-11
expected customer orders from
EC, planned intersite demand
from ISL/MISL, MLI requirements
from MRP, and APS
Inventory (PPIINV) On-hand quantity from IM and A-13
MRP
Workorder Heading (PPIMOM) Manufacturing order and REP A-14
schedule masters, from IM,
PC&C, and REP
Workorder Allocation (PPIMOD) Component allocations for A-15
manufacturing orders and REP
schedules from IM and REP
Workorder Routing (PPIMOR) Operations for manufacturing A-16
orders and REP schedules from
PC&C and REP
Jobs in Progress (PPIJIP) Hours remaining for in-progress A-18
long operations from APS
Purchase (PPIPUR) Purchase orders and requisitions, A-20
intersite orders from PUR and
ISL/MISL
Warehouse Control (PPIPLN) MRP planning requirements from A-21
MRP
Page A-2
Item (PPIPRT)
SCM plans an item only if the item has an MRP order policy (not B or C) and is not a
kit, miscellaneous or service item, or an APC/Cameleon item. If KBC is installed,
download creates a unique item number for each KBC configuration on a customer
order and each component in a KBC bill that also has a KBC bill of material. It does
this by appending a sequence number to the item number in order to create a unique
item number for the item and its associated data. These items, bills, and routings are
extracted from the KBC configuration files.
SCM field ERP source

Item ID Item number (ITNB in ITMPLN); if KBC, ITNB and a 7-
position sequence number
Item Description Item description (ITDSC in ITMRVA)
Item Type If lead time code (LTCOD in ITEMBL) is M: 0.
(0=manufacture; Otherwise, 1
1=purchase)
Analyst ID Planner (PLANIB in ITEMBL)
Manufacturing Unit of Stocking unit of measure (UNMSR in ITMRVA)
Measure
Selling price Base price (BZANVA from MBBZREP for the system
date) if not 0. Otherwise, Base price (BZANVA in
ITMRVA)
Forecast family ID Forecast family ID (IPPRTF from PPITEM)
Safety stock (A forecast is Sum of the safety stock (SAFTY in ITEMBL) in the
created for the safety stock warehouses (the planning warehouse and all
quantity due {Current date associated demand warehouses) where Include
+ planning fence}) Inventory Balance (ININ in ITEMBL) is 1 (Yes).
Planning Fence (used with Safety stock lead time as defined in the MRP option for
safety stock) warehouse (established on display AMM151) (SFTY in
PLNINF for warehouse):
1 (LT) Item lead time (M or P used by MRP)
2 (Current) 0
3 (Cum Mtl LT) Cum Material LT (CMTLT in ITEMBL)
4 (Cum Mfg LT) Cum Manufacturing LT (CMFLT in
ITEMBL)
Minimum level (used with If order point (ORDPT in ITEMBL) is greater than 0:
safety stock) ORDPT; otherwise: [order point calculated using ERP
logic] safety stock (SAFTY in ITEMBL) + estimated
annual usage (EAANU in ITEMBL) * lead time
(purchase or manufacturing, per lead time code)/active
days per year (in STATI0 in SYSCTL) * (1 + reorder
point tolerance percent (in STATI0 in SYSCTL).
Ordering information
Aggregation period (in If order policy code (ORDP in ITEMPLN) is G and days
days) supply (NODS in ITMPLN) is greater than 0: NODS.
Otherwise, 1
Minimum Lot If order policy code (ORDP in ITMPLN) is D or H and
the fixed order quantity (FXORQ in ITEMBL) is greater
than the minimum (MINQ in ITMPLN): Fixed order
quantity (FXORQ); otherwise, Minimum (MINQ).
Multiple Of Multiple (MULQ in ITMPLN)
Page A-3

Reschedule flag (for future If item reschedule code (ITRC in ITMPLN) is 1 through
use) 4, the reschedule flag is sent. If the item reschedule
code is 0, the code defaults to 1 (no automatic
rescheduling) for purchased and master-level items;
otherwise, 4 (automatic reschedule in and out).
Frozen period (for future Item reschedule frozen zone (RSFZ in ITMPLN)
use)
Manufacturing information
Make Max Lot Maximum quantity (MAXQ in ITMPLN)
Primary Route ID Blank
Phantom type (0=No; If item type (ITTYP in ITMRVLA) is 0 (phantom): 1;
1=Yes) otherwise, 0
Planning bill item (0=No; Planning bill item (IPPLNB from PPITEM)
1=Yes)
Purchasing information
Cost (Purchasing parts If IM tailoring (CSTCD in the STATI0 record in SYSCTL)
only; SCM computes costs is one of the following:
for manufacturing parts) 1 Standard unit cost (STDUC in ITEMBL)
2 Average unit cost (AVCST in ITEMBL)
Neither 1 or 2: last unit cost (LCOST in ITEMBL)
If cost from above is 0: unit cost default (UCDEF in
ITMRVA)
Yield 1 — Shrinkage factor (SHFC in ITMPLN)
Raw Material Type: If LTCOD is P and constrained part (CPAR in ITMPLN)
2 Priority is 1 (Yes): 2; otherwise, 0
1 Ignore
0 Normal
Primary Vendor ID If not blank: Vendor (VNDNR in ITEMBL); otherwise,
Vendor (VNDNR in ITMRVA)
Buyer ID Buyer (BUYNO in ITMRVC)
Buyer Lead Time Purchase review time (LTREV in ITEMBL)
MRP Lead Time (typical) Purchase vendor (LTVEN in ITEMBL) plus Purchase
safety (LTSAF in ITEMBL)
Minimum MRP Lead Time Purchase vendor (LTVEN in ITEMBL)
Dock to Stock Lead Time Purchase adjustment (LTADP in ITEMBL)
User-defined attribute information
Item class Item class (ITCLS from ITEMBL)
Item sales group Item sales group code (B2ADSB from ITMRVA)
User field—Code A User field—Code A (UUCAIB from ITEMBL if not blank;
otherwise, UUCA from ITMRVA)
Page A-4
Item Process (PPIPRC)

If EPDM is active, the item process table is downloaded to enable future SCM support
for multiple item processes as defined in EPDM. Only the current primary item
process, and the associated bill and routing, is currently downloaded for each
standard manufactured item.

Item ID Item ID
Item revision ERP item revision
Revision start date Revision effective-from date
Revision end date Revision effective-to date
Route ID Sequence number of the item process, generated in
download since the ERP item process token contains
packed data that does not translate into ASCII
Description Process description
Primary process 1 Primary
0 Alternate
Process start date Process effective-from date
Process end date Process effective-to date
ERP alternate BOM ID ERP Alternate BOM ID
ERP routing ID ERP Routing ID
ERP Routing version ERP Routing version
Page A-5
Bill of Material (PPIBOM)

If PDM is active, the download sends the bill for each manufactured item from
PSTRUC. If EPDM is active, the download sends the bill from PSTDTL for each item
process sent. For S-numbered items feature/option records, the F/O planning factor
(FOPPF) is multiplied by the quantity per to compute the Quantity Per sent. The bill for
each KBC configuration is sent from TCFOBM.

Parent item ID If not a KBC configuration: Parent item number
If a KBC configuration: Item number and a 7-position
sequence number
Route ID If EPDM is active and not a KBC configuration: the
sequence number of the item process; otherwise, blank
Item ID (Component) If not a KBC configuration: Component item number
sequence number
Quantity Per 1 If not KBC, and the standard batch quantity is
greater than 0: (QTYPR/standard batch quantity);
otherwise: Quantity per unit (QTYPR)
2 If not KBC and a feature/option record: the results of
step 1 (above) times FOPPF
3 If KBC, and the standard batch quantity is greater is
greater than 0: (COQP/standard batch quantity);
otherwise: Quantity per unit (COQP in TCFOBM)
Job Step If REP schedule: 0001; otherwise, Operation where first
used.
Effective From Date If not KBC and Effective from date (EDATM) is not 0:
EDATM; otherwise, 01011901
Effective To Date If not KBC and effective date (EDATO) is 0 and
American: 12312099
If not KBC and effective date (EDATO) is 0 and not
American: 31122099
If not KBC and effective date (EDATO) is not 0: EDATO
If KBC and American: 12312099; otherwise, 31122099
Page A-6
Routing (PPIRTG)
If PDM is active, the routing for each manufactured item is sent from ROUTNG. If
EPDM is active, the routing is sent from RTGOPR for each item process sent. No
routing is sent for a phantom item. For REP items, a one-step (0001) routing is sent
using data from the item line (ITMLIN) records for the item. With PDM active, the item
line for the primary production line in the item balance is used, and if an item has
additional item line records, they are used to send alternate operations. With EPDM
active, the item line for the current primary item process is used. If there are multiple
item lines for the item process, and one is the primary production line in the item
balance, that item line is used for the routing. If none of the lines is the primary
production line, the first item line found is used for the routing.

Item ID If not a KBC configuration: Item number
sequence number.
Route ID If EPDM is active and not a KBC configuration: the
sequence number of the item process; otherwise, blank
Route Priority If PDM is active, and a routing for a REP item alternate
production line, download numbers starting with 1;
otherwise, 0.
Job Step If a REP item: 0001; otherwise, the operation sequence
number
Workcenter If a REP item: the production line from the item line
record used (see the text above the table).
If position 1 of FCPS resource constraint (FCP1) is
asterisk (*): positions 2-6 of FCP1; otherwise, Facility
Batch Size If a REP item, or if time basis code is not C or H: 1;
If time basis code is C:
If batch size in PPROUT is greater than 0: batch
size in PPROUT; otherwise: 1;
If time basis code is H:
If batch size in PPROUT is greater than 0: batch
size in PPROUT; otherwise, if (item) maximum is
greater than 0: maximum; otherwise, if (item)
minimum or multiple is greater than 0: 75 * {“larger
of” minimum or multiple}; otherwise: 100,000.
Setup time in seconds If REP: changeover time + flow time - run time for one
unit multiplied by 3600; otherwise, if prime load code is
2, 3, or 5: Setup time, divided by setup crew size if setup
crew size is greater than 0, divided by facility standard
efficiency, and converted to seconds; otherwise, 0
Run time per batch in If REP: Item rate converted to hours per piece if rate
seconds designator is P and multiplied by 3600; otherwise, if
prime load code is 1 or 3: run machine hours converted
to hours per piece or lot, based on the time basis code
divided by facility standard efficiency, and multiplied by
3600; otherwise, if prime load code is 4 or 5: run labor
hours converted to hours per piece or lot based on the
time basis code, divided by standard efficiency and
multiplied by 3600
Yield If REP: 1; otherwise, current operation yield
Page A-7

Idling time per batch in If REP: 0; otherwise, the greater of the facility output
seconds buffer hours or operation output buffer hours multiplied
by 3600.
Setup family Routing family (RTGF from PPROUT)
Minor setup family Minor family (MINF from PPROUT)
Minor setup time in Minor setup time in minutes (MINS from PPROUT) * 60
seconds
Cleanup time in seconds Cleanup time in minutes (CLTM from PPROUT) * 60
Step description If REP: Facility (production line) description; otherwise,
operation description
Tool ID If REP: blank; otherwise, tool number and FCPS
resource information if present
Page A-8
Workcenter (PPIWKC)
If PDM is active, the facilities are sent from the WRKCTR file. If EPDM is active, the
facilities are sent from FACMST.

Workcenter ID Facility ID
Workcenter description Facility description
Units Largest of the desired capacities (shift 1, shift 2, or shift
3)
Max planned utilization If the sum of the maximum capacities for the three shifts
is not greater than zero: .95; otherwise, if the sum of the
desired capacities divided by the sum of the maximum
capacities is not greater than 1: the result; otherwise, 1.
Calendar name Production calendar name
Dummy flag If prime load code is 0 (no load): 1; otherwise, if the time
0 Normal basis code from a routing operation for this facility is C:
1 Ignore 2; otherwise, 0
2 Outside processing
Family Facility group
Forced queue time in If REP production line: 0; otherwise, the standard queue
seconds (for non-drums) time in days (STDQT) multiplied by the daily scheduling
capacity in hours multiplied by 3600.
Typical queue time in If REP production line: 0; otherwise, the standard queue
seconds (for drums) time in days (STDQT) multiplied by the daily scheduling
capacity in hours multiplied by 3600.
Minimum queue time in If REP production line: 0; otherwise, input buffer hours
seconds (for drums) (BUFI) multiplied by 3600.
Overtime rate If the prime load code is 2: the current setup labor rate
multiplied by 1.5; if the prime load code is 4 or 5: the
current run labor rate multiplied by 1.5; otherwise, 0
Page A-9
Setup Sequence (PPISEQ)

Desired scheduling sequence of minor setup families in a major setup family, and the
associated setup times are sent from the user-controlled file PPSEQS. See Appendix
D for further information.

Major setup family Routing family (SSRTGF in PPSEQS)
Previous minor setup Previous minor family (SSMNFP in PPSEQS)
family
Minor setup family Minor family (SSMINF in PPSEQS)
Minor setup time in Minor setup time in minutes (SSMINS in PPSEQS) * 60
seconds
Sequence or Edge number Routing priority (SSRTGP in PPSEQS)
Page A-10
Forecast (PPIFCS)
Forecasts are sent for the following types of records in the requirements file. Most
forecast records are retained until the end of a month, for use by SCM forecast
consumption, which works by calendar month. The last four types of records,
however, have corresponding sales records, as they represent demand to be planned
“in addition to normal consumption of forecast by sales”. These records – and the
matching sales records – are dropped from the requirements file following normal
MRP rules.
Forecast type Source Origination Comments

Forecasts (from FCST) RQSOR=5 RQORG=1
User-entered forecasts RQSOR=5 RQORG=0
from MRP
User-propagated forecasts RQSOR=1 RQORG=0
User forecasts from user RQSOR=5 RQORG=10 Order ID-RQCID is blank
forecast file
User forecasts from user RQSOR=5 RQORG=20/+ Order ID-RQCID is blank
programs
Intersite orders, planned RQSOR=5 RQORG=8
from ISL
Intersite orders, customer RQSOR=6,7 RQORG=0 Order ID-RQCID is
orders from ISL present
User-entered requirements RQSOR=6,7 RQORG=0 Order ID-RQCID is blank
from MRP
User-propagated RQSOR=2 RQORG=0
requirements
User forecasts, from User RQSOR=5 RQORG=10 Order ID-RQCID is blank
Forecast file

Item ID Item number
Forecast ID FCST + YYYYMMDD (forecast date/RQDUD in
REQMTS)
Item family Family ID (FMID from PPITEM)
Forecast date Forecast date (RQDUD in REQMTS)
Forecast quantity Forecast quantity (RQQTY in REQMTS)
Page A-11
Sales (PPICOM)
Sales are sent for the following types of records in the requirements file. Customer
orders from COM, etc. are planned only if they are not “held” using a COM hold code
filtered from planning in MRP.
Sales are also sent for shipped customer orders promised in the current month, from
the COM history files and the user customer order file, for use by SCM forecast
consumption, which works by calendar month. At the beginning of a month, sales are
also sent for customer orders shipped on or after 4 days before the last download, to
ensure accurate SCM drum scheduling in resynch and performance analysis. These
sales records are sent directly from these files, and ERP source is not given for these.
Order type Source Origination Comments

Customer orders from RQSOR=6,7 RQORG=0 Order ID-RQCID is
COM, etc. present
Expected customer orders RQSOR=6,7 RQORG=11-15 Order ID-RQCID is
from EC present
User customer orders, from RQSOR=7 RQORG=10 OrderID-RQCID is
User Forecast files present
User customer orders from RQSOR=6,7 RQORG=20+ Order ID-RQCID is
user programs present
Intersite orders, planned RQSOR=7 RQORG=8
Intersite orders, open RQSOR=6,7 RQORG=0 Order ID-RQCID is
present, and an intersite
order exists
User-entered requirements RQSOR=6,7 RQORG=0
from MRP
User-propagated RQSOR=2 RQORG=0
requirements
Page A-12

Item ID If not a KBC configuration: Item number. If a KBC
configuration: Item number and a 7-position sequence
number.
Promise date In all cases: required due date (RQDUD in REQMTS).
If a CO is from COM, etc., this date is loaded as follows:
If Order board matching is Yes and CTP was used to

promise order: Original manufacturing due date
(ADAAN7 in MBADREP)
If Order board matching is Yes and CTP was not

used, or order was later changed: Latest request
date (ADBJDT in MBADREP) minus Ship lead time
If Order board matching is No and Send request date

is No and CO has been scheduled by SCM: Original
manufacturing due date (ADAAN7)

is No and CO has not been scheduled by SCM:
Latest request date (ADBJDT) minus Ship lead time;

is Yes: Latest request date (ADBJDT) minus ship
lead time.
Order quantity Required quantity (RQDUD in REQMTS)
Order ID Company (RQCONO) + Order ID (RQCID) + Release
(RQRLNO) + Kit release (RQKTRL)
Line number Line item sequence (RQLNSQ)
Customer ID If a CO: Customer number in Quote/order header
Selling Price If a CO: Net unit selling price include order-level fixed
and variable trade discounts; otherwise, base price
(BZANVA from MBBZREP for the system date) if not 0.
Otherwise, Base price (BZANVA in ITMRVA)
Requirement sequence RQSEQ in REQMTS for use in upload
number
Page A-13
Inventory (PPIINV)
On-hand inventory is sent from ITEMBL. If the non-nettable enhancement (SH61773)
is active, non-nettable inventory is excluded. On-hand inventory is sent for items other
than KBC configurations. Once a KBC configuration is built, it should be received and
shipped, as the configuration cannot be identified in stock. The customer order shows
a demand for the item number including the 7-position sequence number and the on-
hand (supply) shows the base item number without the sequence number.

Item ID Item number
On-hand quantity The sum of the on-hand quantity (MOHTQ in ITEMBL)
in the warehouses (planning and all associated demand
warehouses) with the Include Inventory balance (ININ in
ITEMBL) of 1 (Yes). If non-nettable is activated, the non-
nettable quantity (totaled in planning in UUQ1IB in
ITEMBL) is subtracted.
Page A-14
Workorder Heading (PPIMOM)

All manufacturing orders and REP schedules (from MOMAST) with order status
(OSTAT) of 00 through 40 or 50 and an open quantity are sent.
If XA Paperless (PLMC) Manufacturing Data Collection and Communications

(MDCC) is running, and a manufacturing order or one or more of its operations are
held, the manufacturing order header is sent, so another order is not planned, but no
component allocations are sent for the order, and operations are sent only if the order
is not held and there are active operations before the first held operation.

Item ID If not a KBC configuration: Item number. If a KBC
number.
Workorder type If a created order in MOMAST: R
R Released workorder
(for future use)
Workorder ID Manufacturing order, or REP schedule ID, and if an
unreleased REP schedule, S in the first position is
replaced with U.
Workorder status (one First position of order status (OSTAT)
character)
Original quantity The order quantity (ORQTY) plus the deviation quantity
(QTDEV) minus the split order quantity (QTSPL) divided
by the cumulative yield of all operations (CUMCY)
Quantity finished Quantity received (QTYRC) divided by the cumulative
yield of all operations (CUMCY)
Quantity scrapped Scrap quantity (QTSCP)
Release date The scheduled start date (SSTDT)
Due date Due date (ODUDT)
Reschedule flag (0-5) (for Order reschedule code (ORRC)
future use)
Page A-15
Workorder Allocation (PPIMOD)

For workorders sent from MOMAST, component allocations not yet issued (quantity
required is greater than quantity issued) are sent from MODATA. For unreleased REP
schedules, download builds these records from the bill of material for the item if PDM
is active, and if EPDM is active, the bill of material for the item process in MOMAST.

(MDCC) is running, and a manufacturing order or one of its operations are held, the
manufacturing order header is sent, so another order is not planned, but no
component allocations are sent for the order.

Workorder ID Manufacturing order or REP schedule ID, and if an
replaced with U.
Child item ID If not a KBC configuration: Item number. If a KBC
number.
Job Step If REP schedule: 0001; otherwise, Operation where first
used (OPRWU).
Sequence number Sequence number (SEQNM)
Quantity required Quantity required (QTREQ)
Quantity issued Quantity issued to date (ISQTY)
Page A-16
Workorder Routing (PPIMOR)

For workorders sent from MOMAST, active operations (OPSTC is not 00) are sent
from MOROUT. For REP schedules, a one-step (0001) routing based on data in
MOMAST.

(MDCC) is running, and a manufacturing order or one or more of its operations are
held, the manufacturing order header is sent, so another order is not planned, but no
component allocations are sent for the order, and operations are sent only if the order
is not held and there are active operations before the first held operation.

Workorder ID Manufacturing order or REP schedule ID, and if an
replaced with U.
Job step If REP: 0001; otherwise, the operation sequence
number
Job step status For open manufacturing orders if OPSTC in MOROUT
is greater than 30: C; otherwise, the first position of
OPSTC in MOROUT. For unreleased REP schedules:
1; for released REP schedules: 3
Workcenter REP: PLINE from MOMAST; otherwise, if the actual
facility is not blank: the actual facility (AWRKC); if the
actual facility is blank: the standard facility (WKCTR)
Batch size If a REP item, or if time basis code is not C or H: 1;
If time basis code is C: if batch size in PPROUT is
greater than 0: batch size in PPROUT; otherwise: 1;
If time basis code is H: if batch size in PPROUT is
greater than 0: batch size in PPROUT; otherwise: order
quantity ([original order qty + qty deviation – qty in splits]
/ cumulative yield)
Setup time in seconds If REP: changeover time + flow time - run time for one
unit multiplied by 3600; otherwise, if prime load code is
2, 3, or 5: Setup time, divided by setup crew size if setup
crew size is greater than 0, divided by facility standard
efficiency, and converted to seconds; otherwise, 0
Run time per batch in If REP: Item rate converted to hours per piece if rate
seconds designator is P and multiplied by 3600; otherwise, if
prime load code is 1 or 3: run machine hours converted
to hours per piece or lot, based on the time basis code
divided by facility standard efficiency, and multiplied by
3600; otherwise, if prime load code is 4 or 5: run labor
hours converted to hours per piece or lot based on the
time basis code, divided by standard efficiency and
multiplied by 3600
Yield If REP: 1; otherwise, current operation yield
Quantity good If time basis code is C: op quantity calculated complete
based on elapsed time; otherwwise, quantity complete
to date, adjusted for splits, if required
Quantity bad Quantity scrapped to date
Page A-17

Idling time per batch in If REP: 0; otherwise, the greater of the facility output
seconds buffer hours or operation output buffer hours multiplied
by 3600.
Setup family Routing family (RTGF from PPROUT)
Minor setup family Minor family (MINF from PPROUT)
Minor setup time in Minor setup time in minutes (MINS from PPROUT) * 60
seconds
Cleanup time in seconds Cleanup time in minutes (CLTM from PPROUT) * 60
Item ID If not a KBC configuration: Item number; if a KBC
configuration item: Item number plus a 7-position
sequence number
Step description If REP: Facility (production line) description; otherwise,
operation description
Tool ID If REP: blank; otherwise, tool number and FCPS
resource information if present
Page A-18
Jobs in Progress (PPIJIP)

Jobs In Progress (JIP) data for partially completed operations allows the planning
engine to more accurately schedule both of the following:
• Long running production operations
• Outside operations.
In either case, “work” may be proceeding, but “quantity complete” is not increasing, so
the engine would, without this data, schedule more time than is required to complete
the operation. JIP data is in addition to the basic data sent for all order operations in
the Workorder Routing.
The user specifies a Long Operation Minimum Hours (default = 8) option in download
to define operations eligible for JIP processing. A JIP record is sent only if the
operation is in progress, has a positive quantity remaining, and the setup time or run
time per batch is equal to or greater than the Minimum Hours specified.
For time basis codes except C, setup and runtime remaining are calculated based on
hours reported to date. This assumes the job is performing according to standards,
adjusted for standard efficiency.
For time basis code C, setup and runtime remaining are calculated based on the time
elapsed since the previous operation completion (or the job start date, if this is the first
operation). This assumes the job is progressing as scheduled. No reporting is
expected until the job is received back from the vendor.

Work order ID Manufacturing order or REP schedule ID, and if an
replaced with U.
Job step Operation sequence number
Workcenter If actual facility is not blank: the actual facility (AWRKC);
otherwise, the standard facility (WKCTR)
Workcenter unit A sequence number generated in download. For normal
facilities, download sends no more JIP records than
units in the facility, and sends the records with the latest
transaction date first. See “Workcenter (PPIWKC)” for
more information. For outside processing facilities (time
basis code C—see Dummy Flag in the Workcenter file),
all JIP records are sent.
Quantity in progress If time basis code is not C or H: 1;
If order quantity remaining (order quantity + quantity
deviation – quantity in splits) is less than or equal to
batch size: order quantity remaining;
If time basis code is H: {lesser of: batch size and
(operation quantity remaining = order quantity
remaining – operation quantity complete – operation
quantity scrapped)};
For time basis code C: {lesser of: batch size and
(operation quantity remaining = order quantity
remaining – operation quantity calculated complete
based on elapsed time)}
Page A-19

Setup time remaining (on If time basis code is C, standard setup time minus
the operation) elapsed time to date; otherwise, standard setup time
minus actual setup time to date, factored for standard
efficiency and standard setup crew size.
Run time remaining (on the Standard run time per batch minus run hours calculated
quantity in progress) spent on the quantity in progress, based on elapsed
time (for time basis code C), or run time reported (all
others).
Item ID If not a KBC configured item: Item number; if a KBC
configured item: Item number plus a 7-position
sequence number
Page A-20
Purchase (PPIPUR)
All open purchase order line items (POITEM and POBLKT), purchase requisitions
(REQHDF), and open intersite orders (XFRORD) are sent.

Item ID Item number
Order Type If open purchase order from POITEM or POBLKT,
R Released order purchase requisition from REQHDF, or open intersite
(for future use) order (IO) from XFRORD: R
Order ID If open POITEM: PO number

If open POBLKT: PO number and release from POBLKT
If purchase requisition: Requisition number
If open intersite order: IO number
Line number If open purchase order: line item sequence; otherwise, 1
Due Date If open purchase order, intersite order, or purchase
requisition: Due date to stock
Order Quantity If open purchase order: order quantity plus deviation
quantity minus the quantity received to stock
If purchase requisition: the order quantity
If an open intersite order: Order quantity minus the
quantity received
Reschedule flag (0-5) (for For POITEM and POBLKT: Order reschedule code
future use) (ORRC in POITEM)
For REQHDF: 1 (no rescheduling). Not supported for
requisitions
For XFRORD: 1 (no rescheduling). Not supported for
intersite orders
Vendor ID For purchase orders and requisitions: the vendor from
the purchase order or requisition; otherwise, blank
Buyer ID For purchase orders and requisitions: the buyer from
the purchase order or requisition; otherwise, blank
Page A-21
Warehouse Control (PPIPLN)

SCM uses the MRP warehouse-level data. Most of this data is stored in either
MRPCTL or PLNINF.

Location ID Planning warehouse (PLWH)
Site ID Site for this warehouse (STID)
Current date MRP current date (plan as of this date {CUDT})
Release date Flag order for release if the order start date is on or
before this date (RLDT)
Start date Horizon start date: the earliest date to use for planning
(STDT)
Calendar end date The last workday in the 5-year calendar (CLNE)
Cancel Reschedule orders to be canceled to last month date if
this code is 1 (CANC)
Last month date Calendar end date less one month. For use with Cancel
(CLNM)
Reschedule frozen zone Warehouse rescheduling frozen zone (RSFZ)
Demands to track The number of demand records to create in order to
track a supply (PEGC)
Track on hand Create demand records for on-hand if this code is 1
(DSQH)
Page A-22
Page B-1
Data uploaded to ERP
Appendix B. Data uploaded to ERP

This table lists the ERP data files on the System i updated during upload after SCM
planning.
ERP file name Contents/Purpose See page...

Requirements (REQMTS) MRP file with planning results B-1
Planned orders (PLNORD) MRP file with planning results B-1
Demand reference (DMDREF) MRP file with planning results B-1
Reschedule activity work (RACWRK) MRP file with planning results B-2
Customer order upload (PPCOWK) Updates made to customer order B-2
dates
Customer order line item release Updated COM customer order dates B-3
(MBADREP)
User customer order (OLCSBL) Updated user customer order dates B-3
Manufacturing Orders (MOMAST, Updated priorities and schedule dates B-4
MOROUT, and MODATA)
REP schedules (MOMAST, MOROUT, Updated schedule dates B-4
and MODATA)
MRP Requirements (REQMTS)

Upload writes two kinds of records from SCM planning to this file:
• Unconsumed forecasts generated during forecast consumption. See “Forecast
consumption” for more information.
• Component demand for planned orders generated by the engine during planning.
MRP Planned orders (PLNORD)

Upload writes a record in this file for each open and planned supply order as
scheduled in SCM planning. As the engine reschedules all open manufacturing orders
and REP schedules to meet demand, those records will have no expedite or defer
(33, 41, or 62) messages. The reschedule activity work file shows all the rescheduled
manufacturing orders and REP schedules, and all supply orders flagged with a
Cancel (72) exception.
MRP Demand reference (DMDREF)

If specified in the MRP Planning Run Execution Options, this file is loaded with the
data to track supply to five kinds of demand:
• Sales
• Unconsumed forecast
• Safety stock
• Supply order
• Negative on hand.
Page B-2
MRP Reschedule activity work (RACWRK)

Upload writes a record to this file for each open order that:
• Was rescheduled during planning to meet demand
• Is not needed to meet demand, and thus was flagged with a Cancel (72)
exception.
Customer order update (PPCOWK)

This file contains customer order rescheduling information from planning:
• There is a record in the file if the scheduled completion date (supply order due
date) from planning does not match the current manufacturing due date in the
customer order.
• If there is a Previous due date, the customer order (current) Manufacturing due
date was updated, as specified in the UpdateCOMCODueDate or
UpdateUserCODates upload parameters in the iSeriesIntegration.ini file.
• If Promise date and Previous promise date have dates, the customer order
(current) Promise date was updated, as specified in the
UpdateCOMCOPromiseDate and UpdateUserCODates upload parameters in the
iSeriesIntegration.ini file.
ERP field Source/contents

Warehouse (Key)
Company number (Key)
Order number (Key)
Order release number (Key)
Item sequence number (Key)
Kit release number (Key)
Item number Item number
Due (ship) date Scheduled in planning
Previous due date If present, manufacturing due date in customer order
before update from planning
Promise (deliver) date Calculated in upload (due date plus ship lead time)
Previous promise date If present, promise date in customer order before update
from planning
Page B-3
COM customer order line item release (MBADREP)

The first two fields are updated if the line item release was not previously scheduled
by SCM, either using CTP during order entry or in a previous planning run. The
second field is set to 1/Yes either during CTP or during update from planning. The
next two fields are updated as specified in the upload parameters in the
iSeriesIntegration.ini file.

Original manufacturing due If Scheduled by APS is 0 (No): supply order due date
date (ADAAN7)
Scheduled by APS (ADZ08F) If 0 (No): 1 (Yes)
Manufacturing due date If supply order due date is not equal to this field, and:
(ADAKDT) UpdateCOMCODueDate is 2 (Update every time) -or-
UpdateCOMCODueDate is 1 (Update only the first time)
and Scheduled by APS is 0 (No): Supply order due date
Promise date (ADBIDT) If (supply order due date plus ship lead time) is not equal
to this field, and:
UpdateCOMCOPromiseDate is 2 (Update every time) -
or-
UpdateCOMCOPromiseDate is 1 (Update only the first
time) and Scheduled by APS is 0 (No): Supply order due
date plus ship lead time
Change date (ADAMDT) If any field above updated: System date
Change time (ADACTM) If any field above updated: System time
User customer order (OLCSBL)

The first two fields are updated if the line item release was not scheduled by SCM in a
previous planning run. The next two fields are updated as specified in the upload
parameters in the iSeriesIntegration.ini file.

Original due date (BLODDT) If Scheduled by APS is 0 (No): supply order due date
Scheduled by APS (BLPDCF) If 0 (No): 1 (Yes)
Manufacturing due date If supply order due date is not equal to this field, and
(BLCDDT) UpdateUserCODates is 1 (Update using the COM CO
update options), and:
UpdateCOMCODueDate is 2 (Update every time) -or-
UpdateCOMCODueDate is 1 (Update only the first time)
and Scheduled by APS is 0 (No): Supply order due date
Promise date (BLPDCT) If (supply order due date plus ship lead time) is not equal
to this field, and UpdateUserCODates is 1 (Update using
the COM CO update options), and:
UpdateCOMCOPromiseDate is 2 (Update every time) -
or-
UpdateCOMCOPromiseDate is 1 (Update only the first
time) and Scheduled by APS is 0 (No): Supply order due
date plus ship lead time
Change date (CHGDT) If any field above updated: System date
Change time (CHGTM) If any field above updated: System time
Page B-4
Manufacturing Order/REP Schedule Master (MOMAST)

Existing manufacturing orders and REP schedules are updated in upload after
planning, if the upload parameter UpdateOpenWorkOrders in the
iSeriesIntegration.ini file is 1 (Update). Values below are also updated in new
manufacturing orders as orders planned by SCM are created on the System i, using
AutoCreate in upload, or MRP or OBPM after upload.
MOROUT and MODATA records for REP schedules are updated using existing REP
function, based on the schedule date. Updates for MOROUT and MODATA records
for manufacturing orders are shown in the next tables.

Generated by APS (GAPS) If not labor complete (status < 50):
1 (planned by APS)
Management priority If a manufacturing order and not labor complete (status
(MPROR) < 50): * (planned by APS)
Priority (PRVAL) If a manufacturing order and flagged for cancel
(exception 72): 9999999; otherwise: 0
Scheduled start date (SSTDT) If not started (status < 40):
SCM release date (POSTD in PLNORD)
Calculated completion date If not labor complete (status < 50):
(OCODT) last operation scheduled completion date (SCODT)
Due date (ODUDT) SCM due date (PODUD in PLNORD)
Manufacturing Order Routing (MOROUT)

Manufacturing order routings are updated in upload after planning, if the upload
parameter UpdateOpenWorkOrders in the iSeriesIntegration.ini file is 1 (Update).
They are also updated as a manufacturing order planned by SCM is created on the System i,
using AutoCreate in upload, or MRP or OBPM after upload.
As “drum” – or constrained – facilities are scheduled differently by SCM than “non-

drums”, different values are used for operation priority and scheduled start and
scheduled completion, as shown below.

Generated by APS (GAPS) 1 (planned by APS / SCM)
Management priority * (planned by APS / SCM)
(MPROR)
Priority (PRVAL) If order not started (status < 40) and flagged for cancel
(exception 72): 9999999;
If facility is a drum: Using Start date and time from drum
schedule; Positions 1 and 2 = last digits of year
(from date: 01 – 99), Positions 3 – 5 = Julian date
(from date: 001 – 366), Positions 6 and 7 = time slot
(from time, in minutes / 15: 01 – 96)
If not a drum: Percent buffer remaining [Buffer remaining
/ Buffer total] from make schedule
Page B-5

Scheduled start date (SSTDT) If operation is not started (status < 30):
If facility is a drum: Start date from drum schedule;
If not a drum: Don’t Do Before date from make schedule;
If before MRP current date and
AdjustOpStartForCurrentDate in
iSeriesIntegration.ini is 1: MRP current date;
If before the previous operation start date and
AdjustOpStartForPrevOpStart in
iSeriesIntegration.ini is 1: Previous operation start
date
Scheduled completion date If operation is not complete (status < 40):
(SCODT) If facility is a drum:
If not split: End date from drum schedule;
If split: Scheduled start date plus run time for the
remaining operation quantity;
If before the previous operation completion date and
AdjustOpComplForPrevOpCompl in
iSeriesIntegration.ini is 1: Previous operation
completion date.
If not a drum: Scheduled start date plus run time for
the remaining operation quantity;
If before the previous operation completion date and
AdjustOpComplForPrevOpCompl in
iSeriesIntegration.ini is 1: Previous operation
completion date
Actual work center (AWRKC) If operation is not started (status < 30) and user has
offloaded the operation to another work center: the
chosen work center
Manufacturing Order Component (MODATA)

Manufacturing order components are updated after planning only if the component is
not completely issued (quantity required is greater than quantity issued to date) and
the required date changed.

Required date (REQDT) If operation where used (OPWRU) is not an active
operation, and the order is not started (status = 10),
and the required date does not equal the order
scheduled start date: SSTDT from MOMAST;
If operation where used is an active operation, and the
operation is not started (status < 30), and the
required date does not equal the operation scheduled
start date: SSTDT from MOROUT.
Page B-6
Page C-1
Download error messages
Appendix C. Download error messages

• Items
Error number Error text

AMM0104 (W) Safety stock quantity was sent with a loss of data
• Bills of materials
Error
number Error text Comments
AMM0111 (E) Calculated quantity per must be This component record is
greater than zero. not downloaded.
AMM0112 (W) Calculated quantity per was sent
with a loss of data.
AMM0113 (E) Operation sequence contains non- The Planning Engine only
numeric characters. works with numeric
operation sequence
numbers as noted below
in Routings.
AMM0114 (W) Operation where used is not found
in the routing file.
AMM0115 (E) Component bill of material is not Refers to KBC items.
referenced in a parent bill of material.
• Routings
Error
AMM0116 (E) Production facility is not found.
AMM0113 (E) Operation sequence contains non- The Planning Engine only
numeric characters. works with numeric
operation sequence
numbers. This operation
was not downloaded.
AMM0117 (E) Routing parent number is not found Refers to KBC items.
in the bill of material.
AMM0121 (E) No routing was sent for item With PDM active, an item
******************** because no item line line is required to send a
exists for primary production line *****. routing.
AMM0122 (E) A primary item process for item With EPDM active, an
******************** was not sent item line is required to
because no item line record exists for send an item process.
it.
Page C-2
Download error messages
• Production Facilities
Error
AMM0100 (I) Maximum capacity is zero. Maximum utilization was set to
95%.
AMM0101 (W) Overtime rate was sent with a
loss of data
AMM0102 (I) Maximum capacity exceeds Maximum utilization was set to
100%. 100%.
• Inventories
Error number Error text

AMM0103 (W) On-hand quantity was sent with a loss of data.
• Manufacturing orders
Error
AMM0113 (E) Operation sequence contains The Planning Engine only
non-numeric characters. works with numeric operation
sequence numbers. This
operation was not
downloaded.
AMM0123 (E) Component has the same item The component was not
number as the parent in MOMAST. downloaded.
• REP schedules
Error
AMM0110 (E) Item line record does not exist. The unreleased REP
schedule was not
downloaded.
AMM0120 (W) Item line record needs review. The unreleased REP
schedule was downloaded,
but the item line must be
valid before the schedule
can be released.
AMM0123 (E) Component has the same item The component was not
number as the parent in MOMAST. downloaded.
Page D-1
Additional SCM Data
Appendix D. Additional SCM Data

APS Integration provides maintenance of the following SCM data that is not used
elsewhere in XA:
• Two demand files allow sales and forecast data from outside XA to
be used in SCM planning.
- User customer orders
- User forecasts
• An Item additional planning attributes file provides controls for SCM forecast
consumption.
• Two operation scheduling files provide additional data for SCM scheduling and
setup savings.
- Routing operation
- Setup sequence
You can maintain the first two files from transactions you supply in a file.
You can maintain the other three files any way you want, as APS Integration does not
provide any user interface to these files.
The following section describes how you maintain these files. In all cases, you are
responsible for the accuracy of the information in these files. APS Integration
performs basic edits on the transactions used to maintain the first two files, as
discussed below, but you must keep the files accurate, especially the user customer
orders, which must be updated in synch with inventory, to keep planning in synch.
User Customer Orders and Forecasts..................................................................... D-1
User-controlled files................................................................................................. D-5
User Customer Orders and Forecasts

The User Customer Orders file allows you to use customer sales demand from a
source other than COM (or other XA products that populate the COM
files) customer orders in SCM planning. The User Forecast file allows you to use
forecast demand from a source other than FCST forecasts in SCM planning.
To provide data for these files, you:

1. Supply add, change, and delete transactions in offline maintenance files,
formatted as defined below
2. Process the maintenance transactions by entering the commands defined below
for each file.
Page D-2
Additional SCM Data
User Customer Orders

User Customer Orders are stored in the Customer order backlog file (OLCSBL).
Maintenance is performed using transactions supplied in the following record format:
Offline file name (default) OLCSBO (Customer order backlog offline load)
Record length 95
Field Dec.
Field description Field name type From To pos.
Transaction type
[1=Add, 2=Change, 3=Delete] BOTRTP A 1 1
Company number BOCONO S 2 3
Customer order BOCORD A 4 10
Item sequence number BOITSQ S 11 17
Warehouse BOHOUS A 18 20
Item number BOITNB A 21 35
Unshipped Order Quantity BOBQTY S 36 45 3
Shipped Quantity BOSQTY S 46 55 3
Request Date BOBDAT S 56 61
Promise Date BOPRMD S 62 67
Selling price BOSLPR P 68 87 8
Customer number BOCUSN S 88 95
Records in the file must:
• Be uniquely identified by company number, customer order number, and item

sequence number, and
• Have a valid warehouse, item number, request date, and quantity. One record
may have an unshipped quantity, a shipped quantity, or both.
Considerations for maintaining this file for use with SCM
You must maintain the unshipped quantity in this file in synch with inventory shipped
for the order, otherwise planning will replan the demand in error.
SCM requires shipped customer orders to be downloaded at least once after they are
shipped, for accurate drum schedules and performance analysis, so you should for at
least one planning cycle, leave the record in the file with the quantity shipped.
If you are consuming forecast in SCM, both shipped customer orders and forecasts
for the entire month should be downloaded throughout the month for best results.
Page D-3
Additional SCM Data
User Forecasts
APS Integration uses the User Forecast file only if XA FCST is not installed and
interfacing to MRP. If XA FCST is interfacing to MRP, and you have user forecasts,
you must load those directly into the MRP REQMTS file, either interactively using
MRP Maintain Forecast (Menu AMMM10, Option 1), or by a user program (See
Chapter 3, “Managing APS Integration“).
User Forecasts are stored in the Period forecast file (OLPFCS).
Maintenance is performed using transactions supplied in the following record format:

Offline file name (default) OLOFCS (Period forecast offline load)
Record length 32
Field Dec.
Field description Field name type From To pos.
Transaction type OFTRTP A 1 1
[1=Add, 2=Change, 3=Delete]
Warehouse OFHOUS A 2 4
Item number OFITNB A 5 19
Period Beginning Date OFPRBD S 20 25 0
Forecast Quantity OFFQTY S 26 32 0
Records in the file must:

• Be uniquely identified by warehouse, item number and period beginning date
• Have a quantity.
If you are consuming forecast in SCM, both shipped customer orders and forecasts
for the entire month should be downloaded throughout the month for best results.
APS Integration during planning deletes records in this file for months earlier than the
current month, as they are not used by SCM.
Page D-4
Additional SCM Data
Processing maintenance transactions

To process the offline maintenance transactions, enter the following commands on an System i
command line:
• MNTAPSUCO, to Maintain User Customer Orders
• MNTAPSUFC, to Maintain User Forecasts.
The following panel appears:
Date **/**/** ************* Offline Maintenance Options AMVPOF
Select one of the following .. . A 1. Edit only

2. Edit and update
Offline file name . . . . . aaaaaaaA10
Offline file library name . . . aaaaaaaA10
Select option for update . . . A 0. Retain all offline records
1. Retain only error records
2. Delete offline file
F3=Exit
What to do
Type in the information required and press Enter. Either error messages appear, or
the requested action is performed and you are returned to the command line.
Function keys
F3=Exit returns you to the command line without performing an action.
Fields
Select one of the following. Type a number that indicates the type of maintenance
you want to perform.
1 Edit only
2 Edit and update.
Offline file name. Type the name of the file that has the offline load transactions.
Offline file library name. Type the library name in which the offline file resides.
Page D-5
Additional SCM Data
Select option for update. Type a number that indicates how you want to handle the
records after the file is processed.
0 Retain all offline records
1 Retain only error records
2 Delete offline file
What reports are printed
An edit list is always printed.
If update was selected, an audit list is also printed.
User-controlled files
You maintain these three files in any way you choose. For example, you can:
• Use the System i Data File Utility (DFU)
• Use the XA DSPFILE tool
• Use the XA Integrator
• Write a user program.
Item (PPITEM)
This file provides three additional item attributes used in SCM forecast consumption.
Download generates a record in this file for each item planned. You enter / maintain
the attributes where required.
Field Explanation
Warehouse (WHID) (Key)
Item number (ITNB) (Key)
Family ID (FMID) Applies to forecasts for an item:
Blank (default) Consume forecast only by customer orders
directly for this item
FULL Consume forecast by any customer order
that uses the item, either parent or component
FamilyName Consume forecast by any customer order for
an item in this forecast family.
Forecast family ID (PRTF) Applies to sales of an item:

Blank (default) Customer orders for this item consume all
forecasts for this item
FamilyName Customer orders for this item consume only
forecasts for this forecast family
Planning bill item (PLNB) A planning bill item:

0 (default) No
1 Yes
Page D-6
Additional SCM Data
Routing operation (PPROUT)

This file provides five additional routing operation attributes, for both standard routings
and manufacturing order routings, used in SCM scheduling and setup savings. See
the SCM documentation for further information. You enter/maintain the entire record.
Field Explanation
Item number (ITNB) (Key)
Operation sequence number (Key)
(OPSQ)
Batch size, 3 decimals (BTSZ) The number of units run at once. Used only for operations
with time basis code of C or H
Routing family ID (RTGF) Major setup family
Minor family ID (MINF) Minor setup family
Minor setup time in minutes, 2 Setup time if the operation follows an operation in the
decimals (MINS) same major setup family but a different minor setup family
Cleanup time in minutes, 2 Time, after running the operation, required for the facility to
decimals (CLTM) be ready for the next operation (setup or run).
Setup sequence (PPSEQS)

This file defines the desired scheduling sequence of minor setup families in a major
setup family, and the associated setup times. See the SCM documentation for further
information. You enter/maintain the entire record.
Field Explanation
Routing family (RTGF) (Key) Major setup family
Previous minor family (MNFP) (Key) Previous minor setup family
Minor family (MINF) (Key) Current minor setup family
Minor setup time in minutes, 2 Setup time when an operation in the Current minor setup
decimals (MINS) family follows an operation in the same Major setup family
and the Previous minor setup family.
Routing priority (RTGP) Desired sequence to run the minor family within the major
family
Page E-1
If APS Bridge is Running
Appendix E. If APS Bridge is Running

If you are currently running the APS Bridge with SCM Release 6.0, here are the key
differences between APS Bridge and APS Integration, and what you must do to run
APS Integration with SCM Release 6.1.
Differences between APS Bridge and APS Integration ............................................E-1
Actions you must take ..............................................................................................E-3
Differences between APS Bridge and APS Integration

APS Integration includes MRP, as described in Chapter 1 and Chapter 3, and the plan
is loaded into the MRP files during planning, so MRP screens and reports can be
used, giving the following benefits over the APS Bridge:
• After planning, either MRP or Order Based Production Management (OBPM) can
be used to review and release planned orders and act on other exception
messages.
• MRP options are available to manage item demand, such as control whether
customer orders are used in planning, and enter or propagate item forecasts and/
or requirements.
• SCM uses the MRP Current Date as the planning date, allowing you to plan, for
example, as of the next workday.
• All items planned by MRP (order policy code not B or C) are now planned by APS/
SCM; the item Planned by code is no longer used.
• APS Integration interfaces with all XA applications that interface with MRP
(except Cameleon and MPSP).
Purchased items are now planned on the engine in stocking unit of measure (as they
are in MRP). For purchased items, purchase unit of measure and purchase
conversion factor are not sent to the engine, and item minimum and multiple are sent
in stocking unit of measure.
APS Bridge Putback transaction tailoring is not used. The item warehouse
manufacture and purchase auto release codes can control by item, whether
manufacturing, purchase and intersite orders flagged for release during planning are
created automatically after planning. See “Uploading to ERP”.
Load/download and Putback/upload are not initiated from the System i, but from the
synch engine planning process. Intermediate download and upload datafiles on the
PC are now optional. SQL is used to transfer data between systems; FTP is not
required.
All integration controls for a warehouse are in the iSeriesIntegration.ini file on the
SCM PC. APS Bridge Interface Control file and the APSCTL Data Area are not used.
See “Integration Control – iSeriesIntegration.ini”.
Page E-2
User Interface Differences

This table maps the user interfaces in the APS Bridge to the user interfaces in APS
Integration.
APS Bridge APS Integration

Menu options (menu number, option number)
(1, 1) Interface control iSeriesIntegration.ini file on the Synch Engine
(maintenance)
(1, 2) Hold Code Filters (MRP 10, 8) Maintain Customer Order Filters
(maintenance)
(1, 3) Customer Order Backlog Maintain User Customer Orders command: MNTAPSUCO
Offline Load (See Appendix D, “Additional SCM Data”)
(1, 4) Period Forecast Offline Maintain User Forecasts command: MNTAPSUFC (See
Load a Appendix D, “Additional SCM Data”)
(1, 5) Putback Transaction iSeriesIntegration.ini file and item warehouse auto release
Tailoring Offline Load codes
(1, 6) Putback Transaction iSeriesIntegration.ini file and item warehouse auto release
Tailoring (maintenance) codes
(2, 1) Customer Orders on (MRP 10, 9) Filtered Customer Order Inquiry
Hold (inquiry)
(0, 3) Initiate Load/Putback Initiated from Synch Engine
(0, 4) Review Load Messages View iSeriesIntegration.log file on the Synch Engine
(0, 5) Review and Approve MRP Review/Approve and Release, and OBPM MRP
Putback Messages Recommendations
Other Interface Control Options
APSCTL Data Area iSeriesIntegration.ini file on the Synch Engine
User-controlled SCM datafile name; Appendix D, “Additional SCM Data”
Item plan (TPPLAN) and Item (PPITEM)
Forecast (TPFCST)
Routing (TPROUT) Routing operation (PPROUT)
Sequence Dependent Setup Setup sequence (PPSEQS)
(TPSEQS)
Capable To Promise (CTP)
Capable To Promise (COM/ Capable To Promise (COM/APS Integration)
APS Bridge)
a. The period forecast offline load record format changed in APS Integration.
See Appendix D, “Additional SCM Data”. If you are using Period Forecast
Offline Load, you must start using the new record format in APS Bridge, as
soon as you load the APS Integration programs onto your system, as the
programs that process that file and update the Period Forecast file, which
run in both APS Bridge and APS Integration, use the new record format.
Page E-3
Actions you must take

Establish an ODBC connection from the SCM engine PC to System i and environment.
This enables the PC to transfer data to and from the ERP data base (replaces the
APS Bridge Interface Control parameters enabling the System i to FTP data to and from
the PC).
Set the MRP planning horizons (Menu AMMM20, Option 1), to control the planning
date, and release and review horizons for working with the plan output (replaces the
APS Bridge Interface Control Release horizon parameter).
Set the MRP safety stock lead time option as desired (Menu AMMM20, option 4), to
select the value sent in item Planning fence, used in SCM safety stock processing
(replaces item Days per forecast period sent by the APS Bridge).
Set most other integration control parameters (now in interface control and the
APSCTL Data Area) for the warehouse in the iSeriesIntegration.ini file on the synch
engine PC. See “Integration Control – iSeriesIntegration.ini”.
Set/verify the following item warehouse fields for planned items:

• Order policy code: cannot be B or C, as this (now) identifies items to be planned
(replaces Planned by).
• Master level item (MLI) code: cannot be blank if the item has independent
demand, for example, forecasts, customer orders or MRP MLI requirements. Note
that forecasts and/or requirements can now be interactively entered and
maintained – individually or propagated – and viewed in MRP screens and
reports.
• Plan customer orders code: controls whether customer orders are used in
planning.
• Plan expected orders code: controls which if any expected customer orders
received via EDI into EC are used in planning.
• Master level forecast code and the 3 associated fields: allows you to propagate
either forecasts (to be consumed by customer orders) or requirements (to be
planned in addition to any forecasts or customer orders). The MRP propagate
function is used instead of the SCM pull signal function, so the propagated
demand shows in the MRP files, and so you can use a different number of days to
propagate your demand, and for your safety stock lead time (sent in Planning
fence, per the MRP safety stock lead time option).
• If you currently use the SCM min-max function for purchased order policy code C
items, you must change this, as APS Integration does not plan order policy code
C items. If order point processing is adequate, you can plan these items with IM
Reorder Report or OBPM Reorder Recommendations. If you want to plan all
items in SCM, you must change the order policy code, and any relevant order
planning parameters, to have it planned there.
• For manufactured items: days supply, minimum and multiple, as the Synch
Engine uses these fields in lot sizing, based on the order policy code, as it does
for purchased items.
• Purchase and manufacture auto release codes: can be used to control, by
item, whether a planned order flagged for release is automatically created in
upload after in planning (replaces Putback transaction tailoring). See “Uploading
to ERP”.
Page E-4
Forecasts from Forecasting (FCST)

• If APS Bridge is running in a warehouse, FCST Load to Master Schedule loads
the forecast to the APS Bridge Period forecast file; APS Bridge downloads all
forecasts from that file.
• If MRP is running in a warehouse and the FCST to MRP interface is active, FCST
Load to Master Schedule loads the forecast to the MRP requirements (REQMTS)
file.
• If the FCST to MRP interface is active, APS Integration downloads forecasts only
from the MRP REQMTS file.
Before you plan a warehouse using APS Integration, activate the FCST to MRP
interface and run FCST Load to Master Schedule to load the forecast to the MRP
REQMTS file.
User forecasts, supplied from an external source, and consuming

forecasts
In both APS Bridge and APS Integration, if you do not use FCST, you can supply user
forecasts in the Period forecast file. With APS Bridge, those forecasts can be:
Consume forecast: Yes Consumed by customer orders and only unconsumed
forecast planned
Consume forecast: No Planned regardless of, or in addition to, customer orders.
In APS Integration, forecasts are always consumed by customer orders. If you have
demand you want planned in addition to customer orders, you can enter requirements
in MRP. You can also supply that demand as user customer orders. See “User
customer orders, supplied from an external source”.
If you currently supply forecasts that you want consumed, you can:
1. Still use the offline load from the APS Bridge. In APS Integration, you can run the
forecast offline load using command MNTAPSUFC. The same option screen is
presented as in the APS Bridge. See Appendix D, “Additional SCM Data”. See
Footnote a.
2. Still do this if you have a user program that loads the Period forecast file
(OLPFCS) directly, as that file is still used in APS Integration.
3. If you have a user program, change your program to load user forecast records
directly into the MRP requirements file (REQMTS), as APS Integration loads all
forecast and unshipped customer order demand into that file. If you change your
user program, when you have loaded your forecast into the MRP REQMTS file,
delete the forecast records in the Period forecast file to avoid duplicate forecasts.
User customer orders, supplied from an external source
In both APS Bridge and APS Integration, regardless of whether you use COM, CSM,
etc. to enter and manage customer orders, you can supply user customer orders in
the Customer order backlog file. If you currently do this, you can:
1. Still use the offline load from the APS Bridge. In APS Integration, you can run the
customer order offline load using command MNTAPSUCO. The same option
screen is presented as in the APS Bridge. See Appendix D, “Additional SCM
Data”.
Page E-5
2. Still do this if you have a user program that loads the Customer order backlog file
(OLCSBL) directly, as that file is still used in APS Integration.
3. If you supply only unshipped quantities in the user customer orders, and you have
a user program, change your program to load user customer order records
directly into the MRP requirements file (REQMTS), as APS Integration loads all
forecast and unshipped customer order demand into that file. If you change your
user program, when you have loaded your customer orders into the MRP
REQMTS file, delete the customer orders in the Customer order backlog file, to
avoid duplicate orders.
Customer order filters
If you filter customer orders with specified COM hold codes from planning, before you
plan using APS Integration, you must enter the COM hold codes to be filtered using
MRP menu AMMM10, option 8, as the APS Bridge file is not used in APS Integration.
User-controlled TP* files (See Appendix D)
The user-controlled TP* files providing additional SCM data have been replaced by
PP* files:
• TPPLAN and TPFCST are replaced by a single PPITEM file, with only the
required fields, and family Ids expanded from 13 to 15 characters
• TPROUT is replaced by PPROUT, with family Ids expanded from 13 to 15
characters, and minor setup time and cleanup time stored in minutes, not
seconds
• TPSEQS is replaced by PPSEQS, with family Ids expanded from 13 to 15
characters, and minor setup time stored in minutes, not seconds.
To copy and convert the data from the APS Bridge files into the APS Integration files,
three commands are provided:
CPYAPSITM “WHS”, where “WHS” is the warehouse, for the PPITEM file
CPYAPSRTG for PPROUT
CPYAPSSEQ for PPSEQS.
These commands clear the data in the PP* file (for PPITEM, just for the one
warehouse), then copy the data from the TP* file(s) into the PP* file. You should copy
the files before your first APS Integration test, and again if you make changes to the
file/s in the APS Bridge. This lets you maintain the data in the APS Bridge while you
are using it, and copy the files changed to APS Integration as required.
Automating and customizing
APS Bridge allows you to call Load and Putback from a user program, and provides
user exits in each:
AXAEXT0C: initiates extract/load, can be called from a user program
UXAEXT01: user exit in load after TPI* files are built on System i and before they
are sent to the SCM engine as described in “Planning and scheduling”
UXAEXT02: user exit in load after files are sent to the SCM engine and DbUtil is
run
Page E-6
AXAPBK0C: initiates putback, can be called from a user program
UXAPBK01: user exit in putback when System i connects to the SCM engine and
before any processing
UXAPBK02: user exit in putback after data is sent from the SCM database to the System i
and processed.
APS Integration initiates download and upload from the SCM engine, so you must set
up/customize your process on the engine, as described in “Planning and scheduling”,
including any changes you require to the format files on the SCM engine.
APS Integration provides the following user exits on the System i:

UXADNL01: exit in download after PPI* files are built on System i and before they
are loaded by DBUtil to the SCM database
UXAUPL01: exit in upload when the SCM engine connects to the System i and
before any processing
UXAUPL02: exit in upload after data is sent from the SCM database to the System i
and processed.
Running SCM 6.1 and APS Integration
As SCM 6.1 and APS Integration provide significant new function and usability, you
should test APS/SCM in a separate environment before running it in your operational
environment, to ensure all the new capabilities are in place and understood, and
working as desired.
APS Integration must be ‘Activated’ in a warehouse before it can upload SCM

planning data to the System i and update ERP files. See “Activating APS Integration”
for details.
Page GL-1
Glossary
Glossary
This glossary defines terms that are important for this application. It does not include
all XA terms nor all terms established for your system. If you do not find
the term you are looking for, refer to the Index in this book or to glossaries in other XA
publications.
Advanced Planning and Scheduling. A method of resource planning that plans

material and capacity concurrently based on independent demand.
APS. See Advanced Planning and Scheduling.
ATP. See Available to Promise.
Available to Promise. The uncommitted portion of a company’s inventory and

planned production, maintained in the master schedule to support customer order
promising.
backlog. Customer orders or customer backlog of orders not yet filled.
Capable to Promise. Customer order promising to deliver based on available

material and capacity as determined by SCM.
client. On a local area network or the Internet, a computer that accesses shared
network resources provided by another computer (called a server). See also client/
server architecture, server.
client/server architecture. An arrangement used on local area networks that

makes use of distributed intelligence to treat both the server and the individual
workstations as intelligent, programmable devices, thus exploiting the full computing
power of each. This is done by splitting the processing of an application between two
distinct components: a “front-end” client and a “back-end” server. The client
component is a complete, stand-alone personal computer (not a “dumb” terminal),
and it offers the user its full range of power and features for running applications. The
server component can be a personal computer, a minicomputer, or a mainframe. The
client and server machines work together to accomplish the processing of the
application being used.
component. An item used to make a higher level item.
CTP. See Capable to Promise.
demand warehouse. A demand warehouse represents a point where customer

orders and/or forecasts are put into a manufacturing system. In XA, these
orders are passed to a planning warehouse where the supply function occurs. In XA,
a demand warehouse can also be included in the MRP equation to
show a common pool of parts available to the planning process.
download The transfer of planning input from the System i database to the planning
engine database.
file transfer protocol. See FTP.

Page GL-2
Glossary
forecast. An estimate of customer (independent) demand for an item for a specific

period in the future.
FTP. Acronym for File Transfer Protocol, the protocol used for copying files to and
from remote computer systems on a network using TCP/IP, such as the Internet.
This protocol also allows users to use FTP commands to work with files, such as
listing files and directories on the remote system.
horizon. A span of time from the current or system date to some future point in time.
item. Any raw material, manufactured or purchased part, or assembly.
part. See item.
planning warehouse. MRP plans for one warehouse at a time. A planning

warehouse is typically a manufacturing location, although customer order demand is
received at the planning warehouse. It is the entity against which MRP is executed.
server. 1. On a local area network (LAN), a computer running administrative

software that controls access to the network and its resources, such as printers and
disk drives, and provides resources to computers functioning as workstations on the
network. 2. On the Internet or other network, a computer or program that responds to
commands from a client. For example, a file server may contain an archive of data or
program files; when a client submits a request for a file, the server transfers a copy
of the file to the client. See also client/server architecture. Compare with client.
upload The transfer of planning results from the planning engine to the System i
database, and associated processing as specified in ISeriesIntegration.ini.
Page IN-1
Index
Index
A
Actions you must take E-3
Activating APS integration 3-9
Additional SCM Data D-1
Automating and customizing E-5
B
Bill of Material (PPIBOM) A-5
Bill of Material (PPIBOM) file A-5, C-1
Both forecast and customer sales demand 3-6
C
Capable To Promise (CTP) for Customer Orders 1-4
COM customer order line item release (MBADREP) B-3
Connecting SCM and XA 2-10
Considerations for maintaining this file for use with SCM D-2
Creating an ODBC data source 2-3
CTP 2-11
CTP for KBC items 3-14
Customer order scheduling and CTP 3-13
Customer order update (PPCOWK) B-2
Customer sales demand 3-5
D
data
files
Forecast (PPIFCS) A-10
Inventory (PPIINV) A-13
Item (PPIPRT) A-2
Item Process (PPIPRC) A-4
Jobs in Progress (PPIJIP) A-18
Purchase (PPIPUR) A-20
Routing (PPIRTG) A-6
Sales (PPICOM) A-11
Warehouse Control (PPIPLN) A-21
Workcenter (PPIWKC) A-8
Workorder
Allocation (PPIMOD) A-15
Heading (PPIMOM) A-14
Routing (PPIMOR) A-16
Data downloaded to SCM A-1
Data uploaded to ERP B-1
Debug 2-13
Demand and forecast consumption 3-3
Differences between APS Bridge and APS Integration E-1
Download 2-10
download
data files
Page IN-2
Index
workorder allocation (PPIMOD) A-15

Workorder Heading (PPIMOM) A-14
Workorder Routing (PPIMOR) A-16
inventories C-2
items C-1
manufacturing orders C-2
production facilities C-2
routings C-1
Download error messages C-1
Downloading to SCM 3-10
E
Enabling Capable To Promise (CTP) 2-14
error messages C-1
bills of materials C-1
inventories C-2
items C-1
routings C-1
F
facilities, production C-2
Fields D-4
files
Inventory (PPINV) A-13
Item (PPIPRT) A-2
Sales (PPICOM) A-11
Workorder Allocation (PPIMOD) A-15
Forecast (PPIFCS) file A-10
Forecast consumption 3-3
Forecast demand 3-5
Forecasts from Forecasting (FCST) E-4
Function keys D-4
H
Handling purchased items in CTP 3-14
I
If APS Bridge is Running E-1
Implementing the Plan 1-4
Implementing the plan 3-13
Information Flow 1-2
Information provided on the SCM PC 1-3
Information used In SCM planning 3-1
Information used in SCM planning 1-2
Page IN-3
Index
Installing APS Integration on the System i 2-1

Installing SCM 6.1 and APS Integration 2-1
Installing SCM 6.1 on the PC 2-1
Integration Control – ISeriesIntegration.ini 2-10
Introducing APS Integration 1-1
Inventory (PPIINV) file A-13
Item (PPIPRT) A-2
Item (PPIPRT) file A-2
Item (PPITEM) D-5
Item Process (PPIPRC) file A-4
Item/product information 3-1
J
Jobs in Progress (PPIJIJP) file A-18
M
Managing APS Integration 3-1
Manufacturing Order / REP Schedule Master (MOMAST) B-4
Manufacturing Order Component (MODATA) B-5
Manufacturing Order Routing (MOROUT) B-4
materials, bills of C-1
messages
error C-1
bills of materials C-1
inventories C-2
items C-1
routings C-1
MRP Demand reference (DMDREF) B-1
MRP Planned orders (PLNORD) B-1
MRP planning parameters 3-8
MRP Requirements (REQMTS) B-1
MRP Reschedule activity work (RACWRK) B-2
O
Offline file library name D-4
Offline file name D-4
Order board matching 3-14
Order board matching = no 3-15
orders, manufacturing C-2
P
Planning and scheduling 3-11
PPIBOM file A-5
PPICOM file A-11
PPIFCS file A-10
PPIINV file A-13
PPIJIP file A-18
PPIMOD file A-15
PPIMOM file A-14
PPIMOR file A-16
Page IN-4
Index
PPIPLN file A-21

PPIPRC file A-4
PPIPRT file A-2
PPIPUR file A-20
PPIRTG file A-6
PPIWKC file A-8
Processing maintenance transactions D-4
Production facility information 3-1
Purchase (PPIPUR) file A-20
R
Routing (PPIRTG) file A-6
Routing operation (PPROUT) D-6
routings C-1
S
Sales (PPICOM) A-11
Sales (PPICOM) file A-11
Select one of the following D-4
Select option for update D-5
Setup Sequence (PPISEQ) A-9
Setup sequence (PPSEQS) D-6
Supply information 3-7
T
The planning process 1-4, 3-9
U
Unconsumed forecast 3-6
Updating customer orders from SCM planning 3-15
Upload 2-12
Uploading to ERP 3-11
User customer order (OLCSBL) B-3
User Customer Orders D-2
User customer orders 3-16
User Customer Orders and Forecasts D-1
User customer orders, supplied from an external source E-4
User Forecasts D-3
User forecasts, supplied from an external source, and consuming forecasts E-4
User Interface Differences E-2
User-controlled files D-5
User-controlled TP* files (See Appendix D) E-5
W
Warehouse Control (PPIPLN) file A-21
What APS Integration does 1-1
What Supply Chain Management (SCM) does 1-1
What reports are printed D-5
What to do D-4
Workcenter (PPIWKC) file A-8
Page IN-5
Index
Workorder
Allocation (PPIMOD) file A-15
Heading (PPIMOM) file A-14
Routing (PPIMOR) file A-16
Workorder Allocation (PPIMOD) A-15
Page IN-6
Index

Aps Ig R9 1 022013

Uploaded by

Copyright:

Available Formats

Aps Ig R9 1 022013

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

Aps Ig R9 1 022013

Uploaded by

Copyright:

Available Formats

Infor XA – Advanced Planning and

Scheduling Integration Guide

Before you begin

What this book contains

To the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i-iii

Sales (PPICOM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-11

Chapter 1. Introducing APS Integration

What Supply Chain Management (SCM) does

What APS Integration does

Information used in SCM planning

This section summarizes the XA information used in SCM planning, and

Production facility information

Information provided on the SCM PC

The following information used in planning is maintained on the SCM PC:

The planning process

The following System i information is updated from planning:

MRP planning files

Implementing the Plan

Capable To Promise (CTP) for Customer Orders

Chapter 2. Installing SCM 6.1 and APS Integration

Installing APS Integration on the System i

Installing SCM 6.1 on the PC

Installing SCM for use with XA includes the following steps:

Creating an ODBC data source

Select Connections Options to display the Connections options window:

Click OK to create an ODBC connection between the PC and the environment

Integration Control – iSeriesIntegration.ini

Connecting SCM and Infor ERP XA

Enabling Capable To Promise (CTP)

Chapter 3. Managing APS Integration

Information used In SCM planning

Production facility information

Additional SCM item information (PPITEM file)

Demand and forecast consumption

As APS Integration interfaces through MRP, it supports demand warehouses

The simplest forecast consumption is by individual item – the additional item

APS Integration downloads forecast demand to SCM from:

Customer sales demand

APS Integration downloads customer sales order demand to SCM from:

- Origination of 20 or greater (RQORG)

Both forecast and customer sales demand

MRP shows forecast demand two places:

Upload builds forecast requirements records for the unconsumed forecast:

MRP planning parameters

• Initiate Planning Run Options:

The planning process

Activating APS Integration

To prevent one of these applications from damaging another application’s information,

Activating APS Integration in a warehouse (set APSActive to 1 and plan): prevents

Parameters in iSeriesIntegration.ini establish the connection to the System i and the

The parameters to connect the SCM PC to the XA system, environment,

The APSActive and DownloadMode parameters, mentioned in the previous section,

• MRP Maintain period intervals

Planning and scheduling

4. Automatically creates manufacturing orders and REP schedules as specified in

• UXAUPL01, called if present on theSystem i, when the SCM engine connects

Implementing the plan

Customer order scheduling and CTP

Handling purchased items in CTP