Linha Microsiga Protheus - Inglês

Páginas filhas
  • Field CVC_CODMUN -- 118120

Versões comparadas

Versão antiga 2

changes.mady.by.user Jose Moises Vera Concha

Gravado em

comparado com

Nova versão Atual

changes.mady.by.user Otto Alexandre Monteiro Altorfer

Gravado em

Chave

  • Esta linha foi adicionada.
  • Esta linha foi removida.
  • A formatação mudou.

...

Portuguese

Pagetitle
Field CVC_CODMUN
Field CVC_CODMUN

Technical Bulletin: Field CVC_CODMUN

Occurrence

Improvement

Summary

The system validation for the City Code field (CVC_CODMUN) has been removed when used in the Brazil environment.

ID of Ticket

TESJKB

Products

  • Microsiga 11

Modules

    • SIGACTB

Portals

    • none

Countries

    • Brazil

Operating System

  • All

Database

    • All

Name + Source

CVC - Accountant Register

Compatibility Tool Adjustments

Yes

Referential Integrity

No

Patch Application

No

Compatibility Tool 1

- UPDCTB

Implementation Procedures

  To make this improvement feasible, you must first apply this ticket's update package (Patch).


Before running the compatibility tool UPDCTB, you must:

a) Backup the database of the product to be executed by compatibility tool (\PROTHEUS11_DATA\DATA directory) and SXs data dictionaries (\PROTHEUS11_DATA\SYSTEM directory).

b) The above directories are the default installation of Protheus®, and you should edit them to match the product installed at your company.

c) This routine must run in exclusive mode; that is, no user should be using the system.

d) If data dictionaries have customized indexes (created by the user), be sure to identify them by their nicknames prior to running the compatibility tool. If the compatibility tool needs to create indexes, it will add them from the original order installed in Protheus®, which can overwrite custom indexes if they are not identified by the nickname.

e) You must run the compatibility program with Referential Integrity deactivated*.



The following procedure must be performed by a professional qualified as Data Base Administrator (DBA) or equivalent!


Improper activation of the Referential Integrity may drastically change the relationship between tables on the database. Therefore, before using it, thoughtfully observe the following procedure:


                          In the Configuration Tool (SIGACFG), check whether the company uses Referential Integrity by selecting option Integrity/Checking (APCFG60A).

                        ii.     If there is no active Referential Integrity, all companies and branches registered for the system are listed on a new window and none of them will be selected. In this case, AND ONLY IN THIS CASE you do not need any other procedure of integrity activation or deactivation; just complete the checking and apply the compatibility program as usual, following the instructions.

                       iii.     If Referential Integrity is active in all companies and branches, a message is displayed in window Relationship Checking Between Tables. Confirm the message to complete the checking, or;

                       iv.     If Referential Integrity is active in one or more companies, though not to its full extent, all companies and branches registered for the system are listed in a new window, in which only those with integrity are selected. Write down which companies or branches have the integrity activated and save this note for later reference on reactivation (you may also contact our Framework Help Desk for a file with this information).

                         v.         In the cases described in items “iii” or “iv”, AND ONLY IN THESE CASES, you must deactivate the integrity by selecting option Integrity/Deactivate (APCFG60D).

                       vi.     Upon deactivation of the Referential Integrity, run the compatibility tool in accordance with the instructions.

                      vii.     Once you have applied the compatibility program, use option Integrity/Activate (APCFG60) to reactivate the Referential Integrity, IF AND ONLY IF it has been deactivated. To do so, have the information of companies and/or branches that had integrity activation at hand, select them once again, and confirm the activation.


IF YOU HAVE ANY QUESTIONS, contact the Framework Help Desk!



  1. In Microsiga Protheus® Smart Client, enter U_UPDATFUPDCTB in field Initial Program.

To correctly update the data dictionaries, make sure the date on the compatibility tool is equal to or after 4/03/2012.

2. Click Ok to continue.

3. After confirmation, a window is displayed for selecting the compatibility tool.. Select the program U_UPDCTB.

4. When you confirm it, a warning message is displayed about the backup and the need to run it in exclusive mode.

Confirm it to start the processing. The first execution step is file preparation, in accordance with the message displayed on-screenonscreen.

5. Afterwards, the window Update Completed is displayed with the history (log) of all updates processed. In this updating log, only the fields updated by the program are presented. The compatibility tool creates fields that do not exist in the data dictionary yet.

6. Click Save to save the history (log) displayed.

7. Click Ok to close the process.

Adjustments Description

  1. Creation of Fields in file SX3 – Fields:
  • Table CVC – Participants


Field

CVC_CODMUN

System Val. System

 



The size of fields that have groups may vary according to the environment in use.

Procedures for Configuration

Utilization Procedures

Technical Data


Tables Used

CVC – Participants


Notes