Linha Microsiga Protheus - Inglês

Child pages
  • Previous Verifications in SIGACON x SIGACTB Conversion (CTBA999 - SIGACTB)

In conversion of SIGACON to SIGACTB, the "origin" database of the migration may have inconsistencies in records with same identification key or "unique key" in the table of accounting entries. These data are evidenced by the "version updater" or by the "duplicity finder."

The result must be analyzed to make sure it is composed by "valid entries" identified by the same registration key. In this case, they must be kept in the accounting entry database, specially is accounting books of the period were already accounted. In the event of duplicities not identified previously, entries must be maintained in order to correct balances.

Procedures for verification and correction of data in the conversion of SIGACON to SIGACTB

If an inconsistency is found in records of accounting entry table, the following procedures must be adopted so that movements and balances of previous fiscal years are not affected.

a) In environment 7.10 Management Accounting (CTB) to version 8.11 of Management Accounting (CTB)

When the environment in use is version 7.10 of Management Accounting.

  1. Run the "duplicity finder" or the "version updater," which evidence the occurrence of duplicities in accounting entry table (CT2).
  2. Check if field CT2_SEQIDX, in accounting entry table (CT2) is configured as follows:

Name

CT2_SEQIDX

Type

C (character)

Size

05

Description

Index sequence

3. If this field does not exist you must create it and run the version updater again.

While running the updater, field CT2_SEQIDX is automatically increased in sequence each time a unique key duplicity is found, keeping records of accounting entry table in version 8.11 and compatible with the unique key concept.


Important:

The duplicity finder does not correct entries.

b) Accounting 7.10 environment (CON) to version 8.11 of Management Accounting (CTB)

  1. In 7.10 environment, configure and run the SIGACON Converter through menu Miscellaneous / Integrations.
  2. After the conversion is finished, follow the steps described in item a).

c) Accounting 8.11 environment (CON) to version 8.11 of Management Accounting (CTB)

Even if the environment was already migrated to version 8.11 and Accounting (CON) is still in use, follow the procedures below:

  1. In Configurator environment version 8.11, access Database/Dictionary/Database and check if field CT2_SEQIDX exist; if it doesn't, create it in table CT2 - Accounting Entries, according to explanation in item a) sub-item 2.
  2. Configure and execute in Management Accounting version 8.11 the SIGACON Converter, through option Miscellaneous / Integrations.


Important:

The SIGACON Converter checks inconsistencies in records and increases field CT2_SEQIDX sequentially each time a key duplicity is found in table CT2.

In order to analyze inconsistencies detected in table CT2, records are identified as duplicate according to description below:

  • In situations a and b duplicities are identified through records with field CT2_SEQIDX filled with 00001 or higher.
  • In situation c, duplicities are identified through records with field CT2_SEQIDX filled with content higher than 00001.

Records can be filtered using the "generic query" or through detailed reports or checking reports printed through Management Accounting environment.

You must assure that duplicities are to be removed indeed, or if records of valid entries are to be kept, although saved under the same lot identification and document.


See Also

  • Converter SIGACON x SIGACTB
  • Conversion of initial balances and movements
  • Technical information
  • Tables