By using this website, you agree to our Terms of Use (click here)
We have setup a vendor and used the action of "Extend to Customer" to link the customer and vendor; however, we would like to undo this action. I have been going through the help files, and I cannot find any information on how to unlink a Customer and Vendor. It is not an available Action on either the Customer or Vendor.
Can anybody point me in the right direction towards figuring out how to unlink Customer and Vendor?
Have you tried deleting the undesirable customer or vendor?
I cannot delete the undesirable vendor since they are one of our primary vendors and have been involved in many transactions (as a vendor, not as a customer). The mistake was linking them to a customer instead of creating a separate customer.
We have several companies under a single tenant that are sharing a vendor list; however, we need to have this vendor as an independent customer for each of the companies that sell to them because of the differences in how each company interacts with this company.
Essentially, I need to unlink their VENDOR<-->CUSTOMER relationship so the VendorID isn't showing up as a CustomerID.
Not sure I understand. If the vendor and customer share the same ID, they MUST be the same Baccount, otherwise the system would not let you use the same ID. If they do not share the same ID, you would not able to extend to each other anyway.
In other words, if the ID is the same, the vendor and customer are by definition and extension of each other.
That said, I may be missing the point of what you are trying to do, and unfortunately I do not have a solution to you core question - How to unlink the vendor- customer relationship.
I didn't do a great job explaining it because our environment is probably a little unconventional; however, our integrators agreed that we need to separate them. We're just not sure how.
Essentially, we have (3) companies on a single tenant. Company A, Company B, and Company C.
All of our vendors have a (4) digit vendorID. All of our customers have a (5) digit CustomerID.
All (3) of our companies buy products from Vendor, and we only need to have a single Vendor to purchase products from for all (3) companies.
All (3) of our companies also sell products to this Vendor; however, setting them up as a single customer for all (3) to sell to will cause us a massive headache. Instead, it would be better for us to set them up as (3) separate customers--(1) for each of Company A, Company B, and Company C to sell too.
Unfortunately, I hit "Extend Vendor to Customer" before I realized the headache that was going to introduce. I'd like to "Unextend" the Vendor from it's Customer counterpart.
The explanation might not make a ton of sense; however, this seems like it should be a simple operation. there's no option for it though.
I see. I doubt there is a way to do unlink, although you can probably mark the customer only as inactive and create the 3 new customers instead.
Unfortunately, marking the customer as inactive also marks the linked vendor as inactive.
I'll lean on our integrators to see if they can find a solution. This seems like an oversight on Acumatica's behalf. Thanks for taking the time to read through my question, Ellie.
Good luck!
No problem.
Extend to Vendor takes the current vendor details and creates a NEW customer using those details.
If you don't need the customer, just delete it.
I also confirmed that Inactivating the Customer also inactivates the Vendor, which is kinda weird. But deleting the customer had no bearing on the vendor.
@royce-lithgo
Royce, I gave it a shot trying to delete the customer in a test environment, but I was unable to do so. It shows that Customer 1040 is part of other tables--even though the only other tables it is part of has to do with the Vendor. There are no sales orders or anything associated with Customer 1040. There are Purchase Orders associated with Vendor 1040.
I also modified the Generic Inquiry on the Customer and Vendor screens to show Customer --> BAccountID and Vendor --> BAccountID. Both of these show that the Customer and Vendor 1040 have an identical AccountID of 7208.
So I don't believe that I can simply remove the Customer 1040 if it is linked to a Vendor 1040 that has transactional history tied to it.
It worked fine for me when i deleted the customer created from "Extend to Customer" action. Something else must be going on in your instance. Have you reported it to Acumatica?
It worked fine for me when i deleted the customer created from "Extend to Customer" action. Something else must be going on in your instance. Have you reported it to Acumatica?
Are you using a vendor with existing transactional data?
For example, I just tried this again in a sample Acumatica environment with the basic filler sample data. Take vendor "EDPOWER" and select "Extend to Customer". Then try to delete the customer--I don't believe you'll be able to because it has Checks and Payments associated with the vendor despite there being no activity related to the customer. It's only related to the Vendor.
In the same environment, I created a new vendor (TESTVEN) with no transactional data tied to it. Then I hit "Extend to Customer". I was able to immediately delete the Customer (TESTVEN) without deleting the vendor. Good!
However, I recreated the customer with "Extend to Customer". Then I put in a Purchase Receipt for the Vendor (TESTVEN). I was no longer to delete the Customer (TESTVEN) because the Vendor had transactional data associated with it.
Soooooo... as far as I can tell, the customer and vendor are not separate entities and cannot be unlinked.
I have reported it to our integrators and requested that they open a ticket with Acumatica (since it's not something I believe I can do myself). I haven't heard anything back in about a month of waiting.
I have reproduced your issue on another Vendor which had an open balance. I cannot delete the Customer record Extended from the Vendor.
1: Document (Debit Adj., BIL001891), PX.Objects.AP.APRegister - Foreign key APRegister(vendorID) references BAccount(bAccountID), with Restrict-behavior, achieved by DeclareReferenceAttribute
2: Purchase Receipt (Receipt, POR000021), PX.Objects.PO.POReceipt - Foreign key POReceipt(vendorID) references BAccount(bAccountID), with Restrict-behavior, achieved by DeclareReferenceAttribute
3: Purchase Ord ... (see full message text in the details section)
Tried the same thing on our 2019.1 test environment and also couldn't delete the Customer.
This really makes no sense. Can't see the logic in having referential integrity rules between customer and vendor tables. Think you need to follow up with your integrators.
@royce-lithgo
Royce, I really appreciate you taking the time to test this out. Acumatica is still very new to me, and I was really hoping it would be something obvious I was missing.
I'll follow up again with the people we're working with.
Just as a final update to this--Acumatica applied and ran a fixing script to remove the "Extended" Customer from the Customer Master. It is not something that they have built into the product yet, but they "may do so in the future". So, it's resolved to an extent.
We will be hiding the "Extend to Customer" and "Extend to Vendor" Action Options on the Vendor and Customer screens for our employees, so this shouldn't be recreated in our environment. If this is a worry for anyone else, I'd consider doing the same until Acumatica implements a procedure for "Un-Extending" the entities.
Glad to hear that there is a script to fix this. Probably one of those things where putting it on the front-end isn't a high priority since there is a workaround and maybe not that many people have encountered the situation.