Setups

• Company (field CPY)

Company code (transcript value) to which will be allocated to migrated data.

• Main site (field FCY)

Site code (transcript value) to which some data will be allocated by default (Work orders...).

• Field 1 (field PRXFLD1)

When creating standard costs linked to migrated products, the cost components are recovered. If all their values is null, it is then possible to select a field in the Integrale product table (XIART) to initialize the standard cost.
« Field 1 » will have priority and « Field 2 » will be used if the value recovered by the « Field 1 » is null.

• Field 2 (field PRXFLD2)

• Product: Purchased+Sold (field ITGAV)

Code of the product category that will be allocated to the products purchased and sold.

• Purchased+sold+stock (field ITGAVS)

Code of the product category that will be allocated to the products purchased, sold and managed in stock.

• Purchased+sold+produced (field ITGAVF)

Code of the product category that will be allocated to the products purchased, sold and produced.

• Purchased+sold+produced+stock (field ITGAVFS)

Code of the product category that will be allocated to the products purchased, sold, produced and managed in stock.

• Customer (field BCGCOD)

• Supplier (field BSGCOD)

• Class A interval (field DAYGAPCLSA)

Enter the number of days between two cycle counts for this product class. The number of annual counts is determined based on this time range.
If you have modified this range, exit the function and open it again in order to display the updated number of annual counts.

• field DAY001

• Class B interval (field DAYGAPCLSB)

Enter the number of days between two cycle counts for this product class. The number of annual counts is determined based on this time range.
If you have modified this range, exit the function and open it again in order to display the updated number of annual counts.

• field DAY002

• Class C interval (field DAYGAPCLSC)

Enter the number of days between two cycle counts for this product class. The number of annual counts is determined based on this time range.
If you have modified this range, exit the function and open it again in order to display the updated number of annual counts.

• field DAY003

• Interval class D (field DAYGAPCLSD)

Enter the number of days between two cycle counts for this product class. The number of annual counts is determined based on this time range.
If you have modified this range, exit the function and open it again in order to display the updated number of annual counts.

• field DAY004

• Weekly structure (field DEFTWD)

Code of the weekly structure used by default when creating workstations.

• Stock integration alloc date (field IPTDATSTK)

Posting date used to integrate stocks.

This date will concern a period opened in X3 during the integration.

• Sales tax (field INTVACVEN)

• Purchase tax (field INTVACACH)

• Invoice tax due (field DEBENC)

• Tax level (field VACITM1)

specify the 1st level of tax that will be allocated to the products with the corresponding "VAT sales / VAT purchase" couple (Integrale value).

• Country (field PAYC)

• Subject to tax (field VACINT)

• Subject to additional taxes (field VACTPF)

• Additional tax (field VACADD)

• Tax rule (field VACBPC)

For all the possible triplets "Subject to tax / Subject to Additional taxes", specify the corresponding tax rule in X3. This field loads the VACBPR field in BPCUSTOMER.

If the triplet exists in the Integrale customer database, the flag "Exist" will be checked.

The matching will also be used when recovering the sales documents.

• Levy (field INTTPF)

• Tax level (field VACITM2)

Specify the 2nd level of tax that will be allocated to the products with the corresponding additional tax (Integrale value).

• Country (field PAYS)

• Subject to tax (field VACINTBPS)

• Tax rule (field VACBPS)

For all the possible values "Subject to tax" in the Integrale supplier database, indicate the corresponding tax rule in X3. This field loads the VACBPS field in BPSUPPLIER.

If the triplet exists in the Integrale customer database, the flag "Exist" will be checked.

The matching will also be used when recovering the purchase documents.

• Additional tax (field VACITM3)

Specify the 3rd level of tax that will be allocated to the products which "Additional tax" setup has been checked in Integrale.

• field LIBW1

• Valid to (field SPLFINHT1)

This date is used only if a price list HT2 (ex tax) is not present. In the standard case (Price list HT2 present), it is calculated as a function of the start date of the price list HT2.

• Grouping (field SPLCRIHT1)

Criteria used for the grouping of the price list lines on a same record.

The possible values are: 1=Not defined / 2=Group /3=S/Group

Not defined: The record split is carried out only on the line number of a record. On the other hand, the sort order used is Group + S/Group + Product reference.

Group: The record split is carried out on the Group. Within a record, the lines are sorted by S/Group and then by Product reference.

S/Group: The record split is carried out on the Group + S/Group. Within a record, the lines are sorted by Product reference.

• field LIBW2

• Valid to (field SPLFINHT2)

If this date is not entered, it will be created using the start date + 1 year.

• Grouping (field SPLCRIHT2)

• field LIBW3

• Valid to (field SPLFINTTC1)

This date is used only if a price list TTC2 (tax incl) is not present. In the standard case (Price list TTC2 present), it is calculated as a function of the start date of the price list TTC2.

• Grouping (field SPLCRITTC1)

Criteria used for the grouping of the price list lines on a same record.

The possible values are: 1=Not defined / 2=Group /3=S/Group

Not defined: The record split is carried out only on the line number of a record. On the other hand, the sort order used is Group + S/Group + Product reference.

Group: The record split is carried out on the Group. Within a record, the lines are sorted by S/Group and then by Product reference.

S/Group: The record split is carried out on the Group + S/Group. Within a record, the lines are sorted by Product reference.

• field LIBW4

• Valid to (field SPLFINTTC2)

• Grouping (field SPLCRITTC2)

• field LIBW5

• Valid from (field SPLDEBDEV)

No help linked to this field.

• Valid to (field SPLFINDEV)

If this date is not entered, it will be created using the start date + 1 year.

• Grouping (field SPLCRIDEV)

Criteria used for the grouping of the price list lines on a same record.

The possible values are: 1=Not defined / 2=Group /3=S/Group/ 4=Currency + Group / 5=Currency + S/Group

Not defined: The record split is carried out only on the line number of a record. On the other hand, the sort order used is Group + S/Group + Product reference.

Group: The record split is carried out on the Group. Within a record, the lines are sorted by S/Group and then by Product reference.

S/Group: The record split is carried out on the Group + S/Group. Within a record, the lines are sorted by Product reference.

Currency + Group: The record split is carried out on the Currency + Group.

• field LIBW6

• Valid from (field SPLDEBQAF)

No help linked to this field.

• Valid to (field SPLFINQAF)

If this date is not entered, it will be created using the start date + 1 year.

• Grouping (field SPLCRIQAF)

Criteria used for the grouping of the price list lines on a same record.

The possible values are: 1=Not defined / 2=Group

Not defined: The record split is carried out only on the line number of a record. On the other hand, the sort order used is Group + S/Group + Product reference.

Group: The record split is carried out on the Group. Within a record, the lines are sorted by S/Group and then by Product reference.

• field LIBW7

• Valid from (field SPLDEBQAS)

No help linked to this field.

• Valid to (field SPLFINQAS)

If this date is not entered, it will be created using the start date + 1 year.

• Grouping (field SPLCRIQAS)

Criteria used for the grouping of the price list lines on a same record.

The possible values are: 1=Not defined / 2=Group /3=S/Group

Not defined: The record split is carried out only on the line number of a record. On the other hand, the sort order used is Group + S/Group + Product reference.

Group: The record split is carried out on the Group. Within a record, the lines are sorted by S/Group and then by Product reference.

S/Group: The record split is carried out on the Group + S/Group. Within a record, the lines are sorted by Product reference.

• field LIBW8

• Valid from (field SPLDEBQAR)

No help linked to this field.

• Valid to (field SPLFINQAR)

If this date is not entered, it will be created using the start date + 1 year.

• Grouping (field SPLCRIQAR)

Criteria used for the grouping of the price list lines on a same record.

The possible values are: 1=Not defined / 2=Group /3=S/Group

Not defined: The record split is carried out only on the line number of a record. On the other hand, the sort order used is Group + S/Group + Product reference.

Group: The record split is carried out on the Group. Within a record, the lines are sorted by S/Group and then by Product reference.

S/Group: The record split is carried out on the Group + S/Group. Within a record, the lines are sorted by Product reference.

• Integral (field LIBINTTARV)

• Column (field DISCRGVEN)

Indicates in which column number of the price list structure the values of the Integrale discounts should be entered. A control is carried out based on the column type (increase/reduction, percentage/amount)

If no number is specified, the corresponding Integrale discount will not be reused.

• Description (field DISCRGVENL)

• Integral (field LIBINTTARA)

• Column (field DISCRGACH)

Indicates in which column number of the price list structure the values of the Integrale discounts should be entered. A control is carried out based on the column type (increase/reduction, percentage/amount)

If no number is specified, the corresponding Integrale discount will not be reused.

• Description (field DISCRGACHL)

• Command type (field SOHTYP)

No help linked to this field.

• Invoice type (field SIVTYP)

The selected type must be of category "Invoice".

• Credit memo type (field CNOTYP)

The selected type must be of category "Credit note".

• Type of credit memos in value (field CNVTYP)

