Functional pre/post-requisites for the migration of a folder to Update 9.0.0.

Pre-requisites to the migration process

The migration prerequisites of a folder are specified here below. Generally speaking, the first step, highly recommended, is to check that the data to migrate is consistent. For a folder containing many movements, and which has sometimes gone through maintenance phases, it is possible that some data are not perfectly consistent, especially if there are specific developments.

This operation will detect any problem concerning data that may generate errors during the migration procedure, making it necessary to restart it.

It is also recommended to purge a certain number of temporary tables whose migration may be time-consuming (for instance the query table).

Financials

GEXEAN variable

From version V7.3 and higher, the GEXEAN global variable is not initialized when the user logs into the folder.

This variable is now initialized at the user session level when first opening a function that requires this variable (RECBAL, SIMULFINEX, etc.).

The global variable GEXEAN has thus been deleted from the variables dictionary (GESAGB).

The specific developments that require the GEXEAN global variable should allow the declaration and initialization of this variable if it has not been declared yet. To do so, you need to call the EXEAN subprogram: If dim(GEXEAN)<0: Call EXEAN From GLOBCPT: Endif

Post-requisites to the migration process

Financials

Management of XML bank files with the pain001.001.003 format

If you want to use this feature, copy the following setups from the X3 folder to the operating folder:

• Bank files setup function (GESTFB):
  New delivered file: VIRINT03, ISO20022 payment file with pain001.001.003 format
• Payment entry transactions setup function (GESTPY):
  New transaction FVIRV 'Supplier - Variable international transfers' using the VIRINT03 bank file
• Sequence number definition setup function (GESANM):
  New sequence number counter VARFB used in the VIRINT03 bank file
• Sequence number assignment function (GESTCA):
  Assignment of the VAFB sequence number on line 19 of the BP module

Optional management of the BIC code as of February 1st 2016

To get this feature, copy the following setups from the X3 folder to the operating folder:

• Bank files setup function (GESTFB):
  Modified files: SCT03 and SDD02
• Import templates setup function (GESAOE):
  Modified template: MDT

Factoring management with/without recourse

To enable this feature, copy the following setups from the X3 folder to the operating folder:

• Parameters of variables setup function (GESGVA)
  New parameters: AMTNOTFCT, BPRFCT, DUDAMT, DUDLOC, LEDCUR, PAYCUR et VCRCUR
• Automatic journal variables setup function (GESGVG):
  New variables: AMTFCTNREC and AMTNOTFCT
• Automatic journal setup function (GESGAU):
  New automatic journals: FCNOD, FCTN2, FCTOD, FCTQ2
  Automatic journals modified: FCTN and FCTQ
• Automatic journal groups setup function (GESGRA):
  New groups: FCTN, FCTQ
• Default dimensions setup function (GESCDE):
  New default dimension code: FCT (to be adjusted for the definition of customer initialization rules)

New accounting code lines have been delivered in the accounting code lines setup function (GESCCL) - Line 4 to 11 for "factor" accounting codes. You will need to adjust the accounting codes of the "factor" type in order to add the new accounts to be used, depending on the customer's chart(s) of accounts.

Fixed Assets

Buildings

Buildings, which used to be managed in miscellaneous table no. 604, are now managed through an X3 class.
The user must check that buildings have been converted during the migration and that they are now available in the PHYBUI representation (Common data > Fixed asset tables > Buildings).

Locations

Locations, which used to be managed via a classic object, are now managed through an X3 class.
From Update 9 and higher, the location is always linked to a financial site.
The user must check that locations have been converted during the migration and that they are now available in the PHYLCT representation (Common data > Fixed asset tables > Locations).

Physical elements

Physical elements, which used to be managed via a classic object, are now managed through an X3 class.
The user must check that physical elements have been converted during the migration and that they are now available in the PHYELT representation (Common data > Fixed asset tables > Physical elements).

Production plan

The user must check that the unit defined at the level of parameter DEFUOM - Default unit (FAS chapter, FAS group, folder level) is displayed in the production plan plan header (Fixed assets > Fixed assets > Production plan).

Import templates

Since the implementation of a new management for physical elements and for the stock count in Update 9, the related import templates have been deleted in the migration.

Mass recodings

After the migration, mass recoding setups (optional) can be deleted because of obsolete keys. The user must check that their recoding parameters, if used, are available (Fixed assets > Utilities > Mass recodings).

Distribution

Quote types

In the migration process, a quote type must be assigned to the Quote type field (SQHTYP) for all existing quotes.

During folder creation, the following quote types and general parameters are copied from the reference folder:

• SQHTYP – Quote type (VEN chapter, QUO group),
• SOHTYPNOR - Normal order type (VEN chapter, ORD group),
• SOHTYPINV- Direct invoice order type (VEN chapter, ORD group),
• SOHTYPOPN - Open order type (VEN chapter, ORD group).

Only the types having a legislation managed in the destination folder or an empty legislation will be copied from the reference folder.

The user can set up this data on two levels, depending on the time of migration.

• If the migration is performed at the same time as the folder validation: the setup must be made in the reference folder, with the expected type codes (quote type tables and general parameters). Otherwise, the system will use the default types delivered in the standard setup.
• If the migration is performed after the folder validation: the setup must be correctly made in the destination folder, with the expected type codes (quote type tables and general parameters). Otherwise, the system will use the default types copied from the reference folder.

When the quote types table is loaded and when the SQHTYP general parameter is set up, the system populates the quote as follows:

1. For each quote, the system checks the value of the SQHTYP general parameter.
2. If no value is defined for this parameter, the system selects the first quote type in alphabetical order, with respect to the quote legislation.
3. If no result can be found, the system selects the first quote type in alphabetical order, which has a empty legislation.

After migration, or when the migration is performed after folder validation, the sequence numbers defined in the Sequence number assignment function (GESTCA) must be reassigned to the proper quote types in order to preserve the sequence numbers order.

Price initialization on an inter-company sales order

The migration process must assign a value in the Price transfer column in the Automatic flows grid of the Inter-company setup function, for each flow line.

• If the source document is a purchase order, the Price transfer column is initialized to the value 'No'.
• If the source document is a sales order, the Price transfer column is initialized to the value 'Yes'.
  

Transfer rules for invoicing elements of the Sales module

In the Invoicing elements function (GESSFI), you need to check the values on the new lines of the Transfer rules grid.

In folder migration, the rules applying to these new lines in the Invoicing elements function are based on the following principles:

• The transfer rules for a return on credit memo are the same as those used for invoices on credit memos.
• The transfer rules of a service contract on invoice are based on the following values, to ensure their consistency with the behavior of previous versions:
• Split rules: All invoices (for invoicing elements in amount or percentage)
• Grouping rules: First service contract
• Grouping: Yes

You can only modify this rule after the validation is complete.

EU Intrastat

You must perform a blank extraction after a migration to Update 9.0.0 in order to identify the previous documents that have not been extracted yet. Otherwise, they will be displayed when performing a new extraction with the Intrastat declaration.

This action applies to the folders where subcontracting is managed since new subcontracting flows are automatically declared.