Rejection 486 for Bahia and some other regions
There are two rejections happening in the last weeks due to lack of information in the tag group “Authorization to obtain the XML”. The information for the accounting office must be sent in the XML for some regions and when it’s not sent the NF-e is rejected with messages 486 or 487.
The filling of such field is done only via BAdI in the ERP. You can fill it with any of the BAdI’s below:
1- BADI cl_nfe_print -> fill_autxml
2- BADI j_1bnf_add_data -> fill_autxml ( for those who already use the new BAdI )
There is no standard table in the ERP to store such information (CNPJ of the accounting office) so you’ll probably need to store it in a custom table.
In GRC this information is mapped according to the data sent by the ERP. There is not validation in standard GRC to check if this is filled since the validation rule is optional and vary according to the region of the sender.
Thanks Renan for the heads-up!
If it helps other customers, in our ERP solution with help of Felipe Boueri Poroca and Rodrigo Alves & Aline Ferraz we developed a customer master Sales Text that's copied through-out the sales flow (and also can be modified manually in any step of the sales flow, that being sales document, delivery or billing).
This solution is very flexible for business as can be established from the master data process or in the sales process.
Also, it reduces developer team in creating determinations from new Z* tables and rather working with standard configuration that any Business Analyst with some SD experience can supervise.
Only developer point is at BAdI to determine the text from table STXL with function standard FM READ_TEXT.
That's an interesting solution.
Other possibilities would be to use the CNPJ of accounting office as a kind of "master data":
1- It could have been added as a parameter V_T001I and had a value assigned in T001Z which would be assigned to the company code.
2- Besides that another solution more flexible would be to create a TVARV parameter like "AUTXMLCNPJEMISSOR" and assign the respective CNPJ values to it to read inside the BAdI.
The disadvantage is that in case of a change a parameter would need to be adjusted. Both options would not be flexible for changes within the application during the sales flow ( like your solution is ).
Thanks Renan, did not know those other possibilities.. thanks for sharing them 🙂