receive0110: TERM not set ... Only applies to UNIX and DOS systems.
The environmental variable TERM is not set. It can be set by the following command:
TERM=terminaltype
export TERM
receive0120: invalid TERM parameter
The terminal named by the environment variable TERM is not defined in either the /usr/lib/escape directory or the /etc/termcap file.
receive0130: unable to establish dialog area
The process is not able to display the input parameter screen. See your system administrator.
receive0210: system error message
receive0210: cannot open dictionary for purchase order detail file
The system is not able to access the dictionary for the purchase order detail file, pod. This is not a user recoverable error, see your system administrator.
receive0220: No index for order, freight in purchase order detail file
The secondary index made up of the fields order and freight, has been removed from file pod. Make sure the index is defined in the definition file, and then convert the data file.
bopen####: error message
receive0310: cannot open [header | detail] file for name
The system cannot open the file for the reason specified by the bopen error. The table below lists the files this process must open.
Table 37 - 7
File Name
poh purchase order header file
pod purchase order detail file
recvh receiving slip header file
recvd receiving slip detail file
Refer to the General Error Messages section for further information on the bopen message.
receive0320: system error message
receive0320: cannot set [header | detail] file field list for name
The field list cannot be set for the file for the reason specified by system error message. Refer to Table 37 - 7 above for the list of files used in this process.
receive0330: system error message
receive0330: cannot lock for insertions [header | detail] file for name
The file is being used by another user. Wait a little while and then try again. If this message is displayed again, see your system administrator. Refer to Table 37 - 7 for the list of files locked by this process.
receive0410: PO purchase order busy, balance field not updated
The process was not able to update the balance field for purchase order purchase order. The process will continue to create receiving slips. After the process has completed, ensure that the purchase order header file can be updated, and then run the process Update Purchase Order Balances on the Data Entry, Purchase Order menu
receive0510: PO purchase order sequence sequence# busy, received field not updated.
The process was not able to update the received field for purchase order purchase order sequence number sequence#. The process will continue to create receiving slips. As part of the recovery process, set the received field for the purchase order detail record to the number of units on the corresponding receiving slip.
0710: date is in closed period
The date entered for the receiving slips must be in an open period.
0810: purchase order purchase order not found
Both the starting and ending purchase orders must be in the purchase order header file, poh.
0820: First order number is > last order number
An invalid range of purchase orders was entered. The last purchase order number in the range must be greater than the beginning purchase order number. Enter a new range of purchase order numbers.
0900: Purchase order purchase order has already been received
The process is skipping this purchase order because it has been completely received. This message is informational only; it does not halt the process.
1000: purchase order purchase order not found
You must enter an existing purchase order number for the beginning purchase order.
1010: purchase order purchase order has already been received.
The process is skipping this purchase order because it has been completely received. This message is informational only; it does not halt the process.
1200: end of slip number sequence sequence#
The process cannot increment sequence, which is the last receiving slip number in the receiving slip header file. Enter another starting slip number.