Technical Bulletin: Adjustment for FCONT File Generation
Occurrence
Improvement
Summary
The Bookkeeping Center (CTBS001) routine—which unifies the bookkeeping process and generates the file for the PVA-FCONT Accounting Validator—has been adjusted. This update includes the creation of CNPJ fields for signatories and the Period Start Indicator (Ind. Inic. Per.) for special situations. To apply this change, it is necessary to re-save the ECDLIVRO_FCONT.XML file.
ID of Ticket
TEEIQI
Products
Microsiga 11
Modules
- SIGACTB
Portals
- none
Countries
- Brazil
Operating System
All
Database
- TopConnect
Name + Source
Bookkeeping Center (CTBS001)
Compatibility Tool Adjustments
Yes
Referential Integrity
No
Patch Application
Compatibility Tool 1
- U_UPDCTB
Implementation Procedures
The system is updated after applying the update package (patch) of this FNC.
The ECDLIVRO_FCONT.XML layout file must be saved in the Protheus %SystemRoot% directory.
Example:
W:\Protheus10\Protheus_Data\system\mp10top\
Before running the U_UPDCTB compatibility tool, 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 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/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!
|
- In Microsiga Protheus TOTVS Smart Client, enter U_UPDCTB in field Initial Program.
To correctly update the data dictionaries, make sure the date on the compatibility program is equal to or after 12/15/2011.
- Click OK to continue.
- 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.
- 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. A explanatory message is displayed on the screen.
- Afterwards, the window Update Completed is displayed with the history (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 save the history (log) displayed.
- Click OK to close processing.
Adjustments Description
8. Data Dictionary (SX3) – Field Creation:
- Table CS0 – ECD Revision:
Field | CS0_SITPER |
Type | Character |
Size | 1 |
Decimal | 0 |
Context | Actual |
Title | Per.Star.Ind |
Description | Period Start Indicator |
Level | 0 |
Used | S |
Mandatory | N |
Browser | S |
Property | Edit |
Order | 17 |
- Table CS8 – ECD Accountants:
Field | CS8_CGC |
Type | Character |
Size | 14 |
Decimal | 0 |
Context | Actual |
Title | CNPJ (EIN) |
Description | Accounting Firm CNPJ |
Level | 1 |
Used | s |
Mandatory | N |
Browser | N |
Property | Edit |
Order | 09 |
Procedures for Configuration
Utilization Procedures
Technical Data
Tables Used | CS0 – ECD Revision, CS8 – ECD Accountants |