Linha Microsiga Protheus - Inglês

Páginas filhas
  • Field N3_TPSALDO -- 117882

Versões comparadas

Versão antiga 1

changes.mady.by.user Otto Alexandre Monteiro Altorfer

Gravado em

comparado com

Nova versão 2

changes.mady.by.user Otto Alexandre Monteiro Altorfer

Gravado em

Chave

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

Technical Bulletin: Field N3_TPSALDO

Occurrence

Improvement

Summary

We have implemented changes to the routine Assets (ATFA010), in field Balance Type (N3_TPSALDO), so its editing is enabled only when adding a new asset line and blocked when the change is made.

ID of Ticket

TERBSM

Products

  • Microsiga 11

Modules

  • SIGAATF

Portals

  • none

Countries

  • All

Operating System

  • All

Database

  • All

Name + Source

ATFA010 - Fixed Assets

Compatibility Tool Adjustments

Yes

Referential Integrity

No

Patch Application

Compatibility Tool 1

- U_UPDATF

Implementation Procedures

Before running the compatibility tool UPDATF, you must:

a) Backup the database of the product to be executed by compatibility tool (“\PROTHEUS_DATA\DATA” directory) and SXs data dictionaries (“\PROTHEUS_DATA\DATA” 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 tool 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:

 

                         i.     In Configurator (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 the items iii or iv, AND ONLY IN THESE CASES, you must deactivate such 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 TOTVS Smart Client, enter U_UPDATF in field Initial Program.

To correctly update the data dictionaries, make sure the date on the compatibility program is equal to or after 3/19/2012.

2. Click OK to continue.

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

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

5. Click Process to start processing. The first execution step is file preparation.
An explanatory message is displayed onscreen.

6. Then, the window Update Completed is displayed with the log of all updates processed. This update log only shows the fields updated by the program. The compatibility program creates the fields that do not yet exist in the data dictionary.

7. Click Save to keep the log displayed.

8. Click OK to close processing.

The system is updated after applying the update package (patch) of this FNC.


Adjustments Description

Editing in file SX3 – Fields:

    • Table SN1 – Fixed Assets

Field

N3_TPSALDO

X3_WHEN

IIF(FindFunction("AF010ATPSAL"), AF010ATPSAL(), INCLUI)    

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


Procedures

  1. In Fixed Assets (SIGAATF) access Updates/Records/Assets (ATFA010).
  2. The system displays the Fixed Assets Update window.
  3. Click option Add.
  4. Place the cursor on field Balance Type and check whether you can edit the field. 
  5. Select and Confirm the option desired.
  6. Click option Edit.
  7. Place the cursor on field Balance Type of a line already added and check whether you cannot edit the field.
  8. Place the cursor on field Balance Type of a new line and check whether you can edit the field.


Technical Data

Tables

SN3 – Balances and Values