Not all CT-e types are generated for the Freight Bookkeeping in the extractor (Doc ID 3058407.1)

Last updated on NOVEMBER 25, 2024

Applies to:

Symptoms

On : 11.13.24.07.0 version, Local Solution for Brazil

The CT-e type is not generated by the extractor for the freight bookkeeping fiscal flow

When receiving a Freight Document in the FDC module, using the freight bookkeeping fiscal flow, the “LACLS_ExtractApSpedData_Incremental” extractor does not generate the CT-e type information. This is mandatory information that must be sent to the tax authorities.

In the XML of the fiscal document, the “tpCTe” tag indicates which type of CT-e is being received. The possibilities are:
0 - Normal CT-e;
1 - Price Complement CT-e;
2 - Price Cancellation CT-e;
3 - Substitute CT-e.

As this information is not generated in the extractor, the fiscal partner is receiving all CT-es with a fixed value of “0”, and this is not correct. All freight documents need to be integrated with the information according to the XML of the fiscal document, tag “tpCTe”.

This problem has a major impact on the customer, given that around 12,000 documents are received each month.

The expected behavior is for the extractor to generate the XML file according to the information in the “tpCTe” tag of the fiscal document's XML.

It is extremely important that we confirm that this field is already mapped for integration with the Fiscal Partner.

The customer's fiscal partner is Synchro.

This problem has an impact on the Go live date, which is November 1st.

I've attached the evidence of the issue in this SR. File name: "Files_241009".

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.