Sales Returns

(0) Share

Report

Posted on by Community Member

When entering a Sales Order Processing Return through Additional>>Create Return, the following message comes up:

"This Cost of Goods Sold distribution amount is incorrect and will not be posted. Do you want to save with errors?"

RMA Receiving is not being used. Version is GP 10 SP2.

I also noticed the the EXTDCOST and OREXTCST values are zero in the SOP10100 table. Also tried voiding and re-entering the Return.

What could be causing this error?

Thanks,

Kendra

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Frank Hamelly | MVP... 46,627 Moderator on at

Like (0)

Report
Copy link

Link copied!

Kendra, are you using Returns Management? if not, then you need to use the Sales Document Type of 'Return' rather than using the Return option under 'Additional'.

Was this reply helpful? Yes No
Dan Liebl 7,320 on at

Like (0)

Report
Copy link

Link copied!

I have also seen this come up when the cost is like .0001 or less than a fraction of a penny so with rounding it was still 0 in GP, but in the tables there was a cost. I would query the SOP10200 tables and check the cost fields for fractions of a penny. This can also happen with kits.

Dan Liebl, CMA CPIM | Senior Consultant | OTT,Inc | DLiebl@OTT-inc.com

Was this reply helpful? Yes No
don@dtm.ca 425 on at

Like (0)

Report
Copy link

Link copied!

We have run into this error as well. It does not happen all the time but the return posts as exoected but the EXTCOST and OREXTCST are set to zero. Do you have any customizations running triggers on your system? The user cannot repair unless they reset the quanities to 0 and reenter new quantities. This works but the pricing is recalulated

Was this reply helpful? Yes No
Brian P Connell 864 on at

Like (0)

Report
Copy link

Link copied!

For the benefit of anyone else getting this.......This error pops up for us when returns' costs get messed up. why..we don't know. for us it has something to do with fx conversions. Here is our fix.....( if you don't know how to use the below script you shouldn't be doing it. get your dba or GP professional to do it. )

--update sop10100 set extdcost = sl.extdcst , OREXTCST = sl.orexcst

--select sl.*,sh.SOPNUMBE,sh.OREXTCST,extdcst

from sop10100 sh

inner join ( select SUM(EXTDCOST) extdcost ,SUM(OREXTCST)OREXTCST ,sopnumbe from sop10200 a where sopnumbe ='ret1234' group by SOPNUMBE) sl

on sh.SOPNUMBE=sl.SOPNUMBE

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

I had similar problem.

EXTDCOST and OREXTCST values in SOP10100 should not be zero, if you have some value in the system.

Update the EXTDCOST and OREXTCST values to the extended cost available in related Sales Order/Invoice/Return Invoice.

I had checked the Invoice extended cost and return Invoice extended cost, I see a minor difference in decimals value.

I had adjusted it from SQL table SOP10100 then the batch was able to POST.

Thank you.

Was this reply helpful? Yes No
Suggested answer

Lyn Barr 1 on at

Like (0)

Report
Copy link

Link copied!

I have this problem sometimes with kit items being returned, where the COGS on the kit is doubled at the header level (SOP10100), but is correctly shown in the lines. In this case, I manually update the SQL table with the correct EXTDCOST and OREXTCST, and then the transaction posts successfully.

Was this reply helpful? Yes No