Integrale migration start

• To process (field VALID)

This column is used to select the table to migrate. To do this, double-click inside the column. The "Select all" and "Deselect all" right-click options can also be used.

• Description (field INTIT)

Company

This phase is for the creation of the company defined in the transcoding.

The items generated by this migration are visible in the menu Setup / Organizational structure / Companies.

 The duration of the migration may be very long because it is proportional to the number of general and analytical accounting entries to recover. It is recommended to prune the Sage Intégrale closed fiscal years which are not to migrate to Sage X3.

Migrating the company creates the analytical axes(Setup / Organizational structure / Dimension types) and automatically assign them in the "Financials" tab of the company record, and during the setup of the analytical general ledger linked to the account core model. (Setup / Organizational structure / Ledgers). To correctly initialize the dimension types, it is necessary to relaunch the application after the migration of the company record.

 See the migration prerequisites.

 The Sage Intégrale dimension types remain dimension types in Sage X3:

• The titles correspond to the name of the dimension type in Sage Intégrale,
• the format is initialized by default at 20c,
• the Automatic creation check box is selected by default.

An additional "Other" dimension type is added for the analytical dimensions defined in Sage Intégrale that do not correspond to the concatenation of analytical centers.

Sites

This phase is for the creation of the sites defined in the transcoding.

The items generated by this migration are visible in the menu Setup / Organizational structure / Sites.

 The main site is identified as financial, warehouse, sale, purchase, etc., site.

Upon migration of the BOMs, a search of the default production site of the finished product is performed in the data of Sage Intégrale in order to identify the production sites. The work orders are migrated in the default production site of the finished product.

 See the "Documents" tab for more details.

Users

This phase is for the creation of the users defined in the transcoding.

The items generated by this migration are visible in the menu Setup / Users / Users.

 After the migration, these user codes are created with no passwords in Sage X3. Initially, to log on to the migrated company, it is necessary to use the number of the Sage Intégrale user or the "Admin" session. Be careful to set up a new password later on.

Route code

This phase is for the creation of the route codes defined in the transcoding.

The items generated by this migration are visible in the menu Setup / General parameters / Local menus / Sales module.

After the items have been migrated, remember to re-log, as the local menus are updated only after re-logging to the folder.

Statistical groups

This phase is for the creation of the statistical groups defined in the transcoding.

The items generated by this migration are visible in the menu Development / Data and parameters / Miscellaneous tables / Data.

• Product groups are recovered in the miscellaneous table 20.
• Product sub-groups are recovered in the miscellaneous table 21.
• Customer groups are recovered in the miscellaneous table 30.
• Customer sub-groups are recovered in the miscellaneous table 31.
• Supplier groups are recovered in the miscellaneous table 40.
• Supplier sub-groups are recovered in the miscellaneous table 41.

Customs reference

This phase is used for the creation of customs references which existed in Sage Intégrale but do not in Sage X3.

The items generated by this migration are visible in the menu Common data / Product tables / EU commodity codes.

Units of measure

This phase is for the creation of the units of measure defined in the transcoding.

The items generated by this migration are visible in the menu Common data / Common tables / Units of measure.

 All the units are initialized with the "Other" type, except for the "HRS" unit which is of the "Time" type. This is because, in Sage Intégrale, it is the only unit which is systematically a unit of time.

• Processing (field TRT)

The "Processing" column specifies the name of the program launched to perform the migration.

• Remaining for process (field MES)

As the successive migrations take place, the Remaining for process counter displays the items that remain to migrate.

 For the price lists, it is possible that the migration indicates no error even though the Remaining for process counter still displays some items to migrate.
In this case, the items that remain to migrate may be:

• null prices in currency that are not recovered in Sage X3,
• price lines containing product codes ending with a star (grouping code for prices lists in Sage Intégrale) that are not recovered in Sage X3,
• price lines for products which no longer exist.

• Simulation (field SIMFLG)

Specify whether the migration must be launched in simulation mode (no recording is made) or not.

The simulation can be used for controls before performing the real update. As soon as there are no more blocking errors, the real migration can be launched.

If multiple tables are selected for the simulation, they may be interdependent and blocking error messages may occur.
For example, to migrate the "Customers" table in simulation, the "Payment terms" table must be migrated in real mode beforehand.

 For these reasons, it is preferable to process each table in simulation one after the other. If no error are found, the real processing may be launched, before the simulation of the next table, etc.

• As long as no processing has been launched for real (only in simulation), it is possible to restart the import of the Sage Intégrale tables to load and overwrite the content of the XI temporary tables.

 If the import is restarted, the transcoding must be redone and the setup revised. 

• If a XI table has not been migrated for real (all the recordings of the table have their FLGREP field set to zero), restart the import of the "Sage Intégrale" data of the table.

 Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

• If the recordings concerned by the modification have not been processed for real by the migration (FLGREP field set to zero), modify the content of a XI table.

 Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

• Modify the transcoding.
• In some logs, after the simulated migration, the entry numbers assigned in Sage X3 may be identical from one "Sage Intégrale" entry to another.

 This is normal insofar as the Sage X3 entry counter used is not updated for real. The entry numbers assigned after migration can be read and retained only after a processing launched in real mode.

When the processing is performed for real, it is necessary to restore the folder before migration in the event of severe errors that would require modifying the data input.

• Execution (field EXEC)

Launch the migration of the data selected in the table of the current screen, in simulation or real mode.

• To process (field VALID)

This column is used to select the table to migrate. To do this, double-click inside the column. The "Select all" and "Deselect all" right-click options can also be used.

• Description (field INTIT)

Payment terms

This phase is used for the creation of the payment terms and corresponding payment methods defined in the transcoding.

In Sage Intégrale, it is possible to choose other payment terms if the amount is larger or lesser. 
In Sage X3, the replacing is only possible if the amount is lesser.

Sage Intégrale, with due dates by ten-day or two-week periods, can translate the concept of 30 into end of months. This information is not recovered in Sage X3.

Sage Intégrale can define a limit day and a carry-forward day.
This information is not recovered in Sage X3.

Example: let us consider a limit day on the 25 and a carry-forward on the 10. An entry issued on the 25th of the current month and the 9th of the next month will therefore have the 10th of the next month as a calculation base for the due date.

Sage Intégrale can define a day of due date. This information is not recovered in Sage X3 (the option is systematically combined with "End of month" or "Ten-day period").

The items generated by this migration are visible in the menu:

• Common data / BP tables / Payment terms,
• Common data / BP tables / Payment terms.

Factors

This phase is used for the creation of the factors defined in the transcoding.
The factors whose code starts with "$$" (typical record) are not recovered in Sage X3.

The items generated by this migration are visible in the menu Common data / BPs / Factors.

The management of the factors differs between the two software products:

• in Sage Intégrale, the factor may be associated with a control account / miscellaneous auxiliary account, or a general account,
• in Sage X3, the factor is associated only to a general account.

However, the accounting entries of the factors are recovered and can be viewed in these accounts (control or general accounts).

For a correct usage of the data in Sage X3, the setup of the factors must be determined by associating a general account in the factor record. The factors that were associated to a control account must be associated with a general account, and their new entries are attached to these general accounts.

Sales reps

This phase is used for the creation of the sales representatives defined in the transcoding.

The items generated by this migration are visible in the menu Common data / BPs / Sales reps.

Customers

This phase is used for the creation of the customers defined in the transcoding.
The customers whose code starts with "$$" (typical record) are not recovered in Sage X3.

The items generated by this migration are visible in the menu Common data / BPs / Customers.

 

• In Sage Intégrale, customers may have a customer code that differs from their auxiliary code.
  For example: the customer code "Dupont" is posted in the auxiliary account "CDupont".
• In Sage X3, these two codes are the same.
  For example: the customer code "Dupont" can be posted only in the auxiliary account "Dupont".

The entries in Sage Intégrale customers follow the same pattern.

In the case where the customer code and the auxiliary account differed in Sage Intégrale, the former Sage Intégrale auxiliary account is mentioned in the Notes block of the Sage X3 customer record.

Suppliers

This phase is used for the creation of the suppliers defined in the transcoding.

The suppliers whose code starts with "$$" (typical record) are not recovered in Sage X3.
Only the suppliers specified as carriers in supplier records are recovered as carriers in Sage X3. The others must be created manually.

The items generated by this migration are visible in the menu Common data / BPs / Suppliers.

 

• In Sage Intégrale, a supplier and a customer may have the same code without being the same BP.
• In Sage X3, this is no longer possible. If this situation occurs, it is necessary to go back to the transcoding, modify the suggested supplier code to specify a new one, and then relaunch the migration of the suppliers.

If the two Sage Intégrale BPs (customer and supplier) have the same postal code and site tax ID number, only one BP is created in Sage X3 with the double role of customer and supplier.

• In Sage Intégrale, suppliers may have a supplier code that differs from their auxiliary code.
• In Sage X3, these two codes are the same.

The entries in Sage Intégrale suppliers follow the same pattern.

In the case where the supplier code and the auxiliary account differed in Sage Intégrale, the former Sage Intégrale auxiliary account is mentioned in the Notes block of the Sage X3 supplier record.

Products

This phase is used for the migration of the products defined in the transcoding.

The products recovered in Sage X3 are those whose nature is:

• "Normal",
• "Cost",
• "Port", 
• "Service".

For "Normal" products, the production nature must "Component", "Finished product", or "Routing".

For "Finished products", the migration program searches for their default production site in Sage Intégrale in order to identify it as production site in Sage X3.
The products not compatible with Sage X3 are created with the status "Not to be used".
The customers whose code starts with "$$" (typical record) are not recovered in Sage X3.

The items generated by this migration are visible in the menu Common data / Products / Products.

The corresponding customers, suppliers and sites are also created.

Work centers

This phase is used for the migration of the work centers defined in the transcoding. They correspond to the Sage Intégrale products of the "OP" (operation) and "MO" (labor) types.

The items generated by this migration are visible in the menu Manufacturing / Technical data / Work centers / Work centers.



• A product record is created in Sage X3 to enable the recovery of the documents containing the "OP" and "MO" Sage Intégrale product types.
• The products and work centers are independent from one another in Sage X3.
• A work center is created for each site identified as a "production site".

 See the migration of the products.

SO pricing

This phase is used for the migration of the sales prices defined in the transcoding.

Only the following prices are recovered:

• the basic prices -tax / +tax contained in the product record, excluding promotional prices,
• the product price lists in currency,
• the product quantity prices.

The items generated by this migration are visible in the menu Purchasing / Price lists / Price list entry.

 To recover the price lists, certain data elements are mandatory. 

 See the chapters "Setup" and "Sales" in the appendices.

PO pricing

This phase is used for the migration of the purchase prices defined in the transcoding.

The supplier price lists and the discounts (from the supplier records) are recovered. The following items are created:

• The "FOU" price list code, corresponding to the supplier discount percentage or increase percentage. This setup is generated only if the corresponding supplier discount (positive or negative percentage) contains a column number in the setup phase,
• the "ART" price list code, corresponding to the product price lists per supplier,
• the "FAM" price list code, corresponding to the product group price lists per supplier,
• the "SFAM" price list code, corresponding to the product sub-group price lists per supplier.

The validity start date of the price list is initialized on the date of the first day of the first fiscal year recovered by the migration. This date is indicated in the setup of the first "Financials" tab.
The validity end date is equal to the start date plus ten years.

The items generated by this migration are visible in the menu Purchasing / Price lists / Price list entry.

 To recover the price lists, certain data elements are mandatory. 

 See the chapters "Setup" and "Sales" in the appendices.

BOMs

This phase is used for the migration of the BOMs defined in the transcoding.

The BOMs generated by this migration are visible in the menu:

• Common data / BOMs / Production BOMs, for products managed in stock,
• Common data / BOMs / Commercial BOMs, for products not managed in stock (equivalent to the assembly in Sage Intégrale).

The routings generated by this migration are visible in the menu Manufacturing / Technical data / Routings / Routing management.

Products of the "OP" (operation) or "MO" (labor) types are recovered in the routings.



Since the routings may be used in multiple Sage Intégrale BOMs, which themselves may be associated with different production sites, they are systematically created for all the sites identified as "production sites" in Sage X3.

The site code is retained in the routing code. It is therefore important to check that the length of the product code and that of the site code do not exceed the product code max length set up in Sage X3. If they are too long, this must be taken into account in the transcoding of the products and sites; shorter codes must be assigned to them.

For example: if a Sage Intégrale company has 5 warehouses, 3 of which being identified as "production sites": TO, RO, and ZZ, 3 routings are created: GA1, GA2, and GA3. In Sage X3, the following 9 routings are recovered: GA1TO, GA1RO, GA1ZZ, GA2TO, GA2RO, GA2ZZ, GA3TO, GA3RO, and GA3ZZ.

The customer and document specific BOMs are not recovered in Sage X3.

Accounts (general and miscellaneous BP)

This phase is used for the migration of the general accounts (Common data / G/L accounting tables / General / Accounts - if necessary, choose the chart of accounts using the [Plan] button) and, simultaneously, that of the miscellaneous auxiliaries (Common data / BPs / BPs), as defined in the transcoding.

• The format of the accounts depends on the chart code.
• The default class is initialized with regards to the setup of the chart code (Setup / Organizational structure / Charts of accounts) delivered in standard.
• A null currency code indicates that all the accounts are multi-currency.
• If the Sage Intégrale account is managed in analytical accounting, the account of the chart of accounts can be set up with a specified "default account". The screen will be imposed; that is, if there are analytical movements, they are posted to the default account by default.

This phase automatically creates the analytical plan for all the accounts managed analytically.
The analytical accounts are created with the same coding as the general accounts (Common data / G/L accounting tables / General - choose the analytical chart of accounts) and are automatically assigned to them.

Analytical dimensions

This phase is used for the migration of the analytical centers and dimensions defined in the transcoding. The Sage Intégrale analytical centers become dimensions in Sage X3. The Sage Intégrale dimensions are reconstituted on the fly in Sage X3 by concatenating the different centers.

 

The dimension types are created upon the migration of the company. An additional type, "Others", is added for the analytical dimensions defined in Sage Intégrale which do not correspond to the concatenation of analytical centers.

The following items are migrated:

• the Sage Intégrale analytical dimensions which do not correspond to the concatenation of analytical centers. In that case, they are associated with the "Others" type.
• the Sage Intégrale analytical centers. They become analytical dimensions in Sage X3 and are associated with their corresponding type.

The items generated by this migration are visible in the menu Common data / G/L accounting tables / Analytical / Analytical dimensions.

Analytical distribution

Before migrating the analytical distributions, it is necessary to check that the ledger and the company record are set up with the correct dimension types, so that the distributions are assigned to the correct types and dimensions.

This phase is used for migrating the distributions of the analytical models present in Sage Intégrale.

The items generated by this migration are visible in the menu Common data / G/L accounting tables / Analytical / Analytical allocation.

• Processing (field TRT)

As the successive migrations take place, the Remaining for process counter displays the items that remain to migrate.

 For the price lists, it is possible that the migration indicates no error even though the Remaining for process counter still displays some items to migrate.
In this case, the items that remain to migrate may be:

• null prices in currency that are not recovered in Sage X3,
• price lines containing product codes ending with a star (grouping code for prices lists in Sage Intégrale) that are not recovered in Sage X3,
• price lines for products which no longer exist.

• Remaining for process (field MES)

• Simulation (field SIMFLG)

Specify whether the migration must be launched in simulation mode (no recording is made) or not.

The simulation can be used for controls before performing the real update. As soon as there are no more blocking errors, the real migration can be launched.

If multiple tables are selected for the simulation, they may be interdependent and blocking error messages may occur.
For example, to migrate the "Customers" table in simulation, the "Payment terms" table must be migrated in real mode beforehand.

 For these reasons, it is preferable to process each table in simulation one after the other. If no error are found, the real processing may be launched, before the simulation of the next table, etc.

• As long as no processing has been launched for real (only in simulation), it is possible to restart the import of the Sage Intégrale tables to load and overwrite the content of the XI temporary tables.

 If the import is restarted, the transcoding must be redone and the setup revised. 

• If a XI table has not been migrated for real (all the recordings of the table have their FLGREP field set to zero), restart the import of the "Sage Intégrale" data of the table.

 Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

• If the recordings concerned by the modification have not been processed for real by the migration (FLGREP field set to zero), modify the content of a XI table.

 Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

