why wont these parts go away. They were created by the system and not any user here.
good part number
https://elecaccnew.cetecerp.com/part/23487/inventory
bad parts number that i cant delete or merge (get error messages)
https://elecaccnew.cetecerp.com/part/33233/inventory
https://elecaccnew.cetecerp.com/part/33185/inventory
copy of the error message
What do you mean by “I can’t delete” a part? Perhaps this helps:
To @cayma’s point, is there a specific reason you’re trying to merge those parts instead of just editing and deleting/inactivating them?
es, some how the inventory is under the bad part number and needs to be moved over the the good part number. somethign happen when creating the all four POs from the MRP. Somehow the MRP created a new number instead of keepign the orginal part number. Then the good part number kept showing a demand on the MRP and everytime a PO was created from the MRP, it put it under the bad part number. We ordered this part four times befroe we figured out what was happening. There is a problem with this part number for some reason. At the end of the day i need all the data to be in one part number.
i had to manually change the three open POs to the good part number.
did you not read my orginal message where i should you the error message? I know how to deleted and merge parts.
Have you attempted to merge this part multiple times? According to our engineers, that error message seems to indicate that a merge was started and interrupted, but that left some data stuck in limbo that is preventing the merge from completing now.
They’ve tried to clear that blockage, and hopefully you’re able to merge that part now. If not, can you please provide us the exact prcparts your merging from and to, the steps your taking, and any other errors/messages you’re seeing when you try to merge.
Thanks!
i just tried merging again. Here is the error message i got this time.
This is what i am trying to merge.
I think there is something bigger than the merge issue. I cahnge the POs to the correct part and when we receive it in, it went under a different part number. There is something funky with the orginal part number. Just to reiterate, the two bad parts we did not create. The system auto-created them from the MRP.
Another question to help us identify what’s happening:
Are you using the new or old version of the part module when doing this?
You will be able to tell, from the merge page, based on the link at the top that will say either Use Old or Use New version (meaning you’re using new or old respectively), or you can look at the URL of the browser and it will either say “…com/part/…” or “…com/react/part…” where the presence of react indicates the new version.
new
Could you swap to the old version of the page and try there?
i cant change back. Option not available
This part is causing a lto fo problems for us. Can you please merge them all into one?
You may have to go to the main part/inventory page, switch to old from there, and then go back to the merge page and attempt the merge again.
Please let us know if you still have issues with the merge from the old version of the page.
merge still failed.
can you pelase just merge this and fix this problem. I dont have time to keep messing around with this.this is causing major problems. major dollars.
You’re absolutely right. Engineering identified that the root of this problem is that there was a special character in the prcpart of the part you’re trying to merge the others into. While invisible to the user interface, it can be seen in the value stored in the database and is likely leading to most of the problems referenced in this thread. You can see the prcpart with the offending characters in this image they shared, represented by the question marks indicating the database is unable to display those characters:
We are currently working on finding the best way to address this bad data, and we will let you know once a solution has been found. In the meantime, are you able to provide any insight in to how that part was created in your system? The most likely case is that the part number was copy/pasted from another application/source that introduced that invisible character, which went unnoticed until issues started arising. Any information you have there will help us in trying to prevent issues like this in the future.
Thanks!
Can you pelase merge the three parts together. We have inventory in two of the three numbers and the invneotry isnt in the correct one and therefore we cant make a shipment becuase the reciepts wont go into the correct part.
We generate all pquotes from the MRP. Both of these parts were created when we check the box in the MRP screen and clicked add to pquote.
At the end of the day, i really need the parts merged. Please let me know when this is done.
just following up on when this part will be merged since i can not do it.
Hi @ElectricalAccess ,
As I was hoping to convey before, this is a more complex issue than the symptoms yo’ure experiencing would have you believe. Our engineering team is actively working towards a resolution, and we will definitely update you once one has been reached. But in the meantime there’s nothing we can do to expedite the process, unfortunately. The same special character problem that is preventing you from merging those parts also means that we don’t have any secret/special way to force the merge to happen.
The current goal is to rework the merge function to try to account for the special characters, so that you will be able to move forward with merging these, and any other parts potentially affected by similar issues, on your own. I will let you know when that work has been done and when you can expect to see it in your environment.
Thank you!
Great news! Our engineers were able to iron out a good path forward, and a fix should be out to you early next week. We’re going to keep an eye on that, and will confirm here with you once it’s in place.
I did want to let you know that the fix they’ve come up with is specifically designed to allow you to merge a part where the prcpart contains those special characters into another part that doesn’t contain them. The reason for that is those special characters will continue to cause issues in other areas of the system if allowed to continue to be used, so when that’s the case they need to be merged into a different part record that can be used safely.
The reason I mention this is because if you’ll look at the screenshot I sent ealier of the 3 parts from your database, ID 23487 is actually the part you’ve said you want to merge the others into. Unfortunately even with this fix in place you won’t be able to do that. But you will be able to merge that one into 33185, which appears to already have the same prcpart string but without those special characters. There may be some part specific data that doesn’t carry over through the merge, like the part description. But that should make it so that all your transaction history, inventory, etc, end up with part 33185 and that part is able to be used throughout the system without creating other issues.
Like I said, I’ll let you know once I’ve confirmed that fix in in place for you and you can give it a try!
@ElectricalAccess I can confirm that this fix is in your system now. To verify, and to ensure no issues arose during the merge, our engineering team went ahead and erformed the merge of those 3 parts records for you. The consolidated part data can now be found at https://elecaccnew.cetecerp.com/part/33185/inventory. They also went ahead and manually copied over some of the data that was on the bad part record that wasn’t present there, like the description and prefered vendor.
Hopefully that resolves this issue for you moving forward. Please let us know if you have any additional questions about it.
Thank you!
Great News
