Histórico da Página

Pagetitle

	Fields in Fixed Assets for use in PISCOFINS Tax SPED
	Fields in Fixed Assets for use in PISCOFINS Tax SPED

Technical Bulletin: Fields in Fixed Assets for use in PIS/COFINS Tax SPED

Occurrence

Improvement

Summary

We have implemented improvements to routines Fixed Assets (ATFA010) and Asset Group (ATFA270) with the creation of fields Asset Identif. (N1_DETPATR/NG_DETPATR) and Asset Use (N1_UTIPATR/NG_UTIPATR) to identify and classify assets to be used in PIS/COFINS Tax SPED. We have also created the Standard Queries SN011 and SN012, to be used in fields Asset Identif. (N1_DETPATR/NG_DETPATR) and Asset Use (N1_UTIPATR/NG_UTIPATR), respectively.

ID of Ticket

SDLWPV

Products

Microsiga 11

Modules

SIGAATF

Portals

none

Countries

All

Operating System

All

Database

All

Name + Source

Fixed Assets (ATFA010); Asset Group (ATFA270)

FNC Number

00000010666/2011

Compatibility Tool Adjustments

Yes

Referential Integrity

No

Patch Application

Compatibility Tool 1

- U_UPDATF

Implementation Procedures

Important:

Before running the U_UPDATFcompatibility tool, you must:

a) Backup the database of the product where the compatibility tool will run (“\PROTHEUS_DATA\DATA” directory) and SX 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 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*.

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 tool is equal to or after 5/27/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.

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.

5. Click Save to keep the log displayed.

6. Click OK to close processing.

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

Adjustments Description

1. Creation in file SX3 – Fields:

- Table SNG - Asset Groups

Field	NG_DETPATR
Type	Character
Size	2
Decimal	0
Format	@!
Title	Asset Identif.
Description	Asset Identification
Level	1
Used	Yes
Required	No
*Browser*	Yes
Val. System	Vazio().OR.ExistCpo('SN0','11'+M->NG_DETPATR)
*Help*	Identify the asset incorporated to Fixed Assets.

Field	NG_UTIPATR
Type	Character
Size	2
Decimal	0
Format	@!
Title	Asset Use
Description	Asset Use
Level	1
Used	Yes
Required	No
Browser	Yes
Val. System	Vazio().OR.ExistCpo('SN0','12'+M->NG_UTIPATR)
Help	Classify it in accordance with Asset use.

Field	N1_DETPATR
Type	Character
Size	2
Decimal	0
Format	@!
Title	Asset Identif.
Description	Asset Identification
Level	1
Used	Yes
Required	No
*Browser*	Yes
Val. System	Vazio().OR.ExistCpo('SN0','11'+M->N1_DETPATR)
*Help*	Identify the asset incorporated to Fixed Assets.

Field	N1_UTIPATR
Type	Character
Size	2
Decimal	0
Format	@!
Title	Asset Use
Description	Asset Use
Level	1
Used	Yes
Required	No
*Browser*	Yes
Val. System	Vazio().OR.ExistCpo('SN0','12'+M->N1_DETPATR)
*Help*	Classify it in accordance with Asset use.

2. Creation of Standard Query on file SXB – Default Query:

- Survey SN011

Alias	SN011
Type	1
Sequence	01
Column	DB
Description	Generic Table
Contains	SN0

Alias	SN011
Type	2
Sequence	01
Column	01
Description	Table + Key

Alias	SN011
Type	3
Sequence	01
Column	01
Description	Register New
Contains	01

Alias	SN011
Type	4
Sequence	01
Column	01
Description	Table
Contains	N0_TABELA

Alias	SN011
Type	4
Sequence	01
Column	01
Description	Key
Contains	N0_CHAVE

Alias	SN011
Type	4
Sequence	01
Column	03
Description	Description
Contains	N0_DESC01

Alias	SN011
Type	5
Sequence	01
Contains	SN0->N0_CHAVE

Alias	SN011
Type	6
Sequence	01
Contains	SN0->N0_TABELA ="11"

- Survey SN012

Alias	SN012
Type	1
Sequence	01
Column	DB
Description	Generic Table
Contains	SN0

Alias	SN012
Type	2
Sequence	01
Column	01
Description	Table + Key

Alias	SN012
Type	3
Sequence	01
Column	01
Description	Register New
Contains	01

Alias	SN012
Type	4
Sequence	01
Column	01
Description	Table
Contains	N0_TABELA

Alias	SN012
Type	4
Sequence	01
Column	01
Description	Key
Contains	N0_CHAVE

Alias	SN012
Type	4
Sequence	01
Column	03
Description	Description
Contains	N0_DESC01

Alias	SN012
Type	5
Sequence	01
Contains	SN0->N0_CHAVE

Alias	SN012
Type	6
Sequence	01
Contains	SN0->N0_TABELA ="12"

Utilization Procedures

1. In Fixed Assets (SIGAATF) access Updates/Registers/Fixed Assets (ATFA010).

2. Select an asset and click Edit.

3. In folder Others, press the <F3>key in field Asset Identif.

The system displays the standard query SN011 - Table 11 for asset identification.

4. Select an identification for the asset.

5. Enter the other data in accordance with field help instructions.

6. Check and confirm the data.

Note:

The procedure to use the routine Asset Group (ATFA270) is the same as for routine Fixed Assets (ATFA010).

Technical Data

Tables

SN1-Fixed Assets; SNG-Asset Groups

Páginas filhas

Versões comparadas

Versão antiga 1

Nova versão Atual

Chave