Infor ERP XA

Advanced Planning System

Bridge (APS Bridge)

Release 7.0
Copyright © 2008 Infor
All rights reserved. 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 trademarks listed herein are the property of their
respective owners. [Link]
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 com-
pany from Infor pursuant to a separate agreement ("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.
Trademark Acknowledgements
AS/400, IBM, iSeries, System i, OfficeVision, Operating System/400, OS/400 are registered trademarks and Distrib-
uted Automation Edition is a trademark of IBM Corporation.
Microsoft, Windows, Microsoft Peer Web Services and Internet Service Manager are either registered trademarks or
trademarks of Microsoft Corporation.
Publication Information
The product Infor ERP XA was previously know as Infor XA, MAPICS ERP for iSeries and MAPICS XA. These names
may still appear in text or graphics within this book.
Release: Advanced Planning System Bridge for Infor ERP XA Release 7.0
Publication Date: March 2008
 Page iii
Contents Index
To the reader

To the reader
This book contains the information you need to use the APS Bridge in conjunction with the 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 Bridge 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

Chapter 1 introduces you to SCM and the APS Bridge interface.

Chapter 2 provides information on managing APS.

Chapter 3 provides information on installing the APS Bridge interface.

Chapter 4 provides detailed information on the menus and panels used by the APS Bridge.

Appendices A and B describe the offline file layouts you may need and provide information on mapping
XA files to SCM files.

Appendix C summarizes the APS Bridge / REP interface which allows APS Bridge and SCM to process
repetitive schedules and manufacturing orders.
 Page iv
Contents Index
Summary of changes

Summary of changes
Enhancements have been made in manufacturing order creation and scheduling, including an option to
combine multiple orders scheduled to start on the same day and improved use of SCM data in operation
priorities. See Putback for manufacturing transactions in Chapter 2.

Enhancements have been made in customer order scheduling. These enhancements are explained in
Understanding the Putback process and Customer Orders in Chapter 2. These enhancements include the
ability to specify what purchased material is considered when you perform a Capable To Promise (CTP) in
customer order entry.

Additional fields are supported in Interface Control Maintenance (Chapter 4, menu AXAM01, Option 1).

APS Bridge / REP interface supports item (REP) schedules for schedule-controlled items. See Appendix C.

Some corrections have been made in the Appendix B, Data Mapping.

Changes in text are marked by revision bars.

 Page v
Contents Index
Contents

Contents

To the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
What this book contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Chapter 1. Introducing APS Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What Supply Chain Management (SCM) does . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What the APS Bridge does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
How the APS Bridge works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
APS interfaces with XA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Cross Application Support (CAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Customer Order Management (COM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Enterprise Product Data Management (EPDM) . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Forecasting (FCST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Inventory Management (IM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Knowledge Based Configurator (KBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Production Control and Costing (PCC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Purchasing (PUR) or PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Repetitive Production Management (REP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Non-XA ERP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
APS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Chapter 2. Managing APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
General information about APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Understanding the Load process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Edits used in Initiate Load program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Special handling of blank characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Reviewing load messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Understanding the Putback process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Edits used in Initiate Putback program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Putback for manufacturing transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Putback for purchase transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Putback for customer orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Review and Approve Putback messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Forecasts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Customer Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Checking purchased material in CTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Chapter 3. Installing the APS Bridge Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Installing the APS Bridge Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Using File Transfer Protocol (FTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Using Client Access Remote Command (RUNRMTCMD) . . . . . . . . . . . . . . . . . . . 3-2
Verifying special characters for RUNRMTCMD . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Installing the Client Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Starting CTP Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
APS Bridge implementation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Additional setup information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Chapter 4. Using the APS Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Option 1 (AXAM00). Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Option 1 (AXAM01). Interface Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
MO0550—Interface Control (Select) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
MO0551—Interface Control (Page 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
 Page vi
Contents Index Exit Contents

MO0552—Interface Control (Page 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

MO0553—Interface Control CCSID Parameters (1 of 2) . . . . . . . . . . . . . . . . 4-11
MO0554—Interface Control CCSID Parameters (2 of 2) . . . . . . . . . . . . . . . . 4-14
Option 2 (AXAM01). Hold Code Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
MO0640—Hold Code Filters (Select) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
MO0641—Hold Code Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Option 3 (AXAM01). Customer Order Backlog Offline Load . . . . . . . . . . . . . . . . . 4-21
AMVPOF—Customer Order Backlog Offline Load . . . . . . . . . . . . . . . . . . . . . 4-22
Option 4 (AXAM01). Period Forecast Offline Load . . . . . . . . . . . . . . . . . . . . . . . . 4-24
AMVPOF—Period Forecast Offline Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Option 5 (AXAM01). Putback Transaction Tailoring Offline Load . . . . . . . . . . . . . 4-27
AMVPOF—Putback Transaction Tailoring Offline Load . . . . . . . . . . . . . . . . . 4-28
Option 6 (AXAM01). Putback Transaction Tailoring . . . . . . . . . . . . . . . . . . . . . . . 4-30
MO0570—Putback Transaction Tailoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
MO0590—Putback Transaction Tailoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Option 2 (AXAM00). Inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Option 1 (AXAM02). Customer Orders on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
MO0711—Customer Orders on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Option 3 (AXAM00). Initiate Load/Putback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
MO050R—Initiate Load/Putback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
MO0580—Review and Approve Putback Messages . . . . . . . . . . . . . . . . . . . 4-41
MO058S—Subset Window for Putback Messages . . . . . . . . . . . . . . . . . . . . . 4-43
MO0581—Print Putback Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Option 4 (AXAM00). Review Load Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
MO1230—Review Load Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
MO1231—Review Load Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Option 5 (AXAM00). Review and Approve Putback Messages . . . . . . . . . . . . . . 4-49
MO4990—Review and Approve Putback Messages . . . . . . . . . . . . . . . . . . . 4-50
Appendix A. Offline file load and data entry . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
Creating a diskette or disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
Understanding the file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
Assigning a file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2
Record length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2
Special data requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2
Processing the offline files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2
Record formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3
Customer Order Backlog Offline Load file record format . . . . . . . . . . . . . . . . .A-3
Interface Transaction Tailoring Offline Load file record format . . . . . . . . . . . . .A-4
Period Forecast Offline Load file record format . . . . . . . . . . . . . . . . . . . . . . . .A-4
Appendix B. Mapping XA Files to SCM Files . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
PSTDTL mapping to SCM’s BOM file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2
KBC considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2
PSTHDR mapping to SCM’s BOM file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2
ITMRVA mapping to SCM’s Part file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3
ITMRVC mapping to SCM’s Part file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3
ITEMBL mapping to SCM’s Inventory file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3
ITEMBL mapping to SCM’s Part file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4
ITMPLN mapping to SCM’s Part file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5
FACMST mapping to SCM’s Work Centers file . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5
RTGOPR mapping to SCM’s Routing file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-7
MOMAST mapping to SCM’s Work Order Header file . . . . . . . . . . . . . . . . . . . . . .B-8
MOROUT mapping to SCM’s Jobs in Progress file . . . . . . . . . . . . . . . . . . . . . . . . .B-8
 Page vii
Contents Index Exit Contents

MOROUT mapping to SCM’s Jobs in Progress file . . . . . . . . . . . . . . . . . . . . . . . .B-10

MOROUT mapping to SCM’s Work Order Routing file . . . . . . . . . . . . . . . . . . . . .B-11
MODATA mapping to SCM’s Work Order Allocation file . . . . . . . . . . . . . . . . . . . .B-12
Mapping Purchase Orders and Requisitions to SCM’s Purchase file . . . . . . . . . .B-13
POITEM Mapping to SCM’s Purchase file . . . . . . . . . . . . . . . . . . . . . . . . . . .B-13
POBLKT Mapping to SCM’s Purchase file . . . . . . . . . . . . . . . . . . . . . . . . . . .B-13
REQHDF Mapping to SCM’s Purchase file . . . . . . . . . . . . . . . . . . . . . . . . . . .B-14
OLPFCS mapping to SCM’s Forecast file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-14
KBC considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-14
MBADREP Mapping Customer Line Item file to SCM’s Sales file . . . . . . . . . . . . .B-14
KBC considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-15
OLCSBL Mapping Offline Customer Line Item file to SCM’s Sales file . . . . . . . . .B-16
APS Bridge Interface Control file controls processing on SCM and Bridge . . . . .B-17
XA Tailoring Questions that Affect APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-17
Appendix C. XA Release 6 APS Bridge REP Interface . . . . . . . . . . . . . . . . . C-1
Load to SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Facilities / Work Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Alternate production lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Bills of Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Unreleased schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Released schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
SCM processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Putback from SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
New Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Unreleased schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Released schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GL-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-1
Contents Index Exit
 Page 1-1
Contents Index
Introducing APS Bridge

Chapter 1. Introducing APS Bridge

What Supply Chain Management (SCM) does........................................................ 1-1
What the APS Bridge does....................................................................................... 1-1
How the APS Bridge works ...................................................................................... 1-2
APS interfaces with XA ............................................................................................ 1-4
Non-XA interfaces .................................................................................................... 1-6

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, which may also be referred to as the APS Engine, resides on a Client
machine 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 the APS Bridge does

The APS Bridge provides integration of XA to the SCM
application. It includes the following capabilities:
• Tailor information by warehouse
• Extract (Load) information from an XA environment based on
the tailoring rules you specify
• Putback and review of the SCM server’s planning recommendations to XA
• Provide capable to promise inquiries when entering COM’s customer orders.

The APS Bridge extracts information from an XA environment, such as the

following typical data:
• Items
• Bills
• Routings
• Resource capacities
• Work in process (manufacturing and purchase orders)
 Page 1-2
Contents Index
Introducing APS Bridge

• Material availability
• Customer orders
• Forecasts.
The APS Bridge generates messages back to the XA environment for
the specified warehouse in terms of the following actions for manufacturing and
purchase orders:
• Creating orders
• Changing orders
• Cancelling orders
• Changing order quantities
• Updating order promise and manufacturing dates.

These putback messages can be reviewed prior to executing the resulting

transactions. If an action message is accepted, the APS Bridge generates a
transaction to update the XA environment with the specified action.

How the APS Bridge works

The APS Bridge interface runs on the System i. The SCM Server portion (also called
the APS Engine) and the Client portions run on Windows 95/98, Windows 2000, and
on Windows NT.

The APS Bridge is installed using standard XA install/tailor functions

provided through Cross Application Support (CAS). EPDM and IM are prerequisites
for SCM. COM, FCST, KBC, PCC, and PUR are applications that provide the
necessary components of data for realistic planning.

The picture below illustrates an example APS Bridge and SCM installation.
 Page 1-3
Contents Index
Introducing APS Bridge

Once the interface is installed, you must perform the following steps:
• set up the tailoring for the warehouse (use option 1 on the APS Bridge
Maintenance menu)
• set up the items to be planned by APS (use EPDM to enter the Planned by field
in the Item Warehouses object).
The following items cannot be flagged as planned by APS:
Note:
- Miscellaneous or service items
- S-numbered items
- Items defined as Features (Item type= F)
- Items defined as Kits (Item type=K).
• enter COM hold code filters (use option 2 on the APS Bridge Maintenance menu)
• tailor the putback transactions (use option 5 or 6 on the APS Bridge Maintenance
menu).
You can tailor the messages interactively (option 6) or through offline mass
maintenance (option 5). Use offline maintenance if the interactive subset criteria
provided does not meet your needs.

After these steps are completed, you must perform an initial load of APS to load the
appropriate XA (MAPICS) data to the APS Engine.
 Page 1-4
Contents Index
Introducing APS Bridge

The interface captures data from the following XA files:

• Product Structure (PSTDTL)
• Item Revision (ITMRVA, B, C)
• Item / Line (ITMLIN)
• Item Plan (ITMPLN)
• Facility Master (FACMST)
• Routing (RTGOPR)
• Manufacturing Order Master (MOMAST)
• Manufacturing Order Routing (MOROUT)
• Manufacturing Order Component (MODATA)
• Purchase Order Item (POITEM)
• Requisitions (REQHDF)
• Purchase Order Blanket (POBLKT)
• COM Item Release (MBADREP)
• COM Feature/Option Item (MBACREP)
• COM Quote/Order Header (MBC6REP)
• COM Calendar Day (MBAQREP)
• Period Forecast (OLPFCS)
• KBC Routing (TCF000)
• KBC BOM (TCFOBM)
• KBC Header (TCFOHB)
• Offline Customer Backlog (OLCSBL)
APS Bridge provides the following user-populated files to supplement item attributes
found in XA data files:
• SCM Forecast Interface (TPFCST)
• SCM Item Plan Interface (TPPLAN)
• SCM Routing (TPROUT)
• SCM Sequence Dependent Setup (TPSEQS)

Use Cross Application Support to obtain a spool file of the file record layout of the file
you will be working with. On the CAS Reports menu, select option 5 (File Record
Layout). You also can use the System i command DSPFI to view the file layout. See
the CAS User’s Guide for more detailed information.

When you are ready to send data to the APS Engine, you select the Initiate Load
option on the APS Bridge main menu.

The load process reads the master file and formats the data into APS format. After the
data is imported to the APS Engine, you execute SCM’s scheduling functions and
report output files are generated. Then you select the Initiate Putback option on the
APS Bridge main menu to format the transaction messages and place them back on
the System i for processing. At this time you can review the transaction messages and
select transactions for processing.

APS interfaces with XA

Cross Application Support (CAS)

CAS offline load option programs support the APS Bridge offline load functions.
Records are added to files to support the functions from within APS. Security
functions are used to authorize users to access APS’s warehouse data. Period
forecasts and customer sales backlog can be loaded from offline.
 Page 1-5
Contents Index
Introducing APS Bridge

Customer Order Management (COM)

COM provides customer orders (including KBC customer orders) to APS. Items
planned by APS can execute the Capable to Promise function and update the
manufacturing and promise date based on user-selected options. Specific COM-
defined hold codes are used to omit certain demands from SCM.

Enterprise Product Data Management (EPDM)

This is a required application. EPDM provides items, bills of material, routings, and
production facility information to APS. EPDM allows maintenance of item, bill of
material, production facility, and routing fields.

Forecasting (FCST)
FCST provides forecast information to APS. If the item is planned by APS,
Forecasting outputs period forecasts for the APS Bridge.

Inventory Management (IM)

This is a required application. IM provides item information, inventory balances,
planning parameters, and information about released manufacturing orders to APS.
APS provides transactions to IM in terms of releasing and canceling manufacturing
orders and purchase orders, and changing order quantities. These transactions are
based on recommendations from SCM.

Knowledge Based Configurator (KBC)

KBC provides APS with bills and routings for configured customer orders.

Production Control and Costing (PCC)

PCC provides information on the status of operations associated with a manufacturing
work order. It receives information on scheduling dates based on the latest APS plan.
The PCC job scheduler, work list generation, and backward scheduler will not update
operation dates for items planned by APS. PCC provides WIP updates to APS.

Purchasing (PUR) or PM
PM/PUR provide APS with open purchase orders and requisitions. APS provides to
PM/PUR transactions to create, delete, and change order quantities based on the
latest planning in APS.

Repetitive Production Management (REP)

APS creates unreleased production schedules for REP. REP provides item and
production line information, as well as the status of production schedules to APS. For
more information about the REP and APS Bridge interface, see Appendix C.
 Page 1-6
Contents Index
Introducing APS Bridge

Non-XA interfaces
You can input customer sales backlog through an offline file load, using option 3 on
the APS Bridge Maintenance menu. You can use this function to load future line item
demand that has not yet received.

You can load period forecasts from other forecasting sources through an offline file
load, using option 4 on the APS Bridge Maintenance menu.

APS files
APS Bridge uses a variety of files, such as control files, filter files, message files, and
load and putback files. Only the files most frequently encountered by users are
discussed here.

XA/APS Interface Control (OLSYSC). This file is used to specify

execution parameters for the load and putback processes. This file is maintained from
option 1 on the APS Bridge Maintenance menu.

XA/APS Transaction Tailoring by Item (OLITMT). This file is used to

define which transactions are active for an item/warehouse and if the posting is
automatic or manual and if any informational messages should be generated during
the putback process. This file is maintained from option 6 on the APS Bridge
Maintenance menu.

XA/APS Putback Informational Message (OLIMSG). This file is used to

record messages about the putback. Each time a manufacturing order or purchase
order is created, changed, or cancelled during the process, a message is written to
this file to state the actions that have occurred. The file is processed by the user with
Review and Approve Putback Messages activity.

Hold Code Filter (OLFHC). This file is used to stop orders having COM hold codes
from being passed to APS. This file is maintained from option 2 on the APS Bridge
Maintenance menu.

Offline Load Period Forecast (OLOFCS). This file is used to offline load forecasting
information into APS from another forecasting application. This information is used to
supplement the demand from FCST. It is processed from option 4 on the APS Bridge
Maintenance menu.

Period Forecast (OLPFCS). This file is used to load the forecast for a warehouse/
item for a period. The period is defined by the user’s forecasting system.

Customer Order Backlog Offline Load (OLCSBO). This file is used to input
customer order backlog from a source outside XA. This information is used
to supplement the demand from COM. It is processed from option 3 on the APS
Bridge Maintenance menu.
 Page 1-7
Contents Index
Introducing APS Bridge

Customer Order Backlog (OLCSBL). This file is used to store customer order
backlog information that was created during the process of offline load of customer
order backlog.

Load Server Messages (OLLMSG). This file is used during the load process. It
contains a copy of the import log generated by the APS engine during the import of
data. It is not maintained by the user. This data can be viewed by using option 4 on
the APS Bridge Main menu.
 Page 1-8
Contents Index
Introducing APS Bridge
 Page 2-1
Contents Index
Managing APS

Chapter 2. Managing APS

This chapter discusses APS features and functions. Some run parameters are also
discussed, but be sure to utilize the online Help for additional information not covered
here.
General information about APS................................................................................ 2-1
Understanding the Load process.............................................................................. 2-1
Understanding the Putback process......................................................................... 2-2
Forecasts .................................................................................................................. 2-9
Customer Orders ...................................................................................................... 2-9

General information about APS

• XA security is used to check if users are authorized to
perform selected functions. Users must be authorized to specific warehouses.
Warehouses must be designated as a planning warehouse.
• APS uses an XA job queue that is dedicated to APS interface
transactions only. This job queue (AXAPSQ) processes load and putback
requests and associated programs.
• APS provides online maintenance of its Interface Control fields, hold code filters,
and transaction tailoring by item fields. All new fields added to existing XA
databases can be maintained through EPDM.
• All dates in the APS Bridge are stored in century byte, year, month, day format
(CYYMMDD). The dates created in the offline load files, however, must be input in
user (i.e., system) format.
• All dates in the APS Engine are stored in either month, day, year format
(MMDDYYYY) or day, month, year format (DDMMYYYY).
• All times in the APS Bridge are stored in 24-hour format.

Understanding the Load process

The Load is run from the APS Bridge main menu. The load process involves the
following steps:
1. Allows a user to select immediate or deferred execution.
If deferred, you can specify a date and time to run the Load. Load should run at
least one minute after midnight so that changes in product structure component
effective dates can be recorded. Depending on the length of time to run the Load
you should plan on running Load at least once per day.
2. Submits a job to APS’s XA job queue AXAPSQ.
a. Runs a function to verify the connection to the server
b. Clears the Load files and overrides the job to the correct member in the Load
files
c. Translates the master files to the Load files
d. Overrides the Load audit report, if requested
e. Creates the FTP commands in the OLFTPS file
 Page 2-2
Contents Index
Managing APS

f. For all files imported to the engine:

1) Builds the RUNRMTCMD command to import the data to the engine
2) Uses FTP and transfers the files to the engine
3) Imports the data to the database using the RUNRMTCMD command to
execute the DBUTIL program
4) Retrieves the import log generated and copies it to the OLLMSG file.

Edits used in Initiate Load program

For the Load to run successfully, APS Bridge performs the following edits prior to
beginning the Load:
• Checks for a duplicate path to the engine, using the IP address and download
directory against all XA environments on the System i
• Verifies that the user is authorized to the warehouse
• Verifies that all errors from the last putback for the warehouse have been
corrected

Special handling of blank characters

Some databases cannot accept embedded blanks in a key field, and most databases
ignore leading blanks. XA allows the use of blanks in key fields because
the System i database accepts blank characters. In order to transfer data from XA to
a remote system, APS Bridge replaces the occurrence of blanks in fields with
another character called a blank replacement character. You must specify the
character to be used for replacing embedded blanks so that key fields remain unique.
If possible, the replacement character must be one that is not already used in the
data. However, if a replacement character is sometimes used, an initial replacement
character can be specified. The initial replacement character allows APS Bridge to
find and replace all occurrences of replacement characters, such as an underscore ( _
), that are already used before replacing blanks. On Putback, the keys are returned to
their original definition so that their data can be found on the XA system.

Reviewing load messages

The Load process makes a copy of the import log generated by the APS engine and
copies it to the Load Server Messages file (OLLMSG). You can use option 4 on the
APS Bridge Main menu to view these messages, by warehouse. You cannot maintain
the file. The messages are replaced each time the Load process runs.

Understanding the Putback process

The putback process is run from the APS Bridge main menu. You must be authorized
to the selected warehouse in order to perform a putback. If you select timed
execution, a window is displayed allowing you to enter the date and time to execute
the putback. If immediate execution is selected, the putback job is submitted to
XA job queue AXAPSQ to start executing immediately.

The putback process is driven by transactions that are tailored by item and
warehouse (using option 6 on the APS Bridge Maintenance menu). When the
Putback process is initiated, transaction messages are created from SCM files and
 Page 2-3
Contents Index
Managing APS

directed to the System i environment in which the planning warehouse resides.

XA database updates may take place based on the tailoring for the
transactions being processed.

Putback for an item is controlled by the putback transaction tailoring done for the item.
If the putback transaction, CRTMO, for example, has the transaction active flag
turned off (0), any requests from SCM to create a manufacturing order for the item will
be ignored. If the transaction active flag is turned on (1), any requests from SCM to
create a manufacturing order for the item will be processed.
Note: Putback for customer orders is controlled system-wide by settings in the APS
Bridge APSCTL data area, not by item. See Customer Orders in Chapter 2 for more
information.

The following discussion assumes the transaction active flag is turned on (1):

If the informational message flag is turned off (0), informational messages that require
no action will not be written to the putback message file. If the informational message
flag is turned on (1), all informational messages, whether they require action or not,
will be written to the message file. Informational messages requiring no action are
written to the putback message file with the IMINFO flag set to 0. Informational
messages requiring action are written to the putback message file with the IMINFO
flag set to 1. Regardless of what the informational message flag is set to, if an error is
detected during putback processing, an error message is written to the putback
message file with the IMINFO flag set to 2. All error messages require action.
Messages requiring action will have an input capable field when viewed with the
Review and Approve Putback Messages process.

The following discussion assumes the informational message flag is turned on (1):

If the automated posting flag is turned off (0), any putback requests from the engine
will result in an informational message that requires action to be written to the putback
message file. If the automated posting flag is turned on (1), any putback requests
from SCM will be executed and an informational message that requires no action will
be written to the putback message file.

The putback transactions that you can select are listed below:
CRTMO Create manufacturing order / item schedule
CHGMO Change manufacturing order / item schedule
CNLMO Cancel manufacturing order / item schedule
CHGRTE Change manufacturing order / item schedule routing
CRTPO Create purchase order
CNLPO Cancel purchase order
CHGPO Change purchase order
MFGUPM Manufacturing date in customer order update many times
MFGUP1 Manufacturing date in customer order update one time
PRMUPM Promise date in customer order update many times
PRMUP1 Promise date in customer order update one time

For manufacturing orders, you can initiate create, change, and cancel transactions.
The change transaction will handle both date and quantity changes. The Change
 Page 2-4
Contents Index
Managing APS

manufacturing order routings transaction handles changes to operation start and end
dates.

For purchase orders you have the option to create, change, and cancel transactions.
The putback process will create purchase orders, but will give informational
messages only for change and cancel transactions. You must change and delete
those purchase orders manually, either in Purchasing or Procurement Management.

For customer orders you have the option to update the manufacturing due date and
the promise date either when the order is scheduled by SCM the first time, or
whenever the schedule changes.

You can define which items and messages can be automatically putback to
XA without review. Other messages you will want to review prior to
updating XA data. Additionally, you have the option of making the
transaction active and whether the informational message should be created.

By using options on the APS Bridge Maintenance menu, you can tailor the item
messages interactively using fixed subsets of data (Putback Transaction Tailoring by
Item) or through offline mass maintenance if the interactive subset criteria provided
does not meet your needs (Putback Transaction Tailoring by Item Offline Load).

Edits used in Initiate Putback program

For the Putback to run successfully, APS Bridge performs the following edits prior to
beginning the putback:
• Checks for a duplicate path to the engine, using the IP address and download
directory of all XA environments on the System i.
• Verifies that the user is authorized to the warehouse.
• Verifies that the warehouse has been tailored for putback.
• Verifies that the item is coded as an APS planned item.
• Verifies that a Load has been done for the warehouse since the last putback for
the warehouse.
• Determines if any unprocessed order release batches exist in Inventory
Management from any prior putbacks. It terminates if a batch with a workstation
ID of W* is found.

During Putback, an additional check is made to determine if the item being processed
is tailored for the transaction. This edit is accomplished by reading the item
transaction file (OLITMT). If the item is actively interfaced, then the transaction will be
created/updated into XA. If the item is not actively interfaced, then the
record is set to processed and no updates occur in XA.

Putback for manufacturing transactions

Putback for manufacturing orders handles the transactions of create, change, and
cancel. These transactions interface to existing XA applications. The major
change in the PCC interface is that APS is responsible for determining operation
priorities and operation start, end dates, and component required dates. The order
scheduling routines in PCC are not disabled when APS is active, but they are used
only for non-APS planned items and they will not be used on APS planned items.
 Page 2-5
Contents Index
Managing APS

Informational messages are written to the OLIMSG file if information messages have
been selected for the warehouse in Interface Control maintenance. Hard errors, such
as item master missing, item plan missing, etc., are written to the OLIMSG file
regardless of the setting of the information messages field. Such records will have the
OLINFO field in the record set to 2. These messages must be responded to before
the next Load can be run.

Creating manufacturing orders

Manufacturing orders are created by writing records to the IM manufacturing order

entry batch files (ORDATA*). When the order release batch is created for the
manufacturing order creation, the workstation ID is set to W* in the control record
(ORDATC). The W* uniquely identifies the batch as originating from APS’s Putback.

If the Interface Control file record for a warehouse is tailored to release manufacturing
order batches, the entry batch is released once the orders have been processed from
the Review and Approve menu option. If the Interface Control file is not tailored for
automatic release, the batch is set to a suspend status.

During putback, any manufacturing orders created are put into a batch in IM
(ORDATA files). If manufacturing order auto release is turned on in the Interface
Control record for the warehouse, the IM order release function is called to process
the batch after all putback records have been processed. If manufacturing order auto
release is turned off in the Interface Control record for the warehouse, the batch is set
to a Suspended status after all putback records have been processed. A suspended
batch requires the use of IM Order Release and Closeout menu options to process
and release the batch. Use option 1 on IM menu AMIM40 to close the batch and use
option 2 on IM menu AMIM40 to release the batch.

Combining manufacturing orders or item schedules for release on the same

day. For pegging purposes, SCM schedules a separate work order for each demand
for an item. Depending on the item, the work order may be a manufacturing order or
item schedule. Before order release, you can have the APS Bridge combine multiple
orders for an item starting on the same day as long as the total order quantity does
not exceed the item maximum order quantity. The planned orders / schedules are
combined as they are received on the System i before order creation. A combined order
uses the operation priorities and start dates and times from the first order combined.
Combined orders are identified by the literal “Combine” in the order number in the
putback message display and report.

To combine manufacturing orders or item schedules for release on the same day,
enter a 1 in position 15 of the APS Bridge data area APSCTL in AMFLIBy using
CHGDTAARA.

The APS parameters for creating a manufacturing order are item ID, quantity, start
date, and completion date. If an order has been created to replenish safety stock or to
reserve resources for a forecast order, the orders are entered into the batch with the
product structure option equal to REL (Release) and routing option equal to N (No). In
this case the product structure is obtained from EPDM at the time of order release and
the routing is supplied by APS.

If an order has been created for a KBC item, the order is entered into the batch with
the product structure option equal to KEY and a routing option of N (No). In this case
the bill is retrieved from the KBC files and the routing is supplied by APS.
 Page 2-6
Contents Index
Managing APS

Finally, if the order is for a non-KBC item, the order is entered with a product structure
of REL and a routing option of N. In this case the product structure is obtained from
EPDM at the time of order release and the routing is supplied by APS.

In all cases, the order dates and priorities are from the SCM schedule. SCM finitely
schedules operations in drum (critical / bottleneck) work centers by date and time. For
operations in other, non-drum work centers, SCM calculates only a “Don’t Do Before”
date, an approximate, “Don’t Start Before” date, and a Percent Buffer Remaining (the
value SCM suggests to use in prioritizing operations). The Bridge loads the Priority
value in manufacturing order operations with the appropriate SCM data, as new
orders are created and as they are changed, when you process the change
manufacturing order routing transactions.

Priority for drum operations is composed of:

2 positions - the last 2 digits of the year (01 - 99)
3 positions - Julian date (001 - 366)
2 positions - time slot (15 minute period in the workday = 01-96)

Priority for non-drum operations is the Percent Buffer Remaining.

This allows OBPM, PCC, and PMC views, inquiries, and reports to show the work
sequence, as determined by the SCM schedule.
Note: PCC Work List Generation does not update operation priorities for
manufacturing orders scheduled by SCM

Codes that are set for an order are:

• Management Priority code (MPROR) is set to * to designate that the order was
created through APS. The management priority code can be seen when viewing
PCC’s Production Facility Status inquiry and is used to identify an operation that
has been planned by APS as opposed to PCC or FCPS.
• APS flag (GAPS) in the MOMAST file is set either to 3 to identify a safety stock
replenishment order or 1 for all other orders.

Changing manufacturing orders

For orders that are already released, the information that can be changed includes
order start date, order completion date, and order quantity. An expedite message is
issued if the completion date is less than the old completion date. A defer message is
issued if the completion date is greater than the old completion date.

If the order status code is less than 40, the order start date can be changed. If the
order status is less than 50, the completion date can be changed. Quantity changes
are allowed only on status 10 orders. If any change is made to an order, the GAPS
field in the Mfg Order Master file (MOMAST) is set to 1 (planned by APS).

Changing routing operation dates. During putback, operation priorities and dates
may change. APS provides the ability in the putback function to update operation
priorities and start and completion dates as long as the order is still active for
receiving labor transactions. If the operation status is 10 (not started) or 20 (material
moved to the operation) then the scheduled start date can be changed. The
completion date can be changed as long as the operation status is not greater than 30
(activity reported). If one of these dates have changes and are not capable of being
updated due to the order status code setting, the informational message flag is set to
 Page 2-7
Contents Index Exit
Managing APS

2. Component required date is also maintained if the component is used on an

operation whose start date is changed.

Changing component required dates. For components used on orders, their

component required dates may change as operation start dates change. The decision
to change component required dates is based on an unissued quantity remaining in
the component’s MODATA record (QTYREQ less ISQTY is greater
than 0).

If a scheduled operation start date changes, all components on the order that have
the same operation ID will have their required date changed to the new operation start
date.

For components whose Operation Where Used field is blank, their operation start
dates can change if the order start date or completion date changes. If the order start
date changes and the old order start date is equal to the component’s required date,
then the component’s required date is changed to the new order start date. If the
order completion date changes, and the component’s required date does not match
the old order start date (assumes product structure adjusted lead time used to
calculate component required date), then the component required date is changed
plus or minus the number of days the order completion date changes.

Cancelling manufacturing orders

If a manufacturing order generated by the APS interface no longer has a requirement,

a message is issued to cancel the order. The manufacturing order must be at status
10 in order to cancel. If it is at any other status, an informational message will be
issued saying that the order cannot be cancelled.

Creating, changing, and canceling item schedules

For planned orders for schedule-controlled items for a valid production line, APS
Bridge generates an action message that lets you create an unreleased schedule. A
planned order for an invalid production line generates an error message. You can use
current REP function to maintain, release, and/or prime a schedule.

SCM can recommend that released or unreleased schedules be canceled or that the
date, quantity, or production line be changed. APS Bridge generates cancel or change
messages when the change is for a valid production line. A change to a production
line with no item line record generates an error message. APS Bridge generates
change messages that change or cancel a released schedule by changing the
quantity to 0 when processed. Current REP function can also be used to change,
release, and/or prime a schedule. For more information on the APS Bridge REP
interface, see Appendix C.

Putback for purchase transactions

Creating purchase orders and requisitions

APS does not differentiate between purchase orders and requisitions. However, for
purchase orders to be created, the logic will look at the Item Balance auto release
code to determine if the new order should be created as a requisition, purchase order,
or a blanket purchase order. Auto release code 1 relates to requisitions, 2 and 3 relate
to purchase orders, and 4 through 7 relate to blanket purchase orders. To determine if
the order should be released, auto release codes 1 through 3 tag an order for release
 Page 2-8
Contents Index
Managing APS

if the order’s start date is within a firm horizon. Codes 4 through 7 release orders if the
planned order start date is within the firm or authorized horizon, whichever is furthest
in time. For code 0, the requisition or order will not be released.

The start date of the order is determined by subtracting the purchase lead time and
adjustment lead time from the required date. If the order qualifies for release, the
Reference field (REFNO) in POITEM is set to APS, and the Originator code field
(ORGCD) in POMAST is set to A. If a requisition is being created, the Requisitioner
ID field (NAMER) in REQHDF is set to APS.

An expedite exception message is issued if the order’s due date falls within the
horizon of system date plus the item’s total lead time, as stated above. To release the
orders, Putback must be active. APS calls the API that processes releases from IM’s
Reorder Report logic.
Note: When multiple purchase orders or requisitions are to be created for the same
item and same due date, APS consolidates them into only one purchase order or
requisition for the total needed.

Changing and cancelling purchase orders and requisitions

Putback does not change or cancel purchase orders and requisitions. It makes note of
purchase orders that do not have requirements. These orders are loaded from the
engine’s database and given the exception message of CANCEL. You can view
these messages in the Review and Approve Putback Messages option on the APS
Bridge main menu.

Putback for customer orders

Putback for customer orders allows you to update customer orders with the data
currently scheduled in SCM, both the first time the order is scheduled by SCM and
any time the SCM schedule changes.

Regardless of how you receive and enter the customer order into your system, the
first time the customer order is scheduled by SCM, the promised or (scheduled)
shipment date is always stored in the original manufacturing due date in the order line
item.
• If you use Capable To Promise (CTP) in order entry and enter the order with the
date promised by SCM, the promised / scheduled shipment date is stored during
order entry in both the original and the latest manufacturing due dates. The
promised delivery date at the customer site is stored in both the original and the
latest promise dates. See Capable To Promise (CTP) later in this section for more
information about using CTP.
• In all other cases, the promised / scheduled shipment date is stored in the original
manufacturing due date during Putback in the first scheduling cycle after the order
is entered. A scheduling cycle includes Load, SCM Schedule, and Putback.

You can also choose to have the SCM promised shipment date stored in the latest
manufacturing due date and the promised delivery date stored in the latest promise
date. These dates are normally used in the customer order, such as for customer
order acknowledgements.

You can choose to have these fields updated the first time the order is scheduled by
SCM or every time the SCM schedule changes. The two dates are both updated
using the promised /scheduled date from SCM. The SCM scheduled date is the
 Page 2-9
Contents Index
Managing APS

manufacturing due / shipment date. The SCM schedule date plus the customer ship
lead time is the promised /delivery date. See Customer Orders later is this chapter for
instructions on how to make changes using the APS Bridge APSCTL data area.

Review and Approve Putback messages

Putback messages are meant to be very informative to users. They tell the user when
an action has been taken, needs to be taken, or if any errors have occurred against a
manufacturing, purchase or customer order.

Putback informational messages that require no action have the IMINFO flag in the
putback message file (OLIMSG) set to 0. Putback messages that require action have
the IMINFO flag set to 1. Putback error messages have the IMINFO flag set to 2 and
always require action.

If the transaction action flag is set on (1) in the putback transaction, errors
encountered during the processing of the putback request from the engine are always
written to the putback message file, regardless of the state of the informational
message flag.

Putback messages are reviewed by warehouse using option 5, “Review and Approve
Putback Messages”, on the APS Bridge main menu. When you select a warehouse,
all putback messages are displayed for the warehouse. By using F17, the subset
function key, you can subset to look at more specific information.

Messages can be subsetted, deleted, and printed from the putback message panel.
Subsets can be based on message number (blank, 0, or 1), automatic posting code
(blank, 0, or 1), transaction ID, item number, order number, and planner number.

Forecasts
When you load data to APS (APS Menu AXAM00, Option 3), forecasts are loaded
from the Period Forecast file.

If XA Forecasting (FCST) is installed, forecasts are loaded to the Period

Forecast file when you run the Forecast Load to Master Schedules menu option
(FCST Menu AM2M20, Option 5). Whether or not FCST is installed, you can add or
maintain the forecasts in the Period Forecast file via the Period Forecast Offline Load
(APS Menu AXAM01, Option 6). When data is loaded to APS, only forecasts for items
planned by APS are sent. Appendix A has the file format for the Period Forecast
Offline Load file.

SCM can optionally consume forecasts with customer orders. As XA forecasts

must be consumed, the Bridge instructs SCM to consume the forecasts if
FCST is installed. If FCST is not installed, you must specify whether SCM should
consume the forecasts in Interface Control Maintenance (APS Menu AXAM01, Option
1).

Customer Orders
During customer order entry, if you request promised delivery dates (also called
promise dates), they are determined by the application that plans an item. You can
specify what application plans an item in the Planned by field in the Item Warehouse
 Page 2-10
Contents Index
Managing APS

object. If an item is planned by MRP, Available To Promise (ATP) supplies the promise
date. If an item is planned by APS (SCM), Capable To Promise (CTP) supplies the
promise date.

CTP lets you provide realistic, capacity and material tested, promise dates based on
the current SCM plan/schedule. You can request a CTP on an item planned by APS
providing the customer order is not held/filtered from APS planning, and the APS
schedule is loaded into memory after APS scheduling. CTP determines the earliest
date the requested quantity of the item can be delivered to the customer, either by
consuming available forecast, or by scheduling available capacity. If the item is then
ordered with the CTP promise date, a reserved order is entered in the SCM database
to prevent double-booking the forecast or capacity in future CTP requests.

CTP order promising is performed “non-disruptively,” meaning that SCM does not
completely schedule the new customer order. Complete scheduling, including any
additional required manufacturing and purchase orders, is done in the next APS
planning session.

Checking purchased material in CTP

CTP checks the availability of all manufactured items required for the item ordered,
but only purchased items identified in SCM as hard constraints. This is the default
option used by the SCM Customer Service Workbench (CSW). You can change this
option, as it is stored in position 14 of the APS Bridge data area APSCTL. The valid
settings are listed below:

Value Description
Blank / 0 Look at hard material constraints only
1 Ignore all purchased materials
2 Look at all purchased materials

This data area is in the AMFLIB, and if authorized, you can view the data area using
the DSPDTAARA command and change the option by using the CHGDTAARA
command to change the contents of position 14.
Note: Only the two values listed above are valid. CTP will not run with any
other value.

CTP for KBC items

Each customer order entered for a KBC item generates a new configuration of the
item. The Bridge defines each configuration as a unique part to SCM. When
requesting a CTP, it first sends the newly defined part (identified by appending an
APS assigned sequence number to the item number), and its associated bill and
routing, and bills and routings for any lower level parts defined in the configuration, so
SCM can accurately assess the request. CTP requests for KBC items therefore takes
longer than CTP requests for other items.
 Page 3-1
Contents Index Exit
Installing the APS Bridge Server

Chapter 3. Installing the APS Bridge Server

This chapter contains general information about installing the APS Bridge. A ReadMe
file is available on the CD with more detailed information about this process.

You must install the SCM application before beginning this installation. Use the SCM
documentation for information about installing that application.
Installing the APS Bridge Server .............................................................................. 3-1
Using File Transfer Protocol (FTP) ........................................................................... 3-2
Using Client Access Remote Command (RUNRMTCMD) ....................................... 3-2
Installing the Client Interface .................................................................................... 3-3
Starting CTP Listener ............................................................................................... 3-3
APS Bridge implementation considerations ............................................................. 3-4

Installing the APS Bridge Server

1. Log on to a Windows NT 4.0 machine as a user with Administrator privileges.

2. Insert the APS Bridge CD or diskette into the appropriate drive. The installation will
start automatically. You will need to respond to the prompts as you proceed.

3. If the installation does not start automatically, select Run from the Windows Start
menu and enter:
x:setup (where x: is the letter ID of the drive containing the CD or diskette)

4. The Welcome/Warning screen is displayed. Select Next to continue.

5. The License notification screen is displayed. Select Next to continue.

6. The Default folder location is displayed. This location defaults to the location where
SCM is installed. The recommendation is that you use this default. Select Browse to
change the location from the default directory. Select Next to continue.
Note: Setup will look for the SCM [Link] file in the directory specified. If the
config file cannot be found, an error message will be returned.

7. The Default location for the download directory is displayed. This location defaults
to the sample database directory under the main SCM directory. This directory
specifies where your download format files will be placed and will be reflected in your
SCM [Link] configuration file as the Input File Directory parameter. The name of
the download directory is needed during Interface Control maintenance. Select
Browse to change the directory location. Select Next to continue.
Note: If the [Link] is found to be already set with the correct parameters,
then selecting Next will actually perform the install per your selections. If you do
not want to continue, click the Cancel button.

8. The Configuration File Modification window is displayed. All required modifications

to the SCM [Link] file are listed in the scrollable panel at the top. You can use the
radio buttons to select what to do. If you select the first option (Modify), the Setup will
modify the SCM [Link] file. (This is the recommended choice.) If you select the
second option (Save the changes to an alternate file), the Setup will save the required
 Page 3-2
Contents Index
Installing the APS Bridge Server

modifications to the file indicated in the main SCM directory. If you select the third
option (No changes), the Setup will do nothing concerning these parameters.
Note: Selecting Next will perform the install per your selections. If you do not
want to continue, click the Cancel button.

9. The Complete Setup screen is displayed. Select Finish.

Using File Transfer Protocol (FTP)

Microsoft Peer Web Services or another FTP service must be installed for FTP to
work. For Microsoft Peer Web Services, use Internet Service Manager to enter an
FTP user profile as follows:
1. Right click on the ‘FTP’ line and select ‘Service Properties’
2. Turn off the ‘Allow only anonymous connections’ on the ‘Service’ panel
3. Select ‘Apply’
4. Go to the ‘Directories’ panel and modify or enter the ‘C:’ directory as the <Home>
directory
5. Insure that both read and write access are on
6. Select ‘Apply’ and then ‘OK’.

For another FTP service, follow the instructions for that service to enter an FTP user
profile.

Using Client Access Remote Command (RUNRMTCMD)

You must start the ‘Client Access Remote Command’ on the server. Go to the Control
Panel and select ‘Services’. Make the start automatic, and it will start each time the
system is booted. You will need administrative authority to do this.

If RUNRMTCMD will not work from the System i to the APS Bridge server, you will need
to change a byte in the IBM Client Access ‘Share Network’ security field. It can be
changed by clicking on START and then clicking on RUN. Type in REGEDIT and click
OK. This will bring up the Registry Editor. Use the mouse and point to and click on the
‘+’ box of the following directories:
HKEY_LOCAL_MACHINE
SOFTWARE
IBM
Client Access
Current Version
Internal_Components

Double click on the Security folder to show the contents and then double click on
ShareNetwork inside the folder. This will bring up the Edit DWORD Value box.
Change the highlighted ‘0’ to ‘1’ and click OK.
Note: This is not required if you are using Client Access Express.

Verifying special characters for RUNRMTCMD

You must verify several special characters for RUNRMTCMD to work properly. These
characters are:
 Page 3-3
Contents Index
Installing the APS Bridge Server

• Forward slash ( / )
• Back slash ( \ )
• Colon ( : )

To verify the character sets, you meed to find the following Object Names and
Sequence Numbers (through DFU or another utility program). Update the special
characters if necessary.
• The control for the Forward slash ( / ) is under the object WISDOM and Sequence
Number 047.
• The control for the Back slash ( \ ) is under the object WISDOM and Sequence
Number 048.
• The control for the Colon ( : ) is under the object WISDOM and Sequence Number
049.

Installing the Client Interface

1. Log on to a Windows 95/98 or Windows NT 4.0 machine as a user with
Administrator privileges.
2. Insert the APS Bridge CD in the CD-ROM drive. The “APS Bridge Installs” dialog
should appear automatically.
3. Click the Install APS Bridge Client Interface button.
If the “APS Bridge Installs” dialog did not appear when you inserted the CD, select
Run from the Windows Start menu and enter:
d:\client\[Link] (where d: is the letter of your CD-ROM drive)
4. Enter a destination directory and choose a Programs folder as prompted by the
setup program.
5. Answer the remaining setup questions. When the installation is complete, you
must restart the PC before running the software.
Note: For security reasons, you should not give all users the ability to maintain
items, bills and routings.

Starting CTP Listener

Following are the steps needed to create a [Link] file for using the CTP function.
More detailed information is available in the ReadMe file on the CD.
1. Configure server in SCM for each planning warehouse (plant) that should be
extracted:
a. Run SCM Manufacturing Admin from the START menu on NT.
b. Choose the “Create, Modify, or Remove Server” option on the first screen that
appears.
c. Choose the “Create” option on the next screen.
d. For the “Name of application server” field, enter the planning warehouse
identifier you want to extract from in XA.
 Page 3-4
Contents Index
Installing the APS Bridge Server

e. For the “Location of application server” field, take the Browse button and find
the “TP-Manufacturing 5.1” directory (or whatever you changed the default to)
and select the “[Link]” file.
f. For the “Configuration” entry field, take the Browse button and find the “TP-
Manufacturing 5.1” directory (or whatever you changed the default to) and
select the “[Link]” file.
g. Enter the name and password of Administrator for this machine.
h. Enter the database parameters and click “Finish”.
2. Start SCM server via the following command (create a [Link] file for ease of
restart) from the TP-Manufacturing 5.1 directory.
resonance -n(server ID) -u(user) -p(password) /ResServer
where (server ID) is the server you created in Step 1, and (user) and (password)
are the Administrator name and password from Step 1.
Note: Do not use parentheses in the actual command.

APS Bridge implementation considerations

Before going live with SCM and the APS Bridge, consider the following checklist for
activities. This list is not defined in order of importance, nor is it all-inclusive.
• You should be proficient in networking systems; i.e., System i and Windows NT
connectivity.
• You should attend education classes for SCM and the APS Bridge.
• Ideally, all items should be planned in APS. The only time items should be
planned in MRP is if the product lines being planned have totally unique items and
resources. Otherwise, APS will not have a view of all the resources that need to
be planned.
• Run Loads (extracts) multiple times as part of the implementation and training
process. A Load may not complete if an error condition is found. You need to find
the source of errors and correct these conditions before going live. Use the audit
reports from the Load that are in your spool file on the System i, as well as the
import log you can view in the Review Load Messages option on the APS Bridge
main menu to help you locate errors.
• Define hold code filters early in your setup. When a hold code filter is added, it will
be recognized in the next Load.
• Use the Tips document found in the ReadMe file on the APS Bridge CD for a
definitive checklist for initial installation of this product.

Additional setup information

If you have the latest ODBC drivers, and elect to create your own MS Access
database instead of using the default (TPMAN), you can select one of the following
format versions:
• 2.x
• 3.x

Do not use version 4.x as errors can occur.

 Page 3-5
Contents Index
Installing the APS Bridge Server

Scheduling output

Define the Output Horizon for Schedules parameter found under the Scheduling
Output button on the System Configuration display for Synchronize Engine. This
horizon, measured from system date in terms of days, must be at least as long as the
longest cumulative material lead-time plus an allowance to review purchase orders. If
manufacturing orders have operations beyond this horizon, those operations are not
scheduled, and therefore, cannot be released in XA.

Purchase items that are “transaction active” with an auto-release code other than 0
must have a firm and/or authorized time fence horizon in the Item Balance file.

Windows NT Server profile are a maximum of ten characters long; passwords are
only a maximum of ten characters long.
 Page 3-6
Contents Index
Installing the APS Bridge Server
 Page 4-1
Contents Index
Using the APS Bridge

Chapter 4. Using the APS Bridge

This chapter contains information about using the options on the APS Bridge Main
Menu. The APS Bridge is called from the XA Application Selection menu
by typing its option number or APS on the command line.
Option 1 (AXAM00). Maintenance ............................................................................ 4-2
Option 2 (AXAM00). Inquiry.................................................................................... 4-34
Option 3 (AXAM00). Initiate Load/Putback............................................................. 4-38
Option 4 (AXAM00). Review Load Messages ........................................................ 4-45
Option 5 (AXAM00). Review and Approve Putback Messages.............................. 4-49

$;$0 $36 %ULGJH

 0DLQ 0HQX

7\SH RSWLRQ RU FRPPDQG SUHVV (QWHU

 0DLQWHQDQFH !!
 ,QTXLU\ !!
 ,QLWLDWH /RDG3XWEDFN
 5HYLHZ /RDG 0HVVDJHV
 5HYLHZ DQG $SSURYH 3XWEDFN 0HVVDJHV

) ([LW ) 3URPSW ) 5HWULHYH ) $FWLRQV

) -RE VWDWXV ) 5HWXUQ ) 0HVVDJHV

Option 1. Maintenance. Use this option to perform maintenance functions in the

interface. A secondary menu appears so you can choose the type of maintenance you
want to perform.
Option 2. Inquiry. Use this option to perform inquiry functions in the interface. A
secondary menu appears so you can choose the type of inquiry you want to display.
Option 3. Initiate Load/Putback. Use this option to begin either the load server or
putback process.
Option 4. Review Load Messages. Use this option to review messages issued
during the load server process.
Option 5. Review and Approve Putback Messages. Use this option to work with
messages generated during the putback process.
 AXAM00, option 1
Page 4-2
Contents Index
Using the APS Bridge

Option 1 (AXAM00). Maintenance

Use this menu to select the type of maintenance in the APS Bridge you want to
perform.

$;$0 $36 %ULGJH

 0DLQWHQDQFH

7\SH RSWLRQ RU FRPPDQG SUHVV (QWHU

 ,QWHUIDFH &RQWURO
 +ROG &RGH )LOWHUV
 &XVWRPHU 2UGHU %DFNORJ 2IIOLQH /RDG
 3HULRG )RUHFDVW 2IIOLQH /RDG
 3XWEDFN 7UDQVDFWLRQ 7DLORULQJ 2IIOLQH /RDG
 3XWEDFN 7UDQVDFWLRQ 7DLORULQJ

! BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB

) ([LW ) 3URPSW ) 5HWULHYH ) $FWLRQV

) -RE VWDWXV ) 5HWXUQ ) 0HVVDJHV

Option 1. Interface Control. Use this option to maintain the APS Interface Control
file (OLSYSC) that controls the XA to APS Interface. The control file
defines by warehouse where the APS data files should reside and defines the path
used to load files to the APS engine. The bridge tailoring questions also are answered
here.
Option 2. Hold Code Filters. Use this option to filter out, within a specific warehouse
and hold code, specified customer orders that are on hold in XA. This
option is valid only if COM is installed and active.
Option 3. Customer Order Backlog Offline Load. Use this option to load customer
backlog information from a source other than COM.
Option 4. Period Forecast Offline Load. Use this option to load forecasting
information from a source other than XA.
Option 5. Putback Transaction Tailoring Offline Load. Use this option to mass
maintain putback transactions from an outside source.
Option 6. Putback Transaction Tailoring. Use this option to define what putback
transactions are active. Transactions can be subsetted by a particular item, item
class, lead time code, or value class.
 AXAM01, option 1
Page 4-3
Contents Index
Using the APS Bridge

Option 1 (AXAM01). Interface Control

Use this option on the APS Bridge Maintenance menu to access the Interface Control
panels that allow you to define by planning warehouse where the APS data files
reside and to add, change, and delete information used by APS during the load server
and putback processes.

You will need to have completed installation of the APS Server and created a
database there before you begin your Interface Control task.

Enter the control information you want to use on the following panels. These control
selections remain in effect until changed here.
What information you need: Server and warehouse information.
What reports are printed: None.
 AXAM01, option 1
Page 4-4
Contents Index
Using the APS Bridge

MO0550—Interface Control (Select)

Use this panel to select the action and planning warehouse you want to work with in
the interface control file. You must be authorized to the selected warehouse in order to
perform maintenance for that warehouse.

This panel appears when you use choose option 1 on the APS Bridge Maintenance
menu (AXAM01).

'DWH   $36 %ULGJH 02

 ,QWHUIDFH &RQWURO 0DLQWHQDQFH

7\SH RSWLRQV SUHVV (QWHU 3RVLWLRQ WR QQQ

 &KDQJH  'HOHWH  'LVSOD\

6HO :KV 'HVFULSWLRQ

Q
Q
Q
Q
Q
Q
Q
Q
Q
Q
Q
Q


) ([LW ) 5HIUHVK ) &UHDWH

What to do

To change, delete, or display information, type the option number you want to use
beside the appropriate warehouse and press Enter. To add a new interface control
record, use F6. The first panel of Control File information appears so you can begin
maintaining information.

Function keys

F3=Exit causes the APS Bridge Maintenance menu (AXAM01) to appear.

F5=Refresh causes the panel to appear as it originally appeared and removes any
selections you have made.

F6=Create causes the first of two panels to appear so you can add a new warehouse
control record.

Fields

Position to. Type the identifier of the warehouse where you want the list to begin.
 AXAM01, option 1
Page 4-5
Contents Index
Using the APS Bridge

Sel. Type one of the following options to indicate the action you want to take beside
the warehouse you want to use:
2 Change information for this warehouse.
4 Delete information for this warehouse.
5 Display information for this warehouse.
 AXAM01, option 1
Page 4-6
Contents Index
Using the APS Bridge

MO0551—Interface Control (Page 1 of 2)

Use this panel to maintain or view the Interface Control File information.

This panel appears when you use F6 or select an action and press Enter on panel
MO0550. It also appears when you use Rolldown on panel MO0552.
Note: When this panel appears in Display or Delete mode, the fields are not input-
capable.

'DWH   $36 %ULGJH 02

,QWHUIDFH &RQWURO 0DLQWHQDQFH

:DUHKRXVH D$ # 3DJH  RI 

$36 VLJQRQ      DDDDDDD$

$36 SDVVZRUG     DDDDDDD$ &DVH VHQVLWLYH
$36 GLUHFWRU\     BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
'LUHFWRU\ DOLDV      BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
'DWD VRXUFH QDPH    BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB

,3 DGGUHVV       QQQ  QQQ  QQQ  QQQ

'RZQORDG GLUHFWRU\    DDDDDDDDDDDDDDDDD$

0IJ RUGHU DXWR UHOHDVH   Q  1R  <HV

5HOHDVH KRUL]RQ      QQ
3ULQW DXGLW UHSRUWV     Q  1R  $OOGHWDLOV (UURUVRQO\ 


) ([LW ) &DQFHO  ) $XGLW  ) 1/6GDWD  5ROOXS

What to do
• To change or create a warehouse control record, type in the information
requested and press Enter. The next panel appears so you can continue
maintaining information.
• To delete a warehouse control record, after confirming this is the correct record,
press Enter. The Select panel appears again.
• To see the second page of information, use Rollup. The next panel appears so
you can continue viewing information.

Function keys

F3=Exit causes the APS Bridge Maintenance menu (AXAM01) to appear.

F12=Cancel causes the Interface Control Maintenance Select panel (MO0550) to

appear without processing the entries you made.

F14=Audit causes the Audit window to appear so you can see the date, time, and
user who created and changed this record. This function key does not appear when
you are creating a new record.
 AXAM01, option 1
Page 4-7
Contents Index
Using the APS Bridge

F16=CCSID parms causes the CCSID Parameter Maintenance panel (MO0553) to

appear so you can review/modify the parameters used by FTP (File Transfer Protocol
client application) for transferring files to and from a remote system and by the
RUNRMTCMD to run programs on the server. These parameters are used for
translating characters that are used in countries outside the U.S.

Fields

[?] appears next to a field name in the following field definitions to identify a field from
which you can begin a master file search.

Warehouse [?]. The XA warehouse you selected on the previous panel. If

you are creating this record, the warehouse must be a valid warehouse defined in XA.
The warehouse description is also displayed.

APS signon. Your APS Server signon identifier. This should be your normal userid.

APS password. Your APS Server password. Note that this field is case-sensitive.
The entry you make does not display.

APS directory. The identifier (and path) of the directory on the server where APS is
installed. If the directory name is greater than eight (8) characters long, you must use
the MS-DOS name. For example, APS01.05.01.00Server would become APS~[Link].
On the server, you can retrieve the MS-DOS name by right clicking on the folder and
retrieving the properties of the folder.

Directory alias. The identifier defined and used by FTP to locate the directory named
in the previous field. This field is required when that directory does not reside on the
C: drive. The entry must begin with / (forward slash).

Data source name. The identifier assigned to the data source.

IP (Internet Protocol) address. The IP address on the Server where APS is

installed. This field is required. This can be retrieved by entering the command
IPCONFIG on the MS-DOS command prompt window on the server.

Download directory. The name of the APS directory you created on the Server for
this warehouse during the install of the APS Bridge server.

Mfg order auto release. One of the following:

0 No. Do not use auto release for manufacturing orders. The IM order entry
batches that are populated with create manufacturing order messages during
putback will be placed in Suspend mode.
1 Yes. Use auto release for manufacturing orders. The IM order entry batches
that are populated with create manufacturing order messages during putback
will be released automatically.

Release horizon. The number of days to use for the release horizon for
manufacturing orders.
 AXAM01, option 1
Page 4-8
Contents Index t
Using the APS Bridge

Print audit reports. One of the following to indicate if you want audit reports printed
during the Load process:
0 No. Do not print audit reports.
1 All details. Print complete load reports listing all records processed in the load
to SCM with an error message for any record not sent.
2 Errors only. Print only error records and the message for the error.
 AXAM01, option 1
Page 4-9
Contents Index
Using the APS Bridge

MO0552—Interface Control (Page 2 of 2)

Use this panel to continue to maintain or view the Interface Control File information.

This panel appears when you press Enter or use Rollup on panel MO0551.
Note: When this panel appears in Display or Delete mode, the fields are not input-
capable.

'DWH   $36 %ULGJH 02

,QWHUIDFH &RQWURO 0DLQWHQDQFH

:DUHKRXVH # 3DJH  RI 

'D\V WR DXWR UHVFKHGXOH     QQQ

3XWEDFN DOORZHG       Q  1R  <HV
,JQRUHHUURUVGXULQJ/RDG6HUYHU   Q  1R <HV
&RQVXPHIRUHFDVW       Q  1R <HV

/RQJUXQQLQJRSHUDWLRQVOLPLW     KRXUV

/DVW VHUYHU ORDG           

/DVW SXWEDFN           

) ([LW ) &DQFHO ) $XGLW 5ROOGRZQ

What to do

To continue changing or creating a warehouse control record, type in the information

requested and press Enter. Panel MO0550 appears so you can make another
selection or end the job.

Function keys

F3=Exit causes the APS Bridge Maintenance menu (AXAM01) to appear.

F12=Cancel causes the Interface Control Maintenance Select panel (MO0550) to

appear without processing the entries you made.

F14=Audit causes the Audit window to appear so you can see the date, time, and
user who created and changed this record. This function key does not appear when
you are creating a new record.

Fields

Warehouse. The XA warehouse you selected on the previous panel. The

warehouse description is also displayed.
 AXAM01, option 1
Page 4-10
Contents Index
Using the APS Bridge

Days to auto reschedule. The minimum days to reschedule is used during the
Putback process to avoid generating messages and updates when the difference
between the original date and the new date is less than the number of days specified
here.

Putback allowed. One of the following to indicate whether or not XA files

can be updated by actions taken on the APS engine:
0 No, putback is not allowed.
1 Yes, putback is allowed.

Ignore errors during load server. One of the following to indicate whether or not
XA ignores errors during server load.
0 No, error records are not sent to SCM. (Default).
1 Yes, errors are ignored and all records for items planned by SCM are sent.

Consume forecast. This field appears only if FCST is not installed. One of the
following to indicate whether or not the forecast should be consumed by the APS
engine.
0 No, do not consume forecast.
1 Yes, consume forecast.

Long running operations limit. Manufacturing order operations with runtime per
piece equal to or greater than this value are considered long running operations and
have records written to the SCM Jobs in Progress file when the operation is in
progress. See Appendix B for information on MOROUT mapping to Jobs in Progress.

Last server load. The date and time of the last server load.

Last putback. The date and time of the last putback.

 AXAM01, option 1
Page 4-11
Contents Index
Using the APS Bridge

MO0553—Interface Control CCSID Parameters (1 of 2)

Use this panel to maintain or view the Interface Control Coded Character Set Identifier
(CCSID) parameters used by the File Transfer Protocol client application (FTP) for
transferring files to and from a remote system and by the Run Remote Command
(RUNRMTCMD) to run programs on the server. These parameters are used for
translating characters that are used in countries outside the U.S.

The shipped defaults are shown in this example. See the online help when you use
the STRTCPFTP (Start TCP/IP File Transfer) and RUNRMTCMD (Run Remote
Command) commands for more detailed information.

This panel appears when you press F16 on panel MO0551.

'DWH   $36 %ULGJH 02

,QWHUIDFH &RQWURO 0DLQWHQDQFH

:DUHKRXVH 3DJH RI

)73 6757&3)73 SDUDPHWHUV

&RGHG FKDUDFWHU VHW LGHQWLILHU ')7  ')7

2XWJRLQJ (%&',&$6&,, WDEOH    &&6,' 1DPH &&6,' ')7

/LEUDU\             1DPH /,%/ &85/,%
,QFRPLQJ $6&,,(%&',& WDEOH   &&6,' 1DPH &&6,' ')7
/LEUDU\            1DPH /,%/ &85/,%

5XQ 5HPRWH &RPPDQG 581507&0' SDUDPHWHUV

&RGHG FKDUDFWHU VHW ,'      &$/&  &$/&

) ([LW ) &DQFHO ) $XGLW

What to do

To change the defaults shown, type in the new information and press Enter. Panel
MO0551 appears again so you can continue or end the job.

Function keys

F3=Exit causes the APS Bridge Maintenance menu (AXAM01) to appear.

F12=Cancel causes the Interface Control Maintenance Select panel (MO0550) to

appear without processing the entries you made.

F14=Audit causes the Audit window to appear so you can see the date, time, and
user who created and changed this record. This function key does not appear when
you are creating a new record.
 AXAM01, option 1
Page 4-12
Contents Index
Using the APS Bridge

Fields

Warehouse. The XA warehouse you selected on the previous panel. The

warehouse description is also displayed.

FTP (STRTCPFTP) parameters:

Coded character set identifier. Accept the default or type in a valid identifier. This is
the identifier that is used for single-byte character set (SBCS) ASCII file transfers
when the FTP TYPE mode is set to ASCII. This value is used by the FTP client for
ASCII-to-EBCDIC and EBCDIC-to-ASCII mapping. The possible values are:
*DFT The CCSID value 00819 (ISO 8859-1 1-bit ASCII) is used.
1-65533 The user-defined CCSID value. This must be a valid SBCS CCSID value.

Outgoing EBCDIC/ASCII table. Accept the default or type in a valid table name. This
specifies the table object that is to be used to map all outgoing data in the FTP client
from EBCDIC to ASCII. The possible values are:
Name The user-defined name of the table object.
*CCSID The CCSID parameter is used to determine outgoing mapping.
*DFT The CCSID parameter is used to determine outgoing mapping.

Library. Accept the default or type in a valid library name to be searched for the table
object entered in the previous field. The possible values are:
Name The user-defined name of the library.
*LIBL All libraries in the user and system portions of the job’s library list are
searched until the first match is found.
*CURLIB The current library for the job is searched. If no library is specified as the
current library for the job, the QGPL library is used.

Incoming ASCII/EBCDIC table. Accept the default or type in a valid table name. This
specifies the table object that is to be used to map all incoming data in the FTP client
from ASCII to EBCDIC . The possible values are:
Name The user-defined name of the table object.
*CCSID The CCSID parameter is used to determine incoming mapping.
*DFT The CCSID parameter is used to determine incoming mapping.

Library. Accept the default or type in a valid library name to be searched for the table
object entered in the previous field. The possible values are:
Name The user-defined name of the library.
*LIBL All libraries in the user and system portions of the job’s library list are
searched until the first match is found.
*CURLIB The current library for the job is searched. If no library is specified as the
current library for the job, the QGPL library is used.

Run Remote Command (RUNRMTCMD parameters:

Coded character set identifier. Accept the default or type in a valid identifier. This
specifies the identifier that is used for conversion. When data is sent to the remote
system, the data is converted using the CCSID of the job to the CCSID specified on
this parameter. Similarly, when data is received from the remote system, the data is
converted from the CCSID that was specified on this parameter to the CCSID of the
job. The possible values are:
1-65533 The user-defined CCSID value. This must be a valid CCSID value.
 AXAM01, option 1
Page 4-13
Contents Index
Using the APS Bridge

*CALC The CCSID value sent from the target system is used if it is available. If a
value is not provided from the target system, a default value of 00819
(ISO 8859-1 8-bit ASCII) is used.
 AXAM01, option 1
Page 4-14
Contents Index
Using the APS Bridge

MO0554—Interface Control CCSID Parameters (2 of 2)

Use this panel to continue to maintain or view the Interface Control Coded Character
Set Identifier (CCSID) parameters.

This panel appears when you press Enter or use Rollup on panel MO0553.

'DWH   $36 %ULGJH 02

,QWHUIDFH &RQWURO 0DLQWHQDQFH

:DUHKRXVH   3DJH RI

%ODQNUHSODFHPHQWFKDUDFWHUV
,QLWLDOFKDUDFWHU      
,WHPQXPEHU      
2UGHUQXPEHU     
:RUNFHQWHU        

3&'26SDWKVSHFLDOFKDUDFWHUV
&KDUDFWHUDIWHUGULYHOHWWHU   
'LUHFWRU\VHSDUDWRU '26    ?
 'LUHFWRU\VHSDUDWRU )73      

) ([LW ) &DQFHO ) $XGLW 5ROOGRZQ

What to do

To continue to change the defaults shown, type in the new information and press
Enter. Panel MO0551 appears again so you can continue or end the job.

Function keys

F3=Exit causes the APS Bridge Maintenance menu (AXAM01) to appear.

F12=Cancel causes the Interface Control Maintenance Select panel (MO0550) to

appear without processing the entries you made.

F14=Audit causes the Audit window to appear so you can see the date, time, and
user who created and changed this record. This function key does not appear when
you are creating a new record.

Fields

Warehouse. The XA warehouse you selected on the previous panel. The

warehouse description is also displayed.

Blank replacement characters. Type a character to be used for replacing the

embedded blanks in key fields. In order to transfer data from XA and back,
APS Bridge must replace embedded blanks with some other character. The key fields
that are affected are Item Number, Order Number, and Work Center. You can specify
a different replacement character for each of these fields. When possible, use
 AXAM01, option 1
Page 4-15
Contents Index
Using the APS Bridge

replacement characters that are not already used in the data. A record is kept of the
original value and the value as it was sent to SCM and is used to convert data when it
is received from SCM.
Initial character. If a blank replacement character is used in a key field, specify an
initial replacement character, such as #, so the system can find and
replace all occurrences of the replacement character in the field before
replacing blanks.
Item number. Enter a character for the blank replacement character in this field.
Order number. Enter a character for the blank replacement character in this field.
Work center. Enter a character for the blank replacement character in this field.

PC DOS path special characters. The characters used to define a PC DOS or FTP
path include special characters that can be different from one country to another. In
order for APS Bridge to locate data on a remote system, specify the correct
characters used in the DOS or FTP path.
Character after drive letter. Specify the character used after the drive letter in the
DOS path.
Directory separator (DOS). Specify the character used as a directory separator in
the DOS path.
Directory separator (FTP). Specify the character used as a directory separator in the
FTP path.
 AXAM01, option 2
Page 4-16
Contents Index
Using the APS Bridge

Option 2 (AXAM01). Hold Code Filters

Use this option anytime you need to create or delete a COM Hold Code filter. These
codes are used to filter out customer orders and/or line items that are on hold within a
specific warehouse in XA when orders are being loaded into APS.
Note: You must have the proper security authorization to work with the specific
warehouse.

This option is valid only when COM is installed. The hold code must be defined
already in COM.
What information you need: Warehouse identifier and hold code.
What reports are printed: None.

The basic steps for performing this task follow each panel.
 AXAM01, option 2
Page 4-17
Contents Index
Using the APS Bridge

MO0640—Hold Code Filters (Select)

Use this panel to select the warehouse and code you want to delete, or use F6 to
access a panel that allows you to create a new hold code by warehouse.

This panel appears when you use choose option 2 on the APS Bridge Maintenance
menu (AXAM01).

'DWH   $36 %ULGJH 02

+ROG &RGH )LOWHUV
7\SH LQIRUPDWLRQ SUHVV (QWHU 3RVLWLRQ WR D$ $
 'HOHWH

+ROG &UHDWH
6HO :KV &RGH 'HVFULSWLRQ    &UHDWHG %\ 'DWH
Q        
Q     
Q    
Q    
Q    
Q    
Q     
Q     
Q     
Q     
Q     
Q      

) ([LW ) 5HIUHVK ) &UHDWH 5ROOXSGRZQ

What to do
• To delete a hold code, type 4 beside the appropriate warehouse and code and
press Enter. You must be authorized to work with the warehouse. A panel
appears to allow you to confirm your selection or to cancel the request.
• To create a new hold code, use F6. Another panel appears so you can add the
warehouse and code. The warehouse must be defined already in the XA
Warehouse Master file. The code must be defined already in the COM Hold
Code file. When you have added the new code, return to this panel and use F5 to
see the new entry.

Function keys

F3=Exit causes the APS Bridge Maintenance menu (AXAM01) to appear.

F5=Refresh causes the list to be refreshed with any new entries or deletes you have
made.

F6=Create causes another panel to appear so you can add a new warehouse and
hold code record.
 AXAM01, option 2
Page 4-18
Contents Index
Using the APS Bridge

Fields

Position to. Type the identifier of the warehouse and hold code where you want the
list to begin.

Sel. Type 4 beside the warehouse and code you want to delete.
 AXAM01, option 2
Page 4-19
Contents Index
Using the APS Bridge

MO0641—Hold Code Filter

Use this panel to add a warehouse and hold code for which you want to filter out
customer orders that are on hold in XA. The warehouse must be defined
already in the XA Warehouse Master file. The code must be defined
already in the COM Hold Codes file. Use this panel also to confirm the delete
selection you made on the Select panel.

This panel appears when you use F6 on the Hold Code Filters Select panel. It also
appears in display mode only for you to confirm deletion of a hold code you selected
on the Select panel.

'DWH   $36 %ULGJH 02

+ROG &RGH )LOWHU

:DUHKRXVH D$

+ROG &RGH $

) ([LW ) 5HWXUQ ) $XGLW

3UHVV (17(5 WR GHOHWH ) WR FDQFHO

What to do
• To add a new hold code, type in the warehouse and hold code and press Enter.
You are prompted to press Enter a second time. Then use F12 to return to the
previous panel and use F5 on that panel to see the new entry.
• To confirm deletion, press Enter. If you decide not to delete, use F12 to return to
the previous panel.

Function keys

F3=Exit causes the APS Bridge Maintenance menu (AXAM01) to appear.

F12=Return causes the Select panel to appear.

F14=Audit appears in Confirm mode only and causes the Audit window to appear so
you can see the date, time, and user who created and changed this record.
 AXAM01, option 2
Page 4-20
Contents Index
Using the APS Bridge

Fields

[?] appears next to a field name in the following field definitions to identify a field
from which you can begin a master file search.

Warehouse [?]. The warehouse identifier. This must be a valid warehouse defined in
XA Warehouse Master.

Hold code [?]. The hold code identifier. This must be a valid hold code defined in
XA COM Hold Code files.
 AXAM01, option 3
Page 4-21
Contents Index
Using the APS Bridge

Option 3 (AXAM01). Customer Order Backlog Offline Load

Use this option anytime you need to load customer order backlog information from a
source other than COM.
What information you need: Record layout (See Appendix A).
What reports are printed: Offline Maintenance Edit List (MO312R).

The basic steps for performing this task follow. The report is not described in this
manual.
 AXAM01, option 3
Page 4-22
Contents Index
Using the APS Bridge

AMVPOF—Customer Order Backlog Offline Load

Use this panel to select which action you wish to perform on the Customer Order
Backlog Offline file. You can edit only or edit and update the file. In both instances an
edit report of exceptions, error messages, and final record counts is printed. If you
choose to update the file, a second report showing all transactions passed to the
update program and final record counts is also printed.

This panel appears when you select option 3 on the APS Bridge Maintenance menu
(AXAM01).

'DWH   2IIOLQH 0DLQWHQDQFH 2SWLRQV $0932)

6HOHFW RQH RI WKH IROORZLQJ    $  (GLW RQO\

 (GLW DQG XSGDWH

2IIOLQH ILOH QDPH      DDDDDDD$

2IIOLQH ILOH OLEUDU\ QDPH    DDDDDDD$

6HOHFW RSWLRQ IRU XSGDWH    $  5HWDLQ DOO RIIOLQH UHFRUGV

 5HWDLQ RQO\ HUURU UHFRUGV
 'HOHWH RIIOLQH ILOH

) ([LW

What to do

Type in the information required and press Enter. The APS Bridge Maintenance
menu appears again.

Function keys

F3=Exit returns you to the APS Bridge Maintenance menu (AXAM01) 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.
 AXAM01, option 3
Page 4-23
Contents Index
Using the APS Bridge

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
 AXAM01, option 4
Page 4-24
Contents Index
Using the APS Bridge

Option 4 (AXAM01). Period Forecast Offline Load

Use this option anytime you need to load forecasting information from an offline
source.
What information you need: Record layout (See Appendix A).
What reports are printed:
• Offline Maintenance Edit List (MO310R)
• Offline Load Audit List (MO311R).

The basic steps for performing this task follow. The reports are not described in this
manual.
 AXAM01, option 4
Page 4-25
Contents Index
Using the APS Bridge

AMVPOF—Period Forecast Offline Load

Use this panel to select which action you wish to perform when loading forecasting
information from an offline source. You can edit only or edit and update the file. In both
instances an edit report of exceptions, error messages, and final record counts is
printed. If you choose to update the file, a second report showing all transactions
passed to the update program and final record counts is also printed.

This panel appears when you select option 4 on the APS Bridge Maintenance menu
(AXAM01).

'DWH   2IIOLQH 0DLQWHQDQFH 2SWLRQV $0932)

6HOHFW RQH RI WKH IROORZLQJ    $  (GLW RQO\

 (GLW DQG XSGDWH

2IIOLQH ILOH QDPH       DDDDDDD$

2IIOLQH ILOH OLEUDU\ QDPH     DDDDDDD$

6HOHFW RSWLRQ IRU XSGDWH    $  5HWDLQ DOO RIIOLQH UHFRUGV

 5HWDLQ RQO\ HUURU UHFRUGV
 'HOHWH RIIOLQH ILOH

) ([LW

What to do

Type in the information required and press Enter. The APS Bridge Maintenance
menu appears again.

Function keys

F3=Exit returns you to the APS Bridge Maintenance menu (AXAM01) 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.
 AXAM01, option 4
Page 4-26
Contents Index
Using the APS Bridge

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
 AXAM01, option 5
Page 4-27
Contents Index
Using the APS Bridge

Option 5 (AXAM01). Putback Transaction Tailoring Offline Load

Use this option anytime you need to mass maintain putback transactions from an
offline source. You will need to have your own program to generate transactions.
What information you need: Record layout (See Appendix A).
What reports are printed:
• Offline Maintenance Edit List (MO390R)
• Offline Load Audit List (MO391R).

The basic steps for performing this task follow. The reports are not described in this
manual.
 AXAM01, option 5
Page 4-28
Contents Index
Using the APS Bridge

AMVPOF—Putback Transaction Tailoring Offline Load

Use this panel to select which action you wish to perform on putback transactions
from an offline source. You can edit only or edit and update the file. In both instances
an edit report of exceptions, error messages, and final record counts is printed. If you
choose to update the file, a second report showing all transactions passed to the
update program and final record counts is also printed.

This panel appears when you select option 5 on the APS Bridge Maintenance menu
(AXAM01).

'DWH   2IIOLQH 0DLQWHQDQFH 2SWLRQV $0932)

6HOHFW RQH RI WKH IROORZLQJ    $  (GLW RQO\

 (GLW DQG XSGDWH

2IIOLQH ILOH QDPH       DDDDDDD$

2IIOLQH ILOH OLEUDU\ QDPH     DDDDDDD$

6HOHFW RSWLRQ IRU XSGDWH     $  5HWDLQ DOO RIIOLQH UHFRUGV

 5HWDLQ RQO\ HUURU UHFRUGV
 'HOHWH RIIOLQH ILOH

) ([LW

What to do

Type in the information required and press Enter. The APS Bridge Maintenance
menu appears again.

Function keys

F3=Exit returns you to the APS Bridge Maintenance menu (AXAM01) 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.
 AXAM01, option 5
Page 4-29
Contents Index
Using the APS Bridge

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
 AXAM01, option 6
Page 4-30
Contents Index
Using the APS Bridge

Option 6 (AXAM01). Putback Transaction Tailoring

Use this option anytime you need to tailor transactions used in putbacks, by
warehouse. You can select a particular item, or you can select all items with a specific
item class, lead time code, or value class.
What information you need: Warehouse identifier and item number, item class,
lead time code, or value class.
What reports are printed: None.

The basic steps for performing this task follow each panel.
 AXAM01, option 6
Page 4-31
Contents Index
Using the APS Bridge

MO0570—Putback Transaction Tailoring

Use this panel to create a list of transactions you want to work with. You can select to
tailor transactions for a specific item, or create a comprehensive list of transactions
that affect all items containing a specific item class, lead time code, or value class.

This panel appears when you select option 6 on the APS Bridge Maintenance menu
(AXAM01).

'DWH   $36 %ULGJH 02

3XWEDFN 7UDQVDFWLRQ 7DLORULQJ

7\SH LQIRUPDWLRQ SUHVV (QWHU

 6HOHFW

6HO 7\SH
Q ,WHP QXPEHU
Q ,WHP FODVV
Q /HDG WLPH FRGH
Q 9DOXH FODVV

) ([LW

What to do

Type 1 in the Sel field to choose the type of list for which you want to tailor
transactions. A panel appears where you can select the warehouse and type
identifiers you want to change criteria for.

Function keys

F3=Exit returns you to the APS Bridge Maintenance menu (AXAM01) without
performing an action.

Fields

Sel. Type 1 to select the type you want to work with.

 AXAM01, option 6
Page 4-32
Contents Index
Using the APS Bridge

MO0590—Putback Transaction Tailoring

Use this panel to tailor the transactions for the type you selected.

This panel appears when you select a type on the Putback Transaction Tailoring
(Select) panel (MO0570). After you enter the warehouse and a valid value in the type
field (depending on what type was chosen on the Select panel) at the top of the panel,
the lower part of the panel appears so you can tailor the transactions. This sample
shows the Item number field. You can type ? in the Warehouse and Item number
fields to begin a master file search.

'DWH   $36%ULGJH02 

3XWEDFN7UDQVDFWLRQ7DLORULQJ

7\SHLQIRUPDWLRQSUHVV(QWHU
:DUHKRXVHD$

,WHPQ XPEHU    D DDDDDDDDDDD$ 

7UDQ$XWRPDWHG,QIR
7UDQ,' 'HVFULSWLRQ $FWLYH3RVWLQJ 0VJ
&5702 &UHDWHPDQXIDFWXULQJRUGHU  
&+*02 &KDQJHPDQXIDFWXULQJRUGHU  
&1/02 &DQFHOPDQXIDFWXULQJRUGHU 
&+*57( &KDQJHPDQXIDFWXULQJRUGHUURXWLQJ  
&5732 &UHDWHSXUFKDVHRUGHU   
&1/32 &DQFHOSXUFKDVHRUGHU 
0)*83 0DQXIDFWXULQJGDWHXSGDWHRQFH 
0)*8300DQXIDFWXULQJGDWHXSGDWHPDQ\ 
35083 3URPLVHGDWHXSGDWHRQFH 
350830 3URPLVHGDWHXSGDWHPDQ\   



What to do

The default appears in the Transaction Active, Automated Posting, and Info
Message fields. You can type over a particular entry to change the criteria for
handling that transaction, or you can use F9 to change all entries. When you press
Enter, the changes are made and the top part of the panel appears again so you can
enter another warehouse or item number or type.
Note: Cancel and Change purchase order requires you to manually complete the
transaction and is not an automated action.

Function keys

F3=Exit returns you to the APS Bridge Maintenance menu (AXAM01).

F5=Refresh causes the list of processing criteria to be refreshed to its original

appearance.

F9=Set all causes the entire list to be changed to the value of 1.

F12=Cancel returns you to the Select panel.

 AXAM01, option 6
Page 4-33
Contents Index
Using the APS Bridge

Fields

Transaction active. One of the following:

0 No, do not process this transaction on putback.
1 Yes, process this transaction on putback.

Automated posting. One of the following:

0 No, do not post this transaction. Hold this transaction for Review and Approve
option.
1 Yes, post this transaction without Review and Approve option.

Informational messages. One of the following:

0 No, do not create any informational message for this transaction during the
putback.
1 Yes, create informational messages for this transaction during the putback.
Messages will be viewed in Review and Approve option.
 AXAM00, option 2
Page 4-34
Contents Index
Using the APS Bridge

Option 2 (AXAM00). Inquiry

Use this menu to perform inquiry functions in the APS Bridge interface.

$;$0 $36 %ULGJH

,QTXLU\

7\SH RSWLRQ RU FRPPDQG SUHVV (QWHU

 &XVWRPHU 2UGHUV RQ +ROG

) ([LW ) 3URPSW ) 5HWULHYH ) $FWLRQV

) -RE VWDWXV ) 5HWXUQ ) 0HVVDJHV
 AXAM02, option 1
Page 4-35
Contents Index
Using the APS Bridge

Option 1 (AXAM02). Customer Orders on Hold

Use this option to see information on customer order line items that will not be passed
to APS. You will be able to view orders that are on hold within a specific warehouse in
XA when orders are being passed to APS.

This option is valid only if COM is installed.

What information you need: None.
What reports are printed: None.

The steps to perform this task follow.

 AXAM02, option 1
Page 4-36
Contents Index
Using the APS Bridge

MO0711—Customer Orders on Hold

Use this panel to inquire into the customer orders that are being filtered from APS.
You must be authorized to the selected warehouse in order to view information for that
warehouse.

This panel appears when you use choose option 1 on the Inquiry menu (AXAM02).

  $36 %ULGJH 02

&XVWRPHU 2UGHUV RQ +ROG
2SWLRQV 3RVLWLRQ WR D$ DDDDDDDDDDD $ QQQQQ
 $GGLWLRQDO LQIRUPDWLRQ
,WHP &XVWRPHU 2UGHU ,WHP 5HOHDVH
6HO :KV 3ODQQHU ,WHP QXPEHU &ODVV 2UGHU    +ROG +ROG +ROG
Q   
Q   
Q   
Q   
Q   
Q   
Q   
Q   
Q   
Q   
Q   
Q   
Q   

) ([LW 5ROOGRZQ  5ROOXS

 
 $GGLWLRQDO ,QIRUPDWLRQ 
 
 ,WHP 'HVFULSWLRQ 'UDZLQJ QXPEHU 
 
 
 
 
 (QWHU &RQWLQXH ) &DQFHO 
 
  

What to do

To display additional information, type 1 in the Sel field beside the appropriate
warehouse, planner, and item and press Enter. A window appears with additional
information.

Function keys

F3=Exit causes the Inquiry menu (AXAM02) to appear.

 AXAM02, option 1
Page 4-37
Contents Index
Using the APS Bridge

Fields

Position to. Type the warehouse, planner, and item number where you want the list
to begin.

Sel. Type 1 to select the warehouse and item number whose information you want to
see.
 AXAM00, option 3
Page 4-38
Contents Index
Using the APS Bridge

Option 3 (AXAM00). Initiate Load/Putback

When you select option 3 on the APS Bridge Main Menu (AXAM00), a panel appears
to allow you to initiate, by warehouse, a server load or a putback of APS data.

You can choose either timed or immediate execution of the process. You must be
authorized to the selected warehouse and also have security authorization to perform
loads and putbacks in order to perform these tasks.

APS checks to see if any other warehouses in other environments are defined to the
same APS directory. If found, the load or putback process is terminated and a
message is issued to state the environment and warehouse found having the same
data.

To prevent double releasing of manufacturing and purchase orders, APS verifies that
a server load has run since the last putback.

During the load process, APS checks to see if any unprocessed order release
batches exist in Inventory Management from prior putbacks, as well as checking to
see if any putback messages exist. If such a batch or messages are found, the load is
terminated and a message is issued with that information.

Notes:
1. The Putback function is activated in the Interface Control file, using option 1 on
the APS Bridge Maintenance menu.

2. You will need to tailor putback transactions, using option 6 on the APS Bridge
Maintenance menu, if you want the interface active for a specific transaction, want
to post a transaction automatically, and/or generate informational messages.

What information you need: Warehouse identifier.

What reports are printed: None.
 AXAM00, option 3
Page 4-39
Contents Index
Using the APS Bridge

MO050R—Initiate Load/Putback
Use this panel to begin the Load or Putback process. You must be authorized to the
selected warehouse in order to perform either process.

This panel appears when you use choose option 3 on the APS Bridge Main Menu
(AXAM00).

'DWH   $36 %ULGJH 025

,QLWLDWH /RDG3XWEDFN

7\SH LQIRUPDWLRQ SUHVV (QWHU

:DUHKRXVH          D$

/RDG3XWEDFN         Q  /RDG  3XWEDFN

6WDUW WUDQVIHU UHTXHVW      Q  ,PPHGLDWH  7LPHG

2UGHU ERDUG PDWFKLQJ      Q  1R  <HV

) 3XWEDFN PHVVDJHV ) ([LW

What to do

To initiate a server load or putback process, type the required information and press
Enter. If you select a timed request, a window appears to allow you to enter the
desired start date and time.

When you press Enter, the Last load and Last putback date and time is displayed on
the panel. A message appears instructing you to press Enter again to submit the
process.

Function keys

F2=Putback messages causes the Review and Approval Putback Messages panel
(MO0580) to appear where you can work with the messages.

F3=Exit causes the APS Bridge Main menu (AXAM00) to appear.

Fields

[?] appears next to a field name in the following field definitions to identify a field
from which you can begin a master file search.

Warehouse [?]. The XA warehouse you want to use.

 AXAM00, option 3
Page 4-40
Contents Index
Using the APS Bridge

Load/Putback. Type one of the following options to indicate the action you want to
take:
1 Load
2 Putback

Start transfer request. Type one of the following options to indicate the action you
want to take:
1 Immediate. The job is submitted to the job queue to start executing
immediately.
2 Timed. A window appears to allow you to enter the date and time you want
the process to execute.

Order board matching. This field is used only by the load process. Accept the
default of 1, or type 0 to indicate the action you want to take:
0 No, do not use the order board function in SCM to make incremental
schedule changes for this process.
1 Yes, use the order board function in SCM to make incremental schedule
changes for this process.

See the SCM documentation for more information on this function.

 AXAM00, option 3
Page 4-41
Contents Index
Using the APS Bridge

MO0580—Review and Approve Putback Messages

Use this panel to work with putback messages that were created during the putback
process for transactions that were tailored at the item level to state if a message
should be generated. You can decide to either process the message or delete it. You
can use function keys to subset the list or to delete informational messages.

This panel appears when you use F2 on the Initiate Load/Putback panel (MO050R) or
when you press Enter after selecting a warehouse on the Review and Approve
Putback Messages (Select) panel (MO4990) in option 5.

'DWH   $36 %ULGJH 02

5HYLHZ DQG $SSURYH 3XWEDFN 0HVVDJHV
:DUHKRXVH

2SWLRQV
 3URFHVV  'HOHWH
([FHSWLRQ
6HO 7UDQ ,' 2UGHU ,WHP 1XPEHU 3ODQQHU 0HVVDJH
Q  
Q  
Q  
Q 
Q
Q  
Q  
Q  

) ([LW ) 5HIUHVK ) &DQFHO ) 5HSHDW ) 6XEVHW ) 5HSRUWV
) 'HOHWH ,QIR 0VJ 5ROO XSGZQ

What to do
• To process the message, type 1 in the Sel field and press Enter. When the action
has been completed, the Select underscore disappears to inform you that the
action is complete.
• To delete the message, type 4 in the Sel field and press Enter. The message is
deleted from the APS message file and flagged as deleted on the display.

Function keys

F3=Exit causes the APS Bridge Main menu (AXAM00) to appear.

F5=Refresh causes the panel to remove actioned and deleted messages.

F12=Cancel causes the previous panel to appear.

F13=Repeat allows you to repeat the action you typed in the Sel field for all messages
requiring action.

F17=Subset causes Window MO058S to appear so you can narrow the list of
messages you want to work with.
 AXAM00, option 3
Page 4-42
Contents Index
Using the APS Bridge

F21=Reports causes the Print Putback Reports display (MO0581) to appear where
you can select the reports you want to print and where you also can enter the planner
identifier.

F23=Delete Info Msg causes all informational messages that require no action to be
deleted from the APS message file after you confirm that you want to complete the
action.

Fields

Warehouse [?]. The XA warehouse.

Sel. Type 1 beside the transaction for which you want to process the putback
message. Type 4 beside the transaction for which you want to delete the putback
message.
 AXAM00, option 3
Page 4-43
Contents Index
Using the APS Bridge

MO058S—Subset Window for Putback Messages

Use this window to narrow the list of putback messages you want to work with.

This panel appears when you use F17 on the Review and Approve Putback
Messages panel (MO0580).



 6XEVHW E\ 026
 
 0HVVDJHV      %ODQN DOO  DFWLRQ  HUURU 
 $XWRPDWHG SRVWLQJ     %ODQN DOO  PDQXDO  DXWR 
 7UDQVDFWLRQ ,'      
 ,WHP QXPEHU       
 2UGHU QXPEHU       
 3ODQQHU QXPEHU       
 
 ) &DQFHO 
 
 

What to do

Type the information you need to subset the list you want to work with on the panel
and press Enter. The list on the previous panel appears with the selections you chose
to subset.

Function keys

F12=Cancel causes the previous panel to appear without making any changes.
 AXAM00, option 3
Page 4-44
Contents Index
Using the APS Bridge

MO0581—Print Putback Reports

Use this panel to select the report and planner you want to print reports for.

This panel appears when you use F21 on the Review and Approve Putback
Messages panel (MO0580).

'DWH   $36 %ULGJH 02

3ULQW 3XWEDFN 5HSRUWV

7\SH RSWLRQV SUHVV (QWHU

 3ULQW 3ODQQHU DDD$

6HO 5HSRUW
Q 7UDQVDFWLRQV
Q 7UDQVDFWLRQV E\ SODQQHU
Q (UURU PHVVDJHV
Q (UURU PHVVDJHV E\ SODQQHU
Q ,QIRUPDWLRQDO PHVVDJHV
Q ,QIRUPDWLRQDO PHVVDJHV E\ SODQQHU
Q 0DQXDO SRVWLQJ WUDQVDFWLRQV
Q 0DQXDO SRVWLQJ WUDQVDFWLRQV E\ SODQQHU
Q 0DQXIDFWXULQJ RUGHU H[FHSWLRQV
Q 0DQXIDFWXULQJ RUGHU H[FHSWLRQV E\ SODQQHU
Q 3XUFKDVH RUGHU H[FHSWLRQV
Q 3XUFKDVH RUGHU H[FHSWLRQV E\ SODQQHU

) ([LW ) &DQFHO

What to do

Type 1 beside the reports you want to print and press Enter. The reports are
scheduled for printing.

When you enter an identifier in the Planner field, you can select reports for that
planner only. If you leave the field blank, all planners are included in the reports you
select.

Function keys

F3=Exit causes the APS Bridge Main menu (AXAM00) to appear.

F12=Cancel causes the previous panel to appear without causing any action.

Fields

Planner. Type an identifier if you want to select reports for a specific planner. Leave
the field blank if you want to include all planners in the reports you select.

Sel. Type 1 beside the reports you want to print.

 AXAM00, option 4
Page 4-45
Contents Index
Using the APS Bridge

Option 4 (AXAM00). Review Load Messages

When you select option 4 on the APS Bridge Main Menu (AXAM00), a panel appears
for you to select the warehouse for which to display the import log produced by the
server during the last load server process. When you have selected a warehouse, the
next panel appears with messages from the log.
What information you need: Warehouse identifier.
What reports are printed: None.
 AXAM00, option 4
Page 4-46
Contents Index
Using the APS Bridge

MO1230—Review Load Messages

Use this panel to select the warehouse for which you want to review load messages.

This panel appears when you select option 4 on the APS Bridge Main menu
(AXAM00).

'DWH   $36 %ULGJH 02

5HYLHZ /RDG 0HVVDJHV
2SWLRQV
 6HOHFW

6HO :KV 'HVFULSWLRQ

B
B

) ([LW

What to do

Type 1 in the Sel field to choose the warehouse identifier for which you want to see
message information and press Enter. A panel appears with the messages so you
can review and respond.

Function keys

F3=Exit causes the APS Bridge Main Menu to appear.

Fields

Sel. Type 1 to select a warehouse to use.

 AXAM00, option 4
Page 4-47
Contents Index
Using the APS Bridge

MO1231—Review Load Messages

Use this panel to select the message that you want to review.

This panel appears when you select a warehouse on panel MO1230.

'DWH   $36 %ULGJH 02

5HYLHZ /RDG 0HVVDJHV

:DUHKRXVH     
2SWLRQV
 6HOHFW

6HO 0HVVDJH
B    6WDUW 7LPH
B    /RDGLQJ 'DWD :RUNFHQWHU
B    :ULWLQJ 7DEOH :RUNFHQWHU
B    /RDGLQJ 'DWD 3DUW
B     /RDGLQJ 'DWD )*,
B    :ULWLQJ 7DEOH 3DUW
B    /RDGLQJ 'DWD 5RXWLQJ
B     :ULWLQJ 7DEOH 5RXWLQJ
B    /RDGLQJ 'DWD %20
B  > &?730$1a?6DPSOH'%?73,%20GDW @ > /LQH   3DUWB,' _BBBBBB
B  > &?730$1a?6DPSOH'%?73,%20GDW @ > /LQH   3DUWB,' _BBBBBB
B  > &?730$1a?6DPSOH'%?73,%20GDW @ > /LQH   3DUWB,' _BBBB 

) ([LW ) 5HWXUQ ) 6XEVHW ) 3RV WR 5ROO XSGRZQ

What to do

Type 1 in the Sel field to choose the message for which you want to see more details
and press Enter. Panel MO1232 appears with additional information, if available, for
that message. (That panel is not shown in this book.)

If there are more messages on the next page, you can scroll forward to them. When
you use F12 on the next panels, the message you had selected appears at the
beginning of the list on the panel you are returned to.

Function keys

F3=Exit causes the APS Bridge Main Menu to appear.

F12=Return causes the Review Load Messages Select panel to appear.

F17=Subset causes Window MO123W to appear so you can narrow the list of
messages you want to work with by typing in a character string that must appear in
the message. (That window is not shown in this book.)

F21=Position to causes Window MO123P to appear so you can type in a record

number or character string where you want the list to begin. (That window is not
shown in this book.)
 AXAM00, option 4
Page 4-48
Contents Index
Using the APS Bridge

Fields

Sel. Type 1 to select the message you want to review.

Note: You can select only one message at a time.
 AXAM00, option 4
Page 4-49
Contents Index
Using the APS Bridge

Option 5 (AXAM00). Review and Approve Putback Messages

When you select option 5 on the APS Bridge Main Menu (AXAM00), a panel appears
to allow you to select the warehouse for which you want to review and approve
putback messages that were created during the putback process. You must be
authorized to the specific warehouse you select.

After selecting the warehouse, you can display messages that were created during
the putback process. Transactions can be tailored at the item level to state if a
message should be generated. The messages inform you when an action has been
taken against a manufacturing order, purchase order, or customer order.

You can choose to process the message or to delete it.

What information you need: Warehouse identifier.
What reports are printed: None.
 AXAM00, option 5
Page 4-50
Contents Index
Using the APS Bridge

MO4990—Review and Approve Putback Messages

Use this panel to select the warehouse for which you want to review and approve
putback messages.

This panel appears when you choose option 5 on the APS Bridge Main Menu
(AXAM00).

'DWH   $36 %ULGJH 02

5HYLHZ DQG $SSURYH 3XWEDFN 0HVVDJHV
2SWLRQV
 6HOHFW

6HO :KV 'HVFULSWLRQ

B
B

) ([LW

What to do

Type 1 in the Sel field beside the warehouse whose messages you want to work with.
The Work With Putback Messages panel (MO0580) appears.

Refer to “MO0580—Review and Approve Putback Messages” on page 4-41 for a

description of that panel and its subset window.

Function keys

F3=Exit causes the APS Bridge Main Menu to appear.

Fields

Sel. Type 1 to select a warehouse to use.

 Page A-1
Contents Index
Offline file load and data entry

Appendix A. Offline file load and data entry

As an alternative to loading selected information from XA or to mass
maintain putback transactions, you can prepare the information offline in files on a
separate system. The files that you create offline can then be processed by APS.
Offline files can be created on a diskette or written to a disk file; the same format
requirements apply to both.

To use data from offline files in APS, you must:

1. Create a file with the information on diskette or disk; the file must follow the
corresponding file layout given in this appendix.
2. Process the offline files by selecting the appropriate APS menu option.

This appendix describes those activities.

Creating a diskette or disk file

You can create offline files on diskette or disk. To create a diskette file, you need an
offline data entry device. However, you can create a disk file in several ways:
• A user-written program creates the records and writes them to a disk file.
• Another system creates the records on tape using the required file layout. You
copy the tape file to disk.
• A remote location sends the records via telecommunications and writes them to a
disk file.

It does not matter how or where the records originate. As long as they reside in a disk
file that has the defined file layout, they can be processed by APS.

Understanding the file format

Use the file format shown later in this appendix to set up records for the file you want
to load from diskette or disk. The format gives you the following information for each
enterable field:
• A brief description of the field
• The short field name (6 characters)
• Whether the field is alphabetic or numeric (A/N/P/S)
• The position of the field in the record (From and To)
• For numeric fields only, the number of decimal positions in the field (Dec. pos.).
 Page A-2
Contents Index
Offline file load and data entry

Assigning a file name

Assign a special name to each file, or use the default name listed here. You must
enter the name when you load the file.

Offline file name

File to be loaded or updated (default)
Customer Order Backlog Offline Load OLCSBO
Interface Transaction Tailoring Offline Load OLITTO
Period Forecast Offline Load OLOFCS

Record length
Assign a record length of 128, unless otherwise specified.

Special data requirements

Type the information carefully. The system checks for errors when you process the
files. If it finds errors, you must correct the records with errors before you can finish
processing them.

Processing the offline files

When you have finished creating the offline files, you are ready to load the information
onto the system. For instructions on how to load files from offline files, see the “Load
data from offline files” section in the CAS User’s Guide.

The following pages list the record formats for the offline files you can load for this
application.
 Page A-3
Contents Index
Offline file load and data entry

Record formats

Customer Order Backlog Offline Load file record format

Offline file name (default): Customer Order Backlog Offline File Load (OLCSBO)
Record length: 95
Function: Used to load customer order backlog information from a source other than
COM.

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

Note: If the XA Forecasting application (FCST) is installed, forecast

consumption is performed on the APS server. If FCST is not installed, the Interface
Control records for each warehouse define where forecast consumption is performed.

When forecast consumption is performed by the APS server, all closed sales orders
for all active forecast periods must be sent to the server in order for it to perform the
consumption properly. In OLCSBO, a closed sales order is identified by a zero in the
Unshipped Order Quantity field (BOBQTY).
 Page A-4
Contents Index
Offline file load and data entry

Interface Transaction Tailoring Offline Load file record format

Offline file name (default): Interface Transaction Tailoring Offline Load (OLITTO)
Record length: 33
Function: Used to mass maintain putback transactions from an offline source.
Field Dec.
Field description Field name type From To pos.
Warehouse TOHOUS A 1 3
Item number TOITNB A 4 18
Transaction Code TOTRID A 19 28
Transaction Type
[1=Add, 2=Change, 3=Delete] TOTRTP A 29 29
Transaction Active TOIACT A 30 30
Automated Posting TOPSTD A 31 31
Informational Messages TOINFO A 32 32
Errors flag - Reserved TOEDTF A 33 33

Period Forecast Offline Load file record format

Offline file name (default): Period Forecast Offline File Load (OLOFCS)
Record length: 43
Function: Used to load forecasting information from a source other than XA.

Field Dec.
Field description Field name type From To pos.
Warehouse OFHOUS A 1 3 0
Item number OFITNB A 4 18
Period Beginning Date OFPRBD S 19 25
Transaction Code
[1=Add, 2=Change, 3=Delete] OFTRID S 26 35 0
Forecast Quantity OFFQTY S 36 42
Errors flag - Reserved OFEDTF A 43 43 0
 Page B-1
Contents Index
Mapping XA Files to SCM Files

Appendix B. Mapping XA Files to SCM Files

The table below provides a view of how XA files interface with Supply
Chain Management (SCM) files. A discussion of processing for each file follows the
table.

XA file SCM file See page

Product Structure () BOM B-2
Product Structure Header (PSTHDR) BOM B-2
Item Revision “A” (ITMRVA) Part B-3
Item Revision “C” (ITMRVC) Part B-3
Item Balance (ITEMBL) Inventory/Part B-3
Item Plan (ITMPLN) Part B-5
Facility Master (FACMST) Work Centers B-5
Routing (RTGOPR) Routing B-7
Manufacturing Order Master (MOMAST) Work Order Header B-8
Manufacturing Order Routing (MOROUT) Jobs in Progress ( if TBC code is C) B-8
Work Order Routing B-11
Manufacturing Order Component (MODATA) Work Order Allocation B-12
Purchase Order Item (POITEM) Purchase B-13
Purchase Order Item Release ( POBLKT) Purchase B-13
Purchase Order Item ( REQHDF) Purchase B-14
Forecast (OLPFCS) Forecast B-14
Customer Line Item (MBADREP) Sales B-14
Offline Customer Line Item (OLCSBL) Sales B-16

XA input files

An item is excluded from processing if the following conditions exist:

• has no item planning record in the planning warehouse
• is not defined as an APS item in the item plan file
• item type is F (feature) or K (kit), or the item is a miscellaneous or service item, or
an S-numbered item.
 Page B-2
Contents Index Mapping XA Files to SCM Files

PSTDTL mapping to SCM’s BOM file

If the parent is a purchased part (LTCOD=P) the BOM will not be sent to the engine.

Field Comments
Parent item number Edited to ensure parent item is planned in APS and is in
the planning warehouse.
Component item number Edited to ensure component item is planned in APS and
is in the planning warehouse.
Quantity per Engine can factor this value, using Yield.
Bridge factors by the Standard Batch Quantity in the item
Master record.
A negative quantity per generates an error message.
Operation where used If not a valid operation number, sends the operation
number for the first active routing operation.
Component effectivity from date If zero, Bridge substitutes 01011901.
Component effectivity to date If zero, Bridge substitutes 02312099.

KBC considerations
Reads the KBC BOM file (TCFOBM) and checks COM’S line item file to determine if
an order exists. If yes, it gets warehouse from COM line item in TCFOHB. Its parent
item ID is composed of: item number + a sequence number assigned by APS Bridge.
This unique parent item ID will be used for populating the SCM Parts and Routing
files.
Note: If a KBC component is a phantom, the phantom bill is stored in EPDM’s
product structure file.

PSTHDR mapping to SCM’s BOM file

If the parent is a purchased part (LTCOD=P) the BOM will not be sent to the engine.

Field Comments
Parent item number Edited to ensure parent item is planned in APS and is in
the planning warehouse.
Standard batch quantity Used to factor the product structure’s quantity per field.
 Page B-3
Contents Index Mapping XA Files to SCM Files

ITMRVA mapping to SCM’s Part file

The item plan file is read for the planning warehouse to be extracted. Therefore, to
map to the SCM Part file, the item must have an item plan record that is coded as an
APS item. KBC’s product structure file is read and all KBC items are extracted to
SCM.

Field Comments
Item ID
Item description
Stocking unit of measure
Item type code If the item type code is 0, 1, 2, or [9 and lead time code is
M] (manufactured item), map to the Raw Material Type
field as type 0-Normal.
If the item type code is 3 or 4 (raw material or purchased
item) or [9 and lead time code is P] (purchased item) and
is classified as a constrained item, map to the Raw
Material Type field as type 2-Priority. If the item is
unconstrained and an uncontrolled floor stock item, map
to the Raw Material Type field as 1-Ignore. If the item is
unconstrained and is a controlled floor stock item, map to
the Raw Material Type field as 0-Normal.
Item records for codes F (feature) and K (kit) are
bypassed.
Vendor number This is the default used if vendor number is not specified
in the Item Balance file.
Unit cost default This is the default used if Item Balance tailored cost is
zero.
Base price If COM is installed and base price is not specified on
customer order, the base price is obtained from COM’s
Item Master Extension file (MBBZREP).
If COM is not installed, get base price from item Revision
A-record.

ITMRVC mapping to SCM’s Part file

Field Comments
Item number
Buyer ID Buyer number for this item.

ITEMBL mapping to SCM’s Inventory file

Field Comments
Warehouse
Item ID
On-hand quantity This is the sum of all the on-hand quantities in the
planning warehouse and its associated demand
warehouses.
 Page B-4
Contents Index Mapping XA Files to SCM Files

ITEMBL mapping to SCM’s Part file

Field Comments
Warehouse
Item ID Maps to Part ID
Safety stock The import utility places safety stock on the planning time
fence date for replenishment.
Lead time information SCM uses lead times only for purchased items and
supports only whole numbers in days, so XA
lead times are rounded up to the next integer.
If XA lead time code = P:
purchasing review time (LTREV) maps to SCM buyer
lead time;
vendor time (LTVEN) plus safety time (LTSAF) map to
SCM MRP lead time;
purchasing adjustment (LTADP) maps to SCM dock 2
stock time.
Stocking unit of measure Maps to Manufacturing unit of measure
Purchase unit of measure Maps to Purchase unit of measure
Purchase unit of measure Converts a purchase UM to a stocking UM.
conversion factor
Planner ID Maps to SCM’s Analyst ID. Note that SCM supports only
a
3-alpha character data field.
Cost Standard unit, Average unit, or Last unit
- Dependent on how costs are tailored in IM
- If the tailored cost is zero, defaults to value stored in
ITMRVA record’s unit cost default field.
Vendor ID Primary vendor. If blank in ITEMBL file, defaults to
vendor ID in ITMRVA record.
Order point If order policy code is B, C, or H, map order point to
Reorder point field in SCM.
If order point is zero, calculate order point as sum of
Safety stock plus (Estimated average annual usage
times MRP lead time divided by Business days in the
year). Result is adjusted by Reorder tolerance percents
(defined in the IM tailoring questionnaire).
Establishes SCM’s Minimum (inventory) level for
stocking an item. Used with Raw material type of 1
(Ignore).
Estimated average annual usage Used to calculate order point for items using order policy
codes B, C, or H.
Floor stock code Uncontrolled floor stock in conjunction with
unconstrained part defines SCM’s Raw material type of 1
(Ignore).
Controlled floor stock (or not a floor stock item) in
conjunction with unconstrained part defines SCM’s Raw
material type 0 (Normal).
 Page B-5
Contents Index Mapping XA Files to SCM Files

ITMPLN mapping to SCM’s Part file

Field Comments
Warehouse
Item ID Maps to Part ID
Order policy code Tests for order policy code B, C, G, and H. All other
codes are assumed to be lot for lot (order policy code A
(Discrete).
Time periods of supply Valid only for purchased items. If order policy code is G
and master scheduled item code is not P (production
planned), then Time periods of supply map to SCM’s
Aggregation periods.
Minimum order quantity Valid only for purchased items.
Multiple order quantity Valid only for purchased items.
Maximum quantity Maps to Make Max Lot.
Shrinkage factor For purchased parts, if shrinkage is non-zero, SCM’s
Yield is 1-the shrinkage factor. If shrinkage is zero, Yield
is 1.00.
Demand time fence If non-zero, maps to SCM planning fence.
If zero and lead time code = P, purchasing time (LTPUR)
plus safety time (LTSAF) map to planning fence.
If zero and lead time code = M, manufacturing lead time
(LTMAN) plus manufacturing adjustment (LTADM) map
to planning fence.
Master scheduled item If MPSP is interfacing, a non-blank master schedule item
code defines SCM’s Part code.
Master level item code If MPSP is not interfacing, a non-blank master level item
code defines SCM’s Part code.
MPSP/MRP or APS planned Determines the application that plans this item
Constrained part Determines if a purchased item is defined as SCM’s Raw
Material type 2 (Priority). Otherwise, extract looks at the
Floor stock code to determine if the part is coded as
SCM’s Ignore or Normal.

The following fields are user populated in the SCM Item Plan Interface (TPPLAN) file:

Field Comments
Warehouse
Item number ID
Forecast family ID Identifies the name of a planning bill.
Used to consume family forecasts.
Planning bill part Determines if the item is a planning bill part.

FACMST mapping to SCM’s Work Centers file

Field Comments
Work Center ID
Work Center description Maps to workcenters description.
Shift capacity Selects the largest number of resources used on 1st,
2nd, and 3rd shift.
 Page B-6
Contents Index
Mapping XA Files to SCM Files

Field Comments
Prime load code Used to place a monetary rate on Overtime rate; i.e.,
setup or run labor.
Used when calculating operation duration in SCM’s
Routings file.
A prime load code of 0 sets SCM’s Dummy Flag to
Y - Infinite Capacity.
Work Center Group ID Identifies the work center facility to which the work center
belongs.
Standard queue time Maps to SCM’s Forced queue.
Current setup rate Used to place a monetary figure on Overtime rate.
Current labor rate Used to place a monetary figure on Overtime rate.
Overtime rate - If Prime load code is 2, use 1-1/2 times current setup
rate.
- If Prime load code is 4 or 5, use 1-1/2 times current
labor rate.
- If Prime load code is 1 or 3, machine rate is zero.

The following work center fields are used when mapping to SCM’s Routings file:

Field Comments
Standard efficiency
Prime load code
Buffer in
Buffer out
 Page B-7
Contents Index Mapping XA Files to SCM Files

RTGOPR mapping to SCM’s Routing file

Includes routing if item is in the planning warehouse, is planned by APS, and is
considered to be a manufactured part; i.e., lead time code is M.

Field Comments
Item number
Operation sequence Maps to Job Step ID
Work center ID If value in FCP1 begins with the literal "*", override work
center with value that follows the asterisk.
Operation status code Send only active operations to SCM; i.e., status code 10.
Operation description Converts to SCM’s Job Step Description
TBC If code is C:
- Set SCM batch size to 9999999.999.
- Identify work centers with outside operations and
set them to 2-Outside Operation in SCM’s Dummy
Flag field.
If code is H:
- Set SCM batch size to all 9s.
- If batch size in TPROUT is non-zero, use value from
TPROUT record.
Note: Run hours is independent of quantity. Batch
size relates to how many pieces can run through the
operation at the same time.
If code is not C or H:
- Set SCM batch size to 1.
Setup labor hours If Facility Prime Load Code is 2, 3, or 5, setup duration is
calculated to be Setup Labor Hours / Setup Crew Size /
Standard Efficiency. Map setup duration to SCM’s Setup
Time.
If setup is not 2, 3, or 5, setup is zero.
Convert time to seconds.
Crew size Used in the calculation of Setup Duration.
Labor hours Used in calculation of SCM’s Run Time Per Batch.
A work center’s Prime Load code and TBC not C
determines if Labor Hours are used.
Labor hours are factored by the work center’s standard
efficiency.
Machine hours Used in calculation of SCM’s Run Time Per Batch.
A work center’s Prime Load code and TBC not C
determines if Machine Hours are used.
Machine hours are factored by the work center’s
standard efficiency.
Tool number Tool number field is left adjusted in SCM’s tool
description field.
FCP1 If FCP1 does not begin with the literal "*", the value in
FCP1 is included in SCM’s tool description field.
FCP2 The value in FCP2 is included in SCM’s tool description
field.
Buffer out The largest value of Buffer out in the work center and in
the operation record map to SCM’s Idling time per batch.
Current operation yield Used to factor the order quantity at an operation and the
component parts needed at the operation.
Maps to SCM’s Yield.
 Page B-8
Contents Index
Mapping XA Files to SCM Files

The following fields are user populated in the SCM Routing (TPROUT) file. The key is
Item-Operation sequence.

Field Comments
Batch size Used to determine the limit of how many units can be
combined into a single operation. If "capacity" exists,
quantities from multiple work orders can be combined
into a single operation such as in heat treating parts in an
oven.
Family ID Used in work centers defined as Drums. Operations
within the same family are candidates for reducing setup
time.
Minor family ID Defines where a setup time can be avoided if the Major
and Minor Family IDs are identical on back to back
operations that have a different item number or operation
number.
Minor setup time in minutes Relates to operations that have a similar setup.
Cleanup time in minutes Relates to work done after the operation is completed
and parts are sent to the next operation.

KBC considerations

For a KBC BOM, the bill is found in the TCFOBM file and the warehouse is found in
the TCFOHB file. Its parent item ID is composed of: item number + a sequence
number assigned by APS Bridge. This unique parent item ID will be used for
populating the SCM Parts and Routing files. See TCF000 for data fields comparable
to those found in the Routing file.

MOMAST mapping to SCM’s Work Order Header file

Field Comments
Warehouse
Manufacturing order number
Finished item number
Order quantity Maps to SCM’s Original Order Quantity.
Equal to order quantity + deviation - quantity received to
stock.
Quantity deviation
Quantity received Maps to SCM’s Quantity Finished.
Quantity scrapped Maps to SCM’s Scrap Quantity.
Order status If order status is equal to 0 or greater than 45, consider
the order closed and do not map across.
Scheduled start date Maps to SCM’s Release Date.

MOROUT mapping to SCM’s Jobs in Progress file

This mapping is used if Time Basis Code is C (Outside Operation). A record is written
to JIP file and Work Order Routing file.
 Page B-9
Contents Index
Mapping XA Files to SCM Files

Field Comments
Manufacturing order number Used to find Item ID from MOMAST
Operation sequence number Maps to SCM’s Job Step ID
Actual work center Maps to SCM’s Work Center ID. (For an outside
operation, some users define the work center with the
same ID as the vendor ID.)
Operation status For an outside operation, if the previous operation is at
least 40 (complete) and the outside operation (current) is
status 30 (quantity reported) or less, then the outside
operation is considered to be in-progress. In the case,
the duration of the outside operation needs to be
consumed automatically as the system date moves
toward operation completion date. In this case,
remaining duration maps to SCM’s Run Time Remaining.
If current operation status is 40 or 50, complete code is
C, and passes to SCM.
Quantity Moved to this Operation Used to calculate SCM’s Quantity in Progress. If value is
zero, use PCC’s scheduling routine to determine how
many units are at this operation.
If value is greater than 0, determine quantity remaining
by subtracting Quantity Moved to this Operation.
Scheduled Operation Completion Used to calculate SCM’s remaining time on the
Date operation. (Scheduled Operation Completion Date less
System Date). This time is converted to seconds.
 Page B-10
Contents Index Mapping XA Files to SCM Files

MOROUT mapping to SCM’s Jobs in Progress file

Operations are placed in this file and also in Work Order Routing file if an operation
has a per piece setup or run time greater than the long running operations limit
entered in Interface Control Maintenance on display MO0552. The default value
shipped with the APS Bridge is 8 hours.
Note: MOMAST supplies Item ID to the Jobs in Progress file.

Field Comments
Manufacturing order number Used to find Item ID from MOMAST
Operation sequence number Maps to SCM’s Job Step ID
Actual work center Maps to SCM’s Work Center ID.
Operation status If status is 10, 20, or 30, operation is processed. If status
is 40 or 50. the operation is marked as complete in SCM.
Quantity in Progress (SCM Uses Batch Size from TPROUT if its value is non-zero.
mapped data field) This represents the desired batch size that can be
processed through an operation where multiple
operations may be combined; e.g., an oven. If the Batch
Size is zero, or a TPROUT record does not exist, and
TBC is H (Hours per lot), use quantity at the operation. If
TBC is not C or H, assume a quantity of 1 is being
processed. Quantity in Progress is determined as
follows: If Quantity Moved to this Operation is greater
than zero, determine the remaining quantity by
subtracting the quantity moved out of the operation. If
value is zero, use PCC’s scheduling routine to determine
how many units are at this operation.
Standard Setup Labor Hours
Setup Crew Size Used to calculate Remaining Setup Time
Standard Efficiency Used to calculate Remaining Setup Time
Setup Labor Hours to Date Used to calculate Remaining Setup Time
Run Labor Hours to Date Used to calculate Remaining Setup Time
Run Machine Hours to Date Used to calculate Remaining Setup Time
Maps to Remaining Setup time (Standard Setup Labor
Hours / Setup Crew Size / Standard Efficiency) less
(Setup Labor Hours to Date / Setup Crew Size). Assume
that setup is complete if the result is Positive and Run
Machine Hours to Date (RMHTD) or Run Labor Hours to
Date (RLHTD) in MOROUT have been reported. In this
case, remaining time is zero. The results of the
calculation cannot be negative.
Standard Run Time Hours
Standard Run Machine Hours Used to calculate Remaining Setup Time
Run Machine Hours to Date Used to calculate Remaining Setup Time
Standard Run Labor Hours Used to calculate Remaining Setup Time
 Page B-11
Contents Index Mapping XA Files to SCM Files

Field Comments
Prime Load Code Used to calculate Remaining Setup Time
Time Basis Code Used to calculate Remaining Setup Time
Maps to Remaining Run Time
Remaining Run Time is dependent on the Prime Load
Code and Time Basis Code. The remaining time for
machine hours is Standard Run Machine Hours less Run
Machine Hours To Date. For Labor Hours the calculation
is Standard Run Labor Hours less Run Labor Hours to
Date. Remaining run time cannot be negative.

MOROUT mapping to SCM’s Work Order Routing file

Field Comments
Manufacturing order number Maps to Work Order ID.
Operation sequence number Maps to Job Step ID
Actual work center Maps to workcenter ID.
Operation status If order status is 40 or 50 (complete), the order is not
extracted.
Operation description Maps to Job Step Description
Total quantity completed to date Maps to SCM’s quantity completed at an operation
Standard setup labor hours If prime load code is 2, 3, or 5, setup duration is
calculated as standard setup labor hours / setup crew
size / work center standard efficiency. Convert to
seconds.
Setup crew size The number of resources used for this setup.
Standard efficiency The work center’s efficiency.
Time Basis Code If C, a record is also entered into the JIP file.
If not C, used to determine SCM’s Run Time per Batch.
If H (hours per lot), then Batch Size is defaulted to
9999999.999 unless it is specified in TPROUT.
Labor hours Used in conjunction with Time Basis Code, prime load
code, operation quantity, and standard efficiency to
calculate SCM’s Run Time per Batch.
Machine hours Used in conjunction with Time Basis Code, prime load
code, operation quantity, and standard efficiency to
calculate SCM’s Run Time per Batch.
Current operation yield Maps to SCM’s Yield.
Tools Maps to SCM’s Tool Description.
FCP1 Maps to SCM’s Tool Description if the first position is not
"*".
FCP2 Maps to SCM’s Tool Description.
Buffer out The greater of the value of Buffer Out in the work center
versus the value of Buffer Out in the Routing Operation is
mapped to SCM’s Idling Time per Batch.
 Page B-12
Contents Index
Mapping XA Files to SCM Files

The following fields are user populated in the SCM Routing (TPROUT) file. The key
is Item-Operation sequence.
Field Comments
Batch size Used to determine the limit of how many units can be
combined into a single operation. If "capacity" exists,
quantities from multiple work orders can be combined
into a single operation such as in heat treating parts in an
oven.
Family ID Used in work centers defined as Drums. Operations
within the same family are candidates for reducing setup
time.
Minor family ID Defines where a setup time can be avoided if the Major
and Minor Family IDs are identical on back to back
operations that have a different item number or operation
number.
Minor setup time in minutes Relates to operations that have a similar setup.
Cleanup time in minutes Relates to work done after the operation is completed
and parts are sent to the next operation.

MODATA mapping to SCM’s Work Order Allocation file

Field Comments
Manufacturing order number Maps to Work Order ID
Component item number Maps to Child Part ID
Sequence number Maps to Sequence Number
Total Quantity required Maps to Quantity Required
Issue quantity total to date Maps to Quantity Issued
Adjusted quantity per expanded Maps to SCM’s quantity per parent
Operation where used If not a valid operation number, sends the operation
number for the first operation status 10, 20, or 30.
Required date Maps to SCM’s release date
 Page B-13
Contents Index Mapping XA Files to SCM Files

Mapping Purchase Orders and Requisitions to SCM’s Purchase file

For purchase orders, get information from POITEM file. If POITEM indicates the
order is a blanket order (BLCOD = 1), get information from POBLKT file. Include
requisitions in the mapping, using REQHDF file.

Bypass miscellaneous items because they do not have an item balance record.

POITEM Mapping to SCM’s Purchase file

Field Comments
Warehouse
Blanket item code If this item is a blanket item (BLCOD=1) go to Blanket
Release (POBLKT) file for order information.
Item number Maps to Part ID
Order number Maps to Order ID
Due date Maps to the date the order is to arrive in stock.
If past due, SCM places order on system date.
Order quantity The original order quantity.
Sum of Order quantity less Quantity Deviation less
Quantity Received is mapped to SCM’s Order Quantity.
Quantity Deviation The amount of change to the original order quantity.
Quantity Received Amount received into stock.
Line number (PISQ) Maps to line number.
Buyer number The buyer for this line item.
Vendor number The vendor for this line item.
Requisition number If an order has yet to be created, this is the requisition ID.
Purchase unit of measure
Unit of measure conversion factor

POBLKT Mapping to SCM’s Purchase file

Field Comments
Warehouse
Item number Maps to Part ID
Order number Order ID is composed of order number and blanket
release sequence number.
Line number (PISQ) Maps to Line number.
Blanket release sequence Included in Order ID.
number
Purchase order due date Maps to the date the order is to arrive in stock.
Quantity this release Sum of Quantity this release plus Release Quantity
Deviation less Release Quantity Received
Blanket Release Quantity The amount of change to the original quantity for this
Deviation release.
Release Quantity Received The amount received to stock.
Buyer number The buyer for this line item from POITEM.
Vendor number The vendor for this line item from POITEM.
 Page B-14
Contents Index
Mapping XA Files to SCM Files

REQHDF Mapping to SCM’s Purchase file

Field Comments
Item ID Maps to Part ID
Requisition number Maps to Order ID
Requisition due date Maps to the date the order is to arrive in stock.
Original order quantity Maps to Order Quantity
Line number Maps to Line Number
Buyer number Maps to Buyer ID
Requested vendor Maps to vendor ID.

OLPFCS mapping to SCM’s Forecast file

Field Comments
Warehouse
Creation date Maps to SCM’s Forecast ID. Creation date is normally
the date the forecast was created.
Item ID Maps to Part ID
Period beginning date Maps to Target Completion
Forecast quantity Maps to Forecast Quantity

The following field is user populated in the SCM Forecast Interface (TPFCST) file:

Field Comments
Part family Literal values are:
FAMILY: Forecast is for abstract item such as a Planning
Bill. A forecast is consumed by parts within the same
family.
FULL: Forecast is consumed by any sales order that
requires this part. Used for general items and pull signal
parts.
BLANK (Null): Forecast is consumed only by sales order
for only a specific item.
Note: For an unconsumed forecast that is earlier than the system date, SCM will
place the forecast on the system date.

KBC considerations
For a KBC item, the part ID is (only) the item number, so SCM will plan the forecast
using the item bill and routing in EPDM.

MBADREP Mapping Customer Line Item file to SCM’s Sales file

Field Comments
Warehouse
Company number Included as part of SCM’s Customer Order ID.
Order number Included as part of SCM’s Customer Order ID.
 Page B-15
Contents Index
Mapping XA Files to SCM Files

Field Comments
Release number Included as part of SCM’s Customer Order ID.
Only the last 3 digits are used for release sequence.
Kit release sequence Included as part of SCM’s Customer Order ID.
Only the last 3 digits are used for kit sequence.
Line Item Sequence Maps to Line Number.
Item number Maps to Part ID.
Request date Closed orders with a request date later than the current
period beginning date are included for the purpose of
consuming the current period’s forecast.
Latest Promise date Is defined by SCM to be the date the item leaves the
shipping dock. Shipping lead time to the customer is
subtracted from Request Date to establish SCM’s
promise date. Shipping lead time is found in the COM
MBAQREP file.
Customer ID This information is obtained from the COM MBC6REP
file.
Open to Pick Original release quantity less Open to Pick Quantity
maps to SCM’s Quantity Shipped.
Selling Price Maps to SCM’s Selling price in Sales File. Converts from
Pricing UM to Stocking UM. Gives selling price in local
currency.
Selling Price = Local Currency Selling Price /
Order Stock UM conversion rate from
MBADREP file

KBC considerations
For a KBC item, the Part ID is composed of Item number + a sequence number
assigned by the APS Bridge. This Part ID is the same one used to populate the SCM
part, bill, and routing files from the KBC configuration files.
 Page B-16
Contents Index Mapping XA Files to SCM Files

OLCSBL Mapping Offline Customer Line Item file to SCM’s Sales file
This file is used when Sales Backlog is loaded by offline load.

Field Comments
Company number
Customer order number Order ID
Item sequence number
Warehouse
Item number Maps to Part ID
Original promise date Maps to Promise Date
Current promise date (not used) Maps to Promise Date
Original due date Maps to Original Projected Completion
Current due date (not used) Maps to Projected Completion
Request date
Unshipped order quantity
Shipped quantity
Customer number Maps to Customer ID
Selling price Maps to Selling price
Promise date change flag (not
used)
Due date change flag (not used)

KBC considerations

For a KBC item, the Part ID is (only) the item number, so SCM will plan these orders
using the item bill and routing in EPDM.
 Page B-17
Contents Index Mapping XA Files to SCM Files

APS Bridge Interface Control file controls processing on SCM and

Bridge
Option 1 on the APS Bridge Maintenance menu (AXAM01) provides panels where
you define information used in APS processing.

Manufacturing Order Auto Release:

No, do not use auto release for mfg orders. IM order entry batches that are populated with
create mfg order messages during Putback are placed in Suspend mode.
Yes, use auto release for mfg orders. IM order entry batches that are populated with create
mfg order messages during Putback are released automatically.
Release horizon:
Specify the number of days to use for release horizon for mfg orders.
Print audit reports:
Specify whether or not to print audit reports generated by the Load process. Audit reports
contain a list of all the data processed along with the errors to indicate if there were any
problems found during the load process. For start up implementation, recommendation is
Yes.
Days to auto reschedule:
Specify minimum days to reschedule to avoid generating messages and updates when the
difference between the original date and new date is less than this number of days. Used
during Putback process.
Putback allowed:
Specify whether or not XA files can be updated by Putback for actions taken on
the Engine.
Consume forecast:
If FCST is not installed, a question appears as to whether user forecasts are to be
consumed by SCM. XA’s forecasts are always consumed by SCM when FCST is
installed.

XA Tailoring Questions that Affect APS

The IM questions in the Install/Tailor questionnaire that affect APS are listed here:
I06 Costing method for inventory accounting? Use standard, average, or last cost?
I25 Interface IM with PCC.
I26 Interface IM with COM.
I28 Interface IM with EPDM.
I36 How many business days in year?
I40 What is the Inventory Reorder Tolerance Percent?
 Page B-18
Contents Index Mapping XA Files to SCM Files
 Page C-1
Contents Index
XA Release 6 APS Bridge REP Interface

Appendix C. XA Release 6 APS Bridge REP Interface

The APS Bridge processes Repetitive Schedules (REP) as well as Manufacturing
Orders (M.O.s). As SCM handles only one type of make order - a work order - APS
Bridge sends a schedule to SCM as a single operation work order with the production
line as the work center. This allows SCM to better plan and schedule a REP schedule
and makes it easier for you to work with schedules in SCM. When the SCM
scheduling results are returned to XA, APS Bridge treats planned "work orders" for
schedule-controlled items as planned REP schedules and interfaces to REP so that
you can create or change schedules as permitted by current REP edits. The bridge
and SCM handle M.O.s as they are handled today when created for a schedule-
controlled item in but outside APS Bridge.

Load to SCM

Facilities / Work Centers

Facilities - work centers, production lines, and work stations are currently sent to SCM
with no calendar ID. SCM uses a default calendar which you must maintain in SCM in
scheduling.
Note: APS Bridge sends the calendar ID to SCM if it is present in the facility record
for a production line. As SCM does not support the import of calendar data, you must
maintain calendars used for production lines in both SCM and if these calendars are
different for each production line.

Routings
For a schedule-controlled item, APS Bridge sends a single operation, operation
sequence 1, as the routing to SCM. The work center for the operation is the primary
production line for the item from the Item Warehouses object. Setup time and run time
are derived from data in the item line record for that production line.

Attribute Value:
Setup Time changeover time + flow time - run time for one unit
Run Time (for one unit) derived from the item rate and item rate flag.

Alternate production lines

If an item revision has item line records for multiple production lines in a warehouse,
APS Bridge sends an alternate routing operation for each alternate (non-primary) line,
with the route priority of 1, 2, etc. and otherwise described in Routings above, using
data from the other line item record. During SCM scheduling, this helps identify when
planned schedules can be moved to another line.
 Page C-2
Contents Index
XA Release 6 APS Bridge REP Interface

Bills of Material
For a schedule-controlled item, APS Bridge sends the bill of material for the primary
production line identified in the item line record, and sets the operation where-used to
1 on all components.

Unreleased schedules
APS Bridge sends unreleased schedules to SCM and identifies them as unreleased
by appending the order status in MOMAST ("00") to the order (schedule) number.

APS Bridge sends a single operation with operation sequence 1, as the order routing.
The work center, setup time, and run time are derived from the data in MOMAST as
described in Routings above.

APS Bridge sends the bill of material identified in MOMAST and sets the operation
where-used to 1 on all components.

Released schedules
APS Bridge sends a single operation as the order routing with operation sequence 1.
The work center, setup time, and run time are derived from the data in MOMAST as
described in Routings above. Quantity good and quantity bad are sent for the
operation using quantity received and quantity scrapped, respectively, in MOMAST.

For MODATA records sent to SCM, APS Bridge sends components only for active
operations and sets the operation where-used to 1 on all components sent.

SCM processing
SCM views a schedule as one operation (one scheduling entity) on the production line
to more accurately plan and schedule it.

To have SCM plan an item schedule for no more than what can be made in one day -
- or one shift -- enter that quantity into the order maximum quantity in the Item
Warehouses object. APS Bridge sends that field to SCM as the Make_Max_Lot
quantity, and SCM never plans a "make" order (schedule) for greater than that
quantity.
Note: For a single sales order greater than the Make_Max_Lot quantity, SCM plans
as many orders as required to meet the sales order quantity.
Note: For schedules with a flow time of more than a day, all components for that
schedule are scheduled by SCM as required on the schedule start date, as a
schedule has only one operation in SCM.
Note: SCM sees the status or progress of a schedule only when items are reported
as received into inventory or scrapped, rather than at operations or reporting points. If
an item takes longer than a day to produce, SCM will not know the status of
production, as APS Bridge sends no Jobs In Progress records and hours are not
reported for schedules as they are for manufacturing orders.

In scheduling a work center, SCM assumes that back-to-back operations for the same
item and operation number for different work orders require no setup for the second
 Page C-3
Contents Index
XA Release 6 APS Bridge REP Interface

work order for the item. REP can also schedule overlap between schedules for
different items based on an overlap code in item line. APS Bridge does not duplicate
that overlap scheduling for SCM.

During scheduling, SCM can identify by color on the display panel, the operations that
you define as having alternate work centers. This helps identify operations that can be
off-loaded from an overloaded work center. SCM can identify alternate operations
only for planned orders and not for open orders (unreleased or released schedules).
APS Bridge sends all defined item line data for an item revision in a warehouse as
alternate operations with a routing priority greater than 0 so you can identify items that
can be produced on another line.
Note: SCM allows you to off load an operation on planned and open orders,
whether or not an alternate is defined. APS Bridge only processes the off loads in
Putback if they are allowed in REP.
Note: If different components are required to produce an item on another line and
you off load a schedule to that line, SCM will not schedule those components until
they are loaded during the next load.

Putback from SCM

New Schedules
For planned orders for schedule-controlled items for a valid production line, APS
Bridge generates an action message that creates an unreleased schedule when the
message is processed. A planned order for an invalid production line received from
SCM generates an error message. You can use current REP function to maintain,
release, and/or prime the schedule.

Unreleased schedules
SCM can recommend that unreleased schedules be canceled or that the date,
quantity, or production line be changed. APS Bridge generates cancel or change
messages when the change is for a valid production line. A change to a production
line with no item line record generates an error message. Current REP function can
also be used to change, release, and/or prime a schedule.

Released schedules
SCM can recommend that released schedules be canceled or that the date, quantity,
or production line be changed. APS Bridge generates change messages that change
or cancel the released schedule by changing the quantity to 0, when processed.

If the schedule is primed, APS Bridge generates change messages only if changes
are allowed in tailoring option 2 in the REP control file (menu AMAX01, option 1,
display AMQ5Z1). If changes to primed schedules are not allowed in REP, a change
to a primed schedule generates an error message.
 Page C-4
Contents Index XA Release 6 APS Bridge REP Interface
 Page GL-1
Contents Index
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.

file transfer protocol. See FTP.

forecast. An estimate of customer (independent) demand for an item for a specific

period in the future.
 Page GL-2
Contents Index
Glossary

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.

load. In APS, the process of transferring data required by the APS engine from the
XA and APS files on the System i to the APS engine on the NT Server.
Loads may transfer all data required by the engine or data from a subset of files. The
load process may be run immediately or set up to run on a specific date and time.
Contrast with putback.

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.

putback. In APS, the process of transferring the orders and schedules generated
by the APS engine on the NT Server back to the System i for appropriate action. This
process is triggered on the System i and can be run immediately or set up to run on a
specific date and time. Contrast with load.

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.

translate program. In programming, to convert a program from one language to

another. Translation is performed by special programs such as compilers,
assemblers, and interpreters. Also, data translate programs are used to reformat
data from one database to be used by another database.

utility. A program designed to perform a particular function; the term usually refers
to software that solves narrowly focused problems or those related to computer
system management.

utility commands. In APS, the programs on the server used to interface with the
engine’s database.
 Page IN-1
Contents Index
Index

Index
A
AMVPOF—Putback Transaction Tailoring Offline Load panel 4-28
APS Bridge Interface Control file controls processing on T-P and Bridge B-17
APS Bridge, using 4-1
AXAPSQ (load and putback job queue) 2-1

B
blanks, special handling 2-2

C
cancelling manufacturing orders 2-7
Capable to Promise function 2-9
changing component required dates 2-7
changing manufacturing orders 2-6
Client Access Remote Command (RUNRMTCMD) 3-2
creating manufacturing orders 2-5
creating purchase orders and requisitions 2-7
Customer Orders on Hold option 4-35

F
FACMST mapping to Thru-Put’s Work Centers file B-5
File Transfer Protocol (FTP) 3-2
files
mapping XA files to Thru-Put files B-1, C-1
offline file formats A-1
offline, special data requirements A-2
updating the Interface Control file 4-3
forecasts 2-9

H
Hold Code Filters (Select) panel–MO0640 4-17
Hold Code Filters panel–MO0641 4-19

I
initiate extract/putback 4-38
initiate Extract/Putback panel–MO050R 4-39
Inquiry 4-34
Inquiry panels
Customer Orders on Hold panel (MO0711) 4-36
Interface Control Maintenance (Page 1 of 2) panel–MO0551 4-6
Interface Control Maintenance (Page 2 of 2) panel–MO0552 4-9, 4-11, 4-14
Interface Control Maintenance (Select) panel–MO0550 4-4
ITEMBL mapping to Thru-Put’s Inventory file B-3
ITEMBL mapping to Thru-Put’s Part file B-4, C-2
ITMPLN mapping to Thru-Put’s Part file B-5
ITMRVA mapping to Thru-Put’s Part file B-3
ITMRVB mapping to Thru-Put’s Routing file C-2
ITMRVC mapping to Thru-Put’s Part file B-3

L
list of files interfacing with Thru-Put B-1
 Page IN-2
Contents Index
Index

load process, understanding 2-1

load, edits 2-2

M
maintaining Hold Code filters 4-16
maintenance option 4-2
maintenance panels
Hold Code Filters (Select)–MO0640 4-17
Hold Code Filters–MO0641 4-19
Interface Control Maintenance (Page 1 of 2)–MO0551 4-6
Interface Control Maintenance (Page 2 of 2)–MO0552 4-9, 4-11, 4-14
Interface Control Maintenance (Select)–MO0550 4-4
Putback Transaction Tailoring (MO0590) 4-32
manufacturing transactions, putback 2-4
mapping XA Files to Thru-Put Files B-1
Mapping Purchase Orders to Thru-Put’s Purchase file B-13
MBADREP Mapping Customer Line Item file to Thru-Put’s Sales file B-14
MO050R–Initiate Extract/Putback panel 4-39
MO0550–Interface Control Maintenance (Select) panel 4-4
MO0551–Interface Control Maintenance (Page 1 of 2) panel 4-6
MO0552–Interface Control Maintenance (Page 2 of 2) panel 4-9, 4-11, 4-14
MO0570-Putback transaction tailoring (Select) panel 4-31
MO0580–Review and Approve Putback Messages panel 4-41
MO0581-Print Putback Reports panel 4-44
MO0590-Putback Transaction tailoring panel 4-32
MO0640–Hold Code Filters (Select) panel 4-17
MO0641–Hold Code Filters panel 4-19
MO0711—Customer Orders on Hold inquiry panel 4-36
MO310R–Offline Maintenance Edit List 4-24
MO311R–Offline Load Audit List 4-24
MO312R–Offline Maintenance Edit List 4-21
MO390R–Offline Maintenance Edit List 4-27
MO391R–Offline Load Audit List 4-27
MO4990–Review and Approve Putback Messages panel 4-50
MODATA mapping to Thru-Put’s Work Order Allocation file B-12
MOMAST mapping to Thru-Put’s Work Order Header file B-8
MOROUT mapping to Thru-Put’s Jobs in Progress file B-8, B-10
MOROUT mapping to Thru-Put’s Work Order Routing file B-11

O
offline data special requirements A-2
offline file formats A-1
Offline Load of Customer Order Backlog 4-21
Offline load of period forecast 4-24
Offline load of putback transaction tailoring 4-27
OLCSBL Mapping Offline Customer Line Item file to Thru-Put’s Sales file B-16
OLPFCS mapping to Thru-Put’s Forecast Interface file B-14

P
POBLKT Mapping to Thru-Put’s Purchase file B-13
POITEM Mapping to Thru-Put’s Purchase file B-13
Print Putback Reports select panel-MO0581 4-44
processing offline files A-2
PSTDTL mapping to Thru-Put’s BOM file B-2
PSTHDR mapping to Thru-Put’s BOM file B-2, C-1
purchase transactions, putback 2-7
 Page IN-3
Contents Index
Index

Purchasing’s auto release codes 2-7

putback for manufacturing transactions 2-4
putback for purchase transactions 2-7
putback messages, review and approve 2-9
putback process, understanding 2-2
Putback transaction tailoring 4-30
putback transaction tailoring offline 4-27
putback transactions, list of 2-3

R
reports
audit (during Load process) B-17
Offline Load Audit List–MO311R 4-24
Offline Load Audit List-MO391R 4-27
Offline Maintenance Edit List (MO310R) 4-24
Offline Maintenance Edit List (MO390R) 4-27
REQHDF Mapping to Thru-Put’s Purchase file B-14
Review and Approve Putback Messages 4-49
Review and Approve Putback Messages panel–MO0580 4-41
Review and Approve Putback Messages panel–MO4990 4-50
Review Load Messages 4-45
RTGOPR mapping to Thru-Put’s Routing file B-7, C-3
RUNRMTCMD 3-2

U
unconsumed forecasts 2-9
updating the Interface Control file 4-3
using Client Access Remote Command (RUNRMTCMD) 3-2
using File Transfer Protocol (FTP) 3-2
 Page IN-4
Contents Index Index