Technical Bulletin: Fixed Assets - Field NG_VMXDEPR of table SNG
Occurrence
Improvement
Summary
We have implemented the field (NG_VMXDEPR) in table SNG, with the aim of completing, in the assets file (SN3), the equivalent field N3_VMXDEPR, when you specify the asset group (N1_GRUPO) while registering an asset. This field represents the Maximum Value used in depreciation calculation processes. This is how the system uses it: If the value found in field N3_VORIG1 (Source Value Currency 1) is greater than the value found in field N3_VMXDEPR (Maximum Depreciation Value), the system uses, for calculating depreciation, the contents of field N3_VMXDEPR.
ID of Ticket
SCSYG3
Products
- Microsiga 11
Modules
- SIGAATF
Countries
- All
Operating System
- All
Database
- All
Name + Source
ATFA270 and ATFA010
FNC Number
00000017209/2010
Compatibility Program Adjustments
Yes
Referential Integrity
Yes
Patch Application
No
Compatibility Program 1
- U_UPDATF
Implementation Procedures
Important:
Before running the “U_UPDATF” compatibility program, you must:
a) Backup the database of the product to be executed by compatibility program (“\PROTHEUS_DATA\DATA” directory) and SXs data dictionaries (“\PROTHEUS_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 program. If the compatibility program needs to create indexes, it will add them from the original order installed by Protheus, which may overwrite any customized indexes not identified by their nicknames.
e) You must run the compatibility program with Referential Integrity deactivated*.
ATTENTION: The following procedure must be executed by a qualified personnel such as Database Administrator (DBA) or equal! * Improper activation of the Referential Integrity may drastically change the relationship between tables on the database. Therefore, before using it, note closely the following procedures: 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 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 ByYou Smart Client, enter U_UPDATF in field Initial Program.
Important:
To correctly update the data dictionaries, make sure the date on the compatibility program is equal to or after 8/31/2010.
2. Click OK to continue.
3. After confirmation, a screen is displayed for selecting the company in which the data dictionary will be edited, or a window is displayed for selecting the compatibility program.
4. When you confirm it, a warning message is displayed about the backup and the need to run it in exclusive mode.
5. Click Yes to start the process. 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 the process.
Adjustments Description
1. Creation of field in file SX3 – Fields:
- Table SNG: Maximum Depreciation Value
Field | NG_VMXDEPR |
Type | Numeric |
Size | 16 |
Decimal | 2 |
Format | @E 999,999,999,999.99 |
Title | MAX DEPR VAL |
Description | Maximum Depreciation Value |
Level | 1 |
Used | Yes |
Required | No |
Browser | Yes |
Procedures
1. In module Fixed Assets (SIGAATF), access Updates/Registers/Asset Group (ATFA270);
Click Add.
2. In the lower right-hand corner of the page, the system displays the following tabs/options:
- Registrations;
- Accounting;
- Other;
3. Click Other.
4. The new field added “Max Depr Val” is displayed onscreen
Technical Data
Tables | SNG - Maximum Depreciation Value |
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas