ERP - Primavera v10
How do I configure ERP v10 consumption integration for Valuekeep?
Valuekeep is fully integrated with ERP v10 so that you can benefit from the features of both products. This integration is bi-directional, i.e., they share data and maintain communication with each other. To help with the operation, some base ...
Plugin V10 – Solution – Pipelines
An integration solution consists of one or several pipelines (integration flows). The solution provided as a base example contains several integration flows, which can be reused and/or customized according to the defined business processes.
Plugin V10 – Pipelines – Auditing
The PRIMAVERA V10 - Valuekeep Integrator plugin conceptually makes available through information categories, using lists, the possibility of monitoring the execution of all pipelines. This functionality allows the implementer / integrator to control ...
Plugin PRIMAVERA V10 – Overview
The PRIMAVERA V10 - Valuekeep Integrator plugin makes integration between PRIMAVERA ERP V10 and other systems possible, namely the Valuekeep solution. This plugin is designed to use the resources of the Valuekeep Integrator platform and the PRIMAVERA ...
How to download the plugin ERP Primavera V10?
The plugin PRIMAVERA V10 – Valuekeep Integration installation is performed using the PRIMAVERA Deployment Center. This option is only available for customers that have subscribed the module VK.INT – Valuekeep Integrator (see PRIMAVERA Licensing). If ...
Plugin V10 - Pipelines – Overview
The pipelines examples distributed by the plugin PRIMAVERA v10 – Valuekeep Integration, available on – <InstallPath>\VKPlugin\SAMPLES – adopt a configuration based on the methodology Reader-Mapper-Writter, as shown on the following message.
Plugin V10 – Pipelines – Reader
The readers available on the PRIMAVERA V10 – Valuekeep Integration plugin has the goal of providing the systems (PRIMAVERA ERP V10 and Valuekeep) with mechanisms that reduce the number of requests and allow the implementer/integrator to easily ...
Plugin V10 – Pipelines – Mappers
A service integration solution must be able to easily define data bidirectional transformations, from their native representation to other formats, more adequate for the process integration, such as: XML, JSON. The PRIMAVERA V10 – Valuekeep ...
Plugin V10 – Pipelines – Writer
The writers provided by the plugin use the resources of the PRIMAVERA V10 API to register (write) the data coming from a source system, meanwhile transformed according to the mapping file defined in the pipeline. The plugin provides the following ...
Plugin V10 – Pipelines – Hashing
The plugin PRIMAVERA V10 – Valuekeep Integration adopts a version control based on a hashing system. Each pipeline has a version control, that is, it has a hashing key that allows to identify if the information subset (hashset) has still not been ...
Plugin V10 – Pipelines – Lists
When integrating, the readers use the list resources with the purpose of defining and dividing the information applicable to the business process. As a business process monitoring and easy to use tool, the plugin has adopted application lists as a ...
Plugin V10 – Solutions – Schedulers
The execution frequency for a pipeline is defined using the scheduler on the pipeline configuration. The Schedulers catalog, present on the solution made available as a base example, can be customized by including new items, by using the ...
Plugin V10 – Solution – Pipelines
An integration solution is made up of one or several pipelines (integration flows). The solution made available as a base example has several integration flows, which can be reused and/or customized according to the business processes defined.
Plugin V10 – Solution – Overview
The PRIMAVERA V10 – Valuekeep Integration plugin, offers in its installation folder: <Install Path>\VKPlugin\SAMPLES\CONFIGS, an example of a solution that can be reused as a base example, and that can be customized according to the integration ...
Plugin V10 – Solution – Example
In the installation folder: <Install Path>, a file (VK3_V10_Integration.config) is provided, which can be reused as a base example when implementing an integration solution. If you want to reuse the example as a potential integration solution, you ...
Plugin V10 – Solution – Expressions
The use of Expressions when configuring a solution is frequent, due to the high number that a specific expression is applied recurrently. For example, having the solution made available as a base example, all pipelines use the API definition. The ...