V1M Foundation - Administration

Name which solutions are provided by VIM. Delivery Note Solution. Invoice Solution. Quotation Solution. Procure to Pay Solutions. Order to Cash Solutions.

Name which document scenarios are provided in Order to Cash Solutions. Sales Order. Invoices. Quotation. Remittance Advice. Order Confirmation.

Name which document scenarios are provided in Procure to Pay Solutions. Delivery Note. Invoices. Quotation. Remittance Advice. Order Confirmation.

What does include each of the documents scenarios provided by VIM. Preconfigured mapping rules. Enrichment rules. Business rules. User roles. User Actions.

The VIM Foundation consists of the following components. Inbound. Outbound. Analytics. User roles. Workplace.

VIM supports various input channels including scan, fax, e-mail and web services. True. False.

VIM requires an ArchiveLink-compliant SAP-certified content repository for the storage of incoming documents. True. False.

VIM also offers integration with these Opentext Solutions. Opentext RightFax Administrator for SAP Solutions. Opentext Extended ECM for SAP Solutions. Opentext Document Integrator for SAP Solutions. Opentext Document Presentment for SAP Solutions. Opentext Extended Business for SAP Solutions.

VIM supports various input formats, including paper, PDF, DOCX, IDoc and XML. True. False.

Related to Release Notes. They are updated continuously. Once they are released remains static. The latest version is available on Opentext My Support. Are only needed during an upgrade.

Release Notes describes. The software supported by the product. Important dependencies. New features. Known issues. Security issues.

Delivery model in VIM includes... Core VIM Functions and Baseline Configuration. Core VIM Functions and FIORI applications. Baseline Configuration and FIORI applications.

Baseline Configuration is... A set of pre-defined configurations that work out of the box. A set of pre-defined configurations and workflow templates that work out of the box. A multiple scenario configuration that needs to be adjusted to each customer.

Which are basic steps of each VIM workflow process. Validate metadata. Check duplicates. Apply business rules. Post for payment. Capture metadata. Scan document.

Name three one-time administration tasks in Foundation. Configuring authorization settings. Licence reporting: Opentext License Audit Report. Event Watcher. Configuring Document Pipelines. Create and configure the document types. Associate each channel to a mapping ID for a correct extraction.

When configuring authorization settings, the SAP authorization object SAP_ALL must be re-generated to apply the authorizations to this object. True. False.

Which of these authorization objects are delivered with VIM Foundation. J_6NPF_NAV to check navigation in workplace according to workplace ID. J_6NPF_ADM, which is checked in all administrative reports, transactions and programs. J_6NPF_RFC, which is checked in all RFC functions and executable programs. J_6NPF_PRC, which is checked in all procedures. J_6NPF_WTF to check work object types and nodes.

About periodic jobs, select which sentences are TRUE. The status based document handler queue is managed with the document handler job. Information Extraction Service in combination with look-up processing requires download to staging tables. Redundant temporary data is deleted with the clean-up processing. Document extraction with Information Extraction Service (IES) is handled by the IES request handler. Workflows in error are handled by the VIM Workflow Process handler job.

The Document handler job must execute the report /OTX/PF01_P_IDF_TRIGGER. True. False.

About parallel runs of Document Handler job, which sentences are TRUE. For parallel runs, use the program /OTX/PF01_P_IDF_TRIGGER_SPLIT, which can be scheduled. Parallel runs program splits inbound documents into batches according to selections and starts a background job with the document handler, for each batch. You cannot define the size of the batches and the number of jobs. The program selects the inbound documents according to their creation time, starting with the newest document. Parallel runs of the document handler do not support an event based job scheduling.

You must fill staging tables... If you use Validation Client (Validation for SAP Solutions). For any scenario of VIM for SAP Capture. For any scenario of Information Extraction Service. For any scenario with Business Center Capture. If you use Single-Click Entry plugin in SAP.

You can download the following SAP ERP databases to a central staging table: Vendor database. Customer database. Company code database. Purchase order database. Number range database.

The component that includes the programs and tables for calculating and storing the staging data is. OTBCSL00. OTBCSL01. OTBCSL02.

You can run the download to staging table program with an option "With character check" to optimize characters fields. True. False.

To run the clean up program, authorization for J_6NPF_RFC object is needed. True. False.

To run the clean up program, authorization for J_6NPF_ADM object is needed. True. False.

Regarding IES request handler job, Opentext recommends using event-based job scheduling with a delay of 10 seconds, if you are using... Intelligent Capture for SAP® Solutions. Core Capture for SAP® Solutions.

Report to execute actions related to IES request handler. /OTX/PF13_P_TRIGGER. /OPT/PF01_P_TRIGGER. /OTX/PF01_P_TRIGGER. /OPT/PF13_P_TRIGGER.

The event watcher job is only needed if Document Handler or IES Request Handler jobs use the event-based scheduling. True. False.

Which are prerequisites for pre-learning of IES profiles. A process data mapping for IES and BCC/ICC is maintained for fields that you use for pre-learning. The Document Type is active. The Document Type is assigned to IES profile. The IES profile is active. Pre-learning data has been exported from BCC/ICC.

Which sentence or sentences are TRUE regarding pre-learning. Process data mapping is different for Invoice Solution and Solutions Beyond Invoices. In Invoice Solutions, BCC/ICC mapping is done in VIM Customizing (/OPT/SPRO). In Solutions Beyond Invoices, BCC/ICC mapping is done in VIM Foundation Customizing (/OTX/PF00_IMG). In Invoice Solutions, mapping from invoice process to IES is done in VIM Customizing (/OPT/SPRO). Mapping from any Solution process to IES is done in VIM Foundation Customizing (/OTX/PF00_IMG), in Process Foundation > Data Model. You must use data model ID PS03_VIMCL to perform data mapping from the invoice process to IES. You must use data model ID CAPT_IES to perform data mapping from the Solutions Beyond Invoice process to IES.

Which are steps of the pre-learning process. A selection variant is created to define the set of documents which are used for pre-learning. A background task evaluates the selection parameter of the variant and collects key values of the relevant documents. The result set of the selection variant is reviewed, and the selection variant is set to started status. A periodically scheduled report processes the defined set of documents until all documents are processed. The result set of the selection variant is reviewed, and all documents are processed. A background task evaluates the selection parameter of the variant and collects all mapped fields of the relevant documents.

In pre-learning for BCC (Solutions Beyond Invoices), you can configure grouping for documents. True. False.

Pre-learning of Business Entity Determination (BED) is needed... When migrating an IES profile with scenario version 1 to scenario version 2. When migrating from BCC/ICC to IES profile with scenario version 1. When you create a new IES profile in scenario version 2. When migrating from BCC/ICC to IES profile with scenario version 2.

Pre-learning of IES profiles is managed from the IES Administration Work Center, in /OTX/PF03_WP transaction. True. False.

The Batch job for analytics updates analytics data for finished processes. True. False.

The Batch job for analytics updates analytics data for running processes. True. False.

The Batch job for analytics requires authorization for J_6NPF_ADM object. True. False.

Running the batch job for analytics is usually not required for finished processes, as all corresponding analytics data is automatically updated whenever a process is finished. True. False.

Collecting Inbound Analytics data is needed for data created before. BCC 16.3 SP1. BCC 16.3 SP2. BCC 16.3 SP3. BCC 16.3 SP4. BC 16.3 SP4. BC 16.3 SP3. BC 16.3 SP2. BC 16.3 SP1.

License audit for Vendor Invoice Management for SAP Solutions an ICC/IES is based on. SAP System Measurement, using transaction USMM. SAP License Measurement, using transaction ULMM. SAP System Measurement, using transaction USTM. OpenText License Measurement, using transaction /OTX/PF09_LM.

Which are prerequisites for License measurement. Customizing. Scheduling monthly batch job for aggregation. If archiving restricted to old data is used, then the archiving must be done after running the License Report. Clean up Analytics data before running the License Report.

The License Report counts the following documents: Counts all ICC/IES documents with status Extraction Completed at some point of time in the selected period. Counts all VIM documents with start date in the selected period and status in VIM workflow or completed. Counts all Solutions Beyond Invoice documents with start date in the selected period. Counts all VIM documents with start date in the selected period and status completed. Counts all ICC/IES documents with status Extraction Completed or Extraction Started at some point of time in the selected period.

Running the License Report can be done: In dialog, using /n/OTX/PF09_COUNT transaction. In background, using report /OTX/PF09_CL_LICENCING in a background job definition. In dialog, using /n/OTX/PF09_LIC transaction. In background, using report /OTX/PF09_CL_LIC_COUNT in a background job definition.

Name three regular tasks for foundation. Cleaning up search helps and web IDs. Downloading perspectives. Data archiving. Pre-learning of IES Profiles. Event Watcher.

Web IDs are automatically generated the first time an object is displayed in the Fiori Task App. True. False.

To avoid a continuous growth of table /OTX/PF62_T_ID, you must delete (clean up) older web IDs periodically. True. False.

Deleting web IDs includes the deletion of data collections that have been created for these web IDs. True. False.

When downloading perspectives, the downloaded file contains the following perspective data: Perspective settings. Layout definition. Layout texts. View settings.

IES Administration Work Center can be used for. Intelligent Capture for SAP Solutions. Core Capture for SAP Solutions.

The IES Administration Work Center does not support remote scenarios. True. False.

The IES Administration Work Center has following dedicated nodes to monitor activity: Profiles node. Extraction node. Request node. Pre-learning node. Data node.

Which action is not present in Inbound Administration work center. Restart. Change Priority. Change Status. Reject. Reset Retry Counters. Display Validation Agent. Submit Handler. Choose Bulk Action. Download IES Extraction Trace.

Which tab is not present in Inbound Administration work center Detail pane. Single-Click Entry. Document. History. Log. External Data. Attachments. Extraction Trace. Entity Candidates.

You can archive finished inbound, process, and analytics data, using the standard SAP Data Archiving functionality of the SARA transaction. True. False.

As the VIM Foundation is a basis for several scenarios, the following data archiving use cases need to be considered: Archiving of Inbound Data only. Archiving of Inbound, Process, and Analytics data for custom solutions. Archiving of Inbound, Process, and Analytics data for Solutions Beyond Invoice. Archiving of Inbound, Process, and Analytics data for Invoice Solution. Archiving of related SAP data.

Transfer of Machine Learning data from a profile to another profile on the same SAP system. Necessary steps: Copy configuration of source profile. Creating as snapshot of the source profile. Transferring snapshot data (download on source system and upload on target system). Activating the target profile with the restore snapshot option. Switch linkage of ArchiveLink document type from source profile to target profile.

Transfer of Machine Learning data for the same profile from one SAP system to another (for example, from a production to a test system). Necessary steps. Copy configuration of source profile. Creating as snapshot of the source profile. Transferring snapshot data (download on source system and upload on target system). Activating the target profile with the restore snapshot option. Switch linkage of ArchiveLink document type from source profile to target profile.

Transfer of Machine Learning data from an on-premises repository to the cloud repository. Necessary steps. Copy configuration of source profile. Creating as snapshot of source profile (on-premise connection). Transferring snapshot data (download on source system and upload on target system). Activate target profile with the restore snapshot option (cloud connection). Switch linkage of ArchiveLink document type from source profile to target profile. Creating as snapshot of source profile (cloud connection). Activate target profile with the restore snapshot option (on-premise connection).

Transfer Machine Learning data from the cloud repository to an on-premises repository. Necessary steps. Copy configuration of source profile. Creating as snapshot of source profile (on-premise connection). Transferring snapshot data (download on source system and upload on target system). Activate target profile with the restore snapshot option (cloud connection). Switch linkage of ArchiveLink document type from source profile to target profile. Creating as snapshot of source profile (cloud connection). Activate target profile with the restore snapshot option (on-premise connection).

Which are regular tasks for Business Workflow. Setting up substitutes for workflow processes. Reassigning work items belonging to another user. Administering workflows.

Which are one-time administration tasks of Invoice Solution. VIM batch jobs. Roles. Maintaining Chart of Authority. Administering the Approval Portal. Batch jobs for Inbound Configuration. License reporting: Opentext License Audit Report.

Which are one-time administration tasks of Invoice Solution. Scheduling batch jobs for data download from SAP S/4HANA for ICC integration. Scheduling batch jobs for data extraction in an IES multiple backend scenario. Using the SAP early watch service. Configuring the Mobile Approval Portal. Event Watcher. Pre-learning of IES Profiles.

Scheduling batch jobs for workflow is a One-time administration task for Invoice Solution. True. False.

Scheduling batch jobs for Invoice Life Cycle is a One-time administration task for Invoice Solution. True. False.

Scheduling batch jobs for Central Reporting is a Regular administration task for Invoice Solution. True. False.

Scheduling batch jobs for Central Reporting is a One-time administration task for Invoice Solution. True. False.

Scheduling batch jobs for VIM Invoice Workplace is a One-time administration task for Invoice Solution. True. False.

Scheduling batch jobs for VIM Invoice Workplace is a Regular administration task for Invoice Solution. True. False.

Name three VIM batch jobs to be scheduled as a One-time administration task for Invoice Solution. Batch job for KPI Dashboard. Batch job for Ariba network. Batch job for SAP Netweaver BW. Batch job for Document Inbound. Batch job for Chart of Authority. Batch job for VIM Analytics.