R12.1:JL:GL: JLMXJENT Not Able to Validate the Syntax with SAT Using Mexican Accounting Journal Entries Reporting
(Doc ID 2348237.1)
Last updated on AUGUST 19, 2020
Applies to:
Oracle Financials for the Americas - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.3 version, Mexico GL Globalization
When attempting to validate the syntax with SAT,
the following error occurs.
Error: La version del documento no corresponde a lo especificado en el XSD - Linea 2
Error: Para el atributo 'CtaDest' el dato "no es valido. - Linea 505
Error: Para el atributo 'BancoDestNal' el dato "no es valido. - Linea 505
...
Se concontraron demasiados errores
El documento XML no es valido
CSD del sello SAT: No se proporciono el cerfiticado
...
The issue can be reproduced at will with the following steps:
1. Responsibility: General Ledger - Mexico localization
Applied patch 24513258
JL_MX_JOURNAL_ENTRIES_PKG jlmxjreb.pls 120.0.12010000.18 - latest version
JLMXJENT.xml 120.0.12010000.12 - latest version
JLMXJENT.xsl 120.0.1201.0000.9 - latest version
2. Path: Other -> Requests -> Run
3. Run the Mexican Journal Entries - XML File report
Mexican Journal Entries - XML File report is not working as expected.
Not able to validate the syntax with SAT.
Error: La version del documento no corresponde a lo especificado en el XSD - Linea 2
Error: Para el atributo 'CtaDest' el dato "no es valido. - Linea 505
Error: Para el atributo 'BancoDestNal' el dato "no es valido. - Linea 505
...
Se concontraron demasiados errores
El documento XML no es valido
CSD del sello SAT: No se proporciono el cerfiticado
...
This is the first time implementing SAT reporting.
NOTE:
Though it is an Electronic payment, type of payment is MANUAL.The entity code is also "AP_PAYMENTS". We expect the element to be"OtrMetodoPago" considering the entity code & payment type.
Also, defining bank account makes sense for new payments.
It doesn't work for an existing payment if we set up bank account on supplier. Defining bank account doesn't populate External Bank ID/Account ID in Payments table.
The issue has the following business impact:
Due to this issue, users cannot use the report
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |