Páginas filhas
  • Subsidiary Ledger – Filter by Balance Type – 115606

Versões comparadas

Chave

  • Esta linha foi adicionada.
  • Esta linha foi removida.
  • A formatação mudou.

Subsidiary Ledger – Filter by Balance Type – 115606

Technical Bulletin: Subsidiary Ledger – Filter by Balance Type
Occurrence
Improvement
Summary
The report routine Subsidiary Ledger (ATFR130) was implemented in the Fixed Asset (SIGAATF). It allows filtering the report by type of balance and type of Asset information into three types: Tax, Managerial, or Encouraged. To allow the separation of the types of balances that are controlled by the Fixed Asset Module (SIGAATF), the tracking fields Balance Type and Type of Asset were created in the tables: SN5 - Balance Files, SN6 - Balance by Account and Item, SNA - Account x Item x Cl Value Balances and SNC - Account x Cost Center Balances of accounting balances. An adjustment was performed in routine Redo Balances (ATFA120) for this feature.
ID of Ticket
TDQVWX
Products
Microsiga 11
Modules

...

Name + Source
ATFA120 – Redo Balance; ATFR130 – Subsidiary Ledger
Compatibility Tool Adjustments
Yes
Referential Integrity
No
Patch Application
Compatibility Tool 1

  • UPDATF


Implementation Procedures

Before running the compatibility tool UPDATF, you must:

a) Back up 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 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 tool with Referential Integrity deactivated{*}.
 

 
 
The following procedure must be performed by a professional qualified as a database administrator (DBA) or equivalent!
 
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:
 
                          In the Configuration Tool (SIGACFG), check whether the company uses Referential Integrity by selecting the 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 the 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 such integrity by selecting the 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_UPDATF in the Initial Program field.

To correctly update the data dictionaries, make sure the date on the compatibility program is equal to or after 12/07/2011.

Click OK to continue.

The first step of the execution is file preparation. An explanatory message is displayed on the screen.
Then, an Update finished window is displayed with all the processed updating history (log). In this updating log, only the fields updated by the program are presented. The compatibility tool creates fields that do not exist in the data dictionary yet.

Click Save to save the log displayed.

Click OK to close processing.

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

Adjustments Description

1. Creation in file SX1 – Questions:

...

  • Group AFR130:

Group

AFR130

Order

14

Question

Balance Type?

Type

C

Size

1

Object

G

Stand. Query

SLD

...

Group

AFR130

Order

15

Question

Display information ?

Type

N

Size

1

Object

C

Item 1

Tax

Item 2

Managerial

Item 3

Encouraged

Item 4

All

 
2. Creation in file SX3 – Fields:

...

  • Table SN3 - Balances and Values:

Field

N3_TPSALDO

Type

C

Size

1

Decimal

0

Format

@!

Title

Type of Balance

Description

Type of Balance

Used

Yes

Options

#AdmCBGener(xFilial("SX5"),"SX5","SL","01")

Edition Mode

ADD

Relation

'1'

Val. System

VldTpSald( M->N3_TPSALDO )

...

  • Table SN5 - Balance Files:

Field

N5_TPSALDO

Type

C

Size

1

Decimal

0

Format

@!

Title

Type of Balance

Description

Type of Balance

Used

Yes

Ownership

View

 
 

Field

N5_TPBEM

Type

C

Size

2

Decimal

0

Format

@!

Title

Asset Type

Description

Asset Type

Used

Yes

Ownership

View

...

...


  • SN6 - Balances by Account and Item

Field

N6_TPSALDO

Type

C

Size

1

Decimal

0

Format

@!

Title

Type of Balance

Description

Type of Balance

Used

Yes

Ownership

View

 
 

Field

N6_TPBEM

Type

C

Size

2

Decimal

0

Format

@!

Title

Asset Type

Description

Asset Type

Used

Yes

Ownership

View

...


  • SNA - Value Cl x Item x Account Balances:

Field

NA_TPSALDO

Type

C

Size

1

Decimal

0

Format

@!

Title

Type of Balance

Description

Type of Balance

Used

Yes

Ownership

View

 

Field

NA_TPBEM

Type

C

Size

2

Decimal

0

Format

@!

Title

Asset Type

Description

Asset Type

Used

Yes

Ownership

View

...


  • SNC - Cost Center x Account Balances:

Field

NC_TPSALDO

Type

C

Size

1

Decimal

0

Format

@!

Title

Type of Balance

Description

Type of Balance

Used

Yes

Ownership

View

 
 

Field

NC_TPBEM

Type

C

Size

2

Decimal

0

Format

@!

Title

Asset Type

Description

Asset Type

Used

Yes

Ownership

View

 
3. Change of Indexes in file SIX – Indexes:

Index

SN5

Order

1

Key

N5_FILIAL + N5_CONTA + DTOS(N5_DATA) + N5_TIPO + N5_TPBEM + N5_TPSALDO

Description

Account Code + Balance Date + Record Type+Asset Type+Balance Type

Display Search

Yes

...

Index

SN6

Order

1

Key

N6_FILIAL + N6_CONTA + N6_CCUSTO + N6_SUBCTA + DTOS(N6_DATA) + N6_TIPO + N6_TPBEM + N6_TPSALDO

Description

Account Code + Cost Center + Account Item + Date + Transaction Type+Asset Type

Display Search

Yes

...

Index

SNA

Order

1

Key

NA_FILIAL + NA_CONTA + NA_CCUSTO + NA_SUBCTA + NA_CLVL + DTOS(NA_DATA) + NA_TIPO + NA_TPBEM + NA_TPSALDO

Description

Account Code + Cost Center + Account item + Value Class + Date + Type

Display Search

Yes

 
 

Index

SNC

Order

1

Key

NC_FILIAL + NC_CONTA + NC_CCUSTO + DTOS(NC_DATA) + NC_TIPO + NC_TPBEM + NC_TPSALDO

Description

Account Code + Cost Center + Date + Transaction Type+Asset Type+Balance Type

Display Search

Yes

Procedures for Configuration

Procedures

To update the balances of the transactions already carried out, it is recommended to perform the routine Redo Balance (ATFA120) in Fixed Assets (SIGAATF), access Miscellaneous\Adjustments\Redo Balance, and set the Consider? parameter to Transactions.

  1. In Fixed Assets (SIGAATF), access Report/Transactions/Subsidiary Ledger (ATFR130).

...

  1. The following parameters are displayed:

      ...

        1. Balance Type? - Enter the type of balance for the report. This balance type refers to the Balance Type field (N3_TPSALDO). If all balance types are chosen, enter *{}.

      ...

        1. Display information? – Enter the type of assets that is demonstrated in the report.

      ...

        1. Tax – The balance moved by the tax asset types is presented (01, 02, 03, 04, 05, 06, 07, 11, 13)

      ...

      ...

        1. Managerial - The balance moved by the managerial/accounting types is presented (10, 12, 17, 4x, 5x)

      ...

        1. Encouraged - The balance moved by the depreciation incentive asset types is presented (08, 09)

      ...

        1. All – the balance of the accounts is demonstrated in a consolidated manner.

      3. Fill out the fields according to field help instructions.

      4. Confirm to generate the report.

      Technical Data

      Tables

      SN3 – Balances and Amounts
      SN5 – Balance Files

      Notes