Sage X3

Version 12.0.23
Installation Guide

August 2020
Pre-requisites
Ensure you have a verified backup of your Sage X3 system.
Trained knowledge of the installation process is required.
If you have not been trained or require assistance installing, please contact a Sage Project
Manager or a Sage Business Partner to receive a quote on services.

Update your Sage X3 to the level compliant with this patch set.
Verify your current version before proceeding. Sage X3 v12.0.19 and below are not
cumulative and must be applied in sequential order. Sage X3 v12.0.20 and higher are
cumulative patch.

2
 X3 Version 12.0.23
Note
This patch is a cumulative patch for version V12.0.20 and higher. The minimum
version required to apply this patch is V12.0.19.
• To install the patch: This cumulative patch will update your solution to the current patch in
a single step.
• To install the technical components and perform manual actions: Check the previous
releases documents. Depending on your current version, you may need to install other
components or perform other manual actions to complete this update.
See the previous documents in the PreviousReleases subdirectory.

Installation of mandatory technical components

Configuration console
Console_2.47.0.exe file
• Download the file.
• Unzip the file and follow the instructions provided in the file
named CONSOLE_2.47.0_ENG.htm or CONSOLE_2.47.0_FRA.htm.

Adxadmin administration server

Adxadmin_93.1.13.exe file
• Download the file.
• Unzip the file and follow the instructions provided in the file
named ADXADMIN_93.1.13_ENG.htm or ADXADMIN_93.1.13_FRA.htm.

Process server
Runtime_93.1.13.exe file
• Download the file.
• Unzip the file and follow the instructions provided in the file
named RUNTIME_93.1.13_ENG.htm or RUNTIME_93.1.13_FRA.htm.

Syracuse server
SyracuseServer_12.8.0.exe file
• Download the file.
• Unzip the file and follow the instructions provided in the file
named SYRACUSESERVER_12.8.0_ENG.htm or SYRACUSESERVER_12.8.0_FRA.htm.

3
 MongoDB
Mongodb_4.0.18.exe file
• Download the file.
• Unzip the file and follow the instructions in the file named MONGODB_4.0.18_ENG.htm
or MONGODB_4.0.18_FRA.htm.
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.

Installation of the following technical component

Production Scheduler
• New installation: Download the SafeX3ProductionScheduler-6.0.2014.zip file.
Unzip the file and follow the instructions in the file named SafeX3ProductionScheduler-
6.0.2014_ENG.htm.
• Update: Download the PlannerOne.SAGE.6.0.2014.zip file and refer to the installation
documentation.

Installation of recommended technical components

Print server
PrintServer_2.20.0.exe file
• Download the file.
• Unzip the file and follow the instructions provided in the file
named PRINTSERVER_2.20.0_ENG.htm or PRINTSERVER_2.20.0_FRA.htm.

VT Webserver
VTWebServer_2.38.10.exe file
• Download the file.
• Unzip the file and follow the instructions provided in the file
named VTWEBSERVER_2.38.10_ENG.htm or VTWEBSERVER_2.38.10_FRA.htm.
Installation prerequisites on Linux Platform:

4
 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:
• First, install a new, separate instance of the VT Server 2.38 on the server.
• Then, update the existing VT Server to 2.38.
• Then, uninstall the new instance.
The update process is planned to be improved in a future release.

Technical manual update (Oracle database 12.1)

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:
• Launch a system connection with sqlplus: rlwrap sqlplus system/...
• Modify the system by changing the spfile init file: alter system set
deferred_segment_creation=FALSE scope=spfile.
• Restart the database.

Installation of the patch

x3-patch-12.0.23.exe 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

Manual actions only for Sage X3 (not Sage X3 HR &

Payroll)
Revenue recognition
• 2 new automatic journals are delivered*: RRCEA and RRCIR*, to generate revenue
recognition journal entries for the expense part.
• Existing RRCSA and RRCII automatic journals have also been updated: Description at the
header and line level. In the grid line, line 27, each description formula has also been
updated with a new text number from local menu 174 to better fit the context.
• New default dimensions are provided: RRCEA, RRCSA, RRCII and RRCIR. They are
linked to related automatic journals.

5
• 4 new accounting code lines are delivered at Project type level, to default the debit and
credit accounts for the expense lines, from line 7 to line 10:
• Revenue recognition expense accruals
• Revenue recognition deferred expenses
• Expense account for goods/service provisions
• Unbilled account payable
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.

For users of the MTC automatic journal (automatic matching)

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:
• For MTC automatic journal the new formula is:
(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.

For users of VIRINT03 - Bank file definition, function GESTFB

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.

6
 Required modification:
• If the VIRINT03 X3 bank file is used as delivered, you can integrate the patch. Once
integrated, delete the last line of the Detail record type. From the 67 lines, you now have 66
lines.
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 the VIRINT03 X3 bank file has been customized, do not integrate the patch. Identify
the <InstdAmt> tag.
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.

Sequence number "PTFNL" (final number) for POR legislation

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.

7
 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.

Documents
Readme files
• For technical components: Readme-Components-ENG-12.0.23.txt
• For the application patch: Readme-X3-X3HR-ENG-12.0.23.txt