TWS Iserv 5.5 For Infor BPCS - ERP LX User Guide

Research & Development
TWS iServ 5.5

forInforBPCS/ERPLX
User Guide
© 2015 TransitionWorks Software Revised: Feb 2015

About TransitionWorks Software
TransitionWorks Software is dedicated to helping our customers improve efficiencies and simplify
business processes. Since product inception in 1997, our TransitionWorks Software organization has
accomplished this goal by iteratively developing, delivering and supporting a set of solutions that help
manufacturing / distribution companies simplify and automate key supply chain processes using many
forms of Automated Identification and Data Capture (AIDC) technologies including RFID, barcodes,
sensor technology, and PLC’s. With proven, successful implementations world-wide,
TransitionWorks’ premier solutions are the system of choice for many leading companies in the
world.
Address
TransitionWorks Software, LLC
2638 Willard Dairy Road, Suite 102
High Point, NC 27265
Sales
Email: info@TransitionWorksSoftware.com
Product Support
Phone +1.336.885.1375
eMail Support@TransitionWorksSoftware.com
Web http://www.TransitionWorksSoftware.com
The latest information and software updates can be found on the TransitionWorks Software support
site above. You must access this site, to download and apply the latest fixes available, by navigating
in your web browser to http://www.TransitionWorksSoftware.com; once there, click on Support and
input your credentials.
If you have not registered yet, click on the “I like to register” link.
If you have already registered, but have forgotten your credentials, click on the “I do not remember
my credentials” link.

TWS iServ 5.5 for Infor BPCS/ERP LX
USER GUIDE
Table of Contents
Overview ........................................................................................................... 1
Introduction ..................................................................................................... 2
Features .................................................................................................... 2
Hardware Requirements ........................................................................... 2
Software Requirements ............................................................................. 2
Reference Documents ............................................................................... 2
Role in TWS AIDC Platform ............................................................................ 3
Overview of Recommended Configuration ............................................... 3
Posting Programs Summary ........................................................................... 4
ALOCDEAL Allocation and de-allocation .................................................. 4
BPCSAUTB Pick Confirm .......................................................................... 4
BPCSBKFL Back-flush .............................................................................. 4
BPCSINV1 Inventory Transactions ........................................................... 4
BPCSINV2 Inventory Cycle Count ............................................................ 4
BPCSINV3 Physical Inventory .................................................................. 5
BPCSLBR1 Labor Posting ........................................................................ 5
INVTRAN Inventory Transactions ............................................................. 5
LOCTRAN Location Transfers .................................................................. 5
PHYTAG Physical Inventory ..................................................................... 5
PORECPT Purchase Order Receipt ......................................................... 5
BALI Message Layout ..................................................................................... 6
BALI Message Header Data Structure ...................................................... 6
ALOCDEAL - Allocation and de-Allocation ........................................................ 7
Introduction ..................................................................................................... 8
Process Overview ..................................................................................... 8
Transaction ID Definition ........................................................................... 8
Transaction Layout.......................................................................................... 9
BPCS v8.x and ERP LX v8.3.x:................................................................. 9
BPCS v6.x: .............................................................................................. 10
Processing .................................................................................................... 11
Process Details........................................................................................ 11
BPCSAUTB – Pick Confirm ............................................................................ 13
Introduction ................................................................................................... 14
Process Overview ................................................................................... 14
Transaction ID Definition ......................................................................... 14
Transaction Layout........................................................................................ 15
ERP LX v8.3.3, v8.3.4 & v8.3.5: .............................................................. 15

USER GUIDE
BPCS v8.2 and ERP LX v8.3.1 & v8.3.2: ................................................ 16
BPCS v6.x: .............................................................................................. 17
Processing .................................................................................................... 18
Process Details........................................................................................ 18
Notes............................................................................................................. 20
BPCSBKFL – Back-flush ................................................................................ 21
Introduction ................................................................................................... 22
ERP LX v8.2, v8.3.x: ............................................................................... 23
BPCS v6.x: .............................................................................................. 24
Processing .................................................................................................... 25
Process Details........................................................................................ 25
BPCSINVX– Inventory Posting ....................................................................... 27
Introduction ................................................................................................... 28
BPCSINV1 Transaction ID Definition ...................................................... 29
ERP LX v8.2 & v8.3.x: ............................................................................. 31
ERP LX v6.x: ........................................................................................... 32
ERP LX v4.0.05CD: ................................................................................. 33
Processing .................................................................................................... 34
Process Details........................................................................................ 34
BPCSLBR1 – Labor Posting ........................................................................... 36
Introduction ................................................................................................... 37
ERP LX v8.2, v8.3.x: ............................................................................... 38
BPCS v6.0.04 & v6.1: .............................................................................. 39
BPCS v6.0.02: ......................................................................................... 40
BPCS v4.0.05CD: .................................................................................... 41
Processing .................................................................................................... 42
Process Details........................................................................................ 42
Data Elements Explained .............................................................................. 44

USER GUIDE
INVTRAN – Inventory Transactions ................................................................ 48
Introduction ................................................................................................... 49
ERP LX v8.3.4 & v8.3.5: .......................................................................... 50
ERP LX v8.3.3: ........................................................................................ 52
BPCS v8.2, ERP LX V8.3.1 & ERP LX v8.3.2: ....................................... 54
BPCS v8.1: .............................................................................................. 55
BPCS v6.0.04 & v6.1: .............................................................................. 56
BPCS v6.0.02: ......................................................................................... 57
Processing .................................................................................................... 58
Audit Trail ................................................................................................ 58
Process Details........................................................................................ 58
Error Overrides.............................................................................................. 63
BPCS v8.2: .............................................................................................. 63
BPCS v6.x, v8.1, ERPLX v8.3.x: ............................................................. 64
LOCTRAN – Location Transfers ..................................................................... 65
Introduction ................................................................................................... 66
BPCS v8.1, v8.2 & ERP LX v8.3.x: ......................................................... 67
BPCS v6.x: .............................................................................................. 68
Processing .................................................................................................... 69
Audit Trail ................................................................................................ 69
Process Details........................................................................................ 69
Error Overrides.............................................................................................. 74
All versions (BPCS v6.x, v8.1, v8.2 & ERP LX v8.3.x):........................... 74
PHYTAG – Physical Inventory ........................................................................ 75
Introduction ................................................................................................... 76
BPCS v8.2 & ERP LX v8.3.x: .................................................................. 77
BPCS v6.x: .............................................................................................. 78
Processing .................................................................................................... 79
Process Details........................................................................................ 79

USER GUIDE
Notes............................................................................................................. 80
PORECPT – Purchase Receipt ...................................................................... 81
Introduction ................................................................................................... 82
BPCS v8.1, v8.2 & ERP LX v8.3.x: ......................................................... 83
BPCS v6.x: .............................................................................................. 84
Processing .................................................................................................... 85
Process Details........................................................................................ 85
Error Overrides.............................................................................................. 87
ERP LX v8.3.3: ........................................................................................ 87
BPCS v8.1, v8.2 & ERP LX v8.3.1, v8.3.2: ............................................. 89
BPCS v6.0.04 & v6.1.x: ........................................................................... 89
BPCS v6.0.02: ......................................................................................... 90

Chapter
1
User Guide
OVERVIEW
TOPICS
Introduction
Role in TWS AIDC Platform
Posting Programs Summary
BALI Message Layout
© 2015 TransitionWorks Software 1 Revised: Feb 2015

User Guide OVERVIEW
Introduction
TWS iServ for BPCS / ERP LX, hereinafter referred to as TWS iServ, facilitates
automation of posting data collected at various operations of a business into the
Infor BPCS / ERP LX application running on an IBM i server. We use the term Infor
ERP in the place of Infor BPCS / ERP LX further in this document.
Features
TWS iServ is a component of the TransitionWorks™ Auto ID Data Collection Platform and is
installed along with TWS iEnabler. TWS iServ consists of a set of IBM i programs that run under
pre-configured IBM i jobs named in the TWS iEnabler Transaction IDs.
The data to be processed via TWS iServ typically arrives into IBM i data queues named in each
TWS iEnabler Transaction ID. The programs validate the data, typically in line with Infor ERP
requirements, and post into Infor ERP by invoking Infor ERP native programs and or executing
custom code. The data will be held for review, and resend or delete, by TWS iEnabler in case of
validation failures.
Hardware Requirements
Recommended additional disk space is 16 GB and 512 MB memory to begin with. Each of the data
queue objects created by TWS iServ are allowed to grow up to 2GB by the IBM i OS.
Software Requirements
IBM i OS V5R4 or later
DB2/400, SQL/400, TCP/IP and Integrated Language Environment
Optional IBM WebSphere MQ V6R1
IBM i Access V5R4 or later
Reference Documents
Use the TWS Installation Instructions iEnabler and TWS User Guide iEnabler documents.

User Guide OVERVIEW
Role in TWS AIDC Platform
Overview of Recommended Configuration
IBM i (aka iSeries, AS/400)
ERP
IIM
TWS Trigger
Program
DQ
DQ
TWS iServ TWS Trigger Processing

iEnabler TWS iEnabler
MQ DQ DQ MQ
Microsoft Windows
Server
MQ
MQ
IBM i Access
TransitionWorks
RT
TWS DP
Server
Devices running an internet browser
Browser like PCs & Handhelds & Mobile
Clients Phones;
Devices that are TCP/IP capable like
PLCs, Light Stacks etc.

User Guide OVERVIEW
Posting Programs Summary
TWS iServ is composed primarily of programs for processing transactions

received by the TWS iEnabler. The Group ID sent with the transaction record
determines which posting program is called to process a particular transaction.
The Group defined in TransitionWorks must match the Transaction ID Fields
Definition in TWS iServ in the order, and number, of fields sent.
NOTE: The terms Group ID and Transaction ID are used interchangeably.
ALOCDEAL Allocation and de-allocation

TWS iServ attempts to process these transactions in line with Infor ERP allocations in ORD
and SFC modules. While the customer order allocations utilize the native ORD720 batch
program, the shop order allocations are processed via custom code.
BPCSAUTB Pick Confirm

TWS iServ attempts to process these transactions in line with Infor ERP Pick Confirm process
via ORD570 on the ORD menu. Only pick confirm by lines and order are supported. Much of
the processing is accomplished by executing native Infor ERP programs.
BPCSBKFL Back-flush
TWS iServ attempts to process these transactions in line with Infor ERP Shop Floor Posting
via SFC650 on the SFC menu or the Production Reporting via JIT600 on the JIT menu. ERP
application updates are done by executing native Infor ERP programs.
BPCSINV1 Inventory Transactions

TWS iServ attempts to process these transactions in line with Infor ERP Inventory
Transactions posting via custom code emulating INV500. We highly recommend the use of
INVTRAN Transaction ID as the preferred option to process any and all inventory
transactions. This Transaction ID is used as an alternative to INVTRAN in a few Infor ERP
scenarios which do not produce desired results.
BPCSINV2 Inventory Cycle Count

User Guide OVERVIEW
TWS iServ attempts to process these transactions in line with Infor ERP Cycle Count posting
via INV515 on the INV03 Menu. Custom code accomplishes the task.
BPCSINV3 Physical Inventory

TWS iServ writes or updates IPH records using the data in these transactions. We highly
recommend the use of PHYTAG Transaction ID instead. Custom code accomplishes the task.
BPCSLBR1 Labor Posting

TWS iServ attempts to process these transactions in line with Infor ERP Shop Order Labor
Posting via SFC600 on the SFC Menu. Updates to ERP application are accomplished by
executing native Infor ERP programs.
INVTRAN Inventory Transactions

TWS iServ attempts to process these transactions in line with Infor ERP Inventory
Transactions posting via INV500 on the INV Menu. Updates to ERP application are
accomplished by executing native Infor ERP programs.
LOCTRAN Location Transfers