• field TYP

Choice of the expenditure type: there are 3 types of expenditures in the Integrale documents.

• Freight: LPV_POR table associated with a product with a "PO" nature.
• Miscellaneous expenditures: LPV_FRA_DIV table associated with a product with a "FR" nature.
• Fixed expenditures: LPV_FRA_FIX table associated with a product with a "FR" nature.

• field CODART

The Integrale product code must be of nature "PO" or "FR" according to the chosen type.

• field SFINUM

Enter the corresponding invoicing element

• Discount (field DTAREM)

• Settlement discount (field DTAESC)

• Intégrale element (field INVDTALIB)

• Invoicing element (field PFINUM)

Enter the codes of the invoicing elements corresponding to the various elements of the "Integrale".

If "Integrale" elements are never used, no invoicing element should be entered.

The match for the Discount elements is mandatory!

• Positive variances (field PFINUM1)

The code corresponding to the "positive variances" invoicing element must be entered.

This element is used when recovering the invoices in case of imbalance of amounts.

They make it possible to readjust the invoice generated in the new application so that it accurately matches the invoice coming from the Intégrale.

• Negative variances (field PFINUM2)

The code corresponding to the "negative variances" invoicing element must be entered.

This element is used when recovering the invoices in case of imbalance of amounts.

They make it possible to readjust the invoice generated in the new application so that it accurately matches the invoice coming from the Intégrale.

• First fiscal year (field STRPER)

The date of the first fiscal year has to correspond with the start date of a fiscal year in Integrale. It can correspond to the start date of a closed fiscal year or the start date of the first open fiscal year in Integrale.

When recovering the journal entries coming from the history, only the carry forward amounts generated at the date of the first FY specified in this field will be integrated in X3.

• Account core model (field ACM)

• Chart of accounts (field COA)

• Journal (field JOU)

• Entry type (field GTE)

The concept of journal typeis used to group the accounting journals according to their common use principles.

This grid is used to define, for each journal, the document type on which the journal postings will be recovered.

• INTEGRALE only (field OPTACC)

If this flag is unchecked, the accounts defined in the X3 reference folder are deleted and only the accounts of the Integrale will be created in X3. In the opposite case, all the accounts of the X3 reference folder that do not exist in the Integrale will be kept.

• Entry structure (field DACDIAGEN)

• Temporary account (field ACCTMP)

Temporary account that has to be used if the lines have been exceeded when recovering the journal postings coming from the Integrale.

The suspense account defined in the X3 ACCDEF setup is initialized by default.

• Analytical recovery (field OPTANA)

This option is used to define whether the analytical postings of the journal entries have to be recovered.

If it is required to reinitialize the analytical postings, this flag must be unchecked and a default dimension code must be entered.

• Default dimension (field CCEDEF)

If the flag "Recovery" is checked, a default selection code must be entered. It is used to define the way the analytical dimensions have to be initialized when recovering the Integrale postings that post accounts in analytical tracking.

• Analytical structure entry (field DACDIAANA)

• Purchase invoice type (field GTEFACACH)

• Pur credit memo type (field GTEAVCACH)

• Sales invoice type (field GTEFACVEN)

• Sales credit memo type (field GTEAVCVEN)

• field OPTDEV

This field is used to specify the option to use for the postings recovery in the context of an Integral folder with multi-currency postings: postings recovered in local currency (=company currency) or postings recovered in transaction currency.

• Multicurrency postings (field OPTMULDEV)

If it is required to recover the postings in transaction currency, this option is used to specify the option to use when postings (on a same journal/period) involve more than one currency different from the local currency. Two possibilities:

• Recover the postings in local currency
• Recover the postings on the first currency found (different from the local one).

• Authorized gap amount (field AMTDIF)

If the option 'Recover the postings on the first currency found' has been selected, all the recorded postings in another currency will be converted by using the rate defined on the first posting associated with the 'first currency found'. This conversation can lead to a rounding variance to balance the document in currency.

This field is used to define a maximum authorized rounding variance. If this variance has exceeded, an additional option is used to recover the postings in local currency or to scatter the rounding variance on the postings of the X3 document created.

• field CURCPY

• If gap exceeded (field OPTDIF)

This field is used to select the option to use if the maximum variance authorized has been exceeded:

• Recover the journal and period postings in local currency
• Recover the journal and period postings on the first currency found (different from the local one) and scatter the rounding variance on the posting lines of the X3 journal created.

• Debtor variance account (field ACCRNDDEB)

• Creditor variance account (field ACCRNDCDT)