The patch is a cumulative patch for version V12.0.20 and higher. The minimum version required to apply this patch is V12.0.19.
File Console_2.46.0.zip
File Adxadmin_92.2.87.zip
File Runtime_92.2.87.zip
File SyracuseServer_12.7.0.zip
File PrintServer_2.19.0.zip
File SafeX3V2_WebServices237.zip
If your V12 solution has already been installed with version 12.1 of the Oracle database, you have to manually update it according to the following process:
File x3-patch-12.0.22.zip for Sage X3; File x3hr-patch-12.0.22.zip for Sage X3 HR & Payroll.
The patch must be updated from the Updates function of the Syracuse server (Administration > Utilities > Update > Updates).
The zip file contains:
- DELIVERY: for externalized resources
- DIVPAT_Pxx: for presettings (Pxx related to the patch)
- FILES: for standard patches
- INDPAT_Pxx: for additional translations (Pxx related to the patch)
- LAN: for standard patch translations except FRA-ENG
In preparation for the introduction of the Swiss QR-bill (on the 6/30/20), a new bank file definition, ISO3QRC, has been made available in the Bank file definition function (GESTFB) as part of this update.
The ISO3QRC bank file definition allows you to create credit transfers according to the Swiss Payment Standards for the following types of payment:
This bank file definition can be used as a replacement for the current ISO3 bank file definition.
Required modification after patch installation:
In the Payment entry type function (GESTPY), modify any payment entry type currently used for Swiss ISO3 payments (SWI3 by default) as follows:
Steps section, Deposit/Remittances block, Electronic medium field: replace the current value ISO3 by ISO3QRC.
You can continue to use the ISO3 bank file definition until the 6/30/20.
In the Time entry posting function (PTELABPOS), the project code is not necessary on line 2 (Payroll clearing account) of the created journal. Line 2 of the PTE automatic journal has been updated by removing the formula defined against the Project field.
Once the patch list has been integrated, to install this fix on your folder, you have to manually copy the PTE automatic journal from the parent folder to your application folder using the Copy action in the Automatic journals function (GESGAU).
A new EDI pre-setting has been created (CIUS-PT).
To finalize the setup, you must create a class (GESACLA) and a representation (GESASW) by respectively duplicating the CHORUSV and CHORUS codes.
After these duplications, you must change the representation value in the EDI message mapping (EDIMSG) related to the new representation.
The next step is to duplicate or create a new EDI XML file (EDIXMLFIL) using the CIUS-PT file delivered as a standard example. This step depends on the need of each customer (field choice, source fields, etc.).