OpenText VIM 7.6 SP3 for SAP ECC

[Joan_lee]

Hi All,

Currently we are upgrading from OpenText Vendor Invoice Management 7.0 all the way to OpenText Vendor Invoice Management 7.6 SP3 for SAP ECC, 
We are facing issue where the Status for document posted through VIM Workplace are stuck as "Indexed" in /n/opt/vim_va2 (New VIM Analytics) while the status in VIM_1HEAD table and Old VIM Analytics /n/opt/vim_analytics are correctly showing Posted.
Are there any setting or config required for /n/opt/vim_va2 so that it will update accordingly?
We are unable to get the old data from /n/opt/vim_analytics to show up in /n/opt/vim_va2 as well

[Divyesh_Mistry]

Hello Joan,

When VIM Workplace (Vendor Invoice Management by OpenText in SAP) shows documents as "Indexed" and they appear stuck in that status (e.g., under /n/opt/vim_va2), it typically means the documents have been processed by ICC (Invoice Capture Center or OCR) and indexed, but haven't moved to the next stage of processing in VIM.

Common Reasons for "Indexed" Status:

1. VIM Workflow not triggered properly
2. DP document not created
3. Error in configuration or rules (e.g., missing vendor, PO match issue)
4. Workflows are stuck due to technical or process issues
5. Background jobs not running or failing

Troubleshooting Steps:
1. Check Logs and Status
Go to /n/opt/vim_admin > Error Logs

Or use /n/opt/vim_analytics to analyze by status

Identify error messages for the documents stuck in "Indexed"

2. Check if DP Document was Created
Go to /n/opt/vim_va2

Select document > Check if there's a DP Number

If missing: the workflow or rule processing step might have failed

3. Check Background Jobs
Ensure these jobs are running:

/n/spro > VIM Customizing > Schedule Background Jobs

/PTGWFI/WORKFLOW_EXECUTE

/PTGWFI/FETCH_DOCS_FROM_ICC

/PTGWFI/START_WORKFLOW

You can also check via /n/smgr or /n/sm37:

Look for job failures or long delays

4. Validate Vendor/PO Mapping
If documents are not matched to vendor/PO, they may remain in "Indexed"

Check whether the vendor was correctly recognized and exists in SAP

Use VIM tables: /n/se16 > /OPT/VIM_1HEAD, Z tables, or custom ones for OCR data

5. Restart Workflow (If Safe)
If the cause is corrected, you can try re-triggering workflow manually:

In /n/opt/vim_va2: open the document

Actions > Start Workflow (or similar option)

This should resolve your issue.

If you find my response useful, I kindly request you to award kudos as a small gesture. This motivates me to serve you better.

Appreciate your feedback.

Thanks,

Divyesh

[Joan_lee]

Hi Divyesh,

[Joan_lee]

Hi Divyesh,
1. Check Logs
Reply: History and Workflow log is showing the VIM Document is indeed Posted and Workflow Completed

2. Check if DP Document was Created
Reply: Created and Posted

3. Check Background Jobs Ensure these jobs are running:
/n/spro > VIM Customizing > Schedule Background Jobs
/PTGWFI/WORKFLOW_EXECUTE
/PTGWFI/FETCH_DOCS_FROM_ICC
/PTGWFI/START_WORKFLOW
Reply: Program above does not exist

4. Validate Vendor/PO Mapping If documents are not matched to vendor/PO, they may remain in "Indexed" 
Reply: Document is actually posted correctly, just the VIM analytics (New VAN) status are remain Indexed, but if we are checking from /n/opt/vim_analytics it show correct status of Posted

5. Restart Workflow (If Safe) 
Reply: Workflow has completed and posted