To understand this scenario, we use the following example
Example branches.
Origin(D MG 01) -> CNPJ (EIN) -> 65972302000177 / State Registration -> 618599025233
Destination(D MG 02) -> CNPJ (EIN) -> 65972302000177 / State Registration -> 73806611389
Example customers:
We have 2 customers at BRANCH D MG 01 with the following characteristics:
Code | Store | State Registration | CNPJ (EIN): | Branch |
600 | 01 | 618599025233 | 65972302000177 | D MG 01 |
700 | 02 | 618599025233 | 65972302000177 | D MG 01 |
Example supplier:
Code | Store | State Registration | CNPJ (EIN): | Branch |
700 | 01 | Not Applicable. | 65972302000177 | D MG 02 |
Operation of routine:
- Before: Previously, when making a transfer with this scenario, the system always selected the 1st customer with this CNPJ (EIN), if two of them share the same.
- After: Now it uses the State Registration to check which is the right customer when making the transfer, so if the customer desired is 700 02, it finds it based on its registration.
When registering a branch, fill out this field to use this feature:
This will feed table SF2 (Outgoing Invoice with the customer desired as set in parameters).
For further information on the complete process, refer to the FURTHER INFORMATION topic in the link provided.