Thanks for your responses.
It is actually a valid SKU for an item that we track inventory and bill.
To explain it further, the wholesale customer overpays us... say $100 for 1 SKU(unit) and their true price(contract price) is $15.
A month from now, a the wholesale customer sells that unit to a retailer or small store.
The wholesaler transmits back to us, line level detail of the sale out to the retailer (the name of the retailer, the SKU, the qty).
We run the lines through the invoicing program to generate the $85 credit but the qty value is just informational.
Other ERP systems just have different financial reason codes/journal entry models set up for the different types of lines that flow through billing.
This type would generate a credit but not touch inventory even thoughit is for a SKU that we track inventory on.
We would want these transactions all applied to the one SKU so that we could net out the overpriced sale against the credit back to the wholesaler for the selling the unit to the retailer, to get the $15 in the example.
The consultants here set up a dummy SKU for each item to process these credits.
So sales go against one SKU and these credits go against a different SKU even though it is for the same item.
Thanks.