Troubleshooting: Invoices Not Appearing in Banner

  • Updated

When an invoice is created in Unimarket (via electronic cXML or in the Invoices module), it is transmitted to Banner via an API. 

If the invoice does not appear in Banner (e.g., in FAIINVL or FAAINVE), follow this multi-step diagnostic workflow.

 

Step 1: Check Community Inbox for Integration Errors

 

Step 2: Check the Unimarket "Error_" Code

At times, errors will appear in Unimarket to define the error that occur:

  1. Navigate to the Invoices module and open the specific invoice.
  2. Look at the invoice number to see if an error appears (e.g. INXXXX (Error_10))
  3. Unimarket provides high-level diagnostic codes:
Code Meaning Common Cause
Error_10 Header Build Error The Purchase Order has not posted yet or the Vendor ID is missing in Banner.
Error_20 Header API Error Failure in the initial creation of the Banner Invoice header.
Error_30 Item/Accounting Error Invalid FOAPAL strings or referencing a closed/cancelled PO line.
Error_40 Completion API Error The invoice was created but failed the final "Complete" validation in Banner.
  1. If no error appears in Unimarket, proceed to Step 3.

 

Step 3: Reach out to the Support team

  • To review if a timeout or 500 Internal Server error generated on the backend. 
    • A 500 Internal Server Error is a generic HTTP status code indicating the server encountered an unexpected condition preventing it from fulfilling a request. Which occurs if the customer's server was temporarily down, preventing the orders from flowing into Banner.
  • If there are no timeout errors found, proceed to Step 4.

 

Step 4: Technical Diagnostics (SQL)

If the error code is vague, use SQL to view the exact response from the Banner API.

Step A: Check the Request (FZBEPRC)

Verify the message reached Banner. Search by the Unimarket Invoice ID (e.g., I0123456).

SELECT FZBEPRC_ID, FZBEPRC_STATUS, FZBEPRC_DATE_TIME 
FROM FISHRS.FZBEPRC 
WHERE FZBEPRC_CXML LIKE '%IXXXXXXX%' 
ORDER BY FZBEPRC_DATE_TIME DESC;

 

Step B: Check the API Feedback (FZRCXML)

This is the most critical table. It stores the specific error message returned by the Banner API.

SELECT FZRCXML_DOCUMENT_ID, FZRCXML_ERROR_MSG, FZRCXML_ACTIVITY_DATE 
FROM FISHRS.FZRCXML 
WHERE FZRCXML_FZBEPRC_ID = (SELECT FZBEPRC_ID FROM FISHRS.FZBEPRC WHERE FZBEPRC_CXML LIKE '%IXXXXXXX%')
ORDER BY FZRCXML_ACTIVITY_DATE DESC;

 

Step 5. Banner Form Check Incomplete Invoices (FGRIDOC)

Sometimes the invoice is in Banner but is invisible in inquiry forms because it is Incomplete.

  1. Open form FAAINVE (Invoice Entry).
  2. In the Document field, enter the Unimarket I-number.
  3. If the record loads, it means it is "Incomplete." Navigate to the Completion tab to see the specific validation error (e.g., NSF, Invalid Fund).
  4. Alternatively, run the FGRIDOC report to see all incomplete documents.

Technical Note: Following an upgrade to Oracle 19c, ensure the FISHRS user has been granted CREATE JOB permissions. Without this, the background jobs that reprocess "PO Not Posted" errors will fail to trigger.