SAP Technical Consultant with OpenText VIM Experience

SAP Technical Consultant with OpenText VIM Experience

Location: Remote (PST Time Zone)

Duration: 6 Months plus

The Client currently uses OpenText Suite for document storage and retention, document archiving, and invoice processing. The Client implemented these products in 2016/2017 and performed upgrades in 2020 and 2023. The Client needs to upgrade its Open Text environment again to stay within current maintenance. Client use archive server and content server as an enterprise-level archiving system that integrates with several different applications (e.g. Accela, SAP, and SharePoint) and is also used directly by Client users. Client also utilize InfoFusion to do web publishing of rendition created in Content Server to our Client website.

VIM was implemented in 2016 to support a decentralized accounts payable function where invoices are entered and processed by personnel in each department. In 2022, the Client implemented functionality to centralize the accounts payable function where all invoices are processed by the Finance Department.

The Client has technically implemented this functionality but does not anticipate moving towards full centralization before the upgrade is completed. The upgrade project team will need to ensure that the upgrade works for both business processes. The Client also uses VIM to process invoices from an IDOC-based interface with an external grants management application called Fluxx

The scope of work for this task order is listed below. All resources are allowed to work remotely.

1. Vendor Invoice Management Upgrade
1. Analyze the Client’s OpenText VIM products and select upgrade levels that are 1) supported for the next 2-3 years, and 2) compatible with each other.
2. Executing the upgrade from a functional perspective in sandbox, development, quality, and production environments.
3. Mapping the list of cutover tasks/go-live plan and communicating any changes to the Client Project Manager.
4. Assist Client Basis staff with installation issues.
5. Assist Client Development staff with SPAU/SPDD analysis.
6. Performing manual post-installation steps.
7. Assist the Client Help Desk staff with building any necessary SCCM installation packages and testing on various machines.
8. Perform initial functional unit testing in the Development environment and resolve any defects.
9. Resolving any defects from the upgrade.
2. Content Server / Archive Server Upgrade
1. Analyze the Client’s OpenText products and select upgrade levels that are 1) supported for the

next 2-3 years, and 2) compatible with each other.

2. Mapping the list of cutover tasks/go-live plan and communicating any changes to the Client Project Manager.
3. Assist Client Basis staff with installation issues.
4. Assist Client Development staff with SPAU/SPDD analysis.

Minimum Requirements:

• Each resource in the team should have: Experience with at least 2 upgrade projects for their responsible components.
• Experience in SAP and/or Open Text system development lifecycle from understanding of requirements to proper design techniques, configuration, writing specifications, testing, and documentation as needed.
• Knowledge of SAP and/or Open Text best business processes. Must demonstrate a thorough understanding of SAP methodology, principles, theories, concepts, and techniques.
• Excellent oral and written communication skills. Must be able to properly communicate and document findings, proposals, solutions, and analyses as developed.

Current Environment:

ECC System:       SAP EHP8 for SAP ERP 6.0 / SP 36

NetClientaver 7.5, SP29

SAP_APPL 6.18 SP22

SAP_FIN 6.18 SP22

VIM Eco-System: Vendor Invoice Management 7.6 SP 4

Open Text Intelligent Capture 23.4 Enterprise Scan 20.4

Document Pipeline 21.2

Open Text Eco-System: Archive Center 21.2 / 22.4

Content Server 22.4

OTIC/InfoFusion 22.4

Blazon for Content Server 16 EP1 Blazon Server(rendition) 16.6.3

xECM for SAP 21.4 / 22.4

OTDS     23.1

Enterprise Connect 21.4

Enterprise Scan 21.4

Kofax Adaptor 16.4 / 25.1

*Note: For some OpenText systems mentioned above the format shown is as “current production/upgraded version”. Upgraded versions are validated in DEV and QA, with production cutover targeted for early June 2026.