OpenText ICC Training

Agenda:- ICC overview, jobs, settings.

Users are not able to view CC and country list in enterprise scan.

Solution:- This list is available in below path and if we do not maintain CC/country here then it will
not be visible to users.

In order to change the profile, Goto tools-> Import configuration-> Select the profile as per your
requirement.

After doing this if you do not see CC/country list then close and reopen the enterprise scan again.

For region profile, we need to add Company code in the below path:-
Format:- CC-P0-Company Name

Table related to Enterprise Scan: -/OPT/CT_IDH_HEAD

Here we can see all the data related to documents coming from Enterprise scan like scan station,
user list etc.

Scan station has a batch number (Scan Batch report you can see it) present in this table.
ICC (Invoice Capture Center):-It is used for OCR extraction for the documents coming from
document pipeline scanned through enterprise scan using the VIM process.

DP Document generation through ICC & OCR process:-

ICC Dispatcher is part of VIM and it takes the role of Integrating the OCR and VIM. OCR uses SAP as
backend to store and retrieve Invoice Image information through this Dispatcher.

Sequence Steps: -

1. Enterprise Scan calls SAP through Early Archiving Scenario.

2. Enterprise Scan deposits the image to the archive server and creates a DP Document in SAP using
function module /OPT/VIM_IF_NEW_DOC_INSERT.

This function module will insert an entry to tables /OPT/VIM_1HEAD & /OPT/VIM_HD_DP with new
DP Document number, Archive date & time, Document ID, Archive document type, Content
repository ID.

3. ICC-Extraction engine calls API(B) via a scheduled batch job on ICC side -
/OPT/VIM_IF_GET_NEW_DOC_LIST and gets new documents for processing

• Gets all the documents in "Scanned" Status along with Secure URL for Image and XML document
which will be created by ICC extraction engine.

• Updates the DP Document status to “Sent to OCR”

4. ICC– Extraction engine picks documents from step 3 and imports the corresponding images from
archive server.

5. ICC- Extraction engine Export module calls API(D) /OPT/VIM_IF_VIM_OCR_DATA_UPDATE

• Updates the status and OCR data appropriately. This API exports the data to SAP after completion
of extraction phase. Table /OPT/VIM_1EXT_H will be updated with Extracted data at this step.

• DP Document status updated with “Extraction Completed”

6. ICC- Extraction engine sends the results XML file of the exported data to the archive server using
the URL retrieved early from SAP at step 3.

• For each Exported Data to SAP corresponding Results are stored in XML file and archived back to
archive server.

7. Periodic job (program /OPT/VIM_STATUS_EXTR) runs on SAP side and picks up the DP Items with
status “Sent to OCR” and checks the time elapsed and if it exceeds the configured time, set the
status back to “Scanned”.

Maximum allowed time for Extraction will be maintained in table /OPT/VIM_RETRY using transaction
code SM30. This table contains an entry with call point “EX” for extraction.

8. Periodic job (program /OPT/VIM_DP_TRIGGER) runs on SAP side and picks up DP items with status
“Extraction Completed” and runs business rules to check validation required or not.

If validation required, sets the status to “Ready for Validation”. If it is not required, it will start DP
Workflow. --- If Validation is required then System evaluates the agents for the VALIDATOR role and
updates the SAP tables.

9. ICC-Validation engine calls API(G) - /OPT/VIM_IF _GET_VAL_DOC_LIST and gets list of documents
for validation.

• Gets all the documents in "Ready for Validation" Status

• For each DP Document, it gets the secure URL for Image and XML documents which will be used by
ICC Validation Client.

• Function module “SCMS_DOC_URL_READ” will return the URL by taking Archiving ID and Archiving
Doc ID as input.

10. ICC–Validation engine picks documents (both image and XML) for each validation document and
sends the results XML file to the archive server using the URL retrieved from SAP at step 9.

11. ICC-Validation engine calls API(I) - /OPT/VIM_IF_VIM _VIM_OCR_DATA_UPDATE

• Updates the status and OCR data appropriately. This API exports the data to SAP after completion
of validation phase. Table /OPT/VIM_1EXT_H will be updated with Validation data.

• DP Document status updated with “Validation Completed”.

12. Periodic job (program /OPT/VIM_STATUS_VALD) runs on SAP side and picks up DP items with
status “Sent for validation” and after elapsed time sets the status to “Ready for Validation”.

• Maximum allowed time for Validation will be maintained in table /OPT/VIM_RETRY using
transaction code SM30. This table contains an entry with call point “VA” for validation.

13. Periodic job (program /OPT/VIM_DP_TRIGGER) runs on SAP side and picks up DP items with
status “Validation Completed” and starts the DP Workflow.

BATCH Jobs scheduled for ICC

1) Batch program /OPT/VIM_STATUS_EXTR

This program runs in background and reads all the DP Documents with status “Sent to OCR” and
checks the elapsed time crossed the allowed time limit. Maximum allowed time for Extraction will be
maintained in table /OPT/VIM_RETRY.

This table can be maintained using transaction code SM30. Call point “EX” represents EXTRACTION.
We can also maintain the maximum number of retries allowed.

If a particular DP Document is waiting in Extraction queue for more than allowed time, batch job sets
that DP Document status to “Scanned”. Otherwise ignores that DP Document.

Selection Screen of the program is

2) Batch program /OPT/VIM_STATUS_VALD

This program runs in background and reads all the DP Documents with status “Sent to Validation”
and checks the elapsed time crossed the allowed time limit.

Validation maximum allowed time will be maintained in table /OPT/VIM_RETRY. This table can be
maintained using transaction code SM30. Call point “VA” represents VALIDATION. We can also
maintain the maximum number of retries allowed.

If a particular DP Document is waiting in Validation queue for more than allowed time, batch job sets
that DP Document status to “Ready for Validation”. Otherwise ignores that DP Document.

Selection screen for this program is

3) Batch program /OPT/VIM_DP_TRIGGER

This program runs in background and sends the DP Documents to workflow based on the validation
conditions. For Extraction Completed Documents, it checks whether validation required and if
required sends to Validation framework otherwise triggers the workflow. For Validation Completed
Documents, it triggers the workflow.

Selection Screen for this program is

In ICC Customising client:- We have Hotspots where SAP extraction link and SAP download links are
maintained.

SAP extraction link:- It is responsible for OCR extraction. Each extraction link is a separate ICC
machine and is communication to SAP through an RFC user. It can be seen on clicking the properties
after disabling the link.

RFC user should be having all the roles and is present in the SAP system in order to work properly.

Based on document types maintained, link will get the documents.

SAP download link:-It is responsible for downloading the Vendor master data/Po related data from
SAP and storing the same in SQL database.

ICC Jobs and Programs: -

/OPT/VIM_COMPCODE_DOWNLOAD:-To generate the Company code recipient file & this needs to
be added inside the ICC application that is uploaded to PRD.

Table /OPT/VIM_CFG_VER:- To check the ICC hotspot version in SAP table.

/OPT/VIM_STG_POH:- For PO data

/OPT/VIM_STG_LIF:- For Vendor data.

These two tables are updated based on the programs /OPT/IR_DL_PO_TO_STG_TABLES&

/OPT/IR_DL_VENDOR_TO_STG_TABLE
To modify settings:- Open the ICC application and Goto settings.

In order to add a new company code, we need to maintain recipient file (.CSV file generated by SAP
through above mentioned program).
After this follow below path: - Here, add company code in the script with OR condition.

Dokustarservices should be running in order to ensure proper working of ICC OCR extraction.

If extraction link has issue, you can check the logs as shown below.
General issue:- If CPU utilisation is high in PRD then there is high chances that ICC will become non
responsive.

In this case, we should stop all the hotspot services (Download as well as extraction links).

Then stop the Dokustar services.

Go to the below path and clear all the files.

Start Dokustar services then hotspot links. Now go to /OPT/VIM_7AX8 t code and reset the count for
documents present in sent to OCR status.

Please, note a point that Space on a ICC server, specially C drive should be always 50-60 GBs free.