Pagetitle | ||||
---|---|---|---|---|
|
Technical Bulletin: Creation of Parameter MV_ATFRSLD
Occurrence
Improvement
Summary
We have created the parameter MV_ATFRSLD to control the annual carry forward date, in module Fixed Assets (SIGAATF). Running the compatibility program automatically creates the parameter. This feature requires that parameter MV_ATFRSLD be set to .T. (True). The carry forward may occur only once a year, on the 1st of January, after the last depreciation calculation on the 31st of December, in accordance with online help instructions. Activating parameter MV_ATFRSLD in routines Monthly Calculation (ATFA050), Monthly De-calculation (ATFA070), Accelerated Depreciation (ATFA171) and Recalculate Balances (ATFA120) requires the annual carry forward to be on the 1st of January of the current year. Thus, no monthly calculation dated before the carry forward date is allowed.
ID of Ticket
TDRYQH
Products
Modules
Portals
Countries
Translations
Operating System
Database
Name + Source
ATFA001 – Auxiliary Data ATF, ATFA080 – Annual Carry Forward, ATFA120 – Recalculate Balances, ATFA050 – Monthly Calculation, ATFA070 – De-calculation, ATFA171 – Accelerated Depreciation
FNC Number
00000024353/2011
Compatibility Program Adjustments
No
Referential Integrity
Yes
Patch Application
No
Compatibility Program 1
- U_UPDATF
Implementation Procedures
The system is updated after applying the update package (patch) of this FNC.
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*.
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, thoughtfully observe the following procedure:
i. In Configurator (SIGACFG), check whether the company uses Referential Integrity by selecting option Integrity/Verification (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 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 9/20/2011.
2. Click OK to continue.
3. When you confirm it, a warning message is displayed about the backup and the need to run it in exclusive mode.
4. Click Yes to start the process. The first execution step is file preparation. An explanatory message is displayed onscreen.
5. Then, the window Update Completed is displayed with the log of all updates processed. This update log only shows the fields 6. updated by the program. The compatibility program creates the fields that do not yet exist in the data dictionary.
6. Click Save to keep the log displayed.
7. Click Ok to close the process.
Adjustments Description
Variable Name | MV_ATFRSLD |
Type | Logical |
Description | .T. = Determine whether to control the balances carry forward date in fixed asset routines such as Carry Forward/Monthly Calculation/De-calculation/Recalculate Balances/Accelerated Depreciation |
Default Value | .F. |
Procedures for Configuration
FOR PARAMETERS
Name | MV_ATFRSLD |
Type | Logical |
Por. Cont. | .F. |
Description | .T. – Determine whether to control the balances carry forward date in fixed asset routines such as Carry Forward/Monthly Calculation/De-calculation/Recalculate Balances/Accelerated Depreciation |
Technical Data
Tables | SN0 - ATF Auxiliary Data |