This chapter contains the following topics:
Ato COTEPE (Ato Comissão Técnica Permanente) refers to a legal reporting requirement in Brazil. Companies subject to the reporting requirement must report via electronic files all of their business transactions that occurred over a period of time. The government defines the period of time (reporting date range), the required information, and file layout.
This table describes the data that companies must report:
| Type of Data | Description |
|---|---|
| Accounts payable and accounts receivable | Transactions between the company and the customers and suppliers are reported in the customer and supplier files. All transactions, such as purchases and sales, that occurred within a period are considered without regard to status. |
| Inventory | The stock entries, such as those for sales, purchases, inventory movement, and manufacturing are reported in the inventory files. This information is grouped by fiscal company. |
| Fiscal books | The information contained in the fiscal documents (notas fiscais) is reported in the fiscal documents files. Documents issued by the company and those issued by the company's suppliers are reported separately. The files are generated and grouped by the fiscal company. |
| General information | General information such as data about suppliers and customers, data about individual and legal entities, business units, and items are included in the electronic files. |
Not all data required by the government resides in the tables provided by JD Edwards EnterpriseOne software. For SPED Fiscal, Oracle provides programming to generate the registers for blocks C, D, E, H, G, 1, 0, and 9.
When you use the JD Edwards EnterpriseOne software to generate the registers for these blocks, the system creates all of the registers for the block, but populates only those registers for which data resides in JD Edwards EnterpriseOne tables.
You must create custom programs to process data that does not reside in the JD Edwards EnterpriseOne tables and write that data to the Electronic Reporting Processing Details table (F76B0512). Your custom programming should include data for:
Registers in blocks C, D, E, H, G, 0, 1, and 9 that are not populated by Oracle programming.
Blocks for which you must report data and that Oracle programming does not generate.
JD Edwards EnterpriseOne tables that you have modified.
You must include your custom programs when you set up sequencing in the SPED Fiscal Block Setup program (P76B0730).
|
See Also:
|
The electronic tax reporting process consists of generating data for reporting and then sending that data to the government.
The data that you generate includes:
Blocks
Blocks include groupings of registers with similar information. For example, block H includes information about inventory.
Registers
Registers include records, which are detailed information for each register. Oracle programming creates all of the registers for the blocks that it generates, but populates the detailed information for only the data that resides in the JD Edwards EnterpriseOne tables.
For example, registers for block H include the inventory total amount (register H005) and inventory quantities of each item (register H010).
Records
Records are the details of the information for the register.
For example, records for items (register 0200) include information about unit of measure and conversion for the items reported at block C and block H.
You use the SPED Fiscal Administ Process program (P76B0840) to generate the blocks, the registers for the blocks, and to populate the records for the registers for which data resides in the JD Edwards EnterpriseOne tables. The Execute Latest Version checkbox enables you to execute the job according to the latest available version or to proceed with the previous version. If you set up the SPED Fiscal Block Setup program (P76B0730) with custom programs, the system also generates block, registers, and records for which you run your custom programs.
After you generate the data, you can review the text file and copy the text files to media that you submit to the government.
To use the tax reporting process provided by Oracle:
Set up the system for tax processing.
Set up blocks and specify the sequencing for the programs to run.
Generate the blocks, registers, and records; and populate the text files.
Review the data generated.
Copy the text files to media to submit for tax reporting.
|
Important: You must set up a single entry job queue to ensure the correct execution sequence of batch applications. If the job queue allows more than one entry, two processes could be executed at the same time, which could cause transactions integrity issues. |
The F76B0512 table exists to store data for the Cotepe register type (data item B76CRTY) and the Cotepe register data type (data item B76CRDT). The Cotepe register type is a code that specifies if a record in the F75B0511 table is for an input (purchase) or output (sales) transaction. The system uses the values for the Cotepe register type to determine the rules that apply to the record, as you set up the rules in the SPED Fiscal Rules Control program.
Values for the Cotepe register data type are:
I: Input record
O: Output record
B: The record is not classified as an input or output record.
U: The record is undefined; there is no data available in the system to classify the record.
The system writes these values to the F76B0512 table for these block C registers:
| Register | Cotepe Register Type (data item B76CRTY) |
|---|---|
| C001 | blank |
| C100 | If C100. IND_OPER = 0, then B76CRTY= I
If C100. IND_OPER = 1, then B76CRTY= O |
| C110 | Value from C100.B76CRTY |
| C111 | U |
| C112 | U |
| C113 | Value from C100.B76CRTY |
| C114 | U |
| C115 | U |
| C120 | U |
| C130 | Value from C100.B76CRTY |
| C140 | Value from C100.B76CRTY |
| C141 | Value from C100.B76CRTY |
| C160 | Value from C100.B76CRTY |
| C165 | U |
| C170 | Value from C100.B76CRTY |
| C171 | U |
| C172 | Value from C100.B76CRTY |
| C173 | U |
| C174 | U |
| C175 | U |
| C176 | U |
| C177 | U |
| C178 | U |
| C179 | Value from C100.B76CRTY |
| C190 | Value from C100.B76CRTY |
| C195 | U |
| C197 | U |
| C300–C390 | U |
| C400–C495 | U |
| C500–C590 | U |
| C600–C690 | U |
| C700–C791 | U |
The system writes these values to the F76B0512 table for these block D registers:
| Register | Cotepe Register Type |
|---|---|
| D001 | B |
| D100–D190 | U |
| D300–D390 | U |
| D400–D420 | U |
| D500 | If D500.IND_OPER = 0, then B76CRTY = I
If D500.IND_OPER = 1, then B76CRTY = O |
| D510 | U |
| D530 | U |
| D590 | The value from D500.B76CRTY |
| D600–D697 | U |
The system writes a value of B for the Cotepe register type to the F76B0512 table for all registers in block E.
The system writes a value of B for the Cotepe register type to the F76B0512 table for all registers in block G.
The system writes a value of B for the Cotepe register type to the F76B0512 table for all registers in block H.
The system writes a value of B for the Cotepe register type to the F76B0512 table for all registers in block 1.
The system writes a value of B for the Cotepe register type to the F76B0512 table for all registers in block 0.
The system completes the Cotepe Register Data Type field in the F76B0512 table with an I (information available) or a D (no data), depending on whether data exists for a register in the F76B0511 table. When you run the SPED Fiscal- Block 9 Control & Join program (R76B0860) as part of the extraction process, the system uses the values in the Cotepe Register Data Type field in the F76B0512 table as part of the validation of whether to include data for reporting, and whether to issue a warning message that data is missing.
When you extract data using the SPED Fiscal Administ Process program (P76B0840), the system populates the fields in the F76B0511 table depending on whether information is available:
If information is available, the system populates the F76B0511 table with the register number in positions 2–5 of the record, followed by the information divided by pipes ( | ). The first position is also filled with a pipe.
For example, for register 0005, the system might write this data for the register to the F76B0511 table:
|0005|Brazilian Company|04569011|Rua Quintana 753–3 Andar, Broklin Novo||3 4||5411 4396927 |||
When the system writes data to the F76B0511 table, it also writes the code I to the Cotepe Register Data Type field in the F76B0512 table.
If no data is available in the JD Edwards EnterpriseOne software, the system populates the F76B0511 table with the register number in positions 2–5 of the records, followed by a series of pipes and blank spaces. The first position is also filled with a pipe.
For example, data for register 0206 does not reside in the JD Edwards EnterpriseOne database tables. For this register, the system would write this value to the F76B0511 table: |0206||||||||||||||||||
Because the field in the F76B0511 table includes only the register number and no other data, the system would write a code of D for the register to the F76B0512 table.