TWS iServ attempts to process these transactions in line with Infor ERP Mass Locations
Transfers posting via INV510 on the INV Menu. Custom code accomplishes the task.
PHYTAG Physical Inventory

TWS iServ attempts to process these transactions in line with Infor ERP Tag Entry/Update
posting via INV600 on the INV02 Menu. Custom code accomplishes the task.
PORECPT Purchase Order Receipt

TWS iServ attempts to process these transactions in line with Infor ERP Purchase Receipts
posting via PUR550 on the PUR Menu. Custom code accomplishes the task.

User Guide OVERVIEW
BALI Message Layout
TWS BALI Message uses the following header data structure in the beginning of
each BALI Message read from the data queues configured as the transaction source.
Each BALI Message containing a single transaction data is 2048 characters long.
The header occupies the first 49 characters of each BALI Message as described
below. The rest of the message is used by delimited input data element values as
needed by individual transactions, and are detailed in their respective sections
below. BALI stands for Business Application Linking Infrastructure.
BALI Message Header Data Structure

Data Element Type Size Comment
SENDER Char 8 E1=End IBM i job
TWS RT Identifier Char 8 Typically Enn
Typically zeros; assigned the next
Transaction Number Number 9, 0 running sequence by TWS AIE
Transaction Router process
Message Date Number 8, 0 CcYyMmDd format
Message Time Number 6, 0 HhMmSs format
Transaction ID Char 8 ALOCDEAL, INVTRAN etc.
T=Transaction; R=Resent, E=Error,
Process Code Char 1
X=Deleted
Delimiter Char 1 Typically pipe sign |

Chapter
2
User Guide
ALOCDEAL - Allocation and de-Allocation

TOPICS
Introduction
Transaction Layout
Processing

User Guide ALOCDEAL
Introduction
TWS iServ facilitates automation of updating the customer and shop order
allocations of the ERP database by processing ALOCDEAL transactions.
ALOCDEAL transaction is not available for BPCS v4.0.05CD & v8.1.
Process Overview
TWS iServ helps creating and or changing allocations to support any of the Infor ERP
processes like customer order pick confirm, shop order posting, production reporting etc.
Basic validation of the data is performed to begin with and the transaction is held in error with
an appropriate message for review, and resend or delete, by TWS iEnabler. The BPCS / EPR
LX native program ORD720 is invoked with necessary parameters to update customer order
allocations. In case of a shop order allocation request, custom code is used to update relevant
Infor ERP DATABASE files directly.
Transaction ID Definition

User Guide ALOCDEAL
Transaction Layout
TWS iServ requires the following data structure to process ALOCDEAL requests.
BPCS v8.x and ERP LX v8.3.x:

Trans Type AL/DA Char 2 AL=Allocation, DA=de-Allocation
Allocation Type C/S Char 1 C=Customer Order, S=Shop Order
Order Number Number 8, 0
Order Line Number Number 4, 0
Allocation Sequence No. Number 3, 0
Allocation Warehouse Char 3
Location Code Char 10
Lot Number Char 25
Item Code Char 35
Allocation Quantity Number 11, 3
Unit of Measure Char 2 Not Used
FIFO Transaction SET Number Number 10, 0
FIFO Transaction SEQ Number Number 6, 0

User Guide ALOCDEAL
TWS iServ requires the following data structure to process ALOCDEAL requests.
BPCS v6.x:

Trans Type AL/DA Char 2 AL=Allocation, DA=de-Allocation
Allocation Type C/S Char 1 C=Customer Order, S=Shop Order
Allocation Sequence No. Number 3, 0
Allocation Warehouse Char 2
Lot Number Char 10
Item Code Char 15
Allocation Quantity Number 11, 3
Unit of Measure Char 2 Not Used

User Guide ALOCDEAL
Processing
TWS iServ uses the following process in general to process ALOCDEAL requests.
Note that not all of the details below are applicable to all versions of Infor ERP.
Process Details
 Read the next BALI message from the configured data queue.
 If the value of the SENDER data element of the BALI Message Header Data Structure
is “E1”, then end the IBM i posting job for the ALOCDEAL transaction.
 Delay the IBM i job for allocations using system parameter value in DLY4ALOC.
 Perform validation of data.
o Allocation type must be C or S; else error message UME2121 is applied.
o Transaction type must be AL or DA; else error message UMM0358 is applied.
o For customer order allocations:
 Apply error message UME0537 if ECLL02 record is not found.
 Apply error message UMI3409 if item code supplied mismatches the item code
in ECLL02 file.
 Apply error message UME2002 if ECHL01 record is not found.
 Apply error message UME1364 if customer order is in use.
o For shop order allocations:
 Apply error message UME0537 if FMAL02 record is not found.
 Apply error message UMI3409 if item code supplied mismatches the item code
in FMAL02 file.
o Apply error message UMI3000 if IIML01 record is not found.
o Apply error message UMI2197 if item is not lot controlled but a lot is supplied.
o Apply error message UMI8781 if item is lot controlled but the lot is missing in
ILNL01 file.
o Apply error message UMD0365 if IWML01 record is missing for the warehouse
code supplied.
o Apply error message UMD0522 if ILML01 record is missing for the location code
supplied.
o Ensure quantity supplied is not zero; else apply error message UMG0637.
o Ensure location inventory record in ILIL01 exists; else apply error message
UMI8216.
 For customer order allocations, build the parameters and invoke ORD720.

User Guide ALOCDEAL
 For customer order de-allocations, position to the first sequence using ELAL05
matching order, line, item and sequence; apply error message UMG2087 if a record in
ELAL05 is not found. Delete or update allocations by invoking ORD720 until
requested quantity is de-allocated from ELAL05 records when the supplied warehouse,
location & lot values matches the values in the ELAL05 record read next.
 For shop order allocation requests:
o Update the ELAL05 record matching order, line, item, sequence, warehouse,
location and lot supplied. If such an ELAL05 record does not exist then get the
next sequence number from ELAL05 for the matching order, line and item values
supplied. Build the rest of the field values for ELAL05 record from supplied input
data and create a new ELAL05 record.
o Add the quantity to the FMAL02 record and update it.
o Add the quantity to the ILIL01 record and update it.
o Add the quantity to the ILNL01 record and update it.
 For shop order de-allocation requests:
o Update, by reducing the allocation quantity, the ELAL05 records backwards from
the highest sequence for the order, line, item, warehouse, location and lot matches
until the requested de-allocation quantity is exhausted.
o Store the actual quantity de-allocated in the above process to update rest of the files
below.
o Deduct the actual quantity de-allocated from ELAL05 in the FMAL02 record and
update it.
o Deduct the actual quantity de-allocated from ELAL05 in the ILIL01 record and
update it.
o Deduct the actual quantity de-allocated from ELAL05 in the ILNL01 record and
update it.
o Apply the error message ALD0001 when a different quantity was de-allocated than
the requested quantity.
 Update the TWS iEnabler confirmation file DCSCNFRM if needed.
 Update the TWS iEnabler FIFO status file DCSTATUS if needed.
 This completes the process for a single ALOCDEAL transaction.

Chapter
3
User Guide
BPCSAUTB – Pick Confirm

TOPICS
Introduction
Transaction Layout
Processing
Notes

User Guide BPCSAUTB
Introduction
TWS iServ facilitates automation of the Infor ERP application’s Pick Confirm
(ORD570) process via BPCSAUTB transactions.
BPCSAUTB transaction is not available for BPCS v4.0.05CD & v8.1.
Process Overview
TWS iServ processes BPCSAUTB transactions by invoking ORD570B program in the Infor
ERP environment. Preliminary activities like creating pick confirm work records (EWR) and
setting up customer order allocations are performed by invoking ORD572B and ORD720B
programs respectively. On completion of the pick confirm process, configured print files in
Infor ERP application would be generated to support shipping. You can pick confirm, using a
flag in each transaction, a single customer order line or multiple lines of the same order, both
with multiple allocations as needed.

User Guide BPCSAUTB
Transaction Layout
TWS iServ requires the following data structure to process BPCSAUTB requests.
ERP LX v8.3.3, v8.3.4 & v8.3.5:

File: ILML02 w/ location, YCIL07
Warehouse Code Char 3
w/ other input
File: ECHL02, ECLL01 w/ line
number below
File: ECLL01 w/ order number
above
File: ILNL02 w/ item code, YCIL07
Lot Number Char 25
w/ other input
w/ other input
Container Number Char 10 File: YCIL07 w/ other input
Quantity Picked Number 11, 3
blank=accumulate,
Y=accumulate, allocate & prepare
Confirm Flag Char 1
EWR, 6=accumulate, allocate,
prepare EWR & post into BPCS
AFB internal use: jobWSID Char 10 Optional
Load Number Number 6, 0 For future use

User Guide BPCSAUTB
BPCS v8.2 and ERP LX v8.3.1 & v8.3.2:

w/ other input
number below
above
Lot Number Char 25
w/ other input
w/ other input
blank=accumulate,
Confirm Flag Char 1

User Guide BPCSAUTB
BPCS v6.x:

w/ other input
number below
above
Lot Number Char 10
w/ other input
w/ other input
blank=accumulate,
Confirm Flag Char 1

User Guide BPCSAUTB
Processing
TWS iServ uses the following process in general to post BPCSAUTB requests. Note
that not all of the details below are applicable to all versions of Infor ERP.
Process Details
is “E1”, then end the IBM i posting job for the BPCSAUTB transaction, after shutting
down the BPI998E validation module and the DCS910 error processing module.
 In BPCS v8.2 or ERP LX versions, user and error hold flags are reset in ECHL02 &
ECLL02 files.
 Input data is validated by invoking the BPI998E validation module as follows:
o Apply message UMI500 if ECHL02 record is not found.
o Apply message UMI8201 if ECLL01 record is not found.
o Apply message UMI0861 if order line is not ready for pick confirm process.
o Apply message UMI0611 if location supplied was not found in ILML02 file.
o Apply message UMI3000 if IIML01 record is not found for item code input.
o Apply message UMI8203 if lot number supplied is blank or not found in ILNL02
file when item is lot-controlled.
o Apply message UMI8202 if lot number supplied is not blank and item is not lot-
controlled.
o Apply message UML2083 if container number supplied is blank and item is
container controlled in the facility for the supplied warehouse.
o Apply message UMF0039 if container record YCIL07 is not found or inactive.
o Apply message UML2016 if container number supplied is not blank and item is not
container-controlled.
o The transaction is held in TWS iEnabler error processing if the validation above
failed and the posting process is terminated for the current transaction.
 Using warehouse, order, line, location, lot and container input as keys, the TWS iServ
work file DCSRBTRN is updated for the quantity or a new record is created. This step
is equivalent to Infor ERP allocation during pick confirm.
 Apply message AUT0001 to hold the transaction in TWS iEnabler error processing if
there exists another BPCSAUTB transaction in error for this transaction’s order, line
and the posting process is terminated for the current transaction.
 Mark the TWS iServ work file DCSRBTRN records for this order & line as WIP and
invoke the BPI998P posting module for this transaction.

User Guide BPCSAUTB
 The posting module BPI998P performs the following tasks:
o The posting process checks to see if there exists already a *CONF status record in
the Infor ERP database pick confirm work file EWR; if yes, the current transaction
is held in TWS iEnabler error processing with the message AUT0002 and the
posting process is terminated.
o The Infor ERP program ORD572B is invoked by supplying parameters built using
the current transaction data.
o The existence of a Infor ERP database pick confirm work file EWR record is
verified for the supplied order, line. If a record is not found, then the current
transaction is held in TWS iEnabler error processing with message AUT0011, all
EWR records in *PICK status for the current order are deleted and the posting
process is terminated for the current transaction.
o Existing allocations for the order, line are deleted and new allocations are built, by
calling ORD720 program, using the records from TWS iServ work file
DCSRBTRN marked WIP earlier; the records are then marked “Completed” and
the total quantity of shipment is computed.
o Infor ERP database pick confirm work file (EWR) record is now updated with the
shipment quantity computed in the previous step and its status is set to *CONF.
o If the current EWR record is for a parent item with components, then all the EWR
records for component items are set to *CONF status and their shipment quantities
are computed.
o If the input confirmation flag is 6 to indicate the order shall be pick confirmed, then
the Infor ERP database pick confirm work records in *PICK status are deleted and
the BPCS / ERP LX batch program ORD570B is invoked with necessary
parameters.
o Any time the Infor ERP program invoked fails, the transaction is held in TWS
iEnabler error processing with SYS0001 message and the posting process is
terminated for the current transaction.
 Delete the TWS iServ work file records marked WIP previously.
 This completes the process for a single BPCSAUTB transaction.

User Guide BPCSAUTB
Notes
Please take a moment to review the following:
 Back Order Codes in Infor ERP database customer orders and lines dictate how orders and
or lines can be confirmed. This may affect the way you construct BPCSAUTB
transactions.
o For example, you may need to send an extra BPCSAUTB transaction to pick confirm a
customer order line with zero quantity if you decide not to ship that line item but then
the backorder code dictates that the entire order must be shipped together.
 Validation of TWS iServ BPCSAUTB posting should include comparing satisfactorily its
results with posting similar orders thru Infor ERP interactive sessions. Additionally, you
should perform the next step, like Ship Confirm or Billing, on orders those were pick-
confirmed via TWS iServ.

Chapter
4
User Guide
BPCSBKFL – Back-flush
TOPICS
Introduction
Transaction Layout
Processing

User Guide BPCSBKFL
Introduction
TWS iServ facilitates automation of shop floor posting (SFC650) and production
reporting (JIT600) of the Infor ERP application processes via BPCSBKFL
transactions.
BPCSBKFL transaction is not available for BPCS v4.0.05CD & v8.1.
Process Overview
TWS iServ uses the data from the BPCSBKFL transaction, and other default values as
needed, to build a Infor ERP database Labor Ticket record in the FLT file. The BPCSBKFL
transaction includes an input to indicate posting the labor ticket into the Infor ERP application,
in which case, the batch program SFC651B2 or JIT620B2, as dictated by another input in the
BPCSBKFL transaction, is executed with necessary parameters to update the Infor ERP
database.
IMPORTANT: The IBM i user running the TWS iServ job for the BPCSBKFL transaction
and the value of the data element “Job User ID” in each of the BPCSBKFL transaction must
match for the transaction to post into Infor ERP database successfully. Typically, the
components are not issued from inventory when those two values are different and records are
not flushed out of the work file VLA.

User Guide BPCSBKFL
Transaction Layout
TWS iServ requires the following data structure to process BPCSBKFL requests.
ERP LX v8.2, v8.3.x:

Shop Order Number Number 8, 0
Operation Number Number 3, 0
S=Setup, R=Run, M=Machine,
Char 1
Hours Type I=Indirect & D=Downtime
Transaction Type Char 2 NOT USED currently
Good Quantity Number 11, 3
Rejected Quantity Number 11, 3
Reason Code Char 2
Operation Complete? Char 1 Y=Completed, N=Not yet
Hours Number 8, 3
Employee Code Char 8
Item Code Char 35
Lot Number Char 25
Work Center Number Number 6, 0
Machine Code Char 10
Shift Code Char 1
Start Time Number 6, 0 HhMmSs format
Start Date Number 8, 0 CcYyMmDd format
Begin Container Code Char 10
End Container Code Char 10
Container Type Char 10
Order Type Char 2 WS/BF=SFC, WK=JIT
Process Request Char 2 1S=Post, 0S=Do not post
Shift Team Code Char 2
Scrap Reason Code Char 2
Job User ID Char 10
Override Date Number 8, 0 CcYyMmDd format
Override Time Number 6, 0 HhMmSs format
User Guide BPCSBKFL
TWS iServ requires the following data structure to process BPCSBKFL requests.
BPCS v6.x:
Char 1
Hours Type I=Indirect & D=Downtime
Transaction Type Char 2 NOT USED currently
Reason Code Char 2
Hours Number 8, 3
Item Code Char 15
Lot Number Char 10
Shift Code Char 1
Order Type Char 2 WS/BF=SFC, WK=JIT
Process Request Char 2 1S=Post, 0S=Do not post
Job User ID Char 10

User Guide BPCSBKFL
Processing
TWS iServ uses the following process in general to post BPCSBKFL requests. Note
Process Details
is “E1”, then end the IBM i posting job for the BPCSBKFL transaction, after shutting
down the DCS910 error processing module.
 If a shop order number was not supplied, then search FODL06 (item, operation) and or
FODL07 (item, work center) to find the last open, if not closed, shop order matching
the item, operation / work center.
 If the shop order is in use, hold the transaction for TWS iEnabler error processing with
message “UMS1093 - Shop Order currently in use”.
 If the shop order is closed and the hours are neither Indirect nor Downtime, hold the
transaction for TWS iEnabler error processing with message “LBR0002 - Shop order
number is invalid or closed”.
 If the shop order operation is not found in FODL03 file and the hours are neither
Indirect nor Downtime, hold the transaction for TWS iEnabler error processing with
message “LBR0002 - Shop order number is invalid or closed”.
 Populate the transaction’s work center & item code data elements, if any of them is
empty, from the shop order operation detail file and shop order file respectively.
 Get the item master record for the item code.
 Populate much of the fields of FLT file with information from the transaction and the
FSO, FOD and IIM file records.
o If the shop order operation is not collectible according to FODL01 file, hold the
transaction for TWS iEnabler error processing with message “UM00077 - Data
collection not allowed at this operation”.
o Invoke the SFC601B program to obtain the next labor ticket number.
o Transaction type is set to RJ when reject quantity is more than zero, D for
downtime hours and PR otherwise.
o Access the Work Center Master and Department Master for additional info.
 If the shop order item is lot controlled and the supplied lot number & item code is not
found in the ILNL01 file, the invoke SFC738B program to create the lot in Infor ERP
database database.

User Guide BPCSBKFL
 If the shop order item is container controlled:
o If the input value for container type is empty, then hold the transaction for TWS
iEnabler error processing with message “UML2083 - Container Code Cannot be
Blank”.
o If the input value for container type is not empty but a YCIL01 record cannot be
found, then hold the transaction for TWS iEnabler error processing with message
“UMI0704 - Container Type Not Found.”.
o If the input value for to-container is empty, fill it with the value of from-container.
If it is still empty, get the next container number from the system parameter record
with key “LASTCNTR”, populate the rest of the container master fields using
available data and create a new container master record.
 Populate the rest of the labor ticket data including timestamp info and the four rates.
 Write the FLT record.
 If the request is for Shop Floor Posting, then:
o Invoke the BPF600B2 module to set up necessary VLA records for component
issues and any VLT records for additional labor ticket records.
o If posting is requested, then invoke SFC651B2 to update the Infor ERP database
database.
 If the request is for JIT Production Reporting, then:
o Invoke the BPF600B3 module to set up necessary VLA records for component
issues and any VLT records for additional labor ticket records.
o If posting is requested, then invoke JIT620B2 to update the Infor ERP database
database.
 This completes the process for a single BPCSBKFL transaction.

Chapter
5
User Guide
BPCSINVX– Inventory Posting

TOPICS
Introduction
Transaction Layout
Processing

User Guide BPCSINVX
Introduction
TWS iServ facilitates automation of inventory updates into BPCS / EPP LX

application via BPCSINVx transactions with custom code emulating INV500 and
INV515.
We strongly recommend the use of INVTRAN transaction instead of the BPCSINVx

transactions. If the results are unfavorable when posted via INVTRAN, you may post
via the suitable BPCSINVx transaction and verify the results. Our experience shows
that the DRP ‘H’ transaction and Cycle Counts worked favorably in some
installations when posted via BPCSINVx.
The following table describes the availability of BPCSINVx transactions.
BPCSINV1 BPCSINV2 BPCSINV3

BPCS v4.0.05 CD Provided Provided Provided
BPCS v6.0.02 INVTRAN preferred Provided PHYTAG preferred
BPCS v6.0.04 INVTRAN preferred Provided PHYTAG preferred
BPCS v6.1.x INVTRAN preferred Provided PHYTAG preferred
BPCS v8.1 Not Available Not Available Not Available
BPCS v8.2 INVTRAN preferred Provided Not Available
ERP LX v8.3.1 INVTRAN preferred Provided Not Available
NOTE: Use INVTRAN or BPCSAUTB for BPCSINV4 that is discontinued in this release.

User Guide BPCSINVX
Process Overview
TWS iServ uses BPCSINV2 transaction for cycle counting by emulating INV515 of the Infor
ERP application. Physical inventory posting is accomplished via BPCSINV3 transaction with
custom code. Rest of the inventory transactions are posted via BPCSINV1 with custom code
emulating INV500 of the Infor ERP application.
BPCSINV1 Transaction ID Definition

User Guide BPCSINVX
Note: BPCSINV2 & BPCSINV3 transactions use the configuration of BPCSINV1.

User Guide BPCSINVX
Transaction Layout
TWS iServ requires the following data structure to process BPCSINVx requests.
ERP LX v8.2 & v8.3.x:

Transaction Type Char 2 Inventory Transaction Effect code
Order Line Number Number 4, 0 Where applicable
Item Code Char 35 As needed
Warehouse Code Char 3 As needed
Lot Number Char 25 Where applicable
Location Code Char 10 As needed
Transaction Quantity Number 11, 3 As needed
Unit of Measure Char 2 As needed
Order Number Number 8, 0 Where applicable
Cost Number 10, 3 As needed
Comment Char 35 As needed
Reason Code Char 2 As needed
To Shop Order Number 8, 0 Where applicable
Container Code Char 10 Where applicable
Container Type Char 10 Where applicable
Container Flag Char 1 1=On
Mfg Method Material Code Char 2 Where applicable
Manufacturer Code Char 8 Where applicable
Manufacturer Lot Number Char 25 Where applicable
Mfg. Lot Date CcYyMmDd Number 8, 0 Where applicable
Number of Containers Char 5 Where applicable
FIFO Transaction SET Number Number 10, 0 As needed
FIFO Transaction SEQ Number Number 6, 0 As needed

User Guide BPCSINVX
ERP LX v6.x:
Mfg Method Material Code Char 2 Where applicable
Manufacturer Code Char 8 Where applicable
Manufacturer Lot Number Char 10 Where applicable
Mfg. Lot Date CcYyMmDd Number 8, 0 Where applicable
Number of Containers Char 5 Where applicable

User Guide BPCSINVX
ERP LX v4.0.05CD:

User Guide BPCSINVX
Processing
TWS iServ uses the following process in general to post BPCSINVx requests. Note
Process Details
is “E1”, then end the IBM i posting job for BPCSINV1 transaction, after shutting
down:
o BPI505E data validation module and
o BPI505P transaction posting module and
o BPI505CC cycle count processing module and
o DCS910 error processing module.
 Perform data validation by executing the BPI505E module:
o If the transaction effect code input is not found in the ITEL01 file, hold the
transaction for TWS iEnabler error processing with message “UMI3032 - Invalid
Transaction Effect” and get out of the validation process.
o If the transaction effect affects purchase orders, fetch the purchase order line from
the HPOL01 file.
 If successful, replace the input item code with the value from HPOL01 record.
 Otherwise, hold the transaction for TWS iEnabler error processing with
message “UMI3036 - Invalid Purchase Order”.
o If the transaction effect is a customer order shipment, fetch the customer order line
from the ECLL01 file.
 If successful, replace the input item code with the value from ECLL01 record.
 Otherwise, hold the transaction for TWS iEnabler error processing with
message “UMH0108 - Invalid Customer Order”.
o If the transaction effect needs to check shop order number and is a shop order
receipt or multiple issue transaction,
 If the input item code is blank and the input container code is not empty, then
fill the input item code from the container master record YCIL01, if found
matching the input container code.
 If the input item code is not a co/by-product as indicated in the FMAL05 file on
searching the file, then replace the input item code with the parent item code
that is the item in the corresponding shop order header file FSOL01. If a record
is not found in FSOL01 file, then hold the transaction for TWS iEnabler error
processing with message “UMI3034- Invalid Shop Order”.

User Guide BPCSINVX
o If the transaction effect needs to check shop order number and is a shop order
single issue transaction,
 If the input item code is blank and the input order line number is zeros, hold the
transaction for TWS iEnabler error processing with message “UMI3035 – Item
# or Seq # Incorrect for this Shop Order”.
 If the input order line number is not zeros, fetch the FMAL01 record. If the
record is missing, then hold the transaction for TWS iEnabler error processing
with message “UMS1092 - Invalid Shop Order/Sequence Number”.
o If the input container code is not blank but the YCIL01 record is not found and the
transaction effect does not affect inventory receipts and does not affect inventory
opening balance, hold the transaction for TWS iEnabler error processing with
message “UMY0060 – Container ID is invalid”.
 If the validation passed, build a list of parameters for posting into Infor ERP.
o Use supplied data, gathered data in the validation process above and other data
outlined below in this section.
o Fetch the IIML01 record using the input item code; note that the input item code
may have been changed in the above validation process.
o Fetch the lot muster if input lot number was not blank to obtain manufacturer.
o Compute number of containers from the input quantity.
o Use the item code and lot number from the container master if input container was
not empty. Warehouse and location may also be obtained from container master.
 Invoke the posting module BPI505P for BPCSINV1 transaction.
o Custom INV500 emulated code is used to post a variety of inventory transactions.
 Invoke the posting module BPI505CC for BPCSINV2 transaction.
o Custom INV515 emulated code is used to post cycle count transaction.
 Invoke the posting module BPI505PI for BPCSINV3 transaction.
o Using input item code, warehouse, location, lot and container as keys, find the
physical inventory record in IPHL10 file.
o If a record is found, replace the quantity with the input quantity; otherwise, create a
new record in IPHL10 using supplied and gathered data.
 This completes the process for a single BPCSINVx transaction.

Chapter
6
User Guide
BPCSLBR1 – Labor Posting

TOPICS
Introduction
Transaction Layout
Processing
Data Elements Explained

User Guide BPCSLBR1
Introduction
TWS iServ facilitates automation of labor reporting (SFC600 – SFC620) of the

Infor ERP application process via BPCSLBR1 transaction.
Process Overview
TWS iServ uses the supplied data for each BPCSLBR1 transaction, and other default values
as needed, to build a Infor ERP database Labor Ticket record in the FLT file. The labor ticket
is then posted into the Infor ERP database by executing the batch program SFC620B with
necessary parameters to update the Infor ERP database.

User Guide BPCSLBR1
Transaction Layout
TWS iServ requires the following data structure to process BPCSLBR1 requests.
ERP LX v8.2, v8.3.x:

Hours Type Char 1
I=Indirect & D=Downtime
Transaction Type Char 1 Must be 2
Reason Code Char 2
Hours Number 8, 3
Item Code Char 35
Lot Number Char 25
Shift Code Char 1
Order Type Char 1 Must be S
Process Request Char 2
Job User ID Char 10

User Guide BPCSLBR1
BPCS v6.0.04 & v6.1:

Hours Type Char 1
Reason Code Char 2
Hours Number 8, 3
Item Code Char 15
Lot Number Char 10
Shift Code Char 1
Job User ID Char 10

User Guide BPCSLBR1
BPCS v6.0.02:
Hours Type Char 1
Reason Code Char 2
Hours Number 8, 3
Item Code Char 15
Lot Number Char 10
Shift Code Char 1

User Guide BPCSLBR1
BPCS v4.0.05CD:
Hours Type Char 1
Reason Code Char 2
Hours Number 7, 2
Item Code Char 15
Lot Number Char 10
Shift Code Char 1

User Guide BPCSLBR1
Processing
TWS iServ uses the following process in general to post BPCSLBR1 requests. Note
Process Details
is “E1”, then end the IBM i posting job for BPCSLBR1 transaction, after shutting
down the DCS910 error processing module,
 If a shop order number was not supplied, a non-zero shop operation is supplied and the
hours type is neither I nor D, then browse FODL06 (item, operation) to select the order
where the operation is not completed yet. If all order operations are completed,
overwrite the input shop order & work center values with the last shop order number &
work center respectively.
 If no FODL06 record is found and the shop order number is still zeros or the operation
number supplied was zeros, and work center supplied is non-zero, then browse
FODL07 (item, work center, order and operation) to select the order where the
operation is not completed yet. If all order operations are completed, overwrite the
input shop order & work center values with the last shop order number & work center
respectively.
 If the shop order is in use, hold the transaction for TWS iEnabler error processing with
message “UMS1093 - Shop Order currently in use”.
 If the shop order operation is not found in FODL03 file and the hours are neither
Indirect nor Downtime, hold the transaction for TWS iEnabler error processing with
message “LBR0002 - Shop order number is invalid or closed”.
 If the shop order status is ‘XX’ indicating it is closed and the hours are neither Indirect
nor Downtime, hold the transaction for TWS iEnabler error processing with message
“LBR0002 - Shop order number is invalid or closed”.
 If there are no errors so far, then:
o If input work center is zeros, overwrite it with the value from FODL03 record.
o If input item is empty, or it is different from the FSOL01 record, overwrite it with
the value from FSOL01 record.
 If Transaction Type is not 2, hold the transaction for TWS iEnabler error processing
with message “LBR0001 - Labor transaction contains non-elapsed (<>'2') Transaction
type”; else access IIML01 record.

User Guide BPCSLBR1
 Populate much of the fields of FLT file with information from the transaction and the
FSO, FOD and IIM file records.
o If the shop order operation is not collectible according to FODL01 file, hold the
transaction for TWS iEnabler error processing with message “UM00077 - Data
collection not allowed at this operation”.
o Invoke the SFC601B program to obtain the next labor ticket number.
o Transaction type is set to RJ when reject quantity is more than zero, D for
downtime hours and PR otherwise.
o Access the Work Center Master and Department Master for additional info.
o If the item master indicates JIT item or the input order type is J, then hold the
transaction for TWS iEnabler error processing with message “LBR0003 - JIT
Labor Transaction should be handled through backflush”.
 If the shop order item is container controlled, and container type is found and container
master is not found, use input supplied and values from FODL03, LWKL01, CDPL01,
ILNL01 etc. to create a new container master record.
 Populate the rest of the labor ticket data including timestamp info and the four rates.
 Write the FLT record.
 Invoke the SFC620B program with necessary parameters to post the labor ticket.
 This completes the process for a single BPCSLBR1 transaction.

User Guide BPCSLBR1
Data Elements Explained
Job User ID
This data element is currently not used.
Shop Order Number, Operation Number, Hours Type, Transaction Type, Item Code
and Work Center
If the Labor Transaction doesn't have Shop Order Number supplied, then try to get Shop Order
/ Operation Number by using Item Code /Work Center Number combo by searching FOD for
Shop Order / Operation Number, unless the Hours Type is either Downtime or Indirect. If no
open Shop Orders match, use the last closed shop order number, if found. If no Shop Order or
Operation supplied, Item Code and Work Center Number entered, find the first FOD record
with that Item Code / Work Center Number.
In order to identify the shop order(s) to post the labor transaction, the following combo of
input can be fed from the source:
1. Valid Shop Order Number AND Operation Number, in which case, Item Code and Work
Center Code can be blanks and zeros respectively; these will be retrieved from FSO &
FOD respectively.
2. Valid Item Code AND Operation Number, in which case, Shop Order Number and Work
Center Code can both be zeros.
3. Valid Item Code AND Work Center Number, in which case, Shop Order Number and
Operation Number can both be zeros.
4. In 2 & 3 above, an attempt to fetch an open operation detail record from FOD will be
made; if NO open operation is found, then the last completed operation detail record will
be used to get the Shop Order Number & Operation or Work Center Number.
When NO shop order operation detail was found, then the transaction is considered in error for
Invalid Shop Order provided the Hours Type is not I (indirect hours).
If the shop order status (SOSTS from FSO file) is found to be XX, then the transaction is
considered in error for Invalid Shop Order provided the Hours Type is not I (indirect
hours).
If the transaction is NOT an Elapsed Time transaction (SFID2 <> 2), then the transaction is
considered in error with error message id LBR0001 and not processed further.
Other values for Hours Type could be D for downtime hours, R for run hours, S for setup
hours and M for machine hours.
NOTE: During the above search, the values of SFORD, SFOPNO and SFWRKC are modified
as necessary.

User Guide BPCSLBR1
Once a shop order and operation is found fit for posting, the value of the fields TORD,
TOPNO, TWRKC, TPROD & THTYP in file FLT are set as the values of the data elements
Shop Order Number, Operation Number, Work Center Number, Item Code & Hours Type
respectively.
Employee Code
The value of TEMPN in FLT file is set as the value of the data element Employee Code.
Override Date
The value of TTDTE in FLT file is set as the value of Override Date provided it is not zeros;
otherwise, either the Message Date, when not zeros, from the BALI Header data structure is
used to fill TTDTE. System date is used, when Message Date is zeros, to fill TTDTE.
Good Quantity
The value of TPCS in FLT file is set as the value of the data element Good Quantity.
Rejected Quantity
The value of TFQSR in FLT file is set as the value of the data element Rejected Quantity.
Shift Code
The value of TSHFT in FLT file is set as the value of the data element Shift Code.

User Guide BPCSLBR1
Lot Number
The value of TFLOT in FLT file is set as the value of the data element Lot Number.
Machine Code
The value of TMACH in FLT file is set as the value of the data element Machine Code.
Shift Team Code

The value of TSHTM in FLT file is set as the value of the data element Shift Team Code.
Hours and Start Time

If the value of data element Hours is not zeros, then its value is loaded onto the field THRS in
file FLT. Otherwise, the value of the data element Start Time is converted to a decimal
equivalent of hours & minutes to be saved as the value for the field TFSTR in file FLT; the
Message Time from the BALI Header data structure, when NOT zeros, or else the System
Time is converted to a decimal equivalent of hours & minutes will be loaded onto the field
TFSTP in file FLT.
Order Type
While the value of this data element is not significant in anyway, it must be set to S to avoid
the transaction ending in validation failure.
Container Type, Begin & End Container Codes

If the Item Code determined for the labor transaction is container controlled, then the fields
LTFCTR & LTCNTR in FLT file are set to the values of the data elements Begin Container
Code & End Container Code respectively.
If the Container Type was found in Container Master file YCIL01 and if the End Container
Code did not exist in the Container Master file YCIL01, then the End Container Code record
will be created in the Container Master file YCIL01.
Override Time
The first non-zero value in that order from (i) the data element Override Time, (ii) the
Message Time from the BALI Header data structure and (iii) the System Time will be used to
fill the field LTTIME in file FLT.
Process Request
The value of the Process Request data element will be used to fill the LTSTS field of FLT file.
Reason Code
The field TFRES in FLT file will be set to the value of the data element Reason Code.

User Guide BPCSLBR1
Operation Complete
When the value supplied for the data element Operation Complete is N, the field TOCMP in
file FLT is set to blanks; otherwise, the field TOCMP in file FLT is set to the value supplied
for the data element Operation Complete.
Miscellaneous Info
 The value for field TID in file FLT is set as ‘LT’.
 The value for field TICK in file FLT is set to 1 provided the shop order number
(SFORD) is not zeros.
 If Rejected Quantity is sent as a positive value, then the value for field TFTRN in file
FLT is set to ‘RJ’; otherwise, the value of field TFTRN in file FLT is set to ‘PR’.
 The value for field TFWSID in file FLT is set as the value of the Workstation Id
(positions 244 to 253) from the program’s system data structure.
 The value for fields LTENUS & LTMNUS in file FLT is set as the value of the User Id
(positions 254 to 263) from the program’s system data structure.
 The value for field LTENDT in file FLT is set as the value of the Message Date from
the BALI Header data structure when it is not zeros; else the system date is applied.
 The value for field LTENTM in file FLT is set as the value of the Message Time from
the BALI Header data structure when it is not zeros; else the system time is applied.
 The value for field LTMNDT in file FLT is set as the value of the Message Date from
the BALI Header data structure when it is not zeros; else the system date is applied.
 The value for field LTMNTM in file FLT is set as the value of the Message Time from
the BALI Header data structure when it is not zeros; else the system time is applied.
 The value for field TCLAS in file FLT is set from the field ICLAS of file IIM obtained
from the Item Code determined during the validation process.
 If the Work Center Master (LWKL01) record was found for the value of TWRKC,
then the value of the field TFLOC in file FLT is set to the value of field WKLOC of
file LWKL01.
 If the Department Master (CDPL01) record was found for the value of field WDEPT
of file LWKL01, then the value of the field TFWHS in file FLT is set to the value of
field CDWHS of file CDPL01.
 The value of the field LTFAC in file FLT is set to the value of field SOFAC in file
FSOL01.
 If the value of field IJIT in file IIM is ‘J’, then the value of field LTORDT in file FLT
is set to ‘WK’; else, its value is set to the value of field SOORDT of file FSOL01.
 The value of field TDEPT in file FLT is set as the value of the field WDEPT in file
LWKL01.
Labor Ticket Number

The field TREC in FLT file is populated with a call to the BPCS program SFC601B. The
value of the field TPRSH in file FLT is set to the value of TREC.

Chapter
7
User Guide
INVTRAN – Inventory Transactions

TOPICS
Introduction
Transaction Layout
Processing
Error Overrides

User Guide INVTRAN
Introduction
TWS iServ facilitates automation of inventory posting (INV500) of the Infor ERP
application process via INVTRAN transaction.
INVTRAN transaction is not available for BPCS v4.0.05CD.
Process Overview
TWS iServ performs basic validation of the supplied data in each INVTRAN transaction, to
some extent in line with the Infor ERP interactive display program INV500D2, and posts the
INVTRAN transaction to update the Infor ERP database by executing the Infor ERP batch
program INV500B1 with necessary parameters.

User Guide INVTRAN
Transaction Layout
TWS iServ requires the following data structure to process INVTRAN requests.
ERP LX v8.3.4 & v8.3.5:

Transaction Type Char 2
Item Code Char 35
Lot Number Char 25
Mfg Method Material Code Char 2
Container Code Char 10
Transaction Quantity Number 11, 3
Standard Cost Number 15, 5
Comment Char 35
Re-designate Item Code Char 35
Reason Code Char 2
Transaction Date Number 8, 0
Unit of Measure Char 2
Advice Note Number Char 15
Shop Order Line Number Number 4, 0
Manufacturer Code Char 8
Manufacturer Lot Number Char 25
Vendor Number Number 8, 0
Vendor Lot Number Char 25
Exchange Rate Number 15, 7
Manufacturer Date Number 8, 0
Quantity per Container Number 11, 3
Pallet Number Number 9, 0
Pallet Check Flag Char 1
Override Date Number 8, 0

User Guide INVTRAN
Override Time Number 6, 0
Transaction User ID Char 10
Transaction Device ID Char 10
Number of Containers Number 5, 0
Quantity Rejected Number 11, 3
FCI Allocation Seq Number 3, 0
FCI List Number Number 8, 0

User Guide INVTRAN
ERP LX v8.3.3:
Item Code Char 35
Lot Number Char 25
Comment Char 35
Reason Code Char 2
Quantity Rejected Number 11, 3

User Guide INVTRAN

User Guide INVTRAN
BPCS v8.2, ERP LX V8.3.1 & ERP LX v8.3.2:
Item Code Char 35
Lot Number Char 25
Comment Char 35
Reason Code Char 2

User Guide INVTRAN
BPCS v8.1:
Item Code Char 35
Lot Number Char 25
Comment Char 35
Reason Code Char 2

User Guide INVTRAN
BPCS v6.0.04 & v6.1:
Item Code Char 15
Lot Number Char 10
Comment Char 15
Reason Code Char 2

User Guide INVTRAN
BPCS v6.0.02:
Item Code Char 15
Lot Number Char 10
Comment Char 15
Reason Code Char 2

User Guide INVTRAN
Processing
TWS iServ uses the following process in general to post INVTRAN requests. Note
Audit Trail
The IBM i job that posts INVTRAN transactions produces an IBM i spool file named
INV500O1 with details of each transaction processed into Infor ERP.
Process Details
is “E1”, then end the IBM i posting job, after shutting down the BPI500E validation
module and DCS910 error processing module.
 Invoke the BPI500E module to validate supplied data. Here are some details of the
validation process:
o If the Transaction Type supplied does not exist in Infor ERP database ITEL01 file
or if it is one T, # and %, then hold the transaction for TWS iEnabler error
processing with message “UMI3032 – Invalid Transaction Effect”.
o Invoke the Infor ERP program SYS610B to validate the Transaction User ID
supplied for access to the Transaction Type; if not authorized, hold the transaction
for TWS iEnabler error processing with message “UMS6008 – User not authorized
to Transaction Effect”.
o If the Transaction User supplied does not have authority to the Warehouse
supplied, hold the transaction for TWS iEnabler error processing with message
“UMS6009 – User xxx is not authorized to warehouse yy”.
o Hold the transaction for TWS iEnabler error processing for conditions (in line with
the Infor ERP INV500D2 program) causing the error messages below:
 UMA0219 – Enter valid Transaction Date
 UMI0247 – Invalid Manufactured Date
 UMI2030 – Transaction date less than or equal to previous close – F13 to
override
 UMI3036 – Invalid Purchase Order Number
 UMH4067 - Item is invalid for purchase order line
 UMY0012 - Pre-assigned Lot # &1 must be used for this transaction
 UMI3068 - Return is greater than quantity received on this order
 UMH1041 - Warning: Quantity received against closed P.O. F13 to override
 UME1361 - Invalid Transaction Effect, Drop Ships cannot affect inventory

User Guide INVTRAN
 UMH4070 - P.O. is currently being processed by another user. Infor ERP
program PUR950B is invoked to check for this condition.
 UMI3037 - Invalid Location Entered
 UMI9625 - Re-designate item number blank or invalid
 UMI9626 - Entered item number must not be the same as the Re-designate item
number
 UMI9624 - Re-designate item not found
 UMI9663 - Invalid Transaction - To and/or From item cannot be item type '6'
 UMI0241 - Lot exists in a Managed Warehouse
 UMH1012 - Invalid commodity code
 UMH1035 - Invalid Transaction Effect - Service Commodities cannot be
received
 UMI3000 - Invalid item number
 UMI3035 - Item # or Seq # Incorrect for this Shop Order
 UMI0612 - Shop order is not FAS order
 UMY0124 - Inventory locations of ****** are not allowed
 UMY0011 - Item is not a container controlled Item
 UMI9623 - Lot control fields for entered item numbers are not the same
 UMY0126 - Non container controlled items cannot be re-designated container
controlled
 UMI9636 - Different units of measure and/or use physical /theoretical found,
press HELP or F1
 UMI9638 - Allocated Lot records found for this item, cannot Re-designate
 UMI3067 – Lot cannot be blank
 UMY0185 - For Lot controlled items; Warehouse, Location and Container
must be blank
 UMI3041 - Invalid Lot Number Entered
 UMI3100 - Item Number not same as lot Item Number
 UMI9653 - Allocations found on FROM item on the ILN file. Press F13 to
override
 UMI9651 - Allocations found on FROM item (IIM file). Press HELP/F1 or
F13 to override
 UMY0065 - Item and/or Lot number of the &1 in error
 UMY0122 - Container on hand balance is equal to zero
 UMY0123 - Allocations found on container xxx. Press F13 transaction.
 UMI9640 - Quantity on hand for RE-designate item is equal to zero
 UMI9656 - Entered location and Warehouse not found on the ILI file
 UMI9652 - Allocations found on FROM item on the ILI file. Press F13 to
override
 UMI9635 - If location is entered, you must enter the Warehouse for this
process
 UMI9654 - Allocations found on FROM item on the IWI file. Press F13 to
override
 UMI0209 - Multiple container processing is not allowed for this order
 UMD0107 - No shipments made for Order, Line, Lot and Container.

User Guide INVTRAN
 UMD0109 - * Not allowed to receive more than shipped
 UMI3042 - Invalid Reason Code entered
 UMG0420 - Period is closed. F13 to override or re-enter date
 UMI3025 - Invalid unit of measure
 UMI3049 - Unit of Measure for a Commodity Item does not match Unit of
Measure on the Purchase Order
 UMI3070 - Quantity cannot be Negative (for opening balance transactions)
 UMI3034 - Invalid Shop Order Number
 UMY0187 - Warehouse xx is not in facility zz
 UMI2024 - Qty to be received is greater than qty open – Press F13 to override
 UMI2031 - Qty to be received is greater than qty open – Press F13 to override
 UMI0222 - Item number, warehouse, or sequence number incorrect for this
shop order
 UMI3250 - Sequence number must not be zero
 UMI3002 - Invalid shop order number
 UMI9630 - Component found is a Co/By product and cannot be processed
 UMI9622 - Item not allocated to order. F13 to create Allocation
 UMI2022 - Quantity returned is greater than quantity issued –Press F13 to
override
 UMH4065 - Warning: Quantity received greater than Receipt Tolerance. F13 to
receive (after invoking Infor ERP PUR953B program)
 UMH4066 - Warning: Quantity received less than Receipt Tolerance. Press F13
to receive (after invoking Infor ERP PUR953B program)
 UMI5228 - Warning: A different Warehouse has been specified for P.O. F13
to override
 UMI3445 - Neg qty greater than either Qty Received and/or Costed Qty on this
order
 UMI3446 - Negative qty entered greater than Costed Qty.
 UMH1034 - Non-Inventory Items CANNOT Effect Inspection
 UMI3072 - Negative qty entered for "Affect Qty in Inspection" transaction
 UMI3214 - Qty greater than Qty In Inspection for this P. O. Line Number
 UMI3043 - Warehouse Value must be Blank
 UMI3009 - Invalid Warehouse entered
 UMI7373 - A Warehouse Management warehouse may not be used by this
program
 UMI3044 - Lot Value must be Blank
 UMI0245 - Cannot Multi-Issue without Shop Orders when ZPA Parm is set to
"L"
 UMY0213 - Invalid Manufacturing Method Code
 UML0002 - Cannot enter a costing only method code
 UMI2023 - Warning: Cost/Price is negative or zero - Press F13 to override
 UMI5057 - Lot is inactive. Use F13 to reactivate
 UMY0084 - Lot has a status for which transaction not allowed
 UMH0090 - Lot Vendor Number is not equal to this vendor
 UMY0085 - Lot Status is x. Press F13 to accept.

User Guide INVTRAN
 UMY0302 - Location has a status of &1, transaction not allowed
 UMY0301 - Location has a status of &1, Press F13 to accept
 UMI3102 - Lot Has Expired
 UMQ0753 - Manufacturer is not equal to the existing manufacturer assigned to
the lot
 UMQ0765 - Valid Lot Must Exist for Quality Action. Press F13 to Bypass QA
 UMQ0768 - Lot already on "Quality Hold". Press F13 to Bypass QA
 UMQ0754 - Transaction quantity must be greater than zero for a Quality
Transaction
 UMQ0755 - Number of containers must be greater than zero for a Quality