• Modify the transcoding.
• In some logs, after the simulated migration, the entry numbers assigned in Sage X3 may be identical from one "Sage Intégrale" entry to another.

 This is normal insofar as the Sage X3 entry counter used is not updated for real. The entry numbers assigned after migration can be read and retained only after a processing launched in real mode.

When the processing is performed for real, it is necessary to restore the folder before migration in the event of severe errors that would require modifying the data input.

• Execution (field EXEC)

Launch the migration of the data selected in the table of the current screen, in simulation or real mode.

• To process (field VALID)

This column is used to select the table to migrate. To do this, double-click inside the column. The "Select all" and "Deselect all" right-click options can also be used.

• Description (field INTIT)

Journal codes

This phase is used for the migration of the journals defined in the transcoding.

The items generated by this migration are visible in the menu Common data / G/L accounting tables / General.

Bank

This phase is used for the migration of the banks defined in the transcoding.

The items generated by this migration are visible in the menu Common data / BP accounting tables / Bank accounts.

Currency rate

This phase is used for updating the currencies defined in the transcoding.

The items generated by this migration are visible in the menu Common data / Common tables / Currency rates.

Stock

This phase is used to generate stock count entries in order to recover the product/warehouse stock of all the products and potentially the serial/lot numbers that are pending (not closed) in Sage Intégrale, as defined in the transcoding.

The items generated by this migration are visible in the menus Stock / Counts / Stock count sessions and Counts.

One stock count session is created per warehouse.
Certain stock count sessions have the status "In creation" and do not contain stock count lists. They correspond to warehouses without stock.
Others have the status "To be counted" and contain stock count lists (status "Validated"). They correspond to the stocks of the products for these warehouses.

The stock counts are created for the date specified in the "Management" tab of the setup and are valued with the valuation method indicated in the product/site record or in the corresponding category of each product.

If you do not wish to recover the information of the series/lots, place the MVT_SER_LOT Intégrale table in the import folder of the Sage Intégrale tables.

The message "Product not to be used" indicates that the product had a status in Sage Intégrale which is incompatible with Sage X3. This may result in a non null "Remaining to process" stock counter. This is also the case for movements in warehouses which no longer exist and which therefore cannot be migrated.

• Processing (field TRT)

As the successive migrations take place, the Remaining for process counter displays the items that remain to migrate.

 For the price lists, it is possible that the migration indicates no error even though the Remaining for process counter still displays some items to migrate.
In this case, the items that remain to migrate may be:

• null prices in currency that are not recovered in Sage X3,
• price lines containing product codes ending with a star (grouping code for prices lists in Sage Intégrale) that are not recovered in Sage X3,
• price lines for products which no longer exist.

• Remaining for process (field MES)

• Simulation (field SIMFLG)

Specify whether the migration must be launched in simulation mode (no recording is made) or not.

The simulation can be used for controls before performing the real update. As soon as there are no more blocking errors, the real migration can be launched.

If multiple tables are selected for the simulation, they may be interdependent and blocking error messages may occur.
For example, to migrate the "Customers" table in simulation, the "Payment terms" table must be migrated in real mode beforehand.

 For these reasons, it is preferable to process each table in simulation one after the other. If no error are found, the real processing may be launched, before the simulation of the next table, etc.

• As long as no processing has been launched for real (only in simulation), it is possible to restart the import of the Sage Intégrale tables to load and overwrite the content of the XI temporary tables.

 If the import is restarted, the transcoding must be redone and the setup revised. 

• If a XI table has not been migrated for real (all the recordings of the table have their FLGREP field set to zero), restart the import of the "Sage Intégrale" data of the table.

 Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

• If the recordings concerned by the modification have not been processed for real by the migration (FLGREP field set to zero), modify the content of a XI table.

 Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

• Modify the transcoding.
• In some logs, after the simulated migration, the entry numbers assigned in Sage X3 may be identical from one "Sage Intégrale" entry to another.

 This is normal insofar as the Sage X3 entry counter used is not updated for real. The entry numbers assigned after migration can be read and retained only after a processing launched in real mode.

When the processing is performed for real, it is necessary to restore the folder before migration in the event of severe errors that would require modifying the data input.

• Execution (field EXEC)

Launch the migration of the data selected in the table of the current screen, in simulation or real mode.

• To process (field VALID)

This column is used to select the table to migrate. To do this, double-click inside the column. The "Select all" and "Deselect all" right-click options can also be used.

