Sales Posting Help

[ehojr]

7.6.200 sql 2000. We had an invoice that encountered a duplicate invoice error during the post invoice process from o/e. The posting process was partially completed for the first 7 line items on the invoice. The last three line items were properly stopped from posting due to the duplicate invoice number. No processing at all and the correct procedure for macola to follow... The first seven line items correctly created the I/M distributions for cogs. The seven line items created the credit for the a/r entires but failed ot create the debit for accounts rec. The seven line items are no where in oe history. I do see these seven line itmes upon viewing the order history from a/r module.

Is it possible to fix the oehistory in the oe module.

 

[ThunderForest]

I use v7.5.103d Pervasive/SQL. I know, Jurassic Park. I know there's a vast difference, including a vast improvement in your version, but when this happens during invoice posting it's usually caused by some rogue record lock or some Macola WMS (formerly SAS) interaction. Also, when the size of OE history tables get rather large, reducing the quantity of invoices to post at one time greatly minimized problems such as yours. This is not to say that's what caused your problem. To resolve the problem, I create the missing records and insert them into whatever table they're missing from. It is very unfortunate that in my version the first records to be removed during the posting process are those from OEORDHDR and OEORDLIN, the open orders. In my opinion, they should be the last because you need this data when a problem such as yours occurs. When this problem involves large or several orders, resolving this is typically short of a nightmare or like a Monday morning.

Getting answers before I'm asked.
Providing answers if I can.

 

[ehojr]

where does the view in a/r pull it's order history infromation..the records are in that table...I hate to insert with macola..

 

[ThunderForest]

Speaking from the v7.5.103d perspective, when you post an invoice, records are also inserted into the AROPNHST table, which is one of the first steps that occur in posting an invoice. The information is limited in A/R, ie, CUSTOMER NO, APPLY TO NO, TOTAL AMT, and some reference info. You need the O/E history header (OEHDRHST table) and item detail (OELINHST) in order to recreate the invoice detail. If the records aren't there, you have to insert them via an SQL statement or with some database tool. When this type of problem happens, you also can't really tell if the dollar amounts made it to the OESLSHST table, the OE Sales History table - unless you have a copy of the table before posting. This also goes for the A/R customer accumulators in the ARCUSFIL table. Messy, isn't it?

Getting answers before I'm asked.
Providing answers if I can.

 

[ehojr]

Yes, I knew it would be..

 

[NEmacGuy]

When you post invoices in Order Entry, they don't go to the OESLSHST file. Posting invoices moves the invoice to the OEHDRHST and OELINHST, update inventory and ar (not in the order listed). The OESLSHST is populated when you post sales history. This reads the OEHDRHST for the date range that you enter, posts to the OESLSHST, and flags the OEHDRHST as posted.

Now to Whorjr, yes you can edit the OEHDRHST and OELINHST dirrectly thru standard Macola using the OE-Sales-History Load function. Althought intended for a new site to load sales history, it will also allow you to edit posted data.

Proceed with care.

 

[ThunderForest]

NEMacGuy

You are correct. My point was that if the records are not in OE history to begin with, OESLSHST and AR accumulators will not reflect accurate totals.

Getting answers before I'm asked.
Providing answers if I can.

 

[ehojr]

Thanks a lot. The sales history load took care of the order history files. This was our primary concern..