Transaction
 UMY0125 - A Container starting with an * is not allowed for this transaction
 UMY0120 - Container not found. Container must exist for this transaction.
 UMY0009 - Entry of a Container Id is mandatory
 UMY0061 - Container Id is invalid
 UMY0133 - Container creation not supported for negative transactions
 UMY0057 - Container Type record not found in the YCI file.
 UMY0001 - Invalid Container
 UMY0171 - Container type not eligible for use
 UMD0112 - The container on-hand quantity does not match the transaction
quantity. Press Help for more info.
 UMY0069 – Container xxx not available
 UMI3025 - Invalid unit of measure
 UMI2020 - Lot does not exist - cannot accept transaction
 UMI9629 - User defined program for lot numbering not found. Enter Lot
Number
o Invoke the Infor ERP program PUR950B to reset the PO busy flag.
 If the validation failed as coded, then:
o Update the TWS iEnabler FIFO status file DCSTATUS if needed.
o Update the TWS iEnabler confirmation file DCSCNFRM if needed.
o This completes the process for the INVTRAN transaction failing validation.
 If the transaction type is for Multiple Issues, then the BPI500P module is invoked to
execute custom code emulating the Multiple Issue process of Infor ERP INV500. On
completion of posting the Multiple Issue transaction into Infor ERP database:
o Update the TWS iEnabler FIFO status file DCSTATUS if needed.
o Update the TWS iEnabler confirmation file DCSCNFRM if needed.
o This completes the process for a Multiple Issue INVTRAN transaction.
 In preparation of invoking INV500B1, custom code is executed to build the parameters
needed. Some points to note are:
o Execute Infor ERP PUR953B program for purchase tolerance when applicable.
o Hold the transaction for TWS iEnabler error processing with message “UMI3818 -
Resupply order/line number not on file” if the Infor ERP database file ECLL01
does not contain a record for the order line supplied in the transaction.

User Guide INVTRAN
o Hold the transaction for TWS iEnabler error processing with message “UMI2021 -
Entered item number invalid for order/line combination.” if the item code supplied
does not match the item code on the Infor ERP database file ECLL01 record
fetched for the order line supplied in the transaction.
o When Infor ERP is configured to issue non-allocated shop order items and the
transaction pertains to a shop order issue for a non-allocated item and order line
number supplied is zeros, browse the Infor ERP database file FMAL02 to compute
the order line number.
o Execute the Infor ERP programs CST590B (Cost Retrieval) and CST592B (Copy
Global costs to Facility) as appropriate.
o Extract the exchange rate when applicable by browsing Infor ERP database file
GCCL01 using currency codes and transaction date.
o If the item code supplied is container controlled, then update the Infor ERP system
parameter file ZPA record with key ‘LASTCNTR’ as applicable.
 Invoke the Infor ERP program INV500B1 to update the Infor ERP database.
o Multiple invocations may be needed to handle multiple containers.
 This completes the process for a single INVTRAN transaction.

User Guide INVTRAN
Error Overrides
TWS iServ allows for automatically overriding certain Infor ERP application
warnings encountered during the posting of INVTRAN transactions. The warning
messages are pre-defined, applicable globally and configurable via TWS iEnabler.
BPCS v8.2:
Message ID Message Description
UMG0420 Period is closed. F13 to override or re-enter date.
UMH1041 Warning: Quantity received against closed P.O. F13 to override
UMH4065 Warning: Quantity received greater than Receipt Tolerance. F13 to receive.
UMH4066 Warning: Quantity received less than Receipt Tolerance. F13 to receive.
UMI2022 Quantity returned is greater than quantity issued - Press F13 to override.
UMI2023 Warning: Cost/Price is negative or zero - Press F13 to override.
UMI2024 Qty to be received is greater than qty open - Press F13 to override.
UMI2031 Qty to be received is greater than qty open - Press F13 to override
UMI5057 Lot is inactive. Use F13 to reactivate.
UMI5228 Warning: A different Warehouse has been specified for P.O. F13 to override.
UMI9622 Item not allocated to order. F13 to create Allocation.
UMI9636 Different units of measure and/or use physical/theoretical found, press F1.
UMI9651 Allocations found on FROM item (IIM file). Press HELP/F1 or F13 to override.
UMI9652 Allocations found on FROM item on the ILI file. Press F13 to override.
UMI9654 Allocations found on FROM item on the IWI file. Press F13 to override
UMQ0754 Transaction quantity must be greater than zero for a Quality Transaction
UMQ0757 Invalid or Missing Parameters on QA Trigger.
UMQ0765 Valid Lot Must Exist for Quality Action. Press F13 to Bypass QA.
UMQ0768 Lot already on "Quality Hold". Press F13 to Bypass QA.
UMY0085 Lot Status is . Press F13 to accept.
UMY0123 Allocations found on . Press F13 transaction.
UMY0301 Location has a status of , Press F13 to accept.

User Guide INVTRAN
BPCS v6.x, v8.1, ERPLX v8.3.x:
UMI2024 Qty to be received is greater than qty open - Press F13 to override.
UMI2030 Transaction date less than or equal to previous close - F13 to override
UMI2031 Qty to be received is greater than qty open - Press F13 to override
UMI5057 Lot is inactive. Use F13 to reactivate.
UMI5228 Warning: A different Warehouse has been specified for P.O. F13 to override.
UMI9622 Item not allocated to order. F13 to create Allocation.
UMI9636 Different units of measure and/or use physical/theoretical found, press F1.
UMI9651 Allocations found on FROM item (IIM file). Press HELP/F1 or F13 to override.
UMI9652 Allocations found on FROM item on the ILI file. Press F13 to override.
UMI9654 Allocations found on FROM item on the IWI file. Press F13 to override
UMQ0754 Transaction quantity must be greater than zero for a Quality Transaction
UMQ0757 Invalid or Missing Parameters on QA Trigger.
UMY0085 Lot Status is . Press F13 to accept.
UMY0123 Allocations found on . Press F13 transaction.
UMY0301 Location has a status of , Press F13 to accept.

Chapter
8
User Guide
LOCTRAN – Location Transfers

TOPICS
Introduction
Transaction Layout
Processing
Error Overrides

User Guide LOCTRAN
Introduction
TWS iServ facilitates automation of Mass Location Transfers (INV510) of the Infor
ERP application process via LOCTRAN transaction.
LOCTRAN transaction is not available for BPCS v4.0.05CD.
Process Overview
TWS iServ emulates inventory transfers using custom code to update the Infor ERP database
for LOCTRAN transactions.

User Guide LOCTRAN
Transaction Layout
TWS iServ requires the following data structure to process LOCTRAN requests.
BPCS v8.1, v8.2 & ERP LX v8.3.x:

From Warehouse Char 3
To Warehouse Char 3
Transfer Date Number 8, 0
Item Code Char 35
Lot Number Char 25
Quantity Transferred Number 11, 3
From Location Char 10
To Location Char 10
Reference Number Number 8, 0
Reason Code Char 2
Comment Char 35

User Guide LOCTRAN
BPCS v6.x:
From Warehouse Char 2
To Warehouse Char 2
Transfer Date Number 8, 0
Item Code Char 15
Lot Number Char 10
Quantity Transferred Number 11, 3
From Location Char 6
To Location Char 6
Reference Number Number 6, 0
Reason Code Char 2
Comment Char 15

User Guide LOCTRAN
Processing
TWS iServ uses the following process in general to post LOCTRAN requests. Note
Audit Trail
The IBM i job that posts LOCTRAN transactions produces an IBM i spool file named
BPI510O1 with details of each transaction processed into Infor ERP.
Process Details
 Read the next BALI Message from the configured data queue.
 If the value of the SENDER data element of the BALI Message Header Data Structure is
“E1”, then end the IBM i posting job, after shutting down the DCS910 error processing
module.
 Perform validation of data supplied:
o If an IWEL01 record, for key as the value of From Warehouse data element, is found
in the Infor ERP database, then hold the transaction for TWS iEnabler error processing
with message “UMI7373 - A Warehouse Management warehouse may not be used by
this program”.
o If an IWML01 record, for key as the value of From Warehouse data element, is not
found in the Infor ERP database, then hold the transaction for TWS iEnabler error
processing with message “UMI3052 - Invalid From Warehouse”.
o If an IWML01 record, for key as the value of From Warehouse data element, is not
found in the Infor ERP database, then hold the transaction for TWS iEnabler error
processing with message “UMI3052 - Invalid From Warehouse”.
 When the record is found and the Warehouse Type is 2 (Managed Warehouse),
then hold the transaction for TWS iEnabler error processing with message
“UMD0666 - Transaction not allowed for sequenced warehouse”.
o If the Transaction User ID is not authorized for the From Warehouse (a record is
missing for these key values in the Infor ERP database file ZX4L02), then hold the
transaction for TWS iEnabler error processing with message “UMS6009 - User xxx is
not authorized to warehouse yy”.
o Repeat the validations performed to the From Warehouse above on the To Warehouse.
o If the Transfer Date is earlier that the Infor ERP Last Close Date, and if the Infor ERP
warning message UMI2030 is not configured to be automatically overridden, then hold
the transaction for TWS iEnabler error processing with message “UMI2030 -
Transaction date less than or equal to previous close - F13 to override”.
o Halt further processing of the current transaction if any errors were detected with the
above validations; go back to read the next BALI Message from the data queue.

User Guide LOCTRAN
o If Container Code supplied is not blank, access the Infor ERP database file YCIL02
record for the Container Code.
 If the record is locked currently, then hold the transaction for TWS iEnabler error
processing with message “UMI1014 - Attempting to access a record that is in use
by another job. Try again or end job”, ELSE
 If the record is not found, then hold the transaction for TWS iEnabler error
processing with message “UMY0001 – Invalid Container”, ELSE
 If the Warehouse of the Container is different from the From Warehouse, then hold
the transaction for TWS iEnabler error processing with message “UMY0005 – The
Container is not in this warehouse”, ELSE
 If the Container Code supplied starts with “*”, then hold the transaction for TWS
iEnabler error processing with message “UMY0125 – A Container starting with an
* is not allowed for this transaction”, ELSE
 If the Container Code is “*TYPE”, then hold the transaction for TWS iEnabler
error processing with message “UMY0171 – Container type not eligible for use”,
ELSE
 Overwrite From Warehouse, Lot Number, From Location, Item Code input values
with the values from the Container Master record accessed. Compute the current
on-hand quantity from the Container Master record and load it onto the Quantity
Transferred input value.
o Access the Infor ERP database file IIML01 for the Item Code value supplied.
 If the record is not found, then hold the transaction for TWS iEnabler error
processing with message “UMI3000 - Invalid item number”, ELSE
 If the item is not lot-controlled but the Lot Number is not blank, then hold the
transaction for TWS iEnabler error processing with message “UMI8202 - Not a lot
control item”, ELSE
 If the item is lot-controlled and the Lot Number is blank, then hold the transaction
for TWS iEnabler error processing with message “UMI8203 - Invalid Lot
Number”, ELSE
 Access the Infor ERP Database file ILNL01 for Lot Number and Item Code values;
if the record is absent, then hold the transaction for TWS iEnabler error processing
with message “UMI8203 - Invalid Lot Number”.
o If Quantity Transferred is negative, then hold the transaction for TWS iEnabler error
processing with message “UMI3202 - Quantity to allocate cannot be negative”.
o If the value for From Location data element of the transaction is “******”, then hold
the transaction for TWS iEnabler error processing with message “UMY0124 -
Inventory locations of ****** are not allowed”.
o If the value for To Location data element of the transaction is “******”, then hold the
transaction for TWS iEnabler error processing with message “UMY0124 - Inventory
locations of ****** are not allowed”.
o Access the Infor ERP database file ILML01 for the From Warehouse & From Location
values supplied. If a record was not found, then hold the transaction for TWS iEnabler
error processing with message “UMI3048 - Invalid From Location”.

