9-RFE Managing Incompatible Sage X3 Versions
Context and objective
This chapter addresses the following context:
- Yooz acts as the payment administrator for issuing sales invoices.
- Sage X3 is not compatible with e-invoicing (X3 v12 prior to 2024 R1 or X3 v11)
This chapter details the operating procedures for:
-
The enrichment of the Sage X3 dictionary, partly through patches and partly through manual actions.
-
configuration tasks
This document addresses these phases of implementation:
| ▼ | ▼ | |||||
|---|---|---|---|---|---|---|
| Pre-sales | Initialization | Framing | Installation | Setting | Recipe | Production launch |
Operating procedure
Sage X3 patch update
Some of the modifications can be made using a Sage X3 patch.
This relates to activity codes, various tables, and local menus/messages.
Start by retrieving the Sage X3 patch file
Go to the download URL dedicated to the appropriate version of Sage X3
📄 Télécharger le patch SRC_YOOZX3-EINV_1_v12_p39.dat
Format :.dat — Taille : 2.5 MB — Version : 1Next, integrate this patch into the client's Sage test or production folder. An initial integration in a test environment is strongly recommended.
Check for the presence of the following tables: 18, 206, 207, 208, 209, 210, 211, 212, 970, 971, 972. And the local menu/message 7796.
The presence of these elements confirms the successful completion of this part.
Manual modifications
This involves adding fields to the standard tables and areas to the standard screens.
The details of the additions to be made are specified below. The activity code XRJ31 must be entered in all these new areas to avoid any data loss.
Where possible, zone labels are shared.
It should be noted that the various tables are already available, via the integration of the patch in the previous paragraph.
Details for the standard tables. The table must be validated after saving changes. This operation must therefore be performed without a user session. Place an XRJ31 activity code on each field.
| Table | Column | Title | Type | Linked table | Expression | Cancelation | Verification | Mandatory |
|---|---|---|---|---|---|---|---|---|
| SINVOICE | BUSPROTYP | Code type e-facture | ADI 207 | ATABDIV | 207;BUSPROTYP | Blocker | Yes | No |
| TABSIVTYP | EINVTYP1 | Code type e-facture | ADI 206 | ATABDIV | 206;EINVTYP1 | Blocker | Yes | No |
| FACILITY | ELCADD | Email address | A 125 | |||||
| FACILITY | XRJ31EINBT22 | Note | A 250 | |||||
| FACILITY | XRJ31EINBT21 | Code type e-facture | A 3 | |||||
| TABUNIT | INTSAU | Code CEE-ONU | ADI 18 | ATABDIV | 18;INTSAU | Blocker | Yes | No |
| TABVAT | VATCAT | Code type e-facture | ADI 208 | ATABDIV | 208;VATCAT | Blocker | Yes | No |
| BPARTNER | INTSRVCOD | Code service | A 100 | |||||
| BPARTNER | ELCADD | Email address | A 125 | |||||
| FACTOR | XRJ31CRN | SIRET number | A 125 | |||||
| FACTOR | XRJ31ELCADD | Email address | A 125 | |||||
| TABPAM | PAYMETTYP | Code type e-facture | ADI 211 | ATABDIV | 211;PAYMETTYP | Blocker | Yes | No |
| SFOOTINV | DISCRGREACOD | Code type e-facture | ADI 212 | ATABDIV | 212;DISCRGREACOD | Blocker | Yes | No |
| BPDLVCUST | XRJ31ELCADD | Email address | A 125 | |||||
| BPDLVCUST | XRJ31CRN | SIRET number | A 125 |
Adding the zones to the FACTOR table is not necessary if you do not have the case of entrusting your invoices to a factor. And adding the fields on the BPDLVCUST (delivered customer) table is not useful if you do not need to read the invoice addressing information on the delivered customer.
Regarding the standard screens, it is of course necessary to validate the screen after saving the changes.
The location of the zones is suggested, but it is possible to proceed differently. Place an XRJ31 activity code on each zone.
| Screen | Field | Position | Title | Type | Link | Input | Activity Code | Mandatory |
|---|---|---|---|---|---|---|---|---|
| SIH1 | BUSPROTYP | in last position of block 1 | Code type e-facture | ADI 207 | Long | Enter | No | |
| TSV1 | EINVTYP1 | in last position of block 2 | Code type e-facture | ADI 206 | Long | Enter | No | |
| FCY4 | ELCADD | in last position of block 1 | Email address | A 125 | Enter | No | ||
| FCY0 | XRJ31EINBT22 | in last position of block 1 | Note | A 250 | Enter | XRJ31 | No | |
| FCY0 | XRJ31EINBT21 | in last position of block 1 | Code type e-facture | A 3 | Enter | XRJ31 | No | |
| TUN1 | INSAU | in last position of block 1 | Code CEE-ONU | ADI 18 | No | Enter | No | |
| TVT1 | VATCAT | in last position of block 2 | Code type e-facture | ADI 208 | Long | Enter | No | |
| BPR1 | INTSRVCOD | in last position of block 1 | Code service | A 100 | Enter | No | ||
| BPR1 | ELCADD | in last position of block 1 | Email address | A 125 | Enter | No | ||
| BPC1 | INTSRVCOD | in last position of block 1 | Code service | A 100 | Enter | No | ||
| BPC1 | ELCADD | in last position of block 1 | Email address | A 125 | Enter | No | ||
| FCT1 | CRN | in last position of block 1 | SIRET number | A 125 | Enter | No | ||
| FCT1 | ELCADD | in last position of block 1 | Email address | A 125 | Enter | No | ||
| TAM1 | PAYMETTYP | in last position of block 3 | Code type e-facture | ADI 211 | Long | Enter | No | |
| SFI1 | DISCRGREACOD | in last position of block 5 | Code type e-facture | ADI 212 | Long | Enter | No | |
| BPC4 | XRJ31ELCADD | in last position of block 1 | Email address | A 125 | Invisible | XRJ31 | No | |
| BPC4 | XRJ31CRN | in last position of block 1 | SIRET number | A 125 | Invisible | XRJ31 | No | |
| BPC4 | XXRJ31ELCADD | in last position of block 2 | Email address | A 125 | Enter | XRJ31 | No | |
| BPC4 | XXRJ31CRN | in last position of block 2 | SIRET number | A 125 | Enter | XRJ31 | No | |
| BPD1 | XRJ31ELCADD | in last position of block 1 | Email address | A 125 | Enter | XRJ31 | No | |
| BPD1 | XRJ31CRN | in last position of block 1 | SIRET number | A 125 | Enter | XRJ31 | No |
Regarding the modification of the SIH1 screen, it will be necessary to launch the transaction validation function (GENMSKTRT) for the SLI and SLA transaction codes.
Adding the zones to the FACTOR table is not necessary if you do not have the case of entrusting your invoices to a factor. And adding the fields on the BPDLVCUST (delivered customer) table is not useful if you do not need to read the invoice addressing information on the delivered customer.
Configuration tasks
From this point, the essential areas for electronic invoicing are in place, you can proceed to input the values.
We will now review the different entities that need to be configured.
You can, of course, limit yourself to configuring only the data that is used. Indeed, you may have configuration tables containing a lot of information, not all of which is useful. This point applies to all elements and will not be repeated every time.
Units
This is the GESTUN function from the Common data > Common tables menu.
You must fill in the column Code CEE-ONU. A list of values is provided to help you select the correct information.
Payment method
This is the GESTAM function in the Common data > BP tables menu.
You must fill in the area Code type e-facture. A list of values is provided to help you select the correct information.
Tax rate
This is the GESTVT function in the Common data > Common tables > Taxes menu.
You must fill in the area Code type e-facture. A list of values is provided to help you select the correct information.
Billing elements
This is the GESSFI function in the Setup > Sales menu.
You must fill in the area Code type e-facture. A list of values is provided to help you select the correct information.
Types of customer invoices
This is the GESTSV function in the Setup > Sales > Document types menu.
You must fill in the area Code type e-facture. A list of values is provided to help you select the correct information.
Depending on your business management scenarios, it may be necessary to add new types of customer invoices.
Sites
This is the GESFCY function in the Setup > Organizational structure menu.
You must fill in the area Email address. This is the email address of the website issuing the invoice. Therefore, it is your email address, according to the qualification "seller's email address", which corresponds to the business term BT-34. This information is mandatory.
You can also enter a note and its code for electronic invoicing. This information is optional.
Here is a list of possible codes for the note
AAI: General information (often used for footer elements on paper invoices)
BLU: Eco-participation (WEEE) or other environmental taxes
ACC: Subrogation clause for factoring
ON: Supplier's unsolicited remarks
CUS: Customs Information
Factors
This is the GESFCT function in the Common data > BPs menu.
You must fill in the areas SIRET number And Email address on the factor(s) involved in customer electronic invoicing flows.
Clients / Tiers
These are the GESBPR or GESBPC functions of the Common data > BPs menu.
You must fill in the areas Code service And Email address on all customers concerned by electronic invoicing.