Option Conf. Troubleshooting is an interface that enables to direct conflict invoices to a correct branch. By selecting a destination branch to the invoice, you will be able to save such preferences and on the next time that an invoice arrives for importing (with recipient CNPJ, invoice type, supplier and store), it will be automatically imported on the destination branch and will not be referred to the conflict troubleshooting directory. The item Edit Pref. will be available as well, which allows to edit, delete and add import preferences.

This way, you will be able to specify invoices for the branch desired when there is more than one branch with the same CNPJ and it is unable to determine (by CNPJ and not even by State Registration) where the invoice must be imported, thus, this procedure prevents the XML to be idle on folder XMLNFE/NEW.

Help_button Important

To use this feature you need to enable the parameter MV_XMLSOLU and run schedule SCHEDCOMCOL to create the folder SOL (conflict troubleshooting) on structure XMLNFE/SOL.

When the schedule identify invoices to import, whose recipient CNPJ is doubled, it will no longer be idle on folder NEW and will be moved to the conflict troubleshooting directory SOL and there will be workflow submit with the message: “More than one branch that corresponds to the recipient of this invoice was found. The XML file was moved to the conflict troubleshooting directory.”



Procedures

  1. The procedure is valid when there is more than one branch with the same CNPJ on SIGAMAT and is unable to specify the invoice recipient branch by CNPJ and not even by State Registration.
  2. Enable a XML invoice file on folder XMLNFE/NEW with the recipient CNPJ equal to what is doubled on SIGAMAT so that it is imported by TOTVS Collaboration schedule (SCHEDCOMCOL).
  3. Configure schedule of TOTVS Collaboration (SCHEDCOMCOL) to process branches with doubled CNPJs.
  4. Start schedule and wait for file import.
  5. Check the folder SOL (of conflict troubleshooting) creation on structure \XMLNFE\SOL.
  6. If m-messenger is configured to submit inconsistency (052) and imported invoices (053) workflows, check the inconsistency email informed on message: “More than one branch that corresponds to the recipient of this invoice was found. The XML file was moved to the conflict troubleshooting directory.”
  7. See that XML file was moved to folder XMLNFE\SOL.
  8. On Purchase module access the TOTVS Collaboration
  9. When confirming the parameter screen, check the message that flags the existence of files on the conflict directory that need to be specified for the branch desired and if the action must be performed in this moment.
  10. Click Yes to troubleshoot conflicts.
  11. An interface is displayed with the XML file present on file XMLNFE/SOL to be directed in a branch.
  12. Select the file and on the Related Actions option activate Dest.Brn (select destination branch).
  13. Select a branch to specify the invoice and click OK.
  14. Click OK on the message that guides regarding the need to confirm the following screen to process files.
  15. Click Confirm and note the message that indicates that invoices will be imported on the branch selected.
  16. Confirm to import invoices. If there is no Supplier registration on the base or bonding Product x Supplier, the inconsistency will be submitted and, in this case, you only need to correct ir according to indicated and repeat process. With records performed, the invoice will be imported and a message will be displayed asking if you wish to save preferences. An e-mail will be submitted regarding invoice import on the selected destination branch as well.
  17. Click Yes to confirm and save information. This way, by the next time that an invoice arrives for importing with recipient CNPJ, invoice type, supplier and store, it will be automatically imported on the destination branch and will not be referred to the conflict troubleshooting directory.
  18. Check invoices imported on the branch selected on TOTVS Collaboration
  19. In Related Features, select option Troubleshooting and then, click Edit Pref. to access interface of preferences configuration that enables to add, edit and delete import preferences.
  20. Delete the invoice imported on the TOTVS Collaboration monitor and enable again the XML file on folder XMLNFE/NEW so that it can be imported again.
  21. Wait for file processing by schedule of TOTVS Collaboration (SCHEDCOMCOL) and note that the file was automatically imported on branch previously configured on the conflict troubleshooting option.