Using ERPBridge for MAPICS for OS/2 and Windows NT
Using ERPBridge for MAPICS for OS/2 and Windows NT
About this Book
ERPBridge for MAPICS for OS/2 and Windows NT Overview
The TC Script Overview
TC Script Details
Logon
Transaction Formatting
Transactions Longer Than 128 Bytes
Joining Long Transactions
Transaction Formatting Modifications
Error Handling Subroutines and Miscellaneous Utilities
Message Handling
Input Inhibit Handling
Real Number Formatting
Logoff Procedures
MAPICS XA PM&C Release 2.2 and Release 2.3 Differences
Performance
Multiple Sessions
TC Settings
Transaction Data Integrity
Syntax Checking
PM&C Transaction Structure Under MAPICS XA
Function Key Templates and Function Key Definitions for MAPICS XA
Version A Template - Discrete Manufacturing
Template A, F1
Template A, F2
Template A, F3
Template A, F4
Template A, F5
Template A, F6
Template A, F7
Template A, F8
Template A, F9
Template A, F10
Template A, F11
Template A, F23
Template A, F24
Template A, F25
Template A, F26
Template A, F27
Template A, F28
Version B Template - Stock Room
Template B, F1
Template B, F2
Template B, F3
Template B, F4
Template B, F5
Template B, F6
Template B, F7
Template B, F8
Template B, F9
Template B, F10
Template B, F11
Template B, F12
Template B, F13
Template B, F14
Template B, F15
Template B, F16
Template B, F17
Template B, F26
Template B, F27
Template B, F28
Version C Template - Receiving
Template C, F1
Template C, F2
Template C, F3
Template C, F4
Template C, F5
Template C, F6
Template C, F7
Template C, F8
Template C, F26
Template C, F27
Template C, F28
Version D Template - Fast Track Time and Attendance
Template D, F26
Template D, F27
Template D, F28
Version E Template - Quality Control
Template E, F1
Template E, F2
Template E, F3
Template E, F4
Template E, F5
Template E, F6
Template E, F23
Template E, F24
Template E, F25
Template E, F26
Template E, F27
Template E, F28
Version F Template - Repetitive Manufacturing
Template F, F1
Template F, F2
Template F, F3
Template F, F4
Template F, F5
Template F, F6
Template F, F7
Template F, F8
Template F, F9
Template F, F10
Template F, F11
Template F, F23
Template F, F24
Template F, F25
Template F, F26
Template F, F27
Template F, F28
Version G Template - Discrete Manufacturing-Uncontrolled Warehouse
Template G, F1
Template G, F2
Template G, F3
Template G, F4
Template G, F5
Template G, F6
Template G, F7
Template G, F8
Template G, F9
Template G, F10
Template G, F11
Template G, F23
Template G, F24
Template G, F25
Template G, F26
Template G, F27
Template G, F28
Version H Template - Stock Room-Uncontrolled Warehouse
Template H, F1
Template H, F2
Template H, F3
Template H, F4
Template H, F5
Template H, F6
Template H, F7
Template H, F8
Template H, F9
Template H, F10
Template H, F11
Template H, F12
Template H, F13
Template H, F14
Template H, F15
Template H, F16
Template H, F26
Template H, F27
Template H, F28
Appendix A. When Things Don't Work As Expected
Using ERPBridge for MAPICS
(1)
describes the operation and use of the ERPBridge for MAPICS for OS/2 and Windows NT product, a program
that is used to monitor the status of various plant floor activities and
communicate the status from a personal or industrial computer to the host
system.
Review the entire document before installing the program, and then keep the
document for future reference. Installation and basic configuration information
for this product is contained in the DCConnect Installation & User's Guide.
References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
of IBM's intellectual property rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in conjunction
with other products, except those expressly designated by IBM, is the user's
responsibility.
IBM may have patents or pending patent applications covering subject matter
in this document. The furnishing of this document does not give you any license
to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
500 Columbus Avenue
Thornwood, NY 10594
U.S.A.
The following terms, that are denoted by an asterisk (*) in this
publication, are trademarks or service marks of IBM Corporation in the
United States and/or other countries:
PLANT FLOOR SERIES
| OS/2
|
GEARBOX
| Personal System/2
|
PS/2
| AS/400
|
System/36
| Personal Computer
|
Operating System/2
| IBM
|
For online versions of this documentation, we authorize you to:
- Copy, modify, and print the documentation contained on the media, for
use within your enterprise, provided you reproduce the copyright
notice, all warning statements, and other required statements on each
copy or partial copy.
- Transfer the original, unaltered copy of the documentation when you
transfer the related IBM product (which might be either machines you
own, or programs if the programs' license terms permit a transfer).
At the same time, you must destroy all other copies of the documentation.
You are responsible for payment of any taxes, including personal
property taxes, resulting from this authorization.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow the exclusion of implied warranties,
so the above exclusion might not apply to you.
Your failure to comply with the terms above terminates this authorization.
Upon termination, you must destroy your machine-readable documentation.
This document assumes that you have a basic knowledge of the IBM Personal
Computer and specific knowledge of the machine that is the target of this
installation.
In addition to having a general knowledge of data processing, you should be
familiar with the following:
- IBM 7527 Data Collection Terminal
- IBM 7526 Data Collection Terminal
- IBM 7524 Data Collection Terminal
- IBM OS/2
- Windows NT
- DCConnect
This publication is intended for use by those programmers or analysts and
other technical personnel who are responsible for the installation,
configuration, and operation of ERPBridge for MAPICS for OS/2 and Windows NT.
Review this document thoroughly before attempting to perform the described
activities. When a sequence of steps is specified, complete each step in the
order given, ensuring that steps are not skipped unless they are designated as
optional. Otherwise, the activity may not be successfully completed, and errors
may occur.
This section lists the documentation needed to review and reference while
performing the installation and configuration procedures described in
Installing and Configuring Data Collection Connection Program for
OS/2.
- IBM 7527 Data Collection Terminal (Models 001 and 002) Installation,
Operation, and Problem Determination
This publication provides instructions on how to install and operate the IBM
7527 Data Collection Terminal.
- IBM 7527 Extended Terminal Services Technical Reference
This publication provides instructions on how to install and operate the 7527
Extended Terminal Services program that runs on the 7527 Data Collection
Terminal.
- IBM 7526 Data Collection Terminal Installation, Operation, and Problem
Determination
This publication provides instructions on how to install and operate the IBM
7526 Data Collection Terminal.
- IBM 7526 Data Collection Terminal Programming Technical Reference
This publication provides a general overview of the DCT's functions and
capabilities.
- IBM Data Collection Connection User's Guide
This publication describes how to configure and operate DCConnect.
ERPBridge for MAPICS for OS/2 and Windows NT is a ready-to-use
data collection solution for
customers of the MAPICS XA manufacturing and Production Monitoring &
Control (PM&C) modules. This product consists of a set of DCConnect
transaction programs, Transaction Connection (TC), and
TC scripts. This permits the collection of shop floor transactions to be
entered into the data collection terminal (DCT) and be forwarded to the MAPICS
XA PM&C application in realtime.
Product Features
Realtime collection of shop floor data optimizes the use of MAPICS XA
manufacturing modules. It provides immediate access to up-to-the-minute data on
inventory, work orders, machine utilization, resource allocation, and other
important information. Transactions entered at the DCT are immediately
entered into PM&C for update of the MAPICS XA database. Production control,
plant management, and other personnel in need of the latest data from the plant
floor are provided immediate access.
After defining the DCT network in DCConnect, you need to configure only the
ERPBridge for MAPICS for OS/2 and Windows NT product with your host signon ID and password. This
minimizes the time required for implementation of an automated data collection
system.
ERPBridge for MAPICS for OS/2 and Windows NT utilizes the features of TC to:
- Format and send transaction data to the PM&C application.
- Enable the use of multiple ERPBridge for MAPICS for OS/2 and Windows NT sessions to feed data to
one or more MAPICS XA environments, or to run parallel sessions to enhance
throughput.
- Provide the means to create a two-way interface, by writing additional
TC scripts or changing those provided with this product.
*
The ERPBridge for MAPICS for OS/2 and Windows NT product provides transaction programs for eight
different 'templates' of MAPICS XA transactions. A 'template' is a
set of transactions that are related in function. Listed below are eight MAPICS
XA templates with the transactions that make up each template.
For details of a template, select it from following list.
There are 97 transaction programs spread across the eight templates. Some of
these transaction programs are in more than one template and have the same
prompts. Other transactions programs are in more than one template and have
different prompts in the different templates.
Within ERPBridge for MAPICS for OS/2 and Windows NT the eight different templates of transactions
are set up in eight different function groups. These function groups can then be assigned
and downloaded to terminals. There are several different models of terminals
with different screens, keyboard layouts and transaction program capabilities.
Different versions of each template were created for each terminal
model.
All templates are provided for the 7526 model 200, 7527 model 001 and 002,
and the 7524 with the exception of template D on the 7524.
TC directs the interaction between the data collection PC and the host
application, MAPICS XA Production Monitoring & Control (PM&C). The
script is a text file, written in the TC scripting language that is executed
during startup and shutdown of the MAPICS application in DCConnect and
as each transaction arrives in the DCConnect mailbox.
The executable portion of the script during transaction processing
is ruled by the terminal's function group name and the function key
used to initiate the transaction data entry. Logon and logoff portions
of the script are executed during startup and shutdown of the TC session.
These portions are described below in greater detail.
Four script files are provided, two of which are installed based on your
selection of the MAPICS installation. These files are:
The STARTxx.SCR files contain basic TC operational parameters
and initial settings of certain TC user variables that are required for
proper operation of the system.
The user variables set in this script file may be set or changed in either
of two methods: by changing the values in the ERPBridge for MAPICS for OS/2 and Windows NT Settings
Notebook, or by editing the file. The preferred method is to use the
Settings Notebook since some of the data set here is also placed in the
DCX2.INI file and used when the DCConnect Server is started.
Modification of the STARTxx
file should be all that is necessary for normal operation of ERPBridge for MAPICS for OS/2 and Windows NT. If
the "Procedure to Call" and "Library" are not entered in the STARTxx file
as part of the startup routine, that data may be incorporated into the AS/400
user-profile that has been created for the data collection controller. These fields
have all been assigned default values, so if using the AS/400 user profile for this
information, remove the data contained in these parameters in the MAPICS Settings
Notebook.
Click here to see the The Settings Notebook
(SeeMAPICS Settings Notebook Pages) pages.
If editing this file manually, use a text editor such as, OS/2's "E" or
the Windows NT "Notepad" to change any of following fields in the
STARTxx.SCR file. The editable fields are:
- Userid
- Password
- Procedure
- Library
The editor that you select must not insert additional characters in the text
such as tabs, and other possibly non-displayed control
characters that may interfere with the operation of TC.
Do NOT change the overall structure of this file. The DCConnect MAPICS Settings
Notebook requires the file structure of the STARTxx.SCR file to
remain as is. Changing this file structure may cause it to become unreadable
by the Settings Notebook.
Other fields set here are the Sign On Rate, DCConnect Mailbox name, Controller,
and Session ID. For additional information on these parameters, click on the
highlighted item below:
This section is provided as an overview of the steps necessary to set up
PM&C for receiving transactions. For comprehensive information on
installing, configuring, and using PM&C, refer to the documentation
provided with that product.
The following steps are necessary to create a working data collection
user profile on the AS/400.
- Sign on to the AS/400 with a userid having both AS/400 Security Officer
and MAPICS Security Administrator authority.
- From the PM&C main menu, choose option 4 - Administration
- On the Administration menu, choose option 6 - Create Data Collection
User Profile.
- Enter the USERID and PASSWORD the ERPBridge for MAPICS for OS/2 and Windows NT system
is to use for signing on to the AS/400.
- Exit to the MAPICS Main Menu
- Sign on to Cross Application Support
- Select option 3 - Maintenance/Change
- Select option 8 - Security Password Maintenance, then option 1 - Maintain
Security Passwords
- Enter the MAPICS Security Administrator userid
- On the Security File Maintenance screen, enter the ERPBridge for MAPICS for OS/2 and Windows NT
userid that was created in PM&C, action code of "A" for add, and "J"
for the Production Monitoring and Control application.
- Under "CLEARANCE", change all the N's to Y's
- Exit MAPICS and test by signing on to the AS/400 using the ID and Password
just created for ERPBridge for MAPICS for OS/2 and Windows NT.
NOTE: The resulting screen may be completely blank. The
PM&C data entry screen is an unformatted 128 byte input screen containing no
other data, and depending on the record separator character selected for the installed
emulation program, the input record may display as underscores, squares,
vertical bars between input characters, or nothing at all. Press PF24
to exit this procedure.
The Sign On Rate specifies, in seconds, the amount of time the TC script will
wait before attempting another sign-on cycle after host communications have
been interrupted. This is shown in seconds
in the DCConnect MAPICS Settings Notebook, and in milliseconds
in the STARTxx.SCR file.
The Mailbox name specified in the DCConnect MAPICS Settings Notebook and in the
STARTxx.SCR file must exactly match the Mailbox defined in DCConnect
Mailbox Configuration. The default value is "mapics_xa".
This field is case sensitive.
The Controller id is an arbitrary alphabetic letter assigned to enable
identification of the source of the transaction arriving at the host.
This letter should be unique to a particular TC session on a PC. The default
value is "A".
The Session ID here refers to the CM/2 or PCOMM short session ID
configured in the emulator. It provides an identifier for
TC to link to a particular emulated session. The default value is "A".
At the end of the STARTxx.SCR file is an imbed command for
the HCMxx.SCR file
that contains all the logon, logoff, transaction handling and error handling commands.
Each HCMxx.SCR file is comprised of three major sections. The first
section is the Logon sequence that contains all required information for
locating the AS/400 signon screen, entering the USERID and PASSWORD, and
starting the proper procedures for PM&C Data Collection.
The second and largest section of this script contains all the
transaction data handling
routines. It is divided into "function groups" that correspond with the MAPICS
PM&C templates and DCConnect function groups. Each unique transaction has a
set of fields that are appended together
before being placed on the host screen. Where multiple function groups have the
same transaction, a GOTO command is used to access these transactions rather than
duplicate all of the data handling commands.
The last section is a series of subroutines that handle error recovery when
unexpected results are received from the host. These recovery routines should
be reviewed
because under certain conditions TC may be unable to find a
SIGNON screen or a data input screen. In the event of an unknown error occurring, the
error is logged in the TC error log
and the CM/2 or PCOMM session is cycled. You may refer to the commands in the
Transaction Connection Series User's Guide to enhance the
error handling and recovery scheme provided. The error recovery portion
of the TC script handles most of the host system and
application failures, but a customized system may be of value in certain cases
where the AS/400 system and MAPICS have been modified.
The parameters selected in this area determine the overall operation of TC
processing. Operational parameters govern the actions of TC during runtime.
These parameters are typically defined at the very beginning of the TC script.
They are the only TC commands that may be placed outside of the Logon/Logoff,
or StartKey/StartMatch pairs. The HCMxx.SCR file contains all of the
operational parameters. These parameters are defined as follows:
TRACE
| When TRACE is enabled, it creates a file in the directory from which TC
was started that shows the execution and the results of each command as it is
executed. This function is utilized during debugging of the script. Once data
collection testing is completed, TRACE should be turned off to improve system
performance. The default setting of the TRACE command is set to OFF. Removing
the "//" before the TRACE command in the HCMxx.SCR file sets the TRACE
command to ON.
|
SILENT
| Turns the beep OFF when the TC window on the PC is updated or the ENTER
key is pressed. Beeps which occur when the host screen is updated may be enabled
or disabled in the emulator (PCOMM) configuration.
|
NO_DISPLAY_EXECUTE
| Shows executed commands as they happen. The default setting is set to OFF
and this results in better system performance. Changing the setting to ON
causes a reduction in this performance. TC displays on the PC screen in
realtime, each TC command as it executes. Similar to the TRACE command,
its benefits are as a debug facility. Resulting information is not logged to the
disk. Removing the "//" in front of this command causes the TC to display in
realtime, each executed command. It can be enabled after TC is started by
clicking on "DISPLAY" on the command bar of the TC window, followed by "ON".
|
The following sections provide additional details on the TC scripts
including information on how they may be modified for customized data
collection systems.
The commands contained between StartLogon () and EndLogon () in the TC script
file are executed each time the TC session is started. This script calls a
subroutine that handles obtaining the sign on screen
and entering the required data. This "SIGNON" subroutine is described below.
The following line,
Check_Screen ( "Sign On" , 1, 36, 5, NO_SIGNON_SCREEN )
where "Sign On" is the the character string being searched for,
1 is the row number
36 is the column number
5 is the maximum length of time to search
NO_SIGNON_SCREEN is the label of the script to branch to
in the event the string isn't found.
is repeated several times in this section of the script. It is used to
identify the initial AS/400 signon screen. If the AS/400 has been configured
with a customized signon screen, and the characters "Sign On" are not displayed
on row 1, column 36, these lines must be changed to permit the TC script to
identify the initial signon screen. Choose some sequence of characters that are
displayed on the signon screen and are unique to this particular screen, insert
them between the double quotes. Modify the row and column location of those
characters. Note that the search utility is case sensitive. The string can
vary in length as long as it is displayed on a single line. Longer lengths
require a longer time to check and can contain any valid keyboard character less
than ASCII 126 (alpha-numeric characters and most common symbols). When changing
the character string in the Check_Screen command Do NOT change the
labels called at the end of the command. If TC cannot identify the signon screen,
the logon subroutine
fails and TC will not successfully logon, nor recover after a communications
failure.
If the AS/400 signon screen is not available because the host connection is
down or TC cannot identify the signon screen, this section of the TC script
is designed to process several actions such as pressing PF24, looking for an AS/400
command line and entering "SIGNOFF", and others. If these actions do not produce
a signon screen, TC delays for one minute and repeats its attempts to obtain a
signon screen.
Commands may be added to any of the labeled areas of this subroutine to force
TC to make additional attempts at recovery.
The transaction formatting is the section of the script where data fields entered at
the DCT are reformatted and placed in the correct sequence for MAPICS PM&C.
Transaction formats are provided for both MAPICS XA Release 2.2 and 2.3 transactions.
The primary differences between these two release levels from a data collection
point of view, are the length of the Goods Received Note (GRN) field (from 10 to
26 characters), the addition of the Goods Received Invoice (GRNI) field, and the
addition of the Country of Origin field on some receiving transactions.
The scripts and transaction programs provided can be modified to accommodate customer
modifications to their MAPICS XA system. For information on modifying
transaction programs,
refer to the DCConnect User's Guide. Some changes to the
transaction programs may not affect the provided TC scripts. If fields are
removed, added or the length is changed, changing the starting position of data
as it is presented to the host, these scripts must be modified to match the data
as entered.
PM&C Release 2.3 transactions now accommodate a 26 character GRN field. The
expansion of this field causes several transactions to contain more than the
maximum transaction data length of 128 bytes. Due to the date/time
stamp at the terminal,
the maximum length of variable data in a single transaction is 104 bytes. Those
transactions with variable data longer than 104 bytes are accommodated by
breaking the transaction data into two buffers
and sending them individually, in sequence. The DCT transaction program
saves the first half of
the transaction in a user variable, then clears the input buffer (user variable
0) to collect the second half. When the transaction is complete, the user
variable containing the first half is sent to the DCConnect controller, followed
by the transaction data stream that contains the second part of the transaction.
TC contains a facility for storing and retrieving user variables on the
DCConnect PC's disk in a file that is uniquely named for each terminal. When
DCConnect sends the first half of the transaction to TC, it is formatted and
stored in the TC user variable file on the PC's disk. The second part of the
transaction arrives under a new ID, and the first command of the TC script
for this transaction is to restore the saved user variables. TC then formats
the second part of the transaction, appends the two parts together, and sends
them to the AS/400 application as a single unit.
Storage and retrieval of transactions in TC user variables
permits the assembly and transmission of transactions up to any length,
limited only by the number of keys on a terminal to which transactions
may be assigned.
Note: Transaction programs must be broken at the same location as the TC script
formatting for that transaction.
In the following example, all fields, up to and including the FIFO field, are
collected in the transaction program, stored in a TERMINAL user variable, after
which time the terminal transaction record is cleared. At the end of the transaction,
the Terminal user variable is sent to the host, followed by the transaction record.
The transaction program for the "RI" transaction is as follows:
FIFO field
apnd ( UV1, SRC_TRANS_RECORD, TRANSACTION_RECORD );
clrd ( TRANSACTION_RECORD );
the VERY END....
send ( RS_422, SRCUSER_VARIABLE, UV1 );
aka ( SPF4 );
The last two commands send by way of the host port, the contents of
Terminal user variable 1 that contains the first half of the
transaction. This piece goes up with the identifier of the key that
was pressed. For the second half, we've changed the transaction identifier to
Shifted PF4 and the transaction buffer containing the last half is sent up
automatically when the transaction ends.
The corresponding TC script is shown below.
Note: Comments in the script file are preceded by a double slash (//).
// RCPT TO INSPECTION in Receiving assigned to F3
StartKey ( F3 )
C_PF3:
Clear_UV ( UV1)
Append_UV_Ctrl_ID ( UV1 )
Append_UV_Xact_Data ( UV1, LINE, 1, 1 )
Append_UV_Xact_Data ( UV1, ADDRESS, 0, 1 )
Append_UV_Xact_Data ( UV1, YEAR, 0, 12 )
Append_UV_Seq_Num ( UV1 )
Append_UV_Xact_Data ( UV1, TXNDATA, 0, 7 )
Append_UV_Kbd_Data ( UV1, "C" )
Append_UV_Kbd_Data ( UV1, "RI" )
Append_UV_Xact_Data ( UV1, TXNDATA, 7, 9 ) // turnaround
Append_UV_Kbd_Data ( UV4, "16" ) // Append start of Qty field
CallSubroutine ( FORMAT_10_3 ) // Format the Qty field
Append_UV_Xact_Data ( UV1, TXNDATA, 28, 2 ) // unit of measure
Append_UV_Xact_Data ( UV1, TXNDATA, 30, 7 ) // location
Append_UV_Xact_Data ( UV1, TXNDATA, 37, 10 ) // batch lot
Append_UV_Xact_Data ( UV1, TXNDATA, 47, 6 ) // fifo
[1] Save_UVs () // save this part of the transaction to disk.
Release_Xact ()
EndKey ()
- Note that in the first half of the "RI" transaction above, the formatted
data is not sent to the host with the SendData subroutine, but stored
with the Save_UVs () command. This action writes all TC user variables
to a disk. In this case, TC UV1 contains the formatted first half of the
"RI" transaction.
- The second half of the "RI" transaction is assigned by the terminal
to an otherwise unused PF key - Shifted PF4.
- When this transaction arrives, the first action performed by the TC
script is to restore all saved user variables.
- UV1 contains the data formatted above, and since you need to preserve it,
formatting for the second half of this transaction occurs in User Variable 2.
- After formatting the second half, the two pieces are appended together with
the "Append_UV_Xact_Data ( UV1, UV2, 0, 0 )" command.
- When joined, they are then sent to the host as a single unit.
[2] StartKey ( SHIFT_PF4 )
C_SHIFT_PF4:
[3] Load_UVs () // load the 1st part of this transaction from disk.
[4] Clear_UV ( UV2 )
Append_UV_Xact_Data ( UV2, TXNDATA, 27, 3 ) // country of origin
Append_UV_Xact_Data ( UV2, TXNDATA, 30, 10 ) // reference
Append_UV_Xact_Data ( UV2, TXNDATA, 40, 6 ) // reason
Append_UV_Xact_Data ( UV2, TXNDATA, 26, 1 ) // grn invoice
Append_UV_Xact_Data ( UV2, TXNDATA, 0, 26 ) // grn
[5] Append_UV_Xact_Data ( UV1, UV2, 0, 0 )
[6] CallSubroutine ( SendData )
EndKey ( )
The following diagram depicts this splitting and rejoining of transaction
parts. Double click on the item name for viewing.
Joining Long Transactions Diagram
(SeeJoining Long Transactions)
*
Some modifications to the transactions provided may require changes only in
the transaction program that runs in the terminal and no modifications at all to
the TC script. Any changes that prefill a previously required data entry
field or changes to the text of a prompt or message, require changes only in the
transaction program.
If in the Receipt to Inspection transaction, you wanted to pre-fill the Unit
of Measure field with "EA" and remove that prompt from the terminal transaction
program, you edit the transaction program, remove the prompt, and in the
location were the unit of measure was read, change the READ command to APPEND
and add "EA" to the transaction data stream. This adds "EA" at the location
where you previously had to enter "EA" using the keyboard at the DCT. The
transaction data, as sent from the terminal to the PC still contains the same
number of characters in the same position, so the TC script does not need to
be modified.
If you wanted to add or expand a field in the same transaction, such as add a
new field, Vendor Number, after the GRNI field, we would need to add two
commands to the transaction program - a SHOW message command that prompts for
the field followed by a READ that accepts the data entered. In addition, you
need to add a line to the TC script for the RI transaction and change all
the starting offsets (starting position) for all fields following the inserted
field. This example assumes, of course, that MAPICS XA PM&C has been
modified to accommodate the additional field. Following is an example of before
and after picture of the RI transaction.
RI ( uncontrolled warehouse ) Before Modification
StartFunctionGroup ( XA262C )
StartKey ( F6 )
C_PF6:
Clear_UV ( UV1)
Clear_UV ( UV1)
Append_UV_Ctrl_ID ( UV1 ), LINE, 1, 1 )
Append_UV_Ctrl_ID ( UV1 )
Append_UV_Xact_Data ( UV1, LINE, 1, 1 )
Append_UV_Xact_Data ( UV1, ADDRESS, 0, 1 )
Append_UV_Xact_Data ( UV1, YEAR, 0, 12 )
Append_UV_Seq_Num ( UV1 )
Append_UV_Xact_Data ( UV1, TXNDATA, 0, 7 )
Append_UV_Kbd_Data ( UV1, "C" )
Append_UV_Kbd_Data ( UV1, "RI" )
Append_UV_Xact_Data ( UV1, TXNDATA, 7, 9 ) // turnaround
Append_UV_Kbd_Data ( UV4, "16" ) // Append qty start position
CallSubroutine ( FORMAT_10_3 ) // Format the field
Append_UV_Xact_Data ( UV1, TXNDATA, 28, 2 ) // unit of measure
Append_UV_Kbd_Data ( UV1, " " ) // 23 spaces
Append_UV_Xact_Data ( UV1, TXNDATA, 73, 3 ) // country of origin
Append_UV_Xact_Data ( UV1, TXNDATA, 30, 10 )// reference
Append_UV_Xact_Data ( UV1, TXNDATA, 40, 6 ) // reason
Append_UV_Xact_Data ( UV1, TXNDATA, 72, 1 ) // grn invoice
Append_UV_Xact_Data ( UV1, TXNDATA, 46, 26 )// grn
CallSubroutine ( SendData )
In the preceding example, the StartKey (F6) begins a series of actions that take
place when data that was originated on a terminal is assigned to one of the "C"
functions groups arrives in the DCConnect Mailbox. TC User Variable 1 (UV1)
is used to build the transaction data as it is presented to the PM&C
application on the host. The first few lines place into UV1 address data for the
terminal from which the transaction was received such as the line, address and
date or time stamp. Data placed into UV1 may have several sources --
another TC variable, the transaction data stream, or keyboard data as entered
on the "Append_UV..." line and placed between double quotes. An example of these
are the PM&C Template and Transaction ID. The individual fields that follow
are appended to the user variable in the order that PM&C requires them. Note
that the starting offsets, the first numeric parameter on each command, are not
sequential. This is because PM&C uses the transaction fields in a different
sequence than they are entered at the terminal. To maintain consistency with
prior versions of IBM's data collection interface products, the fields are
presented at the DCT in the same order as they always have been, and the field
rearranging takes place in the TC script.
To enter a new Vendor Number field between Reason and GRN Invoice, and to
provide a prompt at the terminal after GRN Invoice, you enter two new commands
(bold) between the prompts for the GRN Invoice and Country of Origin fields in
the transaction program:
Show ( SRC_MESSAGE_FILE, "GRN Invoice...", 2, 1, NONE );
Read ( ALPHA_KEYPAD|SENSOR_PORT, FIXED_LEN_READ, 26 NO_VALIDATION, NONE, ECHO_ON_TIMEOUT );
Show ( SRC_MESSAGE_FILE, "Vendor Number...", 2, 1, NONE );
Read ( ALPHA_KEYPAD|SENSOR_PORT, FIXED_LEN_READ, 5 NO_VALIDATION, NONE, ECHO_ON_TIMEOUT );
Show ( SRC_MESSAGE_FILE, "Country of Origin...", 2, 1, NONE );
Read ( ALPHA_KEYPAD|SENSOR_PORT, FIXED_LEN_READ, 3, NO_VALIDATION, NONE, ECHO_ON_TIMEOUT );
The TC script needs to be changed as follows to accommodate the additional
five bytes of data. You add five to the starting position of every field with a
starting position greater than the GRN Invoice field.
Append_UV_Xact_Data ( UV1, TXNDATA, 28, 2 ) // unit of measure
Append_UV_Kbd_Data ( UV1, " " ) // 23 spaces
Append_UV_Xact_Data ( UV1, TXNDATA, 78, 3 ) // country of origin
Append_UV_Xact_Data ( UV1, TXNDATA, 30, 10 )// reference
Append_UV_Xact_Data ( UV1, TXNDATA, 40, 6 ) // reason
Append_UV_Xact_Data ( UV1, TXNDATA, 73, 5 ) // vendor number
Append_UV_Xact_Data ( UV1, TXNDATA, 72, 1 ) // grn invoice
Append_UV_Xact_Data ( UV1, TXNDATA, 46, 26 )// grn
CallSubroutine ( SendData )
Whenever a new field is inserted or an existing field is expanded
in length, the starting position of all fields with a greater starting
position than the one being added or expanded must be recalculated.
This last part of the TC script handles verification of a data entry
screen and exceptions to normal transaction processing on the host.
While most host conditions have been anticipated and accommodated in
this portion of the script, there may occasionally be a host or
communication problem that has not been foreseen. There are locations
identified by comments in this portion of the script for the addition
of other checking and error recovery that may be required in a
particular installation.
The TC script contains commands monitor and clear messages including
system break messages. Certain MAPICS XA application utilities require the
dedicated use of MAPICS files and procedures, and places the host system in a
"DEDICATED APPLICATION MODE". The ERPBridge for MAPICS for OS/2 and Windows NT script accommodates
those situations by checking any non-data input screen for the word "DEDICATED".
If the word "DEDICATED" is found, the message is cleared and it logs off the
host. The application waits for a period of time, defined as the signon rate in
the MAPICS configuration Notebook in DCConnect, then attempts to logon again.
If "DEDICATED" is found again, this cycle repeats until "DEDICATED" is no
longer found. Other messages that are found are erased.
The "LOCKED" subroutine in this section attempts to handle situations
where the keyboard is in an Input Inhibited state. This subroutine
is called in a number of situations when data cannot be entered. Commands
may be added to or removed from this subroutine to release the keyboard.
MAPICS XA PM&C requires the numeric fields, such as quantity and
transaction amount be formatted prior to entry on the PM&C input data
screen. For example,
-123.4
is formatted by removing the decimal point, placing the sign if any, after the
numeric value and padding all the empty spaces with '0's to the field's maximum
size.
00012340-
This formatting is accomplished with the TC "Format" command.
The subroutines in this section of the TC script take the input string,
formats it as required by PM&C and then appends the formatted field back to
the user variable that is used to hold the transaction data. Comments at the
start of each subroutine indicate the type of formatting being performed.
The commands contained between StartLogoff () and EndLogoff () are executed
every time TC is ended normally. Commands should be added to this section, if
necessary, to return the AS/400 signon screen when the PM&C data entry
procedure is exited.
ERPBridge for MAPICS for OS/2 and Windows NT provides transaction programs and TC scripts for
both Release 2.2 and 2.3 of MAPICS XA PM&C. The primary difference between
the two releases is the length of the Goods Received Note (GRN) field, and the
addition of a Goods Received Note Invoice (GRNI) field in certain transactions
that collect data on materials receipt and return. Based on the Release of the
MAPICS XA system being used, select the release R22 or R23 to match your
particular environment. If you are not using either of these two releases,
select the environment that most closely matches the release being used and make
modifications to transaction programs and scripts as necessary.
Following is a description of the affected transactions and the differences
between the two versions of ERPBridge for MAPICS for OS/2 and Windows NT. The following transactions
are affected:
- Receipt to Dock (RD)
- Receipt to Inspection (RI)
- Uncontrolled Receipt to Inspection (RI)
- Receipt to Stock (RP)
- Uncontrolled Receipt to Stock (RP)
- Purchase Item QC Complete (PQ)
- Vendor Return (VR)
- Uncontrolled Vendor Return (VR)
Differences in these transactions include an expanded Goods Received
Note (GRN) field from 10 to 26 characters, addition of a Goods
Received Note Invoice field (GRNI) which is one character, and
a Country of Origin (COFO) field which is three characters long.
Transactions are included in the following templates:
Template B: Stock Room
Template C: Receiving
Template E: Quality Control
Template F: Repetitive Manufacturing
Template H: Stock Room - Uncontrolled Warehouse
T e m p l a t e s
Transaction B C E F H
----------------------------------------------------------------
Vendor Return (VR) ** X X
Uncontrolled Vendor Return (VR)** X X
Receipt to Dock (RD) ** X
Controlled Receipt to Inspection (RI) **# X
Uncontrolled Receipt to Inspection (RI) **# X
Controlled Receipt to Stock (RP) **# X X
Uncontrolled Receipt to Stock (RP)**# X
Approve Purchase Order (PQ) ** X
Purchase Order Receipt to Inspection (RI) **# X
** Contains expanded GRN field and GRNI (additional sixteen bytes)
# Contains new Country of Origin field (additional three bytes)
Performance of ERPBridge for MAPICS for OS/2 and Windows NT may be influenced by:
- PC's Central Processing Unit (CPU) speed
- AS/400's response time
- Transaction volume
- Load on the systems involved.
Several aspects of ERPBridge for MAPICS for OS/2 and Windows NT that you may change to improve
system performance if transaction throughput is not adequate, are
Multiple Sessions
(SeeMultiple Sessions) and
TC Settings
(SeeTC Settings) .
ERPBridge for MAPICS for OS/2 and Windows NT is designed to process all transactions through a
single ERPBridge for MAPICS for OS/2 and Windows NT session connected to the MAPICS PM&C data
collection interface. This provides adequate performance in most cases. It may
be beneficial to configure multiple 5250 sessions in CM/2 or PCOMM and start
multiple instances of ERPBridge for MAPICS for OS/2 and Windows NT.
MAPICS PM&C's data collection interface is a screen-based interface, and
transaction throughput is never better than what a 5250 native attached
terminal might receive. If average response time after pressing the ENTER key
is three seconds, then it is expected that it takes approximately three seconds
for the data collection system to process a transaction through to PM&C
after it has been logged
into the DCConnect transaction log.
Changing ERPBridge for MAPICS for OS/2 and Windows NT to use multiple ERPBridge for MAPICS sessions
requires several steps:
- Configuration of CM/2 or PCOMM for multiple 5250 sessions
- Creation of multiple Data Collection User Profiles in PM&C
Administration
- Configuration of multiple DCConnect Mailboxes and allocation of different
terminals to those Mailboxes.
- Creation of Multiple ERPBridge for MAPICS for OS/2 and Windows NT applications
- Modification of the STARTxx.SCR file with the new Mailbox name
For CM/2 or PCOMM configuration and PM&C Data Collection User Profile creation,
refer to the documentation for those products. Refer to the DCConnect
User's Guide online documentation provided with that product for creation
of additional Mailboxes. Each Mailbox must have a unique name that is used in
the configuration of the ERPBridge for MAPICS for OS/2 and Windows NT application that is associated
with that Mailbox. Terminals must be assigned to a single DCConnect mailbox or
the result is a duplicate transaction on the host.
To create additional ERPBridge for MAPICS for OS/2 and Windows NT applications copy this DCConnect
application
and change the configuration data that is unique to this particular instance of
ERPBridge for MAPICS for OS/2 and Windows NT, such as CM/2 Short Session ID,
host USERID and PASSWORD, and DCConnect Mailbox.
To improve performance, edit the TC script file that ERPBridge for MAPICS
uses to remove the transaction handling commands for those transactions
that are NOT being handled by a particular instance of ERPBridge for MAPICS for OS/2 and Windows NT.
This action reduces startup compile time and reduces the number of program
instructions TC must search through to find the set of commands associated
with a particular transaction. Remove ONLY commands indicated for terminals or
transactions that are not being used in this application. Avoid the sections of
the TC script designed for system logon and error handling. Create a backup
script of the TC script prior to editing.
TC contains settings that are useful in debugging system problems and
the settings have an adverse effect on system performance. These settings are
TRACE and NO_DISPLAY_EXECUTE.
TRACE builds a trace file of all TC commands and transaction
data and stores this information in the TC subdirectory on disk. It results
in a significant effect on transaction throughput. Refer to the Using the
Transaction Connection Series online book for additional information on
data files. TRACE should be used only when experiencing system problems.
NO_DISPLAY_EXECUTE directs TC to display or not display commands as they
are processed. This is similar to a TRACE command but does not provide detail
and displays data on the TC screen rather than writing the data to a disk
file.
TRACE and NO_DISPLAY_EXECUTE are script commands and their default setting is
set to OFF. Regardless of the script command the setting may be turned ON or
OFF by selecting either TRACE or NO_DISPLAY_EXECUTE from the menu bar of the
TC window. A check next to the item ON in the pulldown indicates TRACE is
enabled. To disable the item, use the mouse button and click on the menu item
and the check is removed.
Every effort has been made to preserve the integrity of collected
transactions, it may be desirable to maintain a log of all transaction data.
In normal operation, DCConnect does not release a transaction from its
logfile until it is successfully handled by ERPBridge for MAPICS for OS/2 and Windows NT. The last
action on a transaction by ERPBridge for MAPICS is a TC Release_Xact
command. The Release_Xact command instructs DCConnect that ERPBridge for MAPICS
has successfully processed this transaction. If the host hardware or
application encounters a problem that causes data loss, the data collected after
the last host backup may be lost if DCConnect's logfile has wrapped and
overwritten the transaction data. A transaction log may be built on the PC's
disk, or data can be sent to a printer with the use of the Log_Data command in
TC. This can be accomplished by inserting a command into the SendData
subroutine. All formatted transactions can then be sent to a file or to a
printer connected to the DCConnect PC.
A section from the Error Handling Subroutines and Miscellaneous Utilities of
the TC script is provided as follows:
StartSubroutine ( SendData )
SENDUV1:
// Get a data input screen
CallSubroutine ( SetupScreen )
// Send the contents of the transaction (UV1) to the host at the
// current location by pressing the ENTER key. If the host doesn't
// respond in 1 minute or if the keyboard is Input Inhibited
// go to "LOCKED".
Send_To_Host ( UV1, 0, 0, 0, 0, NONE, LOCKED )
Send_To_Host ( ENTER, LOCKED )
To log every transaction prior to it being sent to the host, you can add the
command Log_Data as follows:
==> Log_Data ( DCLOG.SAV, UV1, APPEND )
Send_To_Host ( UV1, 0, 0, 0, 0, NONE, LOCKED )
Send_To_Host ( ENTER, LOCKED )
Note: The Log_Data command parameters are:
- A path and file name where log data will be located
- An TC UV number you are saving, for example, UV1
- A Mode, that may be either OVERWRITE or APPEND if desired. Rather than
listing a file name for a transaction log, a PC Printer destination such as LPT1
may be substituted for the filename.ext. This causes each collected transaction
to be spooled to the printer output queue. Each transaction is printed on a
separate page unless the printer is set to ignore page ejects after each print
job.
Logging transaction data impacts system performance and if the APPEND
mode is used, the file created should be purged at regular intervals to avoid
becoming excessively large.
Syntax checking is performed on certain fields by a CFR that is provided
with ERPBridge for MAPICS for OS/2 and Windows NT. The source for CFRs are shipped with the
ERPBridge for MAPICS product. This enables you to add function when needed to
the CFR. Adding syntax checking to a transaction program is a CCFR call
following each read of input that is to be checked. If the field must be
checked in several different ways, then a series of CCFR calls follow. For
example:
READ LEN 7 FROM (KA SA)
CCFR 3, NUMERIC UV0 7
CCFR 3, COMPARE UV0 "0"
CCFR 3, MOD10 UV0 7
In the example above,
the seven digit badge number is checked to see that it contains only numeric
values, that the first digit is a "0", and that the 7 digits passes a Mod 10 check.
If any of the checks fail, a message is displayed by the CFR and then
the CFR returns an ABORT.
The CFR uses function number three with the following parameter strings.
These parameter strings define what checking is to be performed.
COMPARE UV0 "0"
| This is a comparison check. It starts at the beginning of the
specified user variable and must match what is between the double quotes.
|
MOD10 UV0 5
| This is the MOD 10 check. It starts at the beginning of the specified user
variable and continues for the length specified.
|
NUMERIC UV0 5
| This verifies the specified user variable and contains numeric digits only
for the length specified.
|
REAL# UV0 12 3 Y
| This verifies that the specified user variable contains a valid real number.
The first number is the total length (12 in this case). The next value is the
number of digits
allowed to the right of the decimal point. Following that is a Y or N indicating
if a sign is allowed.
|
CHOICE UV0 2 " ERTAZZ"
| This verifies that the value entered is one of several choices. The
comparison starts at the beginning of the transaction and continues for the
length specified by the next value. The string following contains the valid
choices concatenated. In the example above, user variable 0 must
either be blank or contain one of the following three values: ER, TA or ZZ. The
number of bytes between the double quotes must be a multiple of the value before
the string.
|
The error displayed at the terminal as a result of a failed check by
the CFR function defaults to the message programmed in the CFR. These messages may be
replaced by a validation file named MAPXACHK.VAL. If the CFR doesn't find this
validation file, it uses the default messages defined in the CFR itself.
Following is an example of this text file.
Text following the equal (=) sign may be modified to
a desired message text. Remember to make the text no longer than the number
of characters which may be displayed on the terminal type being used.
MSG_COMPARE= Data failed comparison
MSG_MOD10= Failed Mod 10 check
MSG_NUMERIC= Field must be numeric
MSG_REALNUM= Failed real number check
MSG_CHOICE= Incorrect choice
MSG_UNKNOWN= Unknown error
MSG_BAD_PARM= Bad parameter
MSG_PRESS_KEY= Press a key
MSG_READ_UV_ERROR= Error reading User Variable
MAPICS XA requires a specific data structure be adhered to for all transactions,
regardless of the release level or modifications to the transaction being entered.
This section describes that structure.
PM&C Transactions Structure
The following table describes the structure of transactions
required by MAPICS XA PM&C as sent by TC to the host.
While changes may be made to the transaction programs, scripts, and other
areas of the ERPBridge for MAPICS for OS/2 and Windows NT product, the structure defined here,
up to byte 30 of the data stream, should never be changed.
Modifications should only be made to the variable data - bytes 30 through 128.
Formatted-Transaction Data Specifications, MAPICS XA
Byte Number
| Contents
| Description
|
1
| CONTROLLER ID (as defined in the TC Configuration Notebook)
| A 1-byte alphanumeric character chosen by the user when configuring the
MAPICS XA Interface Service to identify the PC from which the transaction
originated.
|
2
|
ARTIC LINE
or
COM Port
| A 1-byte field for the ARTIC line or COM Port attached to the terminal that
sent the transaction. Value 0--7 for ARTIC and 1-4 for the COM Port.
|
3
| TERMINAL ADDRESS
| A 1-byte field for the address of the terminal that sent the
transaction. This can be A-Y, 0-6, or a-p.
|
4-9
| DATE
| The year-month-day the transaction was generated. The format is YYMMDD.
|
10-15
| TIME
| The hour-minute-second the transaction was generated. The format is HHMMSS.
|
16-19
| SEQUENCE NUMBER
| A 4-digit number that indicates the sequence of transactions put into the
spool file. Consecutive transactions sent to the host have consecutive
sequence numbers. This number goes to 0000 after it reaches 9999 and each time
TC is started.
|
20-26
| BADGE
| A 7-digit badge number entered at the terminal by the user.
|
27
| TEMPLATE ID
|
A 1-character template ID:
A = Discrete Manufacturing
B = Stock Room
C = Receiving
D = Fast Track Time and
Attendance
E = Quality Control
F = Repetitive Manufacturing
G = Discrete Manufacturing -
Uncontrolled Warehouse
H = Stock Room -
Uncontrolled Warehouse
|
28-29
| TRANSACTION TYPE
| A 2-character code indicating what the transaction is used for. Example:
ON for Job ON transaction.
|
30-n
| Data
| Starts the remainder of the transaction data. The number of bytes vary
depending on the definition of the transaction program used to initiate the
transaction.
|
The following sample is a formatted transaction for MAPICS XA:
FAA89122514325521340005611AON311111116WORKLI
The transaction was generated at Terminal A on communications line 1 of the
PS/2 whose Controller ID was F. The transaction was generated by
pressing key X (F24), which was set up to read an employee badge containing seven
digits, a turnaround number of nine digits, a work center value of five
characters, and a job type of one character. This is a Job ON transaction.
The following is a breakdown of the transaction data used in
the example:
F
| Controller ID
|
A
| The terminal is on ARTIC line 1
|
A
| The terminal address is A
|
891225
| The transaction was generated on December 25, 1989
|
143255
| The transaction was generated at 2:55 PM
|
2134
| The sequence number of the transaction
|
0005611
| The 7-character employee badge number
|
A
| Template A for Discrete Manufacturing was used
|
ON
| The transaction type is Job ON
|
311111116
| The 9-digit turnaround number entered by the user
|
WORKL
| The 5-digit work center
|
I
| The 1-digit job type
|
This section describes the Production Monitoring and Control (PM&C)
transactions that are supported by DCConnect and ERPBridge for MAPICS for OS/2 and Windows NT to run
with MAPICS XA.
The function keys (F1-F28) on the DCT can be used to generate transactions.
This section describes what each function key does when using ERPBridge for
MAPICS.
MAPICS XA has the following function key templates. Each of these templates
has a corresponding DCConnect function group which is clearly identified by the
function group name.
Function Group naming convention.
All predefined Host Connection function groups are named as follows:
XAtts
Where:
XA
| is constant
|
tt
| Terminal type
271 for 7527 model 001
272 for 7527 model 002
24 for 7524 (any model)
262 for 7526 model 200
|
s
| Suffix relating to the template
|
For details of a template, select it from following list.
This section shows the default function key assignment in the
Discrete Manufacturing template. These function group files are identified with an
"a" suffix in the name.
For details on a transaction program - it's prompts, field lengths and attributes - select it
from following list.
- F1: Move (MV)
(SeeTemplate A, F1)
- F2: Miscellaneous Charge (MC)
(SeeTemplate A, F2)
- F3: Order Complete (OC)
(SeeTemplate A, F3)
- F4: Planned Issue (IP)
(SeeTemplate A, F4)
- F5: Unplanned Issue (IU)
(SeeTemplate A, F5)
- F6: Pick Complete by Order (PC)
(SeeTemplate A, F6)
- F7: Manufacturing Order Receipt (RM)
(SeeTemplate A, F7)
- F8: Return to Stock (RS)
(SeeTemplate A, F8)
- F9: Scrap from Stock (SS)
(SeeTemplate A, F9)
- F10: Manufacturing Component Scrap (SC)
(SeeTemplate A, F10)
- F11: Manufacturing Order Scrap (SM)
(SeeTemplate A, F11)
- F23: Crew Clock (CC)
(SeeTemplate A, F23)
- F24: Job On (ON)
(SeeTemplate A, F24)
- F25: Job Off (OF)
(SeeTemplate A, F25)
- F26: Error Transaction (ER)
(SeeTemplate A, F26)
- F27: User Defined (ZZ)
(SeeTemplate A, F27)
- F28: Time and Attendance (TA)
(SeeTemplate A, F28)
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F1 (A)
| MV: Move
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code... [0, 1, 2]
| 1
| 1
| N
|
|
| 5
| 'From' Turnaround 3...
| 9
| 9
| N
|
|
| 6
| Next Work Area...
| 5
| 5
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F2 (B)
| MC: Misc Charge
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 4...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Cost...
| 15
| 15
| S,2
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F3 (C)
| OC: Order Complete
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F4 (D)
| IP: Planned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F5 (E)
| IU: Unplanned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Item Number...
| 15
| 15
| A/N
|
|
| 4
| User Sequence...
| 4
| 4
| N
|
|
| 5
| Warehouse...
| 3
| 3
| A/N
|
|
| 6
| Quantity...
| 12
| 12
| S,3
|
|
| 7
| Location...
| 7
| 7
| N
|
|
| 8
| Batch Lot...
| 10
| 10
| A/N
|
|
| 9
| FIFO...
| 6
| 6
| N
|
|
| 10
| Reference...
| 10
| 10
| A/N
|
|
| 11
| Reason...
| 6
| 6
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F6 (F)
| PC: Pick Complete
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F7 (G)
| RM: Mfg Order Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F8 (H)
| RS: Return to Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Amount.
| 17
| 17
| S,4
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F9 (I)
| SS: Scrap From Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F10 (J)
| SC: Mfg Comp Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F11 (K)
| SM: Mfg Order Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F23 (W)
| CC: Crew Clock
| 1
| Enter Badge...
| 7
| 7
| N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F24 (X)
| ON: Job On
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Work Center...
| 5
| 5
| A/N
|
|
| 4
| Job Type... [ S, R, I]
| 1
| 1
| A
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F25 (Y)
| OF: Job Off
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [0, 1, 2, 3]
| 1
| 1
| N
|
|
| 5
| Scrap Quantity...
| 12
| 12
| S,3
|
|
| 6
| Job Type [S, R, I, M]
| 1
| 1
| A
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F26 (Z)
| ER: Error Trans
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Transaction Type...
| 2
| 2
| A
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F27
| ZZ: User Defined
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround...
| 9
| 9
| N
|
|
| 3
| User 1...
| 15
| 15
| A/N
|
|
| 4
| User 2...
| 15
| 15
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Sub Type...
| 1
| 1
| A/N
|
The following attributes apply to the table displayed.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Att
|
F28
| TA: Time & Attendance
| 1
| Enter Badge...
| 7
| 7
| N
|
This section shows the default function key assignment in the
Stock Room template. These function group files are identified with a
"b" suffix in the name.
For details on a transaction program - it's prompts, field length and attributes - select it
from the following list.
- F1: Planned Issue (IP)
(SeeTemplate B, F1)
- F2: Unplanned Issue (IU)
(SeeTemplate B, F2)
- F3: Pick Complete by Order (PC)
(SeeTemplate B, F3)
- F4: Miscellaneous Issue (IS)
(SeeTemplate B, F4)
- F5: Manufacturing Order Receipt (RM)
(SeeTemplate B, F5)
- F6: Miscellaneous Receipt (RC)
(SeeTemplate B, F6)
- F7: Inter-warehouse Transfer (TW)
(SeeTemplate B, F7)
- F8: Inter-warehouse Issue (IW)
(SeeTemplate B, F8)
- F9: Inter-warehouse Receipt (RW)
(SeeTemplate B, F9)
- F10: Return to Stock (RS)
(SeeTemplate B, F10)
- F11: Scrap from Stock (SS)
(SeeTemplate B, F11)
- F12: Manufacturing Component Scrap (SC)
(SeeTemplate B, F12)
- F13: Manufacturing Order Scrap (SM)
(SeeTemplate B, F13)
- F14: Sales Shipment (SA)
(SeeTemplate B, F14)
- F15: Vendor Return (VR)
(SeeTemplate B, F15)
- F16: Add Physical Inventory (PA)
(SeeTemplate B, F16)
- F17: Physical Inventory (PH)
(SeeTemplate B, F17)
- F26: Error Transaction (ER)
(SeeTemplate B, F26)
- F27: User Defined (ZZ)
(SeeTemplate B, F27)
- F28: Time and Attendance (TA)
(SeeTemplate B, F28)
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F1 (A)
| IP: Planned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F2 (B)
| IU: Unplanned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Item Number...
| 15
| 15
| A/N
|
|
| 4
| User Sequence...
| 4
| 4
| N
|
|
| 5
| Warehouse...
| 3
| 3
| A/N
|
|
| 6
| Quantity...
| 12
| 12
| S,3
|
|
| 7
| Location...
| 7
| 7
| A/N
|
|
| 8
| Batch Lot...
| 10
| 10
| A/N
|
|
| 9
| FIFO...
| 6
| 6
| N
|
|
| 10
| Reference...
| 10
| 10
| A/N
|
|
| 11
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F3 (C)
| PC: Pick Complete
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F4 (D)
| IS: Misc Issue
| 1
| Enter Badge...
| 7
| 7 c.N
|
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F5 (E)
| RM: Mfg Order Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F6 (F)
| RC: Misc Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 6
| Location...
| 7
| 7
| A/N
|
|
| 7
| Batch Lot...
| 10
| 10
| A/N
|
|
| 8
| FIFO...
| 6
| 6
| N
|
|
| 9
| Reference...
| 10
| 10
| A/N
|
|
| 10
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F7 (G)
| TW: Inter Whse Xfer
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| 'From' Warehouse...
| 3
| 3
| A/N
|
|
| 4
| 'From' Location...
| 7
| 7
| A/N
|
|
| 5
| Batch Lot...
| 10
| 10
| A/N
|
|
| 6
| FIFO...
| 6
| 6
| N
|
|
| 7
| 'To' Warehouse...
| 3
| 3
| A/N
|
|
| 8
| 'To' Location...
| 7
| 7
| A/N
|
|
| 9
| Quantity...
| 12
| 12
| S,3
|
|
| 10
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 11
| Reference...
| 10
| 10
| A/N
|
|
| 12
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F8 (H)
| IW: Inter Whse Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F9 (I)
| RW: Inter Whse Recpt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F10 (J)
| RS: Return to Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Transaction Amount...
| 15
| 15
| S,4
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F11 (K)
| SS: Scrap From Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F12 (L)
| SC: Mfg Comp Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F13 (M)
| SM: Mfg Order Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F14 (N)
| SA: Sales Shipment
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Order Number...
| 7
| 7
| N
|
|
| 3
| Item Number...
| 15
| 15
| A/N
|
|
| 4
| Warehouse...
| 3
| 3
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Location...
| 7
| 7
| A/N
|
|
| 8
| Batch Lot...
| 10
| 10
| A/N
|
|
| 9
| FIFO...
| 6
| 6
| N
|
|
| 10
| Reference...
| 10
| 10
| A/N
|
|
| 11
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F15 (O)
| VR: Vendor Return
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| UOM...
| 2
| 2
| A/N
|
|
| 5
| Resupply... [Y,N]
| 1
| 1
| A
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Location...
| 7
| 7
| A/N
|
|
| 8
| Batch Lot...
| 10
| 10
| A/N
|
|
| 9
| FIFO...
| 6
| 6
| N
|
|
| 10
| GRN...
| 10
| 26
| A/N
|
|
| 11
| GRN Invoice
| N/A
| 1
| A/N
|
|
| 12
| Reference...
| 10
| 10
| A/N
|
|
| 13
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F16 (P)
| PA: Add Phys Inv
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Warehouse...
| 3
| 3
| A/N
|
|
| 3
| Item Number...
| 15
| 15
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F17 (Q)
| PH: Phys Inv
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 11...
| 12
| 12
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F26 (Z)
| ER: Error Trans
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Transaction Type...
| 2
| 2
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F27
| ZZ: User Defined
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Any Turnaround...
| 9
| 9
| N
|
|
| 3
| User 1...
| 15
| 15
| A/N
|
|
| 4
| User 2...
| 15
| 15
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Sub Type...
| 1
| 1
| A/N
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F28
| TA: Time & Attendance
| 1
| Enter Badge...
| 7
| 7
| N
|
This section shows the default function key assignment in the
Receiving template. These function group files are identified with a
"c" suffix in the name.
Note: References in the template description to controlled and uncontrolled operations
refer to whether or
not the terminal operator must specify the Location, Batch Lot, first-in
first-out (FIFO), and Goods Receive Note (GRN) fields for the transaction. In
controlled operations these fields must be filled in by the terminal operator.
In uncontrolled operations, these fields are all filled in with blanks by the
ERPBridge for MAPICS for OS/2 and Windows NT TC script. The VR, RI and RP transactions have both
controlled and uncontrolled versions in this template.
For details on a transaction program - it's prompts, field length and attributes - select it
from the following list.
- F1: Vendor Return (VR)
(SeeTemplate C, F1)
- F2: Receipt to Dock (RD)
(SeeTemplate C, F2)
- F3: Controlled Receipt to Inspection (RI)
(SeeTemplate C, F3)
- F4: Controlled Receipt to Stock (RD)
(SeeTemplate C, F4)
- F5: Purchase Order Scrap (SP)
(SeeTemplate C, F5)
- F6: Uncontrolled Receipt to Inspection (RI)
(SeeTemplate C, F6)
- F7: Uncontrolled Receipt to Stock (RP)
(SeeTemplate C, F7)
- F8: Uncontrolled Vendor Return (VR)
(SeeTemplate C, F8)
- F26: Error Transaction (ER)
(SeeTemplate C, F26)
- F27: User Defined (ZZ)
(SeeTemplate C, F27)
- F28: Time and Attendance (TA)
(SeeTemplate C, F28)
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F1 (A)
| VR: Vendor Return
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Resupply... [Y,N]
| 1
| 1
| A
|
|
| 6
| Transaction Amount...
| 17
| 17
| A/N
|
|
| 7
| Location...
| 7
| 7
| A/N
|
|
| 8
| Batch Lot...
| 10
| 10
| A/N
|
|
| 9
| FIFO...
| 6
| 6
| N
|
|
| 10
| GRN...
| 10
| 26
| A/N
|
|
| 11
| GRN Invoice...
| N/A
| 1
| A/N
|
|
| 12
| Reference...
| 10
| 10
| A/N
|
|
| 13
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F2 (B)
| RD: Receipt to Dock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
|
| 7
| GRN...
| N/A
| 26
| A/N
|
|
| 8
| GRN Invoice...
| N/A
| 1
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F3 (C)
| RI: Controlled R-I
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| GRN...
| N/A
| 26
| A/N
|
|
| 9
| GRN Invoice...
| N/A
| 1
| A/N
|
|
| 10
| Country of Origin
| N/A
| 3
| A/N
|
|
| 11
| Reference...
| 10
| 10
| A/N
|
|
| 13
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F4 (D)
| RP: Controlled R-S
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Location...
| 7
| 7
| A/N
|
|
| 8
| Batch Lot...
| 10
| 10
| A/N
|
|
| 9
| FIFO...
| 6
| 6
| N
|
|
| 10
| GRN...
| 10
| 26
| A/N
|
|
| 11
| GRN Invoice...
| N/A
| 1
| A/N
|
|
| 12
| Country of Origin
| N/A
| 3
| A/N
|
|
| 13
| Reference...
| 10
| 10
| A/N
|
|
| 14
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F5 (E)
| SP: P.O. Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F6 (F)
| RI: Uncontrolled R-I
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F7 (G)
| RP: Uncontrolled R-S
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Reference...
| 10
| 10
| A/N
|
|
| 8
| Reason...
| 6
| 6
| A/N
|
|
| 9
| GRN...
| N/A
| 26
| A/N
|
|
| 10
| GRN Invoice...
| N/A
| 1
| A/N
|
|
| 11
| Country of Origin
| N/A
| 3
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F8 (H)
| VR: Uncontrolled
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Resupply... [Y,N]
| 1
| 1
| A
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Location...
| 7
| 7
| A/N
|
|
| 8
| GRN...
| N/A
| 26
| A/N
|
|
| 9
| GRN Invoice...
| N/A
| 1
| A/N
|
|
| 10
| Reference...
| 10
| 10
| A/N
|
|
| 11
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F26 (Z)
| ER: Error Trans
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Transaction Type...
| 2
| 2
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F27
| ZZ: User Defined
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Any Turnaround...
| 9
| 9
| N
|
|
| 3
| User 1...
| 15
| 15
| A/N
|
|
| 4
| User 2...
| 15
| 15
| N/A
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Sub Type...
| 1
| 1
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F28
| TA: Time & Attendance
| 1
| Enter Badge...
| 7
| 7
| N
|
This section shows the default function key assignment in the
Fast Track Time and Attendance template. These function group files are identified with a
"d" suffix in the name.
Note: The TC script accepts a 'Badge-initiated transaction while fast-clocking is
active' for this template. That transaction, whose transaction ID is 030, is
converted to a TA transaction that looks similar to a transaction generated by
pressing F28.
For details on a transaction program - it's prompts, field length and attributes - select it
from the following list.
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F26 (Z)
| ER: Error Trans
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Transaction Type...
| 2
| 2
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F27
| ZZ: User Defined
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Any Turnaround...
| 9
| 9
| N
|
|
| 3
| User 1...
| 15
| 15
| A/N
|
|
| 4
| User 2...
| 15
| 15
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Sub Type...
| 1
| 1
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F28
| TA: Time & Attendance
| 1
| Enter Badge...
| 7
| 7
| N/A
|
This section shows the default function key assignment in the
Quality Control template. These function group files are identified with a
"e" suffix in the name.
For details on a transaction program - it's prompts, field length and attributes - select it
from the following list.
- F1: Approve Purchase Order (PQ)
(SeeTemplate E, F1)
- F2: Approve Manufacturing Order (MQ)
(SeeTemplate E, F2)
- F3: Approve Cycle Item (CQ)
(SeeTemplate E, F3)
- F4: Approve/Reject Entire Location (QC)
(SeeTemplate E, F4)
- F5: Purchase Order Receipt to Inspection (RI)
(SeeTemplate E, F5)
- F6: Manufacturing Order Receipt (RM)
(SeeTemplate E, F6)
- F23: Crew Clock (CC)
(SeeTemplate E, F23)
- F24: Job On (ON)
(SeeTemplate E, F24)
- F25: Job Off (OF)
(SeeTemplate E, F25)
- F26: Error Transaction (ER)
(SeeTemplate E, F26)
- F27: User Defined (ZZ)
(SeeTemplate E, F27)
- F28: Time and Attendance (TA)
(SeeTemplate E, F28)
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F1 (A)
| PQ: Approve P.O.
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 11,12...
| 12
| 12
| N
|
|
| 3
| Approved Quantity...
| 12
| 12
| S,3
|
|
| 4
| Approved Warehouse...
| 3
| 3
| A/N
|
|
| 5
| Approved Location...
| 7
| 7
| A/N
|
|
| 6
| Approved Amount...
| 17
| 17
| S,4
|
|
| 7
| Rejected Quantity...
| 12
| 12
| S,3
|
|
| 8
| Vendor Returned Quantity...
| 12
| 12
| S,3
|
|
| 9
| Resupply... [Y, N]
| 1
| 1
| A
|
|
| 10
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 11
| Reference...
| 10
| 10
| A/N
|
|
| 12
| Reason...
| 6
| 6
| A/N
|
|
| 13
| GRN...
| 10
| 26
| A/N
|
|
| 15
| GRN Invoice...
| N/A
| 1
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F2 (B)
| MQ: Approve M.O.
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 11,12...
| 12
| 12
| N
|
|
| 3
| Approved Quantity...
| 12
| 12
| S,3
|
|
| 4
| Approved Warehouse...
| 3
| 3
| A/N
|
|
| 5
| Approved Location...
| 7
| 7
| A/N
|
|
| 6
| Approved Amount...
| 17
| 17
| S,4
|
|
| 7
| Rejected Quantity...
| 12
| 12
| S,3
|
|
| 8
| Rejected Warehouse...
| 3
| 3
| A/N
|
|
| 9
| Rejected Location...
| 7
| 7
| A/N
|
|
| 10
| Scrapped Quantity...
| 12
| 12
| S,3
|
|
| 11
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 12
| Reference...
| 10
| 10
| A/N
|
|
| 13
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F3 (C)
| CQ: Approve Cyc. Itm
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 11,12...
| 12
| 12
| S,3
|
|
| 3
| Approved Quantity...
| 12
| 12
| S,3
|
|
| 4
| Approved Warehouse...
| 3
| 3
| A/N
|
|
| 5
| Approved Location...
| 7
| 7
| A/N
|
|
| 6
| Approved Amount...
| 17
| 17
| S,4
|
|
| 7
| Rejected Quantity...
| 12
| 12
| S,3
|
|
| 8
| Rejected Warehouse...
| 3
| 3
| A/N
|
|
| 9
| Rejected Location...
| 7
| 7
| A/N
|
|
| 10
| Scrapped Quantity...
| 12
| 12
| S,3
|
|
| 11
| Reference...
| 10
| 10
| A/N
|
|
| 12
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F4 (D)
| QC: Approve/Rej E L C
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 11,12...
| 12
| 12
| N
|
|
| 3
| Approval Code... [1,2]
| 1
| 1
| N
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F5 (E)
| RI: PO Recpt to Insp
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| GRN...
| 10
| 26
| A/N
|
|
| 9
| GRN Invoice...
| N/A
| 1
| A/N
|
|
| 10
| Country of Origin
| N/A
| 3
| A/N
|
|
| 11
| Reference...
| 10
| 10
| A/N
|
|
| 12
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F6 (F)
| RM: Mfg Order Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [' ', P, C, R]
| 7
| 7
| A/N
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F23 (W)
| CC: Crew Clock
| 1
| Enter Badge...
| 7
| 7
| N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F24 (X)
| ON: Job On
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Work Center...
| 5
| 5
| A/N
|
|
| 4
| Job Type... [S, R, I]
| 1
| 1
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F25 (Y)
| OF: Job Off
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [0, 1, 2, 3]
| 1
| 1
| N
|
|
| 5
| Scrapped Quantity...
| 12
| 12
| S,3
|
|
| 6
| Job Type [S, R, I, M]...
| 1
| 1
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F26 (Z)
| ER: Error Trans
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Transaction Type...
| 2
| 2
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F27
| ZZ: User Defined
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Any Turnaround...
| 9
| 9
| N
|
|
| 3
| User 1...
| 15
| 15
| A/N
|
|
| 4
| User 2...
| 15
| 15
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Sub Type...
| 1
| 1
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| R22
| R23
| Att
|
F28
| TA: Time & Attendance
| 1
| Enter Badge...
| 7
| 7
| N
|
This section shows the default function key assignment in the
Repetitive Manufacturing template. These function group files are identified with an
"f" suffix in the name.
For details on a transaction program - it's prompts, field length and attributes - select it
from the following list.
- F1: Receipt to Stock (RP)
(SeeTemplate F, F1)
- F2: Component Transfer to Line (CL)
(SeeTemplate F, F2)
- F3: Replenishment (RL)
(SeeTemplate F, F3)
- F4: Planned Issue (IP)
(SeeTemplate F, F4)
- F5: Scrap from Stock (SS)
(SeeTemplate F, F5)
- F6: Component Scrap (SC)
(SeeTemplate F, F6)
- F7: Schedule Scrap (SM)
(SeeTemplate F, F7)
- F8: Operation Report (RO)
(SeeTemplate F, F8)
- F9: Schedule Receipt (RM)
(SeeTemplate F, F9)
- F10: Component Transfer to Stores (CN)
(SeeTemplate F, F10)
- F11: Production Status (PS)
(SeeTemplate F, F11)
- F23: Crew Clock (CC)
(SeeTemplate F, F23)
- F24: Job On (ON)
(SeeTemplate F, F24)
- F25: Job Off (OF)
(SeeTemplate F, F25)
- F26: Error Transaction (ER)
(SeeTemplate F, F26)
- F27: User Defined (ZZ)
(SeeTemplate F, F27)
- F28: Time and Attendance (TA)
(SeeTemplate F, F28)
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F1 (A)
| RP: Receipt to Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Unit of Measure...
| 2
| 2
| A/N
|
|
| 5
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Location...
| 7
| 7
| N
|
|
| 8
| Batch Lot...
| 10
| 10
| A/N
|
|
| 9
| FIFO...
| 6
| 6
| N
|
|
| 10
| GRN...
| 10
| 26
| A/N
|
|
| 11
| GRN Invoice...
| N/A
| 1
| A/N
|
|
| 12
| Country of Origin
| N/A
| 3
| A/N
|
|
| 13
| Reference...
| 10
| 10
| A/N
|
|
| 14
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F2 (B)
| CL: Compon xfr line
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 8...
| 9
| 9
| N
|
|
| 3
| Container Quantity...
| 4
| 4
| S,0
|
|
| 4
| Piece Quantity...
| 12
| 12
| S,3
|
|
| 5
| Cancel Repln [' ', 1]
| 1
| 1
| N
|
|
| 6
| Reference...
| 10
| 10
| A/N
|
|
| 7
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F3 (C)
| RL: Replenishment
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 8...
| 9
| 9
| N
|
|
| 3
| Container Quantity...
| 4
| 4
| S,0
|
|
| 4
| Piece Quantity...
| 12
| 12
| S,3
|
|
| 5
| Priority Code [Y, N]
| 1
| 1
| A
|
|
| 6
| Reference...
| 10
| 10
| A/N
|
|
| 7
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F4 (D)
| IP: Planned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 8...
| 9
| 9
| N
|
|
| 3
| Container Quantity...
| 4
| 4
| S,0
|
|
| 4
| Piece Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F5 (E)
| SS: Scrap from Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F6 (F)
| SC: Component Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 8...
| 9
| 9
| N
|
|
| 3
| Container Quantity...
| 4
| 4
| S,0
|
|
| 4
| Piece Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F7 (G)
| SM: Schedule Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Container Quantity...
| 4
| 4
| S,0
|
|
| 4
| Piece Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F8 (H)
| RO: Operation Report
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Container Quantity...
| 4
| 4
| S,0
|
|
| 4
| Piece Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F9 (I)
| RM: Schedule Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Container Quantity...
| 4
| 4
| S,0
|
|
| 4
| Piece Quantity...
| 12
| 12
| S,3
|
|
| 5
| Location...
| 7
| 7
| A/N
|
|
| 6
| Batch Lot...
| 10
| 10
| A/N
|
|
| 7
| FIFO...
| 6
| 6
| N
|
|
| 8
| Last Transaction [Y, N]
| 1
| 1
| A
|
|
| 9
| Reference...
| 10
| 10
| A/N
|
|
| 10
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F10 (J)
| CN: Component xfr Sto
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 8...
| 9
| 9
| N
|
|
| 3
| Container Quantity...
| 4
| 4
| S,0
|
|
| 4
| Piece Quantity...
| 12
| 12
| S,3
|
|
| 5
| Supply Location
| 7
| 7
| A/N
|
|
| 6
| Reference...
| 10
| 10
| A/N
|
|
| 7
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F11 (K)
| PS: Production Stats
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Warehouse...
| 3
| 3
| A/N
|
|
| 3
| Prod Line...
| 5
| 5
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Line Status... [1, 2]
| 1
| 1
| N
|
|
| 6
| Time Code...
| 4
| 4
| A/N
|
|
| 7
| Reference...
| 10
| 10
| A/N
|
|
| 8
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F23 (W)
| CC: Crew Clock
| 1
| Enter Badge...
| 7
| 7
| N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F24 (X)
| ON: Job On
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Work Center...
| 5
| 5
| A/N
|
|
| 4
| Job Type... [ S, R, I]
| 1
| 1
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F25 (Y)
| OF: Job Off
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [0, 1, 2, 3]
| 1
| 1
| N
|
|
| 5
| Scrap Quantity...
| 12
| 12
| S,3
|
|
| 6
| Job Type [S, R, I, M]
| 1
| 1
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F26 (Z)
| ER: Error Trans
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Transaction Type...
| 2
| 2
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F27
| ZZ: User Defined
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Any Turnaround...
| 9
| 9
| N
|
|
| 3
| User 1...
| 15
| 15
| A/N
|
|
| 4
| User 2...
| 15
| 15
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Sub Type...
| 1
| 1
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F28
| TA: Time & Attendance
| 1
| Enter Badge...
| 7
| 7
| N
|
This section shows the default function key assignment in the Discrete Manufacturing,
Uncontrolled Warehouse template. These function group files are identified with a
"g" suffix in the name.
Note: Template G has a transaction set similar to Template A. The difference is in
which fields are prompted in each transaction. In template A (controlled),
certain transaction programs (IP, IU, RM, RS, and SS) prompt the terminal
operator for Location, Batch Lot, and FIFO information. The corresponding
transaction programs in template G (uncontrolled) do not prompt the terminal
operator for this information; instead the ERPBridge for MAPICS for OS/2 and Windows NT TC script
fills in blanks for these fields.
For details on a transaction program - it's prompts, field length and attributes - select it
from the following list.
- F1: Move (MV)
(SeeTemplate G, F1)
- F2: Miscellaneous Charge (MC)
(SeeTemplate G, F2)
- F3: Order Complete (OC)
(SeeTemplate G, F3)
- F4: Planned Issue (IP)
(SeeTemplate G, F4)
- F5: Unplanned Issue (IU)
(SeeTemplate G, F5)
- F6: Pick Complete by Order (PC)
(SeeTemplate G, F6)
- F7: Manufacturing Order Receipt (RM)
(SeeTemplate G, F7)
- F8: Return to Stock (RS)
(SeeTemplate G, F8)
- F9: Scrap from Stock (SS)
(SeeTemplate G, F9)
- F10: Manufacturing Component Scrap (SC)
(SeeTemplate G, F10)
- F11: Manufacturing Order Scrap (SM)
(SeeTemplate G, F11)
- F23: Crew Clock (CC)
(SeeTemplate G, F23)
- F24: Job On (ON)
(SeeTemplate G, F24)
- F25: Job Off (OF)
(SeeTemplate G, F25)
- F26: Error Transaction (ER)
(SeeTemplate G, F26)
- F27: User Defined (ZZ)
(SeeTemplate G, F27)
- F28: Time and Attendance (TA)
(SeeTemplate G, F28)
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F1 (A)
| MV: Move
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1,3
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code... [0, 1, 2]
| 1
| 1
| N
|
|
| 5
| 'From' Turnaround 1,3...
| 9
| 9
| N
|
|
| 6
| Next Work Area...
| 5
| 5
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F2 (B)
| MC: Misc Charge
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 4...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Cost...
| 15
| 15
| S,2
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F3 (C)
| OC: Order Complete
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F4 (D)
| IP: Planned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F5 (E)
| IU: Unplanned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Item Number...
| 15
| 15
| A/N
|
|
| 4
| User Sequence...
| 4
| 4
| N
|
|
| 5
| Warehouse...
| 3
| 3
| A/N
|
|
| 6
| Quantity...
| 12
| 12
| S,3
|
|
| 7
| Reference...
| 10
| 10
| A/N
|
|
| 8
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F6 (F)
| PC: Pick Complete
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F7 (G)
| RM: Mfg Order Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F8 (H)
| RS: Return to Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Transaction Amount...
| 15
| 15
| S,4
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F9 (I)
| SS: Scrap From Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F10 (J)
| SC: Mfg Comp Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S, 3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F11 (K)
| SM: Mfg Order Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F23 (W)
| CC: Crew Clock
| 1
| Enter Badge...
| 7
| 7
| N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F24 (X)
| ON: Job On
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Work Center...
| 5
| 5
| A/N
|
|
| 4
| Job Type... [S, R, I]
| 1
| 1
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F25 (Y)
| OF: Job Off
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 3...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [0, 1, 2, 3]
| 1
| 1
| N
|
|
| 5
| Scrap Quantity...
| 12
| 12
| S,3
|
|
| 6
| Job Type [S, R, I, M]
| 1
| 1
| A
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F26 (Z)
| ER: Error Trans
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Transaction Type...
| 2
| 2
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F27
| ZZ: User Defined
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Any Turnaround...
| 9
| 9
| N
|
|
| 3
| User 1...
| 15
| 15
| A/N
|
|
| 4
| User 2...
| 15
| 15
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Sub Type...
| 1
| 1
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F28
| TA: Time & Attendance
| 1
| Enter Badge...
| 7
| 7
| N
|
This section shows the default function key assignment in the Stock Room,
Uncontrolled Warehouse template. These function group files are identified with an
"h" suffix in the name.
Note: Template H has a transaction set similar to Template B. The difference is in
which fields are prompted in each transaction. In template B (controlled),
certain transaction programs (IP, IU, IS, RM, RC, TW, IW, RW, RS, SS, SA and VR)
have more prompts that the terminal operator must respond to (including Location,
Batch Lot, FIFO, and GRN). The corresponding transaction programs in template H
(uncontrolled) do not prompt for this information; instead the ERPBridge for
MAPICS TC script fills in blanks for those fields.
Another difference between templates B and H has to do with the PH and PA
transactions. Template B has PA on key F16 and PH on key F17 while template H
has PH on key F16 and does not include PA.
For details on a transaction program - it's prompts, field length and attributes - select it
from the following list.
- F1: Planned Issue (IP)
(SeeTemplate H, F1)
- F2: Unplanned Issue (IU)
(SeeTemplate H, F2)
- F3: Pick Complete by Order (PC)
(SeeTemplate H, F3)
- F4: Miscellaneous Issue (IS)
(SeeTemplate H, F4)
- F5: Manufacturing Order Receipt (RM)
(SeeTemplate H, F5)
- F6: Miscellaneous Receipt (RC)
(SeeTemplate H, F6)
- F7: Inter-warehouse Transfer (TW)
(SeeTemplate H, F7)
- F8: Inter-warehouse Issue (IW)
(SeeTemplate H, F8)
- F9: Inter-warehouse Receipt (RW)
(SeeTemplate H, F9)
- F10: Return to Stock (RS)
(SeeTemplate H, F10)
- F11: Scrap from Stock (SS)
(SeeTemplate H, F11)
- F12: Manufacturing Component Scrap (SC)
(SeeTemplate H, F12)
- F13: Manufacturing Order Scrap (SM)
(SeeTemplate H, F13)
- F14: Sales Shipment (SA)
(SeeTemplate H, F14)
- F15: Vendor Return (VR)
(SeeTemplate H, F15)
- F16: Physical Inventory (PH)
(SeeTemplate H, F16)
- F26: Error Transaction (ER)
(SeeTemplate H, F26)
- F27: User Defined (ZZ)
(SeeTemplate H, F27)
- F28: Time and Attendance (TA)
(SeeTemplate H, F28)
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F1 (A)
| IP: Planned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F2 (B)
| IU: Unplanned Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Item Number...
| 15
| 15
| A/N
|
|
| 4
| User Sequence...
| 4
| 4
| N
|
|
| 5
| Warehouse...
| 3
| 3
| A/N
|
|
| 6
| Quantity...
| 12
| 12
| S,3
|
|
| 7
| Reference...
| 10
| 10
| A/N
|
|
| 8
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F3 (C)
| PC: Pick Complete
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F4 (D)
| IS: Misc Issue
| 1
| Enter Badge... c.7
| 7
| N
|
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F5 (E)
| RM: Mfg Order Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Completion Code [' ', P, C, R]
| 1
| 1
| A
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F6 (F)
| RC: Misc Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 6
| Reference...
| 10
| 10
| A/N
|
|
| 7
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F7 (G)
| TW: Inter Whse Xfer
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| 'From' Warehouse...
| 3
| 3
| A/N
|
|
| 4
| 'To' Warehouse...
| 3
| 3
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Reference...
| 10
| 10
| A/N
|
|
| 8
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F8 (H)
| IW: Inter Whse Issue
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F9 (I)
| RW: Intr Whse Receipt
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F10 (J)
| RS: Return to Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F11 (K)
| SS: Scrap From Stock
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Item Number...
| 15
| 15
| A/N
|
|
| 3
| Warehouse...
| 3
| 3
| A/N
|
|
| 4
| Quantity...
| 12
| 12
| S,3
|
|
| 5
| Reference...
| 10
| 10
| A/N
|
|
| 6
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F12 (L)
| SC: Mfg Comp Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 2...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F13 (M)
| SM: Mfg Order Scrap
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 1...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| Reference...
| 10
| 10
| A/N
|
|
| 5
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F14 (N)
| SA: Sales Shipment
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Order Number...
| 7
| 7
| N
|
|
| 3
| Item Number...
| 15
| 15
| A/N
|
|
| 4
| Warehouse...
| 3
| 3
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Reference...
| 10
| 10
| A/N
|
|
| 8
| Reason...
| 6
| 6
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F15 (O)
| VR: Vendor Return
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Turnaround 6,7...
| 9
| 9
| N
|
|
| 3
| Quantity...
| 12
| 12
| S,3
|
|
| 4
| UOM...
| 2
| 2
| A/N
|
|
| 5
| Resupply... [Y,N]
| 1
| 1
| A
|
|
| 6
| Transaction Amount...
| 17
| 17
| S,4
|
|
| 7
| Location...
| 7
| 7
| A/N
|
|
| 8
| Reference...
| 10
| 10
| A/N
|
|
| 9
| Reason...
| 6
| 6
| N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F16 (P)
| PH: Phys Inventory
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Warehouse...
| 3
| 3
| A/N
|
|
| 3
| Item Number...
| 15
| 15
| A/N
|
|
| 4
| Quantity...
| 11
| 11
| U,3
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F26 (Z)
| ER: Error Trans
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Transaction Type...
| 2
| 2
| A
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F27
| ZZ: User Defined
| 1
| Enter Badge...
| 7
| 7
| N
|
|
| 2
| Any Turnaround...
| 9
| 9
| N
|
|
| 3
| User 1...
| 15
| 15
| A/N
|
|
| 4
| User 2...
| 15
| 15
| A/N
|
|
| 5
| Quantity...
| 12
| 12
| S,3
|
|
| 6
| Sub Type...
| 1
| 1
| A/N
|
Attributes
| Definition
|
N
| = Numerics
|
A/N
| = Alpha-Numerics
|
S,x
| = Signed (x = number of decimal positions)
|
*R22
| = Release 2.2 Field length
|
*R23
| = Release 2.3 Field Length
|
Function Key
| Transaction Type
| Step
| Prompts
| *R22
| *R23
| Attr
|
F28
| TA: Time & Attendance
| 1
| Enter Badge...
| 7
| 7
| N
|
MAPICS XA transactions appear to be successfully entered at the
terminal, but are not getting to the AS/400. None of the error logs
indicate any problems.
|
The most common cause of this is having the terminals assigned to
the wrong DCConnect Mailbox. Open the Mailbox Configuration folder in
DCConnect and check the transaction count for the configured mailboxes
by selecting VIEW - DETAILS VIEW. If the transactions are being routed
to the correct mailbox, check the MAPICS Settings Notebook page and
ensure the Mailbox name listed is exactly like the one in DCConnect
Mailbox Configuration. Remember that this field is case sensitive.
|
Every few transactions, the TC session goes into a "Completed"
state and stops. TC Session displays "no commands defined for transaction"
|
This can be caused by renaming any of the MAPICS function
groups in DCConnect. TC formats and routes the transactions based
on the Function Group to which the terminal is assigned, and the
function key that was pressed. If the DCConnect function group
names have been changed, the HCMxx.SCR file must be changed to
match the new names.
For instance, in the HCMxx.SCR file, the
command
StartFunctionGroup ( XA262A )
starts the Discrete Manufacturing function group commands for the
7526 Model 200
terminal. If, in DCConnect, the function group sending these transactions
is called "DM7526" or something else, TC will not have a set of commands
designed to process those transactions and after 3 transactions are released,
TC shuts down to prevent data loss.
Key assignments, such as the
StartKey ( F1 )
within the scripts are not affected by reassignment of keys since every
MAPICS transaction program starts with an AKA (Also Known As) command which sends
the correct Key ID, regardless of the key to which the transaction
program is bound.
|
When starting the ERPBridge for MAPICS for OS/2 and Windows NT application the TC or
AHISS window goes immediately from a "Compiling" status to a "Completed"
status.
|
The TC or AHISS application most likely had a problem connecting to the
correct emulation session. Ensure the emulator is up and running, and
that the Short Session ID assigned in the ERPBridge for MAPICS for OS/2 and Windows NT Settings
Notebook is not in use by some other process. This can be avoided by
selecting the "/S=a" where "a" is the session ID, on the command line
where you start PCOMM.
|
After starting, the TC script loops continuously, starting and
ending the emulator and flashing AS/400 screens.
|
This can be caused by a number of conditions. Check the following:
- Sign on to the host manually, using the ERPBridge for MAPICS for OS/2 and Windows NT
userid and password to ensure the PM&C procedure for collecting
transactions is available. The application should not display any
errors, warnings, or be in Dedicated Application Mode.
- Is the Message Waiting indicator on for this user ERPBridge for MAPICS
may be trying, unsuccessfully, to clear waiting system or user
messages. The action taken by ERPBridge for MAPICS to clear messages depends
on the particular message being displayed. Check this section of
the TC Script (HCMxx.SCR) to ensure the keys being sent are consistent
with those a user would press in order to clear messages. Change
the script if necessary.
- ERPBridge for MAPICS may not be recognizing the AS/400 sign on screen.
Are the characters "Sign On" displayed on the screen at row 1,
column 36? If not, the Logon subroutine in HCMxx.SCR needs to be
customized.
|
The Logon subroutine in the TC script loops and the AS/400
appears stuck on the Sign On screen.
|
This will occur if the row/column position of the User ID, Password,
Procedure and Library fields are not in the default locations
or if the userid/password are unrecognized. The
HCMxx.SCR file places these fields at 6x53, 7x53, 8x53 and 10x53
respectively. If these input fields have been moved in a custom
sign on screen, change the row/column positions indicated in the
logon subroutine of the HCMxx.SCR file.
|
Footnotes:
(1)
MAPICS = IBM Manufacturing Accounting and Production Information Control System,
marketed by MARCAM, Inc.