Patch Information Note 12.0.29
Note
This patch is a cumulative patch for version V12.0.20 and above. 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 documents from the previous releases using the Index or Previous/Next links. Depending on your current version, you may need to install other components or perform other manual actions to complete this update.
Installation of mandatory technical components
Configuration console
Console_2.53.0.zip file
- Download the file.
- Unzip the file and follow the instructions provided in the file named CONSOLE_2.53.0_ENG.htm or CONSOLE_2.53.0_FRA.htm.
Important: The setup file must be executed locally. Make sure to download the setup file locally to the workstation where the Console is installed or updated. Otherwise, a blocking error message can be triggered during the setup process, but the installation will still be completed.
Adxadmin administration server
Adxadmin_94.1.15.zip file
- Download the file.
- Unzip the file and follow the instructions provided in the file named ADXADMIN_94.1.15_ENG.htm or ADXADMIN_94.1.15_FRA.htm.
Process server
Runtime_94.1.15.zip file
- Download the file.
- Unzip the file and follow the instructions provided in the file named RUNTIME_94.1.15_ENG.htm or RUNTIME_94.1.15_FRA.htm.
Syracuse server
SyracuseServer_12.14.0.zip file
- Download the file.
- Unzip the file and follow the instructions provided in the file named SYRACUSESERVER_12.14.0_ENG.htm or SYRACUSESERVER_12.14.0_FRA.htm.
Print server
Print server_2.25.0.zip file
- Download the file.
- Unzip the file and follow the instructions provided in the file named PRINTSERVER_2.25.0_ENG.htm or PRINTSERVER_2.25.0_FRA.htm.
Important: The setup file must be executed locally. Make sure to download the setup file locally to the workstation where the Console is installed or updated. Otherwise, a blocking error message can be triggered during the setup process, but the installation will still be completed.
Installation of recommended technical components
VT Web server
VTWebServer_2.40.0.zip file
- Download the file.
- Unzip the file and follow the instructions provided in the file named VTWEBSERVER_2.40.0_ENG.htm or VTWEBSERVER_2.40.0_FRA.htm.
Elasticsearch
You can use Elasticsearch 7.16.2 with Sage X3.
Note: Although Sage X3 remains compatible with previous releases, Sage strongly recommends that you install this latest version.
MongoDB
Mongodb_4.4.10.zip file
- Download the file.
- Unzip the file and follow the instructions provided in the file named MONGODB_4.4.10_ENG.htm or MONGODB_4.4.10_FRA.htm.
Notes:
- The Sage X3 platform is compatible with MongoDB 4.4. If you are using a previous version of MongoDB, Sage strongly recommends that you upgrade it.
- To install the MongoDB 4.4 upgrade, MongoDB 4.2 must be running. You need to check your MongoDB version and update it to version 4.2, if necessary.
- If you're using an Oracle JAVA platform, please note that the prerequisites have evolved. Refer to the How to upgrade to MongoDB 4.4 documentation for more information.
Installation of other technical components
X3 Services (only for Sage X3, not Sage X3 HR & Payroll)
X3 Services is a new component used to manage Automatic Data Collection.
x3-services-14.0.38-win.zip file
Automated Test Platform
The Automated Test Platform is a technical licensed component used to create automated tests for Sage X3 products using Cucumber tools.
atp-2.6.0-win.zip file
- Download the file.
- Unzip the file and follow the instructions provided in the file named ATP_2.6.0_ENG.htm or ATP_2.6.0_FRA.htm.
Technical manual update (Oracle database 12.1)
If your V12 solution has already been installed with version 12.1 of the Oracle database, check the value of the deferred_segment_creation parameter:
- Enter the following command: show parameter deferred_segment_creation.
If the value is true, you have to manually set it to false:
- 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.29.zip file for Sage X3; x3hr-patch-12.0.29.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)
Rejected SEPA Direct Debit transactions: New requirements from CFONB
What are these new requirements?
From November 20, 2021, new information is required in the SDD file when it contains a payment representing a rejected SDD transaction that you are trying to recover.
The required information is the following:
- The Category Purpose XML tag must contain the new RPRE ISO code (“Represented” for presented again).
- And when it does, the Unstructured XML tag for the Remittance Information must start with “REPRESENTATION”.
This information is required in the following context:
- The direct debit relates to a B2C transaction, where the debtor is a final customer.
- The transaction is made on the French national territory.
- The original SDD transaction has been rejected and returned due to insufficient funds (AM04 reason code for an SDD R-transaction).
- The new payment is the very same as the one that has been rejected (same debtor, same amount, same UMR, same creditor, same debtor account).
- This new payment is issued within 30 calendar days after the Requested collection date for the original direct debit.
How to manage these requirements in Sage X3?
When creating an SDD transaction in this context, you need to:
- Manually enter the new RPRE code in the Payment nature field ([F:PYH]EPANATPAY) in the Payment/Receipt entry function (GESPAY), when relevant. This value is included in the Category Purpose XML tag.
- Make sure that the related remittance (GESFRM) only contains payments with the RPRE payment nature since the Category Purpose XML tag is included in the Header record type of the SDD bank file definition (GESTFB).
What does this mean at the setup level?
To meet these new requirements, the FRSDD02 file definition (GESTFB) has been introduced as part of this update.
This bank file definition can be used instead of the current SDD02 bank file definition.
After the patch installation, you need to:
- In the Payment entry transaction function (GESTPY), change any payment transaction used for French SDD payments and replace SDD02 with FRSDD02 in the SEPA file field in the Steps.
- Add the RPRE value to the list of existing SEPA payment natures in miscellaneous table 313.
Inquiry screens for the Cost structure
Important notes on inquiry screens for customers using the Sage X3 Cost structure
The following inquiry codes are impacted:
- STI - Cost structure-products
- STP - Cost structure-supplier prod.
- STG - Cost structure-product cat.
For the inquiry codes above, the STD and ALL screen codes were missing for customers using upgraded folders. They are now available using the WX_12_0_29_GTC_STI-STP-STG.dat patch file, located in the dedicated PATCH directory:
- Before patching, make sure that your folder doesn't already contain the STD and ALL screen codes for the inquiry codes above. Otherwise, the patch will erase your settings.
- If they're not in your folder, you can install this patch manually using the Patch integration function (PATCH) after upgrading to this current patch/version.
- Don’t forget to perform a validation of these inquiry codes using the Validation action in the Setup > General parameters > Inquiry screens function (GESGTC).
- Customers with a new application folder are not impacted.
Automatic journals PRINC and ACCBP updated for payment posting
Setup > Financials > Accounting interface > Automatic journals (GESGAU)
The lines below have been updated in the PRINC and ACCBP automatic journals.
PRINC automatic journal:
- Line 51, Formulas section:
Syntaxes ‘[F:PYD]DSP’, ‘[F:PYA]AMTANA’ and ‘[F:PYA]QTYANA’ have been added to the relevant fields.
- Line 8, General section, Accounting codes table:
2 lines have been added to use the Drafts to pay on G & S account defined for the supplier accounting code. These lines are triggered when the Purchase type entered on the payment is set to Services.
- Line 18, General section, Accounting codes table:
1 line has been added to use the Drafts to pay on G & S account defined for the supplier accounting code. This line is triggered when the Purchase type entered on the payment is set to Services.
ACCBP automatic journal:
- Line 51, Formulas section:
Syntaxes ‘[F:PYD]DSP’, ‘[F:PYA]AMTANA’ and ‘[F:PYA]QTYANA’ have been added to the relevant fields.
Note: 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 (CMPGAU) to identify your variances.
Automatic journals BDDBR, BDIMP and BDWO
Setup > Financials > Accounting interface > Automatic journals (GESGAU)
Due to some setup inconsistencies, the following automatic journals have been updated:
- BDDBR - Doubtful debts Bad Debts
- BDIMP - Impairments Bad Debts
- BDWO - Write off - Bad Debts
In the General section, Formulas block, the journal value has been updated to ‘evalue(func SUBTFO.FC("DBM"))’ and the description value to ‘evalue(func SUBTFO.FC("DBD"))’.
Setup > Financials > Accounting interface > Formulas per legislation (GESTFOLEG)
The DBD code has been created in the formulas per legislation to update descriptions in automatic journals.
Note: 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 (CMPGAU) to identify your variances.
Import template ROU updated to manage versions
Setup > Usage > Imports / exports > Import/Export templates (GESAOE)
4 fields have been added to the ROU import template to be able to manage versions during import:
- Major version (line 14)
- Minor version (line 15)
- Default ROU code (line 16)
- Option (line 17)
The import template is only delivered in the parent folder so you can decide whether to update the sub-folders or not.
Import/export templates PORSOH and PORSQH
Setup > Usage > Imports/exports (GESAOE)
The setup of the PORSOH and PORSQH import/export templates has been updated. The *15 field has been added with the ATCUD description.
Notes:
- The templates included in this correction are only integrated into the X3 folder. You need to copy the import/export template from the X3 folder to your destination folder using the Copy action and delete this same template from the application folder. Otherwise, the copy will not be allowed.
- If you have applied customizations to these standard templates, you can add the *15 field to the import/export template to manage the ATCUD import.
- This applies to both templates, PORSOH and PORSQH, which must be associated with the IMPSOH and IMPSQH standard scripts.
Documents
Readme files
- For technical components: Readme-Components-ENG-12.0.29.html
- For the application patch: Readme-X3-X3HR-ENG-12.0.29.html