• Description (field INTIT)

Customer quotes

This phase is used for the migration of Sage Intégrale pending "DV"-type entries (quotes) whose date is later or equal to the date defined in the first "Financials" tab of the setup.

The items generated by this migration are visible in the menu Sales / Quotes / Quotes.

Since the "PR"-type entries (proforma) are not migrated, it is necessary for recovering them as quotes to change the type from "PR" to "DV" in the XIEPV table.

The following items are not recovered in Sage X3:

• the product lines whose delivered quantity is equal to zero,
• the entries with no product line.

For example, a purchase entry in which only the freight at the bottom of the entry has been specified.

Customer orders

This phase is used for the migration of Sage Intégrale pending "Co"-type entries (orders) whose date is later or equal to the date defined in the "Financial" first tab of the setup.

Their non posted prepayments (up to 30) are recovered as prepayment open items in Sage X3.
Upon invoice generation in Sage X3, only four prepayment open items are generated.

The items generated by this migration are visible in the menu Sales / Orders / Orders.

In priority, the migration program recovers the Sage Intégrale amounts according to the setup done in Sage X3, including when it comes to taxes.
It is possible, upon usage of these entries in Sage X3, that the amount +tax is recalculated and becomes different from the original amount +tax.

The following items are not recovered in Sage X3:

• the product lines whose delivered quantity is equal to zero,
• the entries that have no product line (for example, a purchase entry in which only the freight at the bottom of the entry has been specified),
• the entries containing product lines that have negative delivered quantities.

The lines of the entries with a negative net price have a value of zero in Sage X3.

Customer invoices

This phase is used for the migration of entries of the type "FA", "AV", and "AC" (invoices and credit memos) posted in Sage Intégrale and whose date is later or equal to the date defined in the first "Financials" tab of the setup.

The items generated by this migration are visible in the menu Sales / Inquiries / Invoices / List of invoices.

The entries appear with a "Validated" status and thus cannot be modified.

The following items are not recovered in Sage X3:

• the product lines whose delivered quantity is equal to zero,
• the entries that have no product line (for example, a purchase entry in which only the freight at the bottom of the entry has been specified).

Invoices with a negative quantity are recovered as is in Sage X3.

Supplier orders

This phase is used for the migration of Sage Intégrale pending "CF"-type entries (orders) whose date is later or equal to the date defined in the "Financial" first tab of the setup.

The items generated by this migration are visible in the menu Sales / Inquiries / Invoices / List of invoices.

Their non posted prepayments (up to 30) are recovered as prepayment open items in Sage X3.

The items generated by this migration are visible in the menu Purchasing / Orders / Orders.

Since the "DF"-type entries (price requests) are not migrated, it is necessary for recovering them as orders to change the type from "DF" to "CF" in the XIEPV table.

The following items are not recovered in Sage X3:

• the product lines whose delivered quantity is equal to zero,
• the entries that have no product line (for example, a purchase entry in which only the freight at the bottom of the entry has been specified).

Supplier invoices

This phase is used for the migration of entries of the type "FF", "AF", and "AA" (invoices and credit memos) posted in Sage Intégrale and whose date is later or equal to the date defined in the first "Financials" tab of the setup.

The items generated by this migration are visible in the menu Purchasing / Inquiries / Invoices / List of invoices.

The entries appear with a "Validated" status and thus cannot be modified.

The following items are not recovered in Sage X3:

• the product lines whose delivered quantity is equal to zero,
• the entries that have no product line (for example, a purchase entry in which only the freight at the bottom of the entry has been specified).

Work orders

This phase is used for the migration of Sage Intégrale pending "PP"-type entries (production plans) whose date is later or equal to the date defined in the "Financial" first tab of the setup.

The items generated by this migration are visible in the menu Manufacturing / Planning / Work order.

Only production plans for which an MRP calculation has been launched in Sage Intégrale with WO generation are processed.

The work orders must not have cost statements (BA) and assigned or specific customer/entry BOMs. If they do, they are ignored.

The selected "PP"-type entry lines trigger the creation of work orders with the status "Closed" in Sage X3.
Theirrelease mode is:

• "Complete", if a routing could be associated,
• "Materials only", otherwise.

