Histórico da Página
| Pagetitle | ||||
|---|---|---|---|---|
|
Technical Bulletin: Title changes in fields NB_DTINI, NB_DTVENC, NB_DESCRIC
Occurrence
Improvement
Summary
We have improved the routines Insurance Policies (ATFA300) and Insurance Policies Report (ATFR300), by adjusting the titles in Spanish, in fields Start Date (NB_DTINI), End Date (NB_DTVEN) and Description (NB_DESCRIC) of table SNB – Insurance Policies.
ID of Ticket
TDNDGW
Products
Microsiga 11
Modules
- SIGAATF
Portals
- none
Countries
- All
Translations
- Spanish
Operating System
All
Database
- All
Name + Source
ATFA300 – Insurance Policies, ATFR300 – Insurance Policies Report
FNC Number
000000184162011
Compatibility Tool Adjustments
Yes
Referential Integrity
No
Patch Application
No
Compatibility Tool 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 (“\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 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! |
- In Microsiga Protheus ByYou 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 8/29/2011.
- Click OK to continue.
- When you confirm it, a warning message is displayed about the backup and the need to run it in exclusive mode.
- Click Yes to start the process. The first step of the execution is file preparation. An explanatory message is displayed on screen.
- 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.
- Click Save to keep the log displayed.
- Click OK to close processing.
Adjustments Description
- Editing in file SX3 – Fields:
- Table SNB – Insurance Policies
Field | NB_DTINI |
TITSPA | Close Start |
Field | NB_DTVENC |
TITSPA | Close Due Date |
Field | NB_DESCRIC |
TITSPA | Description |
Technical Data
Tables | SNB – Insurance Policies |
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas