This document presents the steps required for activating the Protheus x Gesplan integration, through the Carol platform.
Upon acquiring the offer internally, the provisioning flow begins.
Once the provisioning flow is finished, the customer receives the RAC credentials by e-mail (client_id and client_secret) required for running the Protheus Configuration Wizard.
The environment must be updated, following the order described in the topics below.
To start implementing the integration, you need to:
1) Check minimum requirements:
DbAccess from version 21.1.1.4
Protheus Release from 12.1.33
Lib from version 20230227
2) Apply the last Protheus continuous expedition, along with the dictionary differential through the UPDDISTR, in accordance with its release version.
3) Activate parameters in the configurator:
MV_FINTGES - Enter the content true = .T.
MV_PRJOVER - Enter the content true = .T.
Only activate parameter MV_FINTGES in integration deployment. Using the active parameter without running the configuration Wizard may cause system processing errors.
4) Run the Wizard in accordance with the steps listed in the next topic.
To start the Configuration Wizard, enter the initial program: WIZARDTF1
Click Next
Enter a user with administrator privileges and select the companies to be configured. Click Next.
Select the Gesplan product
Confirm user and password to run UPDISTR.
Fields EV_MSUID and EZ_MSUID, of type uniqueidentifier, are created.
Enter the RAC credentials received by e-mail.
In this last step, the editing control fields (S_T_A_M_P_) are created in all integration tables.
After running the Wizard, the FWTECHFINJOB Carol integration job is automatically registered in Protheus.
If the integration has data sent by Gesplan, it occurs through job FWTOTVSLINKJOB, which must be manually added to the schedule.
You must finish configuring the schedule of both jobs and start the service.
Execution Recurrence
To avoid delay when sending data to Carol, you may set the job Recurrence to 'Always active'; however, there is no rule regarding the registration of the execution recurrence. The decision concerning this matter depends on the need for the availability of these data, from the time of their generation onwards.
The greater the recurrence and companies/branches listed for execution, the greater the need for job processing resources.
Enter the configuration only in the environment currently in production.
Test databases configured with Smartlink intercepted messages sent by Gesplan the same way as the production database, causing the data to be saved to the test base, updating the status for Gesplan to integrated.
Gesplan Integration - Bank Transaction
Schedule - How to schedule the execution of routines
With the schedule running, the job FWTECHFINJOB starts sending the records to the staging tables of Carol. Every edit to any ERP record automatically updates the timestamp, in field S_T_A_M_P_, thus the job resends the full record to update the staging table.
You can activate the job logs to evaluate what is being executed and sent. Just follow the procedures described in the link below.
https://tdn.totvs.com/display/public/framework/TechFin+Debug
We recommend activating the log only when some evaluation becomes necessary, because keeping the log on may degrade performance, besides creating too many files in the rootpath of the environment.
The entities entered in the Nature register of the Bill Payable/Receivable will be used in the following fields:
Access Configurator / Database and select fields as Used:
The description of the bill currency updates the Currency Register (CTBA140) of the Management Accounting module in Updates→Registers→Accounting Currencies
Documentation on custom fields: Gesplan Integration - Sent Data and Pipelines