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.
Console_2.47.0.zip file
Adxadmin_93.1.13.zip file
Runtime_93.1.13.zip file
SyracuseServer_12.8.0.zip file
Mongodb_4.0.18.zip file
Note:
The Sage X3 platform is compatible with MongoDB 4.0. If you are using a previous version of MongoDB, you need to update it.
In order to install the MongoDB 4.0 upgrade, MongoDB 3.6 must be running.
You need to check your MongoDB version and update it to version 3.6 if necessary.
Note that if you use an Oracle JAVA platform, prerequisites have evolved.
Please refer to the How-to-upgrade-to-Mongodb-4.0 documentation for more information.
For an update, version 6.0.2014 installation is mandatory
PrintServer_2.20.0.zip file
VTWebServer_2.38.10.zip file
Installation prerequisites on Linux Platform:
1 - The server where VT Server 2.38 is installed MUST have an Internet access.
2 - In case you are updating an existing VT (ADC) server, you MUST follow this specific procedure:
The update process is planned to be improved in a future release.
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:
x3-patch-12.0.23.zip file for Sage X3; x3hr-patch-12.0.23.zip file 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
These automatic journals and default dimensions are available in the X3 parent folder and must be manually copied to your production folder.
Concerning the existing automatic journals (RRCSA & RRCII), before copying them manually to the X3 operating folder from the Automatic journals function (GESGAU), start the Automatic document comparison function (CMPGAU) to identify your variances.
The MTC automatic journal has been updated on the header.
In the context of a matching document (LETTRAGE), the new formula allows documents to be created in temporary status for the Portuguese legislation, using the common method based on the FRADGI general parameter.
In the Formula block of the General section, the Status field of the automatic journals has been modified as follows:
(func AFNC.PARAM("FRADGI",[F:MTU]FCY)="2")*2 + (func AFNC.PARAM("FRADGI",[F:MTU]FCY)<>"2")
These automatic journals are integrated into the X3 parent folder only.
Before copying them manually to the X3 operating folder from the Automatic journals function (GESGAU), start the Automatic document comparison function (CMPGAU) to identify your variances.
The VIRINT03 bank file has been updated at the “Detail” record type level, to delete a carriage return in the <InstdAmt> tag.
The <InstdAmt> tag formula has been modified as follows:
func FICMAG.SET_PARAM_VALUE ([F:PYH]CUR,[F:PYH]AMTCUR,":")
The bank file update is managed through the WX_12_0_23_TFB_VIRINT03.dat maintenance, located in the dedicated PATCH directory.
It is not automatically integrated. If required, integration must be performed manually using the Patch integration function (PATCH) after the upgrade of this patch/version.
Required modification:
The patch has concatenated the <InstdAmt> tag lines (initially split into 2 lines: number 7 and 8) and it has updated the formula as shown previously.
If split into 2 lines, add the end separator </InstdAmt> to the line with the start separator <InstdAmt Ccy="$1$">. Delete the initial line with </InstdAmt> end separator. The <InstdAmt> tag should be on a single line. Then, update the formula with the previous FUNC.
For users of Portuguese companies, a new sequence number structure (GESANM) is delivered, code "PTFNL".
This sequence number has been designed to control the document sequentially, using the final field number in the general ledger entries.
It is defined as follows:
Company with 3 digits
Complement with 6 digits
Month with 2 digits
Year with 2 digits
Constant with 1 digit
Sequence number with 6 digits
This sequence number must be defined at "Company" and "Monthly" levels.
The "Chronological control" and "Reset to zero" options must also be active.
This configuration can truncate the company because we are only using 3 digits for the component type code.
If the user has a maximum of 9,999 monthly documents for each entry, they can increase the company to 5 digits and reduce the sequence number to 4.
In GESTCA, this sequence number is assigned to the “Financials” module and the “POR” legislation.
It will be applied to the "Final Number" document type line.