Ansicht
Dokumentation

J_1BLFB1 - IN68: Cadastros, Dateien und Tabelas

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Description

This report creates the legal files following the Instrução Normativa 68 (IN68). Depending on the selections of the user, it reads and extracts the legal documents and/or internal FI documents and/or internal MM documents, that have been posted during the selected period. In addition to that, masterdata of the respective business partners and sytem tables describing the codes used in the other files can be read and extracted to provide the Cadastros and/or Tabelas required by the law.

When the asset accounting files are selected, all assets of the chosen company code are reported at least once. The date of this record will be the first day of the chosen period. If any of the data has changed within the period, or if there has been any transaction within the period, further records will be created.

Requirements

Mandatory selection criteria:

1. Objects to be generated:
1. Cadastros .... generates the Cadastros containing master data of the business partners
2. Files .... generates files concerning
   - Notas Fiscais
   - FI documents
   - MM documents
   - Bills of material
3. Asset accounting files
   .... generates files concerning
   - Asset accounting
4. Tabelas .... generates the system tables with the explanations of the codes used in the Cadastros and Files (e.g. Chart of accounts, movement types etc.)
2. Nota Fiscal selection criteria:
1. Company Code ... of the company that issues the file(s)
2. Business place ... the company's business place that issues the file(s)
3. Movement date ... first and last date of the reporting period
3. Output control:

Enter either the path and name of the files you want the program to download the data to or mark the checkbox 'testrun', which results in an output on the screen only (without issuing a file).

Please note the following:

1. If you run the program online, the system will stop the output after each type of file. To proceed to the next file type, please press either the 'BACK' or the 'EXIT' button, until all chosen files have been processed. This is not necessary, if you download the files (see b) above) and start the report via background job.
2. If you want to download the files to the application server, please fill the fields
   
   

File address ... with the physical address and the 'leading letters' of the name (e.g. '/tmp/in68') (note also the remarks below!)

File extension ... with the file extension (e.g. '.txt')

In the example given here, the program will then issue the respective files of IN68 in the directory 'tmp' in the following form:


- File 1.1 will have the name in68_11.txt,
- File 4.1 will have the name in68_41.txt,
- etc.

Please note that the extensions _xyz will be generated automatically.

Creating and using IN68 files

This report will select all data from the database according to the selection criteria. Please note, that when data from a long time ago are wanted, they might not be in the database any more but could be archived already. Thus, these data could not be reported. Therefore the following procedure is recommended:

Instead of running the IN68 report only when the tax authorities ask for specific data, the report should be run regularly. Then when asked for specific data, you can use the existing files and extract the data from them. (Extracting software is not delivered by SAP.)

It is important to run IN68 regularly without any interruptions. If the last file contained data until the last day of January, the next run should have the first day of February as starting date.

This procedure has a second advantage. For some data, no change documents are maintained within the system. If these data are changed, the old data cannot be retrieved. But with the regular use of the IN68 report, the old data will be in the files which were created before the change was performed.

Example: A company runs IN68 once a month from January 1998 onwards. In July 1999 the tax authorities demand all asset accounting data for the period May until August 98. The company extracts the data from the files which have been created in May, June, July and August 98.

General file information

Each record in the files will end with a carriage return.

Format changes of this version

In the previous version of the IN68 report not all records in the files had the maximum length. If the last field was alphanumeric and there were blanks at the end, those blanks were omitted when transfering the records to the files. Now all records have the same length. Blanks at the end of a record will be inserted into the file.

Differences between suggested type and the type in the system

The fields 'document type' 'type of operation' 'unit of measure' and 'state' are alphanumerical fields in the system. The suggested type is numeric. The following fields are affected:

(All item numbers are according to the SAP format. They are different from the suggested item numbers, if additional fields have been inserted, see below.)

File Item Description of the field

2.1 7 document type

3.1 2 "

3.2 2 "

3.3 2 "

3.4 2 "

3.5 2 "

3.10 2 "

3.11 2 "

3.12 2 "

3.13 2 "

4.1 2 "

6.3 9 "

1.1 6 type of operation

