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 integration examples are available. 

Below, we explain how to configure the integration of material consumption documents from ERP v10 to Valuekeep. 

Installation prerequisites

1. Have the Valuekeep license for the Valuekeep Integrator add-on and ERP v10;
2. Add the VK.Int module to the ERP v10 license.

Configurations in Cegid ERP v10

To configure the data to be integrated from ERP v10 into Valuekeep, it is necessary to create the lists in ERP v10. If you want to integrate the documents created in ERP v10 into Valuekeep, you must create a list of which documents and their corresponding fields you want to be integrated.

In this scenario, two queries are available in the integrator folder \VKPlugin\SAMPLES\V10LISTS\PRIMAVERA10_VALUEKEEP3 to create the two lists required. Before copying the lists, you must create the user fields (CDU) in ERP v10 and the custom attributes in Cegid Valuekeep.

Create lists in ERP v10

V10_VK3_CONSUMPTIONS_1

1. This list allows you to obtain all the necessary fields for creating a consumption in Valuekeep and is available in the VKPlugin\SAMPLES\V10LISTS\PRIMAVERA10_VALUEKEEP3\V10_VK3_CONSUMPTIONS_1.sql folder. 
2. All fields are mapped in the Mapper file which is represented in the configuration by: MappingFile  = VKPlugin\MAPPERS\PRIMAVERA10_VALUEKEEP3\V10_VK3_CONSUMPTIONS_1.json

V10_VK3_CONSUMPTIONS_3

1. This list allows you to obtain the Money-type fields to update in Valuekeep and is available in the VKPlugin\SAMPLES\V10LISTS\PRIMAVERA10_VALUEKEEP3\V10_VK3_CONSUMPTIONS_3.sql folder
2. All fields are mapped in the Mapper file which is represented in the configuration by: MappingFile = VKPlugin\MAPPERS\PRIMAVERA10_VALUEKEEP3\V10_VK3_CONSUMPTIONS_3.json

Create User Fields

 In the cabecInternos and linhasInternos tables (tables where the information on the documents to be integrated is registered) you must create the following user fields:

CabecInternos

1. CDU_SourceHash: configured with the Varchar (100) type and the false being visible;
2. CCDU_TargetHash: configured with the Varchar (100) type and the false being visible;
3. CDU_IsSync: configured with the Bit type (the false being the default value) and the false being visible;
4. CDU_Funcionario: configured with the Varchar (100) type, and the true being visible for manual filling in ERP v10;
5. CDU_OrdemTrabalho: configured with the Varchar (100) type, and the true being visible for manual filling in ERP v10.

LinhasInternos

1. CDU_IdLinhaVK: configured with the Varchar (100) type and the false being visible;
2. CDU_Localizacao: configured with the Varchar (100) type, and the true being visible for manual filling in ERP v10;
3. CDU_Equipamento:  configured with the Varchar (100) type, and the true being visible for manual filling in ERP v10;
4. CDU_Ferramenta: configured with the Varchar (100) type, and the true being visible for manual filling in ERP v10;
5. CDU_Rota: configured with the Varchar (100) type, and the true being visible for manual filling in ERP v10. It is necessary to indicate the Route and the route asset in the internal document;
6. CDU_SourceHash: configured with the Varchar (100) type and the false being visible;
7. CCDU_TargetHash: configured with the Varchar (100) type and the false being visible;
8. CDU_IsSync: configured with the Bit type (the false being the default value) and the false being visible.

Configurations in Valuekeep 

After creating consumption documents, you can change them in ERP v10, since the integrator detects the information change through the fields described below.

To add the fields, follow these steps:

1. Make sure the following fields are configured in the work order consumption list;
2. Go to Work | Explore Costs | Consumptions;
3. Click on the Manage Custom Attributes button;
4. Add the attributes relating to the Work Order Consumption:
1. SourceHash: configured with the Text type and the false being visible;
2. TargetHash: configured with the Text type and the false being visible;
3. IsSync: configured with the Boolean type and the false being visible;
5. Add the attributes relating to the Work Order Consumption line:
1. ERPIdCabec: corresponds to the ERP v10 internal document ID, which must be configured with the Text type and the false be visible;
2. ERPIdLinha: corresponds to the ERP v10 internal document consumption line ID, which must be configured with the Text type and the false be visible;
6. Go to Workshops and Employees | Employees | Map Employee;
7. Create an employee (e.g., IMPORTER_0004) and in the username (user email) enter the following text: application-user::valuekeep-importer.
8. Click on Save and New.

The employee defined in step 7 will be responsible for the integration. So, whenever you create the internal document in ERP v10, you must indicate that employee in the header user field. Alternatively, the employee's name can be fixed in the V10_VK3_CONSUMPTIONS_1.json configuration file, for example: { "Field": "employee", "Handlers": { "Mapping": [  {  "Field": "Default" } ], "DefaultValue": "IMPORTER_0004", "IgnoreOnUpdate": true } } .   

Configurations in Valuekeep Integrator 

After carrying out the necessary configurations in ERP v10 and Valuekeep, you must carry out the following configurations in the integrator:

Step 1: Configure Pipelines

1. Go to the folder where the integrator is installed and then to the VKPlugin\SAMPLES\CONFIGS folder;
2. Open the VK3_V10_Integration.config file;
3. Copy the V10_VK3_CONSUMPTIONS_1, V10_VK3_CONSUMPTIONS_2 and V10_VK3_CONSUMPTIONS_3 pipelines to the Integration.config file in the following order:
1. V10_VK3_CONSUMPTIONS_1: contains the header information;
2. VK3_V10_CONSUMPTIONS_2: contains the details information;
3. V10_VK3_CONSUMPTIONS_3: contains the information for updating prices.

The three pipelines in this example must be executed in the following sequence:

        <Handler Id="h1"  Order="1" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=V10_VK3_CONSUMPTIONS_1"/>

        <Handler Id="h2"  Order="2" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=V10_VK3_CONSUMPTIONS_2"/>

        <Handler Id="h3"  Order="3" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=V10_VK3_CONSUMPTIONS_3"/>   

...    

And then the remaining pipelines concerning internal documents.

If there are more pipelines concerning internal documents, they should all be executed in the same Handler by sequence, for example:

 <Pipeline Id="VK3_V10_REPORTS" Scheduler="Default" Active="false" >

      <Handlers>

        <Handler Id="h1"  Order="1" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=VK3_V10_LABORS"/>

        <Handler Id="h2"  Order="2" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=V10_VK3_SYNC_MO_INFO"/>

        <Handler Id="h3"  Order="3" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=VK3_V10_MISC_COSTS"/>

        <Handler Id="h4"  Order="4" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=V10_VK3_SYNC_OC_INFO"/>

        <Handler Id="h5"  Order="5" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=V10_VK3_CONSUMPTIONS_1"/>

        <Handler Id="h6"  Order="6" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=V10_VK3_CONSUMPTIONS_2"/>

        <Handler Id="h7"  Order="7" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=V10_VK3_CONSUMPTIONS_3"/>        

        <Handler Id="h8"  Order="8" Type="Valuekeep.Integrator.Handlers.PipelineHandler"   ConfigStr="PipelineId=VK3_V10_REQUISITIONS"/>

      </Handlers>

    </Pipeline>

 Step 2: Configure Mappers

You should copy the sample files distributed in the following folders:

1.  VKPlugin\SAMPLES\MAPPERS\PRIMAVERA10_VALUEKEEP3 
1. Copy the V10_VK3_CONSUMPTIONS_1.json and V10_VK3_CONSUMPTIONS_3.json files;
2. Paste the files in the VKPlugin\MAPPERS\PRIMAVERA10_VALUEKEEP folder;
3. Change the document type for the one used in ERP.
2. VKPlugin\SAMPLES\MAPPERS\VALUEKEEP3_PRIMAVERA10
1. Copy the V10_VK3_CONSUMPTIONS_2.json file;
2. Paste the file in the VKPlugin\MAPPERS\VALUEKEEP3_PRIMAVERA10 folder.

Step 3: Configure Hashsets

You should copy the sample files distributed in the following folders:

1.  VKPlugin\SAMPLES\HASHSETS\PRIMAVERA10_VALUEKEEP3 
1. Copy the V10_VK3_CONSUMPTIONS_1.json and V10_VK3_CONSUMPTIONS_3.json files;
2. Paste the files in the VKPlugin\HASHSETS\PRIMAVERA10_VALUEKEEP folder
2. VKPlugin\SAMPLES\HASHSETS\VALUEKEEP3_PRIMAVERA10
1. Copy the V10_VK3_CONSUMPTIONS_2.json file;
2. Paste the file in the VKPlugin\SAMPLES\HASHSETS\VALUEKEEP3_PRIMAVERA10 folder.