User Guide LOCTRAN
o Access the Infor ERP database file ILML01 for the To Warehouse & To Location
values supplied. If a record was not found, then hold the transaction for TWS iEnabler
error processing with message “UMI3050 - Invalid To Location”.
o If the value for From Warehouse data element of the transaction matches the value for
To Warehouse and the value for From Location data element of the transaction
matches the value for To Location, then hold the transaction for TWS iEnabler error
processing with message “UMI3558 - Invalid From Location/To Location
combination”.
o Access the Infor ERP database file ILIL01 for the From Warehouse, Item Code, Lot
Number and From Location values supplied. If current on-hand quantity computed
from the ILIL01 record (assume zeros when a record does not exist) is smaller than the
value for Quantity Transferred data element of the transaction, then hold the
transaction for TWS iEnabler error processing with message “UMI3559 - WARNING
- transaction will force inventory < 0 at t his LOC, F13 to override” provided the
message UMI3559 is not automatically overridden by TWS iEnabler configuration for
the LOCTRAN transaction.
 If the value for Quantity Transferred data element of the transaction is more than
the current on-hand less soft allocations of the ILIL01 record and the message
UMI3560 is not automatically overridden by TWS iEnabler configuration for the
LOCTRAN transaction, then hold the transaction for TWS iEnabler error
processing with message “UMI3560 - WARNING - transaction > qty avail. due to
existing alloc., F13 to override”.
o If Container Code is not blanks, and the Allocated to Orders quantity in the YCIL02
record accessed earlier is not zeros and the message UMY0114 is not automatically
overridden by TWS iEnabler configuration for the LOCTRAN transaction, then hold
the transaction for TWS iEnabler error processing with message “UMY0114 -
WARNING - The Container has allocations - F13 to Override”.
o If Container Code is not blanks, then access the Infor ERP database file IPHL12 for the
From Warehouse & Container Code values supplied; if a record was not found and the
message UMI0256 is not automatically overridden by TWS iEnabler configuration for
the LOCTRAN transaction, then hold the transaction for TWS iEnabler error
processing with message “UMI0256 - Warning: An unposted physical inventory tag
exists for this container”.
o Access the Infor ERP database file ILIL01 for the To Warehouse, Item Code, Lot
Number and To Location values supplied. If the record is found and the item is quality-
controlled and the location status is different from the From Location Inventory record
and the message UMI0221 is not automatically overridden by TWS iEnabler
configuration for the LOCTRAN transaction, then hold the transaction for TWS
iEnabler error processing with message “UMI0221 - Warning: TO and FROM location
statuses are different. F13 to accept”.
o Access the Infor ERP database file ZPAL01 for the supplied reason code appended to
the literal ‘RCODT ‘. If a record is not found, then hold the transaction for TWS
iEnabler error processing with message “UMI3042 - Invalid Reason Code entered”.
o Halt further processing of the current transaction if any errors were detected so far; go
back to read the next BALI Message from the data queue.

User Guide LOCTRAN
 Use the custom code to update the Infor ERP database.
 Important notes on processing the transfer From data element values supplied:
o Create or update IWIL01 for the From Warehouse & Item Code.
o Create or update ILIL01 for the From Warehouse, Item Code, From Location & Lot
Number.
o Invoke CST590B and CST592B as appropriate to get cost information.
o Initialize and populate certain fields of ITH.
o Read the Infor ERP database file GCCL01 as appropriate for currency exchange rates.
o Lock the Infor ERP database file IIML02 record for the Item Code to obtain next
inventory transaction history sequence number.
o Loop thru the Infor ERP database file ITHL02, incrementing the above sequence
number if needed, until a record for the sequence number is not found.
o Write a new inventory transaction history record in the Infor ERP database file
ITHL02.
o Update the Infor ERP database file IIML02 with the new inventory transaction history
sequence number.
o Print the information in the Audit Trail spool file BPI510O1.
o Print any of the following errors in the Audit Train spool file BPI510O1 if applicable:
 UMI1150 - No Actual Cost found for Item at From Facilty
 UMI1153 - No Actual Cost found for Item at GLOBAL
 UMI1151 - No Standard Cost found for Item at From Facility
 UMI1154 - No Standard Cost found for Item at GLOBAL
 The above process is repeated for the transfer To data element values supplied.
Additionally, inactive records are removed from the Infor ERP database file ILI for the
target location. Additionally, before writing the inventory transaction history record for the
To data element values:
o Access the Infor ERP database container file YCIL02 for the Container Code supplied.
If the record is found and the allocation quantity is more than zero, then browse thru
the Infor ERP database file ELAL10 using the Container Code supplied as key, de-
allocate the inventory by calling Infor ERP SFC735B program and delete the ELAL01
record.
 Update the Infor ERP Shop Order Allocations file FMA or Customer Order Line
details ECL file for allocations as appropriate.
 Update the Cycle Count flag in the Infor ERP database file ILIL01 for the target
location as appropriate.
 Update the Container Master record with To Warehouse, To Location & Lot
Number.
 Write a new inventory transaction history record in the Infor ERP database file ITHL02 for
the target location.
 Update the Infor ERP database file IIML02 with the new inventory transaction history
sequence number.
 Print the information in the Audit Trail spool file BPI510O1.
 Print any of the following errors in the Audit Train spool file BPI510O1 if applicable:
o UMI1152 - No Standard Cost found for Item at To Facility
o UMI1154 - No Standard Cost found for Item at GLOBAL
User Guide LOCTRAN
 Browse thru the Infor ERP allocations ELAL10 file for the Container Code supplied and
update them for the target location supplied. Also update the Infor ERP Shop Order
allocations file FMAL01 as appropriate.
 This completes the process for a single LOCTRAN transaction.

User Guide LOCTRAN
Error Overrides
TWS iServ allows for automatically overriding certain Infor ERP application
warnings encountered during the posting of LOCTRAN transactions. The warning
messages are pre-defined, applicable globally and configurable via TWS iEnabler.
All versions (BPCS v6.x, v8.1, v8.2 & ERP LX v8.3.x):

UMI0221 Warning: TO and FROM location statuses are different. F13 to accept
UMI0256 Warning: An unposted physical inventory tag exists for this container
UMI2030 Transaction date less than or equal to previous close - F13 to override
UMI3559 WARNING - transaction will force inventory < 0 at this LOC, F13 to
override
UMI3560 WARNING - transaction > qty avail. due to existing alloc., F13 to
override
UMY0114 WARNING - The Container has allocations - F13 to Override.

Chapter
9
User Guide
PHYTAG – Physical Inventory

TOPICS
Introduction
Transaction Layout
Processing
Notes

User Guide PHYTAG
Introduction
TWS iServ facilitates automation of Physical Inventory Tag Entry/Update (INV600)

of the Infor ERP application process via PHYTAG transaction.
PHYTAG transaction is not available for BPCS v4.0.05CD & v8.1.
Process Overview
TWS iServ emulates physical inventory tag updates using custom code to update the Infor
ERP database for PHYTAG transactions. Once the physical tags are updated, Infor ERP
Physical Inventory Close program INV650 can be used to post the tags to update physical
inventory. Required report programs can then be executed for audit and other requirements.

User Guide PHYTAG
Transaction Layout
TWS iServ requires the following data structure to process PHYTAG requests.
BPCS v8.2 & ERP LX v8.3.x:

Tag Number Number 7, 0
Item Code Char 35
Physical Location Char 10
Physical Lot Char 25
Physical Count Quantity Number 11, 3
Create New Tag? Char 1 1=Yes

User Guide PHYTAG
TWS iServ requires the following data structure to process PHYTAG requests.
BPCS v6.x:
Tag Number Number 7, 0
Item Code Char 15
Physical Location Char 6
Physical Lot Char 10
Physical Count Quantity Number 11, 3
Create New Tag? Char 1 1=Yes

User Guide PHYTAG
Processing
TWS iServ uses the following process in general to post PHYTAG requests. Note
Process Details
 Read the next BALI Message from the configured data queue.
“E1”, then end the IBM i posting job, after shutting down the DCS910 error processing
module.
 Access the Infor ERP database IPHL05 file using Tag Number & Warehouse Code
supplied.
 If the tag is not found,
o If the Create New Tag flag is set on, create a new physical inventory tag record in the
IPH file using the values supplied and Item Master.
o If the Create New Tag flag is off,
 If the Tag Number supplied is greater than zero, then hold the transaction for TWS
iEnabler error processing with message “PHY0001 - No record exists for the tag
number/warehouse”.
 Otherwise, access the Infor ERP database IPHL10 file using Item Code,
Warehouse Code, Physical Location, Physical Lot and Container Code.
 If a record is found, then replace the quantity with Physical Count Quantity
supplied. If duplicate records exist for the key values, then hold the transaction
for TWS iEnabler error processing with message “PHY0002 - Duplicate
records exist for this Item/Wh/Loc/Lot/Container combo”.
 Otherwise, hold the transaction for TWS iEnabler error processing with
message “PHY0001 - No record exists for the tag number/warehouse”.
 If the tag exists, replace the quantity with Physical Count Quantity supplied.
 This completes the process for a single PHYTAG transaction.

User Guide PHYTAG
Notes
TWS iServ PHYTAG processing includes the benefit of updating physical inventory by
automatically searching the current tags using Item, Warehouse, Location, Lot & Container codes
combo. Duplicates are reported via the TWS iEnabler Error Processing option.
Remember to stop the IBM i posting job for PHYTAG transaction before running the Infor ERP
INV660 Clear Physical Inventory option which requires exclusive locks on the Infor ERP database
IPH file.

Chapter
10
User Guide
PORECPT – Purchase Receipt

TOPICS
Introduction
Transaction Layout
Processing
Error Overrides

User Guide PORECPT
Introduction
TWS iServ facilitates automation of Purchase Receipts (PUR550) of the Infor ERP
application process via PORECPT transaction.
PORECPT transaction is not available for BPCS v4.0.05CD.
Process Overview
TWS iServ performs basic validation of the supplied data in each PORECPT transaction and
posts the transaction to update the Infor ERP database by executing a batch version of the
Infor ERP PUR550D2 program. You must have licensed the purchasing module sources from
Infor to use this TWS iServ PORECPT transaction.

User Guide PORECPT
Transaction Layout
TWS iServ requires the following data structure to process PORECPT requests.
BPCS v8.1, v8.2 & ERP LX v8.3.x:

Purchase Order Number 8, 0
Reason Code Char 2
Comment Char 35
Transaction Date Number 8, 0 CcYyMmDd format
Item Code Char 35
PO Line Number Number 4, 0
Invoice Exchange Rate Number 15, 7
Lot Number Char 25
PO Status Char 1
Receiver Ticket Number Number 6, 0
Quantity Received Number 11, 3
Purchase Unit of Measure Char 2
PO Warehouse Char 3
Costed Quantity Number 11, 3
Actual Cost Total-global Number 14, 2
Manufacturer Date Number 8, 0 CcYyMmDd format
Job User ID Char 10
Transaction Time Number 6, 0
Transaction Type Char 1, 0

User Guide PORECPT
TWS iServ requires the following data structure to process PORECPT requests.
BPCS v6.x:
Purchase Order Number 6, 0
Reason Code Char 2
Comment Char 15
Transaction Date Number 8, 0 CcYyMmDd format
Item Code Char 15
PO Line Number Number 3, 0
Invoice Exchange Rate Number 15, 7
Lot Number Char 10
PO Status Char 1
Receiver Ticket Number Number 6, 0
Quantity Received Number 11, 3
Purchase Unit of Measure Char 2
PO Warehouse Char 2
Costed Quantity Number 11, 3
Actual Cost Total-global Number 14, 2
Manufacturer Date Number 8, 0 CcYyMmDd format
Job User ID Char 10
Transaction Time Number 6, 0 HhMmSs format
Transaction Type Char 1, 0

User Guide PORECPT
Processing
TWS iServ uses the following process in general to post PORECPT requests. Note
Process Details
“E1”, then end the IBM i posting job, after shutting down the BPP550E validation module
and DCS910 error processing module.
 Invoke the BPP550E module to validate supplied data.
o Access the Infor ERP database HPHL01 file with the purchase order number supplied.
If the record exists and its busy flag is set on, then hold the transaction for TWS
iEnabler error processing with message “UMH4070 - P.O. is currently being processed
by another user. Press ENTER and try again”. Terminate the processing of current
transaction and read the next BALI message from the configured data queue.
o Access the Infor ERP database YCIL01 file with the container code supplied when it is
not blank. If the record exists and its item code is not the same as the supplied item
code, then hold the transaction for TWS iEnabler error processing with message
“UMY0001 – Invalid Container”. Terminate the processing of current transaction and
read the next BALI message from the configured data queue.
o Access the Infor ERP database HPOL01 file with the purchase order & line numbers
supplied. If the record exists and the line status indicates “Fully Received and Fully
Costed”, then hold the transaction for TWS iEnabler error processing with message
“UMH1036 – Purchase Order Line fully received”. Terminate the processing of
current transaction and read the next BALI message from the configured data queue.
o Access the Infor ERP database ITEL01 file with the transaction type supplied. If the
record is missing, then hold the transaction for TWS iEnabler error processing with
message “UMI3429 – Invalid Transaction Code Entered”. Terminate the processing of
current transaction and read the next BALI message from the configured data queue.
o If the supplied item is not a commodity,
 Access the Infor ERP database IIML01 file with the item code supplied.
 If the record is missing, then hold the transaction for TWS iEnabler error
processing with message “UMP0206 – Invalid Item Number”.
 Otherwise, if the item is container-controlled and the Container Type supplied is
empty or can’t be found in the Infor ERP database YCIL01 file, then hold the
transaction for TWS iEnabler error processing with message “UMI7275 – Invalid
Container Type entered”. If the item is container-controlled and the Quantity per
Container supplied is zero, then hold the transaction for TWS iEnabler error
processing with message “POR0011 – Quantity per Container MUST be greater
than zero”.
User Guide PORECPT
o If the TWS iEnabler configuration for holding transactions prior to Infor ERP Last
Close date is set to Y, and if the Transaction Date is not zeros and earlier that Infor
ERP Last Close date, then hold the transaction for TWS iEnabler error processing with
message “POR2030 – Transaction date prior to Last Month End Closing Date”.
o Let the calling module know, by the parameter, if there is an error.
 If the transaction was not resent from TWS iEnabler, ensure there is not another
PORECPT transaction in error for the same Purchase Order Line waiting to be processed
in TWS iEnabler.
 If the Infor ERP transaction effect requires spreading this receipt and configured to affect
the receipts column of inventory,
o Browse thru the Infor ERP database HPOL37 file for the purchase order and item code
supplied to store the purchase order line numbers with their respective open quantities,
until the receipt quantity supplied is exhausted.
o Build a TWS iServ PORECPT transaction for each stored line and open quantity.
o Based on TWS iEnabler configuration, either send the transactions to the posting data
queue or process them by executing the validation & posting modules.
o Record the new transactions in the TWS iEnabler log history for auditing.
 Otherwise,
o Create or update the TWS iEnabler work file DCSPOTRN for the values supplied in
the current transaction.
o Set the status flag in the TWS iEnabler work file DCSPOTRN for posting in progress.
o Invoke the TWS iEnabler posting module BPP550P with required parameters.
 The module BPP550P is a clone of PUR550D2 with custom coding to skip UI.
 If the supplied item code is container-controlled, the custom module BPP550D will
be invoked to create necessary container records.
o On successful posting, delete the TWS iEnabler work file DCSPOTRN records which
were flagged earlier for posting in progress.
 This completes the process for a single PORECPT transaction.

User Guide PORECPT
Error Overrides
ERP LX v8.3.4 & v8.3.5:

Message ID Description
DWM0027 WARNING: tolerance check failed. F16 to override.
LMP0134 Customer order in use, Press F13 to accept P/O without allocatin
LMP0135 P/O WH doesn't match C/O WH press F13 to accept PO without alloc
LMP0147 Line will be over allocated. Press F13 to continue without allo
UMH0136 Lot/Item combination does not exist or is "New". Press F14 to co
UMH0328 Warning: Costed amount is negative or zero - Press F22 to overr
UMH1032 Enter the items original receiver ticket number / F22 to bypass.
UMH4076 Warning: Quantity received greater than receipt tolerance, F16 t
UMH4077 Warning: Quantity received less than receipt tolerance, F16 to r
UMH4089 Country of Origin for line is different from PO. Press F5 to ac
UMH5006 not in specified, press F16 to transfer , inventory and any al
UMI0433 Can not update Lot with revised Vendor/Manufacturer Information.
UMI0907 is in managed warehouse and cannot be moved
UMI2020 Lot does not exist - cannot accept transaction.
UMI3006 P.O. receipt is greater than remaining quantity.
UMI3060 WARNING - transaction will force Inventory < 0 at this location.
UMI3430 User not authorized to this warehouse
UMM1619 Press F19 to perform Drop Ship Confirmation or ENTER to continue
UMQ0229 QSN record already on "Quality Hold". Press F19 to bypass QA.
UMQ0230 QMS/Item combination does not exist. Press F14 to create.
UMQ0753 Manufacturer is not equal to the existing manufacturer assigned
UMQ0758 Item/Manufacturer not established in QMS. Press F19 to bypass QA
UMQ0759 Error occurred while processing QA Trigger. Press F19 to Bypass
UM00054 Line will be added to delivery . Press F22 to continue.
UM00267 PO number is not on the Advice Note/GRN number selected.
UM00838 Warning: P.O. Warehouse has been changed to Warehouse from Faci
UM01062 Warning: Line scheduled receipt date outside tolerance, F16 to
UM01422 Warning - Transaction is to a closed period or book. F22 to Override
UM01423 Warning - Transaction is to a closed period or book. F22 to Override
UM01434 Warning: Receiving against a Purchase Order on Hold. F22 to continue.
UM01444 Warning: Number of containers is zero, F14 to override.
UM01526 Invalid Lot Status &1 &3 for transaction. Press F13 to override.
User Guide PORECPT
ERP LX v8.3.3:
DWM0027 WARNING: tolerance check failed. F16 to override.
LMP0134 Customer order in use, Press F13 to accept P/O without allocatin
LMP0135 P/O WH doesn't match C/O WH press F13 to accept PO without alloc
LMP0147 Line will be over allocated. Press F13 to continue without allo
UMH0328 Warning: Costed amount is negative or zero - Press F22 to overr
UMH4089 Country of Origin for line is different from PO. Press F5 to ac
UMI0433 Can not update Lot with revised Vendor/Manufacturer Information.
UMI0907 is in managed warehouse and cannot be moved
UMI2020 Lot does not exist - cannot accept transaction.
UMI3060 WARNING - transaction will force Inventory < 0 at this location.
UMI3430 User not authorized to this warehouse
UMM1619 Press F19 to perform Drop Ship Confirmation or ENTER to continue
UMQ0229 QSN record already on "Quality Hold". Press F19 to bypass QA.
UMQ0230 QMS/Item combination does not exist. Press F14 to create.
UMQ0753 Manufacturer is not equal to the existing manufacturer assigned
UMQ0759 Error occurred while processing QA Trigger. Press F19 to Bypass
UM00054 Line will be added to delivery . Press F22 to continue.
UM00267 PO number is not on the Advice Note/GRN number selected.
UM00838 Warning: P.O. Warehouse has been changed to Warehouse from Faci
UM01062 Warning: Line scheduled receipt date outside tolerance, F16 to

User Guide PORECPT
BPCS v8.1, v8.2 & ERP LX v8.3.1, v8.3.2:
UMG0444 Period does not exist. F22 to override.
UMH0141 Lot status is On Hold
BPCS v6.0.04 & v6.1.x:

UMG0444 Period does not exist. F13 to override

User Guide PORECPT
BPCS v6.0.02:

TWS Iserv 5.5 For Infor BPCS - ERP LX User Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

TWS Iserv 5.5 For Infor BPCS - ERP LX User Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Research & Development

TWS iServ 5.5

© 2015 TransitionWorks Software Revised: Feb 2015

© 2015 TransitionWorks Software Revised: Feb 2015

© 2015 TransitionWorks Software Revised: Feb 2015

© 2015 TransitionWorks Software Revised: Feb 2015

© 2015 TransitionWorks Software Revised: Feb 2015

© 2015 TransitionWorks Software Revised: Feb 2015

© 2015 TransitionWorks Software 1 Revised: Feb 2015

© 2015 TransitionWorks Software 2 Revised: Feb 2015

Overview of Recommended Configuration

IBM i (aka iSeries, AS/400)

TWS iServ TWS Trigger Processing

© 2015 TransitionWorks Software 3 Revised: Feb 2015

TWS iServ is composed primarily of programs for processing transactions

NOTE: The terms Group ID and Transaction ID are used interchangeably.

ALOCDEAL Allocation and de-allocation

BPCSAUTB Pick Confirm

BPCSINV1 Inventory Transactions

BPCSINV2 Inventory Cycle Count

© 2015 TransitionWorks Software 4 Revised: Feb 2015

BPCSINV3 Physical Inventory

BPCSLBR1 Labor Posting

INVTRAN Inventory Transactions

LOCTRAN Location Transfers

PHYTAG Physical Inventory

PORECPT Purchase Order Receipt

© 2015 TransitionWorks Software 5 Revised: Feb 2015

BALI Message Header Data Structure

© 2015 TransitionWorks Software 6 Revised: Feb 2015

ALOCDEAL - Allocation and de-Allocation

© 2015 TransitionWorks Software 7 Revised: Feb 2015

ALOCDEAL transaction is not available for BPCS v4.0.05CD & v8.1.

© 2015 TransitionWorks Software 8 Revised: Feb 2015

BPCS v8.x and ERP LX v8.3.x:

© 2015 TransitionWorks Software 9 Revised: Feb 2015

Data Element Type Size Comment

© 2015 TransitionWorks Software 10 Revised: Feb 2015

© 2015 TransitionWorks Software 11 Revised: Feb 2015

© 2015 TransitionWorks Software 12 Revised: Feb 2015

BPCSAUTB – Pick Confirm

© 2015 TransitionWorks Software 13 Revised: Feb 2015

BPCSAUTB transaction is not available for BPCS v4.0.05CD & v8.1.

© 2015 TransitionWorks Software 14 Revised: Feb 2015

ERP LX v8.3.3, v8.3.4 & v8.3.5:

© 2015 TransitionWorks Software 15 Revised: Feb 2015

BPCS v8.2 and ERP LX v8.3.1 & v8.3.2:

© 2015 TransitionWorks Software 16 Revised: Feb 2015

Data Element Type Size Comment

© 2015 TransitionWorks Software 17 Revised: Feb 2015

© 2015 TransitionWorks Software 18 Revised: Feb 2015

© 2015 TransitionWorks Software 19 Revised: Feb 2015

Please take a moment to review the following:

© 2015 TransitionWorks Software 20 Revised: Feb 2015

© 2015 TransitionWorks Software 21 Revised: Feb 2015

BPCSBKFL transaction is not available for BPCS v4.0.05CD & v8.1.

© 2015 TransitionWorks Software 22 Revised: Feb 2015

ERP LX v8.2, v8.3.x:

© 2015 TransitionWorks Software 24 Revised: Feb 2015

© 2015 TransitionWorks Software 25 Revised: Feb 2015

© 2015 TransitionWorks Software 26 Revised: Feb 2015

BPCSINVX– Inventory Posting

© 2015 TransitionWorks Software 27 Revised: Feb 2015