SIG Error Processing End User Procedure
Last Updated: June 6, 2021
SIG (Strategic Information Group) is an application, which imports input files created in OnBase or thru an automated script process, into QAD. A SIG Error indicates there was a problem with how the information was entered/processed. This document explains how to use the SIG Suspended transaction screen to research AP voucher errors, purchase order create processing errors, and shift production errors in QAD.
Samples of SIG Error Alert email:
Accounts Payable Voucher: These transactions are only processed by the Accounts Payable department.
Transaction : AP Voucher Distribution Template
Date/Time : 01/13/2021 14:46:49.635-05:00
File : /qond/apps/sigcon/data/proc/ap210113144436.prodP2.
"~tab~" "~tab~" "~tab~" ""
"~tab~" "~tab~" "P22101133810" "11/13/20"
Purchasing: These transactions are only handled by the Purchasing department.
Transaction : PO Maint Comments Template
Date/Time : 11/17/2021 14:47:43.040-05:00
File : /qond/apps/sigcon/data/proc/PO211117144427.prodAX.
"CRIBAX" "DTRENT" "12 COMPARTMENT "1.00000"
"DESTINATION" "DELIVERY" "" ""
"~tab~" "90112486" "~tab~" "317087"
Research suspended transaction
Use SIG suspended transaction screen to research the issue.
QAD SIG Suspended Transactions (37.34.1)
Enter site (In this example, we will use prodp2)
Listing of suspended transactions.
For AP Voucher errors, look for AP Voucher Maintenance in the list:
For Purchase Order creation errors, look for PO Maint in the list:
Navigation: This is a terminal screen. Use your arrow keys to navigate the menu. F1 is the go button and F4 to exit the frame of the screen.
With the Browse option selected, use the F1 key to navigate to the list of suspended transactions. Use the arrow key to select the transaction you want to view.
Press F1 to see the details of the transaction:
There are several Transaction Detail records for one file. The detail records can be accessed by pressing the F1 key until you land on the Trans Det #
Use your arrow keys to traverse thru the detail records
Trans Det #2 is where you would find the PO number
Trans Det #3 is where the invoice number, and invoice date are located:
In this example, Trans Det #6 is where the error is located:
Use the F4 key to exit out of the transaction after viewing. At this time, the transaction can be purged and the Invoice voucher can be re-processed using the standard procedure steps in Onbase.
Purging the Errored Transaction
Navigate back to the open 37.34.1 SIG Suspended Transactions screen
Click F4 twice so that you can arrow to the Purge selection
Click Tab to get to the Trans # field.
Enter the transaction # visible on the screen
Click Tab and enter the same transaction # in the To: field
Click Tab until OK is highlighted and click F1.
Click F1 to confirm the transaction will be deleted.
Suspended Transaction Error Examples and Explanations – Accounts Payable Voucher Processing. These transactions are only processed by the Accounts Payable department.
Invalid Account: An invalid account number was used in the distribution record.
Invalid Receiver: Receiver number entered is invalid or the receiver number has already been vouchered.
PO Receiver does not exist: Receiver number entered does not exist in the domain.
Purchase Order does not exist: The purchase order number entered does not exist in the domain.
Period has been closed for entity: The General Ledger calendar is currently closed for the given entity.
Mismatched Account # & Cost Center: The account number and cost center combination in the distribution record is invalid for the domain.
Suspended Transaction Error Examples and Explanations – Purchase Order Processing. These transactions are only processed by the Purchasing department.
Mismatched Account # & Cost Center: The account number and cost center combination in the Item Detail record is invalid for the domain.
Invalid Cost Center: The cost center used is not a valid cost center for the domain
Invalid Account Number: The account number used is not a account number for the domain
File input too long: Error is caused by a special or non-ascii character in either the part number or description filed or the comments section.
Tax Zone not found: Supplier record is either missing a country code, or the tax information for the company code is not setup in QAD. Contact IT for this error
Credit Terms code must exist or be blank: Credit terms that was used is not valid for the domain.
Restricted procedure for item status code O: The item is marked as Obsolete in 1.4.1 item master.
Ship-To does not exist: Supplier code used in the ship to field is invalid for the domain.
Supplier Not found: Supplier code used invalid for the domain.
Item UM does not match Req UM: The unit of measure on the requisition is different than the unit of measure of the part number in the item master 1.4.1.
Suspended Transaction Error Examples and Explanations – Shift Production Reporting. These transactions are processed by the Materials department process owner.
Item not defined on this production line: The production line for the part is incorrect. Use Production Line Maintenance to add the item number to the production line, or enter the correct production line into the suspended transaction.
Not a Valid Downtime Code: An incorrect downtime code was used. Downtime codes are maintained in Reason Codes Maintenance.
Not a valid Employee ID: The employee ID entered does not exist in 2.7.1 Employee Maintenance.
Not a valid scrap code: The scrap code does not exist in generalized codes. Scrap codes must be approved by Corporate Quality and are entered by IT in Generalized codes under rmks field name.
Part is Obsolete: Part is marked as “OB” in the item master.
Period has been close for entity: The GL calendar for the month of posting is closed. This is maintained by the Plant Controller.
Restricted procedure for item status code I or O: This error is produced because the status of the item in the item master is either IC (for inactive part or OB for Obsolete)