Dynamics 365 CommunityForums Microsoft Dynamics AX (Archived) Cannot create a record...

Cannot create a record in Purchase order history (PurchTableHistory). Insert not supported with the values specified for 'Effective' and 'Expiration'. New record overlaps with multiple existing records

(0) Share

Report

Posted on by Community Member

Dear All,

I am using AX2012 R3. I got the error "Cannot create a record in Purchase order history (PurchTableHistory). Insert not supported with the values specified for 'Effective' and 'Expiration'. New record overlaps with multiple existing records" when I try to cancel Purchase Order.

I did try to remove PO line/ Cancel delivery remainder/ change something in PO but always got above error message.

Does anybody here have experience to solve this issue, please share with me.

I did find the hotfix KB 2901696, but technical team did reviewed the hotfix and found that It’s already included in the R3 version.

*This post is locked for comments

All responses (3)

Answers (1)

Community Member on at

Like (0)

Report

RE: Cannot create a record in Purchase order history (PurchTableHistory). Insert not supported with the values specified for 'Effective' and 'Expiration'. New record overlaps with multiple existing records

Hi nglehang,

Nice, Then mark your post as verified. So it will be useful for other members in future.

Thanks

Suresh
Verified answer

Community Member on at

Like (1)

Report

RE: Cannot create a record in Purchase order history (PurchTableHistory). Insert not supported with the values specified for 'Effective' and 'Expiration'. New record overlaps with multiple existing records

Hi,

I did resolve it by open PurchTableHistory table and delete this PO number, after that I could delete the PO
DAX_ajsqd2 269 on at

Like (0)

Report

RE: Cannot create a record in Purchase order history (PurchTableHistory). Insert not supported with the values specified for 'Effective' and 'Expiration'. New record overlaps with multiple existing records

Hi, we are experiencing the same issue. Were you able to determine the root cause?