Dynamics Community Forum Thread Details

Direct SQL Update to Last_Originating_Cost

I am investigating whether or not it is safe to directly update Last_Originating_Cost in SQL.

When suppliers update their pricing they send me 50-1000 item numbers to update pricing for. It is quite cumbersome to update these individually obviously so what I am looking at is this:

UPDATE [WAREC].[dbo].[IV00103]
set Last_Originating_Cost = 2.83
where VENDORID LIKE 'F4300'
AND ITEMNMBR = '200002';

Is there any danger to directly updating this field? I have researched this quite a bit and it seems to be a stand alone field. I don't want to update an exising POs or purchases, just the last vendor price so that when I create a new PO the correct price appears. I create my PO's in SalesPad which sits atop of GP.

Categories:

Dynamics 365 Commerce

Dynamics 365 Supply Chain Management

Hi,

Directly updating the Last_Originating_Cost field in SQL—especially in a table like IV00103 in Dynamics GP—can be risky, even if it appears to be standalone. Here are a few considerations before proceeding:

Data Integrity: While Last_Originating_Cost may not immediately affect existing POs or transactions, it could be referenced by other processes or reports. Manual updates bypass business logic and validations enforced by the application.

Audit Trail: Direct SQL updates do not generate audit logs or history records. This can lead to compliance issues or difficulty tracing changes later.

SalesPad Integration: If SalesPad relies on this field for pricing display, ensure that it doesn’t cache or sync data in a way that could be disrupted by direct updates.

Recommended Approach:
- Use an integration tool or eConnect to update item costs programmatically.
- Alternatively, consider using SalesPad’s import tools or GP’s inventory cost adjustment routines to apply bulk updates safely.