OpenText VIM Invoices in SAP are Stuck in Scanned Status

There are cases where the VIM Invoice statuses are NOT updating in SAP. In this scenario, the status is stuck in “Scanned” status as viewed in /OPT/VIM_7AX8.

You can refer to the screenshot of transaction code /n/OPT/VIM_7AX8 IDH Admin Tool in SAP where the status is set to 01 or Scanned. Here, we are expecting the status to update but it seems to be stuck.

Basic Flow (High Level)

As basic overview: invoices are scanned and these are stored in a content server or ICC Server. ICC is installed and configured in the server alongside other tasks (and setups) that bring these invoice data and images to SAP.

What is ICC?

ICC in this post stands for Invoice Capture Center for SAP. Invoices are scanned here and eventually created in SAP VIM as a document. The scanned image or pdf can also be viewed in SAP.

Routine Checks

Below you will find some standard or routine checks to help solve this concern.

1. Check the SAP Jobs

Check the related OpenText VIM – SAP Jobs in transaction code SM37. Make sure all necessary jobs linking the documents from the concerned content server (example ICC Server) to the specific SAP Environment are running.

Some related jobs could be the following:

VIM Program in SAP	Notes
OA_UPLOAD_AND_LINK	Searches content / files from the content server and links them to SAP. Ensure that the file path specified in the variant coincides with the proper content server. Example: DEV Content Server is specified in DEV SAP Environment System.
/OPT/VIM_DP_TRIGGER	For DP workflow trigger and running of business rules.
OPT/VIM_STATUS_EXTR	For status update and check for Sent to OCR / Ready for OCR.
OPT/VIM_STATUS_VALD	For status update and check for Sent for Validation / Ready for Validation.
…	… <insert other jobs as needed>

2. Check the ICC Server Jobs and / or Hotspot

Go to your ICC Server or Content Server through Remote Connection where ICC Customizing is installed. Check if the Jobs or Hotspot tasks are running as expected.

Below is an example screenshot where ICC Customizing was opened through Remote Connection to ICC Server. As seen below, some tasks have been disabled when they should be in “Scheduled” state to run every N minutes.

The needed tasks should be scheduled or started.

3. Check if SQL Instance of DOKUSTAR is Running

Documents or content are stored in a database or SQL. You can quickly check if the SQL Instance of DOKUSTAR is running. The screenshot below shows that SQL was accessed.

4. Restart the ICC Server

This can be your last resort and mostly occurs for multiple stuck documents processing in the ICC Server. You can try to restart it and monitor if the processing continues.

I hope this helps. Good luck! 😊