1535 PESChanges
Introduction
This document describes the data migration process for the deprecated PESChanges features, which used to display a changes log in your vendor bank account forms:
To see vendor / bank account changes, please use our vendor history, configurable in Parameters, available in all Eftsure menus, and as a data entity for audit purposes.
These features will be deprecated in v1535.
Please ensure your end users have access to vendor history if needed
Upgrade Error
During the standard upgrade, a new batch will be spawned and fail until PESChanges upgrade completes successfully:
The batch will fail will the following error, alerting the key user to perform the update:
A Upgrade PESChanges button is available to help alongside the warning description. Click Upgrade PESChanges to get to the matching data upgrade batch.
Once the upgrade has completed, the version update script will be cleared of all warnings and actions.
Our out of the box upgrade framework is used for all upgrades including this process. It will generate batches in the Eftsure upgrade monitoring category that can be monitored directly in Workspace > Admin > Upgrades > Batches (and Details).
The upgrade is considered successful once all upgrade tasks have completed successfully.
If an error can't be resolved:
Check with key user,
Try to manually edit the bank account causing issue before retrying
Select the failing batch and hit the support icon as per the image below:
Vendor History configuration
To perform the optional data migration of PESChanges into Vendor History, we recommend enabling vendor history first:
Other parameters are optional and recommended to be turned off.
If Vendor History is turned off during the Upgrade, the deprecated data will be lost.
Vendor History
When enabled, the Vendor History is available:
In Eftsure workspace > Dashboard > Vendors > History to access data for all vendor changes.
In our Eftsure menu for any specific vendor or bank account:
Data Upgrade
For environments with vendor history enabled, the data should already be available in the vendor history, no need for data migration, you can run the data migration job to clear data without migration of PESChanges data into Vendor History.
For environments without vendor history configured, if you wish to use a similar process, we recommend migrating and clearing data.
First turn on Vendor History, then run the following:
Parameters
The following parameters are available in the upgrade job:
Enable vendor history:
Turn on Vendor History with default settings (Callstack disabled)
This option is only available if vendor history is disabled
Entities:
This batch needs to run once per enabled legal entity, once per data sharing policy (if cross company data sharing).
We recommend running each batches one after another to avoid performance issues, deadlock and conflicts. Using the Entities combobox, either schedule X batches with current entity or schedule 1 batch will all enabled entities.
Migrate data from PESChanges:
Use deprecated history from VendBankAccount.PESChanges to generate upgraded data compatible with vendor history.
Clear PESChanges after upgrade:
Clear VendBankAccount.PESChanges after processing records. This action is irreversible.
Monitoring progress
The new batch(es) for this upgrade will appear in Workspace > Admin > Upgrades > Batches.
Monitor all infolog messages and ensure each batch completes. Batches can fail due to deadlocks or conflicts and may require massaging.
Depending on the amount of data, this process can take a long time.
Completing upgrade
Once all obsolete data has been cleared, you can now retry the upgrade batch which should complete successfully.
You can restart the failed batch using the status button to set batch status to Waiting.
Once the upgrade batch job for version 1535 has completed, you can proceed with the next upgrade task.
Demonstration
The following sample run demonstrates how to run this process correctly. It starts after the configuration of cross company data sharing and enabling vendor history.
This scenario has the following legal entities : PNC, PNT, PUK, PDS, PNS, where PUK, PDS, PNS are shared via CCDS Policy 'Vendor Master Data'. The data fix should therefore run in PNC, PNT and in one of PUK, PDS, PNS
For all runs, we'll be running with all default options enabled.
First, the standard upgrade fails and provides a link to run the upgrade in each legal entity:
Per entity
We run the upgrade in all entities, one after another:
In PUK:
In PNC:
In PNT:
Once all upgrades have completed, the last batch confirms all enabled legal entities have been processed successfully.
Return to the failed upgrade batch, change status back to Waiting:
After completion, a second batch job history completes successfully and confirms all upgrades have completed successfully.
For all enabled entities:
In this second example, we'll run all enabled legal entities at once, which will take longer if more than one entity is concerned.
This job will run all enabled legal entities and confirm completion.
Return to the failed upgrade batch, change status back to Waiting:
After completion, a second batch job history completes successfully and confirms all upgrades have completed successfully.