Subsequently, the production setup must be readjusted in order to optimize the usage of this module with a Sage X3 approach rather than one of Sage Intégrale.

For example, an MRP mode must be created for each BOM code and production site, so as to be able to launch the requirements calculation in the software product.

General and analytical history

This phase is used for the migration of the general accounting history of Sage Intégrale from the fiscal year whose date has been defined in the first "Financials" tab of the setup.

If the "Analytical recovery" check box is selected, the entries corresponding to accounts that can be analytically distributed in the analytical history of Sage Intégrale are also migrated.

The items generated by this migration are visible in the menu Financials / Journals / Journal entry.

The open items potentially present at the entry phase (Sx phase) in Sage Intégrale are created in Sage X3. The balance is considered as closed.
Only the open items at the entry phase in Sage Intégrale (S phase) are integrated with a null paid amount. The other open items are migrated, but considered as already closed. They therefore do not change any longer.

General and analytical day book

This phase is used for migrating the entires of the Sage Integrale general accounting day book.

For accounts that can be analytically distributed, and if the "Analytical recovery" check box is selected, the corresponding entries in the analytical history of Sage Intégrale are also migrated.

The items generated by this migration are visible in the menu Financials / Journals / Journal entry.

The open items potentially present at the entry phase (Sx phase) in Sage Intégrale are created in Sage X3. The balance is considered as closed.
Only the open items at the entry phase in Sage Intégrale (S phase) are integrated with a null paid amount. The other open items are migrated, but considered as already closed. They therefore do not change any longer.

Analytical history

This phase is used for migrating the entries of the analytical history of Sage Intégrale from the fiscal year whose date has been defined in the first "Financials" tab of the setup.

The items generated by this migration are visible in the menu Financials / Journals / Journal entry.

 The migration is possible only if the "Analytical recovery" check box is selected (menu Setup / Integrale migration / Setup - "Financials" tab).

Analytical day book

This phase is used for migrating the entries of the analytical entries of the general analytical day book.

The items generated by this migration are visible in the menu Financials / Journals / Journal entry.

 The migration is possible only if the "Analytical recovery" check box is selected (menu Setup / Integrale migration / Setup - "Financials" tab).

• Processing (field TRT)

As the successive migrations take place, the Remaining for process counter displays the items that remain to migrate.

 For the price lists, it is possible that the migration indicates no error even though the Remaining for process counter still displays some items to migrate.
In this case, the items that remain to migrate may be:

• null prices in currency that are not recovered in Sage X3,
• price lines containing product codes ending with a star (grouping code for prices lists in Sage Intégrale) that are not recovered in Sage X3,
• price lines for products which no longer exist.

• Remaining for process (field MES)

• Simulation (field SIMFLG)

Specify whether the migration must be launched in simulation mode (no recording is made) or not.

The simulation can be used for controls before performing the real update. As soon as there are no more blocking errors, the real migration can be launched.

If multiple tables are selected for the simulation, they may be interdependent and blocking error messages may occur.
For example, to migrate the "Customers" table in simulation, the "Payment terms" table must be migrated in real mode beforehand.

 For these reasons, it is preferable to process each table in simulation one after the other. If no error are found, the real processing may be launched, before the simulation of the next table, etc.

• As long as no processing has been launched for real (only in simulation), it is possible to restart the import of the Sage Intégrale tables to load and overwrite the content of the XI temporary tables.

 If the import is restarted, the transcoding must be redone and the setup revised. 

• If a XI table has not been migrated for real (all the recordings of the table have their FLGREP field set to zero), restart the import of the "Sage Intégrale" data of the table.

 Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

• If the recordings concerned by the modification have not been processed for real by the migration (FLGREP field set to zero), modify the content of a XI table.

 Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

• Modify the transcoding.
• In some logs, after the simulated migration, the entry numbers assigned in Sage X3 may be identical from one "Sage Intégrale" entry to another.

 This is normal insofar as the Sage X3 entry counter used is not updated for real. The entry numbers assigned after migration can be read and retained only after a processing launched in real mode.

When the processing is performed for real, it is necessary to restore the folder before migration in the event of severe errors that would require modifying the data input.

• Execution (field EXEC)

Launch the migration of the data selected in the table of the current screen, in simulation or real mode.