2.1 4 "

4.1 17 "

3.3 16 unit of measure

3.9 7 "

3.11 16 "

4.2 6 "

5.1 6 "

5.2 7 "

8.1 14 state

Differences between suggested size and SAP system size in field length

The IN68 law suggests sizes for all fields in the files.

Nevertheless, it allows to use different field sizes. This is necessary to preserve data integrity if the system used works with different field sizes. However, if different field sizes are used, they must be reported to the tax authorities.

The documentation of the changes in IN68 field sizes can be found below. Please check the online service system for the most up to date information.

8.1 Person/Company cadastro

Item Field Suggested Size SAP Size
3 Person/Company code 9 10
12 District 20 35
14 State 2 3
15 CEP 8 9

8.2 Codes (structure)

Item Field Suggested Size SAP Size
4 Description 45 121

8.3 Tabela de Códigos

Here there is no suggested field size. Each record has a total size of 30 characters plus the carriage return at the end.

In the SAP format there are two additional entries in this table:

table 31: Plant

table 32: BOM usage

This tables are necessary to specify the extra-fields of files 5.1 and 5.2 (see below).

1.1 Postings

Item Field Suggested Size SAP Size
6 Type of operation 3 4
10 Complementary history 45 50

2.1 NF header data per vendor/customer

Item Field Suggested Size SAP Size
4 Type of operation 3 4

3.1 NF header data/total values/goods/saídas

Item Field Suggested Size SAP Size
8 Document continues on file
code number 1 2

3.2 NF header data/freight data/goods/saídas

Item Field Suggested Size SAP Size
17 Vehicle number plate 17 20

3.3 NF item data/goods/saídas

Item Field Suggested Size SAP Size
8 Item number 5 6
14 Type of operation or
Complementary code 3 4
27 Federal Tributary Situation 1 5

3.4 NF header data/services/saídas

Item Field Suggested Size SAP Size
8 Document continues on file
code number 1 2

3.5 NF item data/services/saídas

Here one additional item is inserted.

Item Field Suggested Size SAP Size
8 Item number 0 6

3.10 NF header data/goods(or conhecimentos between different states

or countries)/entradas

Item Field Suggested Size SAP Size
8 Document continues on file
code number 1 2

3.11 NF item data/goods(or conhecimentos between different states

or countries)/entradas

Item Field Suggested Size SAP Size
8 Item number 5 6
15 Type of operation or
Complementary code 3 4
27 Federal Tributary Situation 1 5

3.12 NF header data/services(or conhecimentos in the same state)/

entradas

Item Field Suggested Size SAP Size
8 Document continues on file
code number 1 2

3.13 NF item data/service(or conhecimentos in the same state)/entradas

Here one additional item is inserted.

Item Field Suggested Size SAP Size
8 Item number 0 6

4.1 Goods movements

Here one additional item is inserted and one item size is changed.

Item Field Suggested Size SAP Size
10 Unit of measure 0 3
17 Type of operation 3 4

5.1 Products using input materials

Here three additional items are inserted. For two of them, there are new tables in table 'Tabela de Códigos' (tables 31 and 32). For the new field 'Alternative BOM' no table is needed, as this is only a counter used to distinguish between alternative methods to produce the output material.

Item Field Suggested Size SAP Size
2 Plant 0 4
3 Usage BOM 0 1
4 Alternative BOM 0 2

5.2 Input materials used in products

(Output products <-> Input materials)

Here three additional items are inserted.

Item Field Suggested Size SAP Size
2 Plant 0 4
3 Usage BOM 0 1
4 Alternative BOM 0 2

6.2 Auxiliar File for Depreciation Suspension Information

One additional item is inserted.

Item Field Suggested Size SAP Size
1 Company code 0 4

6.3 Asset registration file

One additional item is inserted and four field sizes have been adjusted.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 14979 Date: 20240520 Time: 095622     sap01-206 ( 156 ms )

Item Field Suggested Size SAP Size
2 Company code 0 4
4 Asset identification 45 50
10 Acquisition document number 12 16
11 Serial number 12 18
17 Depreciation